SF CareerDevelopment en
SF CareerDevelopment en
4 Configuring Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1 Template Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5 Development Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.1 Development Goal Plan Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.2 Working with Goal Plan Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Basics About Goal Plan Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Permissions for Goal Plan Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Importing a Goal Plan Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87
Configuring Goal Plan Templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
5.3 Configuring Email Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.4 Development Goal Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Importing Development Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
CSV File for Development Goal Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.5 Managing Development Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Importing and Exporting Learning Activity Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Importing and Exporting Competency Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Managing Competency Mappings with Admin Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.6 Enabling Development Goals on the Detailed 360 Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
5.7 Configuring Development Goals Block in People Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Configuring Template to Show All Development Goals in the Block. . . . . . . . . . . . . . . . . . . . . . . . . 118
5.8 Reporting on Development Goals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Syncing Development Goal Data to Table Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.9 Development Goals on Performance Management Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
11 Mentoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Career Development Planning enables employees to benefit from a wide range of employee development and
career planning activities, and provides managers with standardized methods to track the success of their direct
reports.
Note
This is an SAP SuccessFactors Business Beyond Bias feature. Use it to support processes that detect, prevent,
or eliminate the influence of bias, helping you achieve your diversity and inclusion goals.
Consisting of various development-related features, Career Development Planning provides tools and opportunities
for the following areas:
• Personal Growth
• Undertaking relevant development activities
• Ensuring follow-through on development plans
• Career Planning
• Identifying interesting future job roles
• Researching the skills and competencies needed to perform in those roles
• Corrective Remedies
• Closing competency gaps with time-bound development plans
• Succession Candidates
• Linking to development plans and career notes from Succession Planning
• Development Relationships
• Connecting employees of different career levels in a development relationship where a more experienced
person mentors a less experienced person
To help you with your implementation, we recommend the following implementation sequence.
Select available settings in Provisioning to enable the features of Career Development Planning.
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 Technical Support.
Procedure
Setting Description
CDP Full (Development Plan) This option is required for selecting the Enable Development
Plan V12 option.
Enable Development Plan V12 Enables Development Plan v12. This option requires the se-
lection of the CDP Full (Development Plan) option.
Enable Career Path V2 Enables Career Path v2. If not selected, customers can use
Career Path v1.
Use default value for required field validation Do NOT enable this option. If this option is enabled, when
users change the status of learning activities to completed,
the system compares the current value of each field with
the default value in the template and reports errors. Default
values are treated as mandatory fields.
Enable Add Learning Activity Manually Enables users to create custom learning activities in a devel-
opment goal plan.
When you set up Career Development Planning, it's important to grant role-based permissions to right people.
Administrators with required permissions can manage and configure various features in Career Development
Planning. Users with required permissions can access and use the various features.
To see a full list of the permissions for Career Development Planning, refer to List of Role-Based Permissions by
using filters and key words.
Related Information
Configure the templates required for Career Development Planning features to define settings, permissions, and so
on.
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 Technical Support.
Context
The following features require template configuration before you use them:
• Development Goals
• Learning Activities
• Career Worksheet
Procedure
Next Steps
For more information on each template, refer to respective topics in Related Information.
Users can create development goals for their career development. They can also add competencies and learning
activities to development goals to guide their growth.
A development goal plan template, specified in an XML file, defines the categories and fields of users' development
goals.
Development goal plan templates are similar to goal plan templates in Goal Management. For more information on
configuring templates, such as configuring elements and fields, refer to Working with Goal Plan Templates.
Note
Only one learning activity template can be active at a time. Make sure your active development plans
always reference the latest default learning activity template. Otherwise, when a new default learning
activity template is introduced, existing learning activities disappear from existing development plans.
• Cascading and aligning are not supported in development goals. Remove the following permissions from your
template:
• cascade-push
• cascade-pull
• cascade-align
• unalign-parent
• unalign-child
• You can define various goal statuses. Note that the last status, regardless of the name, would be considered as
one that indicates completion of the goal. For goals of this status, no more learning activities can be created.
Therefore, make sure that the Completed status is always the last status on the list.
• When you add custom fields, do not use punctuation or any special characters, for example, "-" or "_", in field
IDs. Spell check is not supported in custom fields with IDs that contain punctuation or special characters.
• In most cases, customers have a single development plan instead of one plan per year. Development goals,
unlike performance goals, frequently span multiple years, especially as career-oriented features are added
to the product. Customers who want to separate completed goals from in-progress goals, can use goal
categories to achieve this. Additionally, if customers use the Career Worksheet, it can only be linked to a
single development goal plan template.
• To make development goal fields visible in People Profile, add the show-in-pp3=”true” attribute to the
field-definition element.
• If you've configured goal plan states, note the following user permissions for activities and learning activities:
• If users can't edit goals according to the setup of goal plan states, they can still create activities with the
Continuous Performance Management permissions.
• If users can't edit goals according to the setup of goal plan states, they can still add and remove learning
activities according to the permissions defined in the learning activity template.
• If users can't view goals according to the setup of goal plan states, they can't view associated learning
activities either.
• The comments field isn't supported in Mobile apps. If you're using Mobile apps for development goals, remove
the comments field definition from your template.
Related Information
A goal plan template is specified in an XML file, defining categories and fields for users' goal plans.
When you edit goal plan templates, make sure that you use the correct HTML formatting.
Note
SAP SuccessFactors makes no commitments to any support services for customized HTML formatting. Test
and validate your customized HTML formatting.
• File header
• Template Configuration Options containing Goal Plan Data including:
• Goal plan id
• Internal name of the goal plan
• Optional description of the goal plan
• Last-modified date
• Start date of the goal plan
• Due date of the goal plan
• An option to automatically number goals
• An option to define goal categories and a default or catch-all category
• (For performance goals only) An option to use the Goal Wizard
• Options to replace text
• (For performance goals only) An option to use a goal library
• Definition of the fields to be used in the goal plan and the order in which they're displayed
• Permission settings for modifying a goal plan
• Definition of the goals on a Performance Management form layout
• (For performance goals only) Metric lookup tables
• (For performance goals only) Rules
• (For performance goals only) Calculations
The Document Type Definition (DTD) file for the SAP SuccessFactors Goal Management 4.0 (objective-
template_4_0.dtd) defines the structure and all legal elements and attributes of the goal plan template XML
file.
Because not all of the attributes are included in the default XML file, you can refer to this DTD file to find additional
required attributes and the correct order.
To download the latest DTD file, go to Software Center . Navigate to INSTALLATION AND UPGRADE, select DTD
Configuration Files, and choose Download Basket.
The file header is the first element in the goal plan template.
The file header declares the DTD for the SAP SuccessFactors Goal Management 4.0 deployment descriptor. All
such deployment descriptors must include a DOCTYPE of the following format:
The <obj-plan-template> tag is the root element of a goal plan template. This tag contains various elements
and attributes.
The definition for the basic <obj-plan-template> tag in the DTD file is as follows:
This table describes elements that you can specify in the <obj-plan-template> tag.
obj-plan-id The unique number that identifies the Numbers are assigned as follows:
goal plan
• 1–1000 for TGM Performance Goal Plans
• 2001–3000 for CDP Development Goal
Plans
• 4001–5000 for Learning Activity
• 5001–5099 for Career Worksheet
obj-plan-name Name of the goal plan This name appears in the UI. The user selects
the name in a dropdown list.
Note
Do not include special or non-English
characters within the obj-plan-name
tag. For example, # or é. Otherwise, you
might encounter errors when you export
the goal plan.
obj-plan-desc Goal plan description The description does not appear in the UI.
obj-plan-start Start date of the goal plan Format must be MM/DD/YYYY. This element
establishes the default value for the start date
for each goal.
obj-plan-due Due date of the goal plan Format must be MM/DD/YYYY. This element
establishes the default due date for each goal.
obj-plan-numbering Option to automatically number goals For further information, see Enabling Auto-
matic Goal Numbering [page 93].
add-wizard (For performance goals only) Option For further information, see Adding Goal Wiz-
to use the Goal Wizard ard.
text-replacement Option to replace text See the example in Text Replacement in a Goal
Plan Template [page 35].
obj-library (For performance goals only) Option For further information, see Mapping of Goal
to use a goal library Library Content to Goal Plans.
category Option to define goal categories For further information, see Defining Category
and Default-Category [page 91].
default-category Option to define a default or catch-all For further information, see Defining Category
category and Default-Category [page 91].
field definition A list of general permissions For further information, see Goal Plan Tem-
permission plate Fields [page 60].
field-permission A list of goal field permissions For further information, see Goal Plan Tem-
plate Fields [page 60].
plan-layout The layout specification of a goal plan For further information, see Goal Plan Tem-
plate Fields [page 60].
form-layout Option to define how goal plan fields For further information, see Defining Goal Plan
appear on a Performance Manage- Field Layout in a Performance Management
ment form Form [page 100].
learning- (For development goals only) Option For further information, see Development Goal
activities template-id to associate a goal with learning ac- Plan Templates [page 25].
tivities
This table describes attributes that you can specify in the <obj-plan-template> tag.
Note
In the goal plan XML tem-
plate, alerts can be config-
ured to display by default.
Alerts appear when any of
the following events occur
on the goal plan:
(For performance goals only) true Allows the goal administrator false
allow-group-goal to create and assign group
goals. This attribute enables
goals for workgroups who re-
port to the same manager.
(For performance goals only) true Creates an icon that links false
goal-tree-link users to the Goal Alignment
Spotlight report directly from
their goal plan.
</obj-plan-numbering>
<text-replacement for="Instructions">
<text><![CDATA[<P>Check out our SuccessFactors website!</P>]]></text>
</text-replacement>
<text-replacement for="category">
<text><![CDATA[Goal Classification ]]></text>
</text-replacement>
<obj-library name="SuccessFactors Library">
<text-replacement for="percentage-symbol">
<text><![CData[]></text>
<text-replacement>
We've made a comparison table for you to find out what elements and attributes are supported in the legacy Goal
Management and latest Goal Management.
Navigation Tips
We understand that some elements and attributes are of your particular interest. To facilitate your search for these
items, you can follow the instructions below to effectively navigate the comparison table:
• switches:
Enter the word “switches” into the search box in the Parent Element column.
• field-definition:
To locate field id, type and other attributes of field-definition, enter the word “field-definition” into
the search box in the Sub-element column. For more details about field id and type in the latest Goal
Management, see Changes to Goal Plan Template in the Related Information section.
To locate sub-elements of field-definition, enter the word “field-definition” into the search box of the
Parent Element column.
• Table fields:
Enter one of the words into the search box of the Parent Element column: “tasks”, “milestones”, “targets”,
“metric-lookup-table” or “certifications”. For more details about table fields in the latest Goal Management, see
Changes to Goal Plan Template in the Related Information section.
Availability
Supported Supported Supported Supported after the uni-
for Legacy for Latest for Legacy for Latest De- versal push
Parent Ele- Performance Performance Development velopment of latest Goal
ment Sub-element Attribute Goals? Goals? Goals? Goals? Management
text- text lang Yes No, except for Yes No, except for Available
replaceme the attributes: the attributes:
nt • for="I • for="I
nstruc nstruc
tions" tions"
• for="c • for="c
ategor ategor
y", y",
which which
you can you can
configure configure
using the using the
admin admin
tool tool
Manage Manage
Language Language
s s
Related Information
Switches are used to enable or disable features in a goal plan template. The default value of the switches is off.
Switches Descriptions
<switches>
<switch for="percentage-value-over-100" value="on"/>
Related Information
Configuring Template to Show All Development Goals in the Block [page 118]
Note
This is an SAP SuccessFactors Business Beyond Bias feature. Use it to support processes that detect, prevent,
or eliminate the influence of bias, helping you achieve your diversity and inclusion goals.
Remember
This code snippet is a sample configuration. The exact configuration depends on your system settings.
• You must define all fields that are used in the plan in this section.
• The order in which the fields are defined determines the order in which they're shown in the goal plan and goal
edit window.
• When you add a new field or remove an existing field from the goal plan template, remember to add or remove
the field references in these sections of the template:
Remember
When you delete a field from the goal plan template, using either the Admin Center Manage
Templates tool or the XML file, do remember to delete the corresponding permissions of that field
from the <field-permission> section of the goal plan template. If you delete a field without deleting its
permissions from the goal plan template, you might encounter errors while using the goal plan.
• When you decide which fields are included in a goal plan, be aware of the following:
• It's important to determine what portlets under Summary on the Goal Plan page are used for reporting on
goals. The Objective Status portlet uses the Status field. The Objectives by Completion and Objective Due
Range portlets use the % Complete field and the Due field. They don't recognize completed goals because
they don't use the Status field.
• The Goal List report on the Goal Plan page displays fields set with certain defaults that individual users can
reset. The administrator can't set these defaults for the entire organization. If users deselect fields through
Display Options, these fields disappear from the report.
The tables describe subelements and attributes of fields in a goal plan template.
<field-definition> Subelements
Fields in a goal plan are controlled by <field-definition> elements in the goal plan template XML file. Each
field has its own unique field definition. <field-definition> includes the following subelements:
Subelements Description
field-label The field label that is displayed in the goal plan template. It can
be configured to use whatever term the customer wants.
In addition to the subelements, you can also configure attributes for a <field-definition> element.
type • text: a single line of text The type of the field. This at-
(nontyped) tribute is a combination of the
stored-data type and UI hints.
• textarea: multiple
lines of text (nontyped) We strongly recommend that
• date: a date (MM/DD/ you use the types as illus-
YYYY) (typed) trated in the XML because
• percent: an unformat- these types have been heav-
ted number (no "%" sign) ily tested and approved.
(typed) You must enter dates in
• enum: an enumerated date fields and numbers
type (shown as a pull-
in percent fields (numbers
down list; see Enum
are formatted according to
Fields [page 72] for de-
tails) field format and ap-
• table: a table of data pended with a "%" sign.)
Note
Whenever you use this field, the
field value appears in a larger font
on the application UI only when the
field is positioned as the first column
within the goal plan table. However,
when you print the goal plan, this
field value always appears in a larger
font regardless of the field's position
within the goal plan table.
state enum (use text and textarea with Typically presented as a dropdown list of
care) values with colors to report the goal state
or status. Used as such in dashboard re-
ports. Limited to 128 characters. Often
labeled Status.
Note
If you define this field with
type="percent" and want users
to be able to enter a value
greater than 100 in this field, set
the value of the percentage-
value-over-100 switch to on in
the template XML.
Remember
• If weight is configured as
enum type, the system doesn't
support min or max weight
warnings and its value can't be
used in calculated ratings.
• If weight is configured as the
text type, the text value en-
tered is used verbatim; and
if configured as text or
textarea, this field isn't sup-
ported in Table Reporting be-
cause the Sub Domain Schema
doesn't support nonnumeric
values for this field.
Note
The field is introduced as a Mission
Statement, however, it can be reused
for other purpose with a different
field-label.
Consider the following scenarios when you configure the field length:
• Empty value: Initialized as "0" at backend. Uses default values as described in the following table.
• 0 < X < 4000: Uses customized value "X".
• >4000: Initialized as "0" at backend. Uses default values as described in the following table.
In general, all text fields have a default maximum length of 4000 characters. Some exceptional field types have
different maximum default lengths. Here are the corresponding default maximum length for the respective field
types:
Note
If the content that you enter in a text field is without natural spaces, the user interface doesn't wrap the text.
For example, if you enter "testesttesttesttesttesttesttestesttesttesttesttesttest", the user interface treats the
content as a single word and introduces a horizontal scroll bar instead of wrapping the text.
Learn about the supported table fields: Task, Milestone, Target, and Achievement Lookup.
A table field is a collection of fields that can be repeated for each goal. For example, each goal may have several
Tasks or Milestones associated with it. Tables can be renamed. For example, you can relabel the Task table as
<Subgoals>, <Activities>, or <Notes>.
You can use Permission tags to control who can create, modify, or delete rows of a table within a goal plan. You can
also set access permission for individual table columns.
rating number
weight number
score number
actualNumber number
date date
achievement-text text
rating number
description text
Columns can be arranged in any order. You can add or remove columns as the customer requires, provided that the
column types match those types in the Table Field Types table shown. The date and percentage columns can't be
transformed to text fields.
table-row-label The label displayed on the UI. The word "Add" is always prepended to the label specified. For
example, "Task" is shown as "Add Task".
table-column id The internal name for the field where the data is stored in the database.
Refer to the list of standard field IDs in the Table Field Types table. You can't add custom fields
to a table.
• column-label
• column-description
• type
• default-value (optional)
You can change the values in the label or description attributes but you must not change the IDs
that are referenced because these IDs are recognized by the system.
• width: Specifies the width of the column in characters. For columns of type textarea,
specify a value to provide enough space for the user input. For all other column types,
ignore this attribute.
• validate-start-before-due: Applicable to all table columns that have the field ID
start and type date. If this attribute is set to true, the start date is before the due
date.
Note
Typically, the Milestone table validates that the start date value is earlier than the due
date value. However, because you can relabel table fields as, for example, <target>
and <actual>, the validation may not be desirable. To avoid this, you can set this
attribute to false for the start field.
column-label The label that identifies the columns that appear in a table. You can configure this subelement
to use whatever term the customer wants.
• For fields or columns of type text or textarea, the value is copied directly to the
contents of a field in a new goal, accounting for the locale as specified by the optional
lang attribute.
• For fields or columns of type date, percent, number, or bool, the value is specified in
a nonlocalized format, and the lang attribute isn't allowed.
field-format Defines the format of a field or column. You can specify only the following formats:
Related Information
A field of type enum allows you to specify a dropdown list with all the possible values for the field.
Enum Fields
Subelements Description
enum-value Defines one of the possible values for a field of <type="enum">. The order of the enum-
value subelements in the XML file determines the order in which the dropdown list is dis-
played, and the collation order for sorting by the field.
• The value attribute defines the nonlocalized, internal string, under which the data is
stored. (Use the enum-label subelement to define localized string labels).
• The style attribute optionally defines the background and text color.
enum-label The text that displays in the dropdown list. There must be at least one enum-label subele-
ment defined per enum-value.
<field-
definitionid="state"type="enum"required="false"showlabel="false"viewdefault="on">
<field-label>Status</field-label>
<enum-valuevalue="none"style="background:white;color:black;">
<enum-label>none</enum-label>
</enum-value>
<enum-value value="Will meet target" style="background:green;color:white;">
<enum-label>Will meet target</enum-label>
</enum-value>
<enum-valuevalue="Don't know"style="background:yellow;color:black;">
<enum-label>Don't know</enum-label>
</enum-value>
<enum-value value="Will not meet target"style="background:red;color:white;">
<enum-label>Will not meet target</enum-label>
</enum-value>
<enum-value value="Goal completed"style="background:blue;color:white;">
<enum-label>Goal completed</enum-label>
</enum-value>
</field-definition>
Custom fields aren't initially defined in the goal plan template. These goal field types aren't listed in the DTD, but
they can be defined in the same way as any of the standard fields.
Custom fields can't be of the table type and must be of the following types:
• text
• textarea (with a length limit of 2,000 characters)
• enum
• date
• percent
• number
• link
• bool
reportable fieldX (where X is the ID of Determines which fields are available in the Goal List report.
the field)
At most 20 fields across an entire company can be reportable.
People Analytics is also supported.
Action permissions grant the ability to perform specific actions on a goal plan, such as adding, deleting, or
cascading goals. The <permission> element describes general goal access permissions, and is referred to as an
action permission.
Overview
The following table describes the action permissions that you can configure for goals.
Private access private-access See private goals, that is, goals that
aren't shared or made public.
Note
Editing goals requires the write per-
mission.
Recommendation
We recommend that you list roles for
this permission when defining it.
Import goal import-goal Import the user's goals from another goal
plan.
In this example, employees and their managers can view unshared or private goals.
<permission for="private-access">
<description> Employees and their managers can view unshared or private goals.
</description>
<role-name>E</role-name>
<role-name>EM</role-name>
</permission>
In this example, everyone can create, delete, or move rows of targets, tasks, milestones, or metric lookup tables.
<permission for="create-row">
<description><![CDATA[Anyone can create row.]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="targets"/>
<field refid="tasks"/>
<field refid="milestones"/>
<field refid="metric-lookup-table"/>
</permission>
<permission for="delete-row">
<description><![CDATA[Anyone can delete row.]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="targets"/>
<field refid="tasks"/>
<field refid="milestones"/>
<field refid="metric-lookup-table"/>
</permission>
<permission for="move-row">
<description><![CDATA[Anyone can move row.]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="targets"/>
<field refid="tasks"/>
<field refid="milestones"/>
<field refid="metric-lookup-table"/>
</permission>
In this example, employees can go to their goal plans to upload goals for themselves. Employees' managers can go
to goal plans of their employees and upload the goals for employees.
<permission for="import-goal">
<description><![CDATA[ Employees' manager can import the goals from the goal
plan. ]]></description>
<role-name><![CDATA[EM]]></role-name>
<role-name><![CDATA[E]]></role-name>
</permission>
Roles are established based on what the system knows about relationships as determined by the employee data in
the instance. The <role-name> element defines who receives permissions.
The following table lists the supported role names and their descriptions.
* Everyone
E Employee or owner
EM Employee's manager
ED+ Employee's direct report, all the way down the reporting hierarchy
EH Employee's HR representative
F Form reviewer (Goal access is restricted through a performance form only. Users with this role
can’t leave comments on goals.)
OP (For performance goals only) Objective parent (For example, a project team lead's goal that is
aligned up from a team member's goal)
OC (For performance goals only) Objective child (For example, a team member's goal that is aligned
down from a team lead's goal)
cascader (For performance goals only) The person who is cascading a goal
TA (For development goals only) Talent administrator, or a similar role, who can manage employ-
ees' development goals
To configure this role in development goal plan templates, you need to grant talent admin-
Same as other roles, talent administrators must have the User Search and Goal Plan
Permissions permissions to search for employees and access their development goal plans.
Roles are case sensitive and you must list them in all uppercase except for cascader, which is in lower case.
The following table lists which roles can be assigned access to goal plan features.
Goal Sug-
Plan gesst
Fea- No ed
tures * E EM EMM EM+ ED EDD ED+ EMD EH EX EY F TA Role Roles
View Y Y Y Y Y Y Y Y Y Y Y Y Y Y N E or
pri- EM
vate
goals
Cre- Y Y Y N N N N N N N Y N Y Y N E or
ate EM,
goals or F
De- Y Y Y Y Y Y Y Y Y N Y Y N Y N E or
lete EM
goals
Move N Y N N N N N N N N N N N N Y E
goals
Share N Y Y Y Y Y Y Y Y Y Y Y N Y N E or
or EM
un-
share
goals
Note
• The roles listed are also used to set read and write permissions when accessing goals in an individual's Goal
Plan.
• The following roles have the same level of support:
• EX and EM
• EY and ED
You can add field permissions to the goal plan template in the XML only. Permissions for table column fields are
scanned in XML source order, and the last applicable permission is the one that is used. For regular fields, the
Note
• Consider action permissions when you grant field permissions. Grant users who can create goals the write
permission for all fields or at least all required fields in a goal plan.
• If every individual in a group of people has the same kind of permissions for the same fields, you can put all
permissions within one element.
The following table describes the subelements and attributes inside the <field-permission> element.
type The following three types are available for field permissions:
• none (default). The user can't see or edit the field at all.
• read. The user can see but can't edit fields.
• write. The user can both see and edit fields.
<role-name> Enclose each role that is granted read or write access sepa-
rately within this tag. This tag applies to all permission sections
of the goal plan.
<field-refid> Enclose each field that the role has permission to access sepa-
rately within this tag.
<table-col> Enclose each table column field that the role has permission to
access separately within this tag.
Example
<field-permission type="read">
<description>Everyone can read name and metric for shared goals.</description>
<role-name>*</role-name>
<field refid="name"/>
<field refid="metric"/>
</field-permission>
<field-permission type="read">
<description>Direct reports can see all fields for Manager's shared goals.</
description>
<role-name>ED</role-name>
<field refid="name"/>
<field refid="desc"/>
<field refid="metric"/>
<field refid="state"/>
<field refid="due"/>
<field refid="done"/>
<field refid="tasks"/>
</field-permission>
<field-permission type="write">
<description>The owner, manager, and form reviewer can write to all fields.</
description>
<role-name>E</role-name>
Table column permissions allow you to define permissions for columns in the table.
• Define table column permissions after table field permissions are defined in the XML.
• To hide a table from a role, define none permission at the table field level. Don't define the write permission
for the table at the field level and then set permissions for all table columns to none. This results in the table
header remaining visible.
• For the Achievement Lookup table,
• Define the same set of permissions for the table columns achievement and achievement-text.
• We don't recommend that you grant action permissions to roles that don't have the write permission for all
columns. This can lead to undesirable behavior in the Achievement Lookup table and calculated rating.
The use case is to create a Milestone table with four columns: Milestone, Start Date, Due Date, and % Complete.
The manager (EM) has full access to all columns but the employee (E) only has access to the % Complete column.
In this scenario, the manager is responsible for setting the milestones and the employee only for updating the
milestone percent completion.
<field-permission type="write">
<description>Manager and Employee can write to the milestone table.</
description>
<role-name>E</role-name>
<role-name>EM</role-name>
<field refid="milestones"/>
</field-permission>
<field-permission type="read">
<description>Employee can only read the description, start, and due fields.</
description>
<role-name>E</role-name>
<table-col id="desc" field-refid="milestones"/>
<table-col id="start" field-refid="milestones"/>
<table-col id="due" field-refid="milestones"/>
</field-permission>
Goal plan states provide the ability to have more than one set of permissions. The difference between states can be
subtle or drastic depending on the customer's needs.
You can't have permissions outside of goal plan states. Goal plan states control the action and field permissions
before and after a goal plan is approved.
The order in which available states are defined in the XML of the goal plan template determines the order in which
they're shown in the goal plan.
Allow components of the goal to be locked after an authorized user, such as E and EM, locks the plan.
Procedure
1. Add the <obj-plan-states> element after the last <field-definition> element in the XML of the goal
plan template.
action-label (Only for the legacy Goal Management) Defines the clickable
option name of the goal plan state on the goal plan page.
Example
<obj-plan-states>
<obj-plan-state id="Locked" default="true">
<state-label lang="en_GB">Locked</state-label>
<state-label lang="en_US">Locked</state-label>
<action-label lang="en_US">Lock</action-label>
…
</obj-plan-state>
</obj-plan-states>
The target-state subelement inside the change-state permission defines the goal plan state to which the
goal plan can be switched (that is, Locked state and Unlocked state).
Example
<obj-plan-states>
<obj-plan-state id="Unlocked" default="true">
<state-label lang="en_GB">Unlocked</state-label>
<state-label lang="en_US">Unlocked</state-label>
<action-label lang="en_US">UnLock</action-label>
<permission for="change-state">
<description><![CDATA[Manger can change the goal plan state.]]></
description>
<target-state><![CDATA[Locked]]></target-state>
<role-name><![CDATA[EM]]></role-name>
</permission>
…
</obj-plan-state>
</obj-plan-states>
4. Optional: Repeat the steps to configure multiple goal plan states inside <obj-plan-states>.
You can change the goal plan state of the user when a form is routed to the next step.
Context
When the form moves to a state where it's unlocked, the goal plan is in an unlocked state.
Note
Creating a new form doesn't trigger a change of the goal plan state or put the goal plan back into initial state.
Procedure
1. Add the <obj-plan-state-change> element after the <meta-grp-label> element in the Goal section of
the Performance Management or 360 form template.
target-state Defines the state to which the goal plan can be switched.
Set the value to one of the goal plan state IDs defined in the
goal template.
to-complete-state Specifies whether to change the goal plan state when the
form is routed to the complete step.
on-form-delete Specifies whether to change the goal plan state when the
form is deleted.
Example
<obj-plan-state-change to-step="Step2">
<target-state id="B"></target-state>
</obj-plan-state-change>
You can't specify the to-step attribute when configuring either to-complete-state or on-form-delete
attribute.
Example
<obj-plan-state-change to-complete-state="true">
<target-state id="A"></target-state>
</obj-plan-state-change>
<obj-plan-state-change on-form-delete="true">
<target-state id="B"></target-state>
</obj-plan-state-change>
3. Optional: To change the goal plan state for each route step, add the configuration multiple times.
Example
<obj-plan-state-change to-step="Step2">
<target-state id="B"></target-state>
</obj-plan-state-change>
<obj-plan-state-change to-step="Step3">
<target-state id="C"></target-state>
</obj-plan-state-change>
Import a goal plan template so that users can use goal plan features.
Context
There's no interface in Provisioning that allows you to edit the XML of a goal plan template. Create and edit your
goal plan templates using an XML editor and import the goal plan to see your changes.
Procedure
1. Log in 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 Technical
Support.
6. (For importing a new goal plan template only) Go to Provisioning Company Settings , locate Refresh RBP
Permission Configuration, and choose Refresh.
Note
When importing a modified goal plan template over an existing one, your changes are reflected in the
system right away, even if goals already exist within that goal plan.
Next Steps
If multiple goal plan templates are imported into an instance, to set the default template, select the radio button in
the Default column.
You can configure your goal plan templates to best suit the business needs of customers through both Admin
Center within an instance and in XML.
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 Technical Support.
Context
Many changes to a goal plan template can be made through Admin Center, but all changes can be made within the
XML of a template.
It's best to perform as much of the configuration as possible in Admin Center, and then export the XML file to make
more advanced changes.
Procedure
Configuring Goal Weight Rules and Goal Count Rules [page 95]
Defining Goal Plan Field Layout in a Performance Management Form [page 100]
Use the <form-layout> element to determine which goal plan fields appear and how they're arranged on
the Goal Details tab of a Performance Management form.
Context
Although offers the capability of exporting goal plan templates, we recommend that you maintain a source copy of
your template in a file. By doing so, you can:
• Preserve any comments that you may have added to date and track updates that you make to the template (for
example, a change log)
• Preserve comments in the template that help distinguish one section from another
Note
Comments are stripped from the goal plan template when you import the template and hence any templates
that you export don't include your comments.
1. Log in 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 Technical
Support.
Link fields allow you to set up a goal plan field to point to a URL. Link fields don't display on the performance form,
but can be displayed in the goal plan.
Procedure
Or you can add link fields through the template XML by adding the following sample code:
Sample Code
7. Go to Action Edit development goal , specify the link label and URL.
8. Save your changes.
You can see the link column in the goal plan. Choosing the link label that you specified opens a browser to display
the URL.
Use the category and default-category elements to determine sections of a goal plan to which the goals are
allocated.
Context
The category element defines a top-level category used to segment a goal plan.
The default-category element defines the default or catch-all category. Any goal not matching one of the
explicitly defined categories is placed in this category.
In a goal plan template, defining at least one category element is considered a best practice. It allows customers
to use more of reporting dashboard tiles from the SuccessStore because some tiles require a category to function.
The length limit for values of the ID for both elements is 128 characters.
• If no category element is defined, the goal plan isn't divided into sections.
• If one or more category elements are present in the template, the goal plans based on the template are
divided in sections according to the categories defined. The order of these sections in the goal plan is based on
the order of the category elements.
If you want to have a category pull-down element in the goal plan and don't want to divide the plan into sections,
define a field with the name category.
Note
Don't include the category elements and a field called category in the same goal plan template.
id Defines the internal name that is used to store and identify the
category. This name can't be localized.
Note
The & character is not supported in the attribute. To dis-
play this character in the category label of the goal plan,
use the ampersand wrapped in a pair of quotation marks,
that is, "&".
Procedure
Example
4. Place the default-category element after the last regular category element in the XML of the goal plan
template.
Example
<category id="Customer">
<category-name>Customer</category-name>
</category>
<category id="Financial">
<category-name>Financial</category-name>
</category>
<category id="Learning and Development">
<category-name>Learning & Development</category-name>
</category>
<category id="Internal Business Operations">
<category-name>Internal Business Operations</category-name>
</category>
<default-category id="Other">
<category-name>Other</category-name>
</default-category>
5. To assign permissions to the category, add the control-category-element attribute with permissions to
the XML.
If control-category-element is not configured, the category field will still be visible when users create,
edit, copy, cascade, or assign goals.
If control-category-element is configured, you need to configure permissions to control who can see the
category dropdown.
<field-permission type="read">
<description><![CDATA[Everyone can read the category]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="control-category-element"/>
</field-permission>
<field-permission type="write">
<description><![CDATA[HR can write to the category]]></description>
<role-name><![CDATA[EH]]></role-name>
<field refid="control-category-element"/>
</field-permission>
Use the obj-plan-numbering element to automatically number goals in the goal plan.
Context
If goal categories are defined, the first number segment always reflects the ordinal position of the goal category.
Note
If you sort goals, for example, by Goal Name, in the goal plan, the Move goal up and Move goal down functions
don't take effect. To resolve this issue, you can reset the sorting criteria by adding the obj-plan-numbering
element.
Procedure
Example
<obj-plan-numbering>
<obj-plan-numbering>
<obj-plan-number-format>#.</obj-plan-number-format>
<obj-plan-number-format>#.</obj-plan-number-format>
</obj-plan-numbering>
2. To enable users to indent goals to one or more levels, include at least three lines of obj-plan-number-
format.
Example
This example automatically numbers goals in the plan as follows and allows a maximum indent level of one,
for example, 1.1.1.
1.1
1.1.1
1.2
1.2.1
...
<obj-plan-numbering>
<obj-plan-number-format>#.</obj-plan-number-format>
<obj-plan-number-format>#.</obj-plan-number-format>
<obj-plan-number-format>#.</obj-plan-number-format>
</obj-plan-numbering>
Users can indent goals through Action Indent goal on the Goal Plan page.
Prerequisites
• The goal plan minimum or maximum weight or count has a dependency on goal plan pagination. That is,
pager-max-objs-per-page must be greater than 0. Otherwise, the minimum or maximum doesn't appear.
• For category-level weights or counts, categories must be defined as elements. For example, <category
id="Financial">.
Context
• Minimum or maximum for the sum of all goal weights in a goal plan
• Minimum or maximum for the sum of all goal weights in a category
• Minimum or maximum supported weight value for an individual goal
For goal count rules, you can configure minimum or maximum at both the goal plan level and the category level.
When you add attributes for goal weight rules and goal count rules, it's important to ensure that the elements are in
the correct order. The following XML example shows the attributes in the order that they can be included.
Example
Tip
• You don't have to configure both a minimum and a maximum. If no maximum is required, don't include the
attribute in the XML of the goal plan template.
• Plan-level weights or counts are independent of category-level weights or counts. You can configure a
category with a higher maximum or a lower minimum than the goal plan maximum or minimum.
• Decimals are supported for goal weights. For example, you can set maximum to 100.5%. Make sure that
your weight field definition also supports decimals in the field-format.
• The validation provides “soft” warnings instead of strictly enforced errors that prevent users from
exceeding the limits configured.
Example
In this example, for the goal plan, goals have a total minimum weight of 1% and a total maximum weight of
100%.
• (For a category) Configure the attributes min-weight and max-weight inside the <category> element.
Example
In this example, for the Financial category, goals have a total minimum weight of 25% and a total maximum
weight of 50%.
• (For an individual goal) Configure the attributes min-weight-per-obj and max-weight-per-obj inside the
<obj-plan-template> element.
Example
Example
<obj-plan-template max-goals="15">
</obj-plan-template>
• (For a category) Configure the attributes min-goals and max-goals inside the <category> element.
In this example, the Financial category requires a maximum of five goals in it.
Configure the custom checkbox field using the type attribute bool in the XML to display a checkbox for the Add
Goal and Edit Goal dialog boxes.
Procedure
1. Export the goal plan template and open it with an XML editor.
2. Add the type attribute bool to the XML.
Sample Code
Results
You can see a custom checkbox when you add or edit the goal plan.
Related Information
Context
Users can collapse or expand the comments section and edit or delete their own comments.
Note
Procedure
2. Add <field refid="comments"/> under <field-permission type="write"> in the goal plan template
to ensure the write permission.
3. Add the following code between goal plan dates and instruction sections in the goal plan template to enable the
threaded-feedback switch:
Note
In the latest Goal Management, you don't need to configure this switch because threaded comments are
supported by default.
Results
You've enabled goal comments and users can see the following on the UI:
• The comments field is invisible in the goal when the goal is opened in edit mode.
• Comments can be managed in Performance Management forms and 360 Review forms.
Use the <plan-layout> section to define the column width of the tables in Goal Plan.
Context
The <plan-layout> section determines how the goal fields appear on the goal plan. When you define this section,
keep the following guidelines in mind:
• Any field that you want to show in the goal plan needs to be included in the <plan-layout> section; otherwise
it doesn't appear in the goal plan.
• Think of the fields as a series of columns. Align them from left to right, starting with the widest column to the
left (usually the goal name and tables).
• The XML is generated from top to bottom, with top correlating to your left-most field, and going down as you
move to fields on the right.
• Allocate sufficient weight for fields. If not, the characters in the fields may miss pixels. Don't position a
subcategory field in the first column of the goal plan layout.
The optional weight attribute defines relative weights for the layout of the column. The sum of all the column
weights equals 100.
• If this attribute is specified, it's converted to a percent when rendering the HTML column and then allows the
column to stretch and shrink with the browser.
• If this attribute isn't specified, the field only takes up as much space as it requires.
Recommendation
We recommend that you define at least one column with a nonzero weight.
• Column 1: 60
• Column 2: 30
• Column 3: 10
Procedure
1. Locate the <plan-layout> element in the XML of the goal plan template.
Example
In the following example, the goal name column takes up 50% of the entire table, apportioning the
remaining fields at 10% each.
<plan-layout>
<column weight="50.0">
<field refid="name"/>
<field refid="description"/>
</column>
<column weight="10.0">
<field refid="weight"/>
</column>
<column weight="10.0">
<field refid="start"/>
</column>
<column weight="10.0">
<field refid="due"/>
</column>
<column weight="10.0">
<field refid="state"/>
</column>
<column weight="10.0">
<field refid="metric"/>
</column>
</plan-layout>
Use the <form-layout> element to determine which goal plan fields appear and how they're arranged on the Goal
Details tab of a Performance Management form.
Context
The order that you enter the fields in the <form-layout> element of the goal plan template determines how they
appear on the Goal Details tab.
Note
Of the tabs available in the Performance Management form, the Goal Details tab is the only one that is
configurable. The Other Details tab, which includes the sub goal tables, is not.
Example
<form-layout>
<![CDATA[#set ($group = "")
<table width="100%" cellspacing="0" cellpadding="0">
<tr>
<td valign="top" width="50%">#if ($display.name) <b>${label.name}:</b><br>
${field.name} #end</td><td> </td><td> </td>
<td valign="top" width="10%">#if ($display.state) <b>${label.state}:</
b><br>
${field.state} #end</td>
<td> </td><td valign="top" width="10%">#if ($display.comments) <b>$
{label.comments}:</b><br>
${field.comments} #end</td>
<td> </td><td valign="top" width="20%">#if ($display.weight) <b>$
{label.weight}:</b><br>
${field.weight} #end</td>
</tr>
</table>
<table width="100%" cellspacing="0" cellpadding="0">
<tr><td valign="top">
<div style="display:none" id="${util.newHiddenDivId()}">
#if ($display.metric) <b>${label.metric}:</b><br>
${field.metric} #end
</div>
</td>
</tr>
<tr><td valign="top">
<div style="display:none" id="${util.newHiddenDivId()}">
#if ($display.link) <b>${label.link}:</b><br>
${field.link} #end
</div>
</td>
<td> </td>
<td valign="top">
<div style="display:none" id="${util.newHiddenDivId()}">
#if ($display.actual) <b>${label.actual}:</b><br>
${field.actual} #end
</div>
</td>
<td valign="top">
<div style="display:none" id="${util.newHiddenDivId()}"><b>$
{label.category}:</b><br>
${field.category}
</div>
</td>
</tr>
<tr><td valign="top">#if ($display.start)
<div style="display:none" id="${util.newHiddenDivId()}"><b>$
{label.start}:</b><br>
${field.start} #end
</div>
</td>
<td> </td>
<td valign="top">#if ($display.due)
<div style="display:none" id="${util.newHiddenDivId()}"><b>$
{label.due}:</b><br>
${field.due} #end
</div>
Note
If you use goal comments, you can still add the comment field to the <form-layout> element, and the
threaded comments on a goal appears on the Performance Management form.
Results
You can see how the goal plan fields are displayed on the Goal Details tab of a Performance Management v12
Acceleration form:
Configure the competencies field in a development goal plan template, so that users can link development goals to
one or more competencies that they're trying to develop.
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 Technical Support.
Context
• By roles
• By forms
• By libraries
• By categories
The competencies users can link are those defined in the current logged-in locale. If a competency is defined in
English only, and when a user signs in the system with Chinese, the competency isn't available for linking.
You can only have one competencies field per development plan.
Procedure
2. To use behaviors in this field instead of competencies, make sure that behaviors are added to competencies,
and set the <field-format> tag within the <field-definition> block as follows.
Only the competencies that have behaviors are shown to users. They can select behaviors under the parent
competency when creating a development goal. The competencies field then lists the selected behaviors.
3. To require users to choose a single competency, and prevent them from selecting multiple competencies, set
the <field-format> tag within the <field-definition> block as follows.
The competencies field uses a dropdown list instead of a list with checkboxes.
Note
4. To define a source of competencies, add the <competency-filters> tag before the <field-definition>
block as follows.
Forms ...
</default-category>
<competency-filters>
<exclude type="roles"/>
</competency-filters>
<field-definition ...>
Note
When you mass create forms with custom competen-
cies, those competencies are not saved to the necessary
places in the system to be linked to employees, until
the form is routed to the next step. If it's the first time
the competencies have been linked to the employees,
development goals don't display the competencies until
the form is routed. To get around this, users can delay
setting development goals until a later step in the route
map, or you can add those competencies to all roles
related to the required users.
Roles ...
</default-category>
<competency-filters>
<exclude type="forms"/>
</competency-filters>
<field-definition ...>
Note
If you're using Job Profile Builder, and define a library
or category as a competency filter, the filter works in
different locales. Before that, make sure that competen-
cies have corresponding translations in desired locales.
The system filters the competencies by library or cat-
egory according to the default locale defined in Provi-
sioning. However, when you change the signed-in locale
</competency-filters>
<field-definition ...>
5. To allow users to add additional competencies from all available libraries, add the following switch.
When users create a development goal, a Competencies link appears next to a list of available competencies.
When they choose the link, the Add Competencies dialog pops up, where competencies are organized into
hierarchical lists of categories under tabs for each library. Users can select competencies to add them to the
development goal.
Results
Enable Coaching Advisor in a text area field for development goals, so that users can add predefined content in
Coaching Advisor to development goals.
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 Technical Support.
Context
When users choose Coaching Advisor in the text area field, a popup window showing the competencies for the
employee's role appears. Users can drill down on to find predefined content to add to development goals.
If you're using Job Profile Builder, Coaching Advisor 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.
Procedure
In a development goal plan template, set the field-show-coaching-advisor attribute of a text area field to
true.
Results
Configure a goal plan template to show the achievements that users add in Continuous Performance Management
in goal plans. It enables employees and managers to view achievements and feedback received on the
achievements, directly in goal plans.
Prerequisites
Context
Note
This is an SAP SuccessFactors Business Beyond Bias feature. Use it to support processes that detect, prevent,
or eliminate the influence of bias, helping you achieve your diversity and inclusion goals.
Procedure
Results
If users have achievements linked to goals, the achievements are shown on users' goal plans.
You can configure email notifications for creating, deleting, modifying, and commenting on development goals.
The configuration is the same as for performance goals. For more information, refer to related topics in the
Implementing Goal Management guide.
You can import development goals to users' development plans using CSV files, including creating, editing, and
deleting development goals.
If the competencies field is configured in your development goal plan template, you can update competencies
using the OBJECTIVE_competency column in CSV files. You can input multiple competency GUIDs and separate
them by comma, for example, "7,8". The competencies are then associated to development goals. To update
competencies, leave the OBJECTIVE_competency column blank, and original associations are not updated.
Import a CSV file to add, edit, or delete development goals using Import Development Goals.
Prerequisites
Procedure
1. In Admin Center, go to Goal Management Feature Settings and select Goal Import.
2. In Admin Center, go to Import Development Goals.
3. Select a development goal plan template from the Available List of Templates dropdown, and choose Generate
a CSV Header to download the import template.
4. Fill in the CSV file and upload it.
5. Choose Import.
Results
When the import job is finished, you receive an email about the job results.
Learn about the supported fields in the import template of development goals.
The following table introduces the descriptions and suggested values for the header fields in CSV files.
Note
If you're updating a manually added
goal, for example, with a learning ac-
tivity, use the "ID" of a development
goal instead of "GUID", as manually
added goals don't have a GUID.
Note
When you add competencies, input
the GUID of competencies.
Note
When you import the file, the date
format must be MM/DD/YYYY.
Note
When you import the file, the date
format must be MM/DD/YYYY.
There are two elements to development content: the catalog of learning activities, and the mappings between
learning activities and competencies.
Permission to manage development content is granted via roles. To grant this permission, in Admin Tools, choose
Set User Permissions Manage Permission Roles , then select the role for which you want to grant access
to managing development content. In the Permission Role Detail page, choose Permission. Under Administrator
Permissions, choose Manage Career Development.
Administrators can import the development catalog under Admin Tools Manage Learning Activity Catalogs .
5 PARENT_ENTR Must reference the GUID of the parent record. For Catalog ID
Y_ID LearningActivity records, these should reference the
LACatalog record.
7 FIELD2 Max length: 1000 chars Leave blank. (Reserved for future
use; possibly duration)
8 FIELD3 Max length: 1000 chars Leave blank. (Reserved for future
use; possibly vendor name)
9 FIELD4 Max length: 1000 chars Leave blank. (Reserved for future
use; possibly prerequisites)
10 FIELD5 Max length: 1000 chars Leave blank. (Reserved for future
use; possibly cost)
11 FIELD6 Max length: 1000 chars. URL for activity launch (if URL
applicable) would typically go here. To launch the
target in a separate window, include <popup> as
a prefix to the url. For example: <popup>http://
mylmsurl/activity.doc
Common CSV formatting rules apply. For example, text strings that might have commas within them should be
surrounded by double quotes ("), and quotes within text strings should be escaped by doubling them. See the entry
on Comma-separated values in Wikipedia for more information.
ENTRY_TYPE,GUID,LOCALE,ENTRY_NAME,PARENT_ENTRY_ID,FIELD1,FIELD2,FIELD3,
FIELD4,FIELD5,FIELD6,ACTIVITY,ACTIVE,EDITABLE
LACatalog,100,en_US,My course catalog,,,,,,,,,,
LearningActivity,101,en_US,"Basics of Microsoft Word",100,"Want to become a
""power user"" of Microsoft Word?
This course will teach you how!",,,,,,ILT,1,1
Learning Activity to Competency mappings are managed in the Admin Tools page under Manage Development
Manage Learning Activity to Competency mappings .
You can view, import, delete, and export competency mappings from this page:
Recommendation
Although the system can support mapping activities from multiple catalogs with a single import file, we
recommend that each import file only reference activities from a single learning catalog.
The export function exports the mappings as a CSV file, with the same format as the import file. The exported file
always uses the competency GUID, not the competency ID.
As an alternative to the mappings import file, administrators can manage competency mappings with a mapping
tool in the Admin Tools.
This tool looks similar to some of the other mapping tools within the product, where the user finds the records on
each side of the tool, and then selectively adds items from the right side to the selected item on the left.
The tool is located with the other Career Development Planning links at the bottom of the Admin Tools menu.
To protect the administrator from accidentally overwriting or corrupting the competency mappings, you must
identify which system is considered the master source of the data. In Provisioning, select Company Settings then
locate the option Learning Activities and Competencies Mapping Tool:
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 Technical Support.
• External Master: the imported mapping file (typically generated by SAP SuccessFactors Learning) is the master
of the data:
• The mapping tool allows the data to be viewed, but not updated.
• Mappings can be re-imported at any time.
• CDP Master: Career Development Planning is the master of the data:
• The mapping tool enables the administrator to change the mappings and save the changes.
• Mappings can be imported only if there are no mappings already in the system.
You must also have valid development goal and learning activity templates loaded before you can map
competencies to activities.
Enable a setting in 360 Reviews form templates, so that the Detailed 360 Report shows a link to development goals
on users' default development plan.
Prerequisites
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 Technical
Support.
2. Open a 360 Reviews form template, and select Enable Development Plan Integration.
Results
If users have development goals related to the competencies or behaviors shown in a 360 Reviews form, the
Detailed 360 Report for this form shows the Development Goals link. Choosing the link, users see a list of
development goals with an option to edit goals. The standard goal edit window provides access to learning activities
as well as catalogs.
They can also add new development goals. The new goals are saved to users' default development plan.
Configure the Development Goals block in People Profile so that users can view, create, edit, and delete
development goals in People Profile.
Context
If users have the permissions to view, create, edit, and delete development goals in the development plan, they can
take the same action in the Development Goals block.
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 Technical
Support.
d. Save the data model and import the file to Provisioning where you export it.
2. Configure the Development Goals block.
a. In Admin Center, go to Configure People Profile.
b. Place the Development Goals block in an available section.
c. Edit block settings and choose Save.
You must select at least one development goal plan template. Otherwise, the block shows no data.
3. Grant users the permission to view the block.
a. In Admin Center, go to Manage Permission Roles.
b. Select a role and choose Permission....
c. In the User Permissions section, choose Employee Data.
With this permission, users can view the block in People Profile. Whether they can view or edit the content
in the block depends on the permissions in the development plan template.
e. Choose Done and Save Changes.
Configure the development plan template so that users' all development goals created out of this template are
shown in the Development Goals block in People Profile.
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 Technical Support.
Context
In the development plan, for each development goal, users can add it to or remove it from the Development Goals
block. When you enable showing all development goals in the block, users can't remove the goals from the block.
Procedure
Sample Code
4. Save the template and upload it to Provisioning where you export the template.
Results
Users' all development goals created out of this template are shown in the Development Goals block in People
Profile.
You can use reporting tools to report on development goals along with competencies and learning activities.
The Development Goals report domain allows you to report on development goals and associated competencies
and learning activities. It can be used regardless of having Transcript enabled. If Transcript is enabled, specific
field IDs supported in the learning activity template are reportable by default. If Transcript is not enabled, see the
information below in Reporting on Learning Activities.
Most of the reports available for performance goals are also available for development goals. Note the following
differences:
• The same portlet can't be used more than once on a dashboard, and portlets don't further separate or filter the
data included in the Processes. It's recommended you set up a separate dashboard for development goals with
a Process that doesn't include performance goals.
The Learning Activities report domain requires having Transcript enabled. It allows you to report on both custom
learning activities and learning from SAP SuccessFactors Learning.
The Learning Activities - historical report domain allows you to report on the same information as the Learning
Activities domain. However, the Learning Activities - historical domain doesn't have the People pill tab or respect
role-based permissions. It brings all data available in the system, including data from inactive users, and therefore
it's best intended for administrators who should have access to every employee's learning activities and want to get
a full report of learning activities available in the system.
For customers without Transcript and SAP SuccessFactors Learning enabled, to report on learning activities in
reports, make sure that you add the reportable=fieldX attribute in the field definition. "X" stands for 1-20 in the
learning activity template.
Note
• The standard name of a description is "desc", and not "description". If you previously specified
"description", treat it as a custom field and add a reportable field for it.
• The "plan" parameter in the script points to the goal plan ID that is associated to the learning activity
template.
• There can be a maximum of 20 reportable fields for a learning activity.
Related Information
After defining custom fields as reportable fields in your development goal plan template, sync the existing data
from the custom fields to table reports.
Procedure
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 Technical
Support.
2. Choose Sync for Sync development goal data to ad hoc report and Sync Learning Activities data to ad hoc
report.
Note
When running the sync, you must select each development goal plan individually. Do not select all in one
job.
Results
When the job is done, development goal data is synced to table reports.
Development goals can be shown on Performance Management forms. When a form is created, development goals
are auto-populated to the form. Development goals can also be auto-synced between a development goal plan and
form.
Prerequisites
You have an SAP SuccessFactors Performance & Goals license and have enabled Performance Management.
Configuration
To show development goals on forms, configure a goal section in a form template and link it to a development goal
plan. For more information, refer to Goal Section.
To auto-sync development goals between a development goal plan and form, configure the autosync attribute in
an XML form template. For more information, refer to Including Goals from Goal Plan into Goal Section. You can't
enable the auto-sync feature for development goals in Admin Center.
To learn about how auto-populate and auto-sync work, refer to Auto-Populate and Auto-Sync.
To learn about what users can do with development goals on forms, refer to Working with Goals on Forms.
Related Information
Goal Section
Auto-Populate and Auto-Sync
Working with Goals on Forms
Including Goals from Goal Plan into Goal Section
Learn about the setup and configuration of the latest Goal Management.
Caution
Upgrading to the latest Goal Management cannot be undone. You cannot revert to the legacy version. The
legacy and latest versions of Goal Management don't support exactly the same features. Features you use
in legacy Goal Management are not necessarily supported in the latest Goal Management. Make sure you've
reviewed the feature differences before the upgrade.
For customers who have legacy Development Goals enabled but haven't migrated from Job Description
Manager to Job Profile Builder or Talent Intelligence Hub (with Growth Portfolio enabled), the upgrade won't
work.
Related Information
The latest version of Goal Management, consisting of performance goals and development goals, provides a new
experience to set up, track, distribute, and manage goals in your organization.
In the latest Goal Management, users can now view an unlimited number of goals without any restrictions in the
goal list view and the team goal list view.
As a manager or an employee, you can benefit from the latest Goal Management in the following scenarios:
Note
To use Development Goal in the latest Goal Management, the SAP SuccessFactors Succession &
Development license and feature enablement in Provisioning are still required. If you’ve enabled the
latest Goal Management, access to Development Plan is removed from Career Development Planning and
integrated into the latest Goal Management.
For the complete list of features, see Supported and Unsupported Features in the Related Information section.
If the feature is not listed, it is not supported in the latest Goal Management.
Upon template conversion, integration between the latest Goal Management and other modules is supported the
same way as it is supported in the legacy Goal Management.
The latest Goal Management can be integrated with the modules in the table below.
Learning No
Related Information
This is a main list of supported and unsupported features in the latest Goal Management.
Create personal Supported Web Performance End user Enables users to create personal
goals from a Mobile goal
goals by selecting and editing goals
goal library
from a goal library.
Cascade per- Supported Web Performance End user We recommend cascading goals
sonal goals Mobile goal one by one.
View other peo- Supported Web Performance End user To view other people's job titles or
ple's goals Mobile goal photos, users must have the View
Development permission for these employee
goal
data under User Permissions
Employee Data .
People Selector Supported Web Performance End user To see the default list and search
Mobile goal for people in People Selector, users
Development
must have the User Permissions
goal
General User Permissions User
Search permission.
Note
On mobile, people search is
available at the search menu
entrance.
Change goal Supported Web Performance End user Changing goal plan states on Per-
plan states in Mobile goal formance Management form is still
Goals Development supported.
goal
Receive goal no- Supported Web Performance End user Enables users to receive email no-
tifications Mobile goal tifications on web or push notifica-
Development tions on mobile.
goal
Notifications of changes to goal
plan states can be received via
email only.
Add learning Supported Web Development End user Make sure you've enabled Tran-
courses to goals goal script learning and set up inte-
gration with SAP SuccessFactors
Learning.
Add competen- Supported Web Development End user Competencies are available only
cies to goals Mobile goal
when Job Profile Builder or Talent
Intelligence Hub is enabled.
• Using
<field-format>use-
competencies-
single</field-
format> to allow
users to select only one
competency isn't supported.
• Using <exclude
type="hidden"/> to ex-
clude hidden competencies
isn't supported. Hidden com-
petencies are excluded by de-
fault.
• Competencies are added
through a picker by default,
regardless of the configura-
tion of the for="show-
competency-browser"
attribute.
Create and view Supported Web Performance End user Enables users to create and view
activities Mobile goal activities between direct manager
Development and employees through Continu-
goal
ous Performance Management.
View achieve- Supported Web Performance End user Enables users to view achieve-
ments linked to Mobile goal ments linked to goals through
goals Development Continuous Performance Manage-
goal
ment.
View audit his- Supported Web Performance End user "Shared" and "Unshared" are sup-
tory of goals goal ported as new action types.
Development
goal
Switch back to Supported Web Performance End user Allows users to switch back to the
the legacy view goal legacy view to see the full field
Development length or unsupported fields that
goal are no longer displayed after tem-
plate conversion.
Metric lookup Supported Web Performance End user Logic of editing and reading the
table Mobile goal
rating scale of a metric lookup ta-
ble has been standardized in the
latest Goal Management.
Goal Alignment Supported Web Performance End user Goal Alignment Chart works for
Chart goal one or more goal plan templates
in which goals were cascaded. Goal
fields shown in an alignment chart
include the user's display name,
goal name, due date, and status.
Initiatives Supported Web Performance End user Initiatives can be linked to both
goal
personal or team goals. Users can
make changes to initiatives in the
"edit" step when assigning team
goals. However, editing initiatives is
not supported in these processes:
copy goals from goal plans, cre-
ate goals from library, and cascade
goals.
Create legacy Supported Web Development End user Using legacy learning activities
learning activi- goal
means you haven't enabled Tran-
ties
script learning. We recommend
that you enable Transcript learning
to use the learning activities fea-
ture. For more information, refer to
Learning Activities in Related Infor-
mation.
Advanced user Supported Web Performance End user Use this feature to cascade per-
search by crite- goal
sonal goals or assign team goals.
ria
Make sure that Enable Solr
People Search (requires Role-
based Permission) is enabled in
Provisioning.
Remember
As a customer, you don't
have access to Provisioning.
To complete tasks in Provision-
ing, contact your implementa-
tion partner or Account Execu-
tive. For any non-implementa-
tion tasks, contact Technical
Support.
• User Permissions
User Search
• For search criteria permis-
sions, refer to Configuring
Search Criteria for People
Search in the Related Informa-
tion section.
• For search results permis-
sions, refer to Configuring
Role-Based Permissions to Al-
low Logged In User to View
Certain Employee Information
in People Search Results in the
Related Information section.
Note
Goal Management doesn't
support the permission valida-
tion for the search criterion
User Role. If users use this
Copy personal Supported Web Performance End user The goals created through copying
goals on behalf goal remain within the target user's goal
of others Development plan.
goal
Allow duplicate Supported Web Performance End user With this feature, users' choice of
assignment of goal Replace in a duplicate assignment
team goals confirmation will replace the most
recently assigned team goal.
Roll-up calcula- Supported Web Performance End user • You can set the rollup-
tion for cas- goal calc-type attribute to
caded and
avg or sum for the bizx-
linked goals
actual, bizx-target,
and bizx-pos fields.
• Roll-up calculations are auto-
matic, so manual confirma-
tion on these fields isn't sup-
ported.
• Each time a parent goal is cas-
caded or linked, two audit re-
cords are generated for it. One
record indicates the action
type, either "Cascaded" or
"Linked," based on the action
taken. The other record shows
"Modified" due to changes in
the roll-up fields. Likewise, a
"Modified" audit record is gen-
erated for the child goal.
Search for inac- Supported Web Performance End user This feature is enabled by de-
tive users in goal fault, requiring no configuration
People Selector Development of switches or role-based permis-
goal sions.
Link goals Supported Web Performance End user In the latest Goal Management,
goal users can only unalign goals from
their own goal details view. Addi-
tionally, the "Unlinked" audit record
is only generated for the child goal
and not for the parent goal.
Create and link Supported Web Development End user Make sure you've enabled Tran-
custom learning goal Admin script learning and the option for
activities
users to create custom learning.
Import personal Supported Web Performance Admin Features supported in this function
or team goals goal are limited to the supported fea-
through Admin Development tures of the latest Goal Manage-
Center goal
ment.
Add goals using Not supported Web Performance The SMART Goal Wizard option
the SMART Goal Mobile goal is not supported in Performance
Wizard Development Management either.
goal
Layout configu- Not supported Web Performance This includes custom learning ac-
ration of the Mobile goal tivities.
goal plan Development
goal
OData APIs (V4) Not supported Web Performance • These include APIs used for
Mobile goal
solution extensions.
Development
goal • OData APIs (V2) support leg-
acy team goals, but not latest
team goals.
Caution
To prevent data loss, avoid us-
ing OData APIs (V2) to cre-
ate goals in the latest Goal
Management. The new version
has constraints, like character
length limits, that V2 APIs
don’t fully enforce because
they still count using bytes. For
example, entering 4,000 Jap-
anese characters may result
in only 1,333 being saved, as
1,333 characters exceed 4,000
bytes. This means goals cre-
ated with OData APIs (V2)
may be successfully created
but could be truncated when
viewed on the UI.
Group goals Not supported Web Performance In the latest Goal Management,
Mobile goal group goals are replaced by team
Development goals. Users cannot perform any
goal actions on group goals except for
viewing group goals v2.
Related Information
As we're planning to universally upgrade customers to the latest Goal Management, some features available in the
legacy Goal Management will be deprecated. Here we list alternatives in the latest Goal Management, if any, to the
deprecated features, and explain reasons why we retire them.
Alternative Fea-
Deprecated Fea- Reason for Depre- ture in Latest Goal Availability of Al-
ture ciation Management ternative Feature More Info
Group goals Existence of a simi- Team goals Already available Latest team goals support the same
lar feature
business process as group goals.
Tasks or targets of Existence of a simi- Milestones Already available The alternative feature allows users to
subgoals lar feature
break down a goal into achievement mile-
stones. Users can set the duration of
milestones and define actual and target
values for each milestone.
Mass assign group Low feature usage Import perform- Already available Access the alternative feature in Admin
goals via the goal ance goals
Center.
plan through the
CSV file Fore more information, see Goal Import.
Import or export Low feature usage Import perform- Already available Access the alternative feature in Admin
goals directly from ance goals
Center.
a goal plan
Fore more information, see Goal Import.
Add goals using the Replacement by a Create goals with Already available This alternative feature will offer an AI-
SMART Goal Wiz- different feature generative AI driven approach to creating goals that
ard meet all the facets of SMART goals.
To offer end users more flexibility and provide better visual appearance on the UI, we've simplified configurations
and set new validations in goal plan templates of the latest Goal Management.
For more information about supported elements and attributes in the latest Goal Management, see Supported
Elements and Attributes Comparison: Legacy and Latest.
Unsupported Fields
What's not supported in the legacy version remains unsupported in the latest version. The following standard fields
are particularly not supported in the latest Goal Management:
For goals bool None of the field IDs for this type is supported.
table
Only metric-lookup-table and milestones are sup-
ported.
text All other field IDs for this type are supported except the follow-
ing:
• obj-plan-field1
• achievement-text
• actual-achievement-text
• goto-url
Learn about the changes that are made to the following fields in the latest Goal Management:
Note
You can adjust the character limits to 4,000 for desc, metric, comments, and custom field IDs of the
textarea type. However, the previously recommended limits of 1,000 and 2,000 remain as best practices.
It's important to note that template conversion results in automatic application of maxlength configurations.
Therefore, if you've previously converted goal plan templates or set character limits to 1,000 or 2,000 before 1H
2024 and want to take advantage of the new 4,000-character limit, you'll need to manually change the limits in
your goal plan template and re-upload it 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 Technical Support.
name
You must have this field with the attribute required set to true in
the goal plan template.
This is the first field displayed on the UI when users create a goal.
desc The maximum length allowed for this field is 4,000. The recom-
mended length is 2,000.
metric The maximum length allowed for this field is 4,000. The recom-
mended length is 1,000.
competency This field is supported only in development goals with Job Profile
Builder enabled.
You can't define this field to require users to choose only one compe-
tency.
metric-lookup-table Metric lookup tables don't allow empty rows when the write permis-
sion is granted to this field.
comments comment The maximum length allowed for this field is 4,000. The recom-
mended length is 1,000.
<custom field ID> text The maximum length allowed for this field type is 500. However, the
maximum length allowed for the standard field ID takes precedence.
For example, if the field ID of this field type is desc, the maximum
length allowed for this field is 2,000.
<custom field ID> textarea The maximum length allowed for this field is 4,000. The recom-
mended length is 2,000. However, the maximum length allowed for
the standard field ID takes precedence. For example, if the field ID of
this field type is name, the maximum length allowed for this field is
500.
• You can't set field ID to type, flag, initiatives, id, or category because they are reserved as part of
the definition for API entity and property.
• For fields with character countdown, characters in multi-byte languages are counted as one character
each, in contrast to the previous logic where one character could account for multiple units. As of 2H 2024,
this change also applies to reports generated in Report Center.
• For fields name, desc, metric, comments, text, and textarea, if the value you entered exceeds the
maximum length before the upgrade to the latest Goal Management, you can only see the value within the
character limit in the goal plan of the latest Goal Management. However, you can switch to the Legacy View
or go to Report Center to see the full value in the report. If users want to update a field value and save it,
they need to reduce the value length to conform to the new character limit.
Related Information
Supported Elements and Attributes Comparison: Legacy and Latest [page 35]
Goal Plan Template Elements and Attributes [page 29]
Goal Plan Template Fields [page 60]
Context
Recommendation
We recommend that you first test this feature in preview or test environments before enabling it for production
environments. This feature targets those who use simpler goal functions and goal plan templates without
complex configurations.
After you upgrade to the latest Goal Management, existing goal plan templates and related goal data across all
supported modules will be available in read-only mode through the Legacy View unless converted. They remain
accessible and fully reportable.
Caution
• The SAP SuccessFactors Mobile app can be downloaded from App Store for iOS or Google Play for
Android. The Android app is available from Tencent App Store if you're in mainland China.
• Enabling the latest Goal Management automatically enables the new experience for both web and mobile
applications. Mobile enablement is no longer controlled by Enable Mobile Features settings.
Results
You've upgraded to the latest Goal Management. You can view the completed upgrade through Admin Center
Upgrade Center View Recently Completed Upgrades .
Next Steps
• (Recommended) Upload a new goal plan template in Provisioning or add a new template from SuccessStore
through Admin Center Manage Templates for the latest Goal Management.
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 Technical
Support.
• If you want to use existing goal plan templates and the related goal data in the latest Goal Management,
convert these templates.
Related Information
Convert your existing goal plan templates so that you can use and edit your templates and the related goal data
in the latest Goal Management. Template conversion is mandatory for integration with Continuous Performance
Management, Onboarding 1.0, Onboarding 2.0, Performance Management forms, and 360 Reviews forms
Prerequisites
Context
The conversion can't be stopped or undone. Converting a template takes from a few minutes to several hours,
depending on the configuration and the amount of data in it.
Note
Results
Your template is converted and available for use in the latest Goal Management. The converted template retains the
original ID and name so that it can integrate with other modules properly.
For backup and reference, the original goal plan template is copied with a new ID, renamed <Original Name>
Backup, and set to the read-only mode. This backup template preserves any fields or data not yet supported
in the latest Goal Management prior to conversion. The backup template appears in the available templates list,
with role-based permissions from the original template automatically applied. This ensures all users and roles with
access to the original template can seamlessly access the backup template as well.
Note
• Unsupported fields are not shown in the latest Goal Management. If you want to view this data, either
create a report on the backup template if the template is already converted or go to Legacy View of the
unconverted template.
• As the field ID name is required in the latest Goal Management, we'll fill in the field for you if you haven't set
it before template conversion. Additionally, field refid="name" is added for field permissions "read"
and "write".
• The system automatically applies the maxlength attribute to templates that have been converted.
Related Information
Prerequisites
Context
Caution
Check the legal and regulatory framework of your organization before you enable this function. For details on
how SAP SuccessFactors processes user data, please refer to SAP Sub-processors & Data Transfer Factsheets.
The prompt template automatically applies goal plan configurations, such as start, due, and maxlength, to
AI-generated goals. Goal fields available for AI generation are name, desc, metric, start, due, milestones,
and custom fields of text and textarea types. Among the supported fields, AI generates content for whatever
fields you configured, except for read-only fields, which cannot be populated by AI. By providing meaningful text for
<field-description> for custom text and textarea fields, you give context that helps improve the quality of
AI-generated suggestions, ensuring more accurate and relevant results for goals.
Once enabled, users can use this feature in both the latest Goal Management and the modules integrating with
Goal Management, such as Performance Management, 360 Reviews, and Continuous Performance Management.
While in the mobile experience, users can only view or edit the AI-generated goals in these integrated modules.
To be able to use AI for goal creation, users should read carefully and agree to the AI Usage Acknowledgment. Users
should always review AI-generated content and make necessary changes before saving a goal.
Procedure
Related Information
The AI-assisted writing tool is an interactive tool that uses generative AI capabilities to assist employees with their
writing tasks. While writing content in the SAP SuccessFactors applications, employees can leverage the features of
the AI-assisted writing tool to enhance multiple aspects of their writing, such as clarity, conciseness, and tone.
The AI-assisted writing tool helps improve the content of goals, such as goal name, description, and other
content provided in goal fields of text and textarea types. It isn't yet supported in custom learning activities
of development goals.
The following is a summary of the capabilities offered by the AI-assisted writing tool:
• Uses language processing capabilities to understand the context of a sentence and suggest enhancements in
grammar, spelling, vocabulary choices, and phrasing.
• Ensures improved readability and a consistent tone (professional, personable, or constructive) to suit the
communication needs for different audience groups in the organization.
• Provides the options to communicate a message in fewer or more words and transform paragraphs to bulleted
lists.
• Provides additional actions in the context of the tasks that users perform in their SAP SuccessFactors
applications.
The following table outlines the available actions in the AI-assisted writing tool.
Action Description
Enhance Writing Suggests enhancements in grammar, spelling, vocabulary choices, and phrasing in the con-
text of the selected line or paragraph.
Change Tone Provides options to change the tone of the selected line or paragraph to professional,
personable, or constructive to suit the communication needs for different audience groups
in the organization.
Make Shorter Shortens a selected line or paragraph to convey the message more concisely.
Make Longer Rewrites a selected line or paragraph by adding more words to provide a detailed explana-
tion based on the original content.
Make Bulleted List Converts a selected line or paragraph into a bulleted list to simplify complex information,
and enhance readability by breaking it down into easy-to-read points.
Analyze Text Performs a safety scan on each text box, prompt entry, or Generative AI output in order to
detect bias, and suggest replacement text for any language flagged as potentially biased,
discriminatory, or harmful.
Translate Translates the written text into the target language chosen by the user. The following capa-
bilities are supported with this action:
• Translation from en-US (US English) to all 46 languages supported in SAP SuccessFac-
tors.
• Full translation between the following languages: English (US), German, French, Span-
ish, Portuguese, Chinese (Simplified) and Japanese.
Note
For information about the languages supported by the AI-assisted writing tool, refer to SAP Note 3396784 .
Related Information
Enable AI-assisted writing, including Translation and Text Analyzer features in SAP SuccessFactors applications to
help users enhance the quality of their writing.
Prerequisites
• You've purchased the AI units license. For more information about AI units license, please contact your Account
Executive.
• You have the Administrator Manage AI Capabilities AI Services Administration permission.
• Users have the User Permissions AI Access Assisted Writing permission.
Note
The Translate and Analyze Text options appear in the assisted writing menu only when their respective
toggles are enabled.
Next Steps
Users can view the AI-assisted writing tool icon when they navigate to the text input area and use the options in the
assisted writing menu to enhance their writing.
Related Information
In development goal plans, users can add and create learning activities to help achieve their development goals.
Administrators can also import learning activities for users.
Note
Make sure you've enabled Transcript learning and set up integration with SAP SuccessFactors Learning.
Add learning directly Add New Learning Add Learning From • Users have the Users can't add learn-
from SAP SuccessFac- access permission ing from SAP Success-
Activity Find in Library
tors Learning to the learn- Factors Learning when
Catalog ing activity tem- acting as a proxy as an-
other user.
plate in User
Goals Goal Plan
Permissions in
Manage Permission
Roles.
• Users have action
and field permis-
sions in the learn-
ing activity tem-
plate.
Add learning from SAP Add New Learning Add Learning By • The When users choose the
SuccessFactors Learn-
Activity Search by Competency competencies option, a dialog pops up
ing according to the field is configured
Competency where they can see the
competencies linked to in the development
development goals competencies they've
goal plan template.
linked and a list of learn-
• Users have linked
ing items related with
competencies to
each competency. They
development goals.
can also see two ratings
• Users have the
access permission for each competency
to the learn- to guide them on how
ing activity tem- much they need to work
plate in User on the competency:
Create custom learning Add New Learning Create Custom Learning • Enable Add
activities Learning Activity
Activity Custom
Manually is se-
Learning Activity lected in Provision-
ing.
• Users have the
access permission
to the learn-
ing activity tem-
plate in User
Goals Goal Plan
Permissions in
Manage Permission
Roles.
• Users have action
and field permis-
sions in the learn-
ing activity tem-
plate.
Connect development The option is available Link Custom Learning • Users are able
goals with learning ac- to create custom
when users create or
tivities Users can link learn- learning activities.
edit a custom learning
ing activities to develop- • The dev_goals
activity.
ment goals, but can't field is configured
Users can link develop- link development goals in the learning ac-
ment goals to learning to learning activties. tivity template.
activities, but can't link • Users have read
learning activities to de- and write per-
velopment goals. missions to the
dev_goals field.
Import custom learning Admin Center Admin Center See more details. Importing Custom
activities Learning Activities
Import Development Import Development
Goals Goals
Note
• In a development goal plan that was migrated from another development goal plan, any updates to existing
learning activities in the new development goal plan are reflected in the old development goal plan. This
situation doesn't happen if learning activities are added to the new development goal plan after migration.
• Users are not allowed to add or create learning activities after development goals are completed.
• If you've enabled the Prevent removal of learning activities from completed development goals setting in
Manage Templates Development <development goal plan template> General Settings , users are
not allowed to remove learning activities after development goals are completed. This setting is only
applicable to the latest version of Development Goals.
Set up integration with SAP SuccessFactors Learning in Provisioning so that users can add or create learning
activities in their development goal plan.
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 Technical
Support.
Procedure
Note
We do not recommend you select Use default value for required field validation.
4. Select Enable Add Learning Activity Manually to allow users to create custom learning activities.
5. Select Enable SuccessFactors Learning integration and specify the SuccessFactors Learning Integration URI.
You can request the URI from the Data Center Operations.
Example
https://companyID.scdemo.<app-server-domain>.com
6. Optional: If you use Akamai or reverse proxy, you should specify the SuccessFactors Learning Integration API
URI.
7. Save your changes.
Next Steps
A Transcript learning activity template defines the fields, permissions, and layout of learning activities. Only one
learning activity template is supported in the system.
Here are the key differences between learning activity and development goal plan templates:
Recommendation
The following table describes the supported fields in a Transcript learning activity template.
Note
This field is to au-
tomatically record
the date when the
status is set to
"Completed". We
recommend that do
not grant users the
write permission to
this field.
Mandatory Fields
The following fields are mandatory for adding learning from SAP SuccessFactors Learning and field data is synced
with data in SAP SuccessFactors Learning:
• assignee
• completed_date
• name
• description
• status
• guid
• type
• dev_goals
• text
• textarea: Supports Coaching Advisor, Legal Scan, and Spell Check.
• date
• percent
• bool
• enum
• checkbox
• number
Note
The comment field type is not supported in the learning activity template. If users do need to add comments,
they can add them to corresponding development goals.
Action Permissions
Action permissions define users' ability to perform specific actions on learning activities. The following table
describes the elements used for configuring action permissions.
Element Description
<role-name> Name of the roles that you want to configure permissions for
Sample Code
<permission for="create">
<description><![CDATA[All roles can add and create learning in the employee's
plan.]]></description>
<role-name><![CDATA[*]]></role-name>
</permission>
<permission for="delete">
<description><![CDATA[Only employee and manager can remove learning from the
employee's plan.]]></description>
<role-name><![CDATA[E]]></role-name>
<role-name><![CDATA[EM]]></role-name>
</permission>
Field Permissions
Field permissions define users' ability to view and edit fields of learning activities. The following table describes the
elements used for configuring field permissions.
<field-permission type=""> Type of field permissions. The following types are supported:
<role-name> Name of the roles that you want to configure permissions for
Sample Code
<field-permission type="read">
<description><![CDATA[All roles can view the following fields when the
learning activity status is Planned.]]></description>
<condition><![CDATA[status eq Planned]]></condition>
<role-name><![CDATA[*]]></role-name>
<field refid="link"/>
<field refid="assignee"/>
<field refid="guid"/>
<field refid="type"/>
<field refid="start_date"/>
<field refid="due_date"/>
<field refid="name"/>
<field refid="description"/>
<field refid="purpose"/>
<field refid="cost"/>
<field refid="dev_goals"/>
<field refid="customtext4"/>
<field refid="completed_date"/>
<field refid="certifications"/>
</field-permission>
Value Permissions
Value permissions define the values that users can edit for a field. The following table describes the elements used
for configuring value permissions.
<role-name> Name of the roles that you want to configure permissions for
Sample Code
<value-permission>
<description><![CDATA[All roles can change the status to Planned, In Progress,
and Completed.]]></description>
<field refid="status"/>
<role-name><![CDATA[*]]></role-name>
<allow-value><![CDATA[Planned]]></allow-value>
<allow-value><![CDATA[In Progress]]></allow-value>
<allow-value><![CDATA[Completed]]></allow-value>
</value-permission>
<value-permission>
<description><![CDATA[EL role can change the status to Planned, In Progress,
Completed, and Locked.]]></description>
<field refid="status"/>
<role-name><![CDATA[EL]]></role-name>
<allow-value><![CDATA[Planned]]></allow-value>
<allow-value><![CDATA[In Progress]]></allow-value>
<allow-value><![CDATA[Completed]]></allow-value>
<allow-value><![CDATA[Locked]]></allow-value>
</value-permission>
<value-permission>
<description><![CDATA[EJ, EC, EH roles can change the status to Planned when
the status is Completed.]]></description>
<field refid="status"/>
<condition><![CDATA[status eq Completed]]></condition>
<role-name><![CDATA[EJ]]></role-name>
<role-name><![CDATA[EC]]></role-name>
<role-name><![CDATA[EH]]></role-name>
<allow-value><![CDATA[Planned]]></allow-value>
</value-permission>
Supported Roles
Role Description
E Employee
EM Manager
EH HR representative
EC HR developer
Configure the status field in the learning activity template so that users can choose statuses for learning
activities.
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 Technical Support.
Context
• Planned
• Completed
• Locked
• Deleted
• Failed
When goals are completed, all the related learning activities must be set to Completed or Locked, after which no
new statuses can be added to the learning activities.
Recommendation
To allow users to add learning from SAP SuccessFactors Learning, you must configure the Planned status. We
also recommend you configure the Completed and Failed statuses.
Note
Changes to the learning statuses made in SAP SuccessFactors Learning are synced to associated development
goals. However, you must make sure that users have signed in to the Learning solution with the SAP
SuccessFactors HCM suite credentials. Any status changes users make, except the Completed status, while
still using the Learning sign-in credentials are saved in the solution only and not synced to development goals.
The field type is enum. You can use <enum-value> and <enum-label> to define status options and use
<default-value> to define the default status.
Sample Code
Configure the certifications field in the learning activity template so that users can upload one or two
certificates to a completed custom learning activity.
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 Technical Support.
The field is formatted as a table. You can use name, issue_date, and expire_date to define table columns.
Sample Code
Sample Code
<field-permission type="read">
<description><![CDATA[Employee, manager, learning admin, educ rep and HR
rep can view the following fields.]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="assignee"/>
…
<field refid="certifications"/>
<table-col id="name" field-refid="certifications"/>
<table-col id="issue_date" field-refid="certifications"/>
<table-col id="expire_date" field-refid="certifications"/>
</field-permission>
<field-permission type="write">
<description><![CDATA[Employee, manager, learning admin, educ rep and HR
rep can edit the following fields.]]></description>
<role-name><![CDATA[*]]></role-name>
<field refid="assignee"/>
…
<field refid="certifications"/>
<table-col id="name" field-refid="certifications"/>
<table-col id="issue_date" field-refid="certifications"/>
<table-col id="expire_date" field-refid="certifications"/>
</field-permission>
Sample Code
<transcript-detail-layout>
<transcript-detail-portlet id="details" column="1" row="1">
<transcript-detail-portlet-label lang="en_US">Details</transcript-detail-
portlet-label>
<field refid="purpose"/>
<field refid="name"/>
<field refid="description"/>
<field refid="start_date"/>
<field refid="due_date"/>
<field refid="cost"/>
</transcript-detail-portlet>
<transcript-detail-portlet id="tracking" column="2" row="2">
<transcript-detail-portlet-label lang="en_US">Tracking</transcript-detail-
portlet-label>
<field refid="status"/>
<field refid="completed_date"/>
<field refid="certifications"/>
</transcript-detail-portlet>
</transcript-detail-layout>
6. Save the template and upload it to Provisioning where you exported the template.
Configure the field layout in the learning activity template to determine how learning activity fields are shown on
the UI.
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 Technical
Support.
Context
Procedure
In the legacy version of Development Goals, learning activities are shown in a table below a development goal
and learning activity fields are shown as table columns. In the following example, the table consists of four
columns, showing the name and description, status, completed_date, and purpose fields respectively.
Sample Code
<plan-layout>
<column weight="40.0">
<field refid="name"/>
<field refid="description"/>
</column>
<column weight="20.0">
<field refid="status"/>
</column>
<column weight="20.0">
<field refid="completed_date"/>
</column>
<column weight="20.0">
<field refid="purpose"/>
</column>
</plan-layout>
In the legacy version of Development Goals, learning activity fields in the creating or editing dialog are shown in
sections. In the following example, there are three sections, from left to right namely, General Info, Details, and
Process Info.
• The General Info section shows the start_date, due_date, and customtext11 fields.
• The Details section shows the guid, customdate1, and customtext12 fields.
• The Process Info section shows the comfirmed_status and confirmed_by fields.
Sample Code
<transcript-detail-layout>
<transcript-detail-portlet id="general" column="1" row=“1”>
<transcript-detail-portlet-label lang="en_US">General Info</transcript-
detail-portlet-label>
<field refid="start_date"/>
<field refid="due_date"/>
<field refid="customtext11"/>
</transcript-detail-portlet>
<transcript-detail-portlet id="details" column="1" row="2">
<transcript-detail-portlet-label lang="en_US">Details</transcript-detail-
portlet-label>
<field refid="guid"/>
<field refid="customdate1"/>
<field refid="customtext12"/>
</transcript-detail-portlet>
5. Save the template and upload it to Provisioning where you exported the template.
Configure the learning activity template to enable a deep link for learning activities. When users choose a learning
activity added from SAP SuccessFactors Learning, they can be directed to the Learning page.
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 Technical
Support.
Procedure
Sample Code
4. Save the template and upload it to Provisioning where you exported the template.
Configure the learning activity template to disable the fancy layout for the name, description, and status fields
shown in the popup where users create or edit custom learning activities.
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 Technical Support.
Procedure
<switches>
<switch for="transcript-disable-fancy-pod" value="on"/>
</switches>
4. Save the template and upload it to Provisioning where you exported the template.
Configure the learning activity template to show competencies' expected rating as N/A in the Learning Activities by
Attributes dialog when users' current rating is N/A.
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 Technical Support.
The default rating scale used in the Learning Activities by Attributes dialog is 1–5. If users' current rating has been
provided in a different rating scale, the system uses the custom rating scale to calculate the expected rating. For
example, the custom rating scale is 0–4, the expected rating percent defined in Job Profile Builder is 50%, and the
expected rating is calculated as 2 (50% * (4-0) + 0). If users' current rating is N/A, the system uses the default
rating scale (1–5) to calculate the expected rating. In the example above, the expected rating is calculated as 3
(50% * (5-1) + 1).
However, customers who're not using the 1–5 rating scale can choose to show the expected rating as N/A when
users' current rating is N/A, so as to avoid confusion to users.
Procedure
obj-plan-id?,obj-plan-type?,obj-plan-name+,obj-plan-desc?,obj-plan-
lastmodified?,obj-plan-start?,obj-plan-due?,obj-plan-numbering?,switches?,custom-
scale?,
category-config?,add-wizard?,summary-section?,text-replacement*,obj-
library?,behaviors?,self-assessment?,assessment-filters?,learning-activities?,
category*,default-category?,competency-filters?,field-definition+,obj-plan-
states?,permission*,field-permission*,value-permission*,calculator*,
auto-population*,plan-layout,form-layout,pdf-layout?,details-layout,competency-
wizard-layout?,custom-wizard-layout?,transcript-list-layout?,
transcript-detail-layout?,mobile-field-list?
4. Save the template and upload it to Provisioning where you exported the template.
Import a CSV file to create, edit, or delete custom learning activities using Import Development Goals.
Prerequisites
1. In Admin Center, go to Goal Management Feature Settings and select Goal Import.
2. In Admin Center, go to Import Development Goals.
3. Select a development goal plan template from the Available List of Templates dropdown, and choose Generate
a CSV Header to download the import template.
Columns for learning activities in the template are appended immediately after development goal fields and are
the same as the fields configured in the learning activity template.
4. Fill in the CSV file and upload it.
a. To create a learning activity, fill in the CSV file as follows:
Leave the SUBGUID and LEARNING_guid columns blank. When a learning activity is created, the system
automatically generates a value starting with MANUAL$. Leave the LEARNING_dev_goals column blank as
well. The column is used to specify the mapping relationship between a development goal and learning
activity. When a learning activity is created, the system automatically generates a value for it.
If you create, edit, or delete a learning activity for a development goal that was created on the UI, use the ID
column to enter the development goal ID instead of GUID.
You can mass delete learning activities through one CSV file, but you can't do it in one row. Instead, specify
a row for each learning activity.
When deleted, the backend status of a learning activity is changed from IS_ACTIVE to N, which means the
learning activity becomes inactive, but the learning record or relevant mappings are not deleted.
5. Choose Import.
When the import job is finished, you receive an email about the job results.
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 Technical Support.
You can search learning activities by relevant competencies. The display of competency-related information in the
learning catalog pop-up window is controlled by the optional hide-competencies tag.
Career Worksheet allows users to manage the job roles they're considering and the associated competencies, so as
to gain an understanding of the development efforts required to move into target roles.
Note
This is an SAP SuccessFactors Business Beyond Bias feature. Use it to support processes that detect, prevent,
or eliminate the influence of bias, helping you achieve your diversity and inclusion goals.
Each role on the Career Worksheet displays the job code, description, and required competencies. It can also
display a gap analysis for each competency, comparing the last rating specified for the employee with an expected
rating for the role. If a competency has either a last rating or expected rating, or both, a horizontal bar graph for
ratings is shown below the competency.
You can manage the access permissions to Career Worksheet and specific career worksheet plans. In addition, you
can also define the permissions to view, add, or remove the target job roles in the career worksheet plans or the
read permissions of fields in the plans.
Grant the required role-based permission so that the permitted roles can access Career Worksheet under
Development.
Prerequisites
Procedure
Career Development Plan (CDP) Access Permission controls access to Career Development Planning
5. Enable Career Worksheet Access Permission. You can also enable Career Worksheet Suggested Roles Access
Permission, which allows the role to access the Career Worksheet Suggested Roles tab.
Next Steps
To be able to access the content of the Career Worksheet tab, users must have the permission to the career
worksheet template. Without the permission to the career worksheet template, when they open the Career
Worksheet tab, they are not authorized to view the career worksheet plan.
Next task: Granting Access Permission to Career Worksheet Template [page 179]
Grant the access permission to the Career Worksheet template so that users can view the individual's Career
Worksheet.
Prerequisites
Context
The permission to view Career Worksheet is managed by target population. For example, an employee can view
their own Career Worksheet but isn't allowed to view others' Career Worksheet. A manager, however, can view the
Career Worksheet of their direct reports.
Procedure
Results
The relevant role can view the Career Worksheet of the people who belong to their target population.
Next Steps
You can further customize the permission to target roles and read permissions for certain fields in the Career
Worksheet.
The detailed permission to target job roles and read permission to certain fields in a career worksheet plan are
defined in the career worksheet template. Note that the career worksheet template can only be exported for editing
through 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 Technical Support.
Permission Roles
The permissions in the career worksheet template are assigned based on roles, and the common roles that you can
use are as follows:
• E: Employee
You can define detailed permissions over the target job roles in the Roles I’m Considering... section, that is, who can
view, add, or remove target job roles of an user.
Following are the available permissions and XML definition examples that you can use in the template file:
private-access The permission to view the available tar- Employees themselves, all the managers
get roles of an employee. in their reporting lines, and their HR man-
ager can view the target roles. For this
scenario, you can define the definition as
follows:
<permission for="private-
access">
<description><!
[CDATA[Employees and
their managers up
the reporting chain
may view “Job Roles
I’m Considering”.]]></
description>
<role-name><!
[CDATA[E]]></role-name>
<role-name><!
[CDATA[EM+]]></role-name>
<role-name><!
[CDATA[EH]]></role-name>
</permission>
create The permission to add target job roles for Only the employees themselves and their
the employee. direct managers can add target job roles.
For this scenario, you can define the defi-
nition as follows:
<permission for="create">
<description><!
[CDATA[Only the employee
and their direct manager
may add a role in
a user's worksheet.]]></
description>
<role-name><!
[CDATA[E]]></role-name>
<role-name><!
[CDATA[EM]]></role-name>
</permission>
delete The permission to remove target job Only the employees themselves can re-
roles from the section. move target job roles. For this scenario,
you can define the definition as follows:
<permission for="delete">
<description><!
[CDATA[Only the employee
may delete role in
his/her worksheet.]]></
description>
<role-name><!
[CDATA[E]]></role-name>
</permission>
You can define the read permissions for the fields in the career worksheet plans. Note that the write permission is
not supported.
• readiness_meter
The percentage rate of readiness for the target roles.
• development_goals
Development goals associated with each competency or behavior. The number of development goals and the
button to add a new development goal are displayed by default. But the details of the development goals
nested under a competency or behavior is controlled by the permission defined here.
Note
By default, the read and write permissions for the user are derived from the development plan template
configuration. If a user is granted the read permission in the career worksheet template without permission
to view development goals, they still cannot view the details of the goals.
Note
If a role has the read permission to other competency-related details (for example, last_rated_date and
last_rated_form), this read permission to competency_name should also be granted. Otherwise, the
competency will be listed as “undefined” as its name.
• last_rated_date
The date on which the competency was last rated.
• last_rated_form
The form in which the competency was last rated.
• gap_graph
A graphical representation of comparison between the expected competency rating and the user’s latest
rating.
• last_rating
The user’s latest competency rating. Note that the read permission for last_rating is a prerequisite
for a user to view the graphical representation (gap_graph). If you have defined the read permission for
gap_graph, define it for last_rating as well.
Previous task: Granting Access Permission to Career Worksheet Template [page 179]
A Career Worksheet template, specified in an XML file, defines fields, features, and permissions of Career
Worksheet.
• Field labels
• Inclusion of fields, for example, you can remove the gap_graph field if you don't want to include the gap
analysis graph.
• The rating-scale-id, in the last_rating field definition. It's the normalized scale used for showing rating
comparisons.
• Permissions for features and fields
• The maximum number of job roles that users can add, with the max-per-category attribute
Example
<category-config>
<max-per-category>5</max-per-category>
</category-config>
competency_name text
last_rated_form text
last_rated_date date
last_rating number
gap_graph number
development_goals text
readiness_meter percent
In the Career Worksheet, by default, users can view the number of employees who are in their target roles and the
number of open positions of their target roles. You can configure the Career Worksheet template in Provisioning to
hide both of them or open positions only.
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 Technical Support.
In the Career Worksheet, users can view the information of at most 20 current employees by choosing [Number]
Employees. If the number of current employees is more than 20, they can choose Show All [Number] Employees to
view all on the Directory Search page.
If Employee Directory isn't selected in Provisioning, users can only view the number of current employees, but can't
choose [Number] Employee to view the detailed information.
Open positions shown in the Career Worksheet are from legacy Succession positions, not from MDF positions.
Procedure
• To hide both current employees and open positions, change the cws-people-role attribute from "true"
to "false".
• To hide open positions only, add the following XML code in the <switches> element:
Sample Code
Configure the Career Worksheet template to show not-applicable competencies so that users can view the details
of those competencies in the Career Worksheet. The details include expected rating, last rating, rating date, and
rating source.
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 Technical Support.
Context
Not-applicable competencies refer to the competencies that were unrated in employees' last performance review.
By default, they are listed in the section of the competencies that employees need to work on, and a horizontal bar
chart showing last rating and expected rating is not available.
When you enable showing not-applicable competencies in the Career Worksheet template in Provisioning, users
can see the following changes on the Job Roles I'm Considering and My Current Roles tabs.
Note
For employees' target roles, the last rating of not-applicable competencies is not included in the calculation
of role readiness.
Procedure
Sample Code
4. Save the template and upload it to Provisioning where you exported the template.
Results
Users can view the details of not-applicable competencies in the Career Worksheet.
Configure the Career Worksheet template to show "Too New to Rate" so that the rating is available in the horizontal
bar chart for ratings in the Career Worksheet.
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 Technical Support.
Context
"Too New to Rate" relates to a special rating on the rating scale that performance reviewers can select when they
think it's too early to give a regular rating. By default, it is not shown in the employees' Career Worksheet.
When you enable showing "Too New to Rate" in the Career Worksheet template in Provisioning, users can see the
following changes on the Job Roles I'm Considering and My Current Roles tabs.
• If the last competency rating is "Too New to Rate", a stop sign ( ) representing "Too New to Rate" is shown in
green on the left side of the horizontal bar. Expected rating, if any, is shown in blue.
• If the last competency rating is not "Too New to Rate", the stop sign is shown in black on the left side of the
horizontal bar.
Procedure
Sample Code
4. Save the template and upload it to Provisioning where you exported the template.
Results
Users can view "Too New to Rate" in the horizontal bar chart for ratings.
Configure the Career Worksheet template to show the number of development goals for a competency created
from users' default development plan. Users can also create development goals for the competency directly in the
Career Worksheet.
Prerequisites
Note
If you use behaviors instead of competencies, make sure that the competencies field is configured
accordingly.
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 Technical Support.
Users who have read and write permissions for the competencies field in the development goal plan template
can view and add development goals in the Career Worksheet. The development goals that users create from the
Career Worksheet are added to their default development plan.
Because a development goal can be linked to more than one competency, the same goal can be counted more than
once in the Career Worksheet. The same goal can also be represented in more than one job role.
Procedure
Sample Code
4. Optional: To show the competency description by default, add the following switch.
<switches>
<switch for="cws-dispoption-competency-desc" value="on"/>
</switches>
5. Save the template and upload it to Provisioning where you exported the template.
Results
By default, behaviors that are mapped to a job role are shown in the list of required competencies for the role.
You can configure the Career Worksheet template to decide whether to show behaviors and behavior ratings, and
whether to include behavior ratings in role readiness calculation.
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 Technical Support.
Procedure
Sample Code
Behaviors are shown for each competency, but behavior ratings aren't shown or included in role readiness
calculation.
c. To show behaviors and ratings, but exclude the ratings from role readiness calculation, set hide="false",
hide-ratings="false", and use-in-readiness="false".
Behaviors and ratings are shown for each competency, but aren't included in role readiness calculation.
4. Save the template and upload it to Provisioning where you exported the template.
Results
Configure the Career Worksheet template to show the job profiles of job roles from Job Profile Builder.
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 Technical Support.
Context
When you've enabled Job Profile Builder, we recommend that you perform this task. Otherwise, there will be data
discrepancies in Career Worksheet: My Job Roles and Suggested Roles sections show the job description defined
in Job Profile Builder, whereas the Browse job roles... dialog shows the job description defined in Job Description
Manager.
Procedure
<switches>
<switch for="disable-jpb-profile-in-cws" value="off"/>
</switches>
4. Optional: To continue using job profiles in Job Description Manager, set value="on" as follows.
<switches>
<switch for="disable-jpb-profile-in-cws" value="on"/>
</switches>
5. Save the template and upload it to Provisioning where you exported the template.
The job profiles of job roles shown in Career Worksheet come from Job Profile Builder.
Role readiness provides valuable metrics that help employees plan their career development. By adding roles they
are considering to Career Worksheet, they can start regularly tracking and measuring development to prepare
themselves for the future roles and responsibilities.
A role might require a number of competencies and each competency can have an expected rating. An employee's
readiness for the role depends on whether the employee’s current competencies are up to the expected ratings. If
Job Profile Builder is used, when a competency's expected rating is 0, 0 is a valid value in the calculation of role
readiness. If Job Decription Manager is used, when a competency's expected rating is 0, the expected rating is
regarded as N/A (no expected rating) in the calculation of role readiness.
Both calculation options require the employees’ current competency ratings of competencies, which can come
from the following:
By default, the system uses the latest rating information in the system. You can also specify a specific form or a
couple of forms as the source of the existing ratings.
Related Information
Role readiness can be calculated as the percentage ratio between employees’ ready competencies and the total
of required competencies for the role: (number of competencies the employee is ready for)/(total number of
required competencies) %.
To determine whether an employee is ready in a competency, the system checks the employee’s current rating and
the expected rating required for the future role. If the current rating equals to or exceeds the expected rating, the
employee is ready for this competency.
Note
However, you may not have an expected rating for all competencies, in that case, the employee is regarded as
not ready for that competency regardless of his or her current rating.
For example, a role requires five competencies. For one of the competencies, the expected rating is 4 and the
employee’s current rating is 5. And for all other four competencies, the employee isn’t ready, either because the
current rating is lower than expected or because the competency hasn’t been rated. Then, the role readiness is
calculated as (1/5) x 100% = 20%.
Behaviors you have defined for competencies in Job Profile Builder can also be considered when calculating role
readiness. Turn on the XML switch in the Career Worksheet template, and the role readiness is calculated as (total
number of current competencies and behaviors that the employee is ready for)/(total number of required
competencies and behaviors)%.
For example, a role requires two competencies and each competency has two specified behaviors. One of the
competencies and one of the behaviors equal to or exceed the expected ratings. In this case, the role readiness is
calculated as (1+1)/6 x 100% = 33%.
Related Information
With this averaging-out calculation option, the system first calculates readiness for each required competency for a
role, and then calculates an average of the competency readiness, which is used as the role readiness.
The employee’s current competency rating is lower than the (Current rating – smallest rating in the rating scale)/(Expected
expected rating. rating – smallest rating in the rating scale) 100%
Note
The calculation is done in the rating scale defined in the Career Worksheet template. If you use a different scale
to rate the employee's competencies, the system will normalize the ratings for calculation.
Then, with the readiness for each competency calculated, the system adds up the readiness rating for all required
competencies in a role and divides the total by the number of competencies.
If you have defined behaviors and enabled behavior rating in role readiness calculation, the calculation logic of
behavior readiness is the same and role readiness is the average of both competency and behavior readiness.
Example
For a rating scale from 0 to 5, see the following expected ratings and the employee’s current rating.
Engineering 4 5 100%
Communication 4 3 75%
Presentation 4 2 50%
Then, the role readiness is calculated as (100% + 66.67% + 75% +100% + 50% + 50%)/6 x 100% = 74%.
To specify the calculation option the system uses to calculate role readiness, define the calculation option switch in
the Career Worksheet 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 Technical Support.
Procedure
If no switch configuration is added, the system, by default, calculates the role readiness by summing up the
number of ready competencies.
The system uses the specified calculation option to determine the role readiness.
Related Information
By default, ratings from completed performance review or 360 review forms can be used to determine the current
competency rating. However, you can also specify a specific form or a number of forms as the only source of
existing ratings.
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 Technical Support.
Procedure
1. In Provisioning, go to Form Template Administration, and find the ID of the review form templates that you use
as the competency rating source.
2. Go to Manage Plan Template Import/Update/Export Career Worksheet Templates and export the
template.
3. In the template, add the XML definition that includes the source form template IDs. See the following XML
configuration sample:
<assessment-filters>
<include-form-ids lang="de_DE">1, 2, 3</include-form-ids>
<include-form-ids lang="en_US">1,5</include-form-ids>
</assessment-filters>
Results
You have configured the Career Worksheet template for the rating source and the system only uses the ratings
from the specified forms to calculate an employee’s readiness for a future role.
Related Information
You can include a link in the Career Worksheet, with which employees, managers, and any other roles who have
permission can launch an assessment form for role readiness and rate employees' competencies for a target role.
Remember
To configure and use the role readiness form, you must have access to the Performance Management module.
Choosing the link directly opens the form, bypassing usual form creation steps. The default dates are used for
the form. The form is configured to auto-populate competencies and include all competencies for the role. As an
admin, you can't use proxy to access users' role readiness forms.
The competencies that are available in the role readiness form are the competencies that have been defined in the
current sign-in locale. If a competency is defined in English only, and when a user signs in the system with Chinese,
the competency isn't available in the form.
Note
By default, the form setting in Admin Tools 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. The form title has the following behaviors:
You can enable 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, if you want the form title to
behave like the following:
Once the form is complete, the updated ratings are used in the Career Worksheet. Users can relaunch the form as
many times as required. Rules governing the official competency ratings are as follows:
• The latest official rating from any form is the one used in the Career Worksheet.
• Competency ratings aren't differentiated by role (for example: a rating of 5 on Communications applies to both
the current role and a target role, if they share that competency).
• Some functions can differentiate ratings by form, including Dashboards, List Views, and People Profile.
• Other functions can't differentiate by form, including Career Worksheet, Talent Search, Side-by-Side
Comparison, and Succession Org Chart.
Caution
Alternate configurations may not be supported and should be deployed with extreme care.
Related Information
Configure the Career Worksheet template to allow employees to launch role readiness forms for their target role.
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 Technical Support.
Context
Role readiness assessment is form-based, and you need to add the ID of the form template used for role readiness
assessment in the Career Worksheet template.
When available, the assessment results are just regarded as another rating source in addition to performance
review or 360 review. When employees open the Career Worksheet, the role readiness shown in the worksheet is
always calculated based on the latest ratings, be they from assessment forms, performance review, or 360 review.
Procedure
1. In Provisioning, go to Form Template Administration, and find the ID of the form template used for role
readiness assessment.
2. Go to Manage Plan Template Import/Update/Export Career Worksheet Templates and export the
template.
3. In the template, add the XML definition that includes the form template ID:
<self-assessment>
<each-assessment lang="locale">form template ID</each-assessment>
</self-assessment>
Note
You can only specify one form template for role readiness assessment.
The Evaluate Readiness link appears in the competency section of Career Worksheet. Employees can choose the
link to launch role readiness forms.
Related Information
Configure the Career Worksheet template to allow more roles such as manager and HR to launch role readiness
forms for an employee’s target role.
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 Technical
Support.
• You've enabled Performance Management and configured a form template for role readiness assessment. In
this form template, you've configured settings to allow other roles to launch forms for the employee role.
• Users are granted the private-access permission and the readiness_meter field permission in the Career
Worksheet template.
Sample Code
<permission for="private-access">
<description><![CDATA[E, EM, and EH can view unshared/private roles.]]></
description>
<role-name><![CDATA[E]]></role-name>
<role-name><![CDATA[EM]]></role-name>
<role-name><![CDATA[EH]]></role-name>
</permission>
Sample Code
<field-permission type="read">
<description><![CDATA[E, EM, and EH can view the percentage rate of
readiness for target roles.]]></description>
Context
As more roles obtain the ability to launch role readiness forms, the way the link to the forms shows in Career
Worksheet can vary. This variation occurs across route map steps and roles’ views. Consider a use case when
a manager is going to launch a form and the form's route map follows an E > EM > Completion sequence. The
following table explains the different scenarios in this case in detail.
Before a form is launched The link shows Evaluate Readiness, and The link shows Evaluate Readiness, and
the employee can choose it to launch a the manager can choose it to launch a
form. form.
EM (The step is automatically added The link shows In Progress, but it's not The link shows In Progress, and the man-
to the route map because the manager clickable because the form hasn't been ager can choose it to open the form and
launched the form.) routed to the employee's form inbox yet. take action.
E The link shows In Progress, and the em- The link shows In Progress, and the man-
ployee can choose it to open the form ager can choose it to open a read-only
and take action. version of the form.
EM The link shows In Progress, and the em- The link shows In Progress, and the man-
ployee can choose it to open a read-only ager can choose it to open the form and
version of the form. take action.
Completion The link shows Evaluate Readiness, and The link shows Evaluate Readiness, and
the employee can choose it to launch a the manager can choose it to launch a
new form. new form.
Procedure
1. In Provisioning, go to Form Template Administration and find the ID of the form template used for role readiness
assessment.
2. Go to Manage Plan Template Import/Update/Export Career Worksheet Templates and export the
template.
3. In the template, add the XML definition that includes the form template ID:
<self-assessment>
<each-assessment lang="locale">form template ID</each-assessment>
</self-assessment>
Note
• You can specify only one form template for role readiness assessment.
In the following example, the employee, manager, and HR roles can launch role readiness forms for an
employee's target role.
Sample Code
<permission for="launch-assessment-form">
<description><![CDATA[E, EM, and EH can launch role readiness forms for an
employee's target role.]]></description>
<role-name><![CDATA[E]]></role-name>
<role-name><![CDATA[EM]]></role-name>
<role-name><![CDATA[EH]]></role-name>
</permission>
Note
Employees are allowed to launch role readiness forms without this permission configuration. However, if
you configure this permission setting to allow other roles to do so but don't include the employee role,
employees are no longer able to launch forms by themselves.
Results
The Evaluate Readiness link appears in the competency section of Career Worksheet. Users can choose the link to
launch role readiness forms.
You can allow employees to launch role assessment forms for their current roles directly in Career Worksheet.
Prerequisites
• You've configured a Performance Management form template for current role assessment. You can configure
the form template in the same way of configuring the form template for role readiness assessment. See
Assessment Form for Role Readiness [page 198].
• You have access to Provisioning.
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 Technical
Support.
Context
When you enable this function in the Career Worksheet template in Provisioning, employees don't have to navigate
to Performance to create assessment forms. They can launch forms for current role assessment directly from
Career Worksheet. If they have more than one current role, only the competencies of the selected role are to be
assessed in forms.
Procedure
1. In Provisioning, go to Form Template Administration and find the ID of the form template used for current role
assessment.
2. Go to Manage Plan Template Import/Update/Export Career Worksheet Templates and export the default
template.
You can only enable current role assessment in the default template.
3. In the template, add the following XML code:
4. In the template, add the following definition that includes a form template ID:
<current-self-assessment>
<current-each-assessment lang="en_US">form template ID</current-each-assessment>
</current-self-assessment>
Results
The Evaluate Readiness link appears in the competency section of Career Worksheet. Employees can choose the
link to launch self-assessment forms for current roles.
Future roles are automatically suggested to employees based on a set of criteria you can adjust.
The Suggested Roles feature provides a proactive step in employee development by automatically recommending
future roles to an employee. The system uses an algorithm to produce the list of suggested roles and calculates a
score (0-1) for the role based on the following criteria:
Competencies associated with The system uses the Career For example, if the readiness is 40%
the role Worksheet readiness calcula- 40%, the score is then 0.4.
tion to compute a competency
match score. The score com-
pares the employee's compe-
tency rating with the expected
rating for the role.
Common job family Roles in the same family as The score is determined ac- 20%
Open positions for the role The algorithm looks at the The score is determined by 10%
Note
This criterion is only avail-
able when Position is
selected for Succession
nomination method in
Provisioning.
Popularity of the role within The more popular a role is in The score is calculated with 10%
Each of these criteria is then multiplied with the configured weight to calculate a final score for each of the
considered roles. The roles are then ranked from highest score to lowest and displayed on the Suggested Roles tab.
Note
The algorithm only fetches 60 roles. Any filters applied to the search filter those 60 roles. The display is limited
to 4 pages of role cards and is therefore affected by screen size.
The suggested roles are only accessible to the employees themselves. Managers can't view the suggested roles
of their direct reports.
You can refine and control the algorithm that drives the results of suggested roles in Career Worksheet.
Prerequisites
Context
You can distribute weights for each set of criteria as well as remove some of the criteria all together.
Procedure
Next Steps
You can further enable filters to allow users to narrow the list of roles suggested.
Related Information
Enable filters on the Suggested Roles tab to allow users to narrow the list of roles suggested.
Prerequisites
Context
To allow users to filter out roles that are not aligned with their career interests, you can introduce the following
filters on the Suggested Roles tab in Career Worksheet:
• Competencies
• Job Families
• Relevant Industries
Note
Filtering for relevant industries is only available when you use Job Profile Builder.
The list of suggested roles is determined based on the range of defined algorithm criteria and weighting. With the
filters, users can narrow down the suggested roles to those belonging to certain competencies, job families, or
industries. Nevertheless, in some circumstances, applying such filters may not influence the content and order of
the list. For example, you have adopted one criterion (Job Family) for the algorithm, and the employee can use the
Job Families filter to look for roles that belong to the same job family of his or her current role. In such cases, the list
of the suggested roles won’t change after the filtering.
Procedure
Related Information
Customers who have SAP SuccessFactors Learning can assign learning activities to their learning management
system to-do list in the Career Worksheet page of each target role.
Users can access a graphic view of the different career paths that their current role or target roles could lead them
to.
For any role that has a career path defined in the system, users can access the graphical career path view by
choosing View Career Path in the Career Worksheet. The career path appears in a dialog box, shown as follows.
Users can take the following actions in the career path view:
• If the system uses Job Profile Builder, the permission is User Miscellaneous Permissions Career Path .
• If the system uses Job Description Manager, the permission is User Miscellaneous Permissions Legacy
Career Path .
In the Career Worksheet, you can include the Show in People Profile checkbox on each target role for users to
select, so they can specify the job role as a career interest in their People Profile.
Prerequisites
You've specified preferredNextMove in the background-element tag defined in the live profile data model and
included title in the data-field tag defined within that background-element.
Example
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 Technical Support.
Caution
Don't set any fields in the background-element to required="true", except for title. Otherwise, the
Career Worksheet can't add records to the background-element, since it's only populating the title field.
The fields must have a lowercase letter as the initial letter of the ID. If the first letter of the ID is uppercase, you'll
receive an error.
Note that this feature only copies the job role name from the Career Worksheet to the live profile data model. If
users enter a job role name directly in People Profile, and the job role is in their Career Worksheet, the checkbox is
selected automatically.
Be aware of the following feature differences when you've enabled the latest People Profile:
• Target roles only from the default Career Worksheet template with Show in People Profile selected are shown in
the Spotlight and Full Profile.
• If the Full Profile is not enabled yet, the Show in People Profile checkbox continues to be available in non-default
Career Worksheet templates. However, if the Full Profile is enabled, the checkbox is no longer available in
non-default templates.
Procedure
1. In the Career Worksheet template, enable the share permission for relevant roles.
In this example, only employees can select the checkbox to show target roles in People Profile.
<permission for="share">
<description><![CDATA[Only the employee may copy roles to their live profile
page.]]></description>
<role-name><![CDATA[E]]></role-name>
</permission>
2. Grant the roles the View permission for Manage Permission Roles User Permissions Employee Data
Preferred Next Move .
Results
Users with granted permissions can select the Show in People Profile checkbox in Career Worksheet.
Career Worksheet allows users to manage their current and target roles and associated skills and attributes.
Through the redesign of key features and interactions, we've significantly improved users' experience with it.
The new experience starts from Growth Portfolio, where users can preview the information about their current
roles and target roles, if any, in the Roles and Aspirations section. The information includes top three skills and
attributes they've already achieved or they need to improve, and their readiness for a role. Choosing the Explore
Career Options button directs users to a page where they can explore recommended career roles.
For each role, users can view more information about the role on its details page, including the following:
Users can also perform the following actions specific to a current, target, or recommended role:
Related Information
Users can explore recommended roles in both card and chart views, and delve into a role's details by choosing the
role card.
By choosing Explore Career Options in Growth Portfolio, users are directed to a page, where recommendations are
organized in several sections.
Next Career Move The system retrieves the next role of an • Enable Career Path V2 is selected in
employee's current role from organiza-
Provisioning.
tional career paths set by HR managers
and administrators. • Users have the View permission to
any of the following permissions de-
pending on your system:
• User Miscellaneous
• User Miscellaneous
Trending Roles The system recommends roles with open • MDF Position is selected for
positions.
Succession Nomination Method in
Provisioning.
• The system was migrated from Job
Profile Builder to Talent Intelligence
Hub.
Roles of People Like You The system uses role recommendations You've enabled Career Explorer. See Ca-
from the Career Explorer feature. reer Explorer [page 225] for more infor-
mation.
Each section recommends at most 16 roles. For the system migrated from Job Profile Builder to Talent Intelligence
Hub, on each role card, users can add the role to Bookmarks in Opportunity Marketplace, or mark it as not
interested.
By choosing Navigate Career Paths on the Explore Career Options page, users can discover recommended roles in a
chart view. An employee's current role is the starting point of the chart, followed by recommended roles including
the "Organizational path" roles from organizational career paths and the "Personalized path" roles that are highly
matched with the employee.
• On the "Organizational path" role card, users can check a role's peer roles, if any.
• On the "Personalized path" role card, users can learn about why a role is recommended to them. The
recommendation reason could be one of the following factors according to their influence on the match score:
"[number] matched skills", "Same job family", "Progression role", "Open positions", and "Popular".
The chart view also supports switching between different current roles. If users have more than one current role,
they can select a role and discover the recommendations specific to the role. Expanding recommended roles in the
first layer gets recommendations from organizational career paths in subsequent layers. To get personalized role
recommendations in those layers as well, contact Product Support to enable the advanced feature.
Enable the latest Career Worksheet in Upgrade Center so that your users can try out the new experience for using
Career Worksheet.
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 Technical Support.
Context
If you haven't enabled Growth Portfolio or Opportunity Marketplace, the Latest Career Worksheet option is not
available in Upgrade Center.
When the upgrade is done, the Growth Portfolio landing page and the Role Details page in Opportunity Marketplace
are replaced with the new version, whereas the legacy Career Worksheet still exists through Development
Career Worksheet .
1. Go to Upgrade Center.
2. Under Optional Upgrades, find Latest Career Worksheet and choose Learn More & Upgrade Now.
3. Choose Upgrade Now.
Results
You've upgraded to the latest Career Worksheet. You can undo the upgrade within 30 days.
Related Information
Learn about feature differences between the legacy and latest Career Worksheet and unsupported features and
known behaviors in the latest Career Worksheet.
Here are major feature differences between the legacy and latest Career Worksheet:
• Only the default Career Worksheet template is used in the latest version.
• Skills and attributes are shown in a card view in the latest version, consistent with those in Growth Portfolio. By
choosing the card, users can view more information about a skill or attribute in a dedicated page.
• The rating scale used in the latest version follows that configured in Growth Portfolio rather than the Career
Worksheet template.
• Expected and current ratings shown in the skill or attribute card are rounded to the nearest whole number in
the latest version.
• The Suggested Roles feature is enhanced in the latest version. See Recommended Roles in Latest Career
Worksheet [page 213] for more information.
If a skill or attribute associated with a user's current or target role is not added to the user's Growth Portfolio,
there are issues with the skill or attribute card. We recommend that users add the skill or attribute to their Growth
Portfolio.
• When users choose the skill or attribute card, there's no response to open the details page.
• When users have given a rating on the skill or attribute in a self assessment form, the rating is not updated in
the skill or attribute card.
Leveraging generative AI capabilities, employees can gain insights into development actions they can take towards
their target role.
In the latest Career Worksheet, employees can access the feature by choosing the Generate button in the new
Boost your career with AI-powered insights! section on a target role's details page. Generative AI produces insights
by considering several factors, including employees' current role information, their skill and attribute ratings, and
the description, required skills, and expected ratings of the target role. Such generated insights cannot be saved on
the page. If users refresh the page or return after leaving it, they can generate content again.
The insights are organized into sections to help employees grasp the most important aspects of their development:
• Summary: Provides a high-level overview of the employee's current role and target role.
• Suggestions for Improvement: Identifies three growth areas for upskilling and career development, and for
each area, provides achievable suggestions in the following aspects:
• Skills and attributes in this category
• Keywords of learning courses
• Ideal mentor's position
• Suggested development goal. Besides it, employees can directly create a development goal from scratch
or with the help of generative AI by choosing the Create Goal link.
Enable the AI-assisted career insights feature so that employees can gain insights into development actions they
can take towards their target role.
Prerequisites
Procedure
3. Go to Manage Permission Roles and grant employees the User AI Access Assisted Career Insights
permission.
Results
Career Path allows HR managers and HR administrators to create unique and complex organizational career paths.
Users can create multiple new career paths and associate them to a given role. They can also restrict employee
access to the career paths displayed in the Career Worksheet based on criteria such as role, department, and
division. The career paths created are instance-wide.
To access Career Path, users go to Development Career Path . Here's a screenshot of Career Path, where
users can create, view, and edit career paths.
Use
Users add the first node to the career path by choosing in the Select a role area. A role selection window appears
where they can select the role that they want to add as the first node in the career path. They can toggle between a
tree view (roles are organized hierarchically into families) and list view (all roles are displayed) in the role selection
window. They can also enter a role name or the start of a role name in the search field to narrow down the list of
roles displayed.
Note
Remember to save changes by choosing Save in the lower-right part of the window.
Related Information
Grant required role-based permissions so that permitted roles can use Career Path under Development.
Prerequisites
Procedure
For the organizations that don't use Career Worksheet, to allow employees to view career paths, grant them the
View permission to Career Path.
6. To allow users to specify which elements of basic information to display or hide for a career path definition,
select Field Level Overrides.
7. To restrict users' access to specific career paths based on code, business unit, division, department, or other
custom views, go back to the Permission Role Details page of the selected role. Scroll to the Grant this role to
section, and choose Edit Granting.
8. In the Grant this role to popup window, scroll to the Specify the target population for the other objects section.
Next to Career Path, select the Restrict target population to option and specify the restrictions in the dropdown
menu.
9. Save your changes.
Related Information
You can create, edit, and delete career paths by importing a CSV file in Import and Export Data.
The object definitions you can select to import and export career paths are as follows:
• Career Path: This contains the career path basic information such as external code, name in the default
language, and name in other languages supported in the system. If you create a career path by import, you can
input this information as you want.
• Career Path-Career Path Details: This contains the career path details information, including the following:
• External Code: System-generated code when a role is added to a career path on the UI. If you add a role by
import, you must input a number as an external code.
• Role GUID: GUID of a role, used to map lead-from and lead-to roles. You can obtain role GUID by exporting
the Role object definition in Import and Export Data.
In mapping lead-from and lead-to roles, careerPathDetails.role.externalCode is used to specify
the GUID of a lead-from role and careerPathDetails.nextRole.externalCode is used to specify the
GUID of a lead-to role.
In mapping peer roles, careerPathDetails.role.externalCode and
careerPathDetails.nextRole.externalCode can be interchanged.
• Is Peer Role: Used to identify if two roles are peer roles.
Here is how the career path details looks like in a CSV file:
For more information on how to import and export object definitions, refer to Related Information.
Related Information
Mentoring allows you to manage your organization's mentoring programs, from program setup, participant signup,
matching, tracking, to completion.
For details on how to enable and use Mentoring, refer to the guide in Related Information.
Related Information
Mentoring
Powered by machine learning technology, Career Explorer recommends career opportunities to employees based
on the career paths of people who are similar to them in the organization.
Use
In Career Explorer, employees view recommended job roles and a future career path of each role in a lineage chart
by expanding the role card. They can use the following features to explore the recommended roles:
• View job profiles: View the recommended roles' job profile to see if they're interested in the roles.
• View recommendation reasons: View the reasons why the roles are recommended to them. Employees'
previous jobs, previous job information, and employment data have a great influence on why the roles in
the first layer are recommended. The roles in the second layer and onward are recommended because it's a
common job role that people often transition into from the previously recommended role.
• Add as target roles: If Career Worksheet is used, they can add the recommended roles to Career Worksheet to
do gap analysis for personal skills.
• Dislike roles: If they don't like the recommended roles, they can remove the roles to further personalize
subsequent recommendations. The removed roles won't be recommended to them again. When they remove a
role, any child roles are removed together.
• Check next update date for recommendations: The machine learning algorithm of Career Explorer is
retrained every two weeks, or when there are enough delta changes to the data such as employee and job
information. They can visit the page regularly to explore new possible recommendations. Additionally, if they
remove all the recommended roles, they're notified of a date on which new recommendations may be available.
Prerequisites
To use Career Explorer, make sure that your SAP SuccessFactors system meets all of the following requirements:
Enable the People Connection system, which is built based on SAP AI Business Service Personalized
Recommendation, to prepare for the integration between SAP SuccessFactors and People Connection.
Prerequisites
Your company must have at least 1,000 employee-and-job role pairs in the system.
Note
Employee-and-job role pairs include current and historical data of employee-and-job role pairs. Historical
data can be from your former employees who had been associated with job roles and left the company, or
current employees who changed job roles within the company. The following examples are qualified for the
prerequisite:
• Your company has 1,000 employees and they're all associated with their respective job roles, and there's no
historical data of employee-and-job role pairs.
• Your company has 500 employees and they're all associated with their respective job roles, and there are
500 historical employee-and-job role pairs.
• Your company has reorganized the whole job structure. All the new job roles have replaced the old ones.
You have 1,000 employees and they're all associated with the new job roles.
Procedure
1. Go to Upgrade Center, select the Platform module, and enable People Connection.
2. In Admin Center, go to Manage Permission Roles Administrator Permissions People Connection and
grant admins the permission of Manage People Connection Integration.
Results
Configure the integration settings between your SAP SuccessFactors system and the People Connection system to
retrieve and analyze your employee data.
Prerequisites
Context
If you have configured IP address allowlist in your system, make sure to include IP ranges for SAP AI data centers
in Company Settings Restrict access to IP range in Provisioning before saving the configurations in Manage
People Connection Integration. For more information, refer to KBA 3016222 .
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 Technical Support.
Procedure
You can deselect the option whenever you want to disable the feature. If disabled, all the training data in the
People Connection system is deleted.
3. Enter a Super Admin user.
To allow the People Connection system to retrieve your Employee Central data, the Super Admin user must at
least have the permission of Employee Central API.
4. Select the data center where your SAP SuccessFactors system is deployed.
If you’re not sure in which data center your system is deployed, contact Technical Support.
5. Choose Save.
Results
You’ve configured the integration settings for People Connection. The system can start data sync and data training.
You can track the process status in Manage People Connection Integration.
You can enable Career Explorer when your employee data is qualified for the People Connection system to
recommend career opportunities.
Prerequisites
Context
After data sync between your system and the People Connection system is successful, we provide a data quality
report with multiple parameters in Manage People Connection Integration. After data training is successful, you can
check one of the parameters to see if your company can use Career Explorer.
In addition, after an AI model is trained successfully, we provide trained model metrics to help you understand the
performance and reliability of our trained models.
Procedure
If Recommended Roles is Ready for Use, you can go to Upgrade Center and turn on Career Explorer.
Parameter Description
Employee Data Quality Compared to total employees, the ratio of the employees
that have background education and competency rating in-
formation in your tenant data
Position Data Quality Compared to total employees, the ratio of the employees
that have corresponding job code information in your tenant
data
Employee-Position Ratio The ratio between the number of employees and the number
of positions, calculated as the number of employees divided
by the number of positions.
Tip
The larger the number of pairs, the better the data qual-
ity.
Data Sparsity Data Sparsity indicates unpaired employee and position data
in your tenant data. It is calculated as: 1 − Number of Pairs /
(Number of Employees * Number of Positions).
Tip
The lower the level of data sparsity, the higher the data
quality.
Sparsity Threshold Sparsity threshold is an ideal data sparsity level of your ten-
ant data. It is calculated as: 1 − Max (Number of Employees,
Number of Positions) / (Number of Employees * Number
of Positions).
Note
If your data sparsity level exceeds the sparsity thresh-
old, machine learning doesn't proceed.
Recommended Career Paths When Recommended Career Paths is Ready for Use, em-
ployees can see a future career path for each future role. If
Recommended Career Paths is Not Ready, your tenant data
is insufficient for the system to recommend career paths.
3. Go to Upgrade Center, select the Career Development Plan module, and enable Career Explorer.
• Career Explorer: Allows users to access the Career Explorer tab under Development and use the feature for
their own career opportunities.
• View User's Career Opportunities in Career Explorer: Allows users to view the recommended job roles
and career paths of a selected user within their target population in Career Explorer. Users can't add a
recommended role as a target role or remove it on behalf of the user.
In addition, users must have the User Search permission to search for specific users in Career Explorer.
Results
You can exclude job roles from data sync between your system and the People Connection system, so that they
won't be recommended to employees in Career Explorer.
Prerequisites
Procedure
Results
When you configure the integration with People Connection for the first time, the selected job roles are excluded
from data sync immediately; otherwise, the selected job roles will be excluded during the next retraining session.
Job role recommendations are generated by applying machine learning to user data that includes user attributes
and data related to users' job history.
This data is synchronized periodically from SAP SuccessFactors to the recommendation engine on SAP AI
Business Services. There are three SAP AI Business Services data centers – two in Europe and another one in
the U.S.. The data from your SAP SuccessFactors HCM suite tenant is transferred to a recommendation engine
tenant on an SAP AI Business Services data center.
The following table summarizes the data used to generate recommendations that are transferred to the
recommendation engine.
Employment Information Users' job history, including job classification, department, and
position
Learn about the data used for generating job role recommendations to individual employees.
Background Information
The extract includes selected data fields from users' background information record. These fields are custom
fields.
school School
degree Degree
major Major
degree_editable Degree
major_editable Major
school_editable School
The extract includes the employment information of job roles on which users have taken or are taking.
company Company
manager_id Manager ID
location Location
department Department
division Division
position Position
Competency Rating
rating Rating
If you've migrated to Talent Intelligence Hub, users can use skills besides competencies in Development Goals,
Career Worksheet, and Mentoring.
Development Goals
If you configured the competencies field in the development goal plan template, users can use a picker to add
skills and competencies to development goals.
Be aware of the following feature differences from Development Goals you use before you migrate to Talent
Intelligence Hub:
...
</default-category>
<competency-filters>
<exclude type="forms"/>
<exclude type="roles"/>
<include type="library" match="tag name"/>
</competency-filters>
<field-definition ...>
...
</default-category>
<competency-filters>
<exclude type="forms"/>
<exclude type="roles"/>
<include type="category" match="tag name"/>
</competency-filters>
<field-definition ...>
Career Worksheet
For Career Worksheet use cases, refer to the Using Skills in Career Worksheet topic.
Mentoring
If you defined the Competency picklist as a question category on the mentoring signup form, users can use a picker
to answer questions about skills and competencies when signing up for mentoring programs.
• Skills can't be reported in Table reports, but can be reported in Story reports.
• The Skill picklist used in the condition of Job Profile Builder is no longer available. The Attribute picklist,
previously labeled as Competency, includes both skills and competencies.
Related Information
If you've migrated to Talent Intelligence Hub, users can explore skills besides competencies for their current role
and target roles in the Career Worksheet.
Make sure that you've enabled Growth Portfolio and users have the following role-based permissions for using
Growth Portfolio:
• View the skills and competencies required for a job role. The skills and competencies they need to work on are
shown first, followed by the skills and competencies they've already achieved.
• View the gap between the expected rating of a skill or competency and the self-rating they provided in Growth
Portfolio in a horizontal bar chart.
Note
Because ratings from Growth Portfolio are normalized according to the rating scale configured in the
Career Worksheet template, users may see different ratings in Growth Portfolio and Career Worksheet.
• Create development goals for the skills and competencies they need to work on.
• Check role readiness, calculated using self-ratings and expected ratings of skills and competencies, to see how
prepared they are for a target role.
• Use a picker to filter job roles by skills and competencies when exploring suggested roles.
• Growth Portfolio is the only source of skill and competency ratings. If you also configure forms for providing
ratings, the latest rating is synced to Growth Portfolio and then shown in the Career Worksheet.
• Behaviors aren't supported. If there are behaviors mapped to job roles, we recommend you hide behaviors
by adding the following element to the Career Worksheet template: <behaviors hide="true" hide-
ratings="true" use-in-readiness="false"/>.
• The permission control for viewing certain job roles and competencies isn't supported.
• Tags instead of competencies are used in the Manage Suggested Roles tool. Tags are created in the Manage
Talent Intelligence Hub tool and used for labeling different attributes.
Related Information
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 HCM 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 each 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
Get an overview of potential problems and errors in your configuration that you can try to solve yourself before you
contact Technical 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 you upgrade to a new release to see whether issues have
been found by new checks.
In addition to these runs performed by the system, you can also run individual checks after you make 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.
2. Depending on the check type of the check you're interested in, select the corresponding tab.
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 Technical 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.
Related Information
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 Technical 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 checks so that you can resolve the issues 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, select 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 Technical Support Tickets from the Check Tool [page 242]
When the check tool reports a serious issue that you can't solve, you might need to contact Technical 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 Technical 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 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.
After a short time, the system runs the check again to verify that the fix has run correctly.
15.7 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
Restriction
• Payroll Information
• Position Management
• Time Off
• Time Sheet
Procedure
The Check Tool page opens with a list of all applications for which you can use the check tool..
2. 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.
3. Choose the Export Configuration link in the information message.
The system downloads a file with the configuration information for the application you’ve selected.
Next Steps
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.
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.
Learn about changes to the documentation for Career Development Planning in recent releases.
2H 2024
October 4, 2024
New You can now configure the Career Work- Enabling More Roles to Launch Role
sheet template to allow more roles such Readiness Forms [page 201]
as manager and HR to launch role readi-
ness forms for an employee’s target role.
New In the latest Career Worksheet, employ- AI-Assisted Career Insights [page 217]
ees can gain insights into development ac-
tions they can take towards their target Enabling AI-Assisted Career Insights
role using generative AI capabilities. [page 218]
New In the latest Career Worksheet, users can Overview of Latest Career Worksheet
now view the following information about
[page 213]
roles: job family, current employees, and
organizational career paths. Therefore, we Feature Comparisons Between Legacy
removed these from the unsupported fea- and Latest Career Worksheet [page 216]
ture list in the feature comparisons topic.
New In the latest Career Worksheet, users can Recommended Roles in Latest Career
now explore recommended roles in both Worksheet [page 213]
card and chart views, and delve into a
role's details by choosing the role card.
Added We added more information about feature Configuring Links to Preferred Next
differences in showing target roles in lat- Move in People Profile [page 211]
est People Profile.
Changed We added the following features that are Supported and Unsupported Features
currently supported in the latest version: [page 125]
Changed We removed the information about classic Reporting on Development Goals [page
reports. 119]
Changed We updated prerequisites for using Career Career Explorer [page 225]
Explorer.
1H 2024
Added We added information about role-based Using Skills in Career Worksheet [page
permissions required for using Career 234]
Worksheet after you've migrated to Talent
Intelligence Hub.
Added We added a topic about career path im- Career Path Import [page 222]
port.
Added We added information about leaving the Importing Custom Learning Activities
LEARNING_dev_goals column blank when [page 172]
importing a custom learning activity.
Added We added information about table report Reporting on Development Goals [page
domains available for reporting on devel- 119]
opment goals and learning activities.
New Users can now use the following fea- Supported and Unsupported Features
tures in the latest version of Development [page 125]
Goals:
Supported Elements and Attributes
• Link custom learning activities to de- Comparison: Legacy and Latest [page
velopment goals 35]
• Create legacy learning activities
• Coaching Advisor
• Generate goals using Generative AI
(AI-assisted goals)
• AI-assisted writing
• Display goal weight on goal cards and
goal plan header
• Display goal weight at the category
level
New With proper role-based permissions, you Enabling Career Explorer [page 228]
can now view an employee's recom-
mended job roles and career paths in Ca-
reer Explorer.
New Talent administrators (TA) or similar roles Roles in Goal Plans [page 79]
in your organization can now manage an
employee's development goals directly in
the employee's development goal plan.
New You can now check the trained model Enabling Career Explorer [page 228]
metrics of role recommendations in Ca-
reer Explorer.
New You can now enable the latest Career Overview of Latest Career Worksheet
Worksheet in Upgrade Center so that your
[page 213]
users can try out the new experience for
using Career Worksheet. Enabling Latest Career Worksheet [page
215]
New You can now enable AI-assisted features Enabling AI-Assisted Goal Creation [page
for end users.
150]
Added We added the following information about Configuring Links to Preferred Next
showing target roles in People Profile: Move in People Profile [page 211]
Added We added information about how to filter Using Skills in Career Development Plan-
skills and competencies by tag in the at- ning [page 233]
tribute picker in Talent Intelligence Hub.
Changed We changed the reason why the roles in Career Explorer [page 225]
the second layer and onward are recom-
mended to be more specific.
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.