UI Policy best practices to avoid conflicts

Darlene York
Tera Contributor

Good Morning,

I was wondering what the best practice is for writing multiple ui policies on 1 field. 

Example:

Request type is New

Show fields a, b, c

Hide fields d, e, f, g, h, I , j

 

Request type is Modify

Show fields, d, e, f, g

Hide Fields a, b, c, g, h, I j

 

Request type is Retire

Show fields I, j

Hide a, b, c, d, e, f ,g, h

 

I’m trying to avoid confusion with my policies.

 

I wrote 3 policies New, Modify and update.  I listed all the fields on each policy and set the read only to true, mandatory to false except for fields that are required on tasks and visible to either true or false based on the requirement.  I also set Clear the variable value to false and uncheked the Reverse if false.

 

Is the advisable, is not what would be the best approach?

 

DarleneYork_0-1676468031172.png

 

Thank you

 

1 ACCEPTED SOLUTION

Basheer
Mega Sage

Hi @Darlene York ,

The approach which you've used is absolutely fine.

If there are conflicts directly you will get a red dot next to the ui policy action. In your screen shot there is no red dot it means there is no conflict.

 

Please hit like button if my suggestion has helped you in any way.
Please mark correct if my response has solved your query.

Cheers,
Mohammed Basheer Ahmed.

View solution in original post

3 REPLIES 3

Basheer
Mega Sage

Hi @Darlene York ,

The approach which you've used is absolutely fine.

If there are conflicts directly you will get a red dot next to the ui policy action. In your screen shot there is no red dot it means there is no conflict.

 

Please hit like button if my suggestion has helped you in any way.
Please mark correct if my response has solved your query.

Cheers,
Mohammed Basheer Ahmed.

Basheer,

Thank you so much.  I feel so much better now.

Have a nice day.

Where does the red dot show up? I am not sure I have ever seen a red dot in the next experience for conflicting ui policies