Peer Review Actions
Last updated
Last updated
Peer Review Actions are a great way for different members of a team to crosscheck each other's work for key actions within a case, letting you embed quality checks into your processes without having to add in feedback flows.
Enate supports this with a 'Manual with Peer Review' Action type that you can add to your Case flows. These are like 'Manual' Action types, except that once the initial manual activity is carried out by a user, Enate will route the Action to be picked up by a different user to check the work, passing or failing it. If failed, it will route back to the original user to resolve the issues.
Watch this video to find out more about how to set up a Peer Review Action:
Click here for more information and examples about when and why you would user Peer Review Actions.
For detailed information on how Peer Review Actions work at runtime, see the dedicated Work Manager section.
You can either create a Peer Review Action type in the Service Line section of Builder, or directly from your Case flow.
Creating a Peer Review Action type from the Service Lines page adds the Action type to your menu of available Actions when you're building flows subsequently in Cases.
To do this, in the Service Line page, select which service line you would like to add the peer review Action to and then click on the plus symbol next to the 'Process Search' box. This will bring up a drop down menu where you can select an Action.
This will open up a new Action for you to create.
Add a name and description to your Action and then in the type drop down select 'Manual Action with Peer Review'.
You can then choose to add a global checklist to the Action. This contains a standard checklist of activities that will be added any time this Action type is added to a Case flow. See here for more information on checklists.
You can also choose to add a Peer Reviewer global checklist to the Action. This contains a standard checklist of activities for the peer reviewer to complete that will be added any time this Action type is added to a Case flow. See here for more information on peer review checklists.
Once you are happy with your Action, hit save to create it. This Action can now be added to new and existing business processes by selecting it from the dropdown list when adding a new Action to a Case.
Alternatively you can add an Peer Review Action type directly from the Case flow itself.
To do this, open a Case flow in edit mode, click on an Action's menu and then instead of clicking to add an existing Action, select to create a new Action by clicking the '+' icon.
Give the Action a name, add a description if you wish and for its type, select 'Manual with Peer Review Action'.
This will add the Peer Review Action to the Case flow.
You now need to configure the settings for the new Action you have added to your Case. Click on the Action in the flow to highlight it in the info section.
In the Action Info tab, you need to add the usual following information for an Action:
Setting | Description | Notes |
When is it due? | This is for the initial 'completion' stage of the Action. Select a value from the dropdown menu of Due Date ‘flavours’ | Mandatory to set live. (See Due Date Flavours Settings for more information). |
Who does it go to? | This is for the initial 'completion' stage of the Action. Select a value from the dropdown menu of Allocation ‘flavours’ | Mandatory to set live. (See Allocation Flavours Settings for more information). Note that the system will not allow the user who carried out the manual activity to also carry out the peer review. |
General Settings | Select a value from the dropdown menu of Follow Up ‘flavours’ | Mandatory to set live. (See General Settings Flavours Settings for more information). |
Main Card | You can select a Custom Card to display on the main section of the Action screen. | Optional. See here for more information about Custom Cards. |
Side Card | You can select a Custom Card to display on the side panel of the Action screen. | Optional. See here for more information about Custom Cards. |
Manual Creation | Switching this setting on allows the Action to be started manually in Work Manager. | Optional. See Adding Ad-hoc Actions section for more information. |
Checklist | Here you can add local checks to the Action that help support 'custom' activities that take place for that specific Action. You can also edit the global checks for the Action type from here too, if it has any. | Optional. See here for more information about adding checklists. |
Additionally, once a Peer Review Action has been added to your Case flow, a new 'Peer Review' tab will display in the info grid.
Here you need to add the following settings that are only relevant for the Action once it is in its 'Peer Review' stage.
Setting | Description | Notes |
When is it due? | This is for the peer review stage of the Action. Select a value from the dropdown menu of Due Date ‘flavours’ | Mandatory to set live. (See Due Date Flavours Settings for more information). |
Who does it go to? | This is for the peer review stage of the Action. Select a value from the dropdown menu of Allocation ‘flavours’ | Mandatory to set live. (See Allocation Flavours Settings for more information). Note that the system will not allow the user who carried out the manual activity to also carry out the peer review. |
Peer Review Checklist | Here you can add local checks for the peer reviewer to complete and edit the global peer review checks for the Action type, if it has any. | Optional. See here for more information. |
You can set up Peer Review Actions to display a dedicated checklist for the peer review section of the Action. These checks must be carried out and confirmed by the peer reviewer before the Action can be marked as resolved, allowing you to enforce procedure in how Peer Review Actions should be completed by agents at runtime.
In Work Manager, users will then have to confirm for each item in the checklist whether they have completed it (the options are Yes, No, N/A) and they can even add a note for each check.
You can create two different levels of peer review checklists:
'Global' checklists - these are added to the Action type and contain a standard checklist of activities must be carried out and confirmed by the peer reviewer before the Action can be marked as resolved. Global checks will be added any time this Action type is added to a Case flow. Global peer review checks can be added/edited at Service Line level or from the Peer Review Checklist setting in the Case screen.
'Local' checklists - these help support 'custom' activities that take place for that specific Action that must be carried out and confirmed by the peer reviewer before the Action can be marked as resolved. Local checks will only apply to the specific Action they have been added to. Local peer review checks are added to the Peer Review Action itself from the Peer Review Checklist setting in the Case screen.
Once important feature to note is that once you've created a local checklist item, you can drag it up to LINK it to a global check, specifying whether it should run before or after a standard global check. You'll see the colour-coding denoting which global check it's linked to. If ever the order of global checks is adjusted, all the linked 'local' checks will move with it. Once you're happy with your overall checklist you can OK this and the checklist for this Action is saved.
At runtime, users reviewing the Action in Work Manager will just see a single list of the checks they must complete, with no differentiation between global and local checks. They'll have to complete all of the checks in order to mark their Action as resolved.
You can also choose to automatically bypass a peer review by adding a condition to a Peer Review Action in your Case configuration. If that condition is met, the peer review part of the Action will no longer be required. This gives you more flexibility when using Peer Review Actions and allows you to avoid any unnecessary peer reviews.
To set a condition for a peer review, in your Case flow screen select the relevant Peer Review Action and, on the Peer Review tab, click the 'Bypass if' icon.
In the resulting popup, set your condition - choosing a data field (which can be standard or one of your own custom data items), then a condition and a value.
Selecting the 'Advanced' option lets you create a more complex condition with a combination of multiple criteria, adding a plus symbol between each part. You can check the validity of your expression via the external DotNetfiddle link. Once you're happy with your settings here, apply the condition.
The 'Bypass if' icon will the be highlighted, showing that a condition has been added.
Save the update to your Case and set the new version live.
Over in Work Manager, if the condition you have added is met, at runtime the activity will move straight from the manual activity onto the next Action, bypassing the peer review stage. A note will subsequently be displayed in the Actions list on the Case screen, showing that the peer review activity was not required.
