Multiple UI Policies on the same field

[lisa_ong]

Hi everyone,

Couldn't find much detail around this on the wiki or specifics that we can relate/use in the community, so I'll ask the question.

Is it possible to have more than one UI policy run on the same field?

For example, we have a field called Asset Tag. We have two policies running on it, each with a slightly different condition to the other.

UI Policy 1:

Company = X

OR Company = Y

AND Device class = ABC

AND Device ownership = Corporate (this is the differing condition)

AND Asset status = one of these: 1,2,3,4 etc

Make Asset tag field visible and mandatory

Run order: 100

UI Policy 2:

Company = A

OR Company = B

AND Device class = ABC

AND Asset status = one of these: 1,2,3,4 etc

Make Asset tag field visible and mandatory

Run order: 101

Originally the run order on both was 100, but because of the conflict error that appears, we have changed it to 100 and 101. The problem now is that Policy 1 works when you re-open the record, but Policy 2 does not work.

[Olorunfemi]

Very helpful tip.

[randrews]

Why do this?

if you use the or function at the top of the ui policy settings you can setup complex or conditions and define those requirements in one policy instead of worrying about conflict...

the trick to remember is the or button int he conditions adds an or to that set of conditions.. the or at the top adds a more complex or that should do exactly what you want.

[lisa_ong]

Hi guys, thanks for your responses. In the end what I did was set both UI policies to have the same run order and selected Reverse if false on one only and not on both.

So the policies looked like this: -

UI Policy 1:

Company = X

OR Company = Y

AND Device class = ABC

AND Device ownership = Corporate (this is the differing condition)

AND Asset status = one of these: 1,2,3,4 etc

Make Asset tag field visible and mandatory

Run order: 100
Reverse if false: False

UI Policy 2:

Company = A

OR Company = B

AND Device class = ABC

AND Asset status = one of these: 1,2,3,4 etc

Make Asset tag field visible and mandatory

Run order: 100

Reverse if false: True