Why step condition do not respect the container's values?

[alonso_valenzue]

Hi Gurus,

In a workflow, I'm trying to evaluate some values in a condition step.

At moment the condition evaluate the values of some object's attributes at container, those values are empty, and I get a FALSE result.

When I review the values at workflow log (SWI6), the values are correct.

Why step condition do not respect the container's values? Is this problem because I'm using object's attributes in the comparisons? I must let pass a time before making the comparison of values?

[former_member185167 · Accepted solution]

Hello,

Is it a database attribute or a virtual attribute? Has it been recently updated?

Sometimes you do have to put in a dummy wait step (eg set a requested start deadline of 1 minute) to refresh the buffer if there's been a recent change.

What condition are you testing - you're sure it's giving the wrong result for that value?

regards

Rick Bakker

Hanabi Technology

[alonso_valenzue]

I solved the problem obtain the value correct with an object's method. I tried with a 2 minutes waiting task, but doesn't work. Thank to everybody.

[former_member185167]

Hello,

But how did you solve it, if not with a waiting step?

regards

Rick Bakker

Hanabi Technology

[Former Member]

I think it is a timing issue. Most probably the attribute is not getting updated when the condition is checked. I think you can put some logic in the code unless a mandatory field in table is getting updated you need to execute the code at that point of time.

Thanks

Arghadip

[surjith_kumar]

Hi,

At the Runtime, the Value not set for that attribute. This happens if the values not updated in the Table, because the COMMIT not occurred. I think after few seconds it will work

For the Testing purpose give a wait for '2' Seconds and check it. So that you can understand it, assign accordingly.

Regards,

Surjith

[Former Member]

By the way, what is the workflow you are working with ?

I have faced a similar problem with Service Entry Sheet(SES) workflow where after the SES has been released and saved it updates some table in the background and it takes some time (roughly 5 to 10 seconds).

But after this step I have used a Condition step to get the values from a container and everytime the result turned out to be "False". When I check the container values in the log, its absolutely fine..

The reason was the condition step used to get executed immeadiately after the Release step and it was not able to find values in the container becoz of the 5 to 10 seconds time delay..

What I did was created a activity step(use a dummy method with no code inside the method) with the requested start as "1" minute just above the condition step.

By using this, what ever updates has to happen will happen in the respective tables or attributes and after the 1 minute, the containers get filled and your condition step works absolutely fine...

Hope this helps you....

Regards,

PR.