Skip to main content

๐Ÿคบ Hiding Links in the Right-Side Navigation Menu of Application Records

๐ŸšงSlate Adventures In Progress๐Ÿšง
This page will be updated regularly as we learn of new Slater contributions so be sure to check back. ย  Also, if you notice any broken links, content in need of updating, or other ReSources you would like to share, you can leave an anonymous comment below. Even better, we would be thrilled to thank you personally and (with your permission) give a community shoutout. Contact us at resource@reworkflow.com.

Important Notes:
ย 
The recommendations below have been tested in a few Slate instances and proved to work as of the time this article was published/last updated. However, every local context has potential differences that could cause unintential behaviors. Additionally, Technolutions ongoing deployment of Slate enhancements could potentially result in disrupting this "Slater hack". It isย highly recommended to experiment in your Slate test environment first and to proceed with caution in production.
Additionally, as Chase Matzinger points out (๐Ÿ” requires login) along with what ReW has also experienced, this workaround does not prevent the original default dashboard and data from flashing briefly upon page loading before the JavaScript runs. This could raise some security concerns for hiding sensitive / personal identifiable information.

The Why

The right-side navigation menu when on an application record in Slate provides some key delivered out-of-the-box features. However, there currently is no functionality for customizing these links nor is there a way to control who has access to them. For example, at the time of this article's publishing, the "Application Update" permission allows for access to the "Workflows" menu where a user can then edit which workflow bin an application is in. Additionally, the "Person Impersonate" permission allows a Slate user to access both theย  "Impersonate > Applications" and "Impersonate > Status Page" links, but there are reasons why a staffer should only need access to the student's view of the Status Page (highly recommended read:ย ๐Ÿง‘โ€๐Ÿ’ป Impersonating Appl... | ReSource).ย 

โœ…Feedback Request: Please lend your vote (and comment if you are inspired) to:

The How

  1. If you have not done so already, create anย Customizing Records > Dashboards (i.e. Type = Record | Base = Application").

  2. In the "Edit Dashboard" tab, click the "Source" button in the editor ribbon.

    Dashboard.png

  3. ย Insert the following script based on your intended use case:

    Hiding both Impersonate > links:
    <html xmlns="http://www.w3.org/1999/xhtml">
      <head>
        <title></title>
        </head>
        <body>
         //Hide built-in impersonate links
      $('li > a:contains("Impersonate")').remove();};</script>
      [Lorem ipsum --> i.e. all of your awesome dashboard content you want to put in the body]
      </body>
      </html>
    Hiding the Impersonate > Applications link:
    <html xmlns="http://www.w3.org/1999/xhtml">
      <head>
        <title></title>
        </head>
        <body>
         //Hide built-in impersonate links
      $('li > a:contains("Impersonate > Applications")').remove();};</script>
      [Lorem ipsum --> i.e. all of your awesome dashboard content you want to put in the body]
      </body>
      </html>
    Hiding the Impersonate > Status Page link:
    <html xmlns="http://www.w3.org/1999/xhtml">
      <head>
        <title></title>
        </head>
        <body>
         //Hide built-in impersonate links
      $('li > a:contains("Impersonate > Status Page")').remove();};</script>
      [Lorem ipsum --> i.e. all of your awesome dashboard content you want to put in the body]
      </body>
      </html>

๐Ÿ“šRelated ReSources