Multiple UI Policies on Same Field Not Working as Expected
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2018 11:13 AM
NowI have multiple UI Policies on the same field, and I cannot get them to work the way that I want. It is my understanding that the one I want to "override" (or take precedence over the other should be the larger Order number).
So, here is my original UI Policy that was working fine. Basically, it hides my approver field from sc_req_item when the approver field is empty. This UI Policy has an order number of 100.
Now, I am trying to add a new UI Policy. There is one situation in which the Approver field is empty that I want to show it. Not only do I want to make it visible, but I also want to make it editable (basically, in part of a workflow, if the field is blank, the RITM is being assigned to a group that needs to populate it). The order number I use for this is 200. However, it doesn't work. It does, in fact show the field in this scenario, but it is Read-Only so I cannot edit (and I am in the group it is being assigned to). Here is what that UI Policy looks like:
I did also search for any other UI Policies on this field, and could not find any.
Can anything see what I am doing wrong? How can I accomplish my goal?
Thanks
- Labels:
-
User Interface (UI)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2018 06:51 AM
If the UI Policy isn't behaving as expected, then I would deactivate it entirely and put an onLoad client script in place instead. This way, you can put in the appropriate if/else statements to determine, based on what is found on the form, how it should show/hide/make read only the field.