Behaviour of OmniScript Input Fields When Marked as Both Required and Read-Only

In OmniScript, marking a field as both Required and Read-Only creates a functional conflict:

• Required → mandates user input before proceeding
• Read-Only → prevents user interaction or data entry
  
  

Runtime Comparison:

• Managed Package Runtime: Validation is not triggered for read-only fields marked as required, even when the “Disable Read Only” condition is enabled.
  
  
• Standard Runtime: Validation is triggered for read-only fields marked as required, even when the “Disable Read Only” condition is evaluated to true, and users are prevented from proceeding to the next step if required fields are not populated.
  
  

1. Input Elements That DO NOT Enforce Validation

When both Required and Read-Only are enabled, the following input elements bypass required-field validation and allow users to proceed even if the field is blank:

• Text
• Password
• URL
• Text Area
• Time
• Date/Time
• Date
• Email
• TypeAhead

2. Input Elements That DO Enforce Validation :

The following input elements continue to enforce required-field validation, even when marked as Required and Read-Only:

• Telephone
• Radio
• Select
• Currency
• Multi-Select
• Number
• Lookup