You have created a Workflow Rule to run on Tasks (we will use Tasks as example, this is the same for any object in the system) that were created by a previous Workflow Rule.
SAP Cloud for Customer
Reproducing the Issue
Let's suppose this scenario:
- You have Workflow Rule ABC (ABC represents the Workflow Rule Name) set to create Tasks on a Ticket based on a set of conditions.
- Also, you have another Workflow Rule 123 (123 represents the name of a second Workflow Rule) that is set the Task created by Workflow Rule ABC.
This results in:
- Workflow Rule 123 is not working for the Tasks created by Workflow Rule ABC, even though the meet the conditions.
- Workflow Rule 123 works fine for manually created Tasks that meet the conditions.
Workflow Rules do not work for objects that were created by another workflow rule. Same is valid for Workflow Changes in objects that would trigger another Rule. They don't work.
This is the system expected behavior.
The system has been designed this way to serve as a defense mechanism for loop scenarios. The idea is to avoid that a Workflow Rule has to create an object based on another Workflow Rule created object, which could lead to a loop and hence performance issues.
Workflow Rule ; not working ; Tasks ; Action ; Activity Tasks ; , KBA , LOD-CRM-WKF , Workflow , How To