- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2016 09:38 PM
Hi Guys, I have an issue where another admin has created a UI action (button) called 'form_button' and I am unsure how he has controlled its visibility.
Currently I can see 'form_button' if I impersonate a user with 'Role A' but I cannot see it when impersonating users with 'Role B' or 'Role C'. Id like to change the visibility to include 'Role C'.
In the action itself, the UI action visibility section is empty, and there are no roles specified in the condition or script sections. For this form there is only 1 view and I cant find any client script that is referring to 'form_button' either.
Where else should I be looking? Why does 'Role A' see the button but not 'Role C'?
Many thanks in advance.
- Ben
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-23-2016 07:57 PM
Thanks for your help guys. It seems this was an OOB UI error. This was fixed after upgrading to Helsinki.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2016 10:11 PM
HI Benl,
Do you have anything in the Condition field? Can you please clear it and test it again?
Also, Are you running Domain separation instance?
Thanks
Srinivas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2016 10:18 PM
Hi Srinivas, Thanks for your reply.
As mentioned above there are no conditions set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2016 10:12 PM
Hi Benl,
If the UI action is new , submit or delete then you should look out for the ACLs.
For eg: for your role if you don't have the delete ACL configured to true then you can't delete a record likewise for write and create ACL.
So, you can look out for the ACLs.
Hope it's helpful.
Thanks and Regards,
Vikas Malhotra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2016 10:22 PM
Hi Vikas, Thanks for your reply.
Yes, the purpose of this this UI action is to move a work order state from 'Draft', to 'Pending assignment'.
I have Checked the ACL's relating to work orders, and all user roles have access to create, write and delete a work order.