When the Application record is onboarded, the system triggers the new Governance Rules which are part of the ACES App. The system validates the imported Application attributes against the Reference Tables and auto-populates the target attributes to improve the system performance.
The following table lists the details of the auto-populated Application specific attributes.
| Attribute Display Name | Source | Reference Table | Description |
|---|---|---|---|
| Drop Application | ACES XML | Net Change Status | The value is auto-populated based on "Net Change Status" reference table. You can view the populated attribute values at the Application level. |
| ACES Parts Classification and Related PIES Parts Classification | ACES XML | Auto Parts Classification and Parts Relationship | The value is auto-populated by validating "Part Type against the Auto Parts Classification and Parts Relationship reference table. |
| All VCdb Attributes Pattern Text | ACES XML | The value is auto-populated based on the Vehicle Type Group Name, Vehicle Type Id, and Vehicle Type Name. |
Drop Application
Consider a scenario, where vendor has previously imported the Catalog with three Application records into the system. When the same Catalog is imported with two Application records, those two Application records are created in the system, and the previously imported Application records are dropped.
Whenever the Net Change status of the "Application" is Dropped, then the system triggers a business rule which validates the Net Change Status based on Net Change Status reference table.
Result: If the Net Change Status value is "Dropped", the system populates the Drop Application attribute value to "True". You can view the populated attribute value at the Application level. For more information, see Application Drop Management.
ACES Parts Classification and Related PIES Parts Classification
Consider a scenario, where vendor imports Catalog and Application records with Part Type Id "54116" into the system. Whenever a Catalog and related Applications are created, the system triggers the business rule, which validates the PartType against Auto Parts Classification and Parts Relationship reference tables.
- ACES Parts Classification reference table: The system validates the Part Type (Part Terminology ID) against the Auto Parts Classification reference table. If the Part Type is available in the reference table, then the system auto-populates the ACES Parts Classification attribute value with the 'Part Classification' column value.
- Parts Relationship reference table: The system validates the Part Type (Part Terminology ID) against the Parts Relationship reference table. If the Part Type is available in the reference table, then the system auto-populates the Related PIES Parts Classification attribute value with the 'Related Parts Classification' column value.
Result: You can view the auto-populated attribute values at the Application level.
If the 'Part Type or Part Terminology ID' is not available in the Parts Classification reference table, then the system copies ACES Parts Classification and populates the same value for the Related PIES Parts Classification attribute.
All VCdb Attributes Pattern Text
Consider a scenario, where vendor imports the Catalog and Application records with Vehicle Type Name, Sub Model, and Vehicle Type Group Name into the system.
Result: Based on the Vehicle Type Group Name, Vehicle Type Id, and Vehicle Type Name, the system automatically populates All VCdb Attributes Pattern Text attribute value. The format of the attribute is "VehicleType, SubModel, VehicleTypeGroup" separated by delimiter. You can view the auto-populated attribute values at the Application level.
