nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Per role authorization for built-in menu items

brizrobbo

Hi Folks,

I'm trying to do a pretty simple thing (you would expect!): basically I want to disable some "built-in" menu items for the author role (more specifically, the ->edit, ->copy and ->edit, ->copy to... links).

However, I read in the doco that the documented per-role authorization method (i.e. using operationID with a matching entry in userops_custom.xml) can only be applied to new menu items that you create for your own customized operations. It cannot be applied to built-in menu items.

I did think of first deleting the menu item, and then creating my own customized "Copy" menu item, but this seems a bit dodgy??

Therefore, the question is:

Is there a documented way of controlling access to the "Copy" menu item (which is a built-in) by role?

Any help is appreciated.

Find more posts tagged with

Comments

Jcse

Hi Folks,

I'm trying to do a pretty simple thing (you would expect!): basically I want to disable some "built-in" menu items for the author role (more specifically, the ->edit, ->copy and ->edit, ->copy to... links).

However, I read in the doco that the documented per-role authorization method (i.e. using operationID with a matching entry in userops_custom.xml) can only be applied to new menu items that you create for your own customized operations. It cannot be applied to built-in menu items.

I did think of first deleting the menu item, and then creating my own customized "Copy" menu item, but this seems a bit dodgy??

Therefore, the question is:

Is there a documented way of controlling access to the "Copy" menu item (which is a built-in) by role?

Any help is appreciated.

Hi

Check file roles.xml at location [\\iw-home\conf\roles].This file have access defined for the TS functions corresponding roles.

I have not tried this,but try by commenting the entry of particular menu item (let's say copy) defined under a particular role.
Reset the server.

May it work ?

sample.xml

new_report_2.rptdesign

brizrobbo

A-ha! Well, I'm a big bozo! Obviously I went to sleep for that bit for training Smiley Surprised

. When you suggested modifying

roles.xml

directly, I thought: "that can't be right. There must be something within the UI that modifies this file??". And there is: it's called "Manage Roles". How stupid....this is a clear as! I just have to switch those bits off for the author role, and voila, it's off.

Now, all I need to learn is how to get more granular than the choices that are on offer in the "Manage roles" function. For instance, how do I disable the "Get Latest" link on the "More" menu when you "List your bookmarks" for authors only. Any tips here?

brizrobbo

Just an update: seems like the concept of using the roles management function to control access to in-built TS menu items is slightly more complicated than I anticipated. You can obviously control access to certain menu items (as listed in the "Manage roles" tab). But they don't list ALL the in-built functions. For instance, I can control access to "->Edit, ->Copy" by selecting or de-selecting "Copy Files and Folders" check box in the "Files, Forms and Folders" section of each respective role. But there is no selection for "->Edit, ->Copy To...".

Support are looking into it for me. I will keep you posted.

brizrobbo

Further update:
IWOV (or should I say Autonomy) support got back to me. The role configuration to change in order to disable >Edit, >Copy to... is the "Update workarea" check box (apparently because ">Copy to..." is a "workarea" function). Anyway, this also disables "Get latest" (as you would expect). Unfortunately you are unable to de-couple these two functions. I have asked for a change request to be created in order to do this (as I have a requirement for one and not the other).

Conclusion:
It seems that this is a bit of a limitation with customizing the UI? You cannot set operationID's to control role access to "built-in" menu items. The only way to do this is by setting configuration items in the role management screen. And, therefore, you are restricted to what setting those configuration items does.

Any comments?