![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: Restricting access to object source code Topic Summary: Restricting access to object source code Created On: 6-Jun-2006 21:14 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I have developed a new user role ChangeSynergy for users that are not allowed to download object source code. They have complained about not being able to see task information. Is there a way to set it up for these users to see the tasks but not able to view the objects?
Thanks, Alicia ![]() |
|
![]() |
|
![]() |
|
I don't know of anything in the core product, but you might be able to achieve it by the following approach (theoretical, I havn't tried it).
Also, I'm not sure if by "user role" you mean a login role or a privilege (as on the Admin Users page); I'm assuming you mean a login role. All customisation should be done as a package so that it can be re-installed easily after an upgrade. For a separate login role: This is probably quite complicated, and will probably need Telelogic consultancy, unless you have done similar things before. 1. Find the code behind the task display. 2. Make a copy of the code and modify it not to provide the object information; rename all files so they do not clash with the Telelogic standard files. 3. Add approriate entries to the package.cfg file. (this is not a simple process; there seem to be many entries needed for what seems a simple modification). 4. Define a new relation type for "tasks with no objects". 5. Add appropriate entries to the package.cfg file for the new relation type, and to link itto the new task-display code. 6. Modify lifecycle to use the new relation type for the log-on role. For a new privilege: This seems simpler to me (but again, it is theoretical), but it may still need telelogic consultancy, depending on your level of expertise. I am assuming that you are running Change 4.4 or higher; for 4.3 the implementation is a little different, but the principle is the same. 1. Define a new privilege (say "no_object_view") for the lifecycle 2. Find the code behind the "Associated object" table that is displayed on the "Task Information" view and in the expanded task details on a CR view. 3. Find the point in the code where the object links are implemented. 4. Edit (a copy of the file in a package, but don't change the name) the code to: 4a) determine if the user has the no_object_view privilege [this is the bit I believe can be done, but have no idea how). 4b) only allow the link if the user does not have the privilege. |
|
![]() |
Telelogic SYNERGY
» SYNERGY/Change
»
Restricting access to object source code
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.