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: Column identifying object's last baseline
Topic Summary:
Created On: 22-Nov-2005 14:24
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.
 22-Nov-2005 14:24
User is offline View Users Profile Print this message


Phil Schmidt

Posts: 3
Joined: 2-Dec-2004

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?
Report this to a Moderator Report this to a Moderator
 22-Nov-2005 15:02
User is offline View Users Profile Print this message


Hazel Woodcock

Posts: 78
Joined: 6-May-2005

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
Report this to a Moderator Report this to a Moderator
 22-Nov-2005 17:42
User is offline View Users Profile Print this message


cliff Bly

Posts: 58
Joined: 11-Apr-2003

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
Report this to a Moderator Report this to a Moderator
 28-Nov-2005 19:15
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

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
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.