Making field(s) mandatory when changing sc_task to "Closed Complete"

MWright1
Giga Guru

Hi all,

I have a requirement that 2 fields be made mandatory before users can set the catalog task to Closed Complete.

I created a client script to handle the UI component.  This works just fine, with one huge exception:

When users change the state via the drop-down option, the Client Script does not kick in and they are able to by pass the validation.  How can I make sure that the validation rule is applied regardless?

find_real_file.png

Thanks much.

M

1 ACCEPTED SOLUTION

chrisperry
Giga Sage

You will need to implement the logic server-side to make sure the validation rule is applied regardless. So you could use an Abort business rule, something like below should work (replace Transfer reason & Short description empty field conditions with your fields accordingly):

find_real_file.png

find_real_file.png

If this answer is helpful please mark correct and helpful!

Regards,

Christopher Perry

If this answer is helpful please mark correct and helpful!

Regards,
Chris Perry

View solution in original post

8 REPLIES 8

chrisperry
Giga Sage

You will need to implement the logic server-side to make sure the validation rule is applied regardless. So you could use an Abort business rule, something like below should work (replace Transfer reason & Short description empty field conditions with your fields accordingly):

find_real_file.png

find_real_file.png

If this answer is helpful please mark correct and helpful!

Regards,

Christopher Perry

If this answer is helpful please mark correct and helpful!

Regards,
Chris Perry

Thank you so much!

Hi Christopher,

The Abort action flag did not work for me.  It still saved it even though the message did show up.  

Thoughts?

M

Hi Christopher,

The Abort action flag did not work for me.  It still saved it even though the message did show up.  

Thoughts?

M