SF Perf MGMT V12acc Imp
SF Perf MGMT V12acc Imp
SAP SuccessFactors Performance Management is part of the SAP SuccessFactors Performance & Goals bundle of
applications. Using Performance Management, employees and managers work together to assess employees' work
performance, including their goal achievements and competencies.
• Form
In a performance review cycle, employees and managers use an online form, that is, Performance Management
form to give ratings and comments on employees' goals and competencies. The form consists of several
sections with configured features. For example,
• A goal section that shows employees' goals from their goal plan
• A competency section that shows employees' competencies by their job code
• A summary section that lists the rating of each goal and competency as well as overall form rating
• Form Template
Performance Management forms are created based on a form template. Before the forms are in use, the form
template needs to be configured. It's used to define form settings, for example,
• Form title and description
• Associated route map and rating scale
• Fields and sections
• Form permissions
• Route Map
When employees and managers do a performance review, each role gives ratings and comments in a single
step. When they finish their step, they route the form to the next step until the form is completed. A route map
establishes the steps and roles that are involved in a performance review.
Following is the process of how you can implement and configure Performance Management.
Enable Performance Management in Provisioning so that users can access Performance Management in their
instance.
Prerequisites
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Procedure
Now, users can access Performance Management through the Performance tab in the instance. Note that if
you enable 360 Multi-Rater or Succession Planning instead of Performance Management in Provisioning, the
tab is also visible to users but Performance Management features are not available.
4. Select Workflow.
Now, the route maps feature can be used to establish the steps and roles that are involved in a performance
review.
5. Optional: Select Stack Ranker for Performance Management to use the Stack Ranker feature.
When you set up Performance Management, it's important to grant role-based permissions (RBP) to the right
people. You can identify user groups, for each of which you can create individual roles, and then grant permissions
to those roles. Users who change roles or positions within your organization automatically lose or inherit
permissions.
With RBP, you can manage the permissions for Performance Management flexibly. For example, you can only allow
HR to create rating scales, or only allow managers to hide or unhide a form from employees without deleting it.
To see a full list of the RBP for Performance Management, refer to List of Role-Based Permissions by using filters
and key words.
Related Information
You can grant an access permission to certain users, so that other users are restricted from accessing the
Performance tab.
Prerequisites
You have the permission of Performance Management Feature Settings under Manage System Properties.
Context
Note
If users have forms in their form Inbox, though they don't have the access permission, they can access the
Performance tab. When all the forms are deleted, they can no longer access it.
1. In Admin Center, go to Performance Management Feature Settings and select Enable Performance Management
Access Permission.
Note
As an implementation partner or Product Support, you can choose to select the option in Company
Settings in Provisioning.
2. Go to Manage Permission Roles and grant the permission of Performance Management Access under
Performance to selected roles.
Before configuring a form template, you need to configure goal plans and competencies, and create a rating scale
and route map.
A Performance Management form can be linked to a goal plan. Before configuring a form template, you need to
configure a goal plan so that goals in the goal plan can be populated and synced on the form.
For more information on configuring goal plans, see the implementation guide of Goal Management.
Related Information
In performance reviews, managers and employees can review employees' competencies to evaluate how well
employees have fulfilled their organization-wide and job-specific requirements. Before configuring a form template,
you need to manage competencies that can be used in competency sections in Performance Management forms.
• Job Description Manager: You manage competencies in the Manage Competencies admin tool.
• Center of Capabilities: You manage competencies in the Manage Center of Capabilities admin tool.
• Talent Intelligence Hub: You manage competencies in the Manage Talent Intelligence Hub admin tool.
Note
Job Description Manager is a legacy framework for managing competencies, while Talent Intelligence Hub is the
latest one.
After you create competencies, you also need to map the competencies to job roles so that they can be populated
or added to forms.
• If Job Description Manager is enabled, use the Families and Roles admin tool.
• If Job Profile Builder is enabled, use the Manage Job Profile Content admin tool.
Related Information
SAP SuccessFactors provides a number of competency libraries that you can tailor to suit your needs. You can
create your own competency libraries from scratch. You can also edit an existing competency to add performance
details.
Procedure
1. Go to Admin Center, and in the tools search field, search for Manage Competencies.
Option Description
Name or description of the competency The category is most-often used to help organize information within this
and the category tool.
Performance Details Text that appears in the writing assistant and coaching advisor.
5. If you want to identify a competency as core to your organization, for example if your organization has core
values or mission competencies, select Yes in the Core field to tag or identify this competency as core to the
organization.
In the Manage Templates tool, you can set the form to dynamically pull the core competencies for all your
employees when you launch the form.
Note
If the Core flag is set in Manage Templates, users must also mark competencies as core in the Manage
Competencies tool, otherwise this section will be blank for your users.
6. Under Performance Details click the text to update the tone and voice that you want to change.
7. When you have finished updating the text, click Save.
Results
Prerequisites
Note
Procedure
1. Go to Admin Center, and in the tools search field, search for Manage Competencies.
The Competency Libraries List opens. You can create a new competency library from this page.
2. On the Competency Library List screen, select the competency to edit.
3. Within the competency, edit any of the following: Name, Category, Description, Performance Details, Core
Settings Job Role Assignments, Status, or Assigned Behaviors.
Note
Results
You have successfully edited your competency on the Competency Libraries List.
Performance details are short but specific statements that describe actions, attitudes, or skills that demonstrate
proficiency in the competency. You can move, delete, edit or create a performance detail on the Performance
Details tab.
Prerequisites
Context
You can organize performance details into multiple performance levels, such as Meets Expectations, Exceeds
Expectations, or Needs Improvement.
For example, to show that an employee meets the "Customer Focus" competency, you, as an admin, can create the
following performance details:
Procedure
1. Go to Admin Center, and in the tools search field, search for Manage Competencies.
The Competency Libraries List opens. You can create a new competency library from this page.
2. On the Competency Library List screen, select the competency to modify.
3. To move performance details to another performance level, select checkbox next to the Performance Detail and
then click Move Selected To.... Select the performance level from the dropdown menu.
4. To delete a performance detail, select checkbox next to the a performance detail and then click Delete
Selected. Click Yes to confirm deletion.
5. To edit a performance detail, click the teaser text. Edit the performance detail as necessary and then click OK
to save. Click Save within the competency to save all changes.
6. To create a new performance detail, click the competency to edit. On the Performance Detail tab, click Take
Action in the performance level where the new performance detail is desired, and then select Add Teaser.
Enter the performance detail information, select the voice, and edit the tone. Click OK to save the performance
detail. Click Save within the competency to save all changes.
Results
You can edit existing competencies in a competency library, or you can create new competencies from scratch.
Procedure
• Competency Name
• Description
• Locale: This dropdown menu specifies the language in which the competency is written. For example when
more than one language is used, each language has its own competency within the appropriate locale.
Note
It cannot be edited in this page. To edit this, you can export the competency, update the locale and
re-import.
Note
Make sure that the language of a competency and the related category is consistent with the
language of a Performance Management form template. Otherwise, the competency and category
aren't available when you add competencies in the template.
• Category: You must place each competency within a category. Use this category tag to both organize your
competency library as well as filter competency sections of forms.
• GUID: Global Unified Identifier is the unique alpha numeric value you have assigned to tag or identify your
competency. If you have multiple locales, this unique number is what ties them together as being the same
competency in different languages.
For example, if the customer is located in Canada each competency must exist in both English (en-us) and
French (fr_ca). As an admin you should create competencies for Customer Focus in each language:
• Locale=en-us Customer Focus GUID: 7 ID: 7-Eng
• Locale=fr-ca L'orientation cClient GUID: 7 ID: 7-Fr
Note
The ID is slightly different, but the GUID is the same for each version. As a result, the French language
version is pulled into the performance forms of French speaking employees, and the English language
version is pulled into the performance forms of English-speaking employees.
• Status: Each competency can have a status of Read Only, Editable or Hidden, which you choose when you
create the competency. A Read Only status defines that you can read a competency but you cannot edit a
competency. An Editable status defines that you can edit a competency. A Hidden status defines that end
users can add the competency to a form or not.
• Core: Selecting "Yes" designates the competency as "Core" competency. If desired, you can configure the
performance form template so that core competencies are dynamically pulled into the performance form
for each employee.
• Description
5. Click Save.
Results
You can add categories to the library either when you create new competency or when you edit an existing
competency.
Context
You can use the category tag to both organize your competency library as well as filter competency sections of
forms.
Procedure
You can manage competencies by going into the competency itself, or change competencies using the Actions
menu within the competency library.
Context
Procedure
A rating scale is a tool used in Performance Management forms with which the reviewer assigns a score to the
employee as a measure of performance.
When creating a rating scale, you can choose from the prebuilt rating scale types that are based on best practices,
or create a new type as you need. By default the smallest number is the lowest rating and the largest the highest.
7-Point Scale (1-7) This type of scale offers the highest level of differentiation,
and may be helpful when extreme accuracy is preferred over
convenience.
5-Point Scale (1-5) Default rating scale type. This type is recommended because it
contains a midpoint and allows for a balanced level of differen-
tiation.
3-Point Scale (1-3) This type of scale is applicable if you would like the result to be
divided into two polar points or the neutral one.
A rating scale is required before creating a form template. You can create a rating scale based on a predefined
rating scale or build you own.
Prerequisites
Note
If you use EZ Rater, please note that the more levels in a rating scale, the smaller the gap scale values display in
the gap analysis chart on the form. You may find the gap scale values too small to read. For more information,
refer to KBA 3266377 .
Procedure
• If you're using the Rating Scale Designer, choose Create New Rating Scale.
• If you're using the Enterprise Rating Scale tool, enter the name for the rating scale and choose Create.
2. Enter a name and description for your rating scale.
Note
The maximum length for the name field is 32 characters in English. If you're configuring the field in other
languages, pay attention that one character may take up more than one English character.
You can generate scores that increase incrementally by entering the minimum number in Low, maximal
number in High, and the increment in Increment.
4. Choose Save.
Next Steps
To use this rating scale, when you configure a form template, associate the rating scale with the form template.
A route map establishes the steps and roles that are involved in a performance review. Each role on the route map
gives ratings and comments in a step and then routes the form forward until it's completed.
Example
A Performance Management form is sent to the employee first, and then to the direct manager and to the
HR manager. Before the form is sent to the HR manager, the form can be sent back and forth between the
employee and direct manager.
• Modify Stage: This stage marks the start of a performance review and is the main stage during the whole
process. For example, in this stage, employees give self-assessment on a form and managers review the form
to give manager assessment.
• Signature Stage: This stage is where employees and managers sign and approve the form to acknowledge that
the performance review is done.
• Completion Stage: This stage is where the form is archived in the employees' completed form folder.
Create a route map to establish the steps and roles in a performance review.
Prerequisites
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
Procedure
Choose from Library You add a route map from the SuccessStore library. You can
edit the route map after adding it.
Option Description
I want to personalize the evaluation stage in a 360 review This option is to create a route map for 360 Reviews.
route map
Only create iterative and collaborative steps when all If a role selected for an iterative or collaboration step doesn't
roles exist for a user exist in your instance, the step is not created.
Use relative dates for form routing Instead of selecting a specific date for the start date, exit
date, and due date of a step, you can use relative dates.
For example, you set the start date as 1 day after the form
creation date.
5. Choose the Add Step icon to create steps in the modify and signature stages.
Note
A step in the completion stage is automatically created. Because users can't edit forms in the completion
stage, you can't create additional steps for this stage.
6. In the Create A New Modification Step pop-up window, enter a step name and choose OK.
The following table lists all fields. Some fields don't apply to all steps and thus may not appear on the step
configurations page.
Step Name The field is prepopulated with the name that you entered
when creating the step.
For more information on how to use step types, see the Step
Types topic in Related Information.
Roles Select a role for a single role step and more than one role for
an iterative and collaboration step.
Start Date Select a date on which users can start working in this step.
Exit Date Select the earliest date on which users can route the form to
the next step.
Use this date only to prevent users from routing the form to
the next step at any time. If you also use the Automatic send
on due date option in the Due Date field, the exit date must
be earlier than the due date.
Remember
As a customer, you don't have access to Provisioning. To
complete tasks in Provisioning, contact your implemen-
tation partner or Account Executive. For any non-imple-
mentation tasks, contact Product Support.
Note
The form is sent to the next step on the day after the
due date.
Additionally, to route only the forms that pass the form vali-
dation check, select Only send forms that pass validation. To
route all forms regardless of whether they pass validation,
select Always send regardless of validation.
Carbon Copy These User Roles Upon Document Completion Select roles to whose completed form folder the copy of the
(For the completion step only) form is sent when the form is completed.
Advanced Options
Step Introduction & Mouseover text Enter a description of users' action in this step.
Step Name After Completion Enter a name for the step after it is completed. If you leave
this field blank, the step name remains the same one as
specified in Step Name.
Iterative Button Text (For iterative steps only) Enter a text to customize the button text for users to send
the form in an iterative step. You can use the [username]
token, for example, Send to cgrant.
Note
To customize the button text, make sure that Hide
Hierarchy isn't selected in Provisioning.
Reject Button Mouseover Text (For signature steps only) Enter a description to inform users of what their action
means.
Exit Button Text Enter a text for the button to send the form to the next step.
If you leave this field blank, the button is Send to Next Step.
Step Exit Text Enter a description to inform users of what they need to do
and what their action means.
Previous Step Exit Button Text Enter a text for the button to send the form to the previ-
ous step. If you leave this field blank, the button is Send to
Previous Step.
Previous Step Exit Text Enter a description to inform users of what they need to do
and what their action means.
Step Exit Reminder See the Step Exit Reminder topic in Related Information.
Step Id It doesn't indicate the order of the step in a route map, but
an ID that the system generates to identify the step inter-
nally.
Start of Review (For modification steps only) Select the checkbox to mark the step as the start of a per-
formance review.
Note
In a route map, only one step can be marked as Start of
Review.
Out of Turn Access (For modification steps only) Select the checkbox to enable the Out of Turn Access fea-
ture. It grants the permission of viewing and editing the form
to the step owner before the form is routed to their step.
1:1 Meeting (For modification steps only) Select the checkbox to set up a dedicated conversation be-
tween an employee and their direct manager.
Note
• This option is available only in the last step in the
modify stage.
• It's available only in single-role steps. Manager (EM)
is the recommended role for 1:1 Meeting.
8. Choose Save.
Next Steps
To use this route map, when you configure a form template, associate the route map with the form template.
You can create a step in a performance review as a single-role step, an iterative step, or a collaboration step.
• Single Role: A single role works on a form in one step. For example, the employee works on a form in a step.
• Iterative: It is the most commonly used step type when several roles participate in one step. The form is sent to
one user at a time, and the user sends the form to the other users specified in the step.
Example
"I E EM EH" specifies an iterative step between the employee, their direct manager, and HR manager. All
three roles can edit the form and send the form back and forth to each other before routing the form to the
next step.
To use this step type, we recommend that you specify the entry user and exit user. So, the form is sent to the
entry user first and to other users, before the exit user routes the form to the next step.
• Collaboration: It is another step type when several roles participate in one step. The form is sent to all users at
the same time, but only one user can work on the form at a time. When users open a form, they may find it
locked. It is because another user is currently editing the form. The form remains locked until the user chooses
Cancel or Save and Close on the form. If the user doesn't leave the form, the form remains locked for 60
minutes.
Example
"C E EM" specifies a collaboration step between the employee and their direct manager. Both of them have
access to the form, but only one of them can edit the form at a time.
To use this step type, we recommend that you specify an exit user, who routes the form to the next step.
Note
If you don't specify an exit user, when forms are sent automatically on the due date or sent manually in
Route Form, a form validation check won't be triggered.
Learn about the standard and custom roles that are used in Performance Management.
E Employee Employee
Note
O role can't add, edit, or remove
goals on the form.
By configuring form templates, you define form settings, for example, form title and description, associated route
map and rating scale, fields and sections, and form permissions. You can use Manage Templates in Admin Center to
configure form templates.
Create a form template so that you can configure the form template for performance reviews.
Procedure
Next Steps
Configure the general settings and edit fields and sections of the form template.
Configure the general settings of a form template to define the title, route map, rating scale, and other
configuration of Performance Management forms.
Prerequisites
Grant the permission of Form Templates and Comprehensive template configuration for PMv12 under Manage Form
Templates in Manage Permission Roles.
Procedure
Name Enter a name for the template. By default, it's the form title.
Hide numeric rating values (only show text labels) Select the checkbox to show on the form only the rating
labels defined in Rating Scales.
When the rating scale has no more than five rating levels, if
you select this option, the rating field on the form becomes a
dropdown list showing rating labels only.
When the rating scale has more than five rating levels, the
default rating field is a dropdown list showing both rating
values and labels. If you select this option, the dropdown list
shows rating labels only.
Unable to Rate Enter a name, for example, Too New to Rate, to define a
special rating on the rating scale. Performance reviewers can
select this rating when they think it's too early to give a
regular rating for a goal or competency of an employee.
Allow managers to stack rank employees on competency Select the checkbox to enable the Stack Ranker feature.
sections
Select Globally to enable the feature for all competency sec-
tions on the form, or Section by Section to enable the feature
in the section level.
Advanced Options
Enable Previous Step Button Select the checkbox to enable the Send to Previous Step
button on the form.
You can enable the button for specified steps and roles by
configuring button permissions.
Enable Delete Button Select the checkbox to enable the Delete Form button on the
form.
You can enable the button for specified steps and roles by
configuring button permissions.
Enable Scale Adjusted Calculation See the Configuring Scale Adjusted Calculation topic in Re-
lated Information.
4. Choose Save.
Related Information
Configure scale adjusted calculation to adjust the calculated form rating to a fixed rating value, so that the
calculated form rating with a decimal can be shown as an integer with a rating description.
Procedure
Field Description
Score Min Value The lowest possible rating of the calculated form rating that
will be adjusted to a fixed value. Example: 0.1
Score Max Value The highest possible rating of the calculated form rating that
will be adjusted to a fixed value. Example: 1.49
Map to Score A fixed value to which the calculated form rating in the range
from Score Min Value to Score Max Value will be adjusted.
Example: 1
Map to Description The rating description of the fixed value. Example: Unsatis-
factory
6. Optional: Select Enable Display Calculated Rating to show the original calculated form rating under the
adjusted calculated form rating in the form.
7. Choose Done in the dialog box and choose Save on the page.
Results
The scale adjusted rating is configured. It applies to only the forms that are launched after your configuration.
The Form Template Settings tool provides you with options to enable or disable some form template settings.
To access Form Template Settings, you can either navigate to Admin Center Form Template Settings , or
choose Advanced Settings in the General Settings section of the form template in Manage Templates.
Learn about the form template settings and descriptions in the following table.
Note
Some but not all changes made to the form template apply to the in-progress forms that are based on this
template.
Setting Description
Template Name The name of the form template. You can change it at any time although not recommended.
Form title includes this name by default.
Note
If the form setting in Company System and Logo Settings is All documents will display their
form template name at the time the document was created. This option does not support
translations of the document name,
• When the template name is changed after the form is launched, users don't see the
changed form title on the form.
• The form title isn't adapted to logged-in users' language settings, but is displayed in
the default language.
If the form setting is All documents will display their current form template name as
configured in the Form Template Administration settings. This option supports translations
of the document name,
• When the template name is changed after the form is launched, users can see the
changed form title on the form.
• Once the template name is configured in logged-in users' language, the form title is
displayed in logged-in users' language.
Template Type For Performance Management form templates, the type is PM Review. It's read-only.
Last Modified The date and time when the form template was last modified. It's read-only.
Routing Map The route map associated with the form template
Default Dates for Form Determines the default start, end, and due dates either fixed or relative to:
Creation
• Form Creation Date
• Default Start Date
• Default Due Date
Note
If a form template is saved as another template, this setting is not cloned to the new
template.
Disable Ask for Feedback Refer to Ask for Feedback [page 171].
functionality
Display circle icon as rating The rating field uses the star icon by default. If you select this option, the rating field uses the
circle icon.
There's a default tooltip over the star or circle icon on forms to guide users to give ratings by
keyboard. You can customize the tooltip in the Manage Languages admin tool using this key:
PERFORMANCE_PM2_RATING_STAR_WIDGET_TITLE.
Display check mark instead of If enabled, check mark is displayed instead of rating in Team Overview.
rating in Team Overview
All scores recorded for the form are made visible to any user who has access to Team
Overview. To hide any scores from users in Team Overview, you must select the check mark
option.
Note
If a form template is saved as another template, this setting is not cloned to the new
template.
Default Due Notification Date The number of days before the form due date. On the due notification date, an email
(in days) notification is sent to the user who has the form in their form inbox, reminding them that the
form is approaching the due date. The email is sent during off business hours, after midnight
EST.
Default Late Notification Date The number of days after the form due date. On the last notification date, an email notification
(in days) is sent to the user who has the form in their form inbox, reminding them that the form is past
the due date. The email is sent during off business hours, after midnight EST.
Template Status • Enable: The form template can be used to launch forms.
• Disable: The form template can't be used to launch forms.
Template Flag • Public: Forms are transferable whenever a manager transfer process is started. For
example, all public forms under the old manager are transferred to the new manager.
• Private: Forms are not transferred during the manager transfer process. Private forms
remain with the old manager.
This setting has no impact on the route map. If there are EM steps in the route map that
haven't been completed, the form is routed to the new manager in the EM steps.
Do Not Transfer Documents Refer to Configuring Document Transfer in Form Templates [page 183].
Note
If a form template is saved as another template, this setting is not cloned to the new
template.
Automatic Manager Transfer Refer to Configuring Document Transfer in Form Templates [page 183].
Note
If a form template is saved as another template, this setting is not cloned to the new
template.
When the system is When an employee is set to inactive, the following settings override the global setting that
configured to remove may remove inactive employee's documents. The settings are useful when an employee is
documents for inactive terminated but still has an active form that entitles this employee to incentive pay.
employees, apply these
overrides so the system does
• Do Not Remove Inactive Employee's In-Progress Documents
not remove documents for • Do Not Remove Inactive Employee's Completed Documents
this form template
Default Targets • Self and Direct Reports: Users can create forms for which they themselves or their direct
reports are the subject.
• Self Only: Users can create forms for which they are the subject.
• Direct Reports Only: Users can create forms for which their direct reports are the subject.
• HR Reports Only: Users can create forms for which their HR reports are the subject.
• Self and Matrix Reports: Users can create forms for which they themselves or their matrix
reports are the subject.
• Matrix Reports Only: Users can create forms for which their matrix reports are the
subject.
See also the setting Allow form creator to select anyone as a subject.
Hide Route Map on the Form Hides the route map section on the form.
Keep last touched version Users can't see form updates after their last modification step.
upon Document completion
Enable Auto Restore Deleted If employees have been deactivated and are reactivated, the deleted forms of the employees
will be restored when they are imported into the system.
Form When Importing User
Note
• When you enable the setting, it may take a long time to import employees because
there may be a large number of deleted forms to be restored. If you think it's not
necessary to restore the forms for those employees, we do not recommend you
enable the setting.
• Only those forms that were in progress when being deleted are restored. Completed
forms are not restored.
• If document transfer is disabled and the manager has changed, forms are restored to
the old manager who had the forms.
• If document transfer is enabled and the manager has changed, when forms are
restored, document transfer settings are applied.
• If forms had been sent to others for feedback when being deleted, the forms are
restored to the person who had them.
Use Plain Text Only for Only plain texts are used when users enter comments.
Comments (Warning: You will
lose RTE formatting in existing
forms by enabling this.)
Disable Ask for Edit Routing Refer to Get Feedback [page 208].
Hide Add/Remove Signer Refer to Add Signer and Remove Signer [page 168].
buttons
Disable All Toolbar Buttons Hides Actions, History, (Print), (Save as PDF), and (Save) in the top right of the form.
(overrides all button
selections below)
Disable Print Button Hides (Print) in the top right of the form.
Disable Send and Open Next Hides the Send and Open Next Form button on the confirmation page of sending the form to
Form Button another step.
Disable Page Setup button Hides page setup options when users want to save as PDF.
Disable Delete button Users can't delete forms. See also Button Permissions [page 70].
If this setting is not selected, you can disable deletion in forms by selecting Hide Delete Icon
inside Form in the Performance Management Feature Settings admin tool. The delete icon is
still available in form Inbox.
Disable Note button Hides Notes information from the Supporting Information pod.
Disable Form button Hides the Performance form history option from the History dropdown in the top right of the
form.
Disable 360 button Hides the 360 form history option from the History dropdown in the top right of the form.
Disable Send button Users can't send forms to the next step. See also Button Permissions [page 70]
Disable Send button for Hides the Send button in completed forms.
completed documents
Disable Late Notification Disables the email notification sent to the user when the form is past the due date. See also
the setting Default Late Notification Date (in days).
Disable Due Notification Disables the email notification sent to the user when the form is approaching the due date.
See also the setting Default Due Notification Date (in days).
Disable Step Exit Notification Disables the email notification sent to the user when the form is sent to another step.
Disable PDF printing Hides (Save as PDF) in the top right of the form.
Allow form creator to select Allows users to create forms for anyone, besides themselves, including their direct reports, HR
anyone as the subject reports, and matrix reports.
Allow Matrix Manager to Allows matrix managers to delete forms if Delete Form isn't disabled.
Delete document if Delete
button is available
Show Signoff routing step Shows the signature step name in the signature stage.
names in Signoff Stage
Enable form title editability in When you select the option, the following effects are applied:
the Form
• The form title is the template name in the language used at the time of form launch.
• The form title is no longer affected by changes to the template name.
• The form title is no longer affected by the logged-in user's language settings. It's in one
language only.
If this setting is disabled later, the title of all launched forms is automatically updated to match
the current template name.
Enable form title editability in Apart from the same effects of the previous setting, this one, when enabled, allows you to edit
Form info page the form title on the Form Information page.
Enable Completed Form Item The comments for goals or competencies on completed forms can be copied.
Comment Copy
Choose when to display the Refer to Add Signer and Remove Signer [page 168].
Add/Remove Signer buttons
Only create for users who Forms can't be launched for users who already have the form in the specified date range. If
don't have an existing or in- you select this setting, you can also select Do not allow admin users to edit the date range in
progress form with an End the Launch Form tool.
Date: between [date] and
[date] Note
If a form template is saved as another template, this setting is not cloned to the new
template.
Hide the Export and Export Hides the Export and Export (Compact) buttons on completed forms.
(Compact) buttons for
documents in the Completed
Folder
Show digital signatures in Shows digital signatures in the form print preview.
Document Print Preview
Disable Due Date Validation Disables the validation that checks the form to make sure the end date is before or the same
as the due date.
Disallow users from changing Users can't change the start date on the form.
the Start Date
Disallow users from changing Users can't change the end date on the form.
the End Date
Disallow users from changing Users can't change the due date on the form.
the Due Date
Enable form routing to Users can send forms to the previous step. See also Button Permissions [page 70].
previous step
Enable SMART Goal Wizard The SMART Goal Wizard is enabled in forms.
(requires SMART Goal Wizard
enabled on goal plan) Note
If you're using the latest Goal Management, the SMART Goal Wizard is not available.
Show Manager Rating first for Manager's rating is shown first in the EZ Rater mode.
EZ Rater mode
Prevent forms from being Users or admins can't create forms that have overlapping date ranges. This setting checks the
created with overlapping dates of all launched forms that have this setting enabled.
date ranges (this applies
to all templates with this
configuration enabled)
Enforce permissioning for By default, Detailed Document Search disregards permissions and includes all form fields.
Detailed Document Search & Enable this setting to ensure the permissions are respected.
Archive & Print Reporting
This setting also enables the archive and print report to respect permissions for the logged-in
user.
Allow exit step comments to Exit step comments are visible to all the participants in a collaboration step on the Form
be visible to all participants in Information page. This setting applies to only the forms that have not progressed beyond the
a Collaborative (C) Step (only collaboration step.
applicable for forms that have
If you select the option, make sure that Document Routing Notification in E-Mail Notification
not progressed beyond the C
Templates Settings is enabled and the [[DOC_COMMENT]] token is included in the email
Step)
notification template.
Enable attachments Allows users to upload attachments in the Supporting Information pod.
Disable Table of Contents Hides the form section navigation under the form subject information on the form.
Note
If a form template is saved as another template, this setting is not cloned to the new
template.
Enable Achievements tab in Refer to Achievements and Feedback from Continuous Performance Management [page 284].
Performance Goal Section
Display Achievement
Feedback for Performance
Goal Achievements
Display Achievement
Feedback for Development
Goal Achievements
Enable New Confirmation When users send a form to the next or previous step, a message popup appears and allows
Experience for Sending Forms
them to confirm the action. It applies to the following actions:
The message popup includes the following labels that you can replace using Manage
Languages in Admin Center:
For more information on replacing labels, refer to Customizing UI Text with the Manage
Languages Tool
Configure the sections and fields of a form template to define the settings for Performance Management forms.
Prerequisites
Grant the permission of Form Templates and Comprehensive template configuration for PMv12 under Manage Form
Templates.
Context
Performance Management forms provide four kinds of summary sections: summary section, goal competency
summary section, performance potential summary section, and customized weighted rating section. The overall
form rating is from any configured one of these four sections, and if multiple are configured, the following order
applies:
Note
If the Section Name field is empty in a section, the system considers the corresponding section as an item
or custom element of the previous section. In this case, the form can't get printed properly when users
choose Save as PDF or Print on the form.
Section Description
Introduction The section provides information about a performance review to users. It can include the
purpose of the review, whom to call for assistance, or any other information that you feel is
relevant to the review.
Review Dates The section shows the dates that you set when you launched the form.
Employee Information The section shows basic employee data of the individual to be reviewed, such as first name,
last name, and username. You can include or exclude various fields to show more or less
information about the employee. This information is read-only on the form.
Goal Competency Sum- See Goal Competency Summary Section for more information.
mary
Performance Potential See Performance Potential Summary Section for more information.
Summary
Customized Weighted See Customized Weighted Rating Section for more information.
Rating
Signature The section shows the name of the people who should sign the form. When they sign the form,
it shows the signature of the signer and the date when signed. You can select Include comment
to set a mandatory comment when the form is signed.
Mid Year The section is an optional area of the form that can be used for open and overall comments
about the subject of the form.
Custom The section is an optional area of the form that can be used for open and overall comments
about the subject of the form.
Additional Comments The section is an optional area of the form that can be used for open and overall comments
about the subject of the form.
4. Choose Save.
Goal sections are used to evaluate employees' performance goals or development goals during a performance
review.
Performance goals are job-oriented and result-based statements of an employee's ongoing and project-specific
responsibilities. Development goals focus on learning, which is essential to improving individual or organizational
performance.
One goal section is linked to one goal plan or one development plan. A form can have several goal sections, for
example, one section for core company goals and one section for departmental goals. All goal sections work in the
same way.
Note
• We recommend that in each performance review cycle, you create a new goal plan and link the new one to
forms. If you use one goal plan continuously for many review cycles, please note that when users update
the goal plan, goal details in completed forms are updated accordingly.
• F role (Form Reviewer) isn't supported in the latest Goal Management. Refer to Roles in Goal Plans for more
information.
Learn about the fields and options that you can configure and select for the goal section in the following table.
Section Name The name of the section that is shown on the form
Section Description The description of the section that is shown on the form
Section Type The goal section supports the following goal types. One section
is for one type.
• Goal Section: Select a goal plan that you want to link to the
form.
Note
If a goal plan template is newly imported, make sure
that the goal plan is effective before you link it to the
form. See Step 6 in Importing a Goal Plan Template.
Note
If you link multiple goal sections with the same goal plan
without using <obj-category> to filter goals, the goals
are displayed in only one section.
Show Add Existing Objective Button / Show Add Existing De- The button is used to add existing goals in the linked goal plan
velopment Objective Button
to the form.
Note
• To see and use this button, users need to have the
create permission for goals in the goal plan tem-
plate.
• The button is not needed if goals are synced to the
form automatically.
Unable to Rate The label of a special rating on the rating scale, for example,
Too New to Rate. Performance reviewers can select this rating
when they think it's too early to give a regular rating for a goal
of an employee.
Include the ability to rate Users can rate on each goal. See the Rating Options topic.
Exclude Private Goals Private goals are excluded from the form when the form is
created. Also, you can't add a new private goal to the form.
Note
This option only works when you launch a form. If you
change the public goals on the form to private goals after
launching the form, the goals still appear on the form.
Include the ability to enter a weight Users can edit the weight of each goal.
Include a comment for each item Users can comment on each goal.
Include an Overall Comment Users can give an overall comment on the goal section.
Display section in summary The rating and weight of goals are shown in the summary sec-
tion.
Display calculated section rating The calculated goal rating is shown in the summary section.
Auto populate goal weights from weights in the goal plan Weights from the goal plan synchronize to the form.
Allow users to add/remove Goals within the section Users can add goals to the form and remove goals from the
form.
You can enable the add and remove actions for specified roles
and steps by configuring action permissions.
Note
To allow users to add goals to forms, if you're using legacy
Goal Management, make sure that users have the "create"
permission in the goal plan template; if you're using the
latest Goal Management, make sure that users have both
the "create" permission in the goal plan template and the
role-based permission for the goal plan template.
Synchronize goals from a goal plan and a review form Changes made to goal plans automatically synchronize to the
goal section on the form. Also, changes to goals on the form
automatically synchronize to the goal plan.
Note
If you use the latest Goal Management and you enabled
the auto-sync feature in Performance Management, please
be aware of the following:
Use Metric Lookup Table Rating If the linked goal plan has a metric lookup table, this option is
selected by default.
Include in overall Goal rating calculation Ratings in this section are included in the calculation of the
overall goal rating. The option is useful if you have multiple goal
sections and want to leave one section out of the calculation.
Display in Goal section Goals in this section are listed in the goal competency sum-
mary section.
Lock item weights Goal weights are locked so that users can't change the weights.
Include in overall performance summary section rating Ratings in this section are included in the calculation of the
performance rating in the performance potential summary
section.
Minimum Goals Required The minimum number of goals required in this section
Maximum Goals Allowed The maximum number of goals allowed in this section
Section Weight for Obj/Comp Summary The weight of the section for calculating the overall goal rating
in the goal competency summary section
Total Weight Target total weight for the goals in this section
Rating Scale The rating scale used in this section. If you've selected a rating
scale in General Settings, you don't need to select it again here.
Default Rating The label that is shown in the rating field if users haven't rated
on goals
Choose an alternate label for the rating field The label of the official rating field
Goal Plan State If you've configured this feature for the linked goal plan, the
goal state can be changed to a specified state when the form
moves to a specified step or when the form is completed or
deleted.
Note
For development goal sections, you can configure only the following settings in Manage Templates:
Related Information
When you select Include the ability to rate in a form template in Manage Templates, you need to further select
settings to define a rating option. Or, in an XML form template, if the no-rate attribute is false, you need to
specify the rating-opt attribute to define a rating option. Performance Management provides four rating options.
Rating Option 0
To use Rating Option 0, select Everyone shares one rating box for each item. In the XML form template, set the
rating-opt attribute to 0.
With this option, all users share one rating field for each item. The only rating field is called item rating, also known
as official rating. The first user sets a rating, but the second user can change it. The last user in the route map has
the final say over the official rating.
Employee's View
Manager's View
Rating Option 1
To use Rating Option 1, select Everyone shares one rating box for each item and Except the employee who has a
self-assessment rating box. In the XML form template, set the rating-opt attribute to 1.
With this option, all users share one rating field for each item which is the official rating. The last user in the route
map has the final say over the official rating. In addition, employees can give self-ratings in a rating field called
unofficial user rating.
Recommendation
To prevent employees from providing the official rating, the recommended approach is to grant them read or
none permission for the item rating field.
Note
To show the unofficial user rating field, select Include a comment for each item in Manage Templates. In the XML
template, set the cmt-opt attribute to 1 or 3.
The rating fields are shown on the form as follows. In the PDF and print version, the official rating and one unofficial
user rating, if any, are available.
Manager's View
Rating Option 2
To use Rating Option 2, select Everyone has their own rating box for each item and The final score can be granted to
any role by permission. In the XML form template, set the rating-opt attribute to 2.
With this option, all users can edit both the item rating field and the unofficial user rating field. Users who can
provide the official rating should have write permission for the item rating field. The last user among them has
the final say over the official rating. Users who aren't supposed to provide the official rating should have none
permission for the item rating field and have read or write permission for the unofficial user rating field.
Recommendation
Users have two rating fields by default. To avoid confusion, we recommend that you configure field permissions
to hide the unofficial user rating field from users who can provide the official rating.
Note
To show the unofficial user rating field, select Include a comment for each item in Manage Templates. In the XML
template, set the cmt-opt attribute to 1 or 3.
The rating fields are shown on the form as follows. In the PDF and print version, the official rating and unofficial user
ratings, if any, are available.
Manager's View
To use Rating Option 3, select Everyone has their own rating box for each item and The final score is the EM's rating.
In the XML form template, set the rating-opt attribute to 3.
With this option, only employees and managers can provide ratings. The rating field for employees is called subject
rating and the field for managers is called item rating or official rating.
The rating field for employees or managers is shown on the form as follows. In the PDF and print version, the official
rating and subject rating are available.
Employee's View
Manager's View
Note
You can find the XML language of the fields in the following table.
For Rating Option 0, 1, and 2, the Ratings from Others tab shows unofficial ratings and comments only.
Related Information
Competency sections are used to evaluate employees' competencies during a performance review. A Performance
Management form can include three competency sections, respectively for job-specific competencies, core
competencies, and custom competencies.
Recommendation
To optimize system performance, especially when you use Internet Explorer, we recommend that no more than
60 competencies are rated on a form.
Learn about the fields and options that you can configure and select for the competency section in the following
table.
Section Name The name of the section that is shown on the form
Section Description The description of the section that is shown on the form
Unable to Rate The label of a special rating on the rating scale, for example,
Too New to Rate. Performance reviewers can select this rating
when they think it's too early to give a regular rating for a
competency of an employee.
Allow users to add competencies Users can select competencies from your competency library
and add them to the form, and also remove competencies from
the section. They can add the same competency to the form
only once.
Caution
If you configure the template to rate on behaviors, users
can add the same competency with different behaviors to
different sections. When the rating or comment of a com-
petency in one section is updated, that in other sections is
updated as well. To avoid confusion, users should add one
competency to the form only once.
You can enable the add and remove actions for specified roles
and steps by configuring action permissions.
You can also select Filter By Job Code to show only the
role-specific behaviors on the form. When a competency is
assigned with the behaviors of multiple job roles, only the be-
haviors of the employee's job role are shown.
Recommendation
We recommend that you use XML template to configure
ratings and comments on behaviors. For more informa-
tion, see Rating Behaviors in Related Information.
Include the ability to rate Users can rate on each competency. See the Rating Options
topic in Related Information.
Include a comment for each item Users can comment on each competency.
Include an overall comment Users can give an overall comment on the competency section.
Include in overall competency rating calculation Ratings in this section are included in the calculation of the
overall competency rating. The option is useful if you have
multiple competency sections and want to leave one section
out of the calculation.
Display in competency section Competencies in this section are listed in the goal competency
summary section.
Show expected competency rating The expected rating of competencies for the job role is shown
along with the actual rating. The option is useful to view the
gap between an employee's expected and actual performance.
Note
• If users add a competency to the form by role and
the competency has an expected rating, the expected
rating is displayed on the form along with the added
competency. If the competency is assigned to multi-
ple roles with different expected ratings, only the ex-
pected rating of the selected role is displayed.
• If you've upgraded to Talent Intelligence Hub, this con-
figuration is not yet supported when users add com-
petencies to the form through the picker. Users won't
see expected ratings next to the competencies added
to the form.
Include in overall performance summary section rating Ratings in this section are included in the calculation of the
performance rating in the performance potential summary
section.
Total Weight Target total weight for the competencies in this section
Include the ability to enter in a weight Users can edit the weight of each competency.
Display section in summary The rating and weight of competencies are shown in the sum-
mary section.
Show calculated section rating The calculated competency rating is shown in the summary
section.
Rating Scale The rating scale used in this section. If you've selected a rating
scale in General Settings, you don't need to select it again here.
Hide numeric rating values (only show text labels) Select the checkbox to show on the form only the rating labels
defined in Rating Scales.
When the rating scale has no more than five rating levels, if
you select this option, the rating field on the form becomes a
dropdown list showing rating labels only.
When the rating scale has more than five rating levels, the de-
fault rating field is a dropdown list showing both rating values
and labels. If you select this option, the dropdown list shows
rating labels only.
Default Rating The label that is shown in the rating field if users haven't rated
on competencies
Choose an alternate label for the rating field The label of the official rating field
If Job Profile Builder is enabled in your instance and data migration to Job Profile Builder is successful, you can
enable the Capability Picker for users to add competencies to Performance Management forms.
Prerequisites
• You have selected JDM v2.0/Skills Management and migrated Families/Roles/Competencies from JDM 1.0 in
Provisioning.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
• The permission of Performance Management Feature Settings under Manage System Properties is granted.
Context
The Capability Picker retains the features of the Competency Picker, for example,
• If you configure specific competency categories in the form template, only the competencies from those
categories are shown.
• If you use behaviors, only the competencies that have behaviors are shown.
Compared to the Competency Picker, the Capability Picker allows users to select competencies by competency
libraries or job roles in a hierarchy structure and to search for the competencies using keywords.
Procedure
The summary section displays the calculated form rating that is based on the ratings from goal and competency
sections. You can also enable manual rating, which is the official rating of the form when enabled.
The summary section also displays summarized information from all other sections in one central place. It displays
a list of goals and competencies with their official rating and weight.
Learn about the fields and options that you can configure and select for the summary section in the following table.
Section Name The name of the section that is shown on the form
Section Description The description of the section that is shown on the form
Allow manual rating Users can manually give the overall form rating to override the
calculated form rating.
Note
There is only one manual rating field, and anyone who
has permission for it can update the rating. For customers
who want employees to manually give an additional overall
form rating, they may need to create a custom section that
includes a custom field for employees to record the rating.
Weights The weight of each goal and competency section for the cal-
culated form rating. You can choose Weight Section Equally
or manually enter weights for different sections, which should
add up to 100%.
Allow Override of Unrated Manual Rating With the manual rating enabled, this option allows the calcu-
lated rating to overwrite the unrated manual rating when the
form is sent to the next step.
Enable "Enforce Maximum Overall Score" With the manual rating enabled, this option sets the maximum
overall score that can be given based on the ratings at the
goal or competency level. See Configuring Enforce Maximum
Overall Score for more information.
Default Rating The label that is shown in the rating field if users haven't rated
Choose an alternate label for the rating field The label of the official rating field
Unable to Rate The label of a special rating on the rating scale, for example,
Too New to Rate. Performance reviewers can select this rating
when they think it's too early to give a regular rating for an
employee.
Note
The rating scale used in the summary section is set in Manage Templates General Settings .
Related Information
When you configure Enforce Maximum Overall Score (EMOS), you set limitations on the rating that a specified role
can give to an employee.
Context
EMOS, also known as "Fail one, fail all", allows you to set a maximum possible overall score to be selected by the
rater, based on the ratings at the goal or competency level. The rater can't give a score that is higher than you set.
Procedure
The "Enforce Maximum Overall Score" Configuration dialog box pops up.
6. Specify the parameters in the dialog box.
The goal competency summary section calculates the OCOC rating, overall goal rating, and overall competency
rating, and allows users to edit the last two ratings.
• OCOC rating: The overall calculated goal and competency rating. It is the overall form rating if no summary
section or performance potential summary section is used. If the overall goal rating or overall competency
rating can be edited, the OCOC rating is calculated based on the manual rating.
• Overall goal rating: An aggregate of ratings from the goal sections on the form.
• Overall competency rating: An aggregate of ratings from the competency sections on the form.
The section can be configured to show a chart of goal and competency ratings. The overall goal rating and overall
competency rating of an employee determine the quadrant in which the employee falls.
Use
We recommend that customers use the goal competency summary section on the form if they want to use the
overall goal rating and overall competency rating in other modules, for example:
Tip
If you don't configure the goal competency summary section, you can export the overall goal rating and overall
competency rating and import them to the other modules accordingly.
Note
To use the goal competency summary section, make sure that X and Y axes are configured as Competency and
Objective in Matrix Grid Reports: How vs. What.
Configuration
Learn about the fields and options that you can configure and select for the goal competency summary section in
the following table.
We recommend that you use the XML template to configure the goal competency summary section. See Goal
Competency Summary Section (objcomp-summary-sect) for more information.
Section Name The name of the section that is shown on the form
Calculate overall competency rating Calculated Form Rating for competencies is enabled. It is the
field for the calculated rating.
Note
Because the overall competency rating is calculated based
on the ratings from the competency sections, Include in
overall Competency rating calculation needs to be selected
in the competency sections.
Allow overall competency rating to be edited Overall Form Rating for competencies is enabled. It is the field
for the manual rating. Users can manually give the overall com-
petency rating.
Calculate overall objective rating Calculated Form Rating for goals is enabled. It is the field for
the calculated rating.
Note
Because the overall goal rating is calculated based on the
ratings from the goal sections, Include in overall Goal rating
calculation needs to be selected in the goal sections.
Allow overall objective rating to be edited Overall Form Rating for goals is enabled. It is the field for the
manual rating. Users can manually give the overall goal rating.
Display the overall objective / competency matrix A chart of goal and competency ratings is enabled.
Overall Rating Display Order Only the manual-calc option is supported. The manual rating is
always shown above the calculated rating.
Section Display Order • comp-obj: Competency sections are shown above goal
sections.
• obj-comp: Goal sections are shown above competency
sections
Related Information
Configure the rating scales for the overall goal rating, overall competency rating, performance rating, and potential
rating, so that they can be used when users manually give those ratings.
Prerequisites
For customers who don't have a Succession Planning license or don't enable the module, make sure that the
following prerequisites are met.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
2. The permission of Matrix Grid Rating Scales under Manage Succession is granted.
Context
If you change a rating scale that in-progress forms are using, the rating scale on the forms is updated.
Procedure
• Performance
• Potential
• Competency
• Objective
The rating value and description are shown together on the form.
5. Choose Save Changes.
The performance potential summary section allows users to manually give the performance rating and potential
rating.
Use
The section can be configured to show a chart of performance and potential ratings. The performance rating
and potential rating of an employee determine the quadrant in which the employee falls. If users can edit both
performance and potential ratings, they can drag employee names from one block on the chart to another in order
to change performance and potential ratings.
Users have the following options to include additional employees on the chart.
• All employees assessed: Displays employees (Employee role) who have a form required as follows:
• The form should be created from the same template as the current form.
• The current user should be a defined role in the route map of the form.
Forms that have been completed within the last 60 days are included.
Note
With this option, if a manager also has a form created from the same form template, they can see
themselves on the chart based on the ratings given by their manager. To prevent this, you can set a filter
for this option. For more information, see the <perfpot-matrix-grid-filter> element in Performance
Potential Summary Section (perfpot-summary-sect) in Related Information.
• My direct reports: Displays users' direct reports who have a form required as follows:
• The form should be created from the same template as the current form.
• The current user should be a defined role in the route map of the form.
Forms that have been completed within the last 60 days are included. If you've set filters for the previous
option, this option doesn't work.
Selected options remain effective the next time users open any Performance Management forms with the chart
configured.
Configuration
Learn about the fields and options that you can configure and select for the performance potential summary
section in the following table.
Section Name The name of the section that is shown on the form
Section Description The description of the section that is shown on the form
Allow overall performance rating to be edited Users can manually give the performance rating. The rating
scale used is configured in Matrix Grid Rating Scales. See Con-
figuring Matrix Grid Rating Scales for more information.
Allow overall potential rating to be edited Users can manually give the potential rating. The rating scale
used is configured in Matrix Grid Rating Scales. See Configur-
ing Matrix Grid Rating Scales for more information.
Display the overall performance-potential matrix A chart of performance and potential ratings is enabled.
Notes
Please note the following impacts when you use the performance potential summary section.
Recommendation
In case that users give a manual rating in the summary section, we recommend that rating scales should be
consistent in both sections, including the Unrated and Too New to Rate configurations. So, the rating in the
performance potential summary section is updated automatically.
Related Information
The Customized Weighted Rating section shows the calculation details that arrive at the calculated rating, including
route steps, roles in each step and their names, ratings, and weights configured in business rules.
Use
Caution
If you want to continue to use the form templates created in 1H 2020, you must configure the rating scale for
the Customized Weighted Rating section in Manage Templates. This configuration is required so that you can
launch forms based on the configured form templates. For the forms launched in 1H 2020, the rating scale for
the Customized Weighted Rating section inherits the same rating scale as used in 1H 2020.
The Customized Weighted Rating section supports two overall scores: the calculated rating and the manual rating.
The calculated rating is calculated based on the ratings given by roles in a route map and the weights configured in
business rules. The calculation can be triggered at a certain step. The manual rating is the official rating when both
the calculated rating and the manual rating are available. If there’s only a calculated rating, this rating becomes the
official rating.
Note
If the manual rating is enabled, the manual rating is defaulted to Unrated. However, if you select Allow Override
of Unrated Manual Rating, the calculated rating will override the unrated manual rating when the form is sent to
the next step. In this case, the calculated rating is rounded to a label that applies to the rating scale score for
the section. Therefore, if you want to use the manual rating as the official rating, you always need to rate the
manual rating after it’s enabled.
The following table explains the information listed in the Previous Ratings table:
Field Description
Note
If the rating scale that applies to the overall form rating is
different from that mapped to the Customized Weighted
Rating section, the overall form rating is normalized to the
rating scale for the Customized Weighted Rating section.
Route Step The route step at which the role gives the rating.
In the En Route folder, the login role's rating and the ratings given by other roles in previous steps are listed in the
Previous Ratings table. After the form goes to the Completed folder, the login role can get a complete view of the
ratings that are given by all roles in the Previous Ratings table.
Configuration
Learn about the fields and options that you can configure and select for the Customized Weighted Rating section in
the following table.
Unable to Rate The label of a special rating on the rating scale, for example,
Too New to Rate. Performance reviewers can select this rating
when they think it's too early to give a regular rating for an
employee.
Allow manual rating If selected, allow users to manually override the calculated
rating on the form. All reporting of employees' scores rely on
the manual rating instead of the calculated rating.
Allow Override of Unrated Manual Rating If a manual rating is enabled, select this option to allow the
calculated rating to override the unrated manual rating when
the form is sent to the next step.
Note
After you've added the section, its rating scale inherits the
form's rating scale. You can select a different rating scale
for the section.
Hide numeric rating values (only show text labels) If a rating's numeric value is mapped to a certain label for the
manual rating's rating scale scores of the section,
Section permissions Configure the section permissions for roles and route steps.
Field permissions Configure the field permissions with Calculated Rating and
Manual Rating.
Limitations
• In the Team Overview page, the overall rating in the Customized Weighted Rating section isn't shown.
Related Information
By default, all roles in all steps are granted with all form permissions, including permissions for buttons, tabs,
sections, actions, and fields. You can configure the form template to allow a role to have or not to have a specific
permission in a specific step.
Procedure
Option Description
0 Button Permission(s) defined. Click to modify. For configuring the permission for buttons and pods on the
form. For more information, see the Button Permissions
topic.
0 Other's Rating Tab Permission(s) defined. Click to mod- For configuring the permission for the Ratings from Others
ify. tab on the form. For more information, see the Tab Permis-
sions topic.
0 Section Permission(s) defined. Click to modify. For configuring the permission for sections on the form. For
more information, see the Section Permissions topic.
0 Action Permission(s) defined. Click to modify. For configuring the permission for actions on the form. For
more information, see the Action Permissions topic.
0 Field Permission(s) defined. Click to modify. For configuring the permission for fields on the form. For
more information, see the Field Permissions topic.
Field Description
Type The type of different form permissions varies. For more in-
formation on the available types of each permission, see the
related topics of the permissions.
Route Steps • All: You grant the defined permission to specific roles in
all steps.
Add Field For field permissions only. For more information on the op-
tions, see the Field Permissions topic.
Note
The permission that you configured first is overridden by the permission that you configured last.
Recommendation
If you want to grant permissions to some roles, define the none permission to all roles in all steps first, and
then grant permissions to the desired roles.
If you want to grant access to a field when the form is completed, grant the read permission in all steps
first, and then either grant the write permission or hide the field in particular steps.
6. Choose Done in the dialog box and choose Save on the page.
Learn about the button permission type and the permission-configurable buttons and pods on the Performance
Management form.
Permission Type
The permission type only applies to permitted roles in some or all steps.
Finalize Form send Used to send the form to the To configure this button,
next step.
Disable Send button shouldn't
be selected in Form Template
Settings.
Send to Previous Step send-back Used to send the form to the To configure this button,
previous step.
• Enable form routing to
previous step should
be selected in Form
Template Settings.
• Enable Previous Step
Button should be selected
in Manage Templates
General Settings .
Delete Form delete Used to delete the form from To configure this button,
the instance.
• Disable Form button
shouldn't be selected in
Form Template Settings.
• Enable Delete Button
should be selected in
Manage Templates
General Settings .
Add Modifier add-modifier Used to add users to edit the You can configure the permis-
form. For more information, sion for these buttons only in
see Add Modifier. an XML form template.
Remove Signer
Pod List
Button Prioritization
To optimize user experience, a maximum of five buttons are shown at the bottom of the form. Except Save and
Close and Cancel, which are always visible, other buttons are shown based on your selection and the predefined
prioritization order.
If you enable no more than three buttons, all the buttons are shown. If you enable more than three buttons,
according to the following prioritization, some buttons are shown and others are included in the More Actions
button.
1. Finalize Form / Sign / Confirm 1:1 (Only one of the buttons is shown at a time)
2. Reject
3. Send to [username] (For iterative steps only)
4. Get Feedback / Recall Feedback
5. Send to Previous Step
6. Add Modifier
7. Add Signer
Example
If you enable Finalize Form, Get Feedback, and Add Signer, three buttons are shown along with Save and Close
and Cancel.
If you enable one more button Add Modifier, Add Modifier and Add Signer are included in More Actions, which is
shown along with other four buttons.
Learn about the tab permission type and the permission-configurable tabs on the Performance Management form.
Permission Type
The permission type only applies to permitted roles in some or all steps.
Tab List
Goal Ratings from Others • To configure the Used to show other You can configure the
users' ratings.
permission in permission for this tab
Competency
the meta sec- in Manage Templates or
tion: <others- an XML form template.
ratingtab-
permission>
• To configure the
permission in a
specific section:
others-rating
Goal Goal Details goal-details Used to show goal de- You can configure the
tails from Goal Manage- permission for these
ment. tabs only in an XML
form template.
Other Details other-details Used to show other de-
tails of goals.
Learn about the section permission type and the permission-configurable sections on the Performance
Management form.
Permission Type
Disabled disabled Users can view the section, but can't edit
it.
The permission type only applies to permitted roles in some or all steps.
Section List
Section Permission-Configurable
Introduction Yes
Goal Yes
Competency Yes
Summary Yes
Signature Yes
Custom Yes
Additional Comments No
Learn about the action permission type and the permission-configurable actions on the Performance Management
form.
Permission Type
The permission type only applies to permitted roles in some or all steps.
Action List
Goal Add Item add-item Users choose Add Goal To configure these
to add goals to the goal
actions, Allow users
section.
to add/remove Goals
within the section
should be selected in
Learn about the field permission type and the permission-configurable fields on the Performance Management
form.
Permission Type
Read read Users can view the field, but can't edit it.
Note
For all calculated rating fields, the
write permission is regarded as the
read permission.
The permission type only applies to permitted roles in some or all steps.
Field List
Competency Unofficial User Rating user-item-cmt- The unofficial rating To configure this field,
rating field of a goal or compe- you should use Rating
tency Option 1 or 2.
Section Weight sect-weight The weight field of the To configure this field,
goal section or compe-
tency section. With the
• Show section
in Manage
Templates Goal
Section .
• For the compe-
tency section:
Display Section
in Summary
and Display
in Competency
section should
be selected
in Manage
Templates
Competency
Section .
Subject Rating subject-item- The rating field of a goal To configure this field,
rating or competency for the you should use Rating
form subject Option 3.
Item Group item-group The goal or competency You can configure the
group permission for these
fields only in an XML
Expected Rating expected-item- The expected rating
form template.
rating field of competencies.
Only available in the
competency section.
Summary Section Comments section-comments The comment field of To configure this field,
the summary section Show Section Comment
should be selected in
Manage Templates
Summary Section .
Manual Overall Rating manual-overall- The rating field in the To configure this field,
rating summary section where Allow manual rating
users give the overall should be selected in
form rating. Manage Templates
Summary Section .
Goal Competency Sum- Section Comments section-comments The comment field of To configure this field,
mary the goal competency Show Section Comment
summary section should be selected
in Manage Templates
Goal Competency
Summary Section .
Objective Manual Over- obj-manual- The rating field in the To configure this field,
all Rating overall-rating goal competency sum- Allow overall objective
mary section where rating to be edited
users give the overall should be selected
goal rating in Manage Templates
Goal Competency
Summary Section .
Calculated Overall comp-calculated- The field in the goal You can configure the
Competency Rating overall-rating competency summary permission for these
section where the cal- fields only in an XML
culated overall compe- form template.
tency rating is shown
Performance Potential Manual Performance manual- The rating field in the To configure this
Summary Rating performance- performance potential field, Allow overall
rating summary section where performance rating
users give the perform- to be edited should
ance rating be selected in
Manage Templates
Performance Potential
Summary Section .
Manual Potential Rating manual- The rating field in the To configure this field,
potential-rating performance potential Allow overall potential
summary section where rating to be edited
users give the potential should be selected in
rating Manage Templates
Performance Potential
Summary Section .
Customized Weighted Manual Rating cwr-manual- The rating field in the To configure this field,
Rating rating customized weighted Allow manual rating
rating section where should be selected in
users give the overall Manage Templates
form rating
Customized Weighted
Rating Section .
Configure required fields in a specific step to require users to complete the fields before they send the form to the
next step.
Procedure
Field Description
Send Action Users must complete the required fields before they can
take the following actions:
• Next Step: Send the form to the next step
• Sign: Sign the form
Note
To make required field configuration take effect when
users send the form to another user in an iterative step,
you need to configure the send action in XML template.
Route Steps Users must complete the required fields in a specific step or
all steps:
• All: All steps
• Selected: The steps you selected
Section Field
Item Weight
Section Weight
Item Comments
Note
If you select the Item Comments or Section Comments
field, you can set a minimum character limit and a max-
imum character limit in Minimum Value and Maximum
Value respectively. The default value is -1. Please enter a
positive number for the minimum value.
Subject Rating
Section Comments
Custom Note
To configure this field in the signature section, Include
Signature Section .
You can set multiple fields as required fields with the same configuration by choosing Add Field.
For more information on the description of the fields listed above, see Field Permissions in Related
Information.
Results
The required fields will appear with a red asterisk (*) on the form.
Related Information
Configure custom fields in a goal section, competency section, and custom section according to your business
needs.
Context
Procedure
Depending on the selected type, you need different configurations. Refer to the following table for more
information.
Editable during mass creation of forms Select this option to allow editing the
field during mass creation of forms.
Note
Writing Assistant only works for the
field in a competency section. It is
not available in a custom section.
Note
The text format on forms is cen-
trally determined by form template
settings. To use Rich Text Editor,
make sure that Use Plain Text Only
for Comments is not selected in
Form Template Settings.
Editable during mass creation of forms Select this option to allow editing the
field during mass creation of forms.
Custom Element's list's value type Select a value type for list options:
• Integer
• Text
• Date
• Double
Custom Element's list's default name Select the radio button to define the de-
fault list option.
Recommendation
If you grant different access per-
missions to roles for the list field,
we recommend that you do not de-
fine the default list option. Leave
the Custom Element's list's default
name field blank and choose Add
Element to List to define list op-
tions.
Custom Element's list's default name Enter the name of the default list op-
tion.
Checkbox Editable during mass creation of forms Select the option to allow enabling or
disabling the checkbox during mass
creation of forms.
Note
5. Choose Done in the dialog box and choose Save on the page.
Localize labels in the form template so that labels on forms can be shown in logged-in user's language.
Prerequisites
To localize labels in a language that uses characters not included in the Basic Latin character set, such as Bulgarian
and Romanian, make sure that Always use TTF Embedding for PDF is enabled in Provisioning. Otherwise, these
languages may not be correctly rendered in PDF output.
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Procedure
A message key associated with your label and language configuration is generated.
The label and language configuration associated with the message key appears.
d. Choose Use this message configuration, refresh.
e. Choose Done in the dialog box and choose Save on the page.
A message key is a random number generated in the system when you localize labels in the form template. When
you edit an existing message key, a new one is created and used.
Context
When a form template is saved as another template, the existing message keys generated in the original template
are copied to the new template. We recommend that you edit those message keys in the new template, so to
distinguish them between different templates. Therefore, when you update label and language configuration in one
template, other templates are not affected.
In Manage Form Label Translations, you can update form label translations, and view the count and name of form
templates where message keys are used.
Context
Note
You can't update label translations for the forms that have already been launched.
Procedure
Option Description
Export Form Label Translations You can export all label translations or the label translations
associated with a particular template.
Import Form Label Translation File You can upload a CSV file based on the form label translation
template to update the label translations.
Caution
The columns of languages that you don't use should be
deleted.
If you import a new message key, you also need to add the
message key to the XML template.
Sample Code
<obj-sect-name
msgKey="PM_GoalSection_name"><!
[CDATA[Goals]]></obj-sect-name>
Form Label Translation Matrix You can use Label Key or Form Template Name to search for
message keys and view the count and name of templates
where these keys are used.
When configuring form templates, you define form settings, for example, form title and description, associated
route map and rating scale, fields and sections, and form permissions. You can use an XML file to configure a form
template and upload it to Admin Center, or edit an existing form template in Provisioning.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Upload a new XML form template so that you can configure the template for performance reviews.
Procedure
Next Steps
Edit the sections and fields of the template or upload an updated template in Provisioning.
The Document Type Definition (DTD) file for Performance Management (sf-form.dtd) defines the structure and
all elements and attributes of the XML form template.
The most basic components of the DTD file for form templates are listed as follows.
Elements can have attributes. The attributes are a list of options that affect the behavior of the element.
To download the latest DTD file, go to Software Center . Go to INSTALLATIONS & UPGRADES DTD
Configuration Files , and choose Download Basket.
This is an XML form template. It consists of an introduction section, a goal section, a competency section, a
summary section, and a signature section.
After you upload a form template, you can edit the template in Provisioning.
Prerequisites
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Context
You can also edit the template by downloading it from Admin Center Form Template Settings , editing it using
an XML editor, and uploading it to Provisioning.
Procedure
Reorder or delete existing sections In the Arrange Sections area, reorder the sections by se-
lecting a section and choosing Move Here, or delete un-
necessary sections.
Configure template settings In the Edit Form Attributes area, make changes and Save
Form.
Edit sections and fields In the Edit Sections area, make changes and Save Form.
The meta section of a Performance Management form is not a section that can be shown on the form. Instead,
you can configure elements under <fm-meta> for form-level features, for example, rating scale, scale adjusted
calculation, and attachments.
For more information on all available elements, refer to the DTD file.
Users can manage attachments in the Supporting Information pod on Performance Management forms. You can
configure permissions for attachments according to customer's business needs.
Prerequisites
Procedure
<attach-action> • read: Users can view all attachments, but can only add
and edit their own attachments.
In this example, employees have the edit permission and managers have the read permission to attachments,
while all other users can't view attachments.
Sample Code
<fm-meta>
<meta-form-id>-1</meta-form-id>
<meta-rated>true</meta-rated>
<meta-rating>0.0</meta-rating>
<meta-scale>0.0</meta-scale>
<meta-grp-label><![CDATA[Group]]></meta-grp-label>
<fm-sect-scale show-value="true">
<scale-source>1</scale-source>
<scale-id><![CDATA[2005b]]></scale-id>
<scale-type><![CDATA[null]]></scale-type>
</fm-sect-scale>
<meta-item-weight-floor-ceiling-option>warning</meta-item-weight-floor-
ceiling-option>
<attachment-permission type="none">
<role-name>*</role-name>
<attach-action refid="read"/>
<attach-action refid="edit"/>
</attachment-permission>
<attachment-permission type="enabled">
<role-name>E</role-name>
<attach-action refid="edit"/>
</attachment-permission>
<attachment-permission type="enabled">
<role-name>EM</role-name>
<attach-action refid="read"/>
</attachment-permission>
</fm-meta>
Related Information
Users with certain role-based permissions can mass route forms in the form inbox. You can further configure
permissions in an XML form template, for example, to allow users to mass route forms only in a specific step.
Prerequisites
Users are granted with the permissions of Mass Route Document Forward and Mass Route Document Backward
under Manage Documents in Manage Permission Roles.
Procedure
Recommendation
We recommend that you set this attribute to true so
that forms should pass validation before being routed to
avoid data issues for other modules.
<route-step> Step ID
In this example, only managers can mass route forms in a collaboration step and the forms should pass
validation before being routed.
Sample Code
<fm-meta>
<meta-form-id>-1</meta-form-id>
<meta-rated>true</meta-rated>
<meta-rating>0.0</meta-rating>
<meta-scale>0.0</meta-scale>
<meta-grp-label><![CDATA[Group]]></meta-grp-label>
<fm-sect-scale show-value="true">
<scale-source>1</scale-source>
<scale-id><![CDATA[2005b]]></scale-id>
<scale-type><![CDATA[null]]></scale-type>
</fm-sect-scale>
<meta-item-weight-floor-ceiling-option>warning</meta-item-weight-floor-
ceiling-option>
You can configure character limits and a character limit bar for section comments, item comments, and custom
text area fields to alert users when the configured character limits are reached.
Context
The default maximum limit is 4,000 characters. If users enter more than that, a warning message is displayed and
the excess characters are truncated. You can also customize the limit by section.
Additionally, when 75% of the default or customized limit is used in comment fields, a character limit bar is
displayed on the bottom-right of the fields. By hovering the mouse over the bar, users can view the number of
characters allowed before the limit is reached.
The configuration can be applied to goal section, competency section, summary section, goal competency
summary section, performance potential summary section, signature section, and custom section.
Note
When Stack Ranker is enabled, section comments and item comments in the competency section allow a
maximum of 4,000 characters. A warning message is displayed when users exceed the limit.
Table reports only support 4,000 characters at maximum for text area fields. If a text area field is configured to
have more than 4,000 characters, only the first 4,000 characters are shown on a report.
Procedure
Sample Code
<fm-meta>
<meta-form-id>-1</meta-form-id>
<meta-rated>true</meta-rated>
2. To customize the character limit by section, set the cmt-max-limit attribute to a number greater than -1 in a
specific section.
Next Steps
You can also configure the character limits by the minimum value and maximum value of required fields. If the
maximum value of required fields is less than 4,000, this value will prevail the cmt-max-limit configuration.
Related Information
You can find the DTD definition, attributes, and elements applicable to this section. This topic lists only the
attributes and elements that are commonly used. For more information, refer to the latest DTD file.
DTD Definition
<!ATTLIST objective-sect
index CDATA #REQUIRED
configurable (true | false) "false"
Attributes
Attribute Description
index A number that represents the display order of the section on the form, for
example, 0, 1, 2, 3.
When you move a section in Provisioning, the index number assigned to the
section will be updated automatically to reflect how you have rearranged the
sections on the form.
configurable
Set to true if you want to allow users to add and remove items within the
section.
no-rate
Set to false if you want rating scale for items to appear within the section.
develop-goal Set to false if you are configuring this section for performance goals.
show-learning-activity-competency Set to false if you want learning activities for compentencies to appear
within the section.
split-cmt
Set to true if you want subject's and manager's comments to show side by
side.
Note
In Performance Management, the attribute is always set to true.
rating-opt
Option values are 0 (default), 1, 2, and 3.
in-summ-display Set to true if you want the section to show in the summary section.
in-overall-rating
Set to true if the section is used in the calculated form rating.
if-no-ratings-then-ignore-section If the section has no ratings, it is excluded from the calculated form rating.
To use 0 for the section in the calculated form rating, set the attribute to
false.
lock-item-weights Set to true if you don't want the weight of goals to be edited.
in-objcomp-summ-display Set to true if you want the section to show in the goal competency sum-
mary section.
in-objcomp-summ-overall-rating Set to true if you want to include the section in the overall goal rating in the
goal competency summary section.
• Set this value to true if you want all the goals in one goal section to be
equally weighted.
• Set this value to false if you want to specify goal weights or to import
the goal weights from a goal plan. Thus the goal weights are shown in
the section and the section's average rating is used in the calculated
form rating.
When you set the attribute to true, table reports will no longer generate a
report on the section weight of the section. Once you set it back to false,
the reports can pull the section weight again.
auto-pop-weights
Set to true if you want to auto-populate the goal weights from the goal
plan. The no-weight attribute must be set to false at the same time.
min-goals-required The minimum number of goals that must be in this section to allow the form
to be routed
max-goals-allowed The maximum number of goals allowed in this section, exceeding which the
form will not be routed
hide-addexistinggoals-btn Set to false to show the button that is used to add existing goals in the
linked goal plan to the form.
Note
• To see and use this button, users need to have the create permis-
sion for goals in the goal plan template.
• The button is not needed if goals are synced to the form automati-
cally.
sect-mode Set to EZ-Rater if customers want to use the EZ Rater feature. See EZ
Rater for more information.
ez-rater-expand-all If the section is in the EZ Rater mode, to expand all competency details, set
the attribute to true. See EZ Rater for more information.
obj-edit Set to popup if you want users to edit goals in a popped-up window.
show-calculated-section-rating Set to true if you want to show the calculated section rating.
use-mlt-rating-if-present Set to true if you want the metric lookup table and ratings from the goal
plan to be considered for rating calculation.
exclude-private-goals Set to true if you want to exclude private goals from the form. Thus users
cannot add a new private goal to the form.
Note
This option only works when you launch a form. If you change public
goals on the form to private goals after launching the form, the goals still
appear on the form.
Elements
Element Description
tab-permission type See Form Permissions in XML Template for more information.
sect-weight The weight of the section for the calculated form rating in the
summary section
sect-weight-4-objcomp-summary The weight of the section for the overall goal rating in the goal
competency summary section
obj-sect-type
The obj-sect-type element indicates how to populate the
goal section:
obj-plan-state-change Configure this element to allow changing the goal plan state
when the form is routed. See Changing the Goal Plan State on
Form Routing for more information.
Related Information
You can auto-populate goals from a goal plan into a goal section, and auto-synchronize goals between the goal plan
and the Performance Management form.
Prerequisites
Considering the fields and layout defined in a goal plan template will appear on the form, make sure that you've
set the type of the name field as text in the goal plan template. If you've set it as enum, set both enum-value and
enum-label as text. This ensures that the text is correctly displayed in the goal section, just as it is in the goal plan.
Procedure
Note
• For the location where the elements should be added, refer to the DTD Definition section in Goal
Section (obj-sect).
• Specify the goal plan ID in the <obj-sect-plan-id> element.
Sample Code
<obj-sect-type><![CDATA[plan]]></obj-sect-type>
<obj-sect-plan-id>3</obj-sect-plan-id>
2. To auto-synchronize goals between a goal plan and a form, set the autosync attribute to true in the <obj-
sect-type> element.
Note
The autosync attribute only applies when a goal plan is referenced in the <obj-sect-type> element.
Note
If you use the latest Goal Management and you enabled the auto-sync feature in Performance
Management, please be aware of the following:
• Users can delete a goal on a Performance Management form only when they have the User
Permissions Objectives Objective Plan Permissions role-based permission to the goal plan of that
goal. The goal deleted from the form will also be deleted from the goal plan.
• Users without the permission can't see the button to delete the goal on the form.
Sample Code
<obj-sect-type autosync="true"><![CDATA[plan]]></obj-sect-type>
3. To populate goals of certain categories, add the <obj-category> element and specify the category ID.
Note
Category ID is the internal id that was assigned to a goal category in a goal plan template. See Defining
Category and Default-Category for more information.
Sample Code
<obj-sect-type><![CDATA[plan]]></obj-sect-type>
<obj-sect-plan-id>3</obj-sect-plan-id>
<obj-category><![CDATA[Customer]]></obj-category>
<obj-category><![CDATA[Financial]]></obj-category>
Note
Sample Code
<obj-sect-type><![CDATA[plan]]></obj-sect-type>
<obj-sect-plan-id>3</obj-sect-plan-id>
<obj-type><![CDATA[user]]></obj-type>
Related Information
You can set the ceiling and floor for weights so that users can't add a goal weight out of the specified range.
Context
If you specify a weight ceiling and floor, by default a warning is displayed to users when a weight is out of the range.
This warning doesn't prevent users from routing the form to another user. If you want to force the user to correct
the out-of-range weight before routing the form, configure the warning as an error instead.
Sample Code
<fm-meta>
<meta-form-id>-1</meta-form-id>
<meta-rated>true</meta-rated>
<meta-rating>0.0</meta-rating>
<meta-scale>0.0</meta-scale>
<meta-grp-label><![CDATA[Balance Scorecard]]></meta-grp-label>
<meta-grp><![CDATA[Customer]]></meta-grp>
<meta-grp><![CDATA[Financial]]></meta-grp>
<meta-grp><![CDATA[Learning]]></meta-grp>
<meta-grp><![CDATA[Operations]]></meta-grp>
<fm-sect-scale show-value="true">
<scale-id><![CDATA[Default Scale]]></scale-id>
<scale-type><![CDATA[null]]></scale-type>
</fm-sect-scale>
<meta-item-weight-floor-ceiling-option>warning</meta-item-weight-floor-
ceiling-option>
</fm-meta>
Note
Replace warning with error if you want to prevent users from saving or forwarding the form when a
weight falls beyond the range.
2. Add the <item-weights> element to set the weight ceiling and floor.
Sample Code
You can find the DTD definition, attributes, and elements applicable to this section. This topic lists only the
attributes and elements that are commonly used. For more information, refer to the latest DTD file.
DTD Definition
<!ATTLIST competency-sect
index="7"
configurable="true"
mgt-only="false"
use-jobcode="false"
use-core-comp="false"
category-filter-opt="no-filter"
no-rate="false"
no-weight="false"
summ-opt="0"
split-cmt="false"
rating-opt="0"
cmt-opt="0"
suppress-item-comments="0"
behavior-rating-opt="0"
behavior-cmt-opt="1"
behavior-mode-opt="0"
in-summ-display="true"
in-overall-rating="true"
no-group="true"
use-behavior="false"
if-no-ratings-then-ignore-section="true" l
lock-item-weights="false"
in-objcomp-summ-display="false"
in-objcomp-summ-overall-rating="false"
show-comp-expected-rating="false"
show-comp-proficiency-level="false"
comp-expected-rating-format="0"
Attributes
Attribute Description
index A number that represents the display order of the section on the form, for example, 0, 1, 2, 3.
When you move a section in Provisioning, the index number assigned to the section will be
updated automatically to reflect how you have rearranged the sections on the form.
configurable Set to true if you want to allow users to add and remove items within the section.
mgt-only Set to true if only managers and HR should view the section.
use-jobcode Used to auto-populate job-specific competencies to the section. See Auto-Populated Competen-
cies for more information.
use-core-comp Used to auto-populate core competencies to the section. See Auto-Populated Competencies for
more information.
no-rate Set to false if you want rating scale for items to appear within the section.
no-weight
Set to false if you want competency weights to show in the section and the section's average
rating to be used in the calculated form rating.
When you set the attribute to true, table reports will no longer generate a report on the section
weight of the section. Once you set it back to false, the reports can pull the section weight
again.
split-cmt
Set to true if you want subject's and manager's comments to show side by side.
Note
In Performance Management, the attribute is always set to true.
rating-opt
Option values are 0 (default), 1, 2, and 3.
suppress-item-comments Only the default value 0 is available, which is used to show item comments.
behavior-rating-opt The rating options for behaviors. See Rating Behaviors for more information.
behavior-cmt-opt The comment options for behaviors. See Rating Behaviors for more information.
behavior-mode-opt The display mode of behaviors when they are only shown but not rated. See Showing but Not
Rating Behaviors for more information.
in-summ-display Set to true if you want the section to show in the summary section.
in-overall-rating
Set to true if you want the section to be used in the calculated form rating.
no-group Set to false if you want the competency groups that have been defined in the meta section to
show in the section.
use-behavior Set to true if you want users to rate behaviors instead of competencies. See Rating Behaviors
for more information.
if-no-ratings-then-ignore- If the section has no ratings, it is excluded from the calculated form rating. To use 0 for the section
section in the calculated form rating, set the attribute to false.
in-objcomp-summ-display Set to true if you want the section to show in the goal competency summary section.
in-objcomp-summ-overall- Set to true if you want the section to be included in the overall competency rating in the goal
rating competency summary section.
show-comp-expected-rat-
Set to true if you want competencies' expected rating for the employees' job role to show. It is
ing
required for showing the gap between expected and actual competency rating.
When you set the attribute to true, you can configure the permission for the expected rating
field using expected-item-rating.
Note
If you've upgraded to Talent Intelligence Hub, this attribute is not yet supported when users
add competencies to the form through the picker. Users won't see expected ratings next to
the competencies added to the form.
show-comp-proficiency- Set to true if you want the proficiency level of competencies to show.
level
show-behavior-expected-
Set to true if you want behaviors' expected rating for the employees' job role to show.
rating
When you set the attribute to true, you can configure the permission for the expected rating
field using expected-item-rating.
Note
• This attribute should be ignored if use-behavior is set to false.
• If you've upgraded to Talent Intelligence Hub, this attribute is not yet supported when
users add behaviors to the form through the picker. Users won't see expected ratings
next to the behaviors added to the form.
behavior-weighted Set to true if you want behaviors to be weighted. Set to false if you want behaviors to be
equally weighted and no weight fields to show.
min-competencies-required The minimum number of competencies that must be in the section. It is validated when the form
is routed.
max-competencies-allowed The maximum number of competencies that are allowed to be in the section. It is validated when
the form is routed.
sect-mode Set to EZ-Rater if customers want to use the EZ Rater feature. See EZ Rater for more informa-
tion.
ez-rater-expand-all If the section is in the EZ Rater mode, to expand all competency details, set the attribute to true.
See EZ Rater for more information.
show-calculated-section- Set to true if you want the calculated section rating to show.
rating
lock-behavior-content
If the value is true, behaviors are hardcoded to the form during form creation and modification,
rather than being linked to the corresponding competency. When the job code changes or the
behavior name or description is updated, the behaviors for the existing form do not reflect the
changes.
If the value is false, behaviors are not hardcoded to the form during form creation and modifica-
tion, but are linked to the corresponding competency. When the job code changes or the behavior
name or description is updated, the behaviors for the existing form reflect the changes. When the
form is completed, the behaviors won't be updated anymore.
hide-waca Set to true if you want Writing Assistant to be hidden from the section. It is only applicable when
companies have enabled Writing Assistant. See Writing Assistant for more information.
Elements
Element Description
field-permission
sect-weight The weight of the section for the calculated form rating in the
summary section
sect-weight-4-objcomp-summary The weight of the section for the overall competency rating in
the goal competency summary section
Related Information
You define dedicated attributes or elements to determine which type of competencies are auto-populated to
competency sections.
Note
When a job code is mapped to multi-
ple job roles and the job roles include
the same competencies, the weights
of those competencies are populated
from the job role that comes first in
the alphabetical order.
You can add hard-coded competency ID and weight in the form template to use custom competencies in a
competency section.
Procedure
Note
For the location where the element should be added, refer to the DTD Definition section in Competency
Section (competency-sect).
2. Specify the corresponding competency ID using <fm-comp-id> and if necessary, specify the competency
weight using <fm-comp-weight>.
You can get the competency ID from one of the following tools:
• (For customers using Job Description Manager) Admin Center or Provisioning Manage
Competencies
• (For customers using Center of Capabilities) Admin Center Manage Center of Capabilities
• (For customers using Talent Intelligence Hub) Admin Center Manage Talent Intelligence Hub
Sample Code
<competency-sect index="3" configurable= " false " mgt-only= " false " use-
jobcode= " false " category-filter-opt= "no-filter" no-rate= " false " no-
weight= " false " summ-opt= "99" split-cmt= " false " rating-opt= "1" cmt-
opt= "2" suppress-item-comments= "0" behavior-rating-opt= "0" behavior-cmt-
opt= "1" behavior-mode-opt= "0" in-summ-display= " true " in-overall-rating=
" true " no-group= " true " use-behavior= " false " if-no-ratings-then-ignore-
section= " false " lock-item-weights= " false " in-objcomp-summ-display= "
false " in-objcomp-summ-overall-rating= " false " show-comp-expected-rating=
" false " comp-expected-rating-format= "0" show-behavior-expected-rating= "
false " behavior-expected-rating-format= "0" behavior-weighted= " false "
sect-mode= "normal" ez-rater-expand-all= " false ">
<comp-sect-name><![CDATA[Competencies]]></comp-sect-name>
<comp-sect-intro><![CDATA[<b>Skills</b>]]></comp-sect-intro>
<fm-sect-config>
<rating-label><![CDATA[Leader Rating]]></rating-label>
<rating-label-others><![CDATA[Associate Rating]]></rating-label-
others>
< default-rating><![CDATA[Not Rated]]></ default-rating>
<hidden-strength-threshold>0.0</hidden-strength-threshold>
<blind-spot-threshold>0.0</blind-spot-threshold>
<num-decimal-places>2</num-decimal-places>
<publish-button-label><![CDATA[Publish Content]]></publish-button-
label>
</fm-sect-config>
<sect-weight>10.0</sect-weight>
<fm-sect-scale show-value= " false ">
<scale-source>1</scale-source>
<scale-id><![CDATA[Competency Scale]]></scale-id>
<scale-type><![CDATA[ null]]></scale-type>
</fm-sect-scale>
Related Information
Center of Capabilities
Talent Intelligence Hub
Prerequisites
The use-jobcode attribute is set to true and the category-filter-opt attribute is set to specified-
category.
Context
If customers want to have different competencies auto-populated to different competency sections, you can set
category filters in the XML form template to determine which competencies should appear in a specific section.
Caution
To use this feature, make sure that all sections that will populate job-specific competencies have a category
filter assigned.
Note
For the location where the element should be added, refer to the DTD Definition section in Competency
Section (competency-sect).
Sample Code
<competency-sect index="3" configurable= " false " mgt-only= " false "
use-jobcode= " true " category-filter-opt= "specified-category" no-rate= "
false " no-weight= " false " summ-opt= "99" split-cmt= " false " rating-
opt= "1" cmt-opt= "2" suppress-item-comments= "0" behavior-rating-opt= "0"
behavior-cmt-opt= "1" behavior-mode-opt= "0" in-summ-display= " true " in-
overall-rating= " true " no-group= " true " use-behavior= " false " if-
no-ratings-then-ignore-section= " false " lock-item-weights= " false " in-
objcomp-summ-display= " false " in-objcomp-summ-overall-rating= " false "
show-comp-expected-rating= " false " comp-expected-rating-format= "0" show-
behavior-expected-rating= " false " behavior-expected-rating-format= "0"
behavior-weighted= " false " sect-mode= "normal" ez-rater-expand-all= " false
">
<comp-sect-name><![CDATA[Competencies]]></comp-sect-name>
<comp-sect-intro><![CDATA[<b>Skills</b>]]></comp-sect-intro>
<fm-sect-config>
<rating-label><![CDATA[Leader Rating]]></rating-label>
<rating-label-others><![CDATA[Associate Rating]]></rating-label-
others>
< default-rating><![CDATA[Not Rated]]></ default-rating>
<hidden-strength-threshold>0.0</hidden-strength-threshold>
<blind-spot-threshold>0.0</blind-spot-threshold>
<num-decimal-places>2</num-decimal-places>
<publish-button-label><![CDATA[Publish Content]]></publish-button-
label>
</fm-sect-config>
<sect-weight>10.0</sect-weight>
<fm-sect-scale show-value= " false ">
<scale-source>1</scale-source>
<scale-id><![CDATA[Competency Scale]]></scale-id>
<scale-type><![CDATA[ null]]></scale-type>
</fm-sect-scale>
<comp-category><![CDATA[1. Thought Leadership (Development)]]></comp-
category>
<comp-category><![CDATA[2. Results Leadership (Development)]]></comp-
category>
<comp-category><![CDATA[3. People Leadership (Development)]]></comp-
category>
<fm-competency index= "1" removable= " false ">
<fm-comp-id>1159</fm-comp-id>
<fm-comp-name><![CDATA[ null]]></fm-comp-name>
<fm-comp-desc><![CDATA[ null]]></fm-comp-desc>
</fm-competency>
<meta-grp-label><![CDATA[Group]]></meta-grp-label>
</competency-sect>
For customers using Job Description Manager, you can pull job-specific competencies in a competency section by
customized data type.
Prerequisites
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
Context
Generally, employees' competencies are auto-populated to a competency section according to their job code. You
can use the <fm-comp-filter-mapping> element to customize the mapping data type.
Procedure
1. In Provisioning, configure the data types to be used for mapping competencies in the Succession Data Model.
This example specifies that Job Code, Department, Division, Custom03, and Custom04 are valid mapping data
types.
2. Create a CSV file based on one particular mapping data type that you've configured, and import the file to
Admin Center Import Job Roles .
Note
For the location where the element should be added, refer to the DTD Definition section in Competency
Section (competency-sect).
Only one mapping data type can be specified for one competency section. Employees' value for the specified
mapping data type will be used for fetching the applicable job roles and the corresponding competencies.
The default value of the enable attribute is false. To enable the feature, set it to true.
<fm-comp-filter-mapping enable="true">
<fm-comp-filter-element refid="department"/>
</fm-comp-filter-mapping>
Sample Code
<competency-sect index="3" configurable= " false " mgt-only= " false " use-
jobcode= " true " category-filter-opt= "no-filter" no-rate= " false " no-
weight= " false " summ-opt= "99" split-cmt= " false " rating-opt= "1" cmt-
opt= "2" suppress-item-comments= "0" behavior-rating-opt= "0" behavior-cmt-
opt= "1" behavior-mode-opt= "0" in-summ-display= " true " in-overall-rating=
" true " no-group= " true " use-behavior= " false " if-no-ratings-then-ignore-
section= " false " lock-item-weights= " false " in-objcomp-summ-display= "
false " in-objcomp-summ-overall-rating= " false " show-comp-expected-rating=
" false " comp-expected-rating-format= "0" show-behavior-expected-rating= "
false " behavior-expected-rating-format= "0" behavior-weighted= " false "
sect-mode= "normal" ez-rater-expand-all= " false ">
<comp-sect-name><![CDATA[Competencies]]></comp-sect-name>
<comp-sect-intro><![CDATA[<b>Skills</b>]]></comp-sect-intro>
<fm-sect-config>
<rating-label><![CDATA[Leader Rating]]></rating-label>
<rating-label-others><![CDATA[Associate Rating]]></rating-label-
others>
< default-rating><![CDATA[Not Rated]]></ default-rating>
<hidden-strength-threshold>0.0</hidden-strength-threshold>
<blind-spot-threshold>0.0</blind-spot-threshold>
<num-decimal-places>2</num-decimal-places>
<publish-button-label><![CDATA[Publish Content]]></publish-button-
label>
</fm-sect-config>
<sect-weight>10.0</sect-weight>
<fm-sect-scale show-value= " false ">
<scale-source>1</scale-source>
<scale-id><![CDATA[Competency Scale]]></scale-id>
<scale-type><![CDATA[ null]]></scale-type>
</fm-sect-scale>
<fm-competency index= "1" removable= " false ">
<fm-comp-id>1159</fm-comp-id>
<fm-comp-name><![CDATA[ null]]></fm-comp-name>
<fm-comp-desc><![CDATA[ null]]></fm-comp-desc>
</fm-competency>
<meta-grp-label><![CDATA[Group]]></meta-grp-label>
<fm-comp-filter-mapping enable="true">
<fm-comp-filter-element refid="department"/>
</fm-comp-filter-mapping>
Behaviors in a competency section can be configured in a flexible way. The following tips can help you configure
and use the behaviors more effectively.
• To rate behaviors, set the use-behavior attribute to true, the behavior-mode-opt attribute to 0, and
the behavior-rating-opt attribute accordingly. All scenarios are invalid if you set use-behavior to true
combined with behavior-mode-opt to 1, 2, 4, or 5.
• To show the mapped behaviors by job code only, set behavior-mode-opt to 1 or 2.
• To show all behaviors, set behavior-mode-opt to 4 or 5.
• If you've configured the settings to rate behaviors, behaviors are hardcoded to the form during form creation
and modification and they won't be updated, regardless of whatever value the lock-behavior-content
attribute may have.
• If you've configured the settings to only show behaviors, you can set lock-behavior-content to true to
hardcode the behaviors to the form.
• To rate behaviors with Rating Option 3 and also define required fields, configure Unofficial User Rating instead
of Subject Rating as the required field for employee self-rating. Therefore, required fields can work properly on
the form and the Incomplete Items pod.
You can configure the behavior-mode-opt attribute for customers to show behaviors in addition to
competencies but they still rate competencies.
Procedure
Value Description
Note
The use-jobcode attribute must be set to true.
Note
The use-jobcode attribute must be set to true.
Sample Code
You can configure the use-behavior attribute for customers to rate behaviors instead of competencies.
Context
Behaviors are shown under each competency and can be rated. Competencies can't be rated and their rating is
calculated based on the ratings of behaviors.
If users can rate behaviors, they can also add behaviors to the form. To achieve that, make sure that the
configurable attribute is set to true.
Value Description
4. Specify the behavior-rating-opt attribute to determine the rating options for behaviors.
Value Description
Note
You can find the DTD definition, attributes, and elements applicable to this section. This topic lists only the
attributes and elements that are commonly used. For more information, refer to the latest DTD file.
DTD Definition
<!ATTLIST summary-sect
index CDATA #REQUIRED
mgt-only (true | false) "false"
ask-4-comment (true | false) "false"
manual-rating (true | false) "true"
override-unrated (true | false) "false"
split-cmt (true | false) "false"
Attributes
Attribute Description
index A number that represents the display order of the section on the form, for example, 0, 1, 2, 3.
When you move sections using Provisioning, the index number assigned to a section will be updated
automatically to reflect how you’ve rearranged the sections in the form.
mgt-only Set to true if you want only managers and HR to view the section.
manual-rating Set to true to allow users to give an overall rating for the summary section.
If it's set to false, the calculated rating is the overall rating, fm-sect-scale is ignored, and users
aren’t allowed to override it.
• Set this value to false to define manual rating always as the overall rating.
• Set this value to true to define the calculated rating as the overall rating when the manual rating is
unrated.
• If the manual rating is unrated when the form is at the current step, then the overall rating won't be
overridden by the calculated rating.
• If the manual rating is unrated when the form is routed, then the overall rating will be overridden by
the calculated rating.
split-cmt
Set to true if you want the subject's and manager's comments to show side by side.
Note
In Performance Management, the attribute is always set to true.
rating-opt
Option values are 0 (default), 1, 2, and 3.
use-adjusted-scale- Controls how the overall section rating is displayed in the summary section. If using text-based ratings,
for-section-header- you can have subtotals using the same adjusted scale values defined in the meta section.
rating
• 0 (default): Displays the manual or calculated rating. For calculated ratings, there's only rating value
without rating label.
• 1: Uses the adjusted scale to display the adjusted rating label and value for the manual or calculated
rating.
• 2: Displays the original rating with the label defined in the adjusted scale.
Note
In Performance Management, the adjusted rating for goal or competency section isn't supported in
the summary section.
overall-rating-dis- The value is manual-calc. The manual rating is always shown above the calculated rating.
play-order
Elements
Element Description
fm-sect-config See Additional Form Section Configuration (fm-sect-config) for more information.
summary-rating Overall form rating. By default it's the calculated average rating of all sections included in
overall calculation.
unadjusted-overall-summary-rat- The original calculated form rating before any adjustments based on the adjusted scale
ing
overall-rating-label A non-zero-length string (including whitespace) will override the default Overall
Form Rating label. For example: <overall-rating-label><![CDATA[Overall
Ranking:]]></overall-rating-label>
calc-rating-label A non-zero-length string (including whitespace) will override the default Calculated
Form Rating label. For example: <calc-rating-label><![CDATA[Computed
Ranking (4 = 100%):]]></calc-rating-label>.
group-matrix-other-label A non-zero-length string (including whitespace) will override the default Other label.
show-gap-behaviors-in-summary The behaviors for each competency, if rated by behavior, are shown in the summary
section along with the gap analysis.
show-behaviors-in-summary The behaviors for each competency, if rated by behavior, are shown in the summary
section.
show-gap-competencies-in-sum- The gap analysis scale for competencies is shown in the summary section.
mary
allow-close-individual-gap-in-sum- If this element is added to the summary section, a clickable link will be available in the form
mary for each competency, to which users can add development goals.
Related Information
Configure Enforce Maximum Overall Score (EMOS) to set limitations on the rating that a specified role can give to
an employee.
Prerequisites
Hre is an EMOS example. For role EM, if the goal section's item rating is below or equal to 3.0, and the competency
section's item rating is below or equal to 4.0, then the maximum manual overall score cannot be greater than 2.0.
Procedure
1. In an XML form template, add the <enforce-maximum-overall-score> element to the summary section.
Sample Code
<enforce-maximum-overall-score condition='and'>
<role-name>EM</role-name>
<max-score>2.0</max-score>
</enforce-maximum-overall-score>
Note
• If no role is specified (role-name is *), the EMOS rule applies to all roles.
• Set condition to or if you want to trigger the EMOS rule when either of the conditions is satisfied.
2. In the goal section for which you want to configure EMOS, add the <emos-min-score> element.
Sample Code
3. In the competency section for which you want to configure EMOS, add the <emos-min-score> element.
Sample Code
You can find the DTD definition, attributes, and elements applicable to this section. This topic lists only the
attributes and elements that are commonly used. For more information, refer to the latest DTD file.
DTD Definition
<!ATTLIST objcomp-summary-sect
index CDATA #REQUIRED
mgt-only (true | false) "false"
comp-manual-rating (true | false) "true"
obj-manual-rating (true | false) "true"
comp-cal-rating (true | false) "true"
obj-cal-rating (true | false) "true"
split-cmt (true | false) "false"
rating-opt CDATA "0"
cmt-opt (0 | 1) "0"
cmt-max-limit CDATA "-1"
show-listing (true | false) "true"
show-ococ-rating (true | false) "false"
rating-mode CDATA "text"
show-9box (true | false) "true"
overall-rating-display-order (manual-calc | calc-manual) "manual-calc"
section-display-order (comp-obj | obj-comp) "comp-obj"
ococ-rating-calc-mode (matrix-lookup | avg | sum) "matrix-lookup"
pdf-page-break-opt (0 | 1 | 2) #IMPLIED
>
Attribute Description
index A number that represents the display order of the section on the form, for example, 0, 1,
2, 3.
When you move a section in Provisioning, the index number assigned to the section will
be updated automatically to reflect how you have rearranged the sections on the form.
mgt-only Set to true if only managers and HR should view the section.
comp-manual-rating Set to true if you allow the overall competency rating to be edited. Set to false if the
overall competency rating should be the calculated rating.
obj-manual-rating Set to true if you allow the overall goal rating to be edited. Set to false if the overall
goal rating should be the calculated rating.
comp-cal-rating
Set to true if the overall competency rating should be calculated and shown.
Note
If you set this attribute to true, the <sect-weight-4-objcomp-summary>
element shoud be configured in competency sections.
obj-cal-rating
Set to true if the overall goal rating should be calculated and shown.
Note
If you set this attribute to true, the <sect-weight-4-objcomp-summary>
element shoud be configured in goal sections.
split-cmt Set to true if you want subject's and manager's comments to show side by side.
cmt-max-limit Set to -1 if you want section comments not to have a maximum character limit. Set
to a value greater than -1 if you want section comments to have a specified maximum
character limit.
show-9box Set to true to enable the chart of goal and competency ratings.
overall-rating-display-order The value is manual-calc. The manual rating is always shown above the calculated
rating.
Note
To ignore weights in calculating the OCOC rating, you also need to set the
rate-by-adding-values attribute in the <sf-pmreview> element to
true.
Elements
Element Description
fm-sect-config See Additional Form Section Configuration (fm-sect-config) for more in-
formation.
comp-scale See Configuring Matrix Grid Rating Scales for more information.
obj-scale See Configuring Matrix Grid Rating Scales for more information.
scale-adjusted-matrix See Configuring Matrix Lookup Table for OCOC Rating for more informa-
tion.
x-axis The x-axis of the chart for either the overall goal rating or the overall
competency rating
y-axis The y-axis of the chart for either the overall goal rating or the overall
competency rating
comp-cal-summary-weight The weight of the calculated competency rating for calculating OCOC
rating by the average or sum method
comp-summary-rating-label The label of Overall Form Rating for competencies can be configured.
comp-cal-summary-rating-label The label of Calculated Form Rating for competencies can be configured.
obj-cal-summary-weight The weight of the calculated goal rating for calculating OCOC rating by
the average or sum method
obj-summary-rating-label The label of Overall Form Rating for goals can be configured.
obj-cal-summary-rating-label The label of Calculated Form Rating for goals can be configured.
Related Information
Context
The mapped score for the OCOC rating is determined based on the overall goal rating and overall competency
rating. For example, if the overall goal rating is from 1.0 to 1.49 and the overall competency rating is from 1.0 to 1.49,
the OCOC rating should be 1.0.
Procedure
Note
For the location where the element should be added, refer to the DTD Definition section in Goal
Competency Summary Section (objcomp-summary-sect).
Note
The <rating-label> element under <scale-adjusted-matrix> is used to define the label of OCOC
rating.
If you don't use the matrix lookup table for OCOC rating but want to change the OCOC rating label, set the
enable attribute of scale-adjusted-matrix from true to false.
Sample Code
You can find the DTD definition, attributes, and elements applicable to this section. This topic lists only the
attributes and elements that are commonly used. For more information, refer to the latest DTD file.
DTD Definition
<!ATTLIST perfpot-summary-sect
index CDATA #REQUIRED
mgt-only (true | false) "false"
perf-manual-rating (true | false) "true"
pot-manual-rating (true | false) "true"
cmt-opt (0 | 1) "0"
cmt-max-limit CDATA "-1"
show-9box (true | false) "true"
section-display-order (perf-pot | pot-perf) "perf-pot"
pdf-page-break-opt (0 | 1 | 2) #IMPLIED
>
Attribute Description
index A number that represents the display order of the section on the form, for example, 0, 1, 2, 3.
When you move a section in Provisioning, the index number assigned to the section will be
updated automatically to reflect how you’ve rearranged the sections on the form.
mgt-only Set to true if you want only managers and HR to view the section.
Elements
Element Description
fm-sect-config See Additional Form Section Configuration (fm-sect-config) for more information.
perf-scale See Configuring Matrix Grid Rating Scales for more information.
pot-scale See Configuring Matrix Grid Rating Scales for more information.
perfpot-matrix-grid-filter Use this element to determine who should be shown on the chart based on the filter
option at Succession Management. You have two filter options:
Sample Code
<perfpot-matrix-grid-filter filter-option="form-
subject">
<role-name>EM</role-name>
<route-step stepid="2"/>
</perfpot-matrix-grid-filter>
Note
This element doesn't check role names or route steps. It only checks whether the
filter is included into the performance potential summary section.
Related Information
The Customized Weighted Rating section displays the calculation details that arrive at the calculated form rating
and supports two overall scores: the calculated rating and the manual rating.
You can find the DTD definition, attributes, and elements applicable to this section.
DTD Definition
<!--
PM Customized Weighted Rating Section.
Attributes
Attribute Description
index The order in which sections are displayed in the form is con-
trolled by a section index number starting with index="0".
As a result, the form XML can list sections in any order. When
you move sections, the index number assigned to a section
is updated automatically to reflect how you've rearranged the
sections in the form.
mgt-only Set to true if only managers and HR should see this section.
Elements
Element Description
When you configure a miscellaneous form section, use the corresponding section element with a nested <fm-
sect> element.
Section Element
DTD Definition
<!ATTLIST fm-sect
Attributes
Attribute Description
mgt-only Set to true if you want only managers and HR to view the
section.
split-cmt
Set to true if you want the subject's and manager's com-
ments to show side by side.
Note
In Performance Management, the attribute is always set to
true.
Element Description
Note
• The review dates section uses <reviewinfo-
sect-name> for section name.
• The job description section uses <job-desc-
sect-name> for section name.
Note
• The review dates section uses <reviewinfo-
sect-intro> for section introduction.
• The job description section uses <job-desc-
sect-intro> for section introduction.
Related Information
The employee information section uses the <fm-element> element to show employee information, which comes
from the data elements in the employee table.
• USERNAME
• FIRSTNAME
• LASTNAME
Attribute Description
type
The data type of employee information, which should be 3
(text).
sync-until-completion By default, each data element displayed reflects the latest em-
ployee data at the time when the form is opened. You can
set this attribute to false to preserve the original employee
information when the form was created, regardless of data
changes after that.
• Manager
• Division
• Department
• Location
Elements
Element Description
ekey The text entered in this element should reflect the static name as listed in the first row of the user
import file.
ename This element should be left blank. It reflects the text that is associated with the field in the User
Directory Settings.
Example
Sample Code
<userinfo-sect>
<fm-sect index="1" mgt-only="false" split-cmt="false" cmt-opt="1">
<fm-sect-name><![CDATA[Employee Information]]></fm-sect-name>
<fm-sect-intro><![CDATA[]]></fm-sect-intro>
<fm-sect-config>
<rating-label><![CDATA[Rating]]></rating-label>
<rating-label-others><![CDATA[Rating]]></rating-label-others>
<default-rating><![CDATA[unrated]]></default-rating>
<hidden-strength-threshold>0.0</hidden-strength-threshold>
You can use the <fm-sect-config> element to configure additional section-level features. You can find the DTD
definition and elements applicable to this element.
DTD Definition
Element Description
rating-label The label of the official rating field. The default value is
Rating.
Note
This label can be configured to show as Rating by
{employee name} on the form. However, in the PDF and
print version, the label is always shown as Rating.
default-rating The label that is shown in the rating field if users haven't given
a rating. The value in reports is shown as blank.
unrated-rating The label of a special rating on the rating scale, for example,
Too New to Rate. Performance reviewers can select this rating
when they think it's too early to give a regular rating. This
value is not included in the calculation.
If the parameters are not met when the form is sent, a warning
message is displayed.
hide-weight-percent-sign The option to hide the percentage symbol (%) next to the
weight for items. This element can be applied to goal section,
competency section, summary section, and goal competency
summary section.
weight-total-option The option to show a warning or error message when the total
weight validation is not passed. The configuration is relevant
only if the <weight-total> element is also specified.
Note
If you use this option and don't allow ratings in forms,
make sure that no-rate is set to false and rating
fields are hidden from users. This is because forms must
be rated to account for weights, even if forms don't count
the ratings in.
publish-button-warning
field-publishing
rating-bar-color
Configure required fields in a specific step to require users to complete the fields before they send the form.
Procedure
1. In an XML form template, add the <required-fields> element under <fm-sect-config> in a specific
section.
2. Specify the role, field, step, and send action accordingly.
Subelement Description
If the field is a text or text area field, you can also specify
min-value and max-value.
<route-step> Step ID
<send-action> Action when required fields are validated. The following ac-
tions are supported.
In this example, managers are required to complete the item rating field in a specific step before they send the
form to next step.
Sample Code
<fm-sect-config>
<rating-label><![CDATA[Rating]]></rating-label>
<rating-label-others><![CDATA[Rating]]></rating-label-others>
<default-rating>Select a rating...</default-rating>
<unrated-rating>Unable to Rate</unrated-rating>
<hidden-strength-threshold>0.0</hidden-strength-threshold>
<blind-spot-threshold>0.0</blind-spot-threshold>
<required-fields>
<role-name>EM</role-name>
<field refid="item-rating" min-value="-1.0" max-value="-1.0"/>
<route-step stepid="phase3"/>
<send-action sendid="next_step"/>
</required-fields>
<num-decimal-places>2</num-decimal-places>
<publish-button-label><![CDATA[Publish Content]]></publish-button-label>
</fm-sect-config>
In this example, managers are required to complete a custom text field with no more than five characters in a
specific step before they send the form to the next step.
Sample Code
<fm-sect-config>
<rating-label><![CDATA[Rating]]></rating-label>
<rating-label-others><![CDATA[Rating]]></rating-label-others>
<default-rating>Select a rating...</default-rating>
<unrated-rating>Unable to Rate</unrated-rating>
<hidden-strength-threshold>0.0</hidden-strength-threshold>
<blind-spot-threshold>0.0</blind-spot-threshold>
<required-fields>
<role-name>EM</role-name>
<field refid="custom-element" min-value="1.0" max-value="5.0">
<ekey>target1</ekey>
</field>
<route-step stepid="manager"/>
<send-action sendid="next_step"/>
</required-fields>
<fm-sect-config>
<rating-label><![CDATA[Official Rating]]></rating-label>
<rating-label-others><![CDATA[Unofficial Rating]]></rating-label-others>
<default-rating><![CDATA[unrated]]></default-rating>
<hidden-strength-threshold>0.0</hidden-strength-threshold>
<blind-spot-threshold>0.0</blind-spot-threshold>
<section-permission type="hidden">
<role-name>*</role-name>
</section-permission>
<num-decimal-places>2</num-decimal-places>
<publish-button-label><![CDATA[Publish Content]]></publish-button-label>
</fm-sect-config>
<fm-sect-config>
<rating-label><![CDATA[Official Rating]]></rating-label>
<rating-label-others><![CDATA[Unofficial Rating]]></rating-label-others>
<default-rating>Choose One</default-rating>
<unrated-rating>Not Observed</unrated-rating>
<hidden-strength-threshold>0.0</hidden-strength-threshold>
<blind-spot-threshold>0.0</blind-spot-threshold>
<section-permission type="hidden">
<role-name>*</role-name>
</section-permission>
<num-decimal-places>2</num-decimal-places>
<publish-button-label><![CDATA[Publish Content]]></publish-button-label>
</fm-sect-config>
This is an example of customized comment labels for managers and employees at the item and section level.
<fm-sect-config>
<rating-label><![CDATA[Rating]]></rating-label>
<rating-label-others><![CDATA[Rating]]></rating-label-others>
<default-rating>Select a rating...</default-rating>
<unrated-rating>Unable to Rate</unrated-rating>
Note
You need to type ''' to get an apostrophe (') in the customized label output.
Use this element to associate a rating scale with a goal section, competency section or summary section.
DTD Definition
Attribute Description
Note
If a rating scale has more than 5 rating values, it can only
display as a dropdown list and cannot be changed to other
rating format.
Elements
Element Description
Related Information
Map rating scales to goal, competency, and summary sections so that users can give ratings on the form.
Context
By default, rating fields in goal and competency sections show the defined unrated rating and default rating, which
are not editable on the form. You must map rating scales to the sections respectively to enable ratings.
You can map only one rating scale to one section. If multiple rating scales are mapped to sections in one form,
ensure the rating scales have the same point scale.
1. To map a rating scale to a goal or competency section, add the <fm-sect-scale> element to <objective-
sect> or <competency-sect>.
Sample Code
2. To map a rating scale to a summary section, add the <fm-sect-scale> element to <fm-meta>.
Sample Code
<fm-meta>
<meta-form-id>-1</meta-form-id>
<meta-rated>true</meta-rated>
<meta-rating>0.0</meta-rating>
<meta-scale>0.0</meta-scale>
<meta-grp-label><![CDATA[Group]]></meta-grp-label>
<fm-sect-scale show-value="true">
<scale-id><![CDATA[Performance & Development Scale]]></scale-id>
<scale-type><![CDATA[null]]></scale-type>
</fm-sect-scale>
<meta-item-weight-floor-ceiling-option>warning</meta-item-weight-floor-
ceiling-option>
</fm-meta>
Reverse a rating scale so that the smallest number becomes the highest rating score.
Context
Generally in a rating scale the largest number is the highest rating and the smallest number the lowest. You can use
the reverse-scale attribute to reverse the order. Read the following notes when using a reversed rating scale:
• Reversed rating scales don't work with expected rating: Expected rating is a value that administrators set
for the competencies assigned to a job role. So, whenever an employee tries to rate a competency, a value is
shown below the rating that specifies the expected rating for that job role. The problem is the expected rating
won't be reversed together with the rating scale.
For example, if the expected rating for an individual competency is set to 20%, and the default 5-point rating
scale is used (1 being the lowest rating and 5 being the highest), then the normalized expected rating for this
scenario is shown as 1, which is considered as the lowest value. In this case, if the rating scale is reversed (1
being the highest rating and 5 being the lowest), the normalized expected rating will still be shown as 1, which is
now considered as the highest rating.
• Reversed rating scales don't work with star rating format: A reversed rating scale is always selected using a
dropdown menu.
• Reversed rating scales don't work with the chart in goal competency summary section: The goal
competency summary section calculates three ratings: an overall goal rating, an overall competency rating,
and an overall goal competency rating. These ratings are calculated as an aggregation of the ratings from all
the goal sections and competency sections to determine the quadrant in which an employee falls on the rating
chart. When a reversed rating scale is used to calculate these ratings, the quadrant doesn't change according
to the reversed rating scale.
Procedure
Sample Code
Note
If you use multiple rating scales in one form, ensure to reverse all the rating scales so that users don't get
confused or make accidental rating errors.
Configure scale adjusted calculation to adjust the calculated form rating to a fixed rating value, so that the
calculated form rating with a decimal can be shown as an integer with a rating description.
Procedure
Subelement Description
<score-min> The lowest possible rating of the calculated form rating that
will be adjusted to a fixed value. Example: 0.1
<score-max> The highest possible rating of the calculated form rating that
will be adjusted to a fixed value. Example: 1.49
<mapto-score> A fixed value to which the calculated form rating in the range
from <score-min> to <score-max> will be adjusted.
Example: 1.0
Sample Code
<fm-meta>
<meta-form-id>-1</meta-form-id>
<meta-rated>true</meta-rated>
<meta-rating>0.0</meta-rating>
<meta-scale>0.0</meta-scale>
<meta-grp-label><![CDATA[Group]]></meta-grp-label>
<fm-sect-scale show-value="true">
<scale-source>1</scale-source>
<scale-id><![CDATA[Performance & Development Scale]]></scale-id>
<scale-type><![CDATA[null]]></scale-type>
<scale-adjusted-calculation enable="true" display-calculated-
rating="false">
<rating-label><![CDATA[Overall Rating:]]></rating-label>
<default-rating><![CDATA[Unrated]]></default-rating>
<scale-map-value>
<score-min>0.1</score-min>
<score-max>1.49</score-max>
<mapto-score>1.0</mapto-score>
<mapto-desc><![CDATA[Below Expectations]]></mapto-desc>
</scale-map-value>
<scale-map-value>
<score-min>1.5</score-min>
<score-max>2.49</score-max>
<mapto-score>2.0</mapto-score>
You can find the DTD definition, attributes, and elements applicable to custom fields.
DTD Definition
<!ATTLIST fm-element
index CDATA #REQUIRED
type (1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10) #REQUIRED
checked (true | false) "false"
min CDATA #IMPLIED
max CDATA #IMPLIED
sync-until-completion (true | false) "true"
waca (true | false) "false"
>
Attribute Description
index A number that represents the display order of custom fields. The index of the first element
should be set to 0.
type The data type of custom fields. Each of the numbers from 2 to 9 represents a specific data
type.
• 2: Label
• 3: Text
• 4: Text area
• 5: Date
• 6: List
• 7: Integer
• 8: Double
• 9: Checkbox
checked This attribute is only applicable to checkbox. The value is true if the checkbox is selected
by default.
sync-until-completion This attribute is not relevant to custom fields but used in the employee information
section. See Employee Information Section (userinfo-sect) for more information.
waca This attribute is applicable to text area in competency sections. The value is true if
Writing Assistant is enabled for the custom field.
Elements
Element Description
ekey The key of custom fields. The value should always be one word and you can use mixed cases and
underscores.
The value must be unique for each custom field within the same form. Though using the same
value doesn't fail the form template validation, it may lead to unexpected issues and will cause a
problem in reporting.
ename The label of custom fields. Its length should be 128 characters or fewer. Otherwise, this will cause a
problem if any custom database reports need to be run on the data.
Note
If you use a checkbox type, you must specify the evalue such as True, Y, Yes. This is the value
that will be stored when users select the checkbox. If you don't specify a value, no value will be
stored in the database.
elist This element is only applicable to list. See Configuring a Custom Dropdown List Field for more
information.
Related Information
Configure a custom dropdown list field in an XML form template according to customer's business needs.
Procedure
Note
For the location where the element should be added, refer to the DTD definition of a specific section.
2. Specify the common attributes and elements of custom fields, for example, index, type, <ekey>, and
<ename>.
Note
Leave the <evalue> element blank if customers use one of the following scenarios:
• The Incomplete Items pod is used.
• The custom dropdown list field is configured with different access permissions for users.
3. Specify the <elist> element to define a data type and dropdown values.
a. Use the elist-value-type attribute to define the data type of the dropdown list.
Subelement Description
Sample Code
This is an example of a custom field that is displayed between each goal's description and rating in a goal section.
Note
When you define the custom field, it appears for each item and not just once in the section.
Learn about the form permissions for buttons, tabs, sections, actions, and fields in an XML form template.
Button Permissions <button- In the meta section XML Example: Button Button Permissions
permission> (<fm-meta>) Permissions [page 159] [page 70]
Tab Permissions <tab-permission> • To configure the XML Example: Tab Tab Permissions [page
Permissions [page 160] 73]
permissions at the
form level: In
the meta section
(<fm-meta>)
• To configure the
permissions at the
section level: In
available sections
Section Permissions <section- Under the <fm-sect- XML Example: Section Section Permissions
permission> config> element of Permissions [page 163] [page 74]
available sections
Action Permissions <action- In available sections XML Example: Action Action Permissions
permission> Permissions [page 163] [page 75]
Field Permissions <field- In available sections XML Example: Field Field Permissions [page
permission> Permissions [page 164] 76]
Example 1
In this example, employee is the only role who can't see the Get Feedback button in all steps.
<button-permission type="none">
<role-name>E</role-name>
<button refid="get-comments"/>
<route-step stepid="*"/>
</button-permission>
<button-permission type="none">
<role-name>E</role-name>
<button refid="get-edits"/>
<route-step stepid="*"/>
</button-permission>
In this example, manager is the only role who can see the Add Modifier button in all steps.
<button-permission type="none">
<role-name>*</role-name>
<button refid="add-modifier" />
<route-step stepid="*" />
</button-permission>
<button-permission type="enabled">
<role-name>EM</role-name>
<button refid="add-modifier" />
<route-step stepid="*" />
</button-permission>
Example 1
In this example, nobody can view the Goal Details, Other Details, and Achievements tabs in a goal section.
Example 2
In this example, only managers can view the Ratings from Others tab in all steps for available sections.
<fm-meta>
<meta-form-id>-1</meta-form-id>
<meta-rated>true</meta-rated>
<meta-rating>0.0</meta-rating>
<meta-scale>0.0</meta-scale>
<meta-grp-label><![CDATA[Group]]></meta-grp-label>
<fm-sect-scale show-value="true">
<scale-source>1</scale-source>
<scale-id><![CDATA[2005b]]></scale-id>
<scale-type><![CDATA[null]]></scale-type>
</fm-sect-scale>
<meta-item-weight-floor-ceiling-option>warning</meta-item-weight-floor-ceiling-
option>
<others-ratingtab-permission type="none">
<role-name>*</role-name>
<route-step stepid="*"/>
</others-ratingtab-permission>
<others-ratingtab-permission type="enabled">
<role-name>EM</role-name>
<route-step stepid="*"/>
</others-ratingtab-permission>
</fm-meta>
You can use the <others-ratingtab-item-permission> element at the section level to configure the field
permissions on the Ratings from Others tab. In this example, nobody can view the Item Rating field on the tab in a
goal section in a specific step.
Example 1
In this example, managers and employees can edit the section in all steps while other roles can only view the
section in all steps.
<section-permission type="disabled">
<role-name>*</role-name>
<route-step stepid="*"/>
</section-permission>
<section-permission type="enabled">
<role-name>EM</role-name>
<role-name>E</role-name>
<route-step stepid="*"/>
</section-permission>
Example 2
In this example, nobody can view the section in a specific step. You can look for the step ID in a route map.
<section-permission type="hidden">
<role-name>*</role-name>
<route-step stepid="7"/>
</section-permission>
Example 1
In this example, employees are not allowed to add or remove goals in any steps.
<action-permission type="none">
<role-name>E</role-name>
<action refid="add-item" />
<action refid="remove-item" />
<route-step stepid="*"/>
</action-permission>
In this example, nobody can add or remove goals while managers can do so.
<action-permission type="none">
<role-name>*</role-name>
<action refid="add-item"/>
<action refid="remove-item"/>
</action-permission>
<action-permission type="enabled">
<role-name>EM</role-name>
<action refid="add-item"/>
<action refid="remove-item"/>
</action-permission>
Example 1
In this example, everyone can at least view the Item Rating, Item Weight, and Item Group fields, managers can edit
the Item Rating and Item Weight fields, and employees can edit the Item Group and Item Weight fields.
<field-permission type="read">
<role-name>*</role-name>
<field refid="item-rating"/>
<field refid="item-weight"/>
<field refid="item-group"/>
</field-permission>
<field-permission type="write">
<role-name>EM</role-name>
<field refid="item-rating"/>
<field refid="item-weight"/>
</field-permission>
<field-permission type="write">
<role-name>E</role-name>
<field refid="item-group"/>
<field refid="item-weight"/>
</field-permission>
Example 2
In this example, employees can edit a specific custom field in all steps and everyone can view another custom field
in a specific step.
<field-permission type="write">
<role-name>E</role-name>
<ekey>target3</ekey>
Performance Management forms have many features that can improve user experience in performance reviews.
Learn about the features in detail and how to enable them.
The Add Modifier feature allows performance reviewers to include other users into the form review process at the
Modify stage.
After the users are added to the form, they will appear in the Route Map section on the form and be recorded in the
Audit Trail page. They will receive the form in their Inbox when the form is sent to the next step. They can provide
ratings and comments on the form, or access the form in Team Overview. After their review is done, they can send
the form forward to the next step without having to send it back to the user who added them to the route map.
When the form is completed, they will get a copy of the form in the Completed folder.
Configure your form template so that users can add modifiers on the form.
Procedure
Add Modifier is available to all users under the Actions dropdown in the Route Map section and at the bottom of
the form. It applies to the forms that have been already launched as well.
4. Optional: Define the add-modifier permission to control user access to the button.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
Related Information
When users do a performance review, if they want to let other users sign on the form, they can add those users as
signers. They can also remove them at the current step. When the form is routed to another step, if they want to
remove the signers that they added, they can open the copy of the form in the En Route folder and remove them.
Add Signer
When users add a signer at the Modify stage, the signer is added before the existing signers. The added signer is
the first one to sign the form. When users add a signer at the Signature stage, the signer is added after the current
signer. When the current signer routes the form to the next step, the added signer is the next one to sign the form.
When users remove signers, they can only remove the signers that were added by them. If they remove signers who
have received the form in their Inbox, the form is automatically routed to the next step. In the case when the form
has only one signer, we recommend that add the right signer before removing the wrong signer. So, the form is not
auto-completed when the only signer is removed.
Additionally, if signers have received the form in their Inbox and later are removed, admins can enable an email
notification to inform those signers. The email notification used is Removing Current Signer Notification. For more
information, see Configuring e-mail Notifications and E-mail Notifications in Performance Management.
Exceptional Cases
When users have added a signer to sign the form at different steps, if the form hasn't routed to the signer, removing
the signer will remove all the steps related to the signer. If the form has routed to the signer, users can choose to
remove the signer in the current step, remove the signer in other steps except the current step, or both.
When users remove a signer who owns the current step of the form and add a new signer, if the form is rejected at
the Signature stage, the form is routed back to the last step at the Modify stage. In the meantime, the route map
at the Signature stage doesn't refresh with the latest change. The previously removed signer appears again in the
route map.
Related Information
Configure your form template so that users can add and remove signers on the form.
Procedure
Add Signer and Remove Signer are available to all users. It applies to the forms that have been already launched
as well.
5. Optional: Define the add-signer permission to control user access to the buttons.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
Results
When the form is currently with users, they can choose the buttons:
When the form is routed to another step, they can choose the buttons in the Actions dropdown menu in the top
right of the form.
Related Information
With Outlook calendar integration, users can add a performance review to their Outlook calendar for personal
reminders.
When they choose Add to Outlook, an Outlook meeting request is generated. It contains form title, form link, and
form due date. Users can send the meeting request to themselves and later the calendar will remind them to do the
performance review.
Configure your system to allow users to add performance review reminders to Outlook calendar.
Prerequisites
Your company is using the latest version of Outlook for Office, Office 2010, 2007, and 2003 Outlook calendars.
Procedure
The Ask for Feedback feature is an integrated approach to solicit feedback from people through email. Managers
can send an email to one or more individuals asking for feedback, and the individuals can reply directly to the email
with their feedback.
Context
Effective and timely feedback is key to a successful performance review. If effective feedback is given to employees
on their progress towards their goals, employees are more likely to improve their performance. A multiperspective
set of feedback allows managers to provide a more balanced review that considers other people's points of view.
Feedback can come from many different sources: managers, supervisors, peers, and customers, just to name
a few. This feature allows people from outside the organization, who can't be added to a route map, to provide
feedback about an employee's performance.
Use
Managers can choose Ask for Feedback in Team Overview to select people and draft the email body for requesting
feedback, as shown in the following screenshot. They can ask the same person for feedback at multiple times,
as long as they send request emails on different days. When managers send a request email, they are cc'ed
automatically.
Messages Explained
In the Feedback from Others column in Team Overview, managers can see different messages under different
circumstances. The following table shows all the messages, when they appear, and whether they coexist with the
Ask for Feedback button.
Recommended Later Before the date range for collecting feed- Yes
back
Recommended Now Within the date range for collecting feed- Yes
back
You have requested feedback about {em- The manager has asked for feedback No
ployee's first name} from {n} people about the employee from one or multiple
people.
You chose not to request feedback about • The end date for collecting feedback No
{employee's first name} is past; and
• The manager hasn't asked for feed-
back.
For more information about setting the date range for collecting feedback, refer to Configuring Ask for Feedback.
Related Information
For managers to use Ask for Feedback, you need to set a date range in a form template for them to send request
emails.
Prerequisites
Disable Ask For Feedback functionality in Form Template Settings is not selected.
Procedure
The relative date can be set relative to the form creation date or the default form start date, end date, or due
date.
You can set the start date as 10 days after the form creation date and the end date as form due date.
3. Optional: Select Disable the external email address feedback option to ask for feedback from internal
employees only.
If you select this option, Add external Email address will not be available in the Ask for Feedback about
{employee name} popup window.
4. Choose Update Form Template.
By default, only the managers who have asked for feedback can view the feedback in the Supporting Information
pod on the form. You can allow other roles who have access to the form to view the feedback as well.
Context
The option to allow all roles to view feedback applies to new, in-progress, and completed forms. If you want to
further configure permissions for different roles, we recommend that you launch forms after configuration to apply
the permissions in new forms.
Procedure
If this option is selected, all roles in the route map of the form can view the feedback.
3. To configure permissions for different roles in different steps, go to Manage Templates General Settings
and choose 0 Ask for Feedback data in Supporting Information Pod Permission(s) defined. Click to modify.
The Ask for Feedback data in Supporting Information Pod Permission(s) popup window appears.
4. Select the permission type, roles, and route steps accordingly.
You can grant the None permission to all roles in all steps first and grant the Read permmission to some roles in
specific steps.
5. Choose Done and save the template.
The pods are shown at the top of the form, right beside the employee photo and name. From left to right in the
screenshot below are the Overall Score, Incomplete Items, Team Ranker, Supporting Information, and Gap Analysis
pods.
Note
The Team Ranker and Gap Analysis pods are for manager view only.
You can configure the permission for pods by configuring button permissions. For more information, see the topics
about configuring form permissions.
Related Information
The Overall Score pod displays the overall score of the ratings in the current performance review step. By choosing
the pod, users can view the detailed ratings of each section.
In the Modify stage, the pod is available to the current user when the following configurations are met:
The overall score is the calculated or manual overall rating based on users' rating permissions in the current step.
See the following table for details.
Item rating and unofficial user rating Calculated overall official rating
Note
If other than the above permissions, users have the permission to give a manual rating in the summary section,
the overall score is the manual rating.
In the Signature stage, if the user is granted with the permission to view the Overall Score pod, they can view the
overall official rating of the form. By choosing the pod, they can view the official rating of each item.
The Incomplete Items pod displays the number of incomplete items that users need to finish in the current
performance review step.
Before users send the form to the next step, the following required fields, if configured, are counted by this pod.
• Item comment
• Item rating
• Item weight
• Section comment
• Section weight
• Manual rating
The Team Ranker pod displays the ranking of an employee among their peers based on the overall form rating. By
choosing the pod, managers can view the full ranking list including the overall form rating of each direct report.
The overall form rating of other direct reports is from the latest Performance Management form based on the same
form template.
To show all direct reports who have the in-progress form in the pod, make sure that Start of Review is selected in a
route map step.
Related Information
The Supporting Information pod displays the number of feedback, notes, and attachments.
• Feedback: Users can view the feedback about the form subject provided through the Ask for Feedback feature.
For more information, refer to Ask for Feedback.
• Notes: Users can view the notes retrieved from the Notes block in People Profile. Notes are displayed with a
maximum count limit of 1000, and there's no filter on date range.
Employees for whom notes are created can view the notes only in their People Profile. Managers who create
notes for their employees can view the notes in this pod on employees' form.
• Attachments: Users can upload attachments to forms and download and delete attachments from forms.
Deleted attachments aren't accessible from the deleted section of the Manage Documents admin tool, because
they've been physically removed from the system.
You can configure permissions to manage attachments. For more information, refer to Configuring Permissions
for Attachments.
Related Information
The Gap Analysis Pod displays the number of items that have rating gaps between employees and managers. By
choosing the pod, managers can view individual items where such gaps exist.
To use this pod, make sure that there's a self-assessment step in the route map.
Change engine is used to define rules for document changes and transfer when the employee data is changed.
Settings are maintained for each change event and are applicable to the entire system.
Change engine allows you to set up rules that will trigger actions based on employee data changes, but the feature
is more often used to keep forms at the old manager's side. For example, when employee's manager is changed,
the old manager can provide final ratings and comments and move the form directly to completion.
Document transfer and change engine are parallel functions, which means when one is working, the other will be
inactive. The following flowchart illustrates how they work in cases of employee import.
Configure change engine rules, so that when the manager, matrix manager, or HR of employees is changed, change
engine will trigger actions for form changes.
Prerequisites
• Enable document transfer for Matrix Manager change and Enable document transfer for HR Manager change are
selected in the Cross Talent Feature Settings admin tool.
• Do Not Trigger Change Engine is not selected in Form Template Settings.
• All settings are disabled in the Automatic Manager Transfer admin tool.
• The permission of Change Engine Configuration under Administrator Permissions Manage System
Properties in Manage Permission Roles is granted.
Procedure
Note
Manager change refers to direct manager change. For matrix managers and HR representatives, select
Matrix Manager Change and HR Rep. Change respectively.
3. In Actions, select the following options that you want to apply when the change occurs.
Option Description
Auto complete old forms With this option selected, as soon as there's a change
in manager, a new step will be inserted into the route
map of the form and owned by the old manager. The
following configuration <freeze-user-to-role><!
[CDATA[true]]></freeze-user-to-role> will be
automatically added to the route map so that the old man-
ager can keep the form. In the newly added step, the old
manager can provide final comments and ratings and then
send the form to completion. All future steps will be skipped.
Disable autosync in old forms Autosync between goal sections in forms and goal plans
from Goal Management will be disabled.
Keep forms with old manager The old manager will keep forms for the ongoing perform-
ance review.
Note
Once this option is selected, the Auto complete old
forms option is not supported.
Send copy of old form to new manager on completion A copy of completed forms will be sent to the new manager.
In HR Rep. Change, you can also configure document transfer options for HR changes.
If you choose I'm Done, all changes are saved and you're back to Admin Center.
Instead of the system-wide settings of change engine, you can configure document change and transfer rules for
HR changes for a specific form template.
Procedure
Relevant options, grouped under Document Changes and Document Transfer, become active for this template.
3. Select the following options that you want to apply for the forms based on this template.
Results
When employee's HR is changed, if the forms are based on this form template, document changes and transfer are
triggered as configured.
Document transfer is used to transfer employee's forms from the old manager to the new manager when the
employee's manager is changed.
There are some occasions that require employee's performance forms to be transferred between managers, for
example, when the manager of a department is changed. Document transfer and related features can be used to
facilitate manual or automatic movement of forms between users.
Document transfer controls forms in the current step only. For example, only when forms are in the Inbox of the
old manager at the time of manager change does document transfer take effect. Here are some cases where
document transfer is not triggered as expected. For these cases, admins should manually route the form to the
next step using Route Form.
• If an employee's manager is changed from A to B and document transfer is not enabled yet, manager A keeps
the employee's form. Later if the manager is changed from B to C and document transfer is enabled, document
transfer is not triggered. This is because the form is not in manager B's form folder.
• If an employee's manager is deleted from the system and a new manager is added, document transfer is not
triggered.
To enable document transfer, the first step is to configure the document transfer settings in form templates. Then
you need to configure document transfer at the user data level in different tools, for example, user import tool. The
form template configuration will override the configuration at the user data level.
To enable the document transfer feature, first configure the document transfer settings in form templates.
Prerequisites
The settings are applicable for managers and matrix managers. Make sure that Enable document transfer for Matrix
Manager change is selected in the Cross Talent Feature Settings admin tool.
Procedure
Setting Description
Do Not Transfer Documents If selected, forms won't get transferred when manager is
changed regardless of any other settings you've configured
elsewhere.
Remember
It is for the current step only and doesn't affect future
manager steps. It only prevents forms from being trans-
ferred at the time of user import, which means that
the current user keeps the forms regardless of manager
changes. However, future steps will reflect the manager
changes.
Caution
If you've configured form permissions, for example, for
the EM role, and an employee's manager is changed,
though the old manager keeps the form, none of the
permissions for the EM role will be applied to the old
manager because they are no longer the EM role. There-
fore, configure this setting only when there are no more
manager actions to complete the form.
With this setting enabled, when the EP role (all matrix man-
agers) is changed during the iterative step for the EP role,
the matrix manager who currently reviews forms keeps the
forms. Meanwhile, the matrix manager reviewer list for the
future steps within the iterative step is updated according to
the latest changes.
Example
The EP role, EX1, EX2, and EX3 participate in an iterative
step of a performance review. Currently, EX2 is review-
ing the form. See the following table for the use cases of
EP role changes:
Note
EX2 remains on the
reviewer list when re-
viewing the form. Af-
ter the form is sent to
another user, EX2 will
be removed from the
list.
Update EX2 to EX4 EX1 > EX4 > EX3 > EX2
Note
EX2 remains on the
reviewer list when re-
viewing the form. Af-
ter the form is sent to
another user, EX2 will
be removed from the
list.
Automatic Manager Transfer > Automatic insertion of If selected, the new manager will become a part of the review
new manager as next document recipient if not already process and the old manager will be removed from account-
ability going forward.
• If the current step is a single manager step, a new step
with the same step name as the current one will be
added as the next step for the new manager.
• If the current step is a single step not for managers, a
new step named Document Transfer will be added as
the next step for the new manager.
• If the current step is an iterative or collaboration step,
no new step will be added.
• If the next step is already for managers, no new step will
be added.
However, if the next step is the first step in the Signa-
ture stage for managers, a new step named Document
Transfer will be added to the Modify stage for the new
manager.
The old manager will retain a copy of the form when the
form is moved to the new manager, but the copy will not get
updated with any new information.
Note
Do not enable this setting unless you want the new man-
ager to be the next reviewer in any cases. Consider our
tip and warning below:
• This setting may not make sense for the last few
steps of performance reviews. For example, when
the form is about to be moved to a signature step,
Automatic Manager Transfer > Automatic Inbox Docu- If selected, forms will be transferred from the old manager's
ment Transfer To New Manager Inbox to the new manager's Inbox.
The old manager will retain a copy of the form when the
form is moved to the new manager, but the copy will not get
updated with any new information.
Automatic Manager Transfer > Automatic En Route Docu- If selected, forms will be transferred from the old manager's
ment Transfer To New Manager En Route folder to the new manager's En Route folder.
The old manager will retain a copy of the form when the
form is moved to the new manager, but the copy will not get
updated with any new information.
Automatic Manager Transfer > Automatic Completed If selected, all completed forms of the employee will be
Document Copy to New Manager transferred from the old manager's Completed folder to the
new manager's Completed folder. The copy of the forms will
be sent to the new manager, and the old manager will retain
the original forms.
Automatic Manager Transfer > Hide Visibility After Docu- If selected, after forms are transferred to the new manager,
ment Transfer the forms will be hidden from the old manager.
Note
This setting is not supported for 360 Reviews forms.
Automatic Manager Transfer > Automatic Process Owner If selected, and the old manager is the process owner, also
Change To New Manager For In-Progress Documents known as the last Modify step user, of in-progress 360 Re-
When Old Manager is Process Owner (Only for 360)
views forms, the process owner will be changed to the new
manager.
Automatic Manager Transfer > Automatic Process Owner If selected, and the old manager is the process owner, also
Change To New Manager For Completed Documents known as the last Modify step user, of completed 360 Re-
When Old Manager is Process Owner (Only for 360)
views forms, the process owner will be changed to the new
manager.
After configuring the document transfer settings in form templates, you need to work in different tools to trigger
document transfer when an employee's manager is changed.
In addition to the following tools, you can also use OData API to update managers and specify document transfer
options. For more information, refer to Managing User API Options.
To trigger document transfer for HR manager changes in the system with Employee Central enabled, you can use
the following ways:
• Position Change, if cross-entity rules to update HR managers are configured. For more information, refer to
Cross-Entity Rules.
• Employee Data Import
• EmpJobRelationships OData API
• Job Relationship block in People Profile
Note
In the system with or without Employee Central enabled, document transfer isn't triggered when you update HR
managers through User OData API or the Basic User Information block in People Profile.
Configuring Document Transfer for Changing Managers in People Profile [page 191]
In a system without Employee Central enabled, if you change employee's manager or matrix manager in
People Profile, you can use Automatic Manager Transfer to set up central rules for document transfer.
You can use Employee Import, Manage Users, HRIS Sync, and more to import or update users and set up document
transfer options.
Note
If you update employee's
manager using the import
file but the employee's
new manager has not
been granted the User
Login role-based permis-
sion, forms will not be
successfully transferred
to the new manager even
though the import job is
completed.
Remember
As a customer, you don't
have access to Provision-
ing. To complete tasks
in Provisioning, contact
your implementation part-
ner or Account Executive.
For any non-implementa-
tion tasks, contact Prod-
uct Support.
Users .
HRIS Sync Yes When an employee's Job In- Human Resource Information
formation data is updated with System (HRIS) Synchroniza-
a new manager, on the Effec- tion
tive Date of the Job Info record
where the manager change
is made, the system will syn-
chronize the manager change
to basic user data and will
then transfer forms based on
the options you have enabled
in the HRIS Sync job.
Basic Import Yes You can trigger document Employee Data Import Proc-
transfer at the time of ess
importing employee data.
Configuring Additional Op-
Go to Admin Center tions with Basic Imports
Import Employee Data Basic
Note
If you use the Import Matrix Manager and Custom Manager Relationships admin tool to import matrix managers
and custom managers for Succession Org Chart, document transfer will not be triggered.
You can use Transfer Forms to New Manager to manually transfer in-progress, en-route, and a copy of completed
forms to the new manager after an employee's manager change.
Context
Procedure
The Transfer From Manager field will be populated automatically. If not, enter the username of the employee's
old manager.
3. Enter the username of the new manager in the Transfer To Manager field, and select Yes in Update Employee's
Manager Field to update the employee's manager.
Note
If you select No, manager will not be updated even though document transfer is triggered.
Option Description
Automatic insertion of new manager as next document The new manager will become a part of the review process
recipient if not already and the old manager will be removed from any accountabil-
ity going forward.
Note
This option is not supported for Performance Manage-
ment forms.
Automatic Inbox Document Transfer to New Manager All the forms in the old manager's Inbox will be sent to the
new manager's Inbox.
Automatic En Route Document Transfer To New Manager All the forms in the old manager's En Route folder will be
sent to the new manager's En Route folder.
Automatic Completed Document Copy to New Manager A copy of forms in the old manager's Completed folder will
be sent to the new manager's Completed folder.
Automatic Process Owner Change To New Manager For The process owner of in-progress 360 Reviews forms will be
In-Progress Documents When Old Manager is Process changed from the old manger to the new manager.
Owner (Only for 360)
Automatic Process Owner Change To New Manager For The process owner of completed 360 Reviews forms will be
Completed Documents When Old Manager is Process changed from the old manger to the new manager.
Owner (Only for 360)
In a system without Employee Central enabled, if you change employee's manager or matrix manager in People
Profile, you can use Automatic Manager Transfer to set up central rules for document transfer.
Prerequisites
Procedure
Option Description
Automatic Completed Document Copy to New Manager All the forms in the old manager's Completed folder will be
moved to the new manager's Completed folder.
Automatic En Route Document Transfer To New Manager All the forms in the old manager's En Route folder will be
moved to the new manager's En Route folder.
Automatic Inbox Document Transfer To New Manager All the forms in the old manager's Inbox will be moved to the
new manager's Inbox.
Automatic insertion of new manager as next document The new manager will become a part of the review process
recipient if not already and the old manager will be removed from any accountabil-
ity going forward.
Results
When employee's manager or matrix manager is updated in People Profile, document transfer is triggered as
configured.
When document transfer is triggered for matrix managers, forms are transferred to the primary matrix manager of
employees.
In the system that doesn't enable Employee Central, the first matrix manager that appears in the Employee Import
or Manage Users admin tool is identified as the primary matrix manager.
• If the primary matrix manager is changed, forms are transferred to the new primary matrix manager.
• If a non-primary matrix manager is changed or removed, or a new matrix manager is added, the primary matrix
manager keeps or receives forms.
• If the order of non-primary matrix managers is changed, or all matrix managers are removed, no document
transfer happens. The matrix manager who has received forms before the change keeps the forms.
You can also update employees' matrix managers using the related block in the People Profile. However, if
employees have more than one matrix manager, when you update the EP role in the block, document transfer
may not work as expected, so we do not recommend that you update the EP role using the block in the People
Profile.
In the system that enables Employee Central, currently, the primary matrix manager can't be identified. If
employees have more than one matrix manager, when you update the EP or EX role in the route map step
where the role reviews forms, document transfer is not supported. We recommend that you avoid changing matrix
managers in the step where the EP or EX role is assigned to review forms.
This example describes how to transfer Performance Management forms from the old manager's Inbox to the new
manager's Inbox when employees' manager is changed.
Context
You have launched forms for employees within a department to evaluate their last year's performance. The forms
have been sent to their manager's Inbox and displayed in To-Do and Team Overview. A personnel change occurs
and the manager of the department is changed, and therefore, the forms in the old manager's Inbox need to be
transferred to the new manager's Inbox.
Here is how you should configure the document transfer options to meet your needs:
1. Select Automatic Inbox Document Transfer To New Manager in Form Template Settings.
2. Launch forms and route the forms to the manager's Inbox.
3. Update the manager in the Employee Import admin tool. Make sure that Automatic Inbox Document Transfer To
New Manager is selected in the Import Users page.
You can also use other tools to update the manager. For more information, refer to User Import Tools [page
188].
Results
• When the new manager logs in to the system, the forms appear in their Inbox, To-Do, and Team Overview. On
choosing (Information), they find their name displayed in the Routing Map section of the form information
page.
• When the old manager logs in to the system, the forms are in their En Route folder instead of Inbox.
Enable the feature so that the Document Transfer and Change Engine issues caused by RBP refresh failures are
automatically fixed on a daily basis.
Prerequisites
You have the Administrator Permissions Manage System Properties Performance Management Feature
Settings permission.
Context
RBP refresh failures block form transfers. With a daily backend check and fix, the blocked processes resume
automatically. You no longer need to manually run the check No document transfer job requests are blocked due to
an RBP refresh failure and quick fix issues in Check Tool.
Note
When you enable the automatic fixing feature, if you've also enabled Document Routing Notification or
Employee Transfer Notification, users don't receive the email notifications about forms that have been blocked
Procedure
Related Information
You can enable email notifications so that users will receive emails when specific actions occur.
The following table lists email notifications used in Performance Management. For information on how to configure
email notifications, refer to Related Information.
Note
If you enabled Enforce start date in Manage Route Maps, make sure you've created a Send Schedule Emails job
in Provisioning in order for the email notifications to be sent out.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
Note
It works only when the
signer is removed from
the form. Removing sign-
ers in the Modify Form
Route Map admin tool
doesn't trigger the email
notification.
Note
The form due date is
set in Form Template
Settings or when a form is
launched.
Note
The form due date is
set in Form Template
Settings or when a form is
launched.
In the email body, tokens are used to populate data from forms into the email text. The following table lists
common tokens used in Performance Management.
Token Definition
[[SIGNATURE]] Signature
Note
• If this token is not configured in the email body, users
can't see the Email Notification Comments box when
sending the form to the next step.
• If the form sender and the form recipient are the
same person, though this token is configured in the
email body, users can't see the Email Notification
Comments box when sending the form to the next
step.
• The comments generated by the system, for example,
"Skipped on behalf of {user}", can't be translated.
[[NO_OF_DAYS]] The number of days between the current date and due date
[[EMP_USER_ID]] Subject's ID
Related Information
You can customize email notification settings for one or more form templates, including enablement, consolidated
email notifications, and additional recipients.
Context
Procedure
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
For example, if you choose 24 hours as the interval for Document Routing Notification for a form template,
every 24 hours users will be notified of all the forms based on this form template that have been routed in
the last 24 hours.
Related Information
It can be used in goal sections and competency sections. It shows employee self-ratings and manager ratings in
parallel and provides a gap analysis chart. If an employee self-rating is higher than a manager rating, the gap is
highlighted in red in the chart; and if a manager rating is higher than an employee self-rating, the gap is highlighted
in green in the chart.
Recommendation
• If you use EZ Rater, we recommend that you use rating option 3. Employee self-ratings and manager ratings
can be shown side by side, and the rating gap will be shown in the gap analysis chart.
If you use other rating options, only official ratings are shown in the collapsed view and the gap analysis
chart is unavailable. If users don't have read or write permission for official ratings, no rating is shown in
the collapsed view. If users have permission for unofficial ratings, when they expand the view, they can see
rating information.
• If you've configured a rating scale with more than one digit, for example, "50: Primarily meets
expectations", "100: Meets requirements", and "150: Exceeds requirements", the numbers may overlap
in the gap analysis chart. Therefore, we recommend that if you are using the rating scale with more than
one digit, do not enable EZ Rater.
Note
When EZ Rater is enabled, the rating labels of official rating (item-rating) are defined differently for the form
and the PDF and print version.
• For the form, the label is defined by FB_UI_SPEED_RATER_OFFICIAL_RATING (for the employee view),
split_rating_title_format_no_colon (for the manager view), and TEXT_BY_USER in the language
package. It's shown as Rating by {manager name} for managers and Official Rating for employees and other
users.
• For the PDF and print version, the label is defined by <rating-label> in XML.
To keep the rating labels consistent on the form and in the PDF and print version, make sure that the definitions
in the language package and XML are consistent.
Context
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
1. In an XML form template, set the sect-mode attribute of a goal section or competency section to EZ-Rater.
2. Set the ez-rater-expand-all attribute to true or false.
If it's set to true, all goal details or competency details are expanded by default. If it's set to false, all details
are collapsed by default.
3. Optional: To disable the gap analysis chart, add <ez-rater show-gap="false"/> under the <fm-sect-
config> element.
4. Optional: To show manager ratings before employee self-ratings, go to Admin Center Form Template
Settings and select Show Manager Rating first for EZ Rater mode.
The system automatically saves Performance Management forms if users don't save the form in a minute.
Additionally, the system triggers form autosave when users leave a form, for example, users choose Back to: Inbox,
Team Overview, (Go to Home Page), or close the tab or browser. Meanwhile, a message is popped up to remind
users that they probably lose changes after leaving the form.
• When users choose buttons on the form, for example, Actions Info about this form , the form is
automatically saved, but there's no reminder message.
• When users choose Cancel on the form, there's no autosave or reminder message. Any changes that have been
autosaved won't be canceled.
When a session is going to expire in the system, the session timeout message is popped up to remind users. At that
point,
• If the form has any unsaved changes, the form is automatically saved and the session keeps working without
the message.
• If the form doesn't have unsaved changes, there's no form autosave and the message is popped up as usual.
Recommendation
To make sure that form autosave works properly, don’t use Safari to edit forms.
Users can get an overview of form history, including all ratings and comments.
After users open a form, by choosing History Performance form history in the top right of the form, they can
access all form records of the form subject. In a separate window called SuccessFactors Business Execution Suite
Reviews, they can specify the form start and due date to search for forms.
The Document List section shows completed forms by default. Users can select Include In-Progress Documents to
search for in-progress forms. By choosing the form title, they can view a copy of the form in the section below.
Note
If you want to disable user access to form history, select Disable Form button in Form Template Settings.
Users can know the basic information about a form, step status, current step owner and more on the Form
Information page.
Note
If you want to disable the access to the page, select Disable Info button in Admin Center Form Template
Settings .
• Route Map, which is the same as the one shown in the form
• Properties, including form originator, subject, due date, and document ID
• Approval Chain, including:
• Routing Map, a table listing the type, stage, employee, name, and status of all the steps of the form
• Audit Trail [page 206]
Audit trail is shown as a table in the Form Information page. It records the changes that users made to a form in
different steps and highlights the user to whom the form has currently been routed.
Entries in the audit trail are only created when a form moves from one step to the next, for example from step 1 to
step 2. They won't be created if the step is an iterative step where the involved employees are only moving the form
back and forth between themselves.
Currently With
The Currently With column shows (arrow) to indicate the current step of a form.
Employee
The Employee column shows the step owner of the form.
Status
The Status column shows the step status, including Not Started, In Progress, and Completed.
Act By
The Act By column shows the step completed date.
If you don't want the comments to be stored and displayed in the audit trail, select Do not store sender's comment
on workflow action in Admin Center Company System and Logo Settings .
Note
• Even though neither of these options is selected, users who have updated the form in a step can always see
a link to that step.
• If users don't have permissions to a step, they can't view that step.
• There's no link for the Create action.
The following table lists the actions on the form and corresponding values in the audit trail.
Move a form to another step on behalf of a user in Route Form Manual Modify
Move a form from a signature step to another step on behalf of Manual Sign
a user in Route Form
Route a form automatically on the due date of a signature step Auto Sign
You can report on audit trail records of form completed steps by using the Audit Trail table in the Performance
Management schema in Story reports. Reportable details include step owner, step action, date time when a step
was completed, and system or user comments. You can further join the Audit Trail table with the Next Route Step
and Previous Route Step tables in the Route Entry schema to report on the previous or next step information of an
audit trail record.
With Get Feedback, performance reviewers can send an entire form to someone outside the route map to collect
both ratings and comments, or comments only.
After the form is sent to a specified participant, the form will appear in their form Inbox. Their comments are not
anonymous, and their name will be shown on the form as well.
The following table compares Get Feedback and Ask for Feedback.
How many people can you send a request One individual Up to 30 people
to at one time?
How do participants provide feedback? Directly on the form By replying to the email
Note
Use
The Get Feedback button appears under the Actions dropdown in the Route Map section and at the bottom of
the form, as shown below. When you choose the button, you can search for the participant and select the type of
feedback that you want them to give.
Configure your form template so that users can use Get Feedback on the form.
Context
Procedure
Option Description
Disable Ask For Comment Routing Users can ask others to give comments only.
Disable Ask For Edit Routing Users can ask others to give ratings and comments.
Note
If the form template uses Rating Option 3, which allows
only the employee and their manager to give ratings,
people who're invited to give feedback can give com-
ments only.
In competency sections, users can view the last competency rating, which is the most recent rating that employees
have received for a competency.
Based on your configuration, the last competency rating is from either of the following:
• Forms based on a specific form template: If a form includes the same competency as in the current form,
after the form is completed, the competency rating will be shown in the Last Rating tab of the competency in
the current form. Users can also open the Previous Form link to view the completed form in detail.
Note
• In in-progress forms, the last competency rating is populated from the latest completed form. In
completed forms, the rating is no longer updated.
• If rating by behavior is enabled, the last competency rating will be the calculated competency rating.
Users can open the previous form to see detailed behavior ratings.
• Rating sources in Job Profile Builder: The rating sources include official ratings from Performance
Management forms and ratings from self-assessment forms used in Career Development Planning. For more
information on self-assessment forms, refer to Enabling Self-Assessment for Role Readiness.
The most recent rating of a competency stored in the selected rating sources, along with the rating date and
source, is shown in the Last Rating tab of the competency.
Note
The last competency rating can also be prepopulated to rating fields, including official and unofficial ones.
Users can then modify the rating as necessary. If a form has multiple reviewers, only the first reviewer sees the
prepopulated rating. If the reviewer gives "Too New to Rate" or no rating for a competency, each time they open
the form before sending it to the next step, the last competency rating is prepopulated.
Note
• If the last competency rating after rating normalization doesn't match a value in the rating field, it's
mapped to the closest value when being prepopulated to the field.
• The rating will be updated according to the latest records in rating sources, so it may change from time
to time during the performance review process.
• If a competency was rated in the last performance review as "Too New to Rate" or any other label
defined in the form template, it's considered as the last competency rating.
• If a competency was unrated in the last performance review, the most recent rating of the competency
is considered as the last competency rating.
• If the rating scale of the last competency rating is different from that of the current form, the rating will
get normalized.
• When users add competencies to the form during review, they don't see the last competency rating
immediately. To see the rating, they should save and close the form and reopen it.
By default, all users can view the last competency rating, if available, in the Last Rating tab. You can configure tab
permissions to enable or disable the access. For more information, refer to Tab Permissions.
Related Information
Configure form template settings to display the last competency rating from forms based on a specific form
template.
Procedure
Configure form template settings to display the last competency rating from rating sources in Job Profile Builder.
Prerequisites
Procedure
The Legal Scan tool checks for any improper or discriminatory language in the comment fields of a form.
Legal Scan examines comments and highlights potentially improper words in red. When users choose the
highlighted words, Legal Scan displays suggested actions or alternative terminology. It doesn't replace the
highlighted words, but alerts users to alternatives. Users can choose to change the existing words based on the
suggestions.
Users can scan the entire form at once or scan a specific field of the form.
• To scan the entire form at once, choose Actions in the top right of the form and select Legal Scan the entire
form.
• To scan a specific field, choose (Run Legal Scan on the text you input here) in the toolbar of the field.
To use Legal Scan, you need to enable the feature both in Provisioning and a form template.
Prerequisites
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Procedure
Context
SAP SuccessFactors provides you with a basic Legal Scan library that contains common controversial terms. You
can use the library as is, or add other terms that your company deems controversial.
Procedure
• If the term exists in the library, modify the suggested term in Suggestions and choose Save entire form.
• If the term doesn't exist in the library, enter a suggested term in Suggestions and choose Save entire form.
Next Steps
If you have multiple terms, you can upload a file that contains all your terms using Legal Scan Library Import.
Out of Turn Access (OOTA) allows users to access a copy of forms from Team Overview before the forms officially
reach them.
You can enable OOTA only for the steps that follow the starting step of the form review. For example, the form
review starts with the Self Assessment step, and therefore, OOTA can be enabled for the steps following the Self
Assessment step.
To use OOTA, users can go to Team Overview and choose Review {employee} under their step. They will be directed
to an open form where they can give ratings and comments. When the form is routed to their step, they can review
the ratings and comments they've left before.
Managers can also use Stack Ranker with OOTA enabled. All competency ratings and comments given by them
in Stack Ranker are saved. To allow using Stack Ranker with OOTA enabled, make sure that the use-behavior
attribute in the competency section in an XML form template is set to false.
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
• If a route map includes two steps for the same role, for example, manager, even though both steps are enabled
with OOTA, managers can use OOTA only in the first step. However, we do not recommend that you enable
OOTA for the step whose role is also involved in another step in the route map.
• If the current step is an iterative or collaboration step and involves the role - for example, manager - who is
granted with OOTA permission in a future step, managers can't use OOTA for now. When the form is routed to
the next step in which managers are not involved, they can then use OOTA.
• If a step with OOTA enabled is skipped because the form is routed one step forward or back, the ratings and
comments provided using OOTA will still appear on the form.
Limitations
During document transfer, the ratings and comments provided by the old manager are only available when the
new manager views the form in the employee's Inbox. They will get deleted once the form is routed to the new
manager's Inbox.
Note
Since the form is in the E step, though the old EM has given ratings using OOTA, the rating is displayed as
unrated.
When the form is routed to the new EM, that is, in the EM (OOTA) step, the ratings and comments provided by
the old EM get deleted, as shown below.
Note
If a route map includes two EM steps with OOTA enabled for the first EM step but not for the second EM
step, and a manager change takes place in the first EM step, the old EM's ratings and comments are not
saved. If a manager change takes place in the second EM step, the old EM's ratings and comments are
saved.
The rules above apply both to manager changes and matrix manager changes.
To allow users to use the Out of Turn Access (OOTA) feature, you need to configure the route map of forms to grant
the permission to them.
Prerequisites
• The Start of Review option is enabled in a step that precedes the step for which you want to enable OOTA.
• The permission of Team Overview Access under Performance in Manage Permission Roles is granted to the
users.
Procedure
Results
After you launch forms that use this route map, users who have a role involved in the step can use OOTA.
The Spell Check tool helps make sure words entered as comments in a form are correctly spelled.
Users can check the spelling for the entire form at once or for a specific field of the form.
• To check the spelling for the entire form at once, choose Actions in the top right of the form and select Spell
Check the entire form.
• To check the spelling for a specific field, choose (Run spell check on the text you input here) in the toolbar of
the field.
Spell Check doesn't work for other areas of the form, such as goal titles and descriptions. The goal fields are
not editable in the form. Users can use the Edit Goal dialog box to edit goals and then use Spell Check to flag
words that are not spelled correctly.
To use Spell Check, you need to enable the feature both in Provisioning and a form template.
Prerequisites
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Procedure
Procedure
Stack Ranker allows managers to quickly review the competency ratings for their direct reports and to visualize
how the employees compare with, or stack up against, one another.
If direct reports have in-progress forms based on the same form template, managers can review their competency
ratings at one time and quickly identify top and low performers.
For Performance Management forms, managers can access Stack Ranker in Team Overview, as shown below.
For 360 Reviews forms, managers can access Stack Ranker in the Competency section, as shown below.
In Stack Ranker, a list of employees and their competency ratings are displayed. You can use the features
highlighted in the screenshot below.
The type of rating fields used in Stack Ranker depends on the rating scale and form template configurations.
• If a rating scale has more than seven rating levels, the dropdown list is used.
• If rating values are not integers from 0 to 9, the dropdown list is used.
Learn about the recommendations for and limitations of using Stack Ranker.
Recommendations
Route Map
Set up a simple route map with a single modification step for the EM role and no signature step, so that managers
get a quick and easy way to stack rank their team. If you configure steps before the EM step, make sure that
automatically routing forms on the due date is enabled in the route map, so that managers can receive forms at
once.
Competency Type
Though Stack Ranker supports job-specific competencies and custom competencies, we recommend that you use
custom competencies, so that all direct reports have the same number of competencies to be reviewed.
Competency Weight
Though competency weights can be included in the rating calculation, the weights are not shown in Stack Ranker
and managers may find it difficult to understand how the ratings are added up. Therefore, we do not recommend
that you use the weight function in Stack Ranker.
If you want the overall competency rating to appear on the form, include a goal competency summary section.
If managers do have to use both Stack Ranker and Calibration in performance reviews, we recommend that you use
them in two separate steps. In the manager rating step, managers do mass ratings using Stack Ranker. After forms
are mass routed to the calibration step, ratings provided in the previous step are updated in calibration sessions.
Disable Stack Ranker in the calibration step to not allow managers to adjust ratings in this step.
Limitations
• If managers are involved in performance reviews with different route maps, or there is a manager change, they
may see people who are not their direct reports in Stack Ranker.
• Forms can't be mass routed to the next step.
• Rating behaviors is not supported.
• Collaborative steps are not supported.
• Comments for competency items or sections can't be printed out.
For managers to use Stack Ranker, you need to enable the feature both in an admin tool and a form template.
Prerequisites
The permission of Performance Management Feature Settings under Manage System Properties is granted.
Procedure
1. In Admin Center, go to Performance Management Feature Settings and select Stack Ranker for Performance
Management.
As an implementation partner or Product Support, you can choose to select the option in Company
Settings in Provisioning.
2. Optional: To allow users other than direct managers to access Stack Ranker, for example, matrix managers and
second-level managers, select Stack Ranker for Performance Management- Enable display of all forms but self.
3. Choose Save.
4. Go to Manage Templates and open a form template.
5. Choose General Settings and select Allow managers to stack rank employees on competency sections.
6. Select any of the following options.
The configuration applies to all in-progress forms based on this form template.
You can replace the Stack Ranker label with a customized text in English, Spanish, and Canadian French.
Procedure
When users send the form to the next step, a reminder message pops up and they can decide whether they want to
review the form or move it forward.
If users send the form to another user within the same step, the reminder doesn't pop up. For example, users send
the form in iterative steps, or they get feedback or recall feedback in the current step.
If you've defined an exit user in collaboration steps, only the exit user receives the reminder. Otherwise, the
reminder pops up to all users in collaboration steps when they exit their current step.
Configure a route map setting to allow users to receive a reminder in a specific step.
Context
You can enable the feature at the Modify and Signature stages.
Procedure
Team Overview is used by managers to organize and conduct their team's performance reviews. It also provides a
one-stop status summary of the performance review of all their reports.
Managers who have the permission of Team Overview Access under Performance can access Team Overview. It's a
dedicated tab in the Performance module, as shown below. There's no specific permission such as field and section
permissions within Team Overview.
Note
Before granting the Team Overview access permission to managers, make sure that Enable Team Overview
Access Permission is selected in the Performance Management Feature Settings admin tool.
As a manager, you'll immediately notice any pending actions on the forms of your reports. Only the forms that
have enabled the Start of Review step in the route map are available in Team Overview. For more information, see
Creating a Route Map.
• You can select a type of reports and focus on the employees for which you want to review the performance
summary. The options available for you depend on your role in the performance review. You can choose Select
all to view the performance summary of all the employees reporting to you.
• Direct Reports: Shows you the performance summary of your direct reports.
• Indirect Reports: Shows you the performance summary of your indirect reports.
• HR Reports: Shows you the performance summary of your HR reports.
• Matrix Reports: Shows you the performance summary of your matrix reports.
If you participate in the performance review as a role other than EM, EMM, EH, or EX, for example, EA role,
you can't filter the employees of your relevant reports.
Reports you see in Team Overview depend on the route map of forms. If you're a step owner in the route
map, but no longer an employee's manager, the employee's form is still available in your Team Overview.
On the contrary, if you choose the My Direct Reports option in form Inbox, you see the forms of your direct
reports based on the current org chart.
• Team Overview shows all the steps of the performance review in one area. In a specific step, you can choose
a button to complete the pending action in the step. For example, you can choose Review {employee name} to
give ratings and comments on the employee's form, choose Confirm 1:1 Meeting to confirm that the meeting
with employees to discuss performance review results has finished, and choose Sign to sign the form.
• Team Overview shows each step's ratings directly on the page. Two kinds of ratings may be available in each
step cell: one is the official rating shown as Rating of Record and the other is the unofficial rating shown as
User Rating. If the goal competency summary section or performance potential summary section has been
configured, you can hover the mouse over in the bottom right of the cell to view ratings.
Note
If manual rating and scale adjusted calculation have both been enabled for the summary section, Team
Overview displays the manual rating rather than the adjusted rating.
If numeric rating values are hidden from the form, note the following cases where Team Overview still
shows numeric rating values.
• Manual rating is enabled and calculated rating is an integer or a decimal number.
• Manual rating is disabled and calculated rating is a decimal number.
• Manual rating and scale adjusted calculation are both enabled, and calculated rating is a decimal
number. In this case, only User Rating is shown as numeric rating values.
Tip
If ratings are not wanted, admins can select Display check mark instead of rating in Team Overview in Form
Template Settings.
• You can ask for feedback about employees from other users. For more information, see Ask for Feedback.
• You can stack rank the competency ratings of your direct reports. For more information, see Stack Ranker.
Limitations
• If the form template is changed after forms are launched, Team Overview may not work properly. For example,
if some sections are removed from the template, the Team Overview page may keep loading.
• When document transfer is triggered, even though the old manager hasn’t rated the employee, the old
manager's rating appears in Team Overview.
Writing Assistant provides complete sentences so that users don't have to type comments on their own. They can
add as many sentences as they'd like. Once those sentences are in the form, they can modify them to better match
their own writing style, or leave them as they are.
Use
When users choose Writing Assistant for a specific competency, a dialog box appears as follows.
1. In Select topics below, select the level of behavior that best describes the employee's competency.
2. In Describe Behavior, select a narrative.
Writing Assistant supports three narratives:
• First person: Sentences that often start with I, for example, I am a team player.
• Second person: Sentences that often start with You, for example, You are a team player.
• Third person: Sentences that often start with a named person, for example, Richard is a team player.
The narratives available to a particular user are determined by the user's role. Employees, as the subject of
the form, can use the first and third person. Other users, for example managers, can use the second and third
person.
The narrative choices can't be hidden or removed. If users don't wish to provide sentences in a certain
narrative, they can ignore that narrative.
3. In Give Advice, select the suggestions to support evaluation comments and choose Place Quote.
4. Based on the predefined sentences, change the tone of the sentences to make them sound more positive or
less positive, to better emphasize one's own perspective.
Note
To ensure that Writing Assistant works properly, users' first name must be maintained in the system. For more
information on managing user information, refer to the Managing User Information Guide.
If Job Profile Builder is used, the Writing Assistant content can be managed in Manage Writing Assistant and
Coaching Advisor. For more information, refer to Adding Writing Assistant and Coaching Advisor Content from
the UI.
Related Information
To use Writing Assistant, you need to enable the feature both in Provisioning and a form template.
Prerequisites
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Overview
• Overall Ratings
• Form Rating from Section Ratings (Summary)
• Overall Objective Rating from Goal Section Ratings (ObjCompSummary)
• Overall Competency Rating from Competency Section Ratings (ObjCompSummary)
• Overall Calculated Objective Competency Rating (ObjCompSummary)
• Overall Customized Weighted Rating (customizedWeightedRatingSection)
• Section Rating from Item Rating
• • Objective Section
• Competency Section
• Competency Rating from Behavior Ratings
• Calculated Objective Rating with MLT (on Total Goal Management)
The default XML for rating scale configuration in form template is as follows:
<fm-sect-scale show-value="true">
<scale-source>1</scale-source>
<scale-id><![CDATA[5pt]]></scale-id>
<scale-type><![CDATA[null]]></scale-type> ---- As per the comment on PMU-290, PMU
doesn't support BAR, RADIO, FREETEXT scale types
</fm-sect-scale>
Customized rating map based on calculation (adjusted calculation) also can be configured for rating scale <fm-
sect-scale> as below:
When the rating is 'Explicit Unrated', such as "Too New To Rate", then: <unrated-rating><![CDATA[Too New
To Rate]]></unrated-rating>
Provides you information on section weights, item weights and competency/objective summary weights.
Section Weight
<meta-item-weight-floor-ceiling-option>warning</meta-item-weight-floor-ceiling-
option>
objective-sect / competency-sect:
<weight-total><![CDATA[100.0]]></weight-total>
<hidden-strength-threshold>0.0</hidden-strength-threshold>
<blind-spot-threshold>0.0</blind-spot-threshold>
<item-weights>
<item-weight-floor>10.0</item-weight-floor>
<item-weight-ceiling>70.0</item-weight-ceiling>
</item-weights>
<weight-total-option><![CDATA[warn]]></weight-total-option>
Note
If you set no-weight as false in a section but do not assign any weight to each item, then the overall
calculated section rating will be 0.
These two summary weights are used in OCOC calculation when ococ-rating-calc-mode is "avg" for
Competencies and Objectives. They are invisible to end user.
objcomp-summary-sect:
<comp-cal-summary-weight><![CDATA[40.0]]></comp-cal-summary-weight>
<obj-cal-summary-weight><![CDATA[60.0]]></obj-cal-summary-weight>
• Overall Form Rating: meta-form-rating-calc: Use this element to select the rating calculation method at
the form level. This shows overall calculated rating in summary section.
<fm-meta>
...
<meta-form-rating-calc><![CDATA[sum]]></meta-form-rating-calc> ----"avg",
"sum" can be configured
...
</fm-meta>
Note
• OCOC Rating: ococ-rating-calc-mode ---- "avg", "sum", "matrix-lookup": Use this attribute to specify the
method of calculating the overall rating for the objective competency summary section.
ococ-rating-calc-mode="sum"
Refer, Calculation Process [page 233] for information about the processes involved in rating calculation.
• Section: section-rating-calc: Use this element to select the rating calculation method at the section level.
<fm-sect-config>
...
<section-rating-calc><![CDATA[sum]]></section-rating-calc> ----"avg",
"sum" can be configured
...
</fm-sect-config>
Note
• Competency: section-item-rating-calc: Use this element to select the item rating calculation method at
the section level.
<fm-sect-config>
...
<section-item-rating-calc><![CDATA[sum]]></section-item-rating-calc>
----"avg", "sum" can be configured
Note
Normalization
Rating normalization occurs when source scale is different from target scale. It typically is used for calc-
type="avg".
Steps
Example
Calculation Formula
Average
Sum
Note
Rating 1, Rating 2, etc may/may not be normalized based on the caclulation type and the rating being
calculated. We should update it to be consistent.
Friendly
Two dimensional lookup based on the lookup map configured in OCOC section. The rule for OCOC rating
calculation based on matrix look up table:
• If both Competency rating and Objective rating are EXPLICIT_UNRATED (too new to rate), the result is
EXPLICIT_UNRATED.
• If either Competency rating or Objective rating is NOT_APPLICABLE, the result is NOT_APPLICABLE.
• If we cannot match value in matrix look up table, then return NOT_APPLICABLE.
• Else, return the matched value in matrix look up table.
Round of Rating
Rounding happens after every calculation. The rounded value is used for subsequent calculation.
The overall customized weighted rating is calculated based on ratings from each role and the weights set for steps
and roles in the route map of a Performance Management form. The overall form rating given at each step is part of
the form's final score.
Only the overall form ratings given in the official rating field are included in the calculation of the overall customized
weighted rating. Since the employee is assigned to the unofficial rating field in the rating option 3, the rating option
3 isn’t recommended to use in the customized weighted rating feature.
If the overall form rating is rated as Unrated or Too New to Rate, it's ignored in the calculation of the overall
customized weighted rating.
Note
If you use the Route Form tool to skip the step at which the calculation of the overall customized weighted rating
is triggered, the calculation will still be triggered and you can get the calculated rating generated in the next
step.
Workflow Diagram
Here is an example of diagram describing what the workflow is like in calculating the overall customized weighted
rating:
Note
Each scenario defines one or more roles assigned to one or more users in one step. You can use different
combinations of the three scenarios in your own route map.
The calculation formula is (Role A's Rating * Role A's Weight + Role B's Rating * Role B's Weight + …) / (Role A's
Weight + Role B's Weight + ...). The total of weights doesn't have to be equal to 1.
• Scenario C: Two or more users with the same role in one step
An example of the route map is like this:
You can configure business rules to trigger the calculation of the overall customized weighted rating for Scenario A.
Prerequisites
Note
You can still create route maps of other languages for localization purposes, but you must ensure that a
route map of English US (English US) is created as business rules used here only work for steps and roles
defined in English US (English US).
Context
The calculation of the overall customized weighted rating involves two rule scenarios:
• Trigger Weighted Rating Rule: You use it to specify the form template and the step at which the calculation of
overall customized weighted rating is triggered.
• Configure Weight for Steps and Roles: You use it to configure the weights for different steps and roles in the
route map.
You're directed to the Business Rules Admin page that contains a list of business rules.
2. Select .
3. Select Performance Management Weighted Rating Configure Weight for Steps and Roles .
4. Enter the required information in the following fields:
• Rule Name
• Rule ID
• Start Date
For example, enter rule name as CWR-Demo-Weight and rule ID will be auto-filled.
5. Create the If and Then statements. You specify the step name and role type in the If statement and define a
weight assigned to each step and role in the Then statement.
Make sure that you enter the step name used in the route map that is created in the language English US
(English US) and the role value described in Roles [page 29]. For example, if a step is called Manager in the
route map, enter Manager as the step name here. If the role in the Manager step is Manager, enter EM as the
corresponding role type.
Tip
Make sure that you specify both the step name and role type in the If statement.
The weight can be a number, but not a percentage. For example, if the weight is 40%, enter 0.4.
Note
If the weight for a step or a role isn't set in the business rule, it's regarded as 0 in the calculation of the
overall customized weighted rating.
6. Select Save.
7. Caution
If you've created the ratingExtTriggerRule rule, don't create it again and you must add an Else If
statement in this rule at step 9. If so, skip step 7 and 8.
Click Create New Rule and you're directed to the Configure Business Rules page. Create a business rule for
Performance Management Weighted Rating Trigger Weighted Rating Rule .
8. Enter the required information in the following fields:
• Rule Name
• Rule ID
• Start Date
Enter ratingExtTriggerRule as the rule name and the rule ID will be auto-filled.
Caution
If you enter a different rule name/rule ID other than ratingExtTriggerRule, the rule doesn't work in the
rating calculation.
9. Note
As it's the first time you've created the ratingExtTriggerRule rule, create an If statement as follows.
Otherwise, you add an Else If statement.
Example
Next Steps
You can now go with the performance review process. The ratingExtTriggerRule rule will be executed after the
user with the role of 2nd Level Manager has given the rating at the Second Manager step and routed the form to
next step. The calculated rating is available after the Second Manager step.
Tip
If the rule doesn't work as expected or a deep review of the logic of business rules is needed, you can trace a
rule to try and figure out exactly what went wrong using the Business Rule Execution Log tool. When you create
rule traces for Trigger Weighted Rating Rule and Configure Weight for Steps and Roles, enter the Login User as
the user at the route step where the ratingExtTriggerRule rule is executed. See Business Rule Execution
Log.
You create the rule traces before the form is routed to the step where the ratingExtTriggerRule rule is
executed. After the form is routed to the step for rule execution and the user has given the rating and sent the
form to next step, you can go to Business Rule Execution Log to download the full business rule execution log.
And, you can set up a rule trace for a maximum time period of two days.
You can configure business rules to trigger the calculation of the overall customized weighted rating for Scenario B.
Prerequisites
Note
You can still create route maps of other languages for localization purposes, but you must ensure that a
route map of English US (English US) is created as business rules used here only work for steps and roles
defined in English US (English US).
Context
The calculation of the overall customized weighted rating involves two rule scenarios:
• Trigger Weighted Rating Rule: You use it to trigger the calculation of overall customized weighted rating.
• Configure Weight for Steps and Roles: You use it to configure the weights for different steps and roles in the
route map.
Procedure
You're directed to the Business Rules Admin page that contains a list of business rules.
2. Select .
3. Select Performance Management Weighted Rating Configure Weight for Steps and Roles .
4. Enter the required information in the following fields:
• Rule Name
• Rule ID
• Start Date
For example, enter rule name as CWR-Demo-Weight-01 and rule ID will be auto-filled.
Make sure that you enter the step name used in the route map that is created in the language English US
(English US) and the role value described in Roles [page 29]. For example, if a step is called Manager in the
route map, enter statements. You specify the step name and role type in the Manager as the step name here. If
the role in the Manager step is Manager, enter EM as the corresponding role type.
Tip
Make sure that you specify both the step name and role type in the If statement.
The weight can be a number, but not a percentage. For example, if the weight is 40%, enter 0.4.
Note
If the weight for a step or a role isn't set in the business rule, it's regarded as 0 in the calculation of the
overall customized weighted rating.
6. Select Save.
7. Caution
If you've created the ratingExtTriggerRule statements. You specify the step name and role type in the
rule, don't create it again and you must add an Else If statement in this rule at step 9. If so, skip step 7 and
8.
Click Create New Rule and you're directed to the Configure Business Rules page. Create a business rule for
Performance Management Weighted Rating Trigger Weighted Rating Rule .
8. Enter the required information in the following fields:
• Rule Name
• Rule ID
Enter ratingExtTriggerRule as the rule name and the rule ID will be auto-filled.
Caution
If you enter a different rule name/rule ID other than ratingExtTriggerRule, the rule doesn't work in the
rating calculation.
9. Note
As the ratingExtTriggerRule rule already exists, add an Else If statement as follows. Otherwise, you
create an If statement.
Add the Else If and Then statements. You choose the form template for which you want to configure the
business rule and specify the step to trigger the calculation in the Else If statement, and then set the Rule ID
created in step 4 in the Then statement.
Example
Next Steps
You can now go with the performance review process. The ratingExtTriggerRule rule will be executed after the
user with the role of 2nd Level Manager has given the rating at the Second Manager step and routed the form to
next step. The calculated rating is available after the Second Manager step.
If the rule doesn't work as expected or a deep review of the logic of business rules is needed, you can trace a
rule to try and figure out exactly what went wrong using the Business Rule Execution Log tool. When you create
rule traces for Trigger Weighted Rating Rule and Configure Weight for Steps and Roles, enter the Login User as
the user at the route step where the ratingExtTriggerRule rule is executed. See Business Rule Execution
Log.
You create the rule traces before the form is routed to the step where the ratingExtTriggerRule rule is
executed. After the form is routed to the step for rule execution and the user has given the rating and sent the
form to next step, you can go to Business Rule Execution Log to download the full business rule execution log.
And, you can set up a rule trace for a maximum time period of two days.
You can configure business rules to trigger the calculation of the overall customized weighted rating for Scenario C.
Prerequisites
Note
You can still create route maps of other languages for localization purposes, but you must ensure that a
route map of English US (English US) is created as business rules used here only work for steps and roles
defined in English US (English US).
Context
The calculation of the overall customized weighted rating involves two rule scenarios:
• Trigger Weighted Rating Rule: You use it to specify the form template and the step at which the calculation of
overall customized weighted rating is triggered.
• Configure Weight for Steps and Roles: You use it to configure the weights for different steps and roles in the
route map.
You're directed to the Business Rules Admin page that contains a list of business rules.
2. Select .
3. Select Performance Management Weighted Rating Configure Weight for Steps and Roles .
4. Enter the required information in the following fields:
• Rule Name
• Rule ID
• Start Date
For example, enter rule name as CWR-Demo-Weight-02 and rule ID will be auto-filled.
5. Create the If and Then statements. You specify the step name and role type in the If statement and define a
weight assigned to each step and role in the Then statement.
Make sure that you enter the step name used in the route map that is created in the language English US
(English US) and the role value described in Roles [page 29]. For example, if a step is called Manager in the
route map, enter Manager as the step name here. If the role in the Manager step is Manager, enter EM as the
corresponding role type.
The weight can be a number, but not a percentage. For example, if the weight is 40%, enter 0.4.
Note
If the weight for a step or a role isn't set in the business rule, it's regarded as 0 in the calculation of the
overall customized weighted rating.
6. Select Save.
7. Caution
If you've created the ratingExtTriggerRule rule, don't create it again and you must add an Else If
statement in this rule at step 9. If so, skip step 7 and 8.
Click Create New Rule and you're directed to the Configure Business Rules page. Create a business rule for
Performance Management Weighted Rating Trigger Weighted Rating Rule .
8. Enter the required information in the following fields:
• Rule Name
• Rule ID
• Start Date
Enter ratingExtTriggerRule as the rule name and the rule ID will be auto-filled.
Caution
If you enter a different rule name/rule ID other than ratingExtTriggerRule, the rule doesn't work in the
rating calculation.
9. Note
As the ratingExtTriggerRule rule already exists, add an Else If statement as follows. Otherwise, you
create an If statement.
Add the Else If and Then statements. You choose the form template for which you want to configure the
business rule and specify the step to trigger the calculation in the Else If statement, and then set the Rule ID
created in step 4 in the Then statement.
Next Steps
You can now go with the performance review process. The ratingExtTriggerRule rule will be executed after the
user with the role of 2nd Level Manager has given the rating at the Second Manager step and routed the form to
next step. The calculated rating is available after the Second Manager step.
Tip
If the rule doesn't work as expected or a deep review of the logic of business rules is needed, you can trace a
rule to try and figure out exactly what went wrong using the Business Rule Execution Log tool. When you create
rule traces for Trigger Weighted Rating Rule and Configure Weight for Steps and Roles, enter the Login User as
You create the rule traces before the form is routed to the step where the ratingExtTriggerRule rule is
executed. After the form is routed to the step for rule execution and the user has given the rating and sent the
form to next step, you can go to Business Rule Execution Log to download the full business rule execution log.
And, you can set up a rule trace for a maximum time period of two days.
Enable the latest version of the My Forms page for Performance Management and 360 Reviews forms, so that
users can work with a more intuitive page layout, improved search functions, simplified flows to create and manage
forms, and other user experience enhancements.
Procedure
Enable the user experience enhancements so that users see Performance Management forms with a reduced
width and some redesigned or rearranged views and UI elements.
Prerequisites
You have the Administrator Permissions Manage System Properties Performance Management Feature
Settings permission.
Procedure
Launch forms based on a well-configured form template so that employees and managers can start performance
reviews in a specific time period.
Prerequisites
• You've enabled the permissions of Mass Create Form Instances (Launch forms now) and Schedule Mass Form
Creation (Launch forms later) under Manage Form Templates in Manage Permission Roles.
• Make sure that employees for whom you want to launch forms have system logon permissions.
• For customers who launch forms according to a recurring schedule, make sure that you create the Schedule
Form Creation job in Manage Scheduled Jobs in Provisioning. For more information, see Creating Job Requests
in Related Information.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
Procedure
You can launch forms now, later on a specified date, or according to a recurring schedule.
Note
Option Description
All Active Em- Select this option to launch forms for all active employees in the organization. You can choose to include
ployees inactive employees.
Note
This option can be hidden by selecting the permission of Hide 'All active/inactive employees' option in
Launch Forms wizard under General User Permission.
One Employee Select this option to launch forms for individual employees. You can add several employees to this list.
Group of em- Select this option to launch forms for a group of employees. You can select a predefined group, upload a
ployees CSV file, or use filters to find employees.
Note
If you upload a CSV file, make sure that the file uses UTF-8 encoding.
You can also choose to launch forms only for users who don't have an existing form within a specified end date
range.
Note
Those selected employees are dependent on your target population. If you schedule forms to be launched
later or according to a recurring schedule, and some of the selected employees have been removed from
the target population before the launch date, forms won't be launched for them.
6. Review the previous selections and select the following options as necessary.
• Send email notifications to form recipients: If you select this option, the first person in the route map will
receive an email notification that a form is created.
Note
To send the email notification, make sure that you also set up Document Creation Notification in E-Mail
Notification Templates Settings.
• Create En Route Copy: If you select this option, the copy of the launched forms will be sent to your En Route
form folder.
7. Choose Launch.
Results
Forms are launched. You can check progress from the reports tab.
When you launch forms now, you can edit the introductory text of custom sections and update custom fields in
Launch Forms.
Prerequisites
• You've added a custom section in your form template and selected the Edit Intro text description in Mass create
option for the section.
• You've defined a custom field and selected the Editable during mass creation of forms option for the field.
For more information, refer to Configuring Form Sections and Configuring Custom Fields.
Procedure
Related Information
After you launch forms using Launch Forms, you can monitor the job status and view a job summary within 30
days.
Prerequisites
You've enabled the permissions of Read Execution Manager Events and Read Execution Manager Payload under
Admin Center Permissions.
Procedure
All form launch jobs within the timeframe are shown in a vertical bar chart.
3. In the job status table, choose (Summary So Far) to view a job summary.
After scheduling a form launch, you can modify or cancel the launch.
Prerequisites
You have scheduled a form launch that runs later. See Launching Forms.
• Modify a launch: Choose Take Action Edit , and make changes on the Launch Forms window.
• Cancel a launch: Choose Take Action Delete , and confirm in the dialog.
Related Information
After launching forms, you can manage those forms in Admin Center while employees and managers are doing
performance reviews. Learn about the tasks involved in managing forms.
You can change the start, end, and due dates of a form.
Prerequisites
Procedure
1. In Admin Center Change Form Date , search for the forms of which you want to modify the dates. You can
do a search in either of the following ways.
• Employee Document Folder: Search for forms in a specific user's inbox, En Route folder, or Completed
folder.
• Advanced Search: Search for forms based on user attributes or form attributes.
2. On the search result page, select the forms and choose Change Date.
3. In the Change Document Date dialog box, enter the new date in the dd/mm/yyyy format, or enter the number
of days by which you want the existing date to be extended.
4. Save your changes.
As an administrator, you can route an in-progress form one step forward, one step back, to a specific step, or to a
new step as necessary.
Prerequisites
Grant the permissions of Route Document under Manage Documents, including Include Completed Documents and
Allow Adding of a Step.
Each form includes a workflow sequence that determines all the people who review the form and the order in which
they review the form. By routing an on-going form, you can manually change the order without modifying the route
map.
Procedure
Note
If you select Move the form one step forward, you need to choose a validation option: Skip form validation or
Validate form. If you choose the latter, the system validates required fields of the form at the current step
according to the following rules:
• If the step is a single step, the system validates the fields required for the step owner.
• If the step is an iterative step, the system validates the fields required for the substep owner. For
example, if the substep owner is EP, all matrix managers' required fields are validated.
• If the step is a collaboration step and has no exit user, the system validates the fields required for all
collaboration step owners.
• If the step is a collaboration step and has one exit user, the system validates the fields required for the
exit user.
• If the step is a collaboration step and has multiple exit users, the system validates the fields required
for all exit users.
5. Select Next.
The form is routed to the step that you selected.
You can find all forms that were created based on the same template and mass route the forms at one go.
Prerequisites
Grant the permissions of Route Document under Manage Documents, including Include Completed Documents and
Allow Adding of a Step.
Procedure
Tip
You can select all the listed forms from across the pages by selecting Select all <n> documents in search
results, or select all the forms on the current page by selecting the Form ID checkbox.
Results
A form group consists of the forms that were mass launched from one form template in a batch.
If you manually modify forms after they were mass launched, they are removed from their group. For example,
• You configured the Automatic insertion of new manager as next document recipient if not already setting for
document transfer.
• You routed the form back from the signature or completion stage.
• You used User (U) steps in the route map.
For the ungrouped forms, you can route them individually. On average one administrator can route 100 forms an
hour manually. Or you can open a support ticket to request these forms to be regrouped for mass routing. See the
KBA 2086638 .
• You configured the Automatic insertion of new manager as next document recipient if not already setting for
document transfer.
• You routed the form back from the signature or completion stage, and this behavior inserted an additional U
step.
You can route multiple forms by uploading form IDs stored in a CSV file to Admin Center.
Context
By uploading the CSV file, you can route multiple forms based on form ID, irrespective of whether the forms are
part of different groups or use different form templates.
Procedure
Note
If you are using this tool for the first time, choose Download Template to download the CSV file template.
The CSV file consists of a single coulmn with a Form ID header.
Tip
You can select all the listed forms from across the pages by selecting Select all <n> documents in search
results, or select all the forms on the current page by selecting the Form ID checkbox.
Results
Modify route maps to add, delete, or edit route steps for one or multiple forms that have been already launched.
Prerequisites
You have the role-based permission Manage Documents Modify Form Route Map .
Procedure
Modify common options You can modify step name, step introduction, dates, and
other text-based attributes.
Change step types and permissions You can change the step type and associated permissions
for a specific step. Note that these changes will only apply to
forms that have not been routed to the selected step.
4. On the Modify Form Route Map page, and add, delete, or edit the route steps within the form.
5. Choose Next, the route maps are modified accordingly, and you are navigated to the Summary page.
Note
If you select more than 20 forms for route map modification, that will trigger a job in Provisioning and the
system will send you an email about the detailed results.
Results
If new goals are added to a goal plan after forms were launched, you can mass update the forms for newly created
goals to display on individual forms and goal reports.
Procedure
Results
Now all the forms within the specified date range are updated to reflect new content, including new goals.
Customize the layout of a Performance Management form that's used for printing.
Prerequisites
Context
If you want to customize the form print layout, note that the BIRT tool doesn't respect field and section permissions
configured in the form template.
Procedure
Results
The forms based on the selected template use the custom layout when they are printed.
Prerequisites
You can hide forms from employees who no longer need access to them during a review or by the end of the review
cycle. The form will be removed from both the employee's form list and the Team Overview page. This task might be
required when employee relationships change during a review event.
Note
• You cannot remove form visibility for users who are outside the route map.
• This feature only works for forms in the En Route, default Completed, and custom Completed folder.
Procedure
• by User
1. Enter the User with Visibility (from whom you want to remove the visibility) and the Subject of
Document (the person who is reviewed) in the required fields, and choose List Documents.
2. From the form list, select the forms you want to be invisible to the user.
• by Document Id: Enter the Document Id and the User with Visibility in the required fields.
• by CSV Upload: Mass remove form visibility by uploading a CSV file that contains form ID and either user ID
or user role.
1. Choose Download CSV Template and select by Roles or by User ID to download the template CSV file.
2. Fill in the CSV file as required and upload the file to this page.
3. From the form list, select the forms you want to be invisible to the user.
Note
Results
If you've made forms invisible to some users, you can grant them access to the forms again.
Prerequisites
Context
This feature only works for forms in the En Route, default Completed, and custom Completed folder. If you
restore the visibility of forms that was in the custom Completed folder, the forms will be restored into the default
Completed folder (Un-Filed).
Procedure
Results
You have successfully restored the access to the form for the selected users.
Delete forms to remove them from the system. You can delete multiple forms at once.
Prerequisites
After you delete forms, the attachments included in the forms are not deleted from the system. They remain in
the deleted section of the Manage Documents admin tool. If you want the attachments to be hard deleted from the
system, delete the attachments from the forms directly.
Procedure
Employee Document Folder Search for the forms in a specific user's Inbox, En Route
folder, or Completed folder.
Note
With this option, the form title is displayed in the default
language of the form template name rather than in the
language of your instance. If your language is different
from the default language, we recommend that you use
advanced search.
Advanced Search Search for forms by specifying user attributes, form attrib-
utes, or by uploading a CSV file of form ID.
Tip
You can select all the listed forms from across the pages by selecting Select all <n> documents in search
results, or select all the forms on the current page by selecting the Form ID checkbox.
4. Choose Yes to confirm that you want to delete the selected forms.
Results
You can restore a deleted form to the route map step when it was deleted.
Prerequisites
Procedure
Employee Document Folder Search for the forms in a specific user's Inbox, En Route
folder, or Completed folder.
Note
With this option, the form title is displayed in the default
language of the form template name rather than in the
language of your instance. If your language is different
from the default language, we recommend that you use
advanced search.
Advanced Search Search for forms by specifying user attributes or form attrib-
utes.
Tip
You can select all the listed forms from across the pages by selecting Select all <n> documents in search
results, or select all the forms on the current page by selecting the Form ID checkbox.
4. Choose Yes to confirm that you want to restore the selected forms.
Results
You can manually update overall scores for multiple forms by importing a CSV file.
Prerequisites
Grant the permission of Import Overall Scores Only for Target Population or Include All Employees under Manage
Documents.
Note
Import Overall Scores Only for Target Population allows users that have been granted this permission to update
manual overall scores for a target population. Include All Employees allows users that have been granted this
permission to update manual overall scores for all employees.
Context
• You have a performance evaluation process that includes a calibration process carried outside the SAP
SuccessFactors system, and therefore you need to update the overall scores in Performance Management
forms.
• After you start using Performance Management, you want to migrate the performance ratings of employees
from previous applications to the SAP SuccessFactors system. With that, you can take advantage of reports
and dashboards including all performance ratings of employees in one central place.
You can update performance rating, potential rating, overall competency rating, and overall goal rating. If you
update performance rating, and there's more than one section that contains performance rating, the section with
highest priority is updated. The following sections are listed in the order of priority from high to low: the customized
weighted rating section, the performance potential summary section, and the summary section.
Please note that this feature has the following prerequisites and limitations:
• The sections for which you want to update the score must have manual rating enabled. Otherwise, the import
fails with PERFORMANCE: Manual rating not enabled for Performance score for document Id
xxxxx.
• You can only update rating scale values (scores).
• The imported score must have a match in the section's rating scale value. Rating scale descriptions are not
supported.
• The OCOC score is recalculated when the overall competency rating or overall goal rating is updated.
• This feature only works for forms at the Modify stage.
• If an error occurs in one entry of a document, the system stops processing the other entries of that document,
but continues to process the entries of other documents.
• For optimum performance, the file size should not exceed 5 MB.
Procedure
The file must be a CSV UTF-8 (comma-delimited) file and have a .csv extension.
The header row must contain DOCUMENT_ID and at least one of the ratings (COMPETENCY, OBJECTIVE,
PERFORMANCE, or POTENTIAL) you want to update.
Note
• Besides numeric values, the following descriptive values are also accepted:
• UNRATED: Change the overall score to the value of default-rating, which is often defined as
"Unrated" rating. This value only works when the rating field is not marked as required.
• NA: Change the overall score to the value of unrated-rating, which is often defined as "Not
applicable" or "Too new to rate". This value is not supported in the goal competency summary
section and performance potential summary section.
• The number of entries in the header row must match the number of entries in other rows.
• Invalid header row entries and blank entries are ignored.
In this example, performance rating is updated to 3 in a form with the document ID 5245.
5245 3
Results
When the import is complete, you receive an email about the detailed results of the import.
Related Information
Learn about the known behaviors when you work with Performance Management forms in the Google Chrome
browser.
• When you save your changes after adding or editing goals in a form, the page refreshes and you are taken to
the top of the form page. To go to a section of your choice, use the top navigation bar of form sections.
Note
This is also a known behavior in other browers like Microsoft Edge and Firefox.
• When you add or delete competencies or behaviors in a form, the page refreshes and you are taken to the top
of the form page. To go to a section of your choice, use the top navigation bar of form sections.
• If you choose the Save as PDF and then the Show PDF button, you cannot download and save the form as PDF.
You can solve this in one of the following ways:
• Switch to another web browser or PDF viewer.
• In your instance using Google Chrome browser, choose the Save as PDF button on the form and then
the Show PDF button. Next, in the preview stage, choose Print instead of Download icon, and then select
Change. In the popup window, choose Save as PDF. This saves the form as PDF.
To provide a seamless talent management experience, Performance Management can be integrated with other
SAP applications, including those from SAP SuccessFactors. Learn about available integration features and how to
achieve integration.
With proper configurations and permissions granted, users can do the following in the goal sections of a form.
• View the form subject's performance or development goals that are auto-populated from a goal plan to the
form.
• Provide ratings and comments on the form subject's goals.
• Add goals to the form in the following ways through the Add Goals dropdown menu:
• Create a goal from scratch and add it to the form.
• Create goals from a goal library and add them to the form.
Note
This option is only available in goals sections that are linked to performance goal plans.
• Select existing goals, including personal goals and assigned team goals, from the linked goal plan and add
the goals to the form.
Note
This option is not needed if you've enabled auto-sync between the linked goal plan and form.
• Edit a goal on the form, such as modify the goal description or add a milestone for the goal. The goal-related
information is shown on the Goal Details and Other Details tabs below the goal.
• Remove a goal from the form.
For information on how the changes to goals on the form affect the linked goal plan, refer to Auto-Populate and
Auto-Sync.
Related Information
Goals in a goal plan are auto-populated to a Performance Management form. When the form is created, all goals
created in the goal plan are included on the form. Goals can also be auto-synchronized between a goal plan and a
form.
Add a goal after the form is created New goal doesn't appear New goal appears
Add a goal before the form is created New goal appears New goal appears
Add a target or a task to an existing goal New target or task appears New target or task appears
Remove a goal The goal still appears and is not deleted The goal is deleted without any warning
message
Add a target or a task to an existing goal New target or task appears New target or task appears
Remove a goal The goal still appears and is not deleted The goal is deleted without any warning
message
Note
If you use the latest Goal Manage-
ment and you enabled the auto-
sync feature in Performance Man-
agement, please be aware of the fol-
lowing:
Note
• When a form is in the modify stage, changes in a goal plan are synced to the form. When the form is in the
signature or completion stage, the changes aren't synced to the form.
• Auto-sync on a form works when the form is saved.
• If goals are auto-populated to multiple goal sections based on goal categories, we do not recommend you
also use auto-sync. This is because changing the category of a goal in the goal plan will move the goal
to a different section in the form. While the goal is moved to the new section correctly, any ratings and
comments associated to the goal are not moved and get lost.
If goals on the forms are metric-based, the rating is calculated based on the metric value. For example, Rating 3
has a metric value of 20.00, Rating 2 has a metric value of 15.00, and Rating 1 has a metric value of 10.00. If an
employee achieves a metric value of 19.99, which falls between Rating 2 and Rating 3, the employee rating would be
2.
When metric lookup table ratings are used, the official rating field of each goal is populated with the corresponding
metric lookup table rating. Generally, other ratings like unofficial user rating and subject rating are not needed. So,
in a performance review step, if official rating is displayed to users, they can't edit unofficial user rating or subject
rating, despite that they have write permission for these ratings.
Tip
• If customers use metric lookup table ratings, we recommend that they use rating option 0.
• If customers want both employees and managers to provide ratings, we do not recommend that they use
metric lookup table ratings.
Note
When a form template is configured to populate goal ratings from the metric lookup table, at least read
permission should be granted to the related fields of the metric lookup table (for example, rating field, actual-
achievement field) in the goal template. Otherwise, goal ratings in the Performance Management forms and
goal plans might be inconsistent. For more information about goal ratings, refer to Metric Lookup Basics.
Related Information
You can configure blocks in SAP SuccessFactors People Profile to display ratings from Performance Management
forms.
• Trend blocks:
• Overall performance rating block
• Overall potential rating block
• Overall goal rating block
• Overall competency rating block
These blocks display respective ratings from all forms as multiple records for employees. For more information,
refer to Configuring a Trend Information Block in People Profile.
• Scorecard blocks:
• Performance History block
Note
• Rating scale labels are displayed in their default language in the blocks.
• The Performance History block uses predefined fields to display data. You can't add fields to or hide fields
from the block.
• Forms in the Performance History block are sorted alphabetically by form title in an ascending order.
• The Competencies block displays an average of the ratings from Performance Management forms, 360
Reviews forms, and competency ratings from SAP SuccessFactors Learning.
• To display Learning URL in the Competencies block, make sure both the SAP SuccessFactors Learning
integration and Transcript features are enabled. For more information, refer to Setting up and Enabling the
Transcript Feature.
• If a competency has more than one rating from different forms, the average rating is displayed in the
Competencies block. The same rule applies to behaviors in the Behaviors block.
• For Scorecard blocks, if the rating scale in a process is different from that in a form, ratings displayed in the
blocks will be normalized to the rating scale in the process. For example, the form has a 5-point rating scale,
and the rating scale selected in the process is a 3-point rating scale. Therefore, ratings will be normalized to
the 3-point scale. Item weight won't be taken into account during the normalization. For more information
about normalization, refer to Calculation Process.
Related Information
The Performance History block displays the performance, potential, goal, and competency rating, which are from
different summary sections on Performance Management forms.
Note
Make sure you have at least one goal section and one competency section on a form. Otherwise, there will be
no ratings in the Performance History block.
Goal competency sum- OCOC rating in this sec- / Overall goal rating in Overall competency rat-
mary section tion, if enabled this section ing in this section
Summary section Overall form rating in / Overall goal rating in the Overall competency rat-
the summary section goal competency sum- ing in the goal compe-
Goal competency sum- mary section tency summary section
mary section
Goal competency sum- Overall performance Overall potential rating Overall goal rating in the Overall competency rat-
rating in the perform- in the performance po- goal competency sum- ing in the goal compe-
mary section
ance potential sum- tential summary sec- mary section tency summary section
Performance potential mary section tion
summary section
Summary section Overall performance Overall potential rating Overall goal rating in the Overall competency rat-
rating in the perform- in the performance po- goal competency sum- ing in the goal compe-
Goal competency sum- ance potential sum- tential summary sec- mary section tency summary section
mary section mary section tion
Performance potential
summary section
Configure a Scorecard block to display the performance history, competency ratings, behavior ratings, or goal
ratings of employees in People Profile.
Prerequisites
• You've added XML code for a background element to Succession Data Model. For more information, refer to
Performance Management, 360 Reviews, and the Succession Data Model.
• You've created a process in Admin Center Processes and Forms to define which ratings are displayed in
the block.
For the options of form drilling visibility, we recommend that you select Managers can drill to see all forms in
their team at any point in the process. So, managers can open all forms in the block no matter whether the
forms have been in their form inbox. Otherwise, they can only open the forms that have once been in their
form inbox.
Procedure
Field Description
Block Title (Required) The title of the block as it appears on the profile
Show the description below the block title By default, users access a block description through the
Help in the block.
Show Ratings as (Required for the Performance History block) The display
option of ratings in the block. The following options are avail-
able:
• Rating (Unrounded)
• Normalized Rating (Unrounded)
• Normalized Rating (Rounded)
• Normalized Rating (Rounded) - Labels only
Number of entries to display (Required for the Competencies block) The number of com-
petencies and their respective ratings to be displayed in the
block
4. On the Configure People Profile page, choose General Settings on the top.
5. On the right panel, complete the following fields under Talent Data Settings.
Field Description
Include talent data within this date range Defines a date range. Only ratings within the range are dis-
played.
Include talent data from this process Specifies the forms, succession data, or goal plans from
which ratings are retrieved. If you select All data sources, all
Note
Do not select All data sources if you want to show nor-
malized ratings in People Profile. Specify a process so
that the rating scale defined in that process can be used
to normalize ratings.
Include in-progress forms Defines whether ratings from in-progress forms are dis-
played.
Note
Any change in these fields affects the rating source for the Performance History, Competencies, Behaviors,
and Goal Ratings blocks. Goal ratings come from associated forms. If there's no associated form, the goal
rating is displayed as 0.
6. Choose Save.
Results
The respective data of employees within the configured date range and process is displayed in the block of the
profile.
Related Information
You can add People Profile block links to forms so that users can view profile information when working on the
form.
Context
• User Information
Procedure
1. In Admin Center, go to Configure People Profile and find the Block Id and Block Type of a block on the right
panel.
2. Go to Manage Templates, open a form template, and choose a section.
3. Enter [[BLOCKLINK|blockid|blockType|displayname]] in Description.
Recommendation
Results
After forms are launched, users can choose the link in the forms to view profile information.
Related Information
For customers who use the multiple employment feature, enable the person-based Performance History block
so that users can view employees' performance review data from multiple employments and inactive users'
performance history.
Prerequisites
When an employee under one employment views their Performance History block, they can view data related
to their active employment only. Information about their inactive employment is not available to them because
employees don't have the role-based permission to access inactive employment.
Procedure
Results
A message strip appears in the block, informing that the block shows information from all employments. If there's
no performance history, users are informed that no data is found for any employments. The exact number of
employments that users view depends on their granted permissions.
If you've enabled global assignments or concurrent employment in Employee Central, the following features are
supported in Performance Management.
• You can create separate forms for multiple employments of one person.
• Employees on multiple employments have multiple managers, matrix managers, and more. The relationship
roles of one employment are involved to review the performance of that employment.
Note
As an administrator, you can't proxy as a user for their multiple employments and then access the forms
from the to-do tasks on the home page. Therefore, you can't see the forms upon choosing them in To-Do.
Employee who returned from multiple Accessing To-Do on the home page • When the employee logs in to their
employments active employment, they see all
forms in To-Do.
• When they choose a form for their
inactive employment, the form
opens and they can rate, com-
ment, and route the form forward.
• When they choose a form for their
inactive employment, their logon is
automatically switched to that of
the inactive user.
Manager of an employee who returned Accessing To-Do on the home page • The manager will see all forms
from multiple employments of the employee's inactive employ-
ment in To-Do.
• When the manager chooses a form
for the employee's inactive em-
ployment, the form opens and they
can rate, comment, and route the
form forward.
Accessing forms in form folders • The manager will see the forms
of the employee's inactive employ-
ment in the form Inbox. From the
Inbox, the manager can rate, com-
ment, and route the form forward.
• The manager will see the forms
of the employee's inactive employ-
ment in Team Overview and Stack
Ranker. If the form is in their form
Inbox, or they have the Out of Turn
Access permission, they can rate,
comment, and route the form for-
ward.
Manager who returned from multiple Accessing To-Do on the home page The manager can access employees'
employments forms from their inactive employment
in To-Do.
• For the information about to-do tasks for employees with multiple employments, see To-Do List.
Limitations
• The competency information of inactive employment is not available in the Competency block in People Profile.
Related Information
Performance Management forms can display achievements and feedback linked to employees' goals in Continuous
Performance Management as supplemental information during the performance review cycle.
If configured, they're shown on the Achievements tab in goal sections, as shown in the following screenshot.
For the achievements to appear on the form, make sure that the achievements are dated between the start and
end date of the form. For example, an achievement dated August 15 won't appear on a form with a start date of
November 20 and an end date of December 10.
If achievements or feedback is deleted from Continuous Performance Management, the data is removed from
forms as well, even though the forms might be completed. So, we recommend don't delete the data that is reused
on forms.
Configure your form template so that users can view employee's achievements and feedback directly on forms.
Prerequisites
Procedure
The Achievements tab is now available to all users with the role-based permission specified in Prerequisites.
This applies to the forms that have been already launched as well.
4. Optional: Define the <tab-permission> element in the form template to control user access to the tab.
Related Information
Configure the Compensation section in a form template so that Performance Management forms can display
compensation-related information and a link to the Compensation form.
Prerequisites
• You've enabled SAP SuccessFactors Compensation and configured a Compensation form template.
• You have access to Provisioning.
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact
your implementation partner or Account Executive. For any non-implementation tasks, contact Product
Support.
Procedure
1. In Provisioning, go to Form Template Administration and copy the ID of the Compensation form template.
2. On the All Form Templates page, open the Performance Management form template that you want to configure.
3. Under Add New Section, select Compensation, add a name for the section, and choose Add.
4. Under Edit Sections, add the following elements in the newly added Compensation section.
Element Description
Sample Code
<compensation-template-id><![CDATA[708]]></compensation-template-id>
<compensation-field id="pmRating" show-if-value-empty="true"></compensation-
field>
Results
After you launch a Performance Management form, the form will have a Compensation section. Also, a
Compensation form will be created.
Data integration between Performance Management and your Human Resource Information System (HRIS) or
payroll system allows updating your employee data from a single source. With this simple data transfer process, the
updates you enter into your HRIS will be passed to Performance Management without duplicated efforts.
Introduction
This integration requires the export of the defined data fields into a flat file, which is uploaded through Admin
Center. The update process can be automated using a Secure File Transport Protocol (SFTP) process and executed
according to your schedule to maintain synchronized data.
To import data from an HRIS (or other data source) into Performance Management, certain business rules MUST
be followed.
• The file must be in Comma-Separated Values (.csv) format. The file can be a plain text file (.txt) too but the
values must be separated by commas. For values with commas, we suggest enclosing them in quotes so they
load properly.
• Take care when using data fields with leading zeroes. Spreadsheet applications such as Microsoft Excel strip
leading zeroes from data fields, which could corrupt the data. If there are leading zeroes in the data file, verify
the leading zeroes are present in the file before uploading.
• The file must contain two rows of predefined column IDs and labels. A template for these column IDs and labels
can be exported from the system using the Export Template option.
• All fields are case-sensitive and reflect what is loaded in the data load.
• JOBCODE is case-sensitive and must match exactly the job codes designated for roles. To see a list of families
and roles, go to Admin Center Manage Job Profile Content .
• JOBCODE is used to determine competency mapping, which allows competencies to be populated on forms
and worksheets based on the value in the JOBCODE field. If the company is using job profiles, the value entered
in this column determines what set of competencies will be displayed on the form for that employee. This value
may be the actual job code from the HRIS or a derived code: Many customers choose to combine job codes
into broad employee groups to simplify administration of competency sets that are common across many roles
in the same group. This decision should be made by the implementation team based on the process.
Example
IC Individual Contributors
• STATUS must be the first field and USERID must be the second field and the upper-case header must be
repeated for the second row. The remaining fields need not be in the order presented here. If a field won't be
populated, don't include it in the import file. If that field in the file is blank, it wipes out what is already in the
database.
• USERID is the system unique value for each user and must be unique. This value is visible in a variety of places
to all end users. Accordingly, USERID shouldn't contain data that is considered confidential, such as a social
security number. This value must be passed with each employee data record during each upload.
Note
Exert extra care when assigning a value to USERID, because the decision has a permanent effect: after the
value is saved, it cannot be changed.
• USERNAME is a unique name for each user and is used as the logon ID value. This value is visible in a variety of
places to all end users. Accordingly, USERNAME shouldn't contain data that is considered confidential, such as
social security number. Unlike USERID, this value can be updated if needed. Most customers choose to use the
same USERNAME that they use for their local network or email application.
• The definition of which fields are required is the minimum requirement and must be populated. The additional
recommended fields are used in the system for reporting and are important for grouping data. Additional fields
can be marked as required during initial implementation based on business need. The order of fields displayed
on the Personal Information screen can be modified if necessary.
• During the initial setup, you can use an option to control whether employees should be allowed to edit or not to
edit the data loaded into the employee record (on the Personal Information screen).
Note
We strongly recommend these edit rights be turned off to maintain sync of data with the HRIS. Take care to
understand impact of ability of the user to update certain variables directly. Values updated from the user
interface will be overwritten by the next data load from the HRIS.
• The individual fields in the employee record can also be hidden during the initial setup so that they won't
display in the Personal Information screen. This allows for the storage of data associated with each individual,
passed from the HRIS to be used by one or more processes, but this data isn't displayed on the Personal
Information screen (accessed by the employee).
• If the DEPARTMENT, DIVISION, or LOCATION field isn't used, don't include them in the import file. Otherwise,
the system will automatically assign "N/A" values to these fields. Report security is tied to these values and
entering a common value, such as NA, will allow for the broadest reporting access to the data. Leaving it blank
will limit reporting access.
Example
"gsmith624|sholmes423|smaddox666"
• DEFAULT_LOCALE is not required in data file. If present, the values in the field determine the languages the
system use for individual users (one language per user). If the field is left blank for a user, the user's existing
value won't be changed. Example: Bo had previously selected "it_IT" (Italian) and the data file now includes
the DEFAULT_LOCALE field with a blank value for Bo; his value for default locale remains "it_IT", which is his
previous selection rather than the company-wide default language.
• PROXY is not required in data file. If present, the value in the field defines which person can act as proxy on
behalf of the user. If left blank, no proxy holder will be assigned and existing proxy holders will be removed.
Example
"admin|sholmes423|smaddox666"
• TIMEZONE is required in the system for internal time/date stamps in the time of the user. If a TIMEZONE value
isn't loaded, the field is automatically populated with a default of Eastern Standard Time. Records may be set
to one value (example: time zone of corporation) rather than different zones for each employee.
By integrating your SAP SuccessFactors system with Qualtrics, you can request feedback from employees and
managers during the different steps that happen at the end of a performance review.
You can integrate survey opportunities in single role, iterative, and collaboration steps. For example, with
a performance review template that contains three steps (employee assessment, manager assessment, and
employee signature), you can have a survey after both the employee and manager assessment steps. You can
create survey opportunities at one or multiple steps.
Qualtrics surveys allow you to gain feedback from your employees such as:
To add Qualtrics feedback opportunities, enable and integrate Qualtrics with your SAP SuccessFactors system.
Refer to Integrating SAP SuccessFactors with Qualtrics for details.
Related Information
Performance Management is part of SAP SuccessFactors Performance & Goals and includes the following features
on the home page.
Review Your Prompts you to For You Today Appears when It's enabled Yes
Performance (self- at Manage
complete perform- a performance re-
review)
ance reviews for view form is added Home Page Card
yourself. to your form inbox. Settings .
Disappears in any
Note
of the following
If the form cases:
template name
is changed af-
• You complete
your task and
ter forms are
the form is no
launched, the
longer in your
name won't be
inbox.
changed on to-
do tasks. It re- • 365 days after
Review Employee Prompts you to For You Today Appears when It's enabled Yes
Performance (for at Manage
complete perform- a performance re-
others)
ance reviews for view form is added Home Page Card
your team. If man- to your form inbox. Settings .
agers have more
Disappears in any
than one task,
of the following
tasks are grouped
cases:
into Direct Reports,
Matrix Reports, and • You complete
Other on the stack your task and
view. the form is no
longer in your
Note inbox.
Learn about Performance Management notification cards users can receive in Microsoft Teams.
Prerequisites
Cards
Review Employee Performance Displays basic information about performance reviews users A performance review form is
(for others) need to complete for their team. added to the users' form in-
Takes users to their SAP SuccessFactors system to complete box.
the performance review form.
Review Your Performance Displays basic information about performance reviews users A performance review form is
(self-review) need to complete for themselves. added to the users' form in-
Takes users to their SAP SuccessFactors system to complete box.
the performance review form.
Related Information
You can use reporting tools in SAP SuccessFactors People Analytics, such as Table reports and Story reports, to
report Performance Management data.
For information on Table reports, refer to the Table Reports guide. For information on Story reports, refer to the
Stories in People Analytics guide.
• If customers have removed a configured language for a competency and add it back, the following columns of
the competency are empty in Table reports:
• Competency Category Name
• Competency Source
• Core Competency
• Competency Name (Locale Specific)
• Behavior Name (Locale Specific)
In an instance with Talent Intelligence Hub enabled, competencies once associated with a form and then deleted
from the Attributes Library can be reported in Story reports.
Related Information
Table Reports
Stories in People Analytics
You can report three different types of rating description in table reports.
• Rating description columns (default locale): Show the rating descriptions that were configured using the
Rating Scales tool, in the rating scale default locale.
Also, all the matrix grid scale columns show the latest description for in-progress forms, which were configured
using Admin Center Matrix Grid Scale , in the company default locale.
• Rating description columns (locale specific): There are 20 columns for localized descriptions. These column
names are appended with the text (Locale Specific) and appear next to the column with default locale.
Note
Out of these 20 columns, 13 columns are scale-based columns, which were configured using Rating Scales.
Seven are template-based, also known as Adjusted columns, which were configured in the template using
Rating Scale Adjusted Calculation.
• Unadjusted rating description columns (locale specific): There are four columns for localized scale-based
descriptions. These columns are prefixed with the text Unadjusted and are shown just after the (Locale
Specific) column.
The following table lists the three different types of rating description columns:
Rating Description Columns (Default Rating Description Columns (Locale Unadjusted Rating Description Columns
Locale) Specific) (Locale Specific)
Competency Official Rating Description Competency Official Rating Description Unadjusted Competency Official Rating
(Locale Specific) Description (Locale Specific)
Adjusted Overall Goal Rating Description Adjusted Overall Goal Rating Description
(Locale Specific)
Goal Official Rating Description Goal Official Rating Description (Locale Unadjusted Goal Official Rating
Specific) Description (Locale Specific)
Overall Performance Rating Description Overall Performance Rating Description Unadjusted Overall Performance Rating
(Locale Specific) Description (Locale Specific)
Section Rating Label Section Rating Label (Locale Specific) Unadjusted Section Rating Label (Locale
Specific)
Learn about known limitations of the rating description columns in table reports.
• If the rating descriptions are not available in the logged in user's locale, they are shown in the default locale in
scale-based columns.
Note
If the default company locale changes, the matrix grid scale localized columns might be affected.
• If you configure filters for the localized columns and use unadjusted rating descriptions, the columns might
show duplicate and unsorted descriptions.
Recommendation
We recommend that you use localized columns for report generation. When applying a filter to a rating
description, you should use the default rating description column.
• The Sort columns and Group by (in report generation) actions might not show the correct sorting order when
locale-specific columns and unadjusted rating descriptions are used.
Recommendation
We recommend that you use the default rating description columns for the Sort columns and Group by
actions on rating description columns.
• If the rating description of the rating scale or matrix grid rating scale is changed after the form is completed
or launched, the latest description will be used for localization. However, this might lead to data discrepancy
between the rating description on the form and the localized descriptions in table reports.
The route entry table contains details on the route steps of forms in story reports.
The following table explains some route entry columns and values.
Step Start Date Behavior infoOnly If you didn't enforce start date to be ef-
fective, the value shows infoOnly.
Step Due Date Action doNothing If you didn't select the setting to auto-
matically send forms on due date, the
value shows doNothing.
Step Base User user ID If the step role is User (U), UM, UH, UMM,
or UHM, the value shows the user ID of
the User.
Related Information
Migrate completed form data to table reports so that the Matrix Grid Scale rating label is consistent in the form and
table reports.
Prerequisites
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Context
When the form data is synced to reporting, by default, both in-progress and completed forms are included. You can
choose to sync only the completed forms so that even if the Matrix Grid Scale rating label is updated after the form
is completed, there's no discrepancy between the form and table reports.
Procedure
1. In Provisioning, go to Company Settings Ad Hoc Report Builder Performance Management Sync and
choose Sync.
2. In the Create New Job dialog box, under Job Parameters, select Migrate Completed Forms: If enabled, in-
progress forms will not be migrated; only completed forms will be migrated.
3. Choose Create & Run Job.
Learn about what features are available in Performance Management after you migrate to Talent Intelligence Hub.
With proper configurations and permissions granted, users can do the following:
• Provide ratings and comments on skills, and add more skills to the form as needed. When the form is
completed, the skills and competencies, together with their ratings, are updated in the form subject's Growth
Portfolio.
• Use Stack Ranker to quickly review the skill ratings for their direct reports.
• View the last proficiency rating from Growth Portfolio for skills and competencies.
• Access the form subject's Growth Portfolio directly from the form.
• Report on skills by using the Skill table in the Performance Management schema in Story reports. Reportable
details include skill ratings, comments, and rating scale information. Users can further join the Skill table with
the Attributes table in the Talent Intelligence Hub schema to report on skill name, description, and so on.
Related Information
Skill sections are used to evaluate employees' skills during a performance review. The Performance Management
form supports three types of skill sections, respectively for job-specific skills, core skills, and custom skills.
Prerequisites
You've managed the three types of skills properly so they can be autopopulated to the form:
• Job-specific skills: You've mapped skills to the form subject's job role in Manage Job Profile Content.
• Core skills: You've assigned the Core tag to skills in Manage Talent Intelligence Hub.
• Custom skills: In Manage Templates, you've selected the Custom section type and then added skills by
choosing Show advanced options [X] Custom Skill defined. Click to modify . Or, you've had skills specified
in the XML form template with the skill IDs obtained from Manage Talent Intelligence Hub.
Configuration
The fields and options that you can configure for a skill section are mostly the same as those for a competency
section. Refer to Competency Section for more information.
Be aware of the following feature differences between the skill section and the competency section you used before
the migration:
• To add a skill section in Manage Templates, you add an Attribute section and then select Skill for the Attribute
Type field; to add a skill section in an XML form template, you use attribute-type="skill" and the same
snippet for competency-sec.
• The term "category" in form template configuration is called "tag" in Manage Talent Intelligence Hub.
"Category" is used, for example, as a dropdown list label on the Custom Skill dialog and in the category-
filter-opt attribute.
• For skills that are manually added to the form through the picker, users don't see their expected ratings.
• Expected skill ratings can only be shown in the format of normalized scores, such as 4.0. The percentage
format isn't supported.
• Users don't see predefined weights for role-specific skills. This is because in Manage Job Profile Content, you
can't configure weights for skills.
• If Job Profile Builder isn't enabled in your instance, you can't map skills to job roles. Therefore, you can't have
role-specific skills autopopulated to a skill section, and users can't filter skills by job role when they use the
picker to add skills to the form.
• Skill ratings aren't included in the calculation of the OCOC rating.
• Writing Assistant isn't supported in the skill section.
• The following options in Manage Templates aren't supported in the skill section:
• Show behaviors
• Include in overall competency rating calculation
Related Information
Learn about how the configuration of competency sections differs after you migrate to Talent Intelligence Hub.
Prerequisites
You've managed the three types of competencies properly so they can be autopopulated to the form:
• Job-specific competencies: You've mapped competencies to the form subject's job role in Manage Job Profile
Content.
• Core competencies: You've assigned the Core tag to competencies in Manage Talent Intelligence Hub.
• Custom competencies: In Manage Templates, you've selected the Custom section type and then added
competencies by choosing Show advanced options [X] Custom Competency defined. Click to modify .
Or, you've had competencies specified in the XML form template with the competency IDs obtained from
Manage Talent Intelligence Hub.
Configuration
The fields and options that you can configure for a competency section are mostly the same as before. Refer to
Competency Section for more information.
• To add a competency section in Manage Templates, you add an Attribute section and then select Competency
for the Attribute Type field; to add a competency section in an XML form template, you use attribute-
type="competency" and the same snippet for competency-sec.
Related Information
When you've migrated to Talent Intelligence Hub, users can view the last skill or competency rating on the form,
which is the most recent rating that the form subject has received for a skill or competency.
Based on your configuration, the last skill or competency rating is from either of the following:
• Forms based on a specific form template. For information about this source, refer to Last Competency Rating.
Note that you can choose to prepopulate the last skill or competency ratings to rating fields, which wasn't
supported before the migration.
• Proficiency ratings from Growth Portfolio: The last proficiency rating of a skill or competency is displayed
on the Last Rating tab of that skill or competency. Users can go to the form subject's Growth Portfolio to see
exactly where the proficiency rating comes from.
Note
If a form template was previously configured to display last ratings from rating sources in Job Profile Builder,
you need to reconfigure the last rating options. This is because the From Rating Sources option no longer exists.
Reconfiguring last rating options affects all in-progress forms and new forms that are based on the form
template.
Related Information
Configure form template settings to display the last proficiency ratings from Growth Portfolio for skills and
competencies.
Prerequisites
Procedure
Related Information
You can add Growth Portfolio links to forms so that users can view employees' Growth Portfolio when working on
the forms.
Prerequisites
Context
• The Actions dropdown menu that appears in the Route Map section and the top right of the form.
• The description of any form section.
Procedure
• To add a Growth Portfolio link to the Actions dropdown menu, do the following:
Selected features of Performance Management are available for users in the SAP SuccessFactors Mobile
application.
Recommendation
We recommend that before you adopt this feature, learn about current feature support, and test it in your
Preview environment.
• View and provide ratings and comments for performance goals, development goals, and competencies in the
form.
• View summary section's calculated or adjusted calculated form rating and provide manual overall rating.
• View signature section, signers, and date of signature.
• Route, sign, and complete forms.
Enable the mobile performance review feature so that users can review performance on their mobile devices.
Prerequisites
• Performance Management
• Mobile PM Reviews
Remember
As a customer, you don't have access to Provisioning. To complete tasks in Provisioning, contact your
implementation partner or Account Executive. For any non-implementation tasks, contact Product Support.
Procedure
Results
Learn about all the Performance Management features that are supported on mobile devices.
Performance review features are supported, partially supported, or not supported in the mobile applications.
Android Supported
Form Sections
Custom Supported
Goal Competency Summary Partially supported See Goal Competency Summary Section
on this page for details.
Completion Supported
Routing Actions
User Roles
Min/max character limit options Partially supported Character limit validation on submission
is supported. It's not possible to indicate
whether users are within or beyond the
character limit in real time.
Item Comment Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Section Introduction Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Section Comment Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Item Comment Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Section Introduction Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Section Comment Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Item Comment Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Section Introduction Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Section Comment Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Summary Section
Section Introduction Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Section Comment Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Signature Section
Section Comment Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Custom Section
Section Introduction Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Custom Element: Text Area Partially supported Plain (unformatted) text only. See the
Rich Text Editor section on this page for
expected behaviors.
Cache data availability Not supported Cache data availability means that users
can view cache data while offline.
Rich Text Editor (RTE) or text formatted with an RTE is not supported in mobile performance reviews.
If you're using RTE for comment fields, be aware of the following impacts:
• If text is formatted using RTE on the web, the text is displayed without any formatting when viewed in the
mobile application.
• If text is formatted using RTE on the web, and then edited in the mobile application, the formatting is lost in
both the web and mobile applications and HTML tags are visible.
Adding custom code, java script, CSS & HTML within the SAP SuccessFactors application is not supported by our
system.
Consider the following before you add any custom code, java script, CSS & HTML in the SAP SuccessFactors
application:
• We do not test the impacts of any custom code. It's unrealistic to account for the unlimited possibilities that
using HTML or any other code might present to the end user's browser.
• The code could be exported anywhere within a non-HTML-rendering environment. However, HTML would never
work in table reports, Detailed Document Search, or a Competency Library export, because there's no HTML
parsing involved.
• You should know that HTML is not supported anywhere in the product, but you can test any customization to
determine if the customization function sufficiently for your purposes.
• Some areas of the product actively sanitize or strip out certain code, including java script, which may
effectively cause it to break, give errors, or not function at all. This is for security reasons to prevent malicious
code, or code that can negatively impact performance, from accidentally or purposely being inserted into the
SAP SuccessFactors application.
• Special formatting from programs such as Microsoft Word actually use custom HTML coding when cut
and pasted into our application, so pasting content into your forms, competencies, goal plans, can cause
unexpected operation and issues.
Caution
You can add custom code and HTML into the system at your own risk. However, you're fully responsible for
testing and validating that no unexpected results are impacted by code. Also, SAP SuccessFactors makes
no representation to support this code, or commitments to change our product in any way to support the
expected functionality you require.
However, you may find that custom code and HTML function for a time and due to our regular product releases
or updates, they may break or stop working as expected without warning. SAP SuccessFactors may release
new updates to the product that negatively impact your custom code, as again we are not responsible for
performing any tests on your code. We also make no commitments to update the product to support the
previously working HTML as we don't consider these impacts as a product bug.
You can use the following supported HTML formatting to edit Performance Management forms: p, a, strong,
em, u, ol, ul, li, font, img, blockquote.
Data protection and privacy features work best when implemented suite-wide, and not product-by-product. For this
reason, they’re documented centrally.
The Implementing and Managing Data Protection and Privacy guide provides instructions for setting up and using
data protection and privacy features throughout the SAP SuccessFactors HXM Suite . Please refer to the central
guide for details.
Note
SAP SuccessFactors values data protection as essential and is fully committed to help customers complying
with applicable regulations – including the requirements imposed by the General Data Protection Regulation
(GDPR).
By delivering features and functionalities that are designed to strengthen data protection and security
customers get valuable support in their compliance efforts. However it remains customer’s responsibility to
evaluate legal requirements and implement, configure and use the features provided by SAP SuccessFactors in
compliance with all applicable regulations.
Related Information
Identify which data purge function in the Data Retention Management tool meets your data protection and privacy
requirements.
The Data Retention Management tool supports two different data purge functions: the newer data retention time
management (DRTM) function and legacy non-DRTM function.
Remember
We encourage all customers to stop using the legacy purge function and start using data retention time
management (DRTM) instead. To get started using this and other data protection and privacy features, refer to
the Data Protection and Privacy guide.
Note
If you are using the legacy data purge function, you can only purge a calibration session when there is at least
one facilitator assigned to the session.
Restriction
Be aware that the legacy data purge function may not meet your data protection and privacy requirements. It
doesn't cover the entire HXM Suite and it doesn't permit you to configure retention times for different countries
or legal entities.
In the longer term, we recommend that you also consider adopting the newer solution. In the meantime, to use
legacy data purge, please refer to the guide here.
Get an overview of potential problems and errors in your configuration that you can try to solve yourself before you
contact Product Support about an issue.
Prerequisites
Tip
Refer to Guided Answers for the Check Tool for a guided navigation through the available check tool checks
and more information on each check.
Context
The check tool provides an overview of the issues found in the system. New checks that are being added in a new
release go through a first initial run to return a result. After the initial run, checks are run on a regular basis (at least
monthly). We recommend you open the check tool after the upgrade to a new release to see if issues have been
found by new checks.
In addition to these runs performed by the system, you can also run individual checks after you made changes
to the system, for example, after updating data models or picklists. For more information, refer to the application-
specific documentation.
Procedure
The Check Tool page opens displaying the results of the first tab System Health.
Tab Description
To display all checks, select all result types in the Result Type
search filter and select Go.
Migration Displays the migrations that are still pending, either because
the check tool couldn't automatically migrate all issues or
because new issues have been found after the last run. We
recommend you solve these in a timely manner.
Note
Validation checks require one or more parameters for
execution, therefore we can't run these checks automat-
ically. You need to enter input parameters and run the
corresponding check manually to get results.
The detail view opens to the right side of the screen with more information on the check and on how to solve
the issue.
4. Evaluate the results and resolve the issues. If the check provides a quick fix that you can use to immediately
correct issues found during a check run, select the Quick Fix button.
5. If you encounter an error you can’t resolve, contact Product Support by creating a ticket.
Next Steps
To verify that you've solved the underlying issue, select the checkbox for the corresponding checks and choose Run
Checks. You can also wait until the next automatic run to see if the issue has been solved.
Note
If the check you selected requires one or more prechecks (checks that need to be run successfully first), the
prechecks are run first even if you haven't selected them.
The SAP SuccessFactors check tool helps you identify and resolve issues when your system doesn’t work as you
expect.
If your SAP SuccessFactors applications are behaving in unexpected ways, it is likely that it has a configuration
or data conflict: you have some data that is inconsistent or a configuration error. The check tool quickly identifies
these types of problems so that you can avoid support tickets. You might still need to create a support ticket if the
problem is severe, but even in severe cases, the check tool can save you time because it can export the results of
the check and your configuration for Product Support. The support engineer, therefore, can identify the issue more
quickly.
• A list of issues in your configuration or data and the severity of each issue.
• A solution or recommendation to address the issue.
Trigger the execution of individual checks to find potential issues in the system, or to check if an issue has been
solved in the meantime.
Prerequisites
Context
In addition to the job runs performed automatically by the system, you can also run individual checks. For example:
Procedure
The Check Tool page opens displaying the results of the first tab System Health.
2. Depending on the check type of the check you want to perform, select the corresponding tab.
A list of checks is displayed in the results table according to the predefined selection criteria.
3. Optional: If the check you're searching for is not listed in the results table, adjust the selection criteria and
choose Go.
You get a list of checks that fulfill the selection criteria you've entered.
4. Select the corresponding checks, and choose Run Checks from the top right of the results table.
Note
Please note that for checks on the Validation tab, you can only select one row at a time. Execution of
multiple checks at once is not possible.
Also, for validation checks you need to enter the required input parameters when running a check.
Note
If the check you selected requires one or more prechecks (checks that need to be run successfully first),
the prechecks are run first even if you haven't selected them.
Next Steps
The check type groups those checks that have a common purpose. On the Check Tool page, each tab represents a
check type.
System Health Checks that run without parameters and • Automatic initial run at the begin-
check configuration and data issues that
ning of a new release
need to be fixed.
• Periodic runs (usually monthly)
The predefined selection criteria displays
only those that have returned errors or
warnings after the last run. We recom-
mend you solve these in a timely manner.
Migration Checks that perform an automatic mi- • Automatic initial run at the begin-
gration of features. ning of a new release
Validation Checks which need one or more parame- Only triggered through user
ters for execution, for example:
• A specific template
• A specific user
• A specific time frame
After you run checks in the check tool, it returns the results of the check so that you can resolve issues that it
found.
The results of a check are displayed in the Result column. If you run the checks multiple times to see how you’re
resolving issues, you can select a previous result from the History dropdown list.
Note
To display the History dropdown list, click on a check. On the details screen that opens on the right side of the
page, expand the header. The History dropdown list is directly below the check title.
Result Action
No issues found If the tool can’t find issues, you see a green check mark in the Result column.
Issues found If the tool finds issues, it reports the number of issues and a yellow warning icon or a red alarm
icon.
• The yellow icon indicates a low severity issue. The system proposes a solution.
• The red icon indicates a high severity issue. You must take action, which could include
creating a support ticket.
Pending migrations If the tool finds pending migrations that need to be completed by the user, you can see a yellow
warning icon or a red alarm icon in the Status column on the Migration tab.
Completed If the tool finds no issues with migration, or the migration has already been completed, you see a
green check mark in the Status column on the Migration tab.
Note
• Select the Export Results button to download the check results. Ensure you run the check before exporting
the check results. If not you can view only the first 100 check results.
• The downloaded check result table can display a maximum number of 10,000 rows.
Related Information
Creating Product Support Tickets from the Check Tool [page 326]
When the check tool reports a serious issue that you can't solve, you might need to contact Product Support. You
can create a support ticket from within the check tool.
Prerequisites
You've run the check tool. You can find the check tool by going to Admin Center Check Tool . You create the
ticket from the details page of the tool.
The detail view opens to the right side of the screen with more information on the check and on how to solve
the issue.
2. On the Result tab, scroll down to the results table to look for the errors you want to report on.
You usually contact Product Support for high severity issues not low severity issues.
3. On the Check Information tab, under Need Assistance?, copy the component ID.
The check tool includes a quick fix feature that you can use to immediately correct issues found during a check run.
Prerequisites
The checks which you want to solve with a quick fix have run and provide a check result with error or warning.
Procedure
The details screen opens on the right side of the page with more information about the check. If the check
includes a quick fix, the Quick Fix button is displayed on the Result tab, under Proposed Solution.
3. Choose Quick Fix to start fixing the issue.
A third screen opens to the right side, with step 1, called Select Correction, that shows one or more corrections
for the issue.
4. Select the correction you want to carry out and choose Step 2 to proceed to Final Approval.
In the Final Approval step, you can opt to change your mind and not carry out the fix.
5. If you want to proceed, choose Step 3.
14.2 Exports
Export the configuration information from your system and attach it to the Support ticket created from the check
tool. This information can help Support identify the issue of a check you can't solve yourself.
Prerequisites
You have the Administrator Permissions Check Tool Allow Configuration Export permission.
Context
Note
Procedure
The legacy check tool UI opens with a list of all applications for which you can use the check tool.
3. Select the corresponding application.
If the application has the export configuration feature enabled, you can see an information message at the
bottom of the page with a link.
4. Choose the Export Configuration link in the information message.
Results
The system downloads a file with the configuration information for the application you’ve selected.
Attach the downloaded file to the Support ticket you created from the check tool.
After you run checks in the check tool, you can export the results.
Context
• Ensure you run the check before exporting the check results. If you don't do this you can view only the first 100
check results.
• The downloaded check result table can display a maximum number of 10,000 rows.
Procedure
On the Result tab, select the Export Results button to download the check results.
Get an overview of all checks available in the system by exporting a CSV file.
Procedure
A CSV file with all checks available in the system is downloaded, including check descriptions and application
area.
Note
The list includes also checks that you can’t access from the user interface if you don’t have the
corresponding applications set up, or if you lack the required permissions.
The Get form template rating permissions check allows you to identify which rating option and field permissions
are configured in a section within a form template. You then understand how the configured field permissions work
differently from the expected behaviors of a specific rating option.
There are four rating options supported in Performance Management, which affect whether a role can view or
edit a certain rating field in the form. Based on the rating option and field permissions you've configured for a
template section, the following table shows the possible check results about check item, check message, and
validation point. The Check Item column shows the fields for a rating option. The Check Message column gives you
an explanation as well as suggested field permissions for a rating option, while the Validation Point column contains
the permissions that you've configured.
Remember
This check returns the field permissions that have been explicitly defined in field, role, and type within a
template.
Rating Option Check Item Check Message Validation Point Additional Note
0 item-rating All the users with per- These are the permis-
mission shares one rat- sions the following roles
ing box for each item. have for item-rating:
This is known as the XXX
rating of record, also
referred as the item-
rating. Only the rating
of record field (item-
rating) is displayed
and is editable by any
user with write permis-
sions for the field. The
first user can set a rat-
ing of record until the
next user changes it.
The last user in the
route map with write
access has final say
over the rating of re-
cord.
1 item-rating and Everyone is able to edit A write permission set • Currently, the val-
item-cmt-rating the rating of record field in item-cmt-rating idation point will
(item-rating) until and item-rating. The show up, only
the fields are permis- ideal configuration for when a role has
sioned. For users updat- the employee role is to been granted a
ing the rating of record grant read or none per- write permission
field, the last user in mission to the rating in both item-cmt-
the route map with per- of record field (item- rating and item-
mission to this field will rating) which will pre- rating. You can
provide the final rating vent the employee from also find the ideal
of record for the item. providing the rating of configuration in the
In addition to the rating record (item-rating) Validation Point.
of record field, the em- as well. • The availability of
ployee is also able to comment rating
edit the unofficial user field is not only de-
rating field (item-cmt- cided by rating op-
rating). tion and its field
permissions, but
also by comment
settings. For exam-
ple, if the user has
a permission to
give comment rat-
ing, but the com-
ment field is not
configured, then he
or she still cannot
access the com-
ment rating field.
2 item-rating and Everyone is able to A write permission set • Currently, the val-
item-cmt-rating edit both the rat- in item-cmt-rating idation point will
ing of record field and item-rating for show up, only
(item-rating) and the following roles: XXX when a role
the unofficial user rat- has been granted
ing field (item-cmt- a write permis-
rating) until the fields sion in item-cmt-
are permissioned. With rating and item-
Rating Option 2, config- rating.
uration of the roles that • The availability of
determine the rating of comment rating
record is accomplished field is not only de-
by putting permissions cided by rating op-
on the rating of record tion and its field
field. permissions, but
also by comment
settings. For exam-
ple, if the user has
a permission to
give comment rat-
ing, but the com-
ment field is not
configured, then he
or she still cannot
access the com-
ment rating field.
Related Information
Learn about changes to the documentation for Performance Management in recent releases.
2H 2023
New Users can now use the latest version of Enabling Latest Version of My Forms
the My Forms page. This feature is ena- Page [page 249]
bled by default.
New Users can now see some visual enhance- Enabling User Experience Enhance-
ments to forms. ments to Forms [page 249]
New When you use Rating Option 2 for a form Field Permissions [page 76]
template, you can now hide unofficial rat- Rating Options [page 47]
ing fields from users who provide official
ratings, without hiding the Ratings from
Others tab. This is done by configuring the
Unofficial User Rating field permission.
New With the latest Goal Management ena- Working with Goals on Forms [page 272]
New If you've migrated to Talent Intelligence Last Skill or Competency Rating [page
Hub, users can now view the last skill or 302]
competency rating from Growth Portfolio. Selecting Growth Portfolio for Last Skill
or Competency Rating [page 303]
New Users can now receive Performance Man- Performance Management in the SAP
agement notification cards in Microsoft SuccessFactors App [page 292]
Teams.
Added We added a note that O role can't add, Roles [page 29]
edit, or remove goals on the form.
Added We added a note that F role isn't sup- Goal Section [page 43]
ported in the latest Goal Management.
Added We added a note that if you enabled Email Notifications [page 194]
Added We added information about using Story Audit Trail [page 206]
reports to report on audit trail records of
form completed steps.
Changed We corrected a related link about setting Performance Potential Summary Section
filters to determine who should be shown [page 64]
on the chart of performance and potential
ratings.
Changed We updated the DTD file download path. DTD for Form Templates [page 91]
Changed We've moved the Change History to the Overview of Performance Management
end of the guide. [page 8]
1H 2023
New The Performance Potential Summary Sec- Mobile Performance Management Fea-
tion is now available in iOS and Android ture Support [page 307]
SAP SuccessFactors Mobile apps. We
changed this section's mobile status to
"Partially supported" and added details.
Changed We updated the note in the Context sec- Enabling Automatic Fixing of Document
tion which now specifies a preventative Transfer and Change Engine Issues
measure against excessive email notifi- Caused by RBP Refresh Failures [page
cations. Previously, we recommendeded 193]
that you manually disable relevant email
notifications before enabling this feature.
Added We added a note that you need to specify Configuring a Scorecard Block in People
a process for the field Include talent data Profile [page 277]
from this process if you want to show nor-
malized ratings in People Profile.
Changed We removed information about Enable Form Template Settings [page 34]
Auto Logout at Session Timeout as this
setting is no longer available.
Changed We corrected a note that forms in the Per- Performance Management Blocks [page
formance History block in People Profile 275]
are sorted alphabetically by form title in
an ascending order.
Changed We specified that the Edit Introduction Editing Custom Sections and Custom
Texts step is available only when you se- Fields When Launching Forms Now
lect Now as the launch date. [page 253]
New You can now disable the Review Performance Management on the Home
Your Performance and Review Employee Page [page 291]
Performance home page cards, so we up-
dated the prerequisites for showing these
cards.
New You can now enable participants of a Adding Growth Portfolio Links to Forms
performance review to view the employ- [page 304]
ee's Growth Portfolio through links on the
form.
New You can now enable automatic daily fix- Enabling Automatic Fixing of Document
ing of the Document Transfer and Change Transfer and Change Engine Issues
Engine issues caused by RBP refresh fail- Caused by RBP Refresh Failures [page
ures. 193]
Added We added information to clarify the re- Team Overview [page 224]
ports users see in Team Overview.
Added We added a note that with Rating Option Enabling Get Feedback [page 210]
3, people who're invited to give ratings
and comments on forms can give com-
ments only.
Added We added more information about im- Importing Overall Scores [page 268]
porting overall scores, including use
cases, column descriptions and examples.
Changed We removed a list of custom roles that are Roles [page 29]
used only in Recruiting.
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:
• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.
Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.