Why would a UI Policy work as admin but not as a user?

[DrewW]

I added functionality so that when certain users create a template then can cause it to show up as a module. The issue that I am having is I created a UI Policy to show and hide the two extra fields that they need to fill out. But for some reason the UI Policy only works for me as an Admin. It does not work for a normal user. My first thought was there was a view involved and the user's view did not have the fields, but I can not locate any views for the sys_template table.

I have tried several things and none of them seam to have help.

If anyone can offer any suggestions I would be most appreciative.

Drew

[Mark Stanger]

My guess would be that there is an ACL restricting access to some of the fields that you're working with on that table. You may try opening up the ACLs and see if that makes a difference.

[DrewW]

Thanks for the response.

My only issue with that is that I just created one of the fields that I am trying to hide and show and the default on the table is public has read access, so I should at least see the field I created I would think.

I disabled the read and write ACL's for the roles field and it did not help.


Drew

[DrewW]

I also just realized that when the form loads you do not see the fields at all. What I mean is just before the UI Policies apply there is always a little lag and you see all of the fields, then the UI Policies kick in and the go away. When logged in as the user this does not happen. Its like the server is just not sending the fields to the client to render them. Which makes me think even more it is a view issue, but I can not find any views for the table (sys_template).

Drew

[DrewW]

Ok, now I am really confused...

I disabled the UI Policy all together and now I can see the roles field but not the new field I added...???