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; } } }

WFM Global Variable??

Amanpreet

I am using WFM 1.0.0

1. I have declared one global variable with a default value (let say A).
2. Then I am changing this its value in an external task to B (using $job->SetVariable (variablename,"B"))
3. Then I am accessing this global variable in a userTask ("$IW_CV (variablename)").
The problem is that I want modified value (B) but the variable is returning default value (A)
4. When I checked job properties its show modified value, but in task properties it show default value.
5. When I access this variable in external script it’s showing modified value.

Please help me.

Find more posts tagged with

Comments

Nikunj

Hi,
Try it with workflow variable..(i.e One you see as "TaskVariables" in workflow properties..and not for particular task)..instead of Global variable...Make that configurable...if you are planing to use that in some user task script.

Experts i really need clarifications regarding difference between Global and workflow variables.
Because pdf just mentions few line about global variables.

Adam Stoller

I am using WFM 1.0.0

1. I have declared one global variable with a default value (let say A).
2. Then I am changing this its value in an external task to B (using $job->SetVariable (variablename,"B"))
3. Then I am accessing this global variable in a userTask ("$IW_CV (variablename)").
The problem is that I want modified value (B) but the variable is returning default value (A)
4. When I checked job properties its show modified value, but in task properties it show default value.
5. When I access this variable in external script it’s showing modified value.

Please help me.

The specification within the workflow model to use a value of "A" is what gets incorporated into the definition of the User Task during instantiation. Since the User Task is just that - a non-scripted task - the fact that you change the job variable value to "B" has no affect on it.

I'm not sure what purpose there would be in utilizing a variable for a User Task -- can you perhaps give a more detailed use-case scenario of what you are trying to accomplish? We might then be able to provide you with a better means of accomplishing it.

Amanpreet

Actually what I require is selection of reviewer group/groups name in between a workflow .For this I have employed a CGI task which helps user select the required group names. Now these selected names should be the ones performing the review in the review task which follows the CGI task.
Here is the exact scenario

1. CGI Task: Here user selects multiple groups from a drop down.
In this task I am setting a job/global variable with the groups name (multiple groups).
2. Email Task: In this I am sending email to multiple groups selected by user in the previous task. (No of groups and name will differ according to user selection). For sending email I need these group name.(therefore job/global variable)
3. Review Task: Lets say if there are six groups for selection in CGI task. Then there should be 6 review tasks and only those corresponding to the groups selected by user in CGI task should get activated. (I still haven’t found a way to achieve this).
4. After getting approval from all the groups, workflow will transition to next task.
Can anyone please suggest a workaround for this instead of using global variables?

mstradling

Set the Review task to be shared by a CV. If you have a default group name you can use that but if you will always be setting in in your CGI you can use a dummy group.

In the CGI you can use the WFTask and WFWorkflow modules to get the WFTask object of the Review task and should then be able to change the value of the SharedbyGroup CV.

I've recently done something similar but using a custom instantiation form and a PostProcess class. The group was defined as a CV that was rendered in the instantiation form as a list of approval groups. When the user clicks the instantiation forms 'Next' button the PostProcess class is automatically run. You get a workflow object and fro that can get to the Review task object and user the setSharedByGroup() and removeGroup() methods to set the value of the CV.

Adam Stoller

...
3. Review Task: Lets say if there are six groups for selection in CGI task. Then there should be 6 review tasks and only those corresponding to the groups selected by user in CGI task should get activated. (I still haven’t found a way to achieve this).

You cannot dynamically add or remove tasks in the middle of an instantiated workflow - at least you could not do so with WFTs, and I do not believe you can do so with WFMs either.

You have to indicate the number of review tasks you want at (or before) job instantiation.
One way to do this "within" the workflow is if you then spawn N sub-workflows for each of the selected reviewing groups.
Another way to do this is to define M (max-possible review tasks) up front, and then based on the number of groups selected in your CGI - transition in such a way as to activate those N (review tasks) you want activated - this can result is rather obscure and confusing code to properly determine the conditions under which you achieve "approved" status though -- you're generally better off pre-defining the number of review tasks up-front and only creating instances of the review tasks that you need and will use.

Nikunj

Hi,
Insn't there something like concurrent reviewer work flow..If am not wrong there is one default provided by TS...Check out the work flow doc.

Adam Stoller

Hi,
Insn't there something like concurrent reviewer work flow..If am not wrong there is one default provided by TS...Check out the work flow doc.

Yes there are concurrent workflow processes - but what does that have to do with the price of tea in China? Neither serial nor concurrent review processes allow you to dynamically add (or remove) review tasks within the process flow after the job has been instantiated.

Nikunj

ya sorry i got bit out of track.
So as you said best option would be to allow user to select the Reviewers at instantiation screen it self.
This could be global configurable variable. So that you can use in script and add logic to it...
(Correct me if am wrong..)
Amanpreet is this not possible? I mean can't you add this to instantiation screen...some requirement constraints?
Adam i did not get you clearly on your second suggestion..It is interesting....

Adam Stoller

ya sorry i got bit out of track.
So as you said best option would be to allow user to select the Reviewers at instantiation screen it self.
This could be global configurable variable. So that you can use in script and add logic to it...
(Correct me if am wrong..)
Amanpreet is this not possible? I mean can't you add this to instantiation screen...some requirement constraints?
Adam i did not get you clearly on your second suggestion..It is interesting....

Any way you go - you have to do some programming and you need some information up-front. The basic choices are:

There may be other alternatives that I'm not thinking of right now, but that's pretty much the lot.Basically - get as much information as possible up front so that you can properly define the process when the job is instantiated and do far less dynamic voodoo.

Amanpreet

Can we use DataSource variables (which call java class), So that we can write output of CGI task to flat file and java class will read from this flat file.
The available group parameter in Review task can have value as above mentioned DataSource variable.
Now my question is this: When will be the class called would it be on instantiation of workflow or when this review task’s object is created /task starts.
In the later case we can have dynamic selection of reviewer group but if the variable is evaluated on the instantiation of the workflow then dynamic selection won’t be possible.

Any views on this?