Improve Transparency and Override Logic for Required Fields in Redwood Flow Configurations

In the Redwood configuration for the "Change Location" flow within Oracle HCM, there is inconsistent and confusing behavior regarding required fields and their visibility, especially in combination with customer-specific rules.

Current Issues:

• In the Default Rule, the field ActionID is visible and mandatory, although the "Required" checkbox is not activated.
• This required behavior cannot be overwritten in the customer-specific rule — even though there is no visible lock icon indicating a restriction.

Requested Enhancement:

• The system should clearly indicate when a field's status (e.g., "Required") cannot be overridden — for example, by displaying a lock icon

Business Justification:
Without clear indicators or consistent behavior, there is a high risk of misconfigurations, user frustration, and unnecessary Service Requests. Improved transparency and control would allow for a smoother setup of Redwood flows and reduce support effort for both Oracle and customers.