![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: History Property Values Topic Summary: Created On: 10-Oct-2002 23:29 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Refer to </lib/dxl/example/hist.dxl> in your DOORS installation for an example. h.attrName only works if ( ht == createAttr || ht == modifyAttr || ht == deleteAttr ) h.absNo only works if ( ht == createObject || ht == copyObject || ht == modifyObject ) h.numberOfObjects only works if (ht == createType || ht == modifyType || ht == deleteType) So, some If-Then checking is mandatory when using History Types. | |
![]() |
|
Did anybody out there experience "fun" with history? I did. I get DXL error messages when the property value is changed in the example below.
History h for h in current Module do print h.sessionNo I had tried type, author, date, sessionNo and it went O.K. I got errors when I used attrName, absNo, numberOfObjects. Can you explain to me, please, where am I mistaking and what shall I do? I will appreciate very much your prompt feedback. Best Regards! Doina Scafaru |
|
![]() |
|
![]() |
|
Refer to </lib/dxl/example/hist.dxl> in your DOORS installation for an example.
h.attrName only works if ( ht == createAttr || ht == modifyAttr || ht == deleteAttr ) h.absNo only works if ( ht == createObject || ht == copyObject || ht == modifyObject ) h.numberOfObjects only works if (ht == createType || ht == modifyType || ht == deleteType) So, some If-Then checking is mandatory when using History Types. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
History Property Values
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.