![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Column identifying object's last baseline Topic Summary: Created On: 22-Nov-2005 14:24 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I want to have a column that shows the oldest baseline that an object lives in that is not different from the current version.
For example, if a module has baselines 0.1 through 0.5, and an object has not been modified since baseline 0.2, then the column should show 0.2 as the oldest baseline. I've looked at DXL history functions, but they don't seem to offer what I need. Can anyone offer any suggestions? |
|
![]() |
|
![]() |
|
Try comparing the last changed date with the baseline dates. Some creative dxl with those two things should give you what you are looking for. I can't be much more helpful, as dxl is not really my thing - I am sure that the usual suspects can come up with a script in just a few minutes.
Hazel |
|
![]() |
|
![]() |
|
See topic in DXL Exchange under the same heading.
https://support.telelogic.com/en/doors/forums/messageview.cfm?catid=17&threadid=2781&enterthread=y ------------------------- Cliff Bly Edited: 22-Nov-2005 at 18:58 by cliff Bly |
|
![]() |
|
![]() |
|
You'll need to clarify "not been modified".
You may need to review the properties of Attributes, specifically "Change Date" and "History". If it means "no changes whatsoever" then you have a huge problem, cycling through all the attributes comparing the baseline's value of the obj.attr with the current version. If it means "nothing that changes the 'change date' of the object" then you can compare the last modified date of the current with each of the baselines. If it means "Nothing that modifies History" then you can cycle through the history of that object in each Baseline; looking for any history at all. You have 3 options for implementation. [1] Write a LayOut DXL that does the above, [2] Write an AttrDXL [3] write a script that updates an attribute that contains this information, and run that script often (such as every night). [2] is better than [1]. With all that baseline opening, [3] is superior to the other two. - Louie |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.