Configuring Standard and Ratable Sections

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Configure other sections in a 360 Reviews form template

Configuration of the Reviewer Information Section

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, Reviewer Information section as a guide.

Reviewer Information Section

Code snippet
<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>Expand

Remember to consult the Order of Elements so that the information is placed in the correct area of the XML.

Configuration of the Competency and Objective (Goal) Sections

The configuration process for the Competency 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 Competency and Goals section is configurable. This means that the manager or process owner of the form can manually add or remove competencies 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>, adding and deleting items is determined by two different attributes:

  • Configurable: If configurable="true", users are able to add goals or competencies. If configurable="false", adding items is not allowed.

  • Removable: If removable="true", users are able to remove or delete goals or competencies. If removable="false", removing items is not allowed.

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 or competencies) could be removable by participants, if we determine these are not critical to rate on a 360 Evaluation.

Every role that accesses the 360 form on the Modify stage, before sending it to Evaluation, can flag competencies and/or goals as nonremovable. Ultimately the Process Owner can review the rater list and those non-removable items flagged, and make the appropriate changes accordingly, before starting the 360 Evaluation. However, if you don't intend to display at all the Nonremovable for Raters checkbox in the 360 form, an option available in Form Template Settings called Hide the Nonremovable checkbox on a form in the Modify stage can be enabled to hide this option entirely.

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 in the code that follows:

Permission Add Remove Buttons

Code snippet
</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>Expand

An example of a Competency section from a user perspective can be seen on this example. A Core Competencies section, where a manager can add/remove competencies (as given on the permissions from XML).

Configuration of Hidden Strength and Blind Spot Thresholds

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, Hidden Strengths and Blind Spots Thresholds, as a guide.

Log in to track your progress & complete quizzes