When importing (upsert) an information through an API call, rules that their "Rule Context" are set to not be triggered through Import or Mass Changes, are being triggered either way.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
- SuccessFactors Employee Central - EC imports
- SuccessFactors Employee Central - OData API
This is currently an expected behavior from the system, as Rule Contexts are not respected when importing information through API call (upsert). Development team is under discussion with Product Management for a long term solution.
If you do not want the rule to be triggered by the API user making the call, an alternative that it can be considered is to add an extra parameter at the Business Rule, such as configuring that the User that is triggering the call is not equal to your API User.
2173085 - Business Rules do not trigger when the data is inserted via the API call
2396714 - Odata API: Workflow not triggered from business rule when creating MDF entries via API call
2684271 - Trigger Workflow for Job information / Job history and Termination entities via API
Business rules, context, not respecting, OData, API, trigger, rule context , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-EC , Employee Central , LOD-SF-EC-JOB-RUL , Job Info Business Rules , LOD-SF-INT , Integrations , Known Error