2697542 - Approver Step Assignment and Removal or Approver Replacement Logic

 Workflows steps population and removal logic behavior in different scenarios.

SAP SuccessFactors Employee Central - Workflows

Workflows steps population and removal logic or restrictions:

• For Role = Self, Employees Manager (EM), Employees Manager's Manger (EMM), and Employee HR (HRM):
• If the self/EM/EMM/HRM - If the first step approver and the initiator is the same as the approver, the first step is removed.
• In the workflow in-flight change time (If an approver updates the workflow and causes the workflow to start over again):
• The first step will NOT be removed.
• The initiator needs to approve the first step because someone change the initial data.
• If the self/EM/EMM/HRM role is used in two subsequent steps approver, one step is skipped to avoid redundant approver.
  
  
• For Dynamic Group & Position & Job Relationship:
  • If the dynamic group or position is the first step approver and the initiator is one of the members, this step is not removed because any other member in the group can approve the workflow.
  • Even when the dynamic group only has one member and the initiator is the member, this step is not removed because we keep the same behavior as if there were multiple users as apart of this dynamic group or multiple incumbents of the position.
  • If the subject user is a member of the dynamic group and Position and job relationship, we change the approver to subject user's manager.
    The one exception is for a Position workflow: In a position workflow:
    • If the subject user is also the initiator, and if the subject user is member of the dynamic group &Position & job relationship, we DON'T change the approver to subject user's manager.
      
      
• For Self Approver type:
  • If the relationship to approver is the Employee, the approver equals the subject user. If the resolved approver equals the subject user, this step will NOT be replaced by the subject user's manager.
  • If the relationship to approver equals Initiator, the approver equals initiator.
    
    
• For Dynamic roles:
  • If the dynamic role is the first step, and If the resolved Role type = PERSON, and the person is also the initiator, this workflow step will be removed.
  • If the dynamic role is the first step and If the resolved Role type = Dynamic group or position, and the initiator is one of the group member, the step will NOT be removed.
  • If the dynamic role's resolves to a Role type = PERSON, and the person is also the subject user, the approver will be changed to the subject user's manager.
    
    
• Dynamic Role with Job Info as Base Object:
• This can be used for the following Transaction Types:
• Any Employee Central HRIS Element Workflows.
• A MDF Workflow if the Workflow Subject is User Based.
• Do not use Dynamic Roles if the Workflow subject is for creating an Object in the system.
• The system will use the subject user's job information to match the Dynamic Role assignment
• If the workflow is object based, the system uses the Workflows Initiator's Job Information to match the Dynamic Role assignment.
• If a Job Info base Dynamic Role is used for a Position Workflow - the system will use the initiators Job Info data to match the dynamic role assignment.
  
  
• Dynamic Role with Position as Base Object:
• This can be only used for a Position Workflow.
• It will use the Subject Users Position Information to match the Dynamic role assignment.
• If it is a Position Dynamic Role listed as the workflow step, the step will be removed when populating the workflow steps.
• If a Position Base Dynamic Role is used in a "Position Workflow" - the system will use the Changed Position Field to match the dynamic role assigment.

Initiator logic and auto replace approver logic

• For EC workflows:
  • If the initiator is a member of a dynamic group or Dynamic Position, the initiator can approve the workflow (as the approver) and can withdraw the workflow (as the initiator).
  • If the subject user is a member of a dynamic group or dynamic position, or if the dynamic role resolves to a PERSON type and the person also is the same as the subject user, we will replace the approver as the subject user’s manager.
    
    
• For MDF workflows:
  • If it is a USER based MDF entity, such as a Time Off workflow or a Time Sheet Workflow, the initiator and subject user are different entities;
  • If the workflow is Object based, such as a Migrated Foundation Object Workflow, The Initiator and subject user are the same entity;
    • If the initiator (subject user) is a member of a dynamic group or dynamic position, or if the dynamic role resolves to a PERSON type and the person is also the subject user, the system will replace the approver as the subject user’s manager.
    • Exception:
      • If it is a Position MDF Workflow, and the initiator and subject user are the same, the initiator can approve the workflow (as the approver) and can withdraw the workflow (as the initiator).
      • We do NOT replace the approver with the employee's manager.

SFSF, SFEC, Position, WFL, PosObj, Base Object, MDF, Assignment, approver behavior, Workflow Logic, remove logic, how system derive Dynamic Role Assignment, Dynamic Role populating, remove step approver, dynamic role,  behavior for base objects with use of Dynamic Roles, time off workflow, time sheet workflow, position workflow , KBA , LOD-SF-EC-WFL , Workflows - Configuration, Tools, Objects & Rules , LOD-SF-EC , Employee Central , Problem

SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HXM Suite all versions