![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Using "Related Number" Experience Topic Summary: Created On: 13-May-2004 16:06 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi -
There is an option that when you create an enumerated list a Related Number value can be assigned to the value. Has anyone used this before and had any problems? Does using Related Numbers increase the speed of filtering? Just curious and thanks, ------------------------- pete.kowalski(at)motorola.com |
|
![]() |
|
![]() |
|
It can be used in some filtering. If you assign "NA" = 0, "Low" = 1, "Medium" = 2, "High" = 3 then you can somewhere say "show me objects that are Medium priority or higher"; actually with a number at least 2.
Doesn't look useful and I've never done it. I'd rather query "Show me Medium or High priority objects". - Louie |
|
![]() |
|
![]() |
|
I have always dismissed the Related Number as not very useful until yesterday when I realised they influence the order in which multi selections are displayed in a view column. Nowdays I set the related number to 0. I did this yesterday to a new option in a list of enumerations that already had some numbers set. I then selected all the possible enumerations in one object as a test. The new selection was second on the displayed list following another with the related number set to 0. If I set them all to zero they displayed in the order set up for their type.
|
|
![]() |
Telelogic DOORS
» Administration
»
Using "Related Number" Experience
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.