Problem in condition checking in workflow

InterwovenIsFun

I have a workflow. thers a global configurable variable ,say ID_flag whose default value is set to 0. Theres a task , say task1 which gets the value of this variable and sets it to 0 or 1 depending upon certain conditions. task1 is followed by task2. task2 takes just gets the value of ID_flag and prints it in a log file. the log file gets created succesfully and contains the correct value of the variable.
task2 is followed by an OR gateway. am using the OR gateway to check 2 conditions. say if the value of ID_flag is 1, taskSuccess should be called and if its 0.taskFail shd be called. but the problem is irrespective of the value set in task1,the or gateway is taking its default value and each time going to taskFail..can sumone guide me on this?

Adam Stoller

I have a workflow. thers a global configurable variable ,say ID_flag whose default value is set to 0. Theres a task , say task1 which gets the value of this variable and sets it to 0 or 1 depending upon certain conditions. task1 is followed by task2. task2 takes just gets the value of ID_flag and prints it in a log file. the log file gets created succesfully and contains the correct value of the variable. task2 is followed by an OR gateway. am using the OR gateway to check 2 conditions. say if the value of ID_flag is 1, taskSuccess should be called and if its 0.taskFail shd be called. but the problem is irrespective of the value set in task1,the or gateway is taking its default value and each time going to taskFail..can sumone guide me on this?

Is this WFM or WFT? I assume WFM since the term "global configurable variable" doesn't tend to come up when talking about WFTs.
Are you using a conditional link or are you handling the conditional programmatically within an external task?
The conditional link is processed as part of the instantiation, so it doesn't care what task1 will (or won't) do to the value of the global configurable variable.
Assuming the global configurable variable is also set as a job variable - and assuming that both task1 and task2 are external (or cgi) tasks, then they should be able to reference and modify the global configurable job variable and "do the right thing" - assuming that your code itself does "the right thing"

subreport_act_old.rptdesign