Restrict the "edit" button of outage for users in change request form.

[thaduri sai]

Hi Team,

We have to restrict the edit button for users - when the change state changes to "Assess" or "Authorize". How to acheive this?

Thanks,

Saikrishna

[Gayathri Ramakk]

Use a UI policy or Client script to hide the edit button when the state is "Assess" or "Authorize"

Client Script for reference:

if (g_form.getValue('state') == 'Assess' || g_form.getValue('state') == 'Authorize') {
// Hide Edit button logic here

g_form.setVisible('edit_button', false); // Hides the button
}

[Nikhil Bajaj9]

Hi @thaduri sai ,

You can use ACL to hide this UI action.

Regards,

Nikhil Bajaj

[Dr Atul G- LNG]

Hi @thaduri sai 

I’ve worked as a Change Manager, so let me share my thoughts on this. I'm not sure why you're looking to hide the "Edit" button, especially in the Assess or Authorize states. In practice, during the CAB (Change Advisory Board) meeting—especially in the Authorize state—there might be questions or suggestions that could lead to the change being marked as an outage.

[TomShek]

Hi Saikrishna, I guess the requirement is to restrict "who" to edit the change request form. During "Assess" and "Authorize", some managers should still able to provide their input and make this ticket move forward. Is it?