Changes

Common Workflow Tasks for Awarded / Approved Status

15 bytes removed, 17:10, 20 May 2022

→‎Configuring A Workflow

===Configuring A Workflow===

# Item Select '''Workflow Type''': The type will dictate which information/fields will be available when creating tasks - You can select different UTA’s, levels, contacts, organizations etc… as your workflow type.# Item Name the workflow and add it to a Category

: Suggested naming convention: UTA, Record Level (1/2/3) - Goal/Status

:: Categories are created by your organization. We suggest creating categories based on the UTA and Record Level.

::: '''EX:''' Submission  Manager L1

: # Item Add a workflow description (optional). :#* #*:** Include a list of tasks and branching conditions for ease of review later.:#*:** Add notes to your workflow if you make changes to it.# Item Set the '''Trigger-On''':#* #*:** The trigger dictates what status or action will initiate the workflow.:#*:** Depending on the workflow type, you will be selecting from a list of statuses or activities.:#*:** For our example, we will be triggering our workflow when a record hits the Approved status.

[[File:Creating Approved Status Workflow- Workflow Main Set-up Page.png|thumb|none|800px|Creating Approved Status Workflow - Workflow Main Set-up Page]]

<span style="color: #000000;">'''Tip:'''</span> You can build a workflow on your production system first and test it on your backup the following day. Make sure to set the Trigger-On to Deactivate so the workflow won’t run. Once your workflow appears in your backup, you can set the Trigger-On to the correct trigger and test your workflow without worrying about impacting your production environment.

• ← Older edit
• Newer edit →

Morgan Liik

121

edits