Issue with MRVS catalog UI policies

[Suryansh Verma]

Hello Community,

I am facing an issue with applying catalog UI policies in MRVS.

My MRVS has 4 variables:

1- Project Code

2- Activity

3- Project Code Test

4- Activity Test

The requirement is to show Project Code Test & Activity Test as mandatory when Requested for and Opened By is the same and show Project Code & Activity when Requested for and Opened By are different.

The condition works fine, but the other requirement is to make Activity Read-Only and non-mandatory when Project Code has any value i.e. not empty, and vice versa to make Project Code Read-Only and non-mandatory when Activity has any value i.e. not empty

Activity Test Read-Only and non-mandatory when Project Code Test has any value i.e. not empty, and vice versa to make Project Code Test Read-Only and non-mandatory when Activity Test has any value i.e. not empty.

To achieve this I applied 4 other UI policies to fulfill this but now after adding the row in MRVS if I click on the edit row, it makes the fields Mandatory and non-read-only.

I have tried changing the order and also the UI policy script but one or the other UI policy does not work when editing the row.

Any help would be greatly appreciated.

[Brad Bowman]

Sorry, I got lost reading all of those vice versas and requirements trying to think of the order.  I think this is an excellent opportunity to scrap all of the UI Policies and write one Client Script that does the same.  This way you can see, organize, and have complete control over the structure of the if statements, elses, and all the combinations therein.