Building Lifecycle Applications for v5.0
Process rules define how workflows behave and have two main parts:
1) Process Information - Defines the high-level process information.
2) Task Rules - Define the task rules that defines the process behavior.
For more information on designing and implementing workflows, refer to the Building Lifecycle Applications Reference.
Creating a New Process
When you press the New button the following screen is displayed:

Field Name | Description |
Name | The name of the process. |
Description | The description of the process. |
Published | The published flag indicates whether the Workflow Connector will process the workflow rules or not. Note, you can make the process published/unpublished from the main process view. |
Cabinet | The target cabinet for the process. |
Starting Workflows |
There are two methods for starting a workflow:
|
Creating Tasks
Once the main process information has been saved, click on the View Tasks link to manage the task creation/updates. Press the New button to create the task. There are three task types:
- Begin - A process requires a Begin task.
- Task - A process will have numerous Task types depending on the business rules.
- End - A process requires an End task.
It is recommended to create the tasks first and then create the connections between the tasks.

Field | Description |
Sequence No | The order the tasks are displayed in the designed, which can help orientate you. |
Task Name | The name of the task that will appear in the user's inbox.. |
Task Description | The description of the task that will appear in the user's inbox. |
Task Group | The task group allows related tasks to be grouped together, which can be useful when designing large workflows. |
Task Mode | Defines whether the task is a Begin, Task, or End task. |
Task Type |
The type of task:
|
Editing a Task
Once the basic task information has been entered and saved, edit the task to enter:
Business Rule
You can enter DocScript to execute before and after the task has been processed.
- Lifecycle DocScript Overview
- Lifecycle DocScript Functions
- Lifecycle DocScript System Variables
- DocuNECT Snippet Library
Task Connections
This tab specifies how the tasks are connected within the workflow:

Field | Description |
Success Connection Execution Rules |
Determine when the next steps of the workflow is executed if the task is successful.
|
Comment If Successful | Allows a comment to be added if the task is successful that is added to the workflow history. |
Next Task(s) If Business Rule Succeeds | Determines what are the next tasks if the task is successful. |
Failure Connection Execution Rules |
Determine when the next steps of the workflow is executed if the task has failed.
|
Comment If Fail | Allows a comment to be added if the task has failed that is added to the workflow history. |
Next Task(s) If Business Rule Failed | Determines what are the next tasks if the task has failed. |
Email Notification
An email can be sent automatically to the user, or all users within the role task when it is received.

Field | Description |
Email Subject | Email subject. Note, refer to the Lifecycle DocScript System Variables in the Document Workflow section to variables that can be added to an workflow email message. |
Email Message | Email message. Note, refer to the Lifecycle DocScript System Variables in the Document Workflow section to variables that can be added to an workflow email message. |
Task Information
Additional information can be presented to the user in the Task Information. This can be text or HTML.
