|
|
| (18 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | ==Overview==
| + | {{Annotation Mode}} |
| − | Annotations is a feature that allows users to add or view annotations at the individual field level (ex: [[Standard Fields]] such as name or address, and also [[Custom Fields]]). These edits to specific fields can be made while keeping the rest of the record locked.
| |
| − | | |
| − | Flexible [[Role Based Security|role-based security]] allows the [[Global User Administrator|System Administrator]] to configure [[UTA role]]-based permissions: different users will have the ability to view or add annotations to fields, while others the ability to edit that field value.
| |
| − | | |
| − | Our annotations feature offers you, the SmartSimple user, an additional communications vehicle for both [[Internal|internal]] and [[External|external]] [[User|users]]. While annotations are similar to the [wiki/Notes Notes] feature, it is targeted towards individual fields. For example: If one of your grants administrators is reviewing an application, and notices that a particular field needs to be revised by the applicant - the administrator can then highlight this field with an annotation and send a comment to the applicant concerning which edit to make. The applicant can review the comment and make the appropriate change.
| |
| − | | |
| − | ==Configuration - Essentials==
| |
| − | In order to configure Field Revision Annotations for your SmartSimple [[instance]], you must create an '''Annotation Type '''and permission it based on [[User Role|roles]].
| |
| − | | |
| − | Following this, you then have the ability to go into a [[Universal Tracking Application]] and configure [[UTA Role]]-based permissions against individual UTA [[Status|statuses]] to control who can view and edit the annotations, and who is able to modify the fields in annotation mode.
| |
| − | | |
| − | ===Creating an Annotation Type===
| |
| − | The '''Annotation Type '''is necessary to use the Field Revision Annotation feature; it allows users to define role-based permissions to control who can use that specific type of annotation.
| |
| − | | |
| − | 1. Click the 9-square menu icon on the top right of your page.
| |
| − | | |
| − | :: {{Icon-Menu}}
| |
| − | 2. Under the heading '''Configuration, '''select '''Global Settings.'''
| |
| − | | |
| − | 3. In the first tab of Global Settings (labelled '''System'''), select '''Annotation Types. '''
| |
| − | | |
| − | :: [[File:Annotation types.png|500px|border]]
| |
| − | :
| |
| − | :* This will open up the list of available Annotation Types in the system. If you do not have any already configured in your system, the page will be blank.
| |
| − | :* To edit an existing Annotation Type, simply click the '''pencil icon '''on the left of the annotation name.
| |
| − | 4. Click the '''+ '''button on the top left to create a new Annotation Type.
| |
| − | | |
| − | 5. Provide an appropriate name, caption and description for your new Annotation Type.
| |
| − | | |
| − | ::: [[File:New annotation type.png|650px|border]]
| |
| − | ::
| |
| − | ::* The Name and Caption field are normally labelled the same, if not similarly.
| |
| − | ::* The Description field is important to fill out for the configuration and creation of all [[SmartSimple]] features: it is best practice to provide guidance in case anyone else needs to modify or use your configuration
| |
| − | ::* The [[Display Order]] field determines where on the page a user will see your Annotation Type listed. The Display Order works from lowest to highest number - ex: inserting 1 into the field will ensure that your type is listed first, and any type with a display order greater than 1 will be listed afterwards in ascending order. If nothing is inputted the system defaults to a display order beginning at 100 and rising in increments of 100 for subsequent fields.
| |
| − | ::* The Colour field allows you to choose which colour your annotations will appear when they are written with this type.
| |
| − | 6. When you have filled out all the fields to create a new Annotation Type, click '''Save. '''
| |
| − | | |
| − | ===Setting Permissions and Availability===
| |
| − | After completing the steps to creating a new Annotation Type, this will bring you to the '''Edit '''page for that type.
| |
| − | | |
| − | 1. Select the second tab on the Annotation Type editing page, labelled '''Permissions and Availability.'''
| |
| − | | |
| − | :::: [[File:Annotation type permissions.png|650px|border]]
| |
| − | ::
| |
| − | ::* '''View & Create - '''Click into the text box to select which [[User Role|roles]] will have the ability to both view and create this Annotation Type. The default will be '''Everyone. '''If you have a role-specific annotation - for example, a '''Reviewer '''Annotation Type, then you should only select the roles that need access to this type, such as those with the role '''Reviewer '''assigned.
| |
| − | ::* '''View Only -''' Click into the text box to select which roles will have the ability to view this Annotation Type. The default will be '''Everyone. '''A role-specific annotation type, such as those for '''Reviewers, '''might only require specific roles to see but ''not'' create this annotation type, such as '''Employee '''or '''Applicant. '''
| |
| − | 2. After selecting the appropriate roles to access your Annotation Type, click '''Save.'''
| |
| − | | |
| − | ===Setting Statuses for UTA-based Annotation Types===
| |
| − | After building your Annotation Type, go to the UTA that you want this annotation to be available for. For example, a '''Reviewer '''Annotation Type that is written by a reviewer to be seen by an applicant is appropriately associated with a Grants Manager application. In this series of steps, we will select the '''Status '''that will allow the Annotation Type to be used by the roles that have been assigned.
| |
| − | | |
| − | 1. To find your UTA, click the 9-square menu icon on the top right of the page.
| |
| − | | |
| − | :::: {{Icon-Menu}}
| |
| − | 2. Under the heading '''Applications, '''select the desired application to open up its details.
| |
| − | | |
| − | 3. Click the '''gear icon '''on the top of the page to go into '''Configuration Mode. '''
| |
| − | | |
| − | :::: [[File:Config settings.png|200px|border]]
| |
| − | 4. Go to the second tab of the Configuration Settings - this displays the settings associated with the [[Level 1 Entity]] of the application.
| |
| − | | |
| − | <pre> The nomenclature for your application and configuration tabs will differ depending on your SmartSimple instance. </pre>
| |
| − | | |
| − | 5. Select '''Statuses '''under the heading '''General Settings. '''
| |
| − | | |
| − | :::: [[File:Statuses config.png|500px|border]]
| |
| − | A list of statuses associated with the Level 1 Entity of your UTA will appear.
| |
| − | | |
| − | 6. Select the status that you want to add this Annotation Type to.
| |
| − | | |
| − | ::* If the status you would like to add an Annotation Type is not yet created, learn [[Status#Creating UTA Statuses|how to create a status]].
| |
| − | ::*: [[File:Under review status.png|300px|border]]
| |
| − | | |
| − | In this example, the '''Under Review '''status is appropriate for an Annotation Type that pertains to a '''Reviewer. '''
| |
| − | | |
| − | The details of the status will open.
| |
| − | | |
| − | 7. Click the second tab of the Status page, titled '''Permissions & Availability. '''
| |
| − | | |
| − | :::: [[File:Annotation for status.png|600px|border]]
| |
| − | {| class="wikitable"
| |
| − | |-
| |
| − | ||'''Annotation System Role Permission'''
| |
| − | ||
| |
| − | '''View: '''Who is allowed to view the annotations associated with this status
| |
| − | | |
| − | '''View and Create: '''Who is allowed to both view and create annotations on this status
| |
| − | | |
| − | '''Edit Field: '''Who is allowed to edit specific fields that have annotations on them in this status
| |
| − | | |
| − | '''Anonymize Creator: '''Choose which roles you would like to hide the identity of when they create annotations on this status
| |
| − | | |
| − | |-
| |
| − | ||'''Annotation Association Role Permissions'''
| |
| − | ||
| |
| − | '''View: '''Which roles will be ''associated ''to view the annotations with this status
| |
| − | | |
| − | '''View and Create: '''Which associated roles will be able to both view and create annotations on this status
| |
| − | | |
| − | '''Edit Field: '''Which associated roles will be able to edit specific fields that have annotations on them in this status
| |
| − | | |
| − | '''Anonymize Creator: '''Choose which associated roles you would like to hide the identity of when they create annotations on this status
| |
| − | | |
| − | ::* Good examples of associated roles might be users with '''Contractor '''roles, or a '''Grant Writer '''who is working on multiple grants at the same time, etc
| |
| − | | |
| − | |}
| |
| − | 8. Once you are done permissioning the annotation feature on a specific UTA status, click '''Save. '''
| |
| − | | |
| − | ===Enabling Annotation Permissions===
| |
| − | Now you need to enable annotation permissions on the newly created Annotation Type.
| |
| − | | |
| − | 1. Click the 9-square menu icon on the top right of your page.
| |
| − | | |
| − | :::: {{Icon-Menu}}
| |
| − | 2. Under '''Configuration, '''select '''Global Settings.'''
| |
| − | | |
| − | 3. Click '''Annotation Permissions, '''which is available on the first tab.
| |
| − | | |
| − | Two tabs will appear: the first for '''Global Permissions '''and the second for '''Status Specific Permissions. '''Enabling permissions for your Annotation Type can be successfully configured from both tabs. Since you have a status-specific Annotation Type - a '''Reviewer Type '''for the status '''Under Review '''- the Status Specific Permissions tab is applicable.
| |
| − | | |
| − | :::: [[File:Status specific annotation permission.png|400px|border]]
| |
| − | :::
| |
| − | :::* '''Entity Type: '''Select the entity that your status and Annotation Type falls under. In this case, it is a specific UTA and the Level 1 Entity that we configured our Annotation Type for.
| |
| − | :::* '''Status: '''Select the status that your Annotation Type applies to. In this case, it is the '''Under Review '''status.
| |
| − | :::* Set '''System Role '''and '''Association Role '''permissions, as applicable and necessary.
| |
| − | 4. Click '''Save. '''
| |
| − | | |
| − | ===Using Annotation Types===
| |
| − | After an Annotation Type has been created, configured onto a UTA Entity and Status, and role-based permissions were enabled on the status and in Global Settings, you can double-check that your annotation works by going to the UTA you want to use the annotation for.
| |
| − | | |
| − | 1. Click the 9-square menu icon on the top right of your page.
| |
| − | | |
| − | ::::: {{Icon-Menu}}
| |
| − | 2. Under the '''Applications '''heading, select the appropriate application.
| |
| − | | |
| − | 3. Select the Level 1 Entity that has the appropriate status the Annotation Type is configured for.
| |
| − | | |
| − | In this example, it must be one that has '''Status - Under Review. '''
| |
| − | | |
| − | 4. Select the '''Annotations '''feature, which appear on the left-side menu of the Level 1 Entity page.
| |
| − | | |
| − | ::::: [[File:Annotations side bar.png|150px|border]]
| |
| − | 5. A list of annotations will appear. If there are no annotations yet, the page will be blank. To create a new annotation, click the '''pencil icon '''on the right hand side of the page.
| |
| − | | |
| − | ::::: [[File:Annotation mode.png|150px|border]]
| |
| − | When you are in '''Annotation Mode, '''all of the fields can now be clicked into and annotations can be created and viewed based on which roles you have permissioned.
| |
| − | | |
| − | Clicking into a field will open up a window with a '''pencil icon '''that you can click to create a new annotation.
| |
| − | | |
| − | ::::: [[File:New annotation.png|
| |
| − | ::::: [[File:Annotation fill in window.png|850px|border]]
| |
| − | Under '''Annotation Type, '''select the type that you have created to ensure that the correct and appropriate roles will have access to this annotation.
| |
| − | | |
| − | After filling in the content of your annotation, click '''Save. '''Any viewer with a role that is permissioned to Edit Fields will be able to view and edit the field that you have written an annotation for.
| |
| − | | |
| − | === ===
| |
| − | ==Using Field Annotations==
| |
| − | To use Annotation a user must first switch on this functionality against the individual record.
| |
| − | | |
| − | Once Annotation has been switched on the user can add, edit or view the annotations, depending on the Status based permissions.
| |
| − | | |
| − | The user may also be able to edit the actual field value when it is locked, depending on the Status based permissions.
| |
| − | | |
| − | | |
| − | | |
| − | ===Switch on Annotation===
| |
| − | If you have do not have the '''Open Record in Annotation Mode''' permissions but have View or View and Create permission, then when you first access the record you will see a Turn On Annotation button along the top of the screen.
| |
| − | | |
| − | [[Image:TurnOnAnnotation.png|border]]
| |
| − | | |
| − | | |
| − | | |
| − | If you click on this button, or if you have '''Open Record in Annotation Mode''' permissions, then you will automatically access the record with annotation switched on. The Turn Off Annotation button will be displayed along the top of the screen.
| |
| − | | |
| − | [[Image:TurnOffAnnotation.png|border]]
| |
| − | | |
| − | | |
| − | | |
| − | ===Add, Edit or View the Annotation===
| |
| − | If the user has View Annotation or View and Create Annotation permissions, then they would automatically see the Annotations tab along the right hand side of the screen. If they clicked on this then it would expand to show any Annotations created.
| |
| − | | |
| − | The Standard or Custom field that the Annotation exists against appears at the top of the individual Annotation within the overall Annotation tab, while the message, the person who entered the message and the date it was entered also appears.
| |
| − | | |
| − | [[Image:AnnotationTab.png|border]]
| |
| − | | |
| − | | |
| − | Turning on Annotation also exposes a series of Edit, View or Modify options against individual Standard and Custom fields, as well as highlighting those fields with existing annotations.
| |
| − | | |
| − | [[Image:AnnotatedFields.png|800px|border]]
| |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | ====View Annotations====
| |
| − | If the user has View but not View and Create Annotation permissions then they will not be able to access the '''New Annotation''' or '''Reply''' buttons against individual fields.
| |
| − | | |
| − | They would still automatically see the Annotations tab along the right hand side of the screen.
| |
| − | | |
| − | If they clicked on this then it would expand to show any Annotations created.
| |
| − | | |
| − | If the user then clicks on one of the Annotations listed then the Annotation is exposed against the relevant field, but still with no Reply or Modify option.
| |
| − | | |
| − | [[Image:AnnotationViewOnlyScreen.png|border]]
| |
| − | | |
| − | | |
| − | | |
| − | | |
| − | | |
| − | ====Edit Field====
| |
| − | The Edit fields Annotation functionality is only relevant when the record is [[Status Lock|locked on status]] and the user has '''View Annotation Roles''' set.
| |
| − | | |
| − | If the user has Edit Field in Annotation Mode Roles but does not have the View and Create Annotation permissions then, when they click on a field caption which has no previous annotations, they will see a pop-up informing them that there is "No annotation found on this field".
| |
| − | | |
| − | | |
| − | If the user has Edit Field in Annotation Mode Roles but does not have the View and Create Annotation permissions then, when they click on a field caption with previous annotations, they will see a pop-up with a Modify button. If they click on the Modify button then they are presented with the Edit Field screen, but the ability to edit the individual field is controlled by the associated [[Field Permissions]].
| |
| − | | |
| − | If the user has both Edit Field in Annotation Mode Roles and View and Create Annotation permissions then, when they click on a field caption which has no previous annotations, they would see a small icon with the caption '''New Annotations'''.
| |
| − | | |
| − | If the user has both Edit Field in Annotation Mode Roles and View and Create Annotation permissions then, when they click on a field caption which has already annotations, they would see a small icon with the caption '''Reply/Modify''' and the historic annotations displayed.
| |
| − | [[Image:AnnotationEditFieldButton.png|border]]
| |
| − | | |
| − | If the user clicks on the '''New Annotations''' or '''Reply/Modify''' button then they will see a Field Value option in the New Annotation screen.
| |
| − | | |
| − | [[Image:AnnotationEditFieldScreen.png|900px|border]]
| |
| − | | |
| − | | |
| − | If they edit the Field Value and click Save then the value stored against the field will be updated accordingly.
| |
| − | | |
| − | ===Review History===
| |
| − | The Revision History feature will list the full annotation history in one place. The history is updated each time when changes are submitted through the [[Submit buttons|Annotation submit button]]. The record must be under Status Lock in order for the Annotation Submit button to appear on the page.
| |
| − | | |
| − | The history will show both when the field is edited and when the record is submitted.
| |
| − | | |
| − | The ability to access the Revision History section is controlled by the [[UTA_Settings_-_Security#View_Revision_History|UTA Security Settings]].
| |
| − | | |
| − | The Revision History section is available by clicking on the Options section at the top of the UTA record, then clicking on the resulting Revision History section.
| |
| − | | |
| | [[Category:Annotations]] | | [[Category:Annotations]] |
Annotations are a collaborative tool that enables users to add notes and responses directly to specific fields within a record. By using field-level annotations, users can modify particular fields and respond to comments without altering the rest of the record. This article will guide you through utilizing and configuring the annotation collaboration feature as part of an application review process.
Note:
- You must be a Global Administrator to configure this feature.
- The interface and recommended configuration practices for the annotations feature have been updated as part of the July 2024 upgrade.
- You can only edit the values of a single field at a time using the annotations feature. Validation will only run on the field being modified. Therefore, if you are using dynamic field visibility controls or need to run full validation on the entire form, you may need to exit annotation mode and go to an unlocked status to achieve this.
How Annotations Work
Let's walk through how the annotation feature can be configured as part of an application process involving an applicant, a program manager, and a reviewer.
1. Applicant Submits Application
The applicant enters the required information into a form and submits it.
2. Program Manager Assigns a Reviewer
The program manager assigns a reviewer to the application and advances the application to the next stage.
3. Reviewer Conducts Initial Review and Creates Annotations
The reviewer is notified of their assignment to review the application.
In this scenario, the application is not yet ready to be approved or rejected, prompting the reviewer to make field-level suggestions (annotations) for changes or clarifications.
The reviewer hovers over and left-clicks the desired field to open a new annotation window. Here, they enter a message asking the applicant to change or clarify something related to this field, and then the reviewer saves the annotation.
This process is repeated for all fields requiring changes or clarifications.
Once all annotations are added, the reviewer clicks the annotation submission button to send the record back to the applicant.
4. Applicant Reviews Annotations, Modifies Values, and Adds Clarifications
The applicant is notified that action is required on their application.
The applicant navigates to their application, which opens in Annotation Mode.
In Annotation Mode, fields without annotations are locked. The applicant sees a list of annotations in the right panel and can click on any annotation to engage in a specific field-level discussion.
When focused on an annotation, the applicant can click the Reply button to open a modal window, where they can modify the field value and add a clarifying message.
Annotations from other users (such as the reviewer) are highlighted in yellow, indicating they may require a response, while annotations you create (as an applicant) are highlighted in blue.
After responding and modifying field values, the applicant clicks the annotation submission button to move the status forward, triggering a workflow that notifies the reviewer of the changes made.
5. Reviewer Conducts a Subsequent Review and Marks Annotations as Resolved
The reviewer is notified that action is required and navigates to the application.
The reviewer evaluates the changes and the applicant's replies. If no further changes or clarifications are needed, the reviewer marks each field-level annotation as resolved.
Resolved annotations are indicated with a green check mark, showing no further action is required.
If all outstanding changes are addressed, the reviewer advances the application using the annotation submission button.
6. Exiting Annotation Mode
Users can exit annotation mode by clicking the close icon (“X”) in the gray box. This may be necessary to access the left navigation or other record-related elements not visible in annotation mode. To re-enter annotation mode, click the "annotation mode" toggle located in the high availability area at the top right of the record.
Below is an explanation of how a Global Administrator could configure the annotations feature to work as described in the scenario above.
User Roles
You will need two roles: a role for the applicant and a role for the person doing the reviewing. Depending on your business process, you may already have two roles you can use or you may wish to create two new roles. If you are creating new roles, you may create these as system or UTA (association) roles depending upon your business process. To create new roles, navigate to the Menu Icon > Roles and Security > User Roles > Click the New Role button (represented by a plus sign). Typically roles created would be called “Applicant” and “Reviewer” or “Internal Staff”.
Annotation Types
Annotation types determine who can make annotations and when. Usually, there are two annotation types: one for the applicant and another for an internal staff member or designated reviewer.
Creating a "Reviewer" Annotation Type
- Navigate to Menu Icon > Global Settings > System tab > Annotation Types.
- Click the New Type button (represented by a plus sign).
- Create an annotation type with the name and caption of either “Reviewer Annotation” or “Staff Annotation” depending on your process and preferred terminology.
- Enter a description that states the purpose of this annotation type. For example, you could enter “Used to create field-level annotations by reviewers requesting changes from the applicant”.
- Navigate to the Permissions & Availability tab.
- For the Allow View field, select both the applicant and reviewer roles. This way both Applicants and reviewers will be able to see both types of annotations on a record.
- For the Allow Create field, select just the reviewer role. So only a reviewer can create the reviewer type of annotation.
Create an "Applicant" Annotation Type
- Navigate to Menu Icon > Global Settings > System tab > Annotation Types.
- Click the New Type button (looks like a plus sign).
- Create a type with the name and caption of “Applicant Annotation”.
- Enter a description the states the purpose of this annotation type. For example, you could enter “Used to create field-level annotations by the applicant, responding to change requests from a reviewer”.
- Navigate to the Permissions & Availability tab.
- For the Allow View field, select both the applicant and reviewer roles. This way both applicants and reviewers will be able to see both types of annotations on a record.
- For the Allow Create field, select just the applicant role. So only an applicant can create the applicant type of annotation.
Setting up Statuses for Annotations
Status are used to control what happens at different stages of a process such as bringing the user directly into annotation mode and notifying a user that they need to change values on their application. To achieve the above scenario, we are using many statuses within our desired universal tracking application.
Statuses are created by going to the desired Universal Tracking Application > Configuration Settings > Select the desired tab (such as “Level 1 Grant”) > Statuses > Click the New Status button (represented by a plus sign). Enter the desired information and define the availability, permissions, and then click Save.
Below is an explanation of each status and how it was configured:
| Name
|
Description
|
Configuration Steps
|
| Draft
|
The grant application is being filled in by the applicant.
|
- Toggle on Is Default Status
- Toggle on Is Default Copy Status
- Go to the Permissions & Availability tab and under the “Availability” section, select the relevant grant types for the Enable on Grant Types field.
|
| Submitted
|
The applicant has submitted the application and can no longer edit it.
|
- Toggle on Lock On Status
- Go to the Permissions & Availability tab and under the “Role Permissions” section, select the “Program Manager” user role for the Override Lock field so they can move the record forward after assigning a reviewer.
- Go to the Permissions & Availability tab and under the “Availability” section, select the relevant grant types for the Enable on Grant Types field.
|
| Reviewer Assigned and Notified
|
The reviewer has been notified that the application is ready for review.
|
- Toggle on Lock On Status
- Go to the Permissions & Availability tab and under the “Role Permissions” section, select the “Program Manager” user role for the Override Lock field so they can move the record forward
- Go to the Permissions & Availability tab and under the “Availability” section, select the relevant grant types for the Enable on Grant Types field.
- Set up a Level 1 workflow to send an email notification to the reviewer by going to Menu Icon > Workflows > Create a new workflow > Set Workflow Object to this UTA and set Trigger On to this status.
|
| Reviewer Annotation Creation
|
The reviewer adds annotations to the grant application, requesting changes and clarifications. They also review the applicant's annotations.
|
- Toggle on Lock On Status
- Go to the Permissions & Availability tab and under the “Annotation System Role Permissions” section, select the “Applicant” user role for the View field, select the “Reviewer” user role for the View and Create field, and select both “Applicant” and “Reviewer” user roles for the Open in Annotation Mode field.
- Go to the Permissions & Availability tab and under the “Availability” section, select the relevant grant types for the Enable on Grant Types field.
|
| Revisions Requested
|
The applicant is notified. They must change values, reply to annotations, and provide clarity to issues raised.
|
- Toggle on Lock On Status
- Go to the Permissions & Availability tab and under the “Annotation System Role Permissions” section, select the “Applicant” user role for the View field as well as the Edit Field input, select the “Reviewer” user role for the View and Create field, and select both “Applicant” and “Reviewer” user roles for the Open in Annotation Mode field.
- Go to the Permissions & Availability tab and under the “Availability” section, select the relevant grant types for the Enable on Grant Types field.
- Set up a Level 1 workflow to send an email notification to the applicant by going to Menu Icon > Workflows > Create a new workflow > Set Workflow Object to this UTA and set Trigger On to this status.
|
| Applicant Revisions Submitted
|
The reviewer is notified that the applicant has made the requested changes and provided clarity.
|
- Toggle on Lock On Status
- Go to the Permissions & Availability tab and under the “Annotation System Role Permissions” section, select the “Applicant” and “Reviewer” user roles for the View field, select the “Reviewer” user role for the View and Create field, and select both “Applicant” and “Reviewer” user roles for the Open in Annotation Mode field.
- Go to the Permissions & Availability tab and under the “Availability” section, select the relevant grant types for the Enable on Grant Types field.
Set up a Level 1 workflow to send an email notification to the reviewer by going to Menu Icon > Workflows > Create a new workflow > Set Workflow Object to this UTA and set Trigger On to this status.
|
| Approved
|
The grant application has been approved.
|
- Toggle on Lock On Status
- Go to the Permissions & Availability tab and under the “Availability” section, select the relevant grant types for the Enable on Grant Types field.
|
| Declined
|
The grant application has been declined.
|
- Toggle on Lock On Status
- Go to the Permissions & Availability tab and under the “Availability” section, select the relevant grant types for the Enable on Grant Types field.
|
Status Settings Explained
These settings are found at UTA > Configuration Settings > Level 1 tab > Statuses > Select a Status.
Lock On Status
Prevents users from editing the application record and hides any Save and Submit Buttons configured to appear on this status.
Override Lock
Allows a user role to edit a locked record and see the submit and save buttons configured to appear at this status.
Availability
Controls which types of applications will have access to this status
Annotation System Roles and Annotation Association Role Permissions
Depending on the business requirements you may choose to use Annotation System Roles (Example: anyone with the system reviewer role has permissions) or Annotation Association Role Permissions (Example: anyone attached to the record as a contact in the UTA role of reviewer has permissions).
View
Who can see the annotations
View and Create
Who can see create new and reply to annotations
Edit Field
Who can edit the value of the field being annotated
Open in Annotation Mode
Who can see the record in annotation mode by default
Anonymize Creator
Hides the name of the person who added the annotation
Workflow Notifications
At multiple stages in the process notifications will automatically be sent to the reviewer and applicant letting them know that action is required on an application.
To accomplish this a workflow is set up by navigating to Menu Icon > Workflows.
- Click the “New Workflow” button (looks like a plus sign).
- Select the desired UTA for the Workflow Object field.
- Select the desired Level 1 status for the Trigger On field. Then click Save.
- Setup a task with the Task Type of “Acknowledgement” and choose the message type of “Email”.
- In the email message, you may wish to include both the name of the application and a link to the application.
Submit Buttons and Annotation Submission Buttons
Submit buttons move a record between statuses that are not locked. A user role can also be given permission to override a locked status to see submit buttons.
Annotation submission buttons are intended for use only in Annotation Mode when the record is locked where other submit and save buttons are hidden.
Both types of submission buttons are configured by navigating to the desired UTA > Configuration Settings > Click on the desired Level 1, 2, or 3 tab > Submit and Save Buttons.
We created the following submit buttons for our scenario:
| Name
|
Description
|
Type
|
Configuration Steps
|
| Submit
|
Applicant submits and this locks the application to the applicant.
|
Submit
|
- Select “Draft” under the Available to Status field.
- Select “Submitted” under the Submit to Status field.
- Toggle on Enable Confirmation Alert Message. Under the Confirmation Message input, enter: “Your application will be sent for review. Once sent, you will no longer be able to modify your application. Are you sure you wish to continue?”
- Toggle on Enable Confirmation Page. For Title, enter “Application Submitted”. For the Message input, enter: “Thank you. Your application has been submitted and will be reviewed.”
- For the Redirect URL, click the URL Lookup button (represented by the binoculars icon) to select the page the user should be redirected to after submitting their application. For the Button Caption input, enter “Back to list of applications”.
|
| Begin Review Process
|
A reviewer is assigned who will approve, decline or annotate the application
|
Submit
|
- Select “Submitted” under the Available to Status field.
- Select “Reviewer Assigned and Notified” under the Submit to Status field.
- Go to the Permissions & Availability tab and under the “Role - Permissions” section, select the “Program Manager” user role for the Allow View field.
|
| Move to Reviewer Annotation and Review
|
Record moved to reviewer annotation and review after the reviewer was assigned and notified.
|
Submit
|
- Select “Reviewer Assigned and Notified” under the Submit to Status field.
- Go to the Permissions & Availability tab and under the “Role - Permissions” section, select the “Program Manager” user role for the Allow View field.
|
| Send Requested Revisions to Applicant
|
Sends requested revisions to the applicant.
|
Submit Annotation
|
- Select “Reviewer Annotation and Review” under the Available to Status field.
- Select “Revisions Requested” under the Submit to Status field.
- Toggle on Enable Confirmation Alert Message. Under the Confirmation Message input, enter: “Annotations will be sent to the applicant for review and amendment. Once sent, you will no longer be able to add additional annotations. Are you sure you wish to continue?”
- Go to the Permissions & Availability tab and under the “Role - Permissions” section, select the “Reviewer” user role for the Allow View field.
|
| Submit Revisions
|
Sends revisions from applicant to reviewer.
|
Submit Annotation
|
- Select “Revisions Requested” under the Available to Status field.
- Select “Reviewer annotation and review” under the Submit to Status field.
- Toggle on Enable Confirmation Alert Message. Under the Confirmation Message input, enter: “Your annotations and amendments will be sent for review. Once sent, you will no longer be able to add additional annotations or make changes. Are you sure you wish to continue?”
- Toggle on Enable Confirmation Page. For Title, enter “Revisions Submitted”. For the Message input, enter: “Your revisions have been submitted and will be reviewed.”
- For the Redirect URL, click the URL Lookup button (represented by the binoculars icon) to select the page the user should be redirected to after submitting their application. For the Button Caption input, enter “Back to list of applications”.
- Go to the Permissions & Availability tab and under the “Role - Permissions” section, select the “Applicant” user role for the Allow View field.
|
| Approve Application
|
The reviewer approves the application (no more changes are required).
|
Submit Annotation
|
- Select “Reviewer Annotation and Review” under the Available to Status field.
- Select “Approved” under the Submit to Status field.
- Toggle on Enable Confirmation Alert Message. Under the Confirmation Message input, enter: “This record will be moved to approved. Once approved, you will no longer be able to add additional annotations or request changes. Are you sure you wish to continue?”
- Toggle on Enable Confirmation Page. For Title, enter “Application Approved”. For the Message input, enter: “The application has been approved”.
- For the Redirect URL, click the URL Lookup button (represented by the binoculars icon) to select the page the user should be redirected to after submitting their application. For the Button Caption input, enter “Back to list of applications”.
- Go to the Permissions & Availability tab and under the “Role - Permissions” section, select the “Reviewer” user role for the Allow View field.
|
| Decline Application
|
The reviewer declines the application.
|
Submit Annotation
|
- Select “Reviewer Annotation and Review” under the Available to Status field.
- Select “Declined” under the Submit to Status field.
Toggle on Enable Confirmation Alert Message. Under the Confirmation Message input, enter: “This record will be moved to Declined. Once declined, you will no longer be able to add annotations or request changes. Are you sure you wish to continue?”
- Toggle on Enable Confirmation Page. For Title, enter “Application Declined”. For the Message input, enter: “This record will be moved to Declined. Once declined, you will no longer be able to add annotations or request changes. Are you sure you wish to continue?”.
- For the Redirect URL, click the URL Lookup button (represented by the binoculars icon) to select the page the user should be redirected to after submitting their application. For the Button Caption input, enter “Back to list of applications”.
- Go to the Permissions & Availability tab and under the “Role - Permissions” section, select the “Reviewer” user role for the Allow View field.
|
Revision History
In addition to the annotation list in the right panel, you can optionally view a chronological history of annotations. To enable this feature, go to the desired universal tracking application, then navigate to Configuration Settings > Security tab > Feature and Function Permissions > Select the desired roles under Enable Revision History.
To view the annotation history log, go to the desired record > Click on Logs in the top action menu > Revisions History.