-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workflow variables should not include command keywords #28
Comments
@jlczuk |
Great! Thanks Eduardo. Would you like me to identify the other workflow definitions that are doing this same thing? So far, I only looked at the ZFS Define workflow definition. |
Signed-off-by: Eduardo Rocha <[email protected]>
@jlczuk I would be thankful, I do think however, this is the only one and honestly , looking at it now I don't quite understand why I opted to do it like this. |
I'll look through them anyway just to be sure. It shouldn't take too long. |
The USS category of workflows does not have a README.md |
That's what I found. |
@jlczuk Thank you... I will fix them all. |
Fix for Issue #28 , removed keywords from prompt (Variable definition updates - CTF)
@erocha Feel free to close this if you're done. |
@ehrocha
I was inspecting this workflow: https://github.com/openmainframeproject/zorow/blob/master/IBM-GTS-Workflows/PA-zOSMF-Workflows-ZFS/IBM-MF-AUTO-ZFS-DEFINE.xml
I noticed that workflow variables are prompting users to enter utility keywords along with the actual variable content needed. For example:
<variable name="zfs-sms-dc" scope="instance" visibility="public"> <label>Data Class</label> <abstract>If coded, the syntax for this parameter is DATACLAS(DC_NAME)</abstract> <description>If coded, the syntax for this parameter is DATACLAS(DC_NAME)</description> <category>SMS</category> <string valueMustBeChoice="false" multiLine="false">
This variable input forces the user to have to know the utility keyword DATACLAS in order to enter the actual information the workflow needs, which is the NAME of the data class to use.
Why wouldn't you just prompt for the VALUE for DATACLAS and substitute that into the workflow like this?
#if($zfs-sms-dc != "") DATACLAS($zfs-sms-dc) - #end
I suspect this is being done in nearly all the GTS workflows.
The text was updated successfully, but these errors were encountered: