October 2025 Release: USAM Resolved Issues

October 2025 (2025.10 GA Release - Package Version 9.21)

File Types Supported By Global Parser Are Ignored By Resume Manager Upload

Users that have OCR parsing enabled in their Textkernel environment reported that they could successfully parse Jpeg, jpg and png file types using the global action for parsing, but that they would get an error when attempting the parsing of the same files from the Resume Manager. This has been resolved.

USAM Tag Clouds Search Automatically After Selection

In USAM, we resolved an issue where searches did not automatically execute after selecting Tag Cloud values, requiring users to manually click the Search button.

Previously, when users selected a Tag Cloud option from any category (Skills, Industries, Job Titles, etc.), the system would not automatically trigger a search, forcing users to take the extra step of clicking the Search button to see filtered results.

Tag Cloud selections now automatically execute a search and display updated results.

Administrators can control this behavior through a new Enable Tag Cloud Autosearch checkbox in the Search & Match UI Configuration custom setting, which is unchecked by default to preserve existing workflows.

USAM Tag Clouds Multiple Tag Selection

In USAM, we resolved an issue where Tag Cloud values became unavailable after selecting an initial Tag Cloud.

Previously, when users selected a Tag Cloud value and performed a search, all other Tag Cloud categories became unavailable, preventing users from selecting additional Tag Clouds to refine their search.

Users can now select multiple Tag Clouds from different categories to build cumulative searches and refine their results.

TrashIt button doesn't work for Application Search

Users reported that when trying to delete breadcrumbs after a search based on the ApplicationClosed First stage of Job placement flow (Application> Submittal>Interview>Offer> Placement) Search facet, the breadcrumbs would not always or all be deleted.

This was qualified as a bug and has now been fixed in the code. No configuration required.

Remove inaccurate numerical values from tag clouds

We resolved an issue where the Tag Cloud filter dropdowns in USAM displayed inaccurate numerical values. Tag Cloud filters now display filter options without any numerical values, providing a cleaner experience. The accurate count is still shown in the USAM tabs after a filter is applied.

Missing X on send email from USAM Job search results

When users tried to send an email from the Job Search results page in USAM, the Send Email pop-up modal was missing the 'x' icon in the top right corner to close it. This has been fixed.

Bulk Adding to Call List does not add all records from USAM

Users reported that when selecting records across multiple pages in USAM search results to add to a call list, not all selected records were being added. The issue occurred when selecting records on a page for the first time before the next page of results had loaded. This bug has been fixed.

Custom Action Modals Now Close Properly

Users reported several instances where custom action modals, opened from the USAM search result page, would not close properly and remained on screen.

The root cause was identified as inconsistencies in the logic within the Mass ActionClosed When used in ATS or Search and Match UI, one of multiple actions available after user has selected a sub-set of Candidates Setting Custom Metadata Type. Refactoring of the Display Type picklist options for this setting was necessary. Please note that you may need to update this setting when upgrading to this release.

Specifically, when the Display Type picklist in Mass Action Setting is blank (set to 'None'), the custom component itself must specify the custom action's display behavior, including how it closes. Previously, we incorrectly indicated that a blank Display Type picklist would result in the same behavior as selecting the 'Modal' picklist value.

The available options in the Display Type picklist are:

  • None: The display behavior is determined by the custom component.
  • Modal: The component will be wrapped with modal markup.
  • New Tab: A new tab will open with the specified URL.
  • Docked: The component will appear in a docked window.

If you use custom actions or components, please review and potentially update this configuration.

Additionally, while the HelpText has been updated to reflect these logical changes, the new HelpText is only visible in new organizations upgrading to this BHRC package for the first time. You will need to manually update the HelpText in existing organizations.

Post Deployment Steps/Configuration

We updated how Display Type field of Mass Action Setting custom metadata type is handled when the value is empty. Now if it is empty (--None--) it is a component responsibility on how it is displayed and acting. So if it's modal it should handle close action by its own.

If custom component should be wrapped with a modal markup its Display Type should be set to Modal.

"Enable Additional Location" Setting Not Respected

When the Enable Additional Location setting was unchecked, the toggle for additional locations was still being displayed.

The system now correctly hides the toggle when the setting is disabled, ensuring that the UI behavior aligns with the configuration.