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:Problem with job variable

SoulReaver

Hi ,
Im assigning the value of global variable into a job variable and then changing the value of these job variable in an external task using perl file. When this job variable is used in other external tasks, the change in the value is getting reflected . But when the job variable is used in a timeout link, the default value is reflected and not the changed value.

Find more posts tagged with

Comments

Crsb

are you using it as configurable variable in the timeout link? if so, then the value in the timeout link is populated at the instantiation of the workflow and cant be changed once the job has started.

SoulReaver

Yes , im using it has a configurable variable . What will be the solution for this problem.

Crsb

i can think of 2 ways:
1- set the timeout link value before instantiating the workflow either in a preprocessor or in the instantiation form. this will work if you can move the code you are using to update the job variable to a preprocessor or to something you can do during the instantiation.
2- create custom/timeout link: some dummy external task where you can sleep for as long as you need to before transitioning to next task.

Adam Stoller

If you know the name of the task with the timeout that you want to change, you can have an externaltask script / program access the task object associated with the task and then change its timeout value - if doing this in Perl - look at the perldoc for TeamSite::WFtask; if doing this in Java - look at the CSSDK javadocs.

SoulReaver

After getting the task object . Which property has to be used to get the timeout link value of a particular task ?

Adam Stoller

After getting the task object . Which property has to be used to get the timeout link value of a particular task ?

Have you tried reading the docs?