Cant Access global variable in Conditional Link

Hi,
I am working on WFM and I am able to access a global variable in a URL task (I have used Java API for the same). I am even able to change the value of the global variable.However , when i try to access the same value of the variable in a succeeding conditional link, I am not able to do so.
Has anyone faced this issue before or has any insights on the same, it will be very helpful.

Thanks

Dhru

Find more posts tagged with

Comments

Rick Poulin

In the SCRIPT for your conditional evaluation, you can refer to it as $IW_CV(varname). It helps when you gave your global variable a useful name, instead of the randomly generated ID it gets by default.

Note: global variable != job variable. Conditional links are evaluated at instantiation time, not when your job instance gets to that point. I answered as though you actually did mean global variable, but that part about URLTask implies that you really meant job variable. The only way to choose a path based on that is to have an External/CGI task with multiple default transitions out of it, and having a custom script decide which transition to take based on your instance (job) variables.

sheikh1

I don't think you can update global variables ever. I had similar issues in the past even with job variables updating through cssdk.

I totally agree with Rick, the best way I used is writing an external perl script and update the job variables NOT global variables and return the control back to right task, hope that helps.

AdarshKukanur

Hi rick,
As you have said that conditional links get evaluated at instantiation. Does that mean that i cannot pass it the value of a job variable which i have changed in a preceding external task.?
It is only taking the original value of the job variable. When i try to pass it the value of the variable which i have changed in the external task , it gives an error on instantiation. How do i solve it ?
I have a requirement according to which I have defined a job variable. In the external task , according to certain conditions, the job variable takes different values. Depending on the value of the variable, it proceeds to different conditional links. The value changes in the task, but that same value is not recognized in the conditional link. Any help will be appreciated .

Dhruv B

Adam Stoller

Hi rick,
As you have said that conditional links get evaluated at instantiation. Does that mean that i cannot pass it the value of a job variable which i have changed in a preceding external task.?
It is only taking the original value of the job variable. When i try to pass it the value of the variable which i have changed in the external task , it gives an error on instantiation. How do i solve it ?
I have a requirement according to which I have defined a job variable. In the external task , according to certain conditions, the job variable takes different values. Depending on the value of the variable, it proceeds to different conditional links. The value changes in the task, but that same value is not recognized in the conditional link. Any help will be appreciated .

Dhruv B

Think about what you are asking and what you've already been told.
If the conditional link is evaluated at instantiation time and the job variable is changed during (for lack of a better term) execution time - there is no way that the change to the job variable can have any effect on the conditional link.

Conditional links are only of use if the condition on which they are dependent is set during instantiation time. E.g.: If you can determine during instantiation whether Task-A should transition to Task-B.

If you need the transition from one task to another (one-of-N) to be dependent upon the value of a job (or task) variable that is altered during execution time, you have to use an external (or CGI) task to perform that "conditional" transition during execution time. Conditional links simply don't apply in that situation.