Symptom
This KB article explains Goal Plan States, and how to configure and use the states.
- Additionally, you can vote and comment in the Customer Influence ideas that were addressed on this topic, asking our Product Management Team to offer these configurations in a future release as self-service in the Admin Center, as opposed to XML manipulation. Your votes help us to prioritize ideas that we will consider for upcoming product releases. For Goal Management please refer to the Improvement Request 211002.
Environment
SAP SuccessFactors Goal Management
Resolution
What is a Goal Plan "State"?
- A common request from customers is the capability to lock and unlock goal plans for Goal Approval purposes. The idea behind TGM-461 is to allow components of the Goal to be locked once an authorized user locks the plan (E, EM, EH, etc.).
- While it can be used in Development templates, it is not currently possible to report on this in Ad Hoc reports (CDP-11762) - but will be reportable in Ad Hoc Development domain after the b1908 release.
- It is not supported for learning activity templates (CDP-2804)
Group Goals and Team Goals
- Please be aware Group Goals and Team Goals cannot be locked down with goal plan state – this only applies to personal user goals (CCD-364, TGM-5409, TGM-6583)
- If you'd like to see this functionality added to the product, please see the following idea in the Customer Influence portal that you may vote on and follow for progress updates: https://influence.sap.com/sap/ino/#/idea/201296/
Value to customers
With this functionality, a manager could cascade a goal to an employee and the employee could updated only certain fields while the goal is Locked and update all fields/delete goals when it is in an unlocked state.
Configuration
Note: To complete tasks in Provisioning, contact your Implementation Partner. If you don't have a Partner, you can find for SAP Certified Partners via the SAP Partner Finder or, alternatively, speak with your Account Executive or Customer Engagement Executive about Professional Services options.
Partners, refer to the PM v12A Implementation Guide. For Configuration or Implementation assistance, please direct your questions to the Partner Delivery Community.
In the Goal Plan XML template, add the below configuration, after defining <field-definition> elements.
- Start with <obj-plan-states> element, this provides the ability to have different objective plan states.
</ obj-plan-state>
</ obj-plan-states>
- <obj-plan-states> element can have multiple <obj-plan-state> element.
obj-plan-state: element is used to define the single goal plan state.
- Id: attribute specifies the internal name of the plan state.
- default: attribute specifics the default state of the objective plan and it should be true for only one plan state.
- state-label: element defines the name of the current state.
- lang: attribute is used for showing the name as per the locale.
<obj-plan-states>
<obj-plan-state id="A" default="true">
<state-label lang="en_GB">State-A</state-label>
<state-label lang="en_US">State-A</state-label>
…
</ obj-plan-state>
</ obj-plan-states>
- Each <obj-plan-state> element can have its own set of action and field permissions.
- Configure a new action permission called "Locked" that provides the ability to lock down certain areas of the goal plan or a goal.
- The target-state element specified inside "change-state" permission defines the objective plan state to which the goal plan can be switched (i.e. Locked state and Unlocked state).
<obj-plan-states>
<obj-plan-state id="A" default="true">
<state-label lang="en_GB">State-A</state-label>
<state-label lang="en_US">State-A</state-label>
<permission for="change-state">
<description><![CDATA[Manger may change the goal plan state to C.]]></description>
<target-state><![CDATA[B]]></target-state>
<role-name><![CDATA[EM]]></role-name>
</permission>
<permission for="private-access">
<description><![CDATA[Employees and their managers up the reporting chain may view unshared/private goals.]]></description>
<role-name><![CDATA[E]]></role-name
<role-name><![CDATA[EM]]></role-name>
</permission>
<permission for="delete-group-goal">
<description><![CDATA[Only the employee may delete goals in his/her own plan.]]></description>
<role-name><![CDATA[EM]]></role-name>
</permission>
…
</permission>
</ obj-plan-state>
</ obj-plan-states>
- Repeat the steps, if you need to configure the multiple objective plan states under </ obj-plan-states> element.
- Any role that has the change-state permission on the plan may change the goal state.
- It can also be controlled by the PM form, based on certain route steps.
Change Locked / Unlocked State on Form Routing
You can change the goal plan state of the user when a form is routed to the next step.
For PM template, it can be configured via Manage Templates. Select the Goal section and click on Show advanced options. Then click on Configuration(s) defined for Goal Plan State.
For 360 template, below xml must be configured in the Goal section.
Note: Add the below configuration after the < meta-grp-label > element in the Objective section of the form:
- obj-plan-state-change: This element is used to define the single goal plan state.
- to-step: attribute specifies the route step id.
- target-state: specifies the state to which the goal plan has to be switched.
- id: attribute specifies the internal name of the objective plan state. It should be from one of the objective plan state id defined in the objective template.
<obj-plan-state-change to-step="Step2">
<target-state id="B"></target-state>
</obj-plan-state-change>
< obj-plan-state-change>
Note: To change the goal plan state for each route step, add the above configuration multiple times.
<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>
Note: If Goal Plan State should only be controlled via the route map and not within the goal plan itself, leave the role empty for permission change-state within the goal plan xml.
<permission for="change-state">
<description><![CDATA[Manager may change the goal plan state to B.]]></description>
<target-state><![CDATA[B]]></target-state>
<role-name><![CDATA[]]></role-name>
</permission>
Note: Creating a new form does not trigger a change of the goal plan state, and does not put the goal plan back into initial state.
See Also
KB article 2250190 - SCR Form: XML Software Change Request for Goal Plans
Keywords
sf, successfactors, success factors, PMGM, GM, objective, locked, unlocked, target, form, route map, state, status, goal, locked, unlocked, obj-plan-state , KBA , LOD-SF-GM-TMP , Template Management , How To