121
edits
Changes
→Configuration - Essentials
=Configuration - Essentials=
<u>'''Creating a </u> ''''''New Workflow'''</u>
* Create a new workflow by clicking the plus button on the workflows home page.
* Select '''Workflow Type''': The type will dictate what which information/fields will be available when creating tasks - You can select different UTA’s, levels, contacts, organizations etc… as your workflow type.
* Name the workflow and add it to a Category
** Suggested naming convention: Activity Level UTA, Record Level (1/2/3) - Goal/Status *** '''EX: ''' Submission Manager L1 - Approved Status
** Categories are created by your organization. We suggest creating categories based on the UTA and Record Level.
*** '''EX: Application ''' Submission Manager L1* Add a a workflow description for your workflow(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.
* Set the '''Trigger-On'''** This The trigger dictates what status or stage of the record action will set this process in motioninitiate 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.
INSERT IMAGE HERE
'''<strong> '''</strong>
<span style="color: #ff0000;">'''*Tip*'''</span> → You can build your a workflow on your production system first and test it on your backup the next the following day. Make Make sure to set the Trigger-on 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 status correct trigger and test your workflow without worrying about impacting your production environment.
''' '''
