![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: DOORS / Synergy Integration - Relationship in ChangeSynergy Topic Summary: Created On: 27-Apr-2004 19:44 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Yes you need to add this new attribute 'associated_req' as a CCM_RELATION for WEbType and child for DBType. For each state of your lifecycle, you need to add the role security * for this specifici attribut in order to let everybody modifies this attribut for each state but you need to add it as HIDDEN in any transition or state. This attribute is hardcoded in the dxl files which are part of the integration. You can use, if you want, the ecps process (even if you do not use ECPS) provided on the CD of ChangeSynergy 4.2 in the following directory : /extras/contrib/unix or windows/cr_process Hope this helps BR | |
![]() |
|
Currently, I'm working with CM Synergy 6.2, ChangeSynergy 4.2, and DOORS 7.0. We recently upgraded to DOORS 7.0 and now am looking into implementing the DOORS / Synergy Integration 3.0 (NOT ECPS). I have it up and running on some test servers, but can't seem to get the full functionality in ChangeSynergy. In DOORS, I can submit a change request against a requirement and see the relationship between the requirement and the CR. I can pull CR attributes into DOORS; however, I can't see the relationship in ChangeSynergy. When I submit a CR, the probem_synopsis and problem_description attributes are automatically filled with information from DOORS, but once the CR is created, I can't find a CR attribute that holds that relationship - nothing to query or report on from ChangeSynergy. Since we're planning on linking many requirements to one CR, the viewing of this relationship is important. Has anyone implemented this Integration with the relationship visible in ChangeSynergy? I think that it's just some attribute that I need to add to the lifecycle...or maybe I'm hoping that it's only an attribute
![]() |
|
![]() |
|
![]() |
|
Hello
The relation used to keep the link between the DOORS object and the CR from ChangeSynergy is called "associated_req". The name of the DOORS object is created on the following basis 'reqUniqueid_of_module_AbsoluteNumber-1". Look at the log to see this information : Relationship change made by seb on 2003/11/24 09:13:19 Created 'associated_req' relationship from cr '82' to misc 'req00000120_2-1' where 00000120 is the uniqueID of my module and 2 the AbsoluteNumber of the object. Hope this helps Best regards Sébastien Cantini. Pre sales Engineer at Telelogic France |
|
![]() |
|
![]() |
|
Thanks, Great information...but how do I get that associated_req relationship to occur? Do I need to add the attribute 'associated_req' to my lifecycle? If so, what type? Does it need to be added like the other 2 attributes (hidden on the START_HERE2* transition)? How does ChangeSynergy know about this attribute? Sorry for getting into the dirty details! Thanks again.
|
|
![]() |
|
![]() |
|
Yes you need to add this new attribute 'associated_req' as a CCM_RELATION for WEbType and child for DBType.
For each state of your lifecycle, you need to add the role security * for this specifici attribut in order to let everybody modifies this attribut for each state but you need to add it as HIDDEN in any transition or state. This attribute is hardcoded in the dxl files which are part of the integration. You can use, if you want, the ecps process (even if you do not use ECPS) provided on the CD of ChangeSynergy 4.2 in the following directory : /extras/contrib/unix or windows/cr_process Hope this helps BR |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.