Resolved Issues

Candidate Experience: Duplicate Translation Key Display in Applicant Profile

We resolved an issue where the duplicate_phone translation key was displayed twice under the phone number field in the Applicant Profile when the ‘Disable International Phone Numbers’ system setting was turned OFF. Now, the message only appears once, providing a clearer experience.

Candidate Experience: SMS Notifications for Applicants with International Phone Numbers

We resolved an issue where applicants with international phone numbers were not receiving their SMS notifications. This update ensures proper storage and formatting of phone numbers within the Talent Platform, improving communication processes and ensuring all applicants receive their notifications as expected.

E-Signature: ‘Add Representative Later’ Display Correction

We resolved an issue where the ‘Add Representative Later’ option for multi-signers on forms (excluding I-9s) incorrectly displayed ‘ES Temporary Signer’ instead of the representative’s name. The correct name now appears, avoiding delays and re-signing.

E-Verify: Intermittent E-Verify Error Message Displayed Despite Valid Reason for Delay Code Selection

We resolved an intermittent issue where the reason for delay error message appeared despite a valid reason for the delay code being selected. This impacted various codes but did not affect auto-order cases or cases created by automations.

Form I-9: Authorized Representative SMS Notification for Form I-9

We resolved an issue in both Staging and Production where the “Proceed to Section 2” button was unresponsive when an Authorized Representative received an SMS notification. This fix now ensures proper navigation to Section 2, allowing Authorized Representatives to complete their tasks without issues.

Order Workflow: Incorrect Splitting of Forms in Packages

We resolved an issue where forms resent from a single package were incorrectly split into multiple packages when “Enable Re-Use of Signed Forms in Packages” was enabled. Forms are now correctly grouped into a single custom package based on expiration dates.

Work History: Multi-Check Field Behavior in Applicant Portal

We resolved an issue where multi-check fields (datatype_id = 19) were not behaving consistently in the Applicant portal. Previously, when applicants edited an existing Work History entry, the values in the multi-check field were not automatically re-checked, but now they are correctly retained and displayed, preventing the field from being saved as null.

Top