Key Features

• Different Automated Tasks can be configured for different request type. Same automated task can be used across different requests as well. 
• Details of the assigned task will be pre-filled to increase efficiency. 
• Automated tasks are included in reminder emails once they are within 90 days of the task due date. 
• Users with the Edit All Tasks privilege (Task Admin) can update any field within automated tasks, including the assigned from and due date fields. 
• Another version of Automated tasks can be configured for Third-Party Renewals. 

Configurations

• Automated tasks can be configured to be triggered by the system when the request activity or recipient is approved 
• Multi-recipient requests can be configured to create a separate task for each approved recipient. (e.g. task to upload completed contract for each HCP
• Task due dates can be based on the following: 
  • X number of days after full approval
  • X number of days after recipient approval
  • X number of days after activity end date
  • Based on Risk Score and Final Approval Date

Things to Note

• Automated tasks are always assigned from System User.

Expected Behavior 

Updates to Engagements or Tasks

• If an approved engagement is updated and reapproved, but the corresponding automated task is already marked as completed or canceled, the task is restarted and the due date is updated to correspond with the updated engagement.

The update is logged in the Task History by System User. 

• If the request is submitted with Approver A as the approver and Approver A shares the request for Approver Collaboration with User B, then the following rules apply:
  • If Approver A approves the request the automated task will be assigned to Approver A
  • If Approver B approves the request the automated task will be assigned to Approver B
• If the submitter is reassigned after the approval of an engagement, the corresponding automated task has to be manually reassigned to the new submitter.  
• If Approver A is reassigned to Approver B before the request is fully approved, the automated tasks will be assigned to Approver B (after the request is fully approved)
• If Approver A is reassigned to Approver B after the request is fully approved, then the task created upon full approval will remain assigned to Approver A. Any corresponding tasks can be manually reassigned to the new approver.