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

Customising the User Interface

Eddy_Hutchins

Hi,

I'm just interested in making a number of small customisations to the user interface, a number of these related to displaying search results.

- I'd like to include the ability to display the 'edit' icon in search results for a document where the user has relevant permissions (similar to what is displays in the cabinet view). Is it viable to simply copy the code that displays the icon in the cabinet view into the 'showObjectAsHitForCSV.shtml' file?

- I'd also like to change the default column of 'Last Modified By' to 'Owner'. Is this again viable to just change the global variable returned in the search results (eg changing globals.MODIFIED_BY to globals.OWNER)?

- The last change I wanted to make was to hide the 'delete' and 'remove' buttons for users with the 'editor' permission. Simply so they can 'edit' but not actually get rid of a document (leaving this for owners, etc). As you cannot directly change the settings for editor, contributor, etc. Is there a way to check within the 'commandBar' shtml page whether a user is a editor or not and simply set the delete button value to null? Eg, if(user=editor)?

I've looked into ways to achieve these, I was just curious as to whether there is a simpler way I'm just missing.

Thanks in advance!

Find more posts tagged with

Comments

Christopher_Parratt

Displaying the edit button in the search results should be relatively straight forward and what you've suggested should work.

Changing the Last Modified By column to Owner, though, isn't as simple as changing the global variable. It is actually fairly complicated. You are on the right track with the delete and remove buttons but the logic check should be done in the button templates themselves, not the commandbar templates.

Eddy_Hutchins

Hi Christopher,

Thanks for your response, I appreciate your help.

In regards to the delete button, could you provide and example of the code that check the users permission status, or point me in the direction of where I can find this?

Cheers,

Christopher_Parratt

essentially, what you need to do is check to see if the user is a Publisher (which is determined by whether the person can change the policy of an object), rather than the default, which is a check to see if the user is an Editor OR Publisher:


     <-    COMMENT OUT THIS
<ISPECT>if(!isAllowedChangePolicy())        <- ADD THIS
   <ISPECT>buttonURL=null</ISPECT>
   
   <ISPECT>buttonTooltip=i18n.getTranslatedTemplateText("Globals.NOT_ALLOWED_DELETE_TOOLTIP", getTypeReadable())</ISPECT>
</ISPECT>

Eddy_Hutchins

Thanks, that's exactly what I was looking for.

Appreciate it,