Hiding The Browse View in a Content Server Custom View

A little tidbit today inspired by a question I was asked while running a training course last week on Causeway ECM / OpenText Content Server.

We were discussing Custom Views and how they can be used to enhance the default user experience or embed bespoke functionality into the application. I was asked if there was a way to hide the content of the folder where the Custom View is stored and my default answer at the time was no, as there is no out of the box option to do this. However in the car on the long drive home (sat stationary on the M42  to be more precise) I had an idea how this could easily be achieved.

The technical name for the area we want to hide is the Browse View, to be clear about the area we are talking about I’ve highlighted it below in a stock example I keep handy.

Option 1 : Hide It All The Time

It would be quite straight forward to just override the standard CSS styling of the Browse View elements by adding the snippet bellow to your Custom View.


Option 2 : Get Clever And Turn It On Or Off

While Option 1 achieves a purpose it isn’t the most elegant solution. It will also be a pain for you as a developer because every time you want to change your custom view you will have to use the Function Menu on the folder and go to the Configure page, or enter the developer console of your chosen browser and remove the style.

This second option gives you a nice clickable link that will toggle the viability of your Browse View.

NOTE: The following snippet assumes you are using Content Server 10 or later, as this is when inbuilt support for the jQuery JavaScript library was introduced.