You must be an Admin to set or change this setting.

Review Groups and Multi-Stage Review

Add Operator Roles and/or Users that will be required to sign off / review procedures before being released, based on the selected Review Group.

Add review groups to account for multiple groups and/or stages of required reviewers to adjust for different review requirements, such as major and minor version updates.

Navigate to Settings and click into the Release section.

Click + Add Review Group to add a new Review Group or click Edit next to an existing Review Group to make changes.

For each review stage, specify if approvals should be cleared when changes are made to the draft version.
NOTE: By default, approvals will be cleared if edits are made to the draft after the approvals were made. This setting can be disabled on a per Release Stage basis, which would allow changes to be made without clearing previous approvals. Approvals will only be cleared in the currently active stage.
Reviewers can be added using our standard "AND" and "OR" logic.
When editing a Review Groups, add additional stages using the + Add Review Stage button. Hover over the review stage and click the x in the top right hand corner to delete the stage.

Expand for more "AND" and "OR" Logic details

Each new block represents a signature. Signatures for review can be gathered by Operator role (anyone with that operator role assigned can signoff) or User (a user's email will be used and that specific person must signoff).

Operator roles and user emails are both represented in the same drop down menu.

In this example, the procedure will need to be signed off by someone with the MD role AND someone with either the AVI role OR the ACO role.

Click the x next to the role or user to remove them as a reviewer. Hover over the reviewer box and click the x in the corner to remove the review block.

Click SAVE to lock in reviewer selections that will apply to all new reviews where that Review Type is selected.

Updates or changes made to Review Groups will only affect new reviews.

When a procedure draft it put into review, the editor will need to select a Review Group.

The operator roles associated with the selected Review Group will automatically populate as required reviewers. Additional reviewers can be added, if desired.

Reviewers that are configured as part of the Review Group are not able to be removed from this procedure, even if you are an admin.

Use the + signs to add additional reviewers before selecting Move to Review.

Caution: Setting specific users as required reviewers will mean that user MUST be available to sign off on all releases.

Utilizing the OR function for specific users will allow for alternate options.

Release Flow

Release Flows can differentiate major and minor releases and auto increment the major or minor schema when using Auto Version Numbering. (See article)

Release Flows can also be used to calculate the risk of procedure changes through a risk assessment, which can be used to automatically choose the appropriate review groups based.

Major / Minor Uprevision

Review Groups need to be created before they can be used in a Release Flow.
(see Review Groups)

Create a Release Flow to work in conjunction with your auto version numbering to update your major and minor schema.

Navigate to Settings > Release and Click +Add Release Flow.

Set which review group should be used for a major release and the minor release.

Major and Minor release is selected by the user when moving to review. Users can adjust the version field during this stage through the review modal screen, helping tailor updates as procedures transition towards release.

Define which Review Process should be used for each procedure within the Procedure Settings.

Note: Release Process encompasses both standard Review Groups as well as Release Flows.

The procedure editor will select Major Version Update or Minor Version Update when putting the procedure into review.

For Example:

With this Auto Version Number Schema:

Version 1 of a procedure will increment to Version 1.1 with a Minor Version Update.

Version 1 of a procedure will increment to Version 2 with a Major Version Update.

A few things to remember about auto version numbering:

The version number is not updated until moving to review.
ONLY procedures who's numbering scheme match the auto version numbering schema will update automatically.
Changing the schema will require all existing procedures to be manually updated to match the new schema for auto version numbering to continue. With auto version numbering enabled, users must rely on the system's automated controls for version updates, which may reduce manual flexibility during edits.

Diagnostic / Risk Assessment Release

Take the guesswork out of determining if your release should be a major or minor release by applying logic criteria to your Release Flow.

Before we can build out a diagnostic Release Flow, there are a couple of things that need to be configured first:

Create a global List and enable numerical values for expressions

Navigate to Settings > Procedures and locate the Custom Lists. Click the +Add List button.

Check the box to Enable Numerical values for expressions.

Create a list and assign a numerical value for the associated risk level.

The risk factors can be anything you want to use to determine if the review should be a Major Release or a Minor Release.

Create a diagnostic procedure with a run result

Once the diagnostic list is created it has to be added to a diagnostic procedure.

A diagnostic procedure is a procedure that has a "Run Result" field added which can be used in the Release Flow logic.

Create a new procedure and add any Field Input Lists needed for the assessment. Remember to only choose lists with numerical values assigned.

Click the blue + next to Unique ID at the top of the procedure and select Add Run Result.

Here you will add a formula to calculate the run result. In our example here, we are just going to add up our field input list values, but other expressions are supported.

Click the blue plus to the right of the Run Result field to reference one of the field inputs.

Review and release this diagnostic procedure.

Create a Release Flow with logic

Navigate back to Settings > Release and add a new release flow.

No need to set the major and minor review groups as we will need to add logic first. Click the +Use Logic button.

Select the diagnostic procedure from the drop down.

Logic rules use the run result field from the selected procedure. You can add logic rules to both the major and minor release selections.

In the above example, if Major release is selected and the run result is greater than or equal to 40, the Safety review group will be assigned.

If Major release is selected and the run result is less than 40, the Major review group will be assigned.

In both cases, the "Major" number in the auto numbering schema will be incremented.

If Minor release is selected, the Minor review group can only be used is the run result is less than 10. Otherwise, the user will be forced to select the Major release option.

Apply Release Flow to a Procedure

Add the Release Flow to a procedure in the procedure settings.

Put the procedure into review.

There will still be a prompt to select Major or Minor review.

In either case, when the procedure is moved into review, review approvals can not be assigned until the diagnostic procedure is run.

Click the link to run the diagnostic procedure.

Make list selections and the run result will be calculated automatically.

Sign off on the step and mark the run as ended.

If the criteria matched the release rules the Diagnostic will pass and the Review Group will be populated.

Back to our example:

Minor release was selected and the run result was 7, so Minor release passed and the Minor Review Group was applied. ✅

If Minor is selected but the run result is greater than 10, the diagnostic procedure will fail because there is no review group match. We will need to go back to edit and push to a major review.