On an application, an attribute or reference exists to model each data point in a valid configuration. For the Vehicle To Body Style Config reference type an attribute for Body Num Doors and Body Type exists (similar to the configuration classification object shown above).
In the workbench example below, the dropdown for the Body Type attribute displays all the available body types that can be chosen for the selected application.
Though the workbench could be used to select any one of the available options, this would be done without the safeguarding of the intelligent automotive validation path functionality, and therefore is not recommended. Applications are not intended to be created nor edited in the workbench. Instead, a robust results table and value editor are provided within an Application Manager Web UI screen.
Within a Web UI Value editor, users can view and select only the valid options for the vehicle they are working with. In the example below, the Application Manager results table 'Value editor' is displayed for the 1996 Dodge Viper Base Vehicle, and only the Convertible and Coupe options display for selection in the dropdown.
When an application is created, validation paths are available for conditions / options stored as either attributes or references. However, each has its own configuration, as described below.
Options / Conditions Stored as Attributes
When the data model uses an attribute to store the vehicle option / criteria, the automotive validation path data is managed as described below.
Easy Setup creates an Automotive Validation Path attribute (AutomotiveValidationPath). This attribute is made valid as metadata on the attribute basic object type, making it available for population on any attribute.
Regardless of the model / standard you are working in, the system always evaluates the automotive validation path by beginning with the Base Vehicle / assembly object used in application records.
In the example above, the automotive validation path data within the data model is determined by:
- Identifying the application and following the ACES Application To Base Vehicle reference (AC_ACESApplicationToBaseVehicle) to the Base Vehicle.
- Examining all vehicle children of the Base Vehicle.
- Following the Vehicle To Body Style Config (AC_VehicleToBodyStyleConfig) reference on the vehicle to the Body Style Config target object.
- Evaluating the value of the VCdb Body Num Doors attribute (AC_VCdbBodyNumDoors) on that target object.
Syntax
The syntax of the automotive validation path is a series of commands, each separated by a period (.). Using the child, reference, ID (shown below), and attribute elements (including IDs of the applicable references and attributes to be followed), an automotive validation path can be applied to any attribute for which the data is modeled in STEP. When the vehicle option is modeled using an attribute, the final element of the syntax should always be an attribute where the value should be retrieved.
Note: Within the AutoCare model, validation paths are populated on some standard ACES vehicle options during Easy Setup when the reference modeling option is first created. If an automotive validation path is subsequently deleted, it can be reapplied manually using the syntax described within this guide. The attribute or reference can be deleted and Easy Setup can be re-run (System Setup > Component Models > Automotive - AutoCare Model > 1. Configure AutoCare Data Model). However, this is not the recommended method for production environments since deleting the reference also deletes all existing data for the reference. It is recommended to re-populate a deleted validation path manually on production environments.
Options / Conditions Stored as References
When the data model uses a reference to store the vehicle option / criteria, the automotive validation path data is managed as described below.
The Automotive Validation Path attribute described in the previous section is still relevant. When created by Easy Setup, the attribute is made valid on the Reference Type basic object type (in addition to the attribute basic object type). Thus, the Automotive Validation Path attribute can then be populated on any reference.
In the example above, the automotive validation path data within the data model is determined by:
- Identifying the application and following the ACES Application To Base Vehicle reference (AC_ACESApplicationToBaseVehicle) to the Base Vehicle.
- Examining all vehicle children of the Base Vehicle.
- Following the Vehicle To Engine Config reference (AC_VehicleToEngineConfig) on the vehicle to the Engine Config target object.
- Following the Engine Config To Engine Base reference (AC_EngineConfigToEngineBase) from the Engine Config Object (which are now considered sources of the Engine Config To Engine Base reference) to the Engine Base target object.
- Retrieving the STEP Name of the Engine Base object to be displayed in Application Manager.
Syntax
The syntax of the automotive validation path is a series of commands, each separated by a period (.). Using the child, reference, ID, and attribute elements (including IDs of the applicable references and attributes to be followed), an automotive validation path can be applied to any reference for which the data is modeled in STEP. When the vehicle option is modeled using a reference, the final element of the syntax should always be an ID of the reference where the STEP Name should be displayed.