Best practices for using creating custom tasks in Workbench

Depending on what you want to modify, copy an existing process to a new application and modify it. For example, when you are required to modify the task assigned to a review initiator, copy the AssignTaskToInitiator process.

Every Assign Task operation that you use in a process to assign tasks to reviewer ir approver must start with Pre Assign Task operation. The process is also required to end with a Post Assign Task operation.

Ensure that the status and disposition attributes are updated in the ParticipantTO variable before you invoke the Post Assign Task operation.

Customize email templates in the Assign Task operation as required. Email templates control the notifications sent to review and approval participants when they are assigned a task. These emails differ from the notifications sent to users when actions occur during the review.

It is necessary to keep only one of the branches of Assign Task route in your custom task. Either keep the Use Reply To Complete or the other route. When you keep the Use Reply To Complete route, remove the route condition from the Assign Task operation. Removal of the route is required because the useReplyToComplete variable is set to true only when the EMAIL_CONNECTED option is selected. When a custom task type is selected, the task type value is CUSTOM, therefore, the useReplyToComplete variable never evaluates to a value of true.