You have created a Workflow Rule and is using the conditions with Before Object Change on and notices that the rule is triggered even when the object has been created.
SAP Cloud for Customer
Reproducing the Issue
Let us suppose you have a Workflow Rule 123 (123 represents the Workflow Rule Name) to trigger when the Escalation Status of a Ticket is changed.
The conditions of Workflow Rule 123 could be something like below:
- Group 1 - Escalated (Before Object Change) - Not Equal - Escalated.
You notice, however, that when the Ticket ABC (ABC represents the Ticket ID) is first created the rule is triggered even though you did not make changes to the Escalation Status.
Before the creation of the Ticket ABC the value of the Escalated field was 'null' and now it is 1 - Not Escalated.
Since there was a change on it, the rule is triggered as there a comparison of before and after the object change (creation, in this case) and there is a difference.
This is the expected behavior of the system and can happen in multiple cases.
Many fields in various scenarios are never empty, so rules that use the before object change condition will also be triggered upon creation as before there was nothing and now there is a value.
For those cases, you need to adjust the rule conditions to something that would avoid this.
Before Object Change ; Workflow Rule ; Rule Log ; Not Expected ; Error ; Workflow Error ; Ticket ; Opportunity ; Lead ; Quote ; Condition , KBA , LOD-CRM-WKF , Workflow , How To