Resource Status in Resource Management Workspace sometimes displays Pending in French

[mah1]

Yokohama Patch 6

Resource Management Workspace v5.2.0

After upgrading to Yokohama Patch 6 and updating the Resource Management Workspace plugin to v5.2.0, we noticed that Resource Status is sometimes showing in French instead of English. This seems to happen when Group by is None.

But if we select a Group by, then resource status En attente displays as Pending.

Any ideas how to resolve this?

Thank you!

[M Iftikhar]

Hi @mah1 , 

It looks like what you’re seeing is related to how translations are handled in Resource Management Workspace with Yokohama Patch 6 + v5.2.0.  

A few things to check: 

• sys_choice records  

Go to System Definition> Choice List and check the resource_status field on the Resource Assignment [sn_plng_att_core_resource_assignment] table. Make sure there’s an active English value for “Pending.” If only the French translation is active, or the English one is inactive, the UI may show “En attente.” 
 

• Fallback property  
  Confirm glide_i18n.language_fallback_enabled is set to true so missing translations fall back to English. 
  Set a fallback language 

• User language / locale  
  For the specific users seeing resource status in French, check their user profile language preference and browser locale. 

• Plugin repair  
  Run a repair on Resource Management Workspace[sn_rm_ws] v5.2.0 in case some translation or sys_choice records were missed. 

• Known issue check   
  Could be a bug in v5.2.0. If unresolved, log a case with ServiceNow Support. 

Thanks & Regards,  
Muhammad Iftikhar  

If my response helped, please mark it as the accepted solution so others can benefit as well. 

[mah1 · Accepted solution]

Thank you. I opened a case with Now Support on this issue. 

ISSUE: Resource Status in Resource Management Workspace sometimes displays Pending in French

SOLUTION PROPOSED: ServiceNow engineers investigated and identified as solved.  This issue was being tracked under PRB1930545.

NEXT STEPS: The issue is with Resource Management Workspace 5.2.0 version where Move button is introduced. The fix is planned for the 2025-12-04 release of the Resource Management Workspace.  The dev team does not have a workaround at this time given that the functionality is still working.