Study guide

9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval

SAP Certified - SAP SuccessFactors Employee Central Core and Position Management C_THR81

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: C_THR81 Exam and SAP SuccessFactors Platform Foundations

1.1 C_THR81 Exam Format, Logistics, and Preparation Plan 1.2 SAP SuccessFactors Suite, Platform Capabilities, and Employee Central Core 1.3 Instances, Provisioning, and Company Settings 1.4 Administrator Types, Super Admin Access, and Admin Center Navigation 1.5 Release Management, Upgrade Center, Release Center, and Consultant Resources

2 Chapter 2: Security, Proxy, and System Administration

2.1 Role-Based Permissions: Groups, Roles, and Target Populations 2.2 RBP Troubleshooting, Reports, and Governance Best Practices 2.3 Proxy Management, Company System and Logo Settings, and Platform Feature Settings 2.4 Admin Alerts, Check Tool, and System Access Settings 2.5 Scheduled Job Manager, Provisioning Job Scheduler, and Execution Manager

3 Chapter 3: User Experience Configuration

3.1 People Search, Action Search, Custom Navigation, Org Chart, and Built-In Support 3.2 Home Page Configuration and Mobile Settings 3.3 E-mail Notifications, Themes, and Company Logo 3.4 Text Replacement, Manage Languages, and Translations

4 Chapter 4: People Profile, Picklists, User Data, and the Metadata Framework

4.1 Latest People Profile, Categories, Cards, and Custom MDF Cards 4.2 Manage Business Configuration and Succession Data Model XML Fundamentals 4.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist 4.4 User Data File, Employee Import, and User Management Tools 4.5 Metadata Framework Enablement and Object Definition Settings 4.6 MDF Fields, Associations, Search, and Security

5 Chapter 5: Business Rules

5.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log 5.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects 5.3 Propagation Rules and Hire/Rehire Rules 5.4 Cross-Entity Rules, Rule Context, and Rule Design Practices

6 Chapter 6: Foundation Objects and Corporate Data Models

6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence 6.2 Foundation Objects: Organization, Pay, and Job Structures 6.3 Configuring Legacy and MDF Foundation Object Definitions 6.4 Foundation Object Associations and Field Criteria 6.5 Country-Specific Fields for Foundation Objects

7 Chapter 7: Employee Data Structures and Permissions

7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers 7.2 Configuring the Succession Data Model with BCUI and XML 7.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data 7.4 HRIS Synchronization and Sync Mappings 7.5 Employee Central Permissions for Administrators

8 Chapter 8: Employee Transactions and Data Maintenance

8.1 Hire, Rehire, Termination, and No-Show Transactions 8.2 Importing New Employees and Updating Employee Data by Import 8.3 Mass Data Management for Job Information, Job Relationships, and Positions 8.4 Employee and Manager Self-Service Permissions

9 Chapter 9: Workflows, Alerts, and Event Reasons

9.1 Workflow Configuration, Participants, Dynamic Roles, and Dynamic Groups 9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval 9.3 Employee Central Alerts and Notifications 9.4 Events, Event Reasons, and Event Reason Derivation 9.5 Workflow Derivation Rules and How They Work with Event Reason Derivation

10 Chapter 10: Optional Employee Central Configurations

10.1 Employee Central Quick Actions and Internal Job History 10.2 Custom Hire Templates, the Diagnostic Tool, and Joule in Employee Central

11 Chapter 11: Position Management Setup

11.1 Position Management Overview: Positions, Jobs, and the Leading Hierarchy 11.2 Enabling Position Management and Setting Role-Based Permissions 11.3 Navigating and Configuring the Position Organization Chart 11.4 Configuring the Position Object 11.5 Position Management Settings 11.6 Creating, Maintaining, Importing, and Mass-Changing Positions

12 Chapter 12: Position Management in the Employee Lifecycle

12.1 Position Fields in Job Information and Hiring Employees to Positions 12.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return 12.3 Manager Self-Service with My Team Positions and Quick Actions for Positions 12.4 Terminations with Position Management and Position Workflows

13 Chapter 13: Position Management Rules, Integrations, and Company Structure

13.1 Position Management Rule Scenarios and Rules for Position Data Entry 13.2 Synchronization Rules and Mass Change Runs for Positions 13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions 13.4 Integrating Position Management with Recruiting and Succession 13.5 Building the Company Structure Overview

9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval

Key Takeaways Explain This Topic AI

Pending workflows are grouped into six categories on the Pending Workflows page, reached from View Pending Workflows.

Delegation requires Is Delegate Supported = Yes on the workflow record, whether it is manual or automatic.

Auto delegation needs the Allow Auto-Delegation permission, and auto-delegation by groups allows up to three delegates.

Workflow reminders use a Workflow Action Reminder job; a value in the job overrides the Remind in Days values on workflow records.

Escalation does not happen when auto-approval is enabled; auto-approval uses a Workflow Auto Approval job and Days until Auto Approval.

Last updated: September 2026

9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval

Quick Answer: Users act on requests from the Home Page (the Approvals card, the To-Do panel , or View Pending Workflows ). Stalled workflows are handled with reminders (Workflow Action Reminder job), escalation paths (Workflow Auto Escalation job), or auto-approval (Workflow Auto Approval job). Delegation requires Is Delegate Supported = Yes on the workflow record.

Where Users See Workflows

Employees track and handle requests from the Home Page. View Pending Workflows organizes requests into six categories :

  • Category Contains
  • My Requests for Approval Requests I submitted that await others (shows who must approve)
  • My Requests Sent Back My requests that were sent back; update and resubmit
  • Pending Requests That I Approved Requests I approved that await others
  • Requests Reassigned to Others Delegated and escalated requests
  • Requests for Comment Requests where I am a contributor
  • Requests for Information Requests where I am a CC role

Requests can be approved from the Approvals card , the To-do panel , or the link Access requests awaiting my approval . To stop quick approval , disable that permission in RBP > Manage Workflows . More filters in My Workflow Requests require Manage Workflows > Professional Edition Manage Workflow Requests .

Assign to Me

In a dynamic group, Assign to me lets one member take ownership of a request. Other members see who took it, and members can remove the assignment from themselves or others. It requires the Manage Workflow Assignments permission, and requests can be filtered by assignment in My Workflow Requests . This prevents parallel work on the same request, for example one that needs a works-council hearing.

Delegation

With Is Delegate Supported , an approver can hand a workflow to someone else, who approves or declines on their behalf. The delegate can refuse , and the original approver can recall .

Manual delegation: the approver names a delegate at a step.

Auto delegation: users name delegates in advance under Homepage > Delegate My Workflows .

Delegation is configured in the Corporate Data Model . With the is-delegate-supported field enabled in wfConfig, each workflow record gets a Yes/No value ( default No ). Both delegation types need Is Delegate Supported = Yes on the record. Delegation follows the four-eyes idea: the submitter cannot be the delegatee.

Auto Delegation

Users need the RBP permission Allow Auto-Delegation .

All workflows with Is Delegate Supported = Yes route to the nominee. This includes workflows received through job relationships, dynamic roles, dynamic groups, and positions.

Start and end times are optional. If left blank, auto-delegation runs indefinitely until switched off.

With Allow delegatees to accept or reject a workflow delegation request (Company System and Logo Settings), delegates can accept or reject. They see delegations under Delegation Requests for Me .

Auto-delegation by groups: administrators group request types in Manage Data > Auto Delegate Group . The system creates ALL OTHERS automatically once one group exists, as a catch-all. Users pick one delegate for all requests or delegates per group, up to three delegates . Administrators can configure auto-delegation for employees in Manage Data > Auto Delegate Config .

Future-Dated Alternate Workflow

An alternate workflow handles conflicts with future-dated records by adding approvers. Example: an address change normally goes to Talent Approval . If the employee already has a future-dated address (for example effective December 15, 2099), the alternate workflow Data Change runs instead. A business rule could achieve the same.

Reminders for Stalled Workflows

Remind the current approver after a number of days:

Create a Workflow Action Reminder job in Scheduled Job Manager .

Either enter Remind in Days in the job (the same for all workflows), or leave it blank and set remind-indays on each workflow record (after enabling the field in the Corporate Data Model).

If the job has a number of days, the values on the workflow records are ignored. The reminder reuses the approver's original notification with "Reminder:" in the subject, so no extra template is needed.

Auto Escalation

If an approver takes no action, the workflow stalls . Escalation moves it to a specified user after a set number of days. The new approver can decline the escalation, returning it to the previous approver, and the previous approver can revoke it. After declining or revoking, escalation continues with the next step after the defined days.

Enable the escalation field under wfConfig in the Corporate Data Model.

Create the escalation path in Manage Data.

Assign workflows to the escalation records.

Create and run the Workflow Auto Escalation job in Scheduled Job Manager .

Escalation does not happen when auto-approval is enabled.

Auto-Approval

Normally a step blocks all later approvers until it is processed. Auto-approval approves steps that stay unanswered for a set time:

Enable autoApproveInDays ( Days until Auto Approval ) under wfStepApprover in the Corporate Data Model.

Create a recurring Workflow Auto Approval job in Provisioning > Managing Job Scheduler > Manage Scheduled Jobs . SAP recommends running it daily , with an active period or an open-ended date.

Enter Days Until Auto Approval on the approval step of the workflow record.

Administrator Tools

Administrators handle stalled workflows in Manage Workflow Requests , where they can move requests forward or reassign them. Admin Alerts list stalled workflows (Section 2.4), and the Diagnostic Tool traces workflow details (Section 10.2).