Input Validation & Feedback

Overview

This scenario ensures that attributes comply with defined format rules and are not left empty. Invalid inputs block the save action with a validation message, while certain conditions may trigger a warning message without blocking the save. Valid inputs proceed seamlessly without warnings or errors.

Objective

  • Protect data integrity by enforcing mandatory and format rules.
  • Provide clear feedback to users through validation and warning messages.
  • Ensure consistency across applications during object creation and modification.

     

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 validate attributes against mandatory and format rules during both object creation and modification, enforced in the Information tab and Instance panel.

Best Suitable Opening Idux_init_edit_properties_modify, compute_new_init

Use cases:

  • Before → Users could save objects with empty or invalid attribute values.
  • After →
    • Empty or invalid values → Save blocked with validation message (Error).
    • Certain non‑critical conditions → Warning message displayed, save allowed (Warning).
    • Valid inputs → Saved without warnings or errors (None).

       

AttributeConditionMessage ShownSeveritySave Allowed
DescriptionEmpty“Description cannot be empty”1 (Error)Blocked
 Contains %, #, @“Invalid characters (%, #, @) are not allowed”1 (Error)Blocked
 ValidNone0 (None)Allowed
Measured Time= 0.0“Measured Time should be greater than 0s”2 (Warning)Allowed
 > 0.0None0 (None)Allowed
<strong>Severity Codes</strong>
<strong>1 (Error)</strong> → Blocks submission. User must fix the issue before saving.
<strong>2 (Warning)</strong> → Allows submission, but highlights a potential issue.
<strong>3 (Information)</strong> → Allows submission, just provides guidance or context.
<strong>0 (None)</strong> → Clears any previous message; no notification is shown.

Business Rules:

Description_Notification

 

MeasuredTime

 

Explanation:

  • Empty check: If the attribute is empty, the save action is blocked with a validation message.
  • Format check: If the attribute does not match the defined format, the save action is blocked.
  • Conditional warning: If the attribute meets a non‑critical condition, a warning is displayed but save is allowed.
  • Valid input: If all checks pass, the attribute is saved without warnings or errors.

     

Example 1: Description Validation

When the Information page is opened, the Business Logic (BL) is triggered and performs the following checks on attributes:

  • Check if PLMEntity.V_description exists.
  • Retrieve its value.
  • Check if the attribute has the Notification property.

Result:

  • If description is empty → Notification message: “Description cannot be empty”
    • Severity = 1 (Error) → Save is blocked.
  • If description contains invalid characters (%, #, @) → Notification message: “Invalid characters (%, #, @) are not allowed”
    • Severity = 1 (Error) → Save is blocked.
  • If neither condition is met → Attribute is valid, editable, and no severity message is raised (Severity = 0).

     

We can see in images as well:

 

Case - empty (Severity 1)

 

Case- Invalid Characters (Severity 1)

 

Case - All OK (Severity 0)

 

Example 2: Measured Time Validation

When the Information page is opened, the Business Logic (BL) is triggered and performs the following checks on attributes:

  • Check if DELLmiOperationReference.V_MeasuredTime exists.
  • Retrieve its value.
  • Check if the attribute has the Notification property.

Result:

  • If the value = 0.0   → Notification message: “Measured Time should be greater than 0s”   → Severity = 2 (Warning) (since saving is still allowed).
  • If the value > 0.0   → No notification message. → Severity = 0 (None) → Attribute passes validation.
  •  

We can see in images as well:

Valid then no warning message( Severity 0)

 

Case - Cannot be zero (Severity 2)

 

 

Other Supported DELMIA Types:

When associated with type DELLmiFunctionReference, the BL is invoked on Manufacturing Item. 

When associated with type DELFmiOperationReference, the BL is invoked on Operation item.

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.

How to Deploy Business Rule

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" = "DELFmiFunctionReference" (Description_Notification)

 Deploy the BL using Data Setup for "Fact type" = "DELFmiOperationReference" (MeasuredTime)

 

Reference

✔ All UX Openings

Author

Person of Contact - @AB @PJ 

Comments 0