Name Discrepancy Report Enhancements
This release addresses sorting and filtering issues within the Name Discrepancy (ND) Report, significantly improving usability and performance.
Resolved Issues:
- Incorrect Sorting: The ND Report now sorts the entire list chronologically by "Date Captured," from newest to oldest. Previously, only individual pages were sorted, leading to inconsistencies when navigating between pages. This fix ensures users can easily find the most recent entries.
Employee Profile Enhancement: Collapsed WGC Section
This release introduces a usability improvement to the Employee Profile page.
New Feature:
- Collapsed WGC Section: The Work Group Code (WGC) section on the Employee Profile page is now collapsed by default. This allows users to immediately see the employee's requirement status upon loading their profile.
Data Cleanup: Inactive Duplicate Past Positions
This release addresses an issue where duplicate past positions remained active on employee profiles. While the underlying cause was previously fixed, a data cleanup script has been implemented to correct existing instances across all accounts.
Data Cleanup:
A script has been run to identify and inactivate duplicate past positions for affected employees. The script ensures that only the position sent in the current day's Employee Demographic Upload remains in an "active" status
Enhancement: Increased Default Page Size
This release improves the user experience by increasing the default number of displayed records per page.
Enhancement:
The default page size for several sections within ECO has been increased from 10 to 50 records. This allows users to view and interact with more data at once, reducing the need for pagination and improving efficiency.
Bug Fix: Accurate Workgroup Code Updates from License Uploads
This release resolves an issue where outdated and incorrect workgroup codes (WGCs) were persisting on employee profiles after license uploads, causing inaccurate notifications and data inconsistencies.
Bug Fix:
Previously, the license upload process did not correctly handle WGCs marked as "inactive" in the EverCheck Admin settings. This resulted in inactive WGCs remaining associated with employees, even when they were no longer included in the upload file.
Resolution:
The license upload process has been updated to handle inactive WGCs correctly. It now differentiates between WGCs that have never been assigned and inactive ones. The upload will now successfully remove inactive WGCs from employee profiles.
Additional Improvement:
A new error message has been added to the bulk upload summary in EverCheck to notify users when a WGC has not been added to an employee profile due to its inactive status in EverCheck Admin.
License Export v2 Modernization
This release modernizes the components responsible for our License Export process, improving maintainability, scalability, and performance.
Benefits:
This modernization effort brings several benefits:
- Improved Performance: The updated components are expected to provide faster processing and response times for LCR Exports.
- Enhanced Scalability: The modernized architecture allows the system to better handle increasing data volumes.
- Increased Maintainability: The refactored code and updated dependencies make the system easier to maintain and update in the future.
- Enhanced Security: Updates to the API and Lambda functions include security enhancements to protect sensitive data.
Bug Fix: Accurate Handling of Past Positions on Employee Profile Updates
This release resolves an issue where outdated position information was not correctly moved to the "past positions" section on employee profiles after a position code update.
Bug Fix:
Previously, in some cases, when an employee's position code was updated to a new position, the old positions were not correctly moved to the "past positions" section of their profile. This resulted in employees having multiple active position sets, which was inaccurate.
Resolution:
The issue has been resolved. Now, when an employee's position code or workgroup code is updated on the employee upload, the old position code or set will be correctly moved to the "past positions" section.
Enhanced Upload Safety and Full-Refresh LCR Naming Convention
This release introduces a significant improvement to upload safety and a new naming convention for full-refresh LCR uploads, protecting employer data from accidental mass deletions.
New Feature: Upload Failsafe
A new failsafe mechanism has been implemented to prevent erroneous uploads from inadvertently clearing employee and LCR data. This safeguard compares the row count in the uploaded file with the existing record count in EverCheck. If the row count is less than 75% of the current record count, the upload process will be halted.
Failsafe Actions:
- Process Termination: The upload process will stop immediately if the 75% threshold is not met.
- Alerting: An alert will be generated to notify the EverCheck team of the failed upload.
- Feature Flag: A feature flag has been created to allow authorized users to enable/disable the failsafe on demand. This provides flexibility for processing uploads that may legitimately fall below the 75% threshold.
New Feature: Full-Refresh LCR Upload Naming Convention
To further enhance data integrity and prevent accidental full-refresh uploads, a strict naming convention has been implemented for these files. Full-refresh LCR uploads must adhere to the following format:
318_EvercheckFormat_MM-DD-YYYY.xlsx
Where:
318
is your employer IDEvercheckFormat
is a fixed string.MM-DD-YYYY
represents the date of the upload in month-day-year format.
Any full-refresh LCR upload that does not follow this naming convention will be rejected.
EverCheck Wallet - Enhanced Registration Security
This release enhances the security of Wallet registration by implementing two-field validation for email and password, ensuring users register with the correct information and create strong passwords for future logins.
New Features:
- Email Confirmation: A "Confirm Email" field has been added to the registration page. Users must enter their email address twice, and the two entries must match exactly.
- Password Confirmation: A "Confirm Password" field has been added to the registration page. Users must enter their password twice, and the two entries must match exactly.
- Password Strength Validation: The password field is validated for strength, requiring:
- A minimum of 8 characters
- At least one uppercase letter
- At least one number
- Password Strength Meter: A visual password strength meter has been added. It will display:
- Green: When the password meets all strength requirements.
- Red: When the password does not meet all strength requirements.
Comments
0 comments
Article is closed for comments.