3801889 - When user status changes from active to inactive, inactive user will be removed from Non-Permission Group - SAP SuccessFactors HCM Core

When user status changes from active to inactive, inactive user will be removed from Non-Permission Group automatically.

After those users become active again, the active user won't be added back to Non-Permission group.

1. User status changes from Active → Inactive.
2. The hardcoded logic removes the user from the corresponding Workflow Group.
3. User status changes back from Inactive → Active.
4. The system does NOT re-add the user to the group, as it is treated as a Static Group and is no longer refreshed.
5. The Workflow Group remains incomplete — the user won't be added back to this Workflow Group.Since Workflow Groups are used to determine Approvers in the approval process, missing group members result in the workflow being unable to identify a valid approver — causing the workflow process to stall and fail to proceed.

We introduced a hardcoded logic: when a user's status changes from Active (t) to Inactive (f), the system automatically removes the user from all non-Permission Groups that do not support Inactive users, executed directly via SQL.

Currently, only COMPENSATION ELIGIBILITY Group supports inactive users. Therefore, aside from Permission Groups and the COMPENSATION_ELIGIBILITY Group, any user transitioning to inactive status will be removed from all other groups — including EC Workflow Groups.

Inactive user won't be deleted from the COMPENSATION ELIGIBILITY Group and Permission Group when the active user become inactive.

active users,inactive users,workflow group,employee group,EC Workflow Groups,COMPENSATION ELIGIBILITY Group , KBA , LOD-SF-PLT-RBP , Role Based Permissions , LOD-SF-EC-WFL , Workflows - Configuration, Tools, Objects & Rules , LOD-SF-MDF-WFL , Custom Object based Workflows , How To