Symptom
When an object is getting created, how does 'Before Object Change' condition gets interpreted by the system?
Environment
SAP Cloud for Customer
Reproducing the Issue
- Create a Workflow Rule with Before Object Change condition
- Create an object to see the behavior with respect to the above Workflow Rule
Resolution
When an object is being created, Before Object Change for all fields are 'empty'.
For example, you are creating a Opportunity with Document Type XYZ. You have workflow condition as 'Document Type (Before Object Change) Not Equal to XYZ'. You expect this condition to fail, but it actually fulfills the condition. The reason is that Document Type (Before Object Change) is 'empty' as all the other 'Before Object Change' fields are 'empty'.
Keywords
Before Object Change, workflow rule, condition, creation , KBA , LOD-CRM-WKF , Workflow , Problem