Who is this article for?

Users who want to know more about the 12.0 Recommendation methodology.

No elevated permissions are required.

The article highlights recent enhancements to the methodology suite, offering improved control over field placement, availability, and editability among users. Interface updates enhance visibility of applied settings, while providing comprehensive control over individual metadata fields akin to standard fields. See below for more information.

1. Overview
2. User guide
   1. Metadata fields
   2. Changing permissions
   3. New metadata element for the Entity Universe
   4. Overall configuration settings
3. Further reading

1. Overview

Several enhancements have been made to the existing methodology suite, allowing for greater fine tuning of field location, availability and editability across the user base.
Important interface changes allow better visibility of applied settings, while individual metadata fields can be organised and controlled to the same degree as standard fields.

2. User guide

1. In Tools, Methodologies then Recommendation View Configuration, the main layout remains the same as in prior versions.

2. Additional colour coding now helps users quickly understand which settings apply to each field.
3. Metadata components are standalone fields that can be moved to any section using drag and drop.

2.1 Metadata fields

1. Individual metadata fields can now be designated as mandatory for completion:

2. Under Selected item details, all User lists including metadata feature additional options to control the availability and editability of the Recommendation.

3. Enabling Represents assigned user in availability grid, ensures that if the availability grid has been configured with User Assigned in the matrix, this availability assignment is linked to that specific user list.

2.2 Changing permissions

1. Use Represents assigned user in change permissions for metadata like User List, Role, and Team.
2. Create up to four user groups with this feature.
3. Each group can control field editability in the recommendation.
4. Assign the metadata element Contact name (metadata element: User List) to Group 1 in your setup.

5. Following this, the Change permissions for the Description are associated with Metadata element Group 1, ensuring that only users assigned to the Contact name can edit the Description.

6. Navigate to Tools, then Configuration, followed by Auditor Teams.
7. Configure the main settings for Auditor Teams.
8. Proceed to Tools, then Configuration, and Users, Roles & Permissions.
9. Set up the primary roles for Users, Roles & Permissions.
10. Ensure that the same functionality applies to standard User fields like Created By, Instigator, Owner, Assigned To, Issue Manager, and all Associated People.

11. To establish the default change permissions using the new functionality, which defines a setting to control all fields collectively instead of individually, make sure you haven't selected a template element.

2.3 New metadata element for the Entity Universe

1. Navigate to the article on the Entity Universe. This new metadata element offers special features.
2. It can be associated with the default Recommendation Tracking search criteria for Linked Entities.
3. When choosing this specific metadata element type, you'll have the option to designate Metadata element represents entity links to the recommendation.

4. With this option enabled, searching for Recommendations by the Linked Entities will display results based on the entity origin and the entity information from the metadata field:

2.4 Overall configuration settings

1. When considering the overall view configuration settings for different types of users, i.e. those that will be using the client application or the online portal, additional options have been introduced to afford Audit and Risk teams additional segregation.
2. Within Template designs, select Add template:

3. Open the User type drop-down list:

4. New options are available for Audit only users and Risk only users, previously grouped as Enterprise users.

Note: Origin and Recommendation Type don't affect these options.

5. After making your selection, click OK and proceed to set up a new template view.
6. This update allows Risk Only users to be considered Auditees for audits.
7. For instance, in a custom Audit File layout, you can assign Risk Only users as Auditees.
8. You may need to create a separate Recommendation View template for Risk Only users.
9. Risk Only users accessing an Audit Recommendation won't have the same options as Audit users.
10. The rest of the Recommendation View Configuration remains unchanged, including system permissions for accessing this component.

3. Further reading

• 12.0 Key Dates methodology release notes
• 12.0 Recommendation Tracking layout release notes
• 12.0 Questionnaire interface release notes