virtual attribute retrieval fails at WF condition step

[Svanikier, Helena]

Hello Torsten
 
Could it be, that your users are lacking certain authorisations to =
access the data used to fill the virtual attribute?
 
I ran into this problem, when I was working with HR-Objects.
 
Best regards
Helena Svanikier
Workflow consultant SAP Switzerland
 
-----Original Message-----
From: Torsten Schnorpfeil [mailto:torsten at processflow.de]
Sent: Montag, 10.M=E4rz 2003 03:15
To: SAP-WUG at MITVMA.MIT.EDU
Subject: virtual attribute retrieval fails at WF condition step
Importance: High
 
 
Hi guys,
 
here's the thing I need your input since it happens on the production =
system:
 
At one point in the customer workflow is a condition, which is based on =
the value of a virtual attribute of the object. A very high percentage =
of workflow instances run into the error WL482/OL826, when the workflow =
comes to this step.
 
In order to build a work-around for the fact the workflow has =
difficulties to process a virtual attribute in a condition, I created a =
container operation, which transfer the value of the attribute to a =
container element right before the condition.
 
Both scenarios work fine in Dev. and QA, but they fail in PROD!!! =
Another strange thing what stroked me, is that this error occurs with =
users which are at a certain facility. From the other facility it works =
fine (might there be any network/connection issue?).
 
As a backup, I'm thinking about creating a method, which actually =
selects the value from the table and imports it as a container element. =
But hey, if you have to built a work-around for a work-around the whole =
thing gets kind of silly.
 
Any input highly appreciated!
 
Cheers,
 
Torsten