Designing Route Maps and Workflow Steps for Performance Forms

Explanation

A route map is the workflow engine behind every SuccessFactors Performance Management form. It defines the ordered sequence of steps a performance document moves through - from initial self-assessment or goal setting, through manager evaluation, second manager review, HR review, and final signoff - and it determines who has write access at each step, what actions are available (send, decline, complete), and what happens to the form status as it transitions. Why this matters: a poorly designed route map is one of the most common causes of stalled performance cycles in production SuccessFactors tenants. Forms get stuck 'in progress' with an employee's former manager, a route step routes to an empty role (e.g., a second-level manager field that is blank in the org structure), or a step is configured with the wrong permission role so managers cannot see ratings they should be able to edit. These issues generate high support ticket volume during peak review seasons, so understanding route map mechanics is essential for both configuration teams and production support consultants. Design and configuration: route maps are built in Provisioning or Admin Center (depending on tenant setup and SAP's ongoing migration of legacy Provisioning functions to Admin Center) as XML-based step definitions referenced by the form template. Each step specifies a step type (e.g., self-assessment, manager assessment, matrix manager review, HR review, get signature, completed), a role resolution (employee's manager, employee's HR business partner via RBP-derived dynamic group, or a named role such as second manager), due-date logic relative to the form's overall timeline, and available actions. Steps can be conditional - for example, a matrix-manager step only appears if the employee has a matrix relationship populated in the job relationships portlet. Runtime flow: when a form launches (individually or via mass launch), the system evaluates the route map to determine the first active step and its owner. As each owner completes their action, the form transitions to the next step per the route map's send-to logic. Route maps can branch: a manager's 'decline' action might route back to the employee, while 'send' routes forward to the next step. HR administrators can use the 'route form' or 'change route map' capabilities (where enabled) to manually move a stuck form. Troubleshooting: common runtime problems include stuck forms due to a missing role occupant (e.g., no HR business partner assigned in the org structure), users reporting incorrect edit permissions on a step (usually a role/permission mismatch between the route map step and the underlying RBP or classic permission role), and forms that skip an expected step because of an unpopulated conditional field. Diagnosing these requires reviewing the form's route map history/audit trail, checking the employee's manager and matrix relationships, and confirming role resolution logic. Deployment differences: route map behavior and the underlying configuration tooling exist within SuccessFactors Performance Management as a cloud product; there is no ECC or S/4HANA on-premise equivalent for this specific workflow engine. Employee Central Payroll integration is not directly relevant to route maps, but the employee's manager/HR relationships driving route resolution are typically sourced from Employee Central foundation and job information, so EC data quality directly affects route map reliability.

Code example

<!-- Simplified illustrative route map step XML structure (conceptual, not a literal SAP export) --><routemap>  <step id="1" type="self-assessment" role="self" due="start+7" actions="send"/>  <step id="2" type="manager-assessment" role="EM" due="start+14" actions="send,decline"/>  <step id="3" type="matrix-manager-review" role="MM" condition="hasMatrixManager" due="start+18" actions="send"/>  <step id="4" type="hr-review" role="HR" due="start+21" actions="send,complete"/>  <step id="5" type="get-signature" role="self,EM" actions="sign"/>  <step id="6" type="completed"/></routemap>-- EM = employee's manager, MM = matrix manager, HR = role-resolved HR business partner group

Real project scenario

During annual review season, an HCM support team receives escalations that ~40 forms are stuck at the 'HR Review' step. Investigation shows the affected employees recently transferred between business units and their HR business partner assignment (driven by a dynamic role-based permission group tied to department code) had not been refreshed after the org change, leaving the HR review role unresolved. The fix involves correcting the RBP dynamic group criteria and foundation object data, then using the admin 'route form' function to manually advance the affected forms, followed by a root-cause review of the transfer process to add a data validation step before future review cycles.

Common mistakes

• Configuring a route map step with a role that has no guaranteed occupant (e.g., second manager) without a fallback or skip condition • Failing to align route map step permissions with the underlying RBP permission roles, causing edit access mismatches • Not testing route maps against edge cases such as employees with no manager, matrix reporting, or mid-cycle transfers • Assuming route map changes apply retroactively to already-launched forms in progress • Overlooking due-date logic that assumes a fixed calendar cycle, breaking for off-cycle or new-hire forms

Best practices

• Always include a fallback or conditional skip for optional roles like matrix manager or second manager • Validate route map role resolution against real org data before launching cycles, especially after reorganizations • Document route map versions and align them with active form templates to avoid mismatched behavior after mid-cycle template changes • Provide HR administrators with a clear escalation process and admin tools (route form, change step) for stuck forms • Test full route map paths, including decline/send branches, in a sandbox instance before go-live each performance cycle

Interview angle

Interviewers assess whether a candidate understands route maps as a distinct workflow engine separate from form template content, can explain how role resolution (manager, matrix manager, HR) drives step ownership, and can describe a realistic troubleshooting approach for stuck forms using audit trails and org data validation rather than guesswork.