Assistance with UI Policy Conditions for Catalog Item Permissions Request

Austin20
Tera Contributor

Hi Everyone! I'm having some difficultly figuring out the best route to go for getting this UI policy to work properly. I have a catalog item setup so that users can request access to documents in our system. I multiple check box variables for the types of documents. Then based on what types they select; a drop-down box will show asking them what type of access they need. Then the request goes to the document owners for approval. 

I'm getting hung up on the UI policies. I can get the drop down boxes to be hidden until they check the box. However, when they change the "select which document type group you need access to", the drop down still appears. In the second screenshot 113756, you can see that I have HR picked but have a student financial aid option still showing. If I switch back to enrollment, it will then clear the variable and make it disappear but seems like I'm missing a step. So I think the catalog item still things it's checked even though I have changed to a new group. When I switch back to enrollment it does show unchecked. 

I added some screenshots that I have on the UI policies to show how I had it setup currently. Any thoughts or suggestions? I thought of going the script route but feel like this should be possibly with the UI policy though.

Thank you!

AustinB

1 ACCEPTED SOLUTION

Sandeep Rajput
Tera Patron
Tera Patron

@Austin20 From screenshot 114343, it is evident that there is a UI Policy which makes the onbase_access_em_sfa_permissions_selection field mandatory. Can you check if on UI Policy Show EM SAF Perms Selection has "Reverse if false" checkbox checked. Also, add more conditions in condition builder in Show EM SAF Perms Selection UI Policy which if not met will make the field non mandatory and ultimately hidden.

 

Please be informed that any Mandatory fields on the form can's be hidden via a UI Policy until it is set to non mandatory.  

View solution in original post

5 REPLIES 5

@Austin20 Glad to know that adding more conditions ultimately did the trick (suggested the same in my very first post.).

 

Regarding the evaluation of conditions across multiple UI Policies, UI Polices are usually evaluated on the basis of their order, UI Policy with least order executes first.