Bmihura,
I'm sorry you feel that the dialog box is "lame". The reason you cannot access those other two items is because they do not exist by default, as Ray stated in his response. If you would like to create your own dialog box, you can do so and add two fields to prompt the user for the hardware revision and the part number. Then simply add two local variables to your process model to hold the resultant values of the hardware revision and the part number. Then later in your CVI code, if you want to access those fields, you can use the property path of "RunState.Root.Locals.UUT.PartNumber" and "RunState.Root.Locals.UUT.HardwareRevision" assuming that you create those two variables within the UUT container.
This dialog box does not prompt for
those values by default simply because there are many different types of users who need different information. If we were to create a dialog box that had all the potential fields that every customer might use, the dialog would become rather large and not useful to the majority of our customers. Instead, we chose to only add the basic information to the dialog box. As with most components of TestStand, if this out-of-the-box component does not fit your needs, you can always customize this as I stated above.
I hope this helps your development within TestStand.
Regards,
Shannon R
Applications Engineer
National Instruments