![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: File -> Baseline -> Compare Topic Summary: is only giving me changes to the Object Heading and Object Text Created On: 24-Jul-2007 15:55 Status: Post and Reply |
Linear : Threading : Single : Branch |
|
![]() |
![]()
|
![]() |
|||
If I look at a baselined version of a module, I can see the changes to a particular object, for all attributes. Therefore I assume that the history is available.
If I use File -> Baseline -> Compare to obtain a list of these changes, it is only showing changes to the Object Heading and Object Text attributes. Is this a limitation of File -> Baseline -> Compare and, if so, is there a script knocking around here which gives me more comprehensive changes? TIA |
|||
![]() |
|||
![]() |
|||
Alan,
Did you get any feedback on your question about a more comprehensive comparision script? I am also interested in being able to easily identify altered values of attributes other than Object heading and text.
|
|||
![]() |
|||
![]() |
|||
I had to write my own script, but it isn't a generic one it's specific to the attributes in our database. Though it works 99% of the certain RTF strings can cause issues, not too mention I haven't figured out how to identify if an image/OLE objects has been modified.
------------------------- Scott Boisvert Engineering Tools Administrator L-3 Communications - Avionics Systems scott.boisvert@l-3com.com |
|||
![]() |
|||
![]() |
|||
Hi Karrin
Unfortunately not.
Like Scott, I've looked into writing a script to do it, but other work has got in the way of any real progress on it.
Alan
|
|||
![]() |
|||
![]() |
|||
The attached script can be used in a layout DXL column in order to display all attribute modifications between two baseline versions (or a baseline and the current version, of course). It will compare those attributes actually displayed in the current view (in the order in which the attributes are displayed in the different columns).
------------------------------------------------- An example: Let's say you have a view with three columns: the first column hosts an attribute called "Requirement ID", the second column is the main column, and the third column displays an attribute "Req. Specification". Now, if you create a fourth column, make it a layout DXL column and enter the following DXL code (given that you have put the attached script as "versionCompare.inc" into your layout DXL folder): #include <versionCompare.inc> modifications() Then the new column will show the differences between the current version and the latest baseline, and it will compare "Object Heading" and "Object Text" as well as the two additional attributes. Whenever a difference is found, it is displayed in the traditional underline / strike through style (together with the attribute name). ------------------------------------------------- Now, if you want to compare to a specific baseline (e.g. 2.1), you can do so as follows: #include <versionCompare.inc> modifications(true, true, 2, 1, "") The two additional boolean variables control the following behaviour: The first one controls whether modifications are shown as differences (underline / strike through) [true]; or whether just the attribute value from the baseline version is shown [false] The second one controls whether it is noted if an attribute was created / deleted since the baseline [false]; or whether this information is not explicitly stated [true]. ------------------------------------------------- Last, there is the option to automatically compare the current version to the last major or minor baseline: #include <versionCompare.inc> modifications(true, true, "Major") or modifications(true, true, "Minor") Cheers, Peter Edited: 12-Oct-2007 at 08:51 by Peter Albert |
|||
![]() |
|||
![]() |
|||
Peter,
I found this script very useful. Do you know what changes are necessary for the script to work with baselines which are part of a baseline set? I have been trying to modify the read_baseline function so that it gets the baseline set definition, loops through the baseline sets, and then through the module versions. I'm not a programmer, but I've attached the edited function to give you an idea of what I'm trying to do. Note that the Baseline Set Definition Name, Baseline Set ID, and module path would have to be hard-coded or passed in... I'm getting a syntax error on the whole script and thought I'd check to see if you've added this functionality before spending too much time on it. Thanks, Gabe Edited: 4-Jan-2008 at 21:18 by Gabriel Applegate |
|||
![]() |
|||
![]() |
|||
Well, I haven't added baseline set functionality to the script yet, but I have attached a slightly modified version of your script which accepts three string variables as input, namely the module name, the name of the baseline set definition and the name of the baseline set. If the specified baseline set contains a baseline of the specified module, the script returns this baseline.
Hope that helps, Regards, Peter |
|||
![]() |
|||
![]() |
|||
Thank you very much Peter! That helped tremendously!
- Gabe |
|||
![]() |
|||
![]() |
|||
I would like to add this option to my users (Projects Managers), Does anyone have a GUI utility for "compare baseline" which i can use?
Thank you! Edited: 14-Jan-2008 at 10:11 by Jon Martin |
|||
![]() |
|||
![]() |
|||
![]() Regards Juergen
Edited: 9-Feb-2008 at 21:19 by Juergen Albrecht |
|||
![]() |
|||
![]() |
|||
This is an amazing script.
Juergen, Do I supposed to see the deltas (changes) in the output file? I'm only getting a table with the ID number and the attribute name, Can you tack a look in the attached file? Thank you for sharing you tool with us!!
Edited: 16-Jan-2008 at 11:15 by Jon Martin |
|||
![]() |
|||
![]() |
|||
Hi Peter,
Congratulation for this wonderful script ! It will save us a lot of time, as we have similar experimentation at various places of our database. Looking at your comments, I've seen your "experimental highlightning" feature. You may want to try the following: ==> On the "diff" line, remove the mark-ups : {Sdiff = diff(difference, oldValue, newValue)} ==> Then, display with color (undocumented feature) : // Display the modifications and delete buffer displayRichWithColor tempStringOf disp Changing both those lines will display the same redlining than in any other DOORS feature: additions in blue and deletions in red. |
|||
![]() |
|||
![]() |
|||
Hi Eric,
thanks for the plaudit, I profited a lot by this forum, and I am glad I could give something back. As for displayRichWithColor , as far as I know this perm was introduced with DOORS 8.x. We are still running on 7.0, so I have not used it so far. But thanks for pointing it out. Regards, Peter |
|||
![]() |
|||
![]() |
|||
Hi Jon,
as I checked your RTF File I think that you have't deselect the Checkbox (Show Object Text changes as markup) If you do it and repeat the process it should show your changes. Hey and please take the script again to make sure it will be the same which I use. regards Juergen Edited: 17-Jan-2008 at 10:39 by Juergen Albrecht |
|||
![]() |
|||
![]() |
|||
Hi All
I'm using Peter script (the one above) and it is working very well. I want to add the name of the user that made the change in the column. Can you help me? 10x |
|||
![]() |
|||
![]() |
|||
Hi Jon,
that's not a straightforward thing to do, as the whole script is not based on the Object's History but rather compares the two object values. This is especially crucial when you compare the current version to a baseline prior to the most recent one, in that case you must open all baselines and check all history records until you find the most recent modification of the attribute in question. However, I'll think about it, probably I'll find an easy way at least for the cases where only changes in the current version are displayed. I'll post if I come up with something. Regards, Peter |
|||
![]() |
|||
![]() |
|||
I would like to add the "Description" for each baseline when i run this report. Anyone tried to add that to this great script?
|
|||
![]() |
|||
![]() |
|||
Peter,
Are you available offline? |
|||
![]() |
|||
![]() |
|||
Terrence,
sure, my E-Mail address is in my profile. Peter |
|||
![]() |
|||
![]() |
|||
Hi Peter,
I tried your email address and it gets pushed back as undeliverable. |
|||
![]() |
|||
Telelogic DOORS
» DXL Exchange
»
File -> Baseline -> Compare
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.