Scenario:

There is a scenario involving the use of Forms and Business Rules. From a Forms perspective, the Deactivate button places a form into an Inactive (read‑only) state. However, there is a Business Rule configured with logic that unlocks a field (making it editable) when the field contains data. As a result, even after the form has been set to an inactive, read‑only state, the Business Rule can still make the field editable, effectively bypassing the intended restriction.

While this behavior aligns with the current Business Rule design, it can be confusing from a user experience standpoint. The existing documentation would benefit from more explicit clarification on this interaction, particularly with Inactive forms. Since the read‑only state is applied through an out‑of‑the‑box (OOB) feature rather than customization, additional explanation from the Product Group would help set clearer expectations and reduce potential misunderstandings.

Request:

We kindly recommend providing clearer guidance on when and under what conditions a read‑only field can or cannot be edited, as well as clarifying the extent to which Business Rules can override or interact with out‑of‑the‑box (OOB) features.

From a user’s perspective, fields on an Inactive (read‑only) form, set through the Deactivate button as an OOB feature, are expected to remain strictly non‑editable. If Business Rule logic is designed to take precedence over this behavior, it would be helpful to explicitly state this in the documentation. Clear clarification in this area would help set proper expectations and avoid potential confusion for customers.