![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Automatic Change to Status Attribute Topic Summary: Created On: 4-Apr-2003 19:38 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
We currently have a "Status" attribute which has a couple of possible values such as New, Modified, Deleted, etc. We were wondering if it possible for a DXL script to automatically change an attribute value should the Object Text of a requirement change. For example, if the Object Text was modified we would like the "Status" attribute to automatically mark it as Modified. Would this be done with using triggers? Are there any scripts out there that would do what we want? Thanks. |
|
![]() |
|
![]() |
|
A "post attribute save" trigger for Object Text could do the trick. The trigger, I believe, can compare the current object text with the one being "proposed" (use "value(trigger) command), and its its new then set Status to "Modified".
Another way is to write an Update script, which for every object in the module if its change date is "recent" set Status to Modified. Another way is to make a copy of the Object text. Later run a script that compares the current with the saved version, setting "Status" as you go. - Louie |
|
![]() |
|
![]() |
|
Hi Jesse,
An alternative to using triggers is to look at creating a DXL layout script that resides within a module column and displays your status information. DXL layout scripts pretty much operate in real-time, that is, they are automatically triggered every time an action occurs on the screen that requires the screen to be refreshed eg: scrolling, editing etc. The DXL layout script could be used to monitor the history records of each object, look for any recorded changes to the "Object Text" attribute, analyse the history record modification type and maybe also the "oldValue" and "newValue" fields and then apply some sort of criteria to determine which appropriate status message should be displayed. The down side? DXL layout columns differ from other columns in that a script is being used to display data in each cell of a column as opposed to an assigned attribute also being a repository for that displayed data. If you need to be able to save a snap shot of what the status is, then you will need to consider using triggers or authoring the DXL script to be a DXL attribute script that must be manually refreshed. If your status column is purely just to provide an immediate visual indication as to what the current real-time status is, then I would recommend writing your code as a DXL Layout script. ------------------------------------------ Paul Miller Tenix Specification Practices Project, Nelson House, Williamstown, Victoria, Australia, 3016. Desk Phone: +61 (0)3 9244 4078 Mobile: +61 (0)418 135 103 E-mail: paul.miller@tenix.com ------------------------------------------ ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Automatic Change to Status Attribute
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.