Skip to main content
NetApp Knowledge Base

WFA custom workflow does not populate variable in WFA 5.0 and 5.1x

  1. Last updated
  2. Save as PDF
Views:
221
Visibility:
Public
Votes:
0
Category:
oncommand-workflow-automation-wfa
Specialty:
legacy
Last Updated:

Applies to

  • OnCommand Workflow Automation (WFA) 5.1.1, 5.0
  • Custom workflow
  • User Inputs
  • Variable

Issue

  • A custom workflow in WFA does not populate a variable that should hold the new qtree name
  • This workflow worked successfully in the old version of WFA (prior to WFA 5.0) and stopped working once we changed to the HTML UI.
  • The custom workflow fails with error:

The value for input $variable_to_catch_new_qtree_name has to be provided

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.