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: Re-establishing CP link
Topic Summary:
Created On: 2-Jan-2007 17:13
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.
Answer This question was answered by Doug Betsinger, on Saturday, January 13, 2007 2:05 PM

Answer:
Thanks Louie, Yes you were correct. The module I was replacing was actually the same module I had archived. the only difference was that in the "current" module, I had hooped to fall back to the previous baseline so had foolishly attempted to do that by deleting the latest baseline. (Needless to say, the result was not desired). Anyway, I appreciate the advice and script, unfortunately though I had already worked around the linking issue prior to getting your script by adding an temporary attribute to the cp module and populating it with the object ids of the module I was replacing via the links prior to deleting the module. (and then recreating them via the link by attribute functionality). Your script would have been much easier, but I had to move too quickly. thanks again for your support. Everything seems to be working fine now. Thanks Doug
 2-Jan-2007 17:13
User is offline View Users Profile Print this message


Doug Betsinger

Posts: 3
Joined: 8-Jul-2005

Hi, Has anyone ever had the need to re-establishing the link between a CP module and a Formal module? I have an issue where I need to remove the current module that is tied to my cp module and restore an archived formal module. I would like to link the restored module to the existing cp module because I I don't want to lose the history in the existing CP module. Also I was hoping to not create a new cp module, since the numbers would restart at 1 (thus a duplication of the previous CP ids). Any suggestions are appreciated. thanks Doug
Report this to a Moderator Report this to a Moderator
 2-Jan-2007 18:47
User is offline View Users Profile Print this message


Doug Betsinger

Posts: 3
Joined: 8-Jul-2005

It appears that creating a linkset within the CP link module is enough for the CP system to now recognize that the new module is attached to that CP module and allow me to create cp's. It is unclear, however, whether doing that is all that needs to be done, or whether there is a lingering inconsistency that will come out at a later time (since it wasn't created by the CP system). I appreciate any comments that may further my understanding.
Report this to a Moderator Report this to a Moderator
 9-Jan-2007 01:00
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

When we create CP module we immediately rename them to be meaningful; thus the CP module for module "XYZ" is renamed from "Proposals 1" to "CPs XYZ". I don't think that qualifies for 'monkeying'. Monkeying with the CP system will theoretically void Telelogic's responsibility for answering any CP related troubles you have. Thus, *ahem*, make use of Telelogic's 'Don't ask - Don't Tell' policy on such monkeying; especially the 2nd half of that policy...

I assume the module you are restoring has common ancestorship with the module you are replacing, meaning that for the most parts the same objects have the same absolute numbers. If not then good luck.

Doug is right that if you create a CP-to-Source linkset in link module "Change Proposal Links" that the CP system is a happy camper. You sould thus do this [1] purge the original; restore the replacement; recreate the link-set.

[2] Relink. Be advised that the Object Identifer of the desired source object is embedded in the Object Text of the CP object. You would thus need to parse the object text of all CPs extracting the Identifier of the corresponding source object, then find the source object with that identifier. Yuuuuuck.

Yiiiiiippyyyy, you are in luck since I've already done that. See attached. Now I cannot guarantee it works since I've never actually used that script since it would void Telelogic support. *Ahem*. The 'fnGetSourcePath' is an undocumented Telelogic written function which I confirmed gets the source name from the link module; you thus must create the link set manually before running the script.

I don't recall the problem with a '-' in a Prefix but suspect it has something to do with the Regular Expression logic I surely stole from someone else, since I don't understand RegExp. You may want to look for 'Applied' and decide if you want that feature. Be advised that if you've changed the 'Prefix' of the source module this script will be a bear. You will probably have to run the script several times, before each time changing the source Prefix to one of its historical values.

Displaimer: this script is 'Deplorable' and wll below my normal standard for 'Deployable' scripts. But it theoretically *ahem* works. Much of the code is someone elses and I never cleaned it up.

Be sure to practice on a sand-box project before doing on the production one. That's not an "*ahem*".

- Louie
Report this to a Moderator Report this to a Moderator
 13-Jan-2007 14:05
User is offline View Users Profile Print this message


Doug Betsinger

Posts: 3
Joined: 8-Jul-2005

Answer Answer
Thanks Louie, Yes you were correct. The module I was replacing was actually the same module I had archived. the only difference was that in the "current" module, I had hooped to fall back to the previous baseline so had foolishly attempted to do that by deleting the latest baseline. (Needless to say, the result was not desired). Anyway, I appreciate the advice and script, unfortunately though I had already worked around the linking issue prior to getting your script by adding an temporary attribute to the cp module and populating it with the object ids of the module I was replacing via the links prior to deleting the module. (and then recreating them via the link by attribute functionality). Your script would have been much easier, but I had to move too quickly. thanks again for your support. Everything seems to be working fine now. Thanks Doug
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.