Making Worknotes mandatory when changing assignment group in any state of catalog task .

Chaithu3 · ‎12-21-2020

VERY IMPORTANT.. URGENT..!!

Whenever an assignment group is changed in any state(i.e. open , work in progress , blocked , pending , onhold , close complete , close incomplete , close skipped) worknotes should be mandatory . User should provide reason for assignment group change.

Please create a new new business rule on Catalog Task table(sc_task ) which runs on update call .
Below are the filter condition for BR
State is Anything and Assignment group changes
worknotes should be mandatory.

ANYONE PLEASE HELP ME WITH A CODE IN BUSINESS RULE

@Ankur Bawiskar @Pradeep Sharma

P-Rudenko-SN · ‎01-06-2021

So let me explain to you what my first script does. The code is triggered, once you set the NEW value into the assignment group. It checks the following:

IF the new value of 'Assignment Group' is different than the old value (the one was there when the form is loaded) AND the 'State' field is 'Open/Work in Progress/Pending' then it makes the 'Work notes' field mandatory. Please NOTE: if you changed the assignment group, set the status to 'Open/Work in Progress/Pending' and the work note became mandatory, then IF you do not submit the for but try to change the state to not of these there above (let's say 'Closed complete'), then, OF COURSE, the work notes will REMAIN to be mandatory because the 'Assignment group' is still other then it was when the form is loaded.

You cannot expect the 'work_notes' field to be set back to the optional if you change the state to another one BUT the Assignment Group field contains the new value. You have to save the ticket and afterward change it to the new state. The client script is constantly checking the assignment group field. This is its nature, otherwise, you can't control the change of assignment group field. I hope it now finally makes sense.

View solution in original post

Sourav16 · ‎12-21-2020

Hi Chaithu,

Yes all the use cases would be fulfilled with that UI policy.

@Pavlo Rudenko yes you are correct the dictionary attribute should have extended_operators=VALCHANGES;CHANGESFROM;CHANGESTO to show that option.

Thanks

Sourav

Chaithu3 · ‎12-21-2020

Hi Sourav,

could u please expand this ?

extended_operators=VALCHANGES;CHANGESFROM;CHANGESTO to show that option.

Sourav16 · ‎12-21-2020

Hi Chaithu,

Please go with the onChange client script which @Pavlo Rudenko has provided in his reply that should solve your issue.

Thanks

Sourav

Sourav16 · ‎12-21-2020

Hi,

This extended_operators=VALCHANGES;CHANGESFROM;CHANGESTO is a dictionary attribute which will show changes from changes to in the filter. But adding this won't work i have tried it go with the onChange Client script.

Thanks

Sourav

Chaithu3 · ‎12-21-2020

But i need that to apply it for all sc_task with the conditions which ive given on top.

i guess client script only works for client side what about server side ?