Changes

Common Workflow Tasks for Awarded / Approved Status

33 bytes added, 15:02, 11 May 2022

→‎Overview

=Overview=

<u>'''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. '''</u>

Example: Once an your application is moved to the Approved Status - you want to create hits a payment activityspecific status, there may be a few report handful of activities, send an email that need to be created or fields that need to be updated in order for the application to move to the applicantnext status. By using various workflow tasks, you can have all these tasks completed automatically, and update the Approved Date fieldsimplifying your granting process.

<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=

• ← Older edit
• Newer edit →

Morgan Liik

121

edits