change management planning tab

[dcarmon99]

Do you lock down the planning tab fields after the approvals have been requested?

[Dr Atul G- LNG]

Hi @dcarmon99 

Technically, we can implement a lock-down. However, as a Change Manager, I would suggest not locking it down. During approvals or implementation, there may be a need to make updates or add points, and restricting changes could cause issues.

I understand that as per process it may not be ideal, but if we lock it completely, necessary updates or additions may not be possible.

Instead, I recommend keeping it open but displaying a warning message to users. If anyone tries to make changes after approval, a pop-up should appear informing them that changes after approval are not recommended, and they should proceed via a change or update in work notes.

[Tanushree Maiti]

Hi @dcarmon99 

This really varies depending on the client. For example, in my current project, once a change request is submitted (i.e., it’s no longer in the “New” state), all fields become read-only or locked for everyone except the Change Management team.

So it’s best to confirm the expected behavior with your business requirements.

To enforce field locking, using ACLs is recommended. Alternatively, you can also achieve this with UI Policies or Client Scripts.

[Srikanth_9]

Hi @dcarmon99,

Basically, it depends on the client business needs or requirements, according to that we need to align with the recommended approaches.

When I was part of custom Change model implementation, I need to make lock down/hide/read-only the fields which are present under the planning tab in the "State - New" itself. So, it depends on the business needs.

I would prefer you to go mostly with the UI Policies to achieve this behaviour (Note: Set the Order numbering for UI Policies correctly so that it works) it helped me while I'm implementing this functionality. 

If the provided solution is useful/working, please Accept as Solution and hit the Helpful. 

Thanks & Regards,

Srikanth Akula.