Visual Rules
  • Dark
    Light

Visual Rules

  • Dark
    Light

While Catalog Item Rules support the business logic of a configurator, Visual Rules ensure the visual representation adjusts with fidelity on the basis of attribute values.

Conditions:

Conditions expose all local Attributes and allow the user to commit manipulation of the visual based on specific Attribute Values. By default, when many conditions are used, AND is the logical operator.

Actions:

Actions manipulate the visual representation. The following Actions are supported; set attribute visible, set attribute enabled, set attribute value, set visibility, set material, set model, and set property.

set attribute visible

Nothing tricky about this Action Type, a previously unexposed attribute will become visible.

set attribute enabled

Allows a previously unconfigurable attribute to become configurable.

set attribute value

This action allows for dynamically setting the value of any attribute specific to the Asset on which it is created.

set attribute value visibility

Makes visible an attribute value to visible based on some criteria

set attribute value enabled

Sets an attribute value base on some criteria

custom script

Leverages the client-side Player API for extremely complex or parametric configuration requirements. An example can be found here.

set visibility

Used for options that may or may not be included on a given model, this action type allows for toggling visibility.

set material

Set material will do just that, on the basis of the Attribute Value, an appropriate material may be applied to any of a given model's meshes. A tangible example is located here.

set model

An extremely powerful action type, set model leverages a reference point such that any model from the library can be placed within the scene. An example of this action can be seen within this configuration experience, and the corresponding setup can be viewed here.

set property

The set property action provides the ability to automate manipulation to any of the properties in a given asset view, as well as the properties of any operator. A simple example can be seen here.

set active camera

Useful for scenes with multiple cameras. set active camera allows for setting the view to any camera in the scene on the basis of some input. Perhaps there is an area of a model which should be emphasized when a given component is being configured. Setting up multiple cameras would allow for transiton between these views.

Was This Article Helpful?