Configure USAM Location Search

Within USAM there is the ability to search and filter candidatesClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. based on their location.

The Location facet section contains the Country dropdown, City textbox, Radius dropdown (disabled), and All/None links.

Rules

Location section works by following rules:

  • If a Country is selected then a breadcrumb Country with the selected value will be populated and the list of candidates will correspond to the selected criteria
  • If TKClosed An abbreviation for Textkernel autocomplete is enabled :
    • If Country & corresponding city are selected and fill the City then a list of available Postcodes with enabled checkboxes will be displayed.
    • City supports autosuggestion if the user inputs at least 3 symbols.
    • 1 or multiple Postcodes can be selected via checkboxes.
      • All/None links affect the checkboxes of PostalCodes - select all or deselect all respectively (limited to TK configured limits of 10)
      • Radius dropdown will be enabled only if a user selects only 1 value of PostCode
      • If Country, 1 City or Postcode, and Radius is selected, the TK search becomes a geolocation / semantic search (GPS coordinates based on TK)
      • City chips are used chips will be converted into breadcrumb/s (City or City&Zip Code) on the search and the Location Facet will be updated with breadcrumbs values and the list of candidates will correspond to the selected criteria.

Desired Location

Additional locations can be added to candidates if they have the mobility to work in different locations.

  1. Navigate to Setup > Custom metadata types > Search & Match UI Configuration Custom Metadata Type > Manage Records.
  2. Click the Enable Additional Locations checkbox.

    • Add the field to Metadata Layout if it’s not visible.
  3. Click Save.
  4. Add the Additional Location Related List Custom-Managed component to the Contact Record Page.
    • Make sure you update the following Page Layout and Fieldsets for the object Additional Locations:
      • Additional Locations Layout: Remove Date, Department, and Country (Deprecated). Add Country field.
      • Add New Additional Location Field Set: Remove Date and Department.
      • RelatedListFieldSet: Remove Date, Department, and Country (Deprecated). Add Country field.
  5. Mobility criteria can be utilized in a candidateClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider. search from the localization section by a switch toggle on the Location filter section.
    • If the Additional Location toggle is on, then in addition to candidates that corresponded by primary location, candidates whose additional location corresponds to the criteria populated in the Location filter will be added.

The Additional location breadcrumbs support all rules as location breadcrumbs.

Technical Note

For expected work of Additional Location functionality in USAM ensure the following:

Copy

Additional Location Code

<!-- Additional locations -->
<ItemGroup key="secondary_locations" bhtk:iterationObject="tr1__additional_locations__c" bhtk:iterationField="tr1__contact__c">
    <Item index="0">
       <Field key="city" bhtk:cdata="true" bhtk:field="tr1__city__c" bhtk:object="tr1__additional_locations__c">
           <Value />
       </Field>
       <Field key="country" bhtk:cdata="true" bhtk:field="tr1__countrynew__c" bhtk:object="tr1__additional_locations__c">
           <Value />
       </Field>
       <Field key="postcode" bhtk:cdata="true" bhtk:field="tr1__postal_code__c" bhtk:object="tr1__additional_locations__c">
            <Value />
        </Field>
    </Item>
</ItemGroup>
  • In Search & Match Configuration custom metadata field Monitored Additional Locations Fields is populated by the next fields:
    • [TR1__City__c,TR1__CountryNew__c,TR1__Postal_Code__c].
      • Add a field to Metadata Layout if it’s not visible.