Workflow start conditions with custom attributes

[Rick Sample]

If the BO is working as expected:
Check bindings between the events and Template / Tasks. 
Check BO event parameters and WF Template containers are same data types.
For the Template this is in the triggering events. If you have parameters in the event like CREATED  
event then the you are passing in parm values like &ZyourValue& not &_EVT_OBJECT.ZyourValue&. 
 
Dumb things to check:
Make sure you do not have "Initial Values" set to anything. I did this ONCE and it 
took a while to figure out. I had an Initial Value set to zero and nothing ever 
passed in the WF template on CREATED. (Humbling experience!) 
 
Template and Tasks set to General Tasks. 
 
Rick
 
 
 
>>> jocelyn.dart at sap.com 10/4/2004 19:01:33 >>>
Swami,
I've used custom attributes, both database and virtual, in delegated objects many many many times in start conditions without any problem.
 
Check your logic - e.g. is the attribute value known at the time the event is raised, is it dependent on any other attributes (in which case have you made sure that other attribute has already been calculated at the time your attribute is calculated).
 
Check you have put your object/attributes in "released" status.
 
Check you have refreshed buffers.
 
Check your start condition is correct - e.g. if you are comparing to alphanumeric constants check the characters are correct in upper/lower case.
 
Check your start condition/event linkage is correctly active (remembering that depending on how you did it, maintaining the start condition can deactivate the event linkage so that you need to reactivate it).
 
Rgds,
Jocelyn
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of Swami Bala
Sent: Tuesday,5 October 2004 5:16 AM
To: SAP-WUG at MITVMA.MIT.EDU 
Subject: Workflow start conditions with custom attributes
 
Hello,
 
I have the custom bus object delegated to BUS2081 and defined a custom
attribute for PO order type ( DB attribute). In the start condition I am
trying to check for specific order types before triggering the workflow. But
it looks to me that when the start conditions are evaluated this attribute
value is still not available. To validate this point I tested the start
condition with PO Order type eq space. It works, meaning the value is not
available when the start condition is being evaluated. When the Bus object
is executed as a standalone everything works perfectly.
I would like to make sure  if this is true. Do i have a better solution in
this situations ?
 
Thanks
 
Swami Bala