Prevent user to reject approval from SOW

swapnilsoni
Tera Contributor

Hello All,

 

There is a requirement to prevent user to reject approval from related list without putting the comment of rejection in native ui and SOW both.

So in native ui i created oncelledit client script to add one popup to put comment when someone rejecting from list view and mapping it in approval comment. (it is working fine)

But in SOW this client script is not working. so i make the modification in sys_ux_list table for My approvals and All approvals. (it is also working)

Now the issue is, in SOW only if someone open change request or RITM and in related records they open approvals and from there if they rejects it, then it is rejecting. so how can i prevent user to reject approval permanently from list view in SOW. 

 

Please suggest some solution. i am struggling for this in last week. Thanks in advance.

8 REPLIES 8

Nishant_Shelar
Tera Expert

Dear @swapnilsoni,

The most foolproof way to handle this is with a Data Policy, since it runs server-side and completely prevents users from bypassing the rule via the SOW list view.

Just create a new Data Policy on the sysapproval_approver table with the condition set to State is Rejected. Once you save that, scroll down to the related list and add a Data Policy Rule to make the Comments field mandatory.

If someone tries to double-click and reject an approval from the list view without a comment, the system will instantly abort the update and throw a Data Policy Exception error on their screen.

hello @Nishant_Shelar ,

 

TAB is  not approving Data policies and ACLs. apart from that any solution that might help?

Then go back to the person requesting this and tell them it can't be done. 

What is the reason for not allowing data policies? They must have given you a reason that it's not allowed? 
You can also just disallow list editing, but TAB will probably also be against that?


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

there might be some integration which may affect it thats why they are not accepting Data policies