what is the best practice in Additional approver configuration in Change Management Module

[anandkay22]

I am trying to introduce additional approvers without customization in Change Management module.

I had 2 options in mind.

One is introducing Additional Approvers custom field.

Another is reusing Group List which is coming from the task table, however, there has to be a dictionary override which is not suitable for a current situation.

But, I wanted to build a change approval flow considering additional approvers.

Wanted to understand if there is something available OOB with minimal configurations. Expecting a response. Thank you in advance.

[Dr Atul G- LNG]

Hi @anandkay22 

I worked as a Change Manager and am happy to share my real-time experience on this topic.

I agree that in some cases, additional approvers are required — for example, teams like Legal or Finance. Here's what we implemented to handle such scenarios:

• We created a custom field on the Change form called "Additional Approver" (List type).

• Only the Change Manager was allowed to add users to this field.

• Additional approvers could only be added in the 'New' state.

• At the time, we were using a Workflow, so we updated the workflow accordingly.

• These additional approvers were inserted either at the beginning or end of the approval list in the Assess state.

• If additional approvals were no longer required, the change had to be moved back to the 'New' state, where the Change Manager could modify the approvers list.

• No additional approvals were allowed once the change entered the 'Authorize' phase.

This is the approach we followed and built. It required extensive testing, as Change workflows can be quite complex — especially when handling rejections or restarts.