Tasks are created and managed within the contract and tied to that specific contract version. Tasks remain visible even after they are marked as Completed or Cancelled.

Tasks configured with Publish Task When = Send for Review is published only once, when the contract is sent for review after the task is created. If users send the same contract version for review multiple times, the system does not re-publish the task or resend notifications. If the contract has already been sent for review before the task is created, the system waits for the next Send for Review action. Tasks published through Send for Review remain associated with the contract version in which they were created.

Tasks continue normally after activation, task ownership and reminders remain intact, and stay associated with the activated contract version.

Tasks can be created, edited, and deleted for an amended contract. Tasks created for the amended contract are linked only to the amended contract version. Tasks from the parent (active) contract are not copied or inherited, regardless of their status. Parent contract tasks remain unchanged and are visible only in the original contract.

Tasks can be created, edited, and deleted for a renewed contract. Tasks created for the renewed contract are linked only to the renewed contract version. Tasks from the original (pre-renewal) contract are not copied or inherited, regardless of their status. Original contract tasks remain unchanged and are visible only in the original contract.

Tasks After Contract Cloning

Tasks are not copied when an activated contract is cloned. Tasks remain associated only with the original active contract and its version. The cloned contract does not contain any tasks by default. Users can create, edit, and delete tasks independently within the cloned contract without impacting tasks in the original contract.