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; } } }

Customization Query : enable a link to master role

System

The above code if updated in UI_custom.xml removes the Search link from CCPRO and it doesn't appears to all roles , if i need to make this link enable to only master users what needs to be done.

can anyone help in this .....

Babu.....

Find more posts tagged with

Comments

Migrateduser

code was not appearing properly (remove greater than symbol) here it is ....................

Adam Stoller

[html]

[/html]The above code if updated in UI_custom.xml removes the Search link from CCPRO and it doesn't appears to all roles , if i need to make this link enable to only master users what needs to be done.

can anyone help in this .....

Babu.....

Unfortunately (at least for pre-671) - modifying OOTB menu items to be role-configurable is a bit messy - you have to essentially delete the menu item (as you did above), then re-create the menu item and include an operationId (check the syntax / capitalization) - and then you have to modify the roles_custom.xml to specify the accessibility of the menu item for each role.

For 671 - I'm not sure if OOTB menu items are easier to configure in this respect, but I think some of them might be configurable based on the flex-role configuration options.

If not, the process is similar - to the pre-671 process, you would need to delete and re-create the menu with an operationId - and then you would need to specify the menu in the userops_custom.xml (or something like that) after which the option would appear within the flex-roles customization screen and you can define which roles have access to that option from there.

Adam Stoller

...code was not appearing properly (remove greater than symbol) here it is ....................

In order to get code to show up in the forums - you need to surround it with

[html]...[/html]

tags, or modify each occurrence of '

' with '

<<x>

' which, if you want to maintain indentation and such you should do within

[code]...[/code]

blocks.

The use of HTML blocks is simple, quick, and easy.
The use of CODE blocks is not as simple, quick, or easy, but does allow for additional formatting within the block - like colorization highlighting[html]
too
[/html]

<if_this_were_code>
    <this_would_be>too</this_would_be>
</if_this_were_code>

And don't forget to click on Preview Post before submitting it.

chicka

Hi All,
I am trying to control delete menu item using roles. I approached with the suggestions made in this thread.

Below is my change:
in ui_custom.xml --> /local/config/lib/content_center/customer_src/etc/conf/customer
I added below
[html]

[/html]

And in userops_custom.xml
I tried placing
[html]

[/html]
under custom-operation tags.
Now I could see this newly added item in "manage roles" section in Administration tab in Content centre UI after successful build.
However enabling/disabling the newly added item doesn't make difference in UI?
Could you please highlight what exactly I am missing in configuring my expectation? Am I in wrong approach ?

Adam Stoller

Hi All,
I am trying to control delete menu item using roles. I approached with the suggestions made in this thread.
...
Now I could see this newly added item in "manage roles" section in Administration tab in Content centre UI after successful build.
However enabling/disabling the newly added item doesn't make difference in UI?
Could you please highlight what exactly I am missing in configuring my expectation? Am I in wrong approach ?

Re-read the posts in this thread - you only did one-part of a two-part change in the ui_custom.xml file - you deleted the OOTB option but never added your own custom option.

However, if you're using 6.7.x (with FlexRoles) and want to control which users have access to the OOTB Delete menu command - you should just consider creating custom roles (based on the OOTB roles), configure them to [not] have the Delete option and use your custom roles instead of the OOTB roles for all the branches where you want this custom setting to be in effect.