nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Option List In Workflow

bgeorge

Hi All,

I have a workflow that has the possibility to deploy content to n environments, but not necessarily always to all n environments, but rather a combination of any of the n, where the combination can change from job to job(eg. one deploy could be to all n environments, another deploy could be environments 1, 2, 5 & 9, yet another just environment 4, etc.) I would like to provide the user with an option list, preferable a checkbox list, that is available at the task that precedes a deploy task, from which the user can easily select the environments he/she would like to deploy to. This option list can be embedded in the task window, or a pop-up window. Is this possible to do, and if so, how would I do this, and how would I get a handle on the return values of these checkboxes? I am trying to stray away from having all possible permutations of the n environments as buttons that transition from one task to the appropriate deploy task, as this is just plain ugly. I am also trying to stray away from having a one-to-one mapping of transitions to respective deploy tasks and looping back to ask if the user wants to deploy to another environment. Lastly, I'm trying not to make the user perform this select at workflow instantiation via datasources, as it is not uncommon for the number of environments to deploy to to change during a job. As such I'd like to save this selection process for as late in the workflow cycle as possible. Thanks in advance!

Find more posts tagged with

Comments

nipper

Cool, sounds like fun. You should be very busy for the next couples months.

Was there a question there or are you just showing off your technical prowess ?

The only question I saw was how to get the value of a check box, is that your only issue ?

bgeorge

Hahaha yes that's my question: how do I go about adding these checkboxes to the appropriate task, and how do I get a handle on their values?

ISCBorisB

Hahaha yes that's my question: how do I go about adding these checkboxes to the appropriate task, and how do I get a handle on their values?

You can code wft (or modeler Form) JS "call-back" function to set Form Fields. Then create a CGI Script or Servlet that presents a matrix of
check boxes or some other GUI you like. Within CGI-generated code use Java Script "opener" attribute of window object to gain access to "call-back"
on "Apply" button click, etc...

Alternatively, use starting CGI Task with the GUI similar to one above. Set Task's "start" and "immediate" Flags to true and make sure that WF owner is a Task
owner as well, that'll open up your CGI window immediately. From CGI you can (for example) set WF variables indicating User's choice that following
Deplyment task(s) can obtain.

nipper

Hahaha yes that's my question: how do I go about adding these checkboxes to the appropriate task, and how do I get a handle on their values?

You did not mention TS level or WFM/WFT. But assuming WFT, can you make this determination at WF instantiation ? It is trivial to put some check boxes in the comment window (or a select list) and read the data in a variable.

bgeorge

I'm using TeamSite 6.7.1.0, Build Number 60750, and Workflow Modeler 1.0.

moonkhanna

you need to use configurable variables..

Adam Stoller

you need to use configurable variables..

Based on the statement that bgeorge does not what to prompt for this during workflow instantiation, but rather wants to do this selection just prior to the actual deployment task - I believe that the 2nd part of ISCBorisB's response is pretty much on the right track:

Alternatively, use starting CGI Task with the GUI similar to one above. Set Task's "start" and "immediate" Flags to true and make sure that WF owner is a Task owner as well, that'll open up your CGI window immediately. From CGI you can (for example) set WF variables indicating User's choice that following Deployment task(s) can obtain.

The changes I would make to the above are that the cgitask needs to precede the deployment task, and that it can only be "immediate" if the task preceding the cgitask is a usertask (or grouptask or another cgitask) owned by the same user - otherwise the owner of the cgitask will have to manually initiate the interface for selecting the target nodes.

Then capture the selections via standard javascript practices and reprocess the selections so that they can be parsed as form variables in Perl and then use the TeamSite::WFworkflow: Smiley Frustrated

etVariable() method to set the value(s) in the workflow.

Unfortunately, for the deployment task a customized script will need to be created to run there - and have it retrieve the values from the workflow and then figure out how to pass that through the OD command line to the deployment configuration file to have it "do the right thing"

Have fun ...

moonkhanna

Based on the statement that bgeorge does not what to prompt for this during workflow instantiation, but rather wants to do this selection just prior to the actual deployment task - I believe that the 2nd part of ISCBorisB's response is pretty much on the right track:
.

Adam, My response was in continuation with Bo's response only. He needs to use Config variables to capture the values of servers he wants to deploy to from the CGI Task, then pass this on to his deploy script.

Adam Stoller

Adam, My response was in continuation with Bo's response only. He needs to use Config variables to capture the values of servers he wants to deploy to from the CGI Task, then pass this on to his deploy script.

It wasn't clear since you didn't actually quote Bo's text in your response.
What do you mean by "Config variables"?

moonkhanna

It wasn't clear since you didn't actually quote Bo's text in your response.
What do you mean by "Config variables"?

Hi Adam, Its the configurable variables used by the WFM. SO basically, he will need to define these configurable variables in WFM and then code the CGI in order to collect values for these Configurable variables.. These variables can then be used to pass values to an external task that runs a deploy script which does the deploys to selected targets..

bgeorge

Thanks for all the comments so far, here's an update. I had to update Workflow Modeler to version 1.0.0.1 Build 68006. I have a dummy workflow with a user task going to a cgi task which calls my cgi script. From the cgi task, I'm calling my cgi script as follows:

/iw-bin/custom_script.cgi

When I step through the workflow from the user task to the cgi task, I get an Internal Server Error and the script wont run. I know there's nothing wrong with my script because up to where I was in coding the script, was working fine before the Workflow Modeler upgrade. So, it has to be a configuration problem. I have set the owner of both the user task and cgi task to the same user, and have set the cgi "immediate" value to true. Any suggestions?

Adam Stoller

Thanks for all the comments so far, here's an update. I had to update Workflow Modeler to version 1.0.0.1 Build 68006. I have a dummy workflow with a user task going to a cgi task which calls my cgi script. From the cgi task, I'm calling my cgi script as follows:

/iw-bin/custom_script.cgi

When I step through the workflow from the user task to the cgi task, I get an Internal Server Error and the script wont run. I know there's nothing wrong with my script because up to where I was in coding the script, was working fine before the Workflow Modeler upgrade. So, it has to be a configuration problem. I have set the owner of both the user task and cgi task to the same user, and have set the cgi "immediate" value to true. Any suggestions?

Try removing the /iw-bin/ at the beginning and just specify: custom_script.cgi

ProtocolListViewerfinalsamle.rptdesign

bgeorge

Try removing the /iw-bin/ at the beginning and just specify: custom_script.cgi

Actually, after messing around with it, it turns out that you need to call it like this:

/iw-bin/iw_cgi_wrapper.cgi/custom_script.ipl/

for Workflow Modeler 1.0.0.1(in case anyone else is having same problem). Still working on trying to get a handle on workflow parameters. I'll update on that soon. Thanks all!

bgeorge

Alright, looks like everything is good to go. Thanks everyone!