Overview
This scenario restricts attribute inputs to predefined lists, ensuring standardization and compliance.
Objective
Prevent invalid or inconsistent data entry.
Enforce organizational standards.
Version – 2026x GA (On‑Premise) / HotFix 1.32 (Cloud)
Pre-requisites: Owner role
Licenses – TXO, MFN / MGA / RME
Disclaimer: Licenses mentioned above are as per 2026x documentation.
Opening ID: | compute_new_init, ux_init_new_modify, compute_edit_properties_init, ux_init_edit_properties_modify |
Customization intent: | Not Applicable |
Execution context: | Server |
Usage | The goal of the Business Logic (BL) is to restrict attributes to authorized values during both object creation and modification, enforced in the Information tab and Instance panel. |
| Best Suitable Opening Id | ux_init_edit_properties_modify, compute_new_init |
Use cases:
The following examples illustrate how the Business Logic (BL) enforces attribute behavior during creation or modification of a workplan or other supported objects. Attributes are validated against predefined lists, ensuring that only authorized values can be selected and saved through dropdowns.
Note: Custom_TaskType is a custom types.
Business Rules:
You can modify the list of values according to your business needs.
Example 1: Authorized Values for Custom Task Type
When the Information page is opened, the Business Logic (BL) is triggered and performs the following checks on attributes:
- Check if the attribute
XP_DELLmiGeneralOperationReference_Ext.Custom_TaskTypeexists. - Check if the attribute has the AuthorizedValues property enabled.
Result:
- If both conditions are met → the BL sets a predefined list of authorized values (
Dispensing, Gluing, Screwing, Welding, Printing, Testing, Riveting, Casing, Stamping, Assembling) for the attribute. - Otherwise → the attribute remains unrestricted.
Script Behavior: The BL appends each authorized value into a list (authvalueForDesc) and then applies it to the attribute using SetUIAttributeAuthorizedValue. This ensures that users can only select from the approved operations, preventing invalid or inconsistent entries.
We can see in images as well:
Other Supported DELMIA Types:
When associated with type DELFmiOperationReference, the BL is invoked on MI.
The same logic can be applied to other DELMIA types as well.
Business Rule Deployment:
You may refer the below page for Business Rule deployment.
For deployment using Data Setup app following Resource set ID and opening needs to be used:
Resource Set ID:
Opening:
Fact Type:
Deploy the BL using Data Setup for "Fact type" = "DELFmiOperationReference"
Reference
Author
