Workflows Frequently Asked Questions
General
The same workflow is used across multiple programs. How can it be set up so that users only see applications for one program and not another?
It is recommended to use different workflows for multiple programs if user access varies.
What is an example of what a complete workflow may look like?
An example of a workflow structure is shown below. Within this workflow, there are four levels:
-
Grant Manager Review - This level is divided into multiple sub-levels based on the Grant Reviewers tasked with reviewing the applications.
-
Secondary Grant Manager Review - This level is divided into multiple sub-levels based on the Grant Reviewers tasked with reviewing the applications.
-
Financial Review Stage - This level is divided into sub-levels based on the Amount Requested for each application.
-
Final Review (if applicable) - This level is optional and does not contain any sub-levels.
Note: The structure of a workflow will vary based on the client, program, and processes in place.
Permissions
What user permissions are required to create and manage workflows?
Users are required to have the following permission:
-
System - Can Manage Workflows
Note: The System - All permission will also allow users to perform these actions.
Optional Permissions
Users will need to have the following permissions to perform certain optional actions:
-
System - Can Configure Workflow Automations - This is required to set up automation for new applications or specific workflow levels.
Note: The System - All permission will also allow users to perform these actions.
Workflow Level Automation
What happens if an application is routed to the wrong workflow level during automation?
If an application is assigned to the wrong workflow level, then a Grant Manager with access to workflow automation can reroute it to any workflow level within that workflow after the initial assignment. An example of when an application may be automatically routed to an incorrect level would be if the Applicant chose the wrong answer on their default form.
If a workflow level assignment or rule is edited, will it impact the applications already assigned to the workflow level?
No. Any edits made to assignments or rules will not affect applications that were submitted prior to the change being saved. Additionally, applications that are in the workflow level and have already met the criteria for routing will not be routed based on the new updated rules unless subsequent action is taken that triggers routing.
Why does a newly created workflow level assignment show as inactive?
By default, all new assignments are set up as inactive. Users must manually activate it before the Status will change to Active and the rules will begin applying to submissions.
What happens if a submission does not meet the criteria outlined by the workflow level assignment?
If an application does not satisfy the rules in the assignments, then it will be assigned to the default workflow level for the program.
Will making edits to forms, workflows, etc. impact workflow level assignments?
It depends on the edits made. If a rule calls a specific program, workflow, etc. that has been modified, it could cause the assignment to become invalid. It is recommended to review all rules associated with these components when changes are made.
Can I route applications to a different workflow using workflow level automation?
No, applications cannot be routed to a different workflow.
What fields can be used when creating workflow level assignments and rules?
The following fields are available for use in workflow level assignments.
| Category or Form | Available Fields |
|---|---|
| Application |
|
| Applicant |
|
| Budget |
|
| Organization |
|
| Employee |
Any Employee SSO fields that are enabled for your organization are available for use in automations. |