Bugfixes
eSS menus centre alignedBackground The menus in eSS were showing as centre-aligned not left-aligned. Update The CSS rules were updated and the buttons now show the correct alignment. |
- Standard security maintenance and fixes
Enhancements/Features
eSS user can now see when they have added a document to a T&Q competency when in pending statusBackground ESS users will provide updates to their training and qualifications from their self service portal. Along with updating their progress and completion dates, they can also upload file/s that provide confirmation of the training or qualification item. When users upload their file/s, and submit the change, the training will change into a pending status that is awaiting HR review and approval. At this stage the user is taken back to the competency listing page and cannot see what file/s they have uploaded. Updates We made an update so that now eSS users will be able to easily see which document/s they have attached to the pending training or qualification they made the update to. This allows eSS users to confirm that the document they uploaded attached properly and it is the correct file. |
Self Service Approvals - Pending competencies with document/s attached are removed on rejectionBackground Several users raised an issue where documents linked to training competencies were being uploaded to the employee document folder while still in self service approval staging area. If the staged changes were rejected (incorrect supporting document provided) the document was still present under the employee record instead of being removed. This lead to incorrect or unnecessary documents being uploaded to the worker record. Updates After this update, when a user rejects pending changes for a competency, the attached document/s will also be removed from the record in the |
iHUB integrations - Notification of errors by emailBackground Whenever an iHUB connector job is initiated, whether through a scheduled or manual run, errors and warnings may occur that require data correction in either the source or target systems to ensure proper synchronization. Currently, iHUB account admins must log into iHUB to be alerted about these issues. Therefore, we need to implement an email notification system that sends error information directly to iHUB account admins. Updates iHUB Account Admins with the 'iHubManageConnections' permission will receive emails for every run, whether initiated manually or on a schedule. The email body will include the Integration Name, Date and Time of Execution, Job Status, and a Summary of the job run. If there are any errors or warnings, detailed information will be provided in a table, including the Employee Name, Unique IDs from both Source and Target systems, and Error Details that require action. Error emails will be generated for all the connectors we have built today and in future. Note: No email will be generated when there aren’t any errors generated during the job run. |
Related to