Changes

* Tasks: define the actions required in the workflow – each task represents a single step in the process. Specific roles or specific users are associated with each task, and these people will be automatically alerted when they need to perform the action defined by that task. These actions are generally used to accept, reject, or request a revision on the associated object, file, user or some application-specific information.

* Connectors: link tasks together, and provide for branching logic based on the user responses to the task or pre-set conditions.

=Configuring – Essentials=

==Create Workflow==

* Pending Queue – click this tab to see a list of outstanding tasks for this workflow, you can delete tasks and reassign tasks to other contacts within the system.

* History - click this tab to see a list of completed tasks for this workflow.

3. The Task details are displayed, with a Task Number initially set to 100 and increasing in increments of 10 for each subsequent workflow task.

[[Image:workflow2017_3.png|1000px]]

4. Update Task Name then select the Task Type. The task type determines how the task should be processed. The available Task Types include:

* '''Acknowledgement''' - use to generate a message such as an email to appropriate users.

9. The Task is listed, but without Connectors, the task will not be executed if the workflow is triggered.

==Create Workflow Connectors==

* If the Acknowledgement task is attached directly after the connector with the delay then the original three contacts will receive the email, even though they are no longer current.

* If there is a blank workflow task following the connector with the delay, which flows into a workflow task configured to email all Level 1 contacts with the role Reviewer, then the four reviewers on the Level 1 record at the time the email is sent, will be emailed, rather than the original three reviewers.

==Enable on Object==