SAP Knowledge Base Article - Public

2072029 - Cascader-role functionality - Goal Management

Symptom

  • This article explains how the Cascader Role works, and how to configure it in the Goal Plan;
  • This option gives you control over which read-only details remain read-only when the goal gets cascaded;
  • It also lets you create action permissions for tables (create-row, delete-row, and move-row).

Environment

SAP SuccessFactors Goal Management

Resolution

There is a role that can be used for permissions specific to cascaded goals. In addition to the normal roles E, EM, EMM, EH etc there is a role called "cascader".

You have the option to specify which goal details can become editable upon cascading when an employee cascading (cascader role) cascades a goal to others.

This option gives you control over which read-only details remain read-only when the goal gets cascaded. It also lets you set action permissions for tables (create-row, delete-row, and move-row).

  1. Cascader-role supports permissions on the following goal elements and actions for the user cascading their goal to other employees:
    1. Field permissions (standard, custom, table) 
    2. Table column permissions Action permissions for tables
      1. Create (create-row)
      2. Delete (delete-row)
      3. Move (move-row)
  2. When the "cascader-role" is disabled, users cascading their goal have write access to all fields and actions for that goal regardless of goal plan permissions.
  3. When the "cascader-role" is enabled, the "cascader" role controls what field can be seen and edited and what table actions are permitted for the user who is cascading their goal.
  4. Current behavior is that the user cascading a goal has write access to all fields and actions for that goal regardless of goal plan permissions. By default, the value of this attribute "enable-cascader-role" is false; this is an 'opt-in' feature.

To enable the Cascader Role functionality first enable cascader-role in the goal template, then, configure the goal template field and action permissions in the goal plan xml via Provisioning:

<switches>
<switch for="cascader-role" value="on" />
</switches>

Permission Example:

<field-permission type="write">
   <description><![CDATA[The goal owner, manager and cascader may write to all fields]]></description>
   <role-name><![CDATA[E]]></role-name>
   <role-name><![CDATA[EM]]></role-name>
   <role-name><![CDATA[cascader]]></role-name>
   <field refid="name"/>
   <field refid="desc"/>
   <field refid="metric"/>
   <field refid="start"/>
   <field refid="due"/>
   <field refid="state"/>
</field-permission>

NOTE: As a customer, you do not have access to Provisioning. To complete tasks in Provisioning, contact your Implementation Partner. For our list of supported configuration changes, please refer to this article 2250190 - SCR Form: XML Software Change Request for Goal Plans and what is an Implementation Request in Goal Management.

To Partners, please refer to the section "Cascader Role" of the Goal Management Implementation Guide. For Configuration or Implementation assistance, please direct your questions to Partner Delivery Community.

Related Error: User gets pop up error "Selected goal is no longer available" or "An error occurred" when trying to cascade a goal or objective? This can occur if the switch cascader-role is set to "on" but no specific goal permissions have been set in the goal plan.

Keywords

Cascader role, goal, objective, gm, permission, cascade, push-down, regular, fields, error, cascade goal error, cascade goal an error occurred , KBA , LOD-SF-GM-TMP , Template Management , LOD-SF-GM , Goal Management , How To

Product

SAP SuccessFactors Performance & Goals all versions