Overview
Customers may expect a task to be blocked from completion when a mandatory field is marked as read-only. However, this behavior is not currently enforced within product policy validations. This article explains why this occurs and what to expect going forward.
Issue Description
There is a requirement to restrict task completion based on a read-only mandatory field within a task. However, even when the field is marked as mandatory, the task can still be completed successfully.
Current Behavior
The behavior being observed is expected.
At this time:
Read-only fields are not included as part of the update request.
Existing validation logic only evaluates fields that are part of the update payload.
Mandatory validation is not triggered for read-only fields that fall outside the scope of the update.
As a result, task completion is not blocked when a mandatory field is read-only.
Why This Happens
Since read-only fields cannot be updated by the user, they are excluded from the update request. The current validation framework does not enforce mandatory checks on fields that are not part of this request, which is why task completion proceeds without restriction.
Future Considerations
We are exploring potential enhancements to this validation behavior in future releases. If such enhancements are implemented:
We can evaluate whether task completion should be blocked in scenarios involving read-only mandatory fields.
Any changes would be introduced only in new versions of tasks, as altering the current behavior would constitute a breaking change for existing tasks.
Conclusion
At present, mandatory read-only fields do not restrict task completion by design. Customers who require stricter validation should plan for future task versions or raise a feature request for consideration in upcoming enhancements.