Configuring Standard and Ratable Sections

The Reviewer Information section is unique to a 360 Reviews form. In this section of code, the information shown about each rater is determined. This section is created and modified using <fm-element>. Each individual element defines a piece of information about the person who is rating the subject, such as first name, last name, job code, division, and so on. You can configure this section similarly to the Employee Information section in a performance form. Use the XML example in the figure that appears below as a guide.

123456789101112131415161718192021222324252627
<fm-sect index="2" mgt-only="false" split-cmt="false" cmt-opt="1">
 <fm-sect-name><![CDATA[Reviewer Info]]></fm-sect-name>
  <fm-sect-config>
    <rating-label><![CDATA[Rating]]></rating-label>
    <rating-label-others><![CDATA[Rating]]></rating-label-others>
    <default-rating><![CDATA[unrated]]></default-rating>
    <hidden-strength-threshold>0.0</hidden-strength-threshold>
    <blind-spot-threshold>0.0</blind-spot-threshold>
    <num-decimal-places>2</num-decimal-places>
    <publish-button-label><![CDATA[Publish Content]]></publish-button-label>
  </fm-sect-config>
  <fm-element index="0" type="3">
    <ekey><![CDATA[LASTNAME]]></ekey>
    <ename><![CDATA[Last Name]]></ename>
    <evalue><![CDATA[]]></evalue>
  </fm-element>
  <fm-element index="1" type="3">
    <ekey><![CDATA[FIRSTNAME]]></ekey>
    <ename><![CDATA[First Name]]></ename>
    <evalue><![CDATA[]]></evalue>
  </fm-element>
  <fm-element index="2" type="3">
    <ekey><![CDATA[TITLE]]></ekey>
    <ename><![CDATA[Title]]></ename>
    <evalue><![CDATA[]]></evalue>
  </fm-element>
</fm-sect>

The configuration process for the Attribute (Competency / Skill) and Goals sections on a 360 Reviews template is similar to that for Performance Management. However, 360 Reviews require some extra configuration. As in the performance form, the content in each Attribute and Goals section is configurable. This means that the manager or process owner of the form can manually add or remove competencies, skills and goals. Additionally, you can configure the review to allow the participant to remove items from the form.

In the <competency-sect> and <objective-sect>, the ability to add and remove Goals. Competencies and/or Skills is determined by the attribute configurable: If configurable="true", users are able to add goals, competencies or skills. If configurable="false", adding and removing goals, competencies or skills is not allowed.

Permissions can be added to restrict who sees the Add and Remove buttons, and in which route steps. To add these permissions, the appropriate code is added to the action permissions portion of the XML, as seen in the code below:

1234567891011121314
</fm-sect-config>
<action-permission type="none">
   <role-name>*</role-name>
   <action refid="add-item"/>
   <action refid="remove-item"/>
   <route-step stepid="*"/>
</action-permission>
<action-permission type="enabled">
   <role-name>EM</role-name>
   <action refid="add-item"/>
   <action refid="remove-item"/>
   <route-step stepid="*"/>
</action-permission>
<sect-weight>100.00</sect-weight>

Nonremovable for Raters

When a goal or competency section is configurable="true", a Nonremovable for Raters checkbox is available during the Modify stage to decide which items (goals, competencies or skills) could be removable by participants, if we determine these are not critical to rate on a 360 Evaluation. These can be determined by any of the roles involved in the Modify stage (before Evaluation starts).

If this is not intended, and the Nonremovable for Raters option should be hidden, you can enable Hide the Nonremovable checkbox on a form in the Modify stage from Form Template Settings.

Hidden Strengths and Blind Spots point out the differences in ratings between self-evaluation and third-party evaluations. So, as an example, if we set a threshold of 0.5, any differences of 0.5 and beyond, between self ratings and other's ratings will be identified as a Hidden Strength (when self rating is lower compared to other's ratings) or a Blind Spot (when self rating is higher compared to other's ratings), and these differences in ratings will display in the 360 Detailed Report.

In order for the Hidden Strength and Blind Spot reports to work properly, the corresponding thresholds must be configured in the XML for the ratable sections. You perform this configuration in the <fm-sect-config> element of the section. Use the XML example in the figure that appears below as a guide.