Difference between revisions of "Common Workflow Tasks for Awarded / Approved Status"
Greg Stanley (talk | contribs) (Created page with "=Overview= Use case: Once your application hits a specific status, there may be a handful of activities that need to be created or fields that need to be updated in order for...") |
Morgan Liik (talk | contribs) (→Overview) |
||
| Line 1: | Line 1: | ||
=Overview= | =Overview= | ||
| − | Use case | + | <u>'''Use case'''</u> |
| − | |||
| − | + | Once your application hits a specific status, there may be a handful of activities that need to be created or fields that need to be updated in order for the application to move to the next status. By using various workflow tasks, you can have all these tasks completed automatically, simplifying your granting process. | |
| − | Once | ||
| − | Some applications may have already been in the Approved Status but were sent back for review or updates. In this case, you don't want applications that have already gone through the Approved Status workflow to repeat the tasks listed above once their status is updated to Approved again. In this case, you will configure the workflow to bypass the activity and email tasks and only update the Approved Date field. | + | <u>'''Example:'''</u> |
| + | |||
| + | Once an application is moved to the Approved Status - you want to create a payment activity, a few report activities, send an email to the applicant, and update the Approved Date field. | ||
| + | |||
| + | Some applications may have already been in the Approved Status but were sent back for review or updates. In this case, you don't want applications that have already gone through the Approved Status workflow to repeat the tasks listed above once their status is updated to Approved again. In this case, you will configure the workflow to bypass the create new activity and email tasks and only update the Approved Date field. | ||
=Configuration - Essentials= | =Configuration - Essentials= | ||
Revision as of 10:02, 11 May 2022
Contents
Overview
Use case
Once your application hits a specific status, there may be a handful of activities that need to be created or fields that need to be updated in order for the application to move to the next status. By using various workflow tasks, you can have all these tasks completed automatically, simplifying your granting process.
Example:
Once an application is moved to the Approved Status - you want to create a payment activity, a few report activities, send an email to the applicant, and update the Approved Date field.
Some applications may have already been in the Approved Status but were sent back for review or updates. In this case, you don't want applications that have already gone through the Approved Status workflow to repeat the tasks listed above once their status is updated to Approved again. In this case, you will configure the workflow to bypass the create new activity and email tasks and only update the Approved Date field.
Configuration - Essentials
Configuration - Advanced
Appendix
Options and Settings
General Settings
| Option | Description | Example |
|---|---|---|
Display Settings
| Option | Description | Example |
|---|---|---|
