Conditional Visibility

Overview

This scenario ensures that the visibility of certain attributes is dynamically controlled based on the values of related attributes. 

By applying these rules, the system provides a cleaner and more intuitive user experience, showing attributes only when they are relevant and hiding them when they are not.

 

Objective

  • Improve user experience by showing only relevant attributes.

  • Prevent confusion and clutter by hiding attributes when not applicable.

  • Ensure consistency across applications during object creation and modification.

     

Demonstration

The following video illustrates how the Inspection Type field is conditionally displayed or hidden depending on the value selected for Incoming Inspections.

 

Hidden/Visible

 

 

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 conditionally control attribute visibility 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

In practice, this scenario ensures that the attribute Inspection Type is displayed only when the attribute Incoming Inspections is set to Yes. If Incoming Inspections is set to No, the Inspection Type field is hidden from the user interface. This conditional visibility rule is consistently enforced across various applications.

 

Business Rules

Visibility based on condition

Explanation

  • The BL checks the value of Incoming Inspections.

  • If set to Yes → Inspection Type is displayed in the UI with multiple values.

  • If set to No → Inspection Type is hidden from the UI.

  • This ensures users only see relevant attributes based on context.

 

Other Supported DELMIA Types

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

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" = "DELLmiOperationReference"

 

Reference

✔ All UX Openings

Author

Person of Contact - @AB @PJ 

Comments 0