can workflow container in log change?

[Barr, Chris]

Thanks! I created a new workflow container element and added a container step as the first step in the workflow. Now I can see that the virtual attribute of my object is in fact blank when the workflow begins. After the workflow is completed the attribute is getting changed in the workflow log. It looks like this happens (the value changing in the log) with virtual attributes but not database attributes.


Chris Barr
Lockheed Martin - Enterprise Business Services
MD 0751
1801 State Route 17C , Owego, NY 13827
607-625-3929
chris.barr at lmco.com<mailto:chris.barr at lmco.com>
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Munday,Sherie J.
Sent: Wednesday, September 30, 2009 1:33 PM
To: SAP Workflow Users' Group
Subject: RE: can workflow container in log change?

Hi Chris,
One other thought.... If you want an attribute of an object to be constant, you should store it in a separate element via a container operation.  We do this a lot with HR flows because as you make changes to the object, the attributes of that object can then change.  If you want a true snapshot of an attribute at a point in time, you need to preserve it in an element of its own.
Kind Regards,
Sherie

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Munday,Sherie J.
Sent: Wednesday, September 30, 2009 1:24 PM
To: SAP Workflow Users' Group
Subject: RE: can workflow container in log change?

Chris,
This is just a thought, but have you thoroughly tested the Condition Step?  We have found that Case sensitivity and spacing sometimes give us results we did not expect.
Best Wishes,
Sherie

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Barr, Chris
Sent: Wednesday, September 30, 2009 1:16 PM
To: sap-wug at mit.edu
Subject: can workflow container in log change?

I have a virtual attribute, UsageDecision, on ZBUS2045 subtype of BUS2045 - Inspection Lot. In custom code an Inspection Lot is Created and then later in the code a Usage Decision is made. My workflow is triggered from the CREATED event. The first step in the workflow is a Condition Step that should just complete the workflow if UsageDecision = AIM. The Condition Step continues the workflow as if UsageDecision was NOT equal to AIM. But in the workflow log in the workflow container I see UsageDecision set to AIM. I couldn't figure out why the Condition Step would not have seen that. I have heard that the workflow container is dynamic and can change after the workflow is Completed. Which would mean that when the Condition Step executed the UsageDecision was not set yet and that's why the workflow continued. Is this true? I thought that the workflow container in the log would have been a snapshot at that point in time that it was used.


Chris Barr
Lockheed Martin - Enterprise Business Services
MD 0751
1801 State Route 17C , Owego, NY 13827
607-625-3929
chris.barr at lmco.com<mailto:chris.barr at lmco.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090930/076786d5/attachment.htm