Why do workflows and tasks only cancel when RITM state changes to 'closed incomplete'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2018 06:10 AM
I found this business rule running on the task table: Cancel Workflows Upon Cancellation
Whenever a records state changes to 'closed incomplete', it ends the workflow and all the tasks. This makes sense. However, if you were to mark the RITM to 'closed complete', the RITM would be deactivated, but the workflow and tasks would remain open.
Can anyone help me understand why manually changing the state to 'Closed Complete', or 'Closed Skipped', wouldn't act the same way as 'Closed Incomplete' out of the box?
Thanks!
- Labels:
-
Instance Configuration

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2018 06:34 AM
There are some business rules on task table that auto closes the task or the child records on closure of parent record. You can extend those to apply for RITM's.
To answer your specific question, I am not sure if that is the OOB behavior. Have you tried that in a fresh developer instance?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2018 06:42 AM
Yes, these were my results from a personal dev instance:
1) manually setting RITM State to closed complete inactivates RITM, but workflow and tasks stay open
2) manually setting RITM State to closed incomplete inactivates RITM, workflow cancels, and tasks close

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2018 06:44 AM
Hi,
Ideally, this should cancel the workflow but it will not cancel the task as i know.
thanks,
Ashutosh Munot