![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: data entry forms Topic Summary: Created On: 15-Nov-2002 18:09 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi, I am new to DOORS, so I thought this might be a good place to start.
Is there a DXL script for creating a Data Entry Form? I have a module with MANY attributes, and rather than creating multiple views, I was wondering if it would make sense to create a form that our end users could use to populate all of the attributes, without having to switch from view to view... Any help / advice would be appreciated. Thanks, Shannon Jarrett ------------------------- Shannon Jarrett BellSouth Telecommunications Atlanta, GA |
|
![]() |
|
![]() |
|
Hello
It may be better to use the views. If the user was only updating Module attributes, a data entry form would be fine. The script you want can be done. This script may give you some ideas. |
|
![]() |
|
![]() |
|
My very first script was the one you suggested (DOORS v4). It was a nightmare. It only took about 3 months (including DXL learning curve). There was just so much to do...
o Write generic get/display/retrieve/put/haschanged functions for each kind of attribute allowed (one for strings, one for text, one for bool, ... one for each different enumerated value... . The multi-enumerated were particularly difficult: you need to write mapping functions to determine what the actual/changed values are/should be, then convert them into DXL commands to add/remove from the object. o Map the generic functions to actual attibutes. o Use Next/Previous/Reset/Refresh navigate buttons. o Keep track of the value of each attribute as changed, and when the "next/previous" or whatever button was pushed, read each field and see of the value changed; if so update the object. o Manuever them on the various Dialog Boxes. o Deal with the fact that Enumeration Lists change, which is hard to keep track of and hard to position on a DB. o Deal with the fact that some attributes don' t exist in some modules. Therefore allow for generic user-defined attributes to be displayed in the DB. Its kind of like writing a procedure for pushing a wet noodle. It CAN be done .... The script died with V4 and I never revived it. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
data entry forms
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.