This checklist includes some recommended best practices for admin users to reference when building and testing a new Application in Risk Cloud.
Review All Steps: Fields & Sections
Field Configuration
- Review each Step to make sure the appropriate Fields are displayed – you can check the available Fields section on the right to see if there are any Fields that aren’t displayed that should be
- If you’ve added any new Fields while building, make sure they have been added in all applicable Steps
- Make sure all Fields have the appropriate settings for that Step in the Application (read-only, enabled, required)
Specific Field Settings
- Text Fields: add data validations where applicable (e.g., phone number, email address)
- Text Area Fields: make sure rich-text is enabled, if desired
- E-Signature Fields: make sure you’ve specified at least one Signing Reason
- Checkbox, Multi Select, Radio, and Select Fields: make sure you’ve specified the appropriate Select Values and designated Numeric Values (if applicable)
- User Fields: make sure you’ve mapped at least one User or Role
- Calculation Fields: make sure the appropriate Fields are being referenced (if applicable)
- If any of the Fields that are referenced in a calculation are in a conditional section, make sure that they have an appropriate default value specified in the case where the condition is not triggered
- Multiple Field types: Make sure default values are defined where appropriate
- If some Records were created before default values were finalized, they will need to be manually updated if you want the default value applied
- Add tool tips where needed
Instructions in Text Area Fields & Rich Text Context Sections
- Add instructions to Text Area Fields or Rich Text Content Sections with default text to each Steps, as needed
- If some Records were created before default text is finalized, make sure to manually update those Records to display the correct instructions text
- If instructions in Text Areas or Rich Text Content Sections include links to other references that you want to open up in a new tab (instead of redirecting the user away from Risk Cloud), make sure that the URL HTML says target=”_blank”
Sections
- If you’ve made changes to any Section or Subsection header labels, make sure those changes have been propagated throughout all Steps where applicable
- Check to make sure that Sections are set to be initially expanded or collapsed as desired (all Sections will be set to expanded by default)
Conditional Form Logic
- If using Conditions on Sections or Subsections, make sure they are enabled
- If there are multiple Conditions on a Section or Subsection, make sure they are listed in the correct order (Conditions are executed in order from first to last)
Review All Steps: Paths & Assignee Options
Paths
- Make sure the correct Default Path is designated
- Make sure the appropriate Conditional Edge Paths have been added and they are listed in the correct order (Conditions are executed in order from first to last)
- Add Selected Redirects where needed (common to add redirects to End Steps in case an item needs to be reopened)
Assignee Options
- Ensure assignee selection is enabled on paths when needed (app user assignee or external email assignee)
- Add Assignee Rules if applicable User Fields are used
Review All Steps: Workflow Link Sections
Workflow Link Sections
- Ensure Workflow Link sections have a custom Layout selected
- If Searchable is enabled, make sure the Search Step is correct
- If Creatable is enabled:
- Make sure Auto-Start is also enabled (recommended)
- Make sure the Origin Step is correct
- Change section header to say “Click "CREATE NEW [OBJECT NAME]" below to add/initiate a [object]:” (recommended)
Jobs
Jobs
- Review each possible path in the Workflow and make sure there is a Job associated with it if you want a notification to be sent (these will all likely be Moved Trigger Jobs)
- If there are any points in the Application where work may be re-assigned and you want a notification to be sent upon re-assignment, make sure to create the appropriate Assigned trigger Jobs
- Create Due Date Trigger Jobs if you want Due Date reminders to be sent
Jobs Configuration
- If any Jobs should only be triggered based on certain conditions, make sure the appropriate conditions have been added
- In the Messages tab:
- Make sure the appropriate recipients are designated
- If you want Field results to be displayed, make sure the checkbox is checked and that you have selected a custom Layout
Layouts
Layouts
- Create Work Queue Layouts and make sure they are specified as 'Use for Work Queue'
- Create other Layouts contextualized for Workflow Links, Jobs, and Relationship Reports, as needed
- For all Layouts:
- Should typically have at least one Linked Field (for Work Queue layouts especially)
- Designate “Sort By” Field if needed
- Change header names as needed (e.g. “Record Name” → “Assessment ID”)
Application Builder: Step Access & Settings
Step Entitlements
- Ensure each Step has at least one Role with Edit access (an Admin role should typically have Edit access in every Step)
- Review the rest of the Roles and make sure the appropriate ones have been granted Edit or Read-Only access per Step
Step Settings
- If any Steps should have SLAs, make sure they are enabled
- For any Workflows that contain Child items, if you only want them to be creatable from a Parent, make sure to toggle off any Origin Steps in the Child Workflow
- For any Origin steps, if you want them to be available as a public form, make sure the Public setting is enabled
- Generate a token and make sure the URL is shared with the appropriate people or posted in the appropriate place so that it can be accessed
- Set up public link expiration dates, if applicable
Application Builder: Workflow Settings
Workflow Settings
- If User Group access should be enforced, make sure that setting is enabled
- If User Group access enforced, make sure at least one User Group is required (recommended)
- Ensure default User Groups are specified
- If there should be a Workflow SLA, make sure it is enabled
- Rearrange the Steps in the appropriate order (this impacts the order steps are displayed in the Status Report)
- Make sure the appropriate Workflow relationships are defined
Access
Roles
- Make sure the appropriate Roles have been specified based on the various people involved in the Application and their division of responsibilities
- Make sure each Role has the appropriate Module entitlements and Step Entitlements
- Make sure the appropriate Users have been added to each Role
- Determine whether User Group access needs to be enforced (if they want to limit what is shown on a Record-by-Record basis)
- Make sure the appropriate Users have been added to each User Group