Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Hide and Show Custom Menus based on Project Access
Topic Summary: Customized Menus
Created On: 21-Oct-2004 17:48
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 21-Oct-2004 17:48
User is offline View Users Profile Print this message


Janet Ma

Posts: 115
Joined: 12-Sep-2002

Our DOORS 6R1 client is on a shared server and therefore, our DXL (both Telelogic scripts and our addins folder) is in a shared folder too.

We have multiple projects on the same database, but I would like to display customized scripts only for my project, "Project A" (as I am the admin of this project) whenever a formal module is loaded.

Is there a way to change the default menubar with the start up DXL so that it checks the access control level for the user to see which group they are in and allow menus to be viewable (Let's say display "Display Test Results") only if they belong with Project A , and not load the menu for "Display Test Results" when Project B user opens up a formal module?

Thanks very much

Report this to a Moderator Report this to a Moderator
 22-Oct-2004 15:23
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

The standard method of deploying DXL is via a shared folder, and setting the "addins" (and "projectaddins") environment variables. It is NOT project sensitive, all modules get the same addins. To do what you want you need to add custom scripts to your startup folder. See Mathis' response, but also search the forums for "createItem" for further discussion.

Note: this method will NOT let you modify the DOORS Explorer menu based on which project is Current; it will only work for Module addins. However, I'm sure there is a way to modify the Explorer addins based on some switch in your doors.exe icon. Users would effectively be saying "Run DOORS using project addins appropriate for Project A". There would be a different Icon for Project B.

- Louie
Report this to a Moderator Report this to a Moderator
 1-Feb-2008 01:33
User is offline View Users Profile Print this message


jason haury

Posts: 39
Joined: 20-Feb-2007

I have a question relating to this thread title, and though there's been a lot of help in similar threads already, I still would like to know if one can do the following: Can one gray-out or even make invisible custom menus and menu items which were made *by means of setting an "addin" path* (project addin or module addin).

I have a set of tools that are meant to be global tools (shows up in a Module menu bar as "ViaTools"). These tools are saved in a network location and displayed by setting an ADDIN key in the Windows Registry. There are additional tools that we would like to add to this menu depending on what groups a user is in. Per other threads, I've put a file in DOORSHOME\lib\dxl\config\formalFiles which simply point to and eval_ DXL in a network location - this DXL is meant to set up menu details (which items are gray, invisible, active, etc). I've also put a file in DOORSHOME\lib\dxl\startupFiles to establish the mapping functions. Both of these files and the "addin" registry keys are set by executing some DXL with the "-C" switch in the shortcut (the character limit keeps me from setting both addin switches, plus, executing DXL is more powerful).

With all this, I now have a ViaTools menu with, say, a "Sys Eng" submenu that I only want to be visible when the user is part of the "Systems Engineering" DOORS group. If I didn't display the ViaTools with addin keys (which is a very easy way to set up menu structure and update the menu with more tools) and instead used createMenu() and createItem() with my formalFiles DXL, then I can see how I could set the display status of each sub-menu and menu item. I would like to continue using this short-hand method for displaying ViaTools, and then write additional DXL only for the exceptions (most tools are for global use, but the exceptions in this example are the Sys Eng tools). Is there a way to gray out Sys Eng after the fact? Or, if not, is there a way to add to the ViaTools menu after the fact using createItem or createMenu?

At the present, it looks like I'll either have to 1) spell out all the tools in ViaTools explicitly and not use the ADDIN keys, or else have a separate menu item on the menu bar for all these group-specific tools.

Any tips?

Thanks!
Jason
Report this to a Moderator Report this to a Moderator
 1-Feb-2008 08:40
User is offline View Users Profile Print this message


Pekka Mäkinen

Posts: 276
Joined: 18-Mar-2004

I have implemented something which will produce the same end results by going the "easy" way of disk directory access rights. As the projects in DOORS are open to specific user groups, also the directories on shared disk containing the scripts are define to be readable for only to the project member user accounts. Thus when DOORS collects the module menus, it will load only those scripts which the current user account is able to access on shared location.

-------------------------
Pekka.Makinen@softqa.fi
SoftQA Oy -http://www.softqa.fi/
Report this to a Moderator Report this to a Moderator
 1-Feb-2008 16:51
User is offline View Users Profile Print this message


jason haury

Posts: 39
Joined: 20-Feb-2007

That's a great idea! In my situation, I'd have to have permission to create "security groups" on our domain and set permissions for those groups to various folders. I'm doubtful our IT department would allow this, but I'll look into this. If anyone knows how to do this strictly through DXL, I'd like to hear about it!

Jason
Report this to a Moderator Report this to a Moderator
 1-Feb-2008 17:00
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

I haven't done this on a per project level, as we have only one, albeit huge, project.

However, I do have some scripts/menu options that I don't want just normal engineers to have access to. What I have done is put users in groups and then within the formal.dxl (I only did this on the "Delete all Links" menu option) or menu building file, I check what group they are in and hide/inactivate the menu options by ascertaing if they belong to certain groups.

Similar to what I have attached.

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com

Edited: 1-Feb-2008 at 17:01 by Scott Boisvert
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.