We've included a Rejected Task Status in our Org. Both, Completed and Rejected are considered a Closed Task Status.
If a user selects Rejected for the Task Status, they are required to put in a Rejection Resaon from a picklist. If they select Other, then they are required to enter information in the Rejection Reason Other text field.
When a user clicks the Mark Complete Action on a Task, a modal opens with the Status picklist field displaying. If the user selects, Completed, then they can click Save in the model and are finished. However, if the user selects, Rejected, the Rejection Reason picklist field must be updated but since it is not in the modal, there is no way to update Rejection Reason.
QUESTION: Is it possible to customize the standard Mark Complete Action so the when the Mark Complete modal opens, and the user selects Rejected for the Status, then the Rejection Reason picklist field displays in the modal below the Task Status picklist and is required. And, if the user selects Other as the reason for the rejection, then the Rejection Reason Other text field will display and be required as well?
If the above is not possible, I guess my only other option would be to create custom Action on the Task Object, correct?
Hi Stephen,
The standard Mark Complete quick action uses a fixed mini page layout, not a Lightning record page, so Dynamic Forms' conditional field visibility doesn't apply to it. That feature only works on full Lightning record pages (Record Detail/Field Section components in App Builder), not quick action modals. So there's no admin-only way to make Rejection Reason and Rejection Reason Other conditionally appear inside that specific modal.
Your path forward: build a custom Screen Flow as a Quick Action (Object-Specific Action on Task, Action Type = Flow). In the flow:
- Screen 1: Status picklist
- Decision element checking Status = Rejected
- Screen 2 (conditional path): Rejection Reason picklist, required
- Decision element checking Rejection Reason = Other
- Screen 3 (conditional path): Rejection Reason Other text field, required
Replace the standard Mark Complete button with this custom action on the Task page layout/list view action bar (you can keep both if some users still just need simple Completed with no extra fields — the flow can handle both paths in one action).
This is the standard, fully-supported way to get conditional required fields on a Task status change — no code needed, just Flow Builder.
