Transfer HR case post Australia upgrade issue

[Gayathri Adoni]

Hi,

We recently upgraded from Yokohama patch 13 to Australia patch 2 and noticed onclick of Transfer case in "HR Agent workspace", a dialog appears and on selecting HR service COE auto populates but an error message "Field is invalid" appearing.

Attaching the screenshot for reference.

Any help on this would be appreciated.

 

[Ankur Bawiskar]

@Gayathri Adoni 

some other member also facing some issue in Transfer Case after Australia upgrade

The 'Transfer Case' in HR Agent Workspace not retrieving the list after the Australia Upgrade 

may be it's because of this PRB

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Tanushree Maiti]

Refer KB Article: KB2657082 Transfer Type Dropdown Not Populating in HR Agent Workspace 

Cause

A bug in the UX Client Script “Update available transfer types for HR case SRP” caused incorrect mapping of transfer types using output.map(type => ...) instead of output.methods.map(type => ...).

Resolution

To resolve the issue:

• Navigate to UX Client Scripts and locate Update available transfer types for HR case SRP.
• Update the script logic to use:

JavaScript

output.methods.map(type => ...)

instead of

JavaScript

output.map(type => ...)

• Test the fix in a development instance and validate that the Transfer type dropdown populates correctly.
• Apply the fix to higher environments following change management.

Refer to PRB1859289 for tracking the permanent fix from ServiceNow.

[Gayathri Adoni]

Hi,

I am not having issues with Transfer type field.

I am getting error even value is filled in COE.

Regards,

G

[jasonjohns5]

This issue is usually caused by a dictionary or reference qualifier mismatch after the upgrade from Yokohama Patch 13 to Australia Patch 2. In HR Agent Workspace, the “HR Service COE” field may still be referencing an old or invalid value, which triggers the “Field is invalid” message even though the COE auto-populates correctly. Please verify the dictionary configuration, reference qualifiers, and any custom client scripts/UI policies related to the Transfer Case dialog. Also, clear cache and test in a non-customized instance to confirm whether the issue is customization-related or a known product defect introduced after the upgrade.