Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic SYNERGY (steve huntington)
Decrease font size
Increase font size
Topic Title: Having certain forms available only in certain databases
Topic Summary:
Created On: 19-Jun-2006 15:35
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
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.
 19-Jun-2006 15:35
User is offline View Users Profile Print this message


Alicia Ade-Kuhn

Posts: 6
Joined: 14-Nov-2005

      Hey, I'm trying to figure out how to have specific forms only available on certain databases. 

     What I have are a bunch of different lifecycles, each representing a specific form (e.g. ECP, FR, AI, CR, etc.).  What I'd like to have is certain forms only available on certain databases.  Like for ECPs, I'd like to have a database that is specifically for only ECPs and nothing else.  Is there a way to make a lifecycle specific to a certain database?  Or is it possible to check the database that an user is in and gray out certain forms or something of that sort? 
   
     I thought of doing it with DCM (the data transfer attachment for change synergy, I'm not sure if I have that right) and transferring any forms that are created in incorrect databases, but I've heard of problems with DCM such as changes in the forms not getting sent over and such, so I'd like to avoid using it if at all possible.
 
     If anyone has any ideas I'd very much appreciate it.  Thanks a lot.
                       -Alicia

Report this to a Moderator Report this to a Moderator
 26-Jun-2006 17:40
User is offline View Users Profile Print this message


michael Barnes

Posts: 85
Joined: 12-Nov-2003

It is possible to do something like you want, but there are other implications iin doing so.

Assuming that in any one database you will only ever want to look at CRs of a particular type, it can be set up as follows:.

A) Have a separate lifecycle definition for each CR type.
B) Have a separate Change installation for each CR type.
C) Allocate databases to installations according to the CR lifecycle they need to follow.

However, if you want to pass CRs from one data base to another, where the lifecycles are different, then you are likely to find that the CRs are not modifiable (or not easily modifiable) in that other database.


An alternate approach would be:

1) Have a combined lifecycle (as you have done already)

2) Define a set of CM Synergy roles for each CR lifecycle (eg "AI_enterer", "FR_enterer", "AI_assigner", "FR_assigner)

3) For each CR type, only allow users with the CM privileges starting with that type's ID to perform actions on the CR (transitions and states).

4) For each database, assign the appropriate privileges according to the CR type that is to be used.

Note that:
a) lines 2 and 3 need careful thought and design before going ahead, to ensure that you will achieve what you want to achieve.

b) To progress tasks within Change, users need (I believe) "developer" privilege.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 15:34.
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.