This feature prompts users to add a note when rejecting a task in Zenople. It ensures that a clear and standardized reason for task rejection is captured and visible for future reference.
Functionality
- Where it appears:
- The feature appears at the point of task action when a user selects Reject on a task.
- Applicable Zenople modules:
- Applies to all Zenople tasks across relevant modules where task rejection is available.
- New UI elements or settings:
- A new input field labeled “Rejection Reason” appears next to the Reject action when selected.
- The field has a character limit of 500 characters, consistent with the existing Task Note field.
- User interaction behavior:
- When a user selects Reject, the Rejection Reason field is displayed.
- The field is mandatory or non-mandatorybased on the option property configuration:
- Entity: Office
- Option: Common
- Option Property: Mandatory Task Rejection Note
- Option Values: Yes / No
- Default Value: No
- Show in UI: True
- Description: Defines whether task rejection notes are mandatory for all Zenople tasks.
- Upon submission:
- The entered reason is added to the Task Note, prefixed with “Rejection Reason”.
- The note adheres to both the field character limit (500) and the existing Note column display limit (approximately 54 characters followed by “…”).
- The rejection reason is displayed in the Note column of the task.
- The same note is also published to Comments on the related entity.