![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: CP dxl Topic Summary: Created On: 19-Apr-2004 19:56 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi all: I have read all of the messages on the system about generation of metrics and have downloaded Dave's *.dxl script from last year. I too need to generate a status-report showing the status of each CP since the last baseline (rather than a simple metrics report). ... i.e.: - CP's added - CP's rejected - CP's reviewed. - CP's Approved - CP's Applied The manual process of calling up each module and filtering multiple times it is HORRENDOUS in my environment (many many modules). I have written quite a few *.dxl scripts now but this one has me stumped as I have searched through the entire *.dxl manual and it is no help at all wrt accessing CP information. Did anyone ever manage to get such a *.dxl CP script to work? Thanks Tim Ryan tryan@drs-esg.com (work) timDavidRyan@aol.com (home) |
|
![]() |
|
![]() |
|
CP information is housed in the CP partner module; NOT in the live module.
There is a dxl function: string fnGetCPModulePath(string NameFull) It gets the name of the CP partner module of the given live module. I'd be tempted to write a function: string fGetCPName(Module mCurr) { // Get the name of the CP partner module if (null mCurr) return("") return(fullName(mCurr)) } Module mCurr = current string NamePartner = fGetCPName(mCurr) Then open the partner. Then start looking for CPs yaddy yaddy via the CP module's attributes. - Louie Perhaps you should remove your home email from your Sig. Edited: 19-Apr-2004 at 21:45 by Louie Landale |
|
![]() |
|
![]() |
|
On the other hand, if all you want to do is open the CPS Partner module, there is a function "fnCPS_OpenPartner(current Module)" that will directly open the CPS partner of any module you can get a handle for (assuming it has a CPS partner of course). It is in "standard/cps/partner/partner.inc" so you need to do a #include of that file first. It makes the CPS Partner the current module when it is opened. I have used this in a script to generate some statistics on how long Change Proposals entered against the currently open module have been in various states without being acted on.
Another case of a function that is not documented. Found this one by poking around in the "standard" folder. It is the only thing in the "\standard\cps\partner\partner.dxl" file. Grant Cyboron ------------------------- Grant Cyboron L-3 Communication Systems East mail grant.cyboron@l-3com.com |
|
![]() |
Telelogic DOORS
» Change Management
»
CP dxl
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.