Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Chase Workflows monitor the status of activities, route work from one activity to another, and enforce business rules.  They ensure that when a project is complete, all necessary steps have been taken and constraints imposed by management have been adhered to.

Chase allows agencies to automate many of their processes by: 

  • Providing statuses for the documents used to control a process.
  • Requiring actions to be performed in response to a change in a document’s status.
  • Monitoring those actions to ensure they are carried out promptly, and escalating those past due.
  • Initiating further or automated actions that will progress a process to its next phase of activity and eventually to its conclusion. 

In Chase, there are two types of workflows, a Predefined workflow and a Manual workflow. 


Children Display

Predefined Workflow

A Predefined Workflow is activated automatically in response to a change in document status.  When there is a status change to a document, a Workflow initiated message will appear, explaining the action the Workflow took.

This workflow is set up in the Configuration. Not all users are able to set up a workflow but in most agencies, the Client Service and Production users can.

To view details of all Workflows activated in response to your actions, check the Workflows Created tab on your Chase Home page. To view details of all actions required by you in response to a Workflow, check the To Do tab on your Chase Home page.

For more field help on this dialog follow this help topic: Workflow dialog explained

Manual Workflow

The Manual Workflow requires a manual action to be performed on a document.  If an action is taken, a Workflow initiated message will appear, explaining the action taken by the Workflow.

The action is taken from the Workflow Action button that appears on each document.

titleScreen layout

Workflow Setup screen

titleField Help
Applies ToSpecify to which type of document the Workflow will apply.

Triggers are used to activate actions when certain conditions change on a Form. For example, once a User changes the status of a document, a Workflow will kick off.

DescThis can be specified to provide a custom description of the Workflow created.
ValuesIndicates that the Workflow kicks off when the status of the document changes from one status to another.
Additional FiltersAllows you to enter additional conditions that must apply before the Workflow will run.
OriginatorIndicate that the Workflow will be run only when a specific User has changed the document’s status.
RecipientIndicate a User who must take action required by the Workflow. For example, a User who will approve/decline the Workflow, or Users who will be notified or who need to acknowledge the Workflow.
Is ActiveIf checked, it indicates that the Workflow can be used immediately after creation. If unchecked, the Workflow cannot be used.