![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Default Attribute settings Topic Summary: Created On: 23-May-2007 18:47 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
I created an enumeration type with 10 different values in the list. I then created an attribute based upon the enumeration type I just created. I selected the attribute to be multi-valued and the default value to automatically select all ten values.
When I add this attribute as a new column to my existing requirements module, there are a few requirements where I would like to completely deselect ALL the values in that enumeration. When I do this and move on to the next requirement, all the values automatically become selected again. If I only deselect a few values, then it works perfectly fine. Any ideas on how to get around this? ------------------------- Charing Maher Systems Engineer, SAIC |
|
![]() |
|
![]() |
|
Hi Charing,
I guess what you see is occuring since you have set the default value as ALL and DOORS sets the default value when none of the values of been selected. It seems to be setting the default value when the attribute value is null. What you could do is add one more value 'None' or anything suitable and select it whn u dont want to select any of the other values. ~uma |
|
![]() |
|
![]() |
|
'Default' means the value it appears to have when it really has no value at all. Well, when you erase all values then it has no value at all and it displays showing all values.
You can have a value called 'none' and select it when that's your intention. You can also remove the default feature of that attr-def, use DXL to set all values to all 10, then adjust it as you want. You have a problem when you create a new object, however, as its value will be null. BTW, there IS a difference between a defaulted value and one that is set explicitely. If one object defaults to all set and you manually set all the values in the next object, they appear to be the same but in fact are not. For one thing, if you change the default value of the attr-def to 9 of the 10, the 1st object will change (since it really has no value) but the 2nd object will not. In DXL; this line gets the apparent value: string Value = obj."MyAttr". In DXL, this perm will tell you if it has an actual value, and from that you can infer that its inherited or defaults" bool HasValuye = hasSpecificValue(obj."MyAttr") |
|
![]() |
Telelogic DOORS
» General Discussion
»
Default Attribute settings
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.