3661841 - Workflow Rules Cross-BO Scenario

When a Workflow Rule is created for a specific Business Object and it involves changes in another Business Object - it is called as cross-BO scenario.

For example:

A Workflow Rule was created for Contacts BO with below information:

• Type = Action.
• Conditions = Account ID (Before Object Change) not equal to blank AND Account ID equal to blank.
• Trigger action = Flag as Obsolete.

When removing a Contact relationship from an Account, or removing an Account relationship from a Contact, either ways the Workflow Rule is not triggered.

SAP Cloud for Customer

In C4C, the Account, Contact, and Relationship are each treated as independent Business Objects. A Workflow Rule was created for the Contact Business Object; however, the change is performed on the Account, specifically by deleting a Relationship (i.e., removing the Contact from the Account). The same applies when the Relationship of an Account is deleted from within a Contact.

This is known as a cross-BO scenario. In these cases, Workflow Rules are not triggered by default. To enable rule execution in such scenarios, the Late Condition Evaluation switch must be activated in the backend. With this switch enabled, an additional evaluation phase is introduced during the finalization step, allowing conditions to be assessed after all related data has been loaded.

However, certain aspects of the workflow logic must be understood:

• When a Workflow Rule is defined for the Contact BO, the triggering change must be executed directly on the Contact. If the Contact is deleted from within the Account, the rule will not be triggered - even if Late Condition Evaluation is active. Instead, the Account must be removed from within the Contact to ensure proper triggering.

• Additionally, the rule will only be triggered if, after the change, no Accounts remain associated with the Contact. For example, if a Contact is linked to three Accounts and only one is removed, the condition “Account ID equal to blank” will not be met, as other Accounts are still maintained. Therefore, to ensure the rule is triggered, it must be verified that the Contact has no remaining Account relationships in the "Relationships" section following the change.

Activation of the Late Condition Evaluation switch is performed by SAP in the backend system and is not accessible through the standard C4C UI. Therefore, a request must be submitted to SAP Support to enable this feature for the tenant.

WKF, EVAL, VAL, BP, business partner, not working, doesn't work, cannot work, cannot trigger, sales, leads, opportunities, employee, individual customer, tickets, service, cross BO , KBA , LOD-CRM-WKF , Workflow , Problem

SAP Cloud for Customer core applications all versions