![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DXL Attributes Broke? Topic Summary: Created On: 19-Nov-2003 17:24 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
DOORS 7.0 (SR1) and DOORS 5.2
I'm not sure if I am just misinterpreting the way DXL Attributes work or if there is a "Bug" in there... Scenario: I have a dxl attribute (attribute=IsValid, formal module=requirement) that is updated based upon the accumulation of another attribute (attribute=TestCasePassed, formal module=test case) in another module. Therefore, if all the linked testcases are passed then the (IsValid) attribute = "Yes". That said: The DXL Attribute value appears to update properly when I am looking at both modules in the same doors session. When I open up a second doors session and look at the Requirement (formal Module) in session 2 and I change the status of a test case (Test Case formal Module) in session one. The DXL Attribute (IsValid)will NEVER be updated even if I invoke the "Refresh DXL Attributes" from the menu in the Requirement module (session 2). The only way the (IsValid) DXL Attribute will be updated is if I close my DOORS Session 2 and re-open another session. Then once I open the Requirement formal module the DXL Attribute will be updated with the correct value. Now if you understand what I'm saying I would have to say that the way DXL attributes appear to work for me is that DXL Attributes only get updated the first time you open a formal module IN A GIVEN SESSION. I'm confused as to if this is the expected operation or not. Any thoughts? If this explanation is not clear enough I will be happy to explain this further. |
|
![]() |
|
![]() |
|
If you read Mod1 is Session1 and then edit it in Session2, make a change, and save it in Session2, you will NOT see the changes in Session1. This has nothing to do with DXL attribute. Session1 doesn't know or care that the loaded module is no longer identical to the (newly) stored module. You need to re-open the module in Session1 after saving it in Session2.
These will 'Re-Open' a module: [1] close it and open it [2] if open Read, change the mode to Exclusive or Shared ([2a] issue "edit" or "share" DXL commands) [3] if open Shared, change mode to Exclusive. I believe these will NOT 'Re-Open' a module: [1] If open Exclusive, change mode to Share or Read ([1a] issue dxl 'downgrade' or 'downgradeShare'). [2] If open Shared, change mode to Read. [3] issuing a DXL "refresh mod" command. I don't know if these will 'Re-Open' a module: [1] if open Exclusive, issue DXL "read" or "share" commands [2] if open Shared, issue DXL "read" commands. [2] if open invisible, open it visible. Be advised that "Re-Open" will also activate module-open triggers, if any. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
DXL Attributes Broke?
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.