On Wed, Aug 6, 2008 at 11:28 AM, Brian York <-> wrote:
> Anybody now how I should go about removing the Documentum menu pick from > the main menu. > > In some case I want to start Editor without the documentum menu. > > I have tried using the menu_delete but it tells me the menu doesn't exist. > I'm not sure where or how the Documentum menu is loaded. >
Hi Brian, I'm assuming you want Documentum integration, just no menu pick, in which case the following won't help:
Disable Documentum integration by editing feature.cf. Obviously you don't want users to have to do this, but you can use a batch file, different batch files, really, to copy a Documentum enabled feature.cf into the local custom folder of a given user or a Documentum disabled feature.cf depending on the task/s they are performing. If you need to determine users by groups etc., it is still do-able, but obviously with lots more batch file coding or some other tricks (which custom folder to use, for example).
More along the lines of what you are probably hoping for, removing the Documentum menu only but leaving the functionality:
I have never done this so I don't know how it will work (for example, will you have to find where Documentum is setting a menu callback or hook and modify it since those menus are getting set and reset throughout a given session), but I did run into conflicts with Documentum's menu setting code while trying to load my own menus on Editor startup. I resolved this by setting the environment variable APTRC and pointing it to an ACL stored in the scripts subfolder of the custom menu. Doing this resolved the timing issues. *Maybe* if you use this var and your menu_delete command, you'll be able to prevent the menu from showing up on load. After that is anyone's guess.
(But tell us if you succeed and what the ongoing behavior is. I'm curious!)
I believe that the fact this is a feature rather than an option is significant in this case. As I remember it, the feature.cf file is read long before the startup.acl is read. I think that Paul's idea that you need to have alternative feature.cf files is the better approach. John Dreystadt Software Development Director Arbortext - PTC 734-352-2835 -
Somewhere in the core code, I know that the adapters work differently than other menu items.
You can do a quick test of Paul's idea. Create alternative custom directories, one with no feature.cf and one with a modified feature.cf that turns off the Documentum adapter. Then you just need to switch the environment variable aptcustom to control which one you get.
John Dreystadt Software Development Director Arbortext - PTC 734-352-2835 -
It will turn of the menu if I change the settings in the feature.cf file. I will just change my startup script to copy in and out the correct file like Paul suggested. I just was looking for a cleaner method.