| Analytics Data Segregation |
Alongside the personnel job types change, Engage Analytics can be set up to segregate data based on user settings |
March |
| Personnel Job Types |
The list of job types in Personnel should come from all the potential job types personnel could be in, based on their site access, instead of just the job types at the current site |
March |
| Map custom fields to CLIENTS |
As per ingestion feed Specification document for CLIENTS we are going to support additional 5 custom columns |
March |
| Add Domain Validation |
In the production site, while adding the users, Engage will verify the user’s email address for a valid domain (configured at the tenant level). |
March |
| Custom Task Always Add Option |
Adding a checkbox to a custom task, which would determine if the task is automatically added or not |
March |
| Improved Virus Scanning |
The current virus scanning, which ensures the safe upload and download of documents, has been improved for performance and cost |
February |
| Improved Access Validation |
In the production site, while adding users, the Engage platform will now verify the user’s email address to ensure it is a valid domain. This means you can no longer provide just any domain name in the user email address (like gmail, etc.) |
February |
| Federated Authentication (New Feature) |
In the production and portal sites, users can now log in using their own organisation user accounts |
January |
| Engage Analytics (New Feature) |
In the client portal, users can now access the reports and analytics functionality |
January |
| Re-submit / Clone Restriction (New Feature) |
In the portal site, when client users provide feedback, the system can now restrict them from either re-submitting or cloning a request |
January |