How to hide unused functions in xECM menu and enable Reminders

for_testing

I have a couple of questions regarding the customization of the xECM application (classic view). I would appreciate your guidance on the following:

1. Is there a way to hide unused functions (e.g., Discussion, Forum, partners database) from the xECM menu? I want to prevent users from accessing functions that are not currently usable.
2. How can I enable the Reminders function in the xECM menu? I saw it listed, but I'm unsure how to use it. Is it the same as the "Follow-up" function mentioned in some online documentation?

I've searched for online resources and documentation, but haven't found any relevant information. Your assistance, suggestions, or references to documentation would be highly valued.

appuq

The Enterprise Menus are kind of hard-coded (they come from Oscript) to hide them it is difficult if you are not an Oscript Programmer. However, since it is classic you are in luck.CS comes with something called an Active View and I believe in the examples section of it it shows you how to customize Personal, and Enterprise menus. If it won't cut it still and older way to do this was to use a "Global Appearance" loaded and then you would use simple JQuery logic to hide those menus. None of this will prevent the actual execution of the command if someone has say book marked it.If that is a problem that is where Oscript comes in.

If Active View is an option I would use that for your second question.Reminders looks very similar to follow-ups so it may be a new wine in …

GregPetti

Agree with everything Appu said. Couple of additional points:

If you create an ActiveView, there are some default templates you can "Function Menu Sample" which provides several examples of how you can delete options.

One slight disagreement is that it is possible to block options using something called a request override. This is a bit more advanced but there is also a default template that provides some help with this. Probably not necessary for your requirement so I'm just being a bit pedantic.

Alfonso Scoppetta

I just want to add a valid alternative that is simple and easily customizable even if you're not an Oscript programmer, which is to use the Module Suite that can be used also to customize an object's functions menu.

Module Suite Content Script can be used to perform changes to the standard object function menus, by adding new options or removing existing ones. This feature is enabled by defining a Content Script that “filters” the object menu and performs the desired modifications. The “amgui” service provides a user-friendly interface to perform modifications to the menu object.

The following example shows a menu customization script that includes:

• fetching the original menu
• filtering the original menu entries (removing entries that match a specific expression)
• adding a divider row to split menu entries
• adding a submenu
• adding a custom menu entry to the new submenu
• returning the modified menu

E.g.

Mily

The exact steps may vary depending on the specific version of xECM you are using and the customization options available within your organization's setup. clipping path image editing service If you're unsure about any step, consulting the xECM documentation or contacting technical support for assistance is recommended.

GregPetti

FYI, All content Server /xECM instances now include ActiveView for free. The method to achieve these changes hasn't changed in in years so you should easily be able to make these changes without any OScript customization.

Here are a couple of blogs on ActiveView. (The second one builds an example)

https://www.ravenblackts.com/blog/deep-dive-how-to-create-custom-sub-tags-for-webreports-and-activeview-0

https://www.ravenblackts.com/blog/a-simple-activeview-example

BLaP

Another solution to consider is the Fastman Access Manager for Extended ECM. It allows you to configure rules to block specific content server functions by group, category, classification, and location regardless of your permissions. It doesn’t hide the function. When a user (classic or Smart UI) attempts to access the function, they will get a custom error message. Even with Active View, users can still get to the functional URL if they are experienced content server users. For example, we use AM for our software download portal and keep the users only in the Smart UI essentially blocking all classic functions. Others use an Access Manager rule to lock down content server in a location (i.e. read only) during a migration instead of changing user permissions. There are many interesting business scenarios. https://www.fastman.com/access-manager