UI Policy action set value not working.

[ArmegaA]

I have created in a PDI a UI Policy on the incident table that has actions to set the value of some fields to true. One is true/false one is String ( ignore the misspelling) . 

 THe actions look liek this : 

 Ii is simply a value action set value and the value is true. I have no condition. I don't understand why it is not setting the value on a random incident I picked:

 

These are newly created fields just for this purpose so they are not in any other br, uip, uia etc. I thought maybe for the true false it doesnt do a converison from string to boolean and that is why it is not populating but the string field doesnt work either.  If I try to do a script in this and just say setValue it works as always.  Is this Set Value action simply not made for this kind of logic? What is it used for in that case?

[Mark Manders · Accepted solution]

What's your use case? If you don't have any conditions, it should just be a default value, right? 

When I check on the OOB UI policy form, there is no 'set value' available. There's only 'clear the field value'. I think the 'set value' is meant for catalog ui policies, where it is available OOB.

[Ehab Pilloor · Accepted solution]

Hi @ArmegaA,

The Set value field is not meant for standard UI Policies.  Check existing OOB UI Policies where UI Policy action doesnt have that field.

You can try setting value for catalog variables.

Regards,

Ehab Pilloor

[Mark Manders · Accepted solution]

What's your use case? If you don't have any conditions, it should just be a default value, right? 

When I check on the OOB UI policy form, there is no 'set value' available. There's only 'clear the field value'. I think the 'set value' is meant for catalog ui policies, where it is available OOB.

[ArmegaA]

I started from a real use case that was checking the category and another field, and would set a true false field to true by a ui policy action like above, then I moved to a PDI just to test i could get a basic one to work. As per the second part, yes, that might be the only explanation.

[Ehab Pilloor · Accepted solution]

Hi @ArmegaA,

The Set value field is not meant for standard UI Policies.  Check existing OOB UI Policies where UI Policy action doesnt have that field.

You can try setting value for catalog variables.

Regards,

Ehab Pilloor

[GlideFather]

Ahoy @ArmegaA,

@Mark Manders was right!

The Value and Value action are related to CATALOG(!!) UI Policy, not UI Policy, and your form is in backend so it cannot use the catalog ui policy actions...

as seen below, my PDI is too slow to create a dummy record but on existing it is already evident:

CC: @Ehab Pilloor