Changes

Common Workflow Tasks for Awarded / Approved Status

3,738 bytes added, 15:15, 10 May 2022
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..."
=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 activity and email tasks and only update the Approved Date field.

=Configuration - Essentials=
=Configuration - Advanced=
=Appendix=
==Options and Settings==
<!--Explain all applicable misc options and settings that shouldn't be explained above here...-->
===General Settings===
{| class="wikitable"
|-
!|Option
!|Description
!|Example
|-
||
||
||
|}


===Display Settings===
{| class="wikitable"
|-
!|Option
!|Description
!|Example
|-
||
||
||
|}

=Examples=
<!--

{| class="wikitable"
!| Option
!| Description
!| Example
|-
|
|
|
|}



Sample Syntax Format:
Empty space at start of line to highlight the row, italicize any variables that the user would fill in (as opposed to literal words that need to be used in syntax)

@section.''SectionNodeName''@



Sample Code Block:
When you want to write an example block of code, you should highlight it and also escape any special characters that might be construed as HTML formatting and outputted incorrectly by the Wiki by using a pre (pre-formatted text) tag

<pre>
<?xml version="1.0"?>
<Company>
<Name>Oranges Inc.</Name>
<Description>Peel.
Eat.
Repeat.</Description>
</Company>
<Company>
<Name>Bananas Ltd.</Name>
<Description>You're going to go "bananas" over our product!</Description>
</Company>
</pre>



Unordered list:
When listing information with bullet points in no order

* Point 1
* Point 2
* Point 3



Ordered list:
When listing information with numbers to denote ordered steps

# Step 1
# Step 2
# Step 3



Sample Page Header Banners:
Deprecated Feature
<span class="mceNonEditable template" id="bs_template:@@@TPL0@@@" data-bs-name="Deprecated" data-bs-type="template" data-bs-id="0"><span class="mceNonEditable template" id="bs_template:@@@TPL0@@@" data-bs-name=" Deprecated" data-bs-type="template" data-bs-id="0">{{ Deprecated }}</span></span>
Deprecated Page
<span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name="DeprecatedPage" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" DeprecatedPage" data-bs-type="template" data-bs-id="1">{{ DeprecatedPage }}</span></span>
Professional Services
<span class="mceNonEditable template" id="bs_template:@@@TPL2@@@" data-bs-name="Banner-Billable" data-bs-type="template" data-bs-id="2"><span class="mceNonEditable template" id="bs_template:@@@TPL2@@@" data-bs-name=" Banner-Billable" data-bs-type="template" data-bs-id="2">{{ Banner-Billable }}</span></span>
Page Under Construction
<span class="mceNonEditable template" id="bs_template:@@@TPL3@@@" data-bs-name="Banner-UnderConstruction" data-bs-type="template" data-bs-id="3"><span class="mceNonEditable template" id="bs_template:@@@TPL3@@@" data-bs-name=" Banner-UnderConstruction" data-bs-type="template" data-bs-id="3">{{ Banner-UnderConstruction }}</span></span>

-->
Smartstaff, administrator
67
edits