19 views

Description

The user had a requirement with their Release records to have a workflow associated. Within the workflow on the Release record, there are some approvals needed. Additionally, a Normal Change Request is generated, and there are some separate approvals on the child Change Request.

It was noted that occasionally, the same group, group 'A', was set as an approval group on both the child Change Request and the parent Release record. This is when the issue occurred.

Cause

The rm_release table did not have the "close_states" attribute set on the dictionary override for its state field.

Resolution

As mentioned above, the rm_release table did not have the "close_states" attribute set on the dictionary override for its state field. 

As such, they can and should be added to resolve the issue:

  • /nav_to.do?uri=sys_dictionary_override.do?sys_id=3aea7d910a0a0bd5001ed3913215ab45

Previously, when the state value of the Release record was being set to '4', Task Active State Management recognized this is a close state, which is the default from task (3, 4, 7), so the rm_release record was flagged as inactive/closed.

Close states for rm_release were modified to be set to 3 and 7, leaving a transition to '4' to not cause the rm_release record to close unexpectedly and thus set the approvals on it to "No longer required".

Article Information

Last Updated:2020-06-12 10:15:32
Published:2020-06-12