2078699 - Routing - The Iterative Review Process (I Step) - Performance Management

The iterative review process allows the manager and employee to participate equally in the review.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

SAP SuccessFactors Performance Management

• A sample iterative step in the route map is between a manager and employee and it would be set as: I E EM.
• The review form is sent back-and-forth between the manager and the employee multiple times, with both parties allowed to view and edit the form. Only after both parties are satisfied with the review content, is the form considered complete and ready for signature.
• This back-and-forth iterative process fosters a flexible exchange of feedback between manager and employee throughout the review period by providing a live document that allows for planning, setting expectations and periodic check-ins and documentation.

Multiple Entry Users in Iterative Step

• It is common to set Step Entry Users and Step Exit users for iterative step similar to collaborative step to control who should first begin the process in this step and who is allowed to complete the step. In Iterative Step, if there are multiple users selected as Entry User, the first role selected will be the first entry user and will be the one who first receives the form once launched. So for example in a route map where first step is I EM EX E and all roles are defined as Entry User, then the Manager will be the first to receive the form. Similarly, when no entry user is selected, the first role of the iterative step will receive the form.
• Below are some other scenarios when routing a form to an Iterative Step:

1. Multiple Entry Users selected - When the user routes the form to the Iterative Step, all the entry users are listed for the user to choose.
2. Single Entry User selected - When the user routes the form to the Iterative Step, no entry user is listed for the user to choose. The form will just be routed to that single entry user.
3. No Entry User selected - When the user routes the form to the Iterative Step, all the roles in the I steps are listed for the user to choose.

Prevent Step If Role Does Not Exist

• Is it possible to have a step in the performance route map that is conditional based on whether the a role exists for the subject? 
  
  For example, I have an collaborative step between the manager and employee for self-assessment and would like to add a second step that would be an iterative step between the manager and matrix manager. If there is no matrix manager, we want this second step to be skipped entirely.
• Yes, you need to check the routing map option 'Only create iterative and collaborative steps when all roles exist for a user' (found under the Route Map name) in Manage Route Maps.

Supported Role types in an Iterative step:

Troubleshooting Users Missing in Iterative Steps

Document Routing - Iterative step in a route map is missing a user - There is a user missing from the Iterative step in a route map for a performance review.

• KBA 2432558 - Required Field Permissions not working in Iterative Step
• KBA 2508254 - Send to Previous Step Button is not visible in Iterative or Collaborative Step
• KBA 2087291 - Exit Users and Entry User in Route Map - Performance Management

Performance, PM, Form, Review, Iterative, step, route map, routing, entry user, exit user, roles, supported, missing user, multiple, single, live , KBA , csg_q , LOD-SF-PM-MAP , Routing, Route Maps & Workflows , How To