![]() | ||
Introduction
To align with the evolving needs of our clients and enhance the usability of our platform, we have received feedback highlighting the necessity to facilitate better communication directly with leave requestors. Specifically, clients have expressed the need to incorporate the leave requestor's email address within our system's interface. This additional detail will enable them to export this information conveniently for further correspondence, promoting efficiency in handling various operational processes. The leave requestor's displayed name already sources from the Users properties, indicating a straightforward integration for this new requirement.
A. Problem statement
Clients using our platform need to be able to directly communicate with leave requestors for various operational purposes. However, the current system does not display the email addresses of these requestors in an accessible manner, nor does it include these details in the exportable data sheets. This limitation hampers efficient communication and slows down process management, as clients have to manually retrieve contact information through secondary means.
B. Solution
To address this issue, we propose to add an "Email" column to the last position of the existing grid where leave requests are displayed. This column will pull email addresses directly from the Users properties, leveraging existing data to fill the new field. Furthermore, we will ensure that this new column is included in the data when the grid is exported. This enhancement will not only fulfill the clients' request for direct access to email addresses but will also streamline their communication and administrative tasks, by providing all necessary information in a single, exportable and easy-to-navigate format.
The plan is to implement the following enhancements to our system:
- Introduce an "Email" column at the end of the existing grid. This will ensure that users can visibly identify the email addresses of leave requestors directly from the interface.
- Guarantee that this new column is also included in the export functionality of the grid. This ensures that when clients export the data, it contains all necessary information, including the email addresses, facilitating seamless external communications and record-keeping.

C. Best Practices
- Data Consistency:
- Ensure that the email addresses sourced from the Users properties are regularly updated and accurately maintained. This guarantees that the information displayed and exported remains reliable and current.
- User Interface Clarity:
- Position the "Email" column at the end of the grid to maintain a clean and organized visual layout. Label the column clearly and distinctly to avoid any confusion, making it easy for users to identify and use.
D. Troubleshooting
- If your site is missing the email column, please reach out to support for help.
E. Related articles
Conclusion
In summary, responding to valuable client feedback has driven us to enhance our platform by incorporating the leave requestor’s email address into our system's grid display. This improvement will enable efficient export of these details, facilitating straightforward communication, and optimizing various operational processes. Given that the requestor's displayed name is already integrated from the Users properties, the implementation of this feature promises to be seamless. This proactive approach not only aligns with our commitment to meet the evolving needs of our clients but also significantly boosts the usability and functionality of our platform.
