January 2026 Release: ATSv2 Resolved Issues

Incorrect Translation for Custom Rejection Reasons

Translations for rejection reasons were incorrectly pulled from the managed field even when a custom field was in use, causing localization errors for non-English users.

The translation logic has been updated to be dynamic. The system now identifies which field is actively configured for rejection reasons and retrieves the corresponding translations from that specific field's metadata. This ensures that users see the correct language regardless of whether they are using the managed or a custom picklist.