Hi @ROSHINIB
Yes, it is possible to restrict (freeze) attachments in Service Operations Workspace during specific approval gates.
This can be achieved by creating Before Insert and Before Delete Business Rules And ACL as well on the sys_attachment table. In these Business Rules, you can check the state of the parent record and restrict users from inserting or updating attachments when the record is in the “Authorize” or “Authorize Implementation” states.
Since attachments are always stored in the sys_attachment table, restricting insert/update operations at this level will effectively prevent users from adding or modifying attachments during the specified approval stages.
so please refer the below logic this will help you.
Note: please modify this code according to your requirement its just a reference. and also you can do for the change task table as well.
// Add your code here
if (current.operation() == 'insert') {
var grChange = new GlideRecord('change_request');
if (grChange.get(current.table_sys_id.toString())) {
if (grChange.getValue('state') == 'Authorize Implementation' && grChangeDet.getValue('state') == 'Authorize') {
gs.addErrorMessage("You can not add the attachment.");
current.setAbortAction(true);
}
}
}
if (current.operation() == 'delete') {
var grChangeDet = new GlideRecord('change_request');
if (grChangeDet.get(current.table_sys_id.toString())) {
if (grChangeDet.getValue('state') == 'Authorize' && grChangeDet.getValue('state') == 'Authorize Implementation' ) {
gs.addErrorMessage("You can not delete the attachment.");
current.setAbortAction(true);
}
}
}
If my answer has helped with your question, please mark my answer as accepted solution and give a thumb up.
Thank You
