SAP Knowledge Base Article - Public

2072109 - Goal Management - Goal Plan State - How to Configure and Use

Symptom

This article explains Goal Plan States, and how to configure and use the states.

Environment

SuccesFactors Goal Management

Resolution

What is a Goal Plan 'State"?

  • The state of the goal plan indicates if a goal plan is Locked or Unlocked.
  • 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.).
  • Is as well supported for CDP (CDP-2651)
  • It is not supported for learning activity templates (CDP-2804)
  • Please be aware that Group Goals and Team goals cannot be locked down with goal plan state – this only applies to personal goals (CCD-364, TGM-5409, TGM-6583)

 

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.

How is it configured:


In the Goal Plan XML template, add the below configuration, after defining <field-definition> elements.

  • Step 1) Start with <obj-plan-states> element, this provides the ability to have different objective plan states.
    <obj-plan-states>
    …..
    </obj-plan-states>
  • Step 2) <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>
\

  • Step 3) Each <obj-plan-state> element can have its own set of action and field permissions.
  • We need to 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

  • We need to provide the ability so that when a form is routed to next step, then the goal plan state of the user can be changed.
  • For this, we need to have the below configuration in the objective section of the PM/360 form template.
  • 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: If we want to change the goal plan state for each route step, then 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 you want goal plan state only be controlled via the route map and not within the goal plan itself, leave 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.

Keywords

Goal Plan State, objective, goal management, gm, configure, state, locked, unlocked, target, pm, form, route map,   , KBA , LOD-SF-GM-TMP , GM Template Management , How To

Product

SAP SuccessFactors HCM Core all versions