Hiding Input Parameters When Users Do Make a Selection

Data Management Capabilities > Managing Part Structures > Developing Advanced Selection Logic for Configurable Modules > Examples and Best Practices for Advanced Selection Logic > Improving the User Interface of the Configuration Process > Hiding Input Parameters When Users Do Make a Selection

In some cases, you may want to define or drive the value of one input parameter based on the value of another input parameter. To do this, you need to define a case table to constrain the values of the second parameter. Consider the following case table example.

askMaterial	askTrim
Oak	Cherry
Walnut	Maple
Cherry	Walnut

In this case, regardless of the value selected by the user for askMaterial, only one possible value exists for askTrim. Therefore, as soon as askMaterial has been defined, askTrim is assigned by this case table.

If the parameter askTrim is defined as: hide when driven = true (on its UI Properties tab), then the user would not be required to provide a value for askTrim once the value of askMaterial is specified.

Remember that parameters are processed by the system on a page-by-page basis. Therefore, if you want the system to automatically specify the parameter askTrim, you must place askTrim on a page after the page where askMaterial is specified.