Skip to content
Textkernel Saleforce Connector
Search and Match recruiter workflows
latest

Configure Search and Match workflow integrationπŸ”—

Once the automatic indexation process is configured, the next step is to configure workflows so that Recruiters working in Salesforce can use the Textkernel’s indexed Search and Match data to quickly find the relevant Candidates/Vacancies, and then trigger relevant inside Salesforce.

Your particular workflows will be custom to the way you work in Salesforce, but Textkernel provides several generic integration mechanisms to enable you to quickly build integrated workflows.

There are two different matching workflows available:

  • Automatch components: inside the Textkernel Connector managed package, we include some automatic-matching widgets that present top match results inside Salesforce. The automatch components are optimized to allow recruters to take quick action on the matches.

  • Unlocked sample components: we also provide some example workflow components in an unlocked package. These are open-source code, so you can re-use these components as-is, or you can copy them and customize them if you want different functionality. The unlocked components always redirect the users to the full Search UI, where they can investigate the match results and tune them.

You may prefer one workflow approach over the other. Or you might configure both workflows

Auto Match componentsπŸ”—

User interactionπŸ”—

Auto Match CandidatesπŸ”—

Scenario: Recruiters see this component whenever they open the Vacancy. They can click on the configurable action button "Add to List" to trigger a Platform Event with the selected Candidates. (All are selected by default). Alternatively, they can Click on View all in Textkernel to see the entire match results, adjust the match query, and/or trigger other workflow actions that are available in the Textkernel Search environment.

Automatch Candidates

Two automatic matching components are included in the managed package: 1. Textkernel Auto Match Candidates: component for the Vacancy page that shows the top N matching Salesforce Candidates for the Vacancy 2. Textkernel Auto Match Vacancies: component for the Candidate page that shows the top N matching Salesforce Vacancies for the Candidate

Both Auto Match components support a configurable Action button. This Action is configured for the most common workflow a Recruiter wants to use to apply the match results. Once configured, the user can select the desired matching records and click the Action button. The Action button generate a Salesforce Platform Event for the Group Action. (See the section below discussing group record workflow actions. The Auto Match widgets generate the same type of Platform Event structure).

Auto Match VacanciesπŸ”—

Scenario: Recruiters see this component whenever they open the Vacancy. They can click on the configurable action button "Add to List" to trigger a Platform Event with the selected Candidates. (All are selected by default). Alternatively, they can Click on View all in Textkernel to see the entire match results, adjust the match query, and/or trigger other workflow actions that are available in the Textkernel Search environment.

Automatch Vacancies

Configuring the auto match componentsπŸ”—

Configuring both Auto Match components for Search accessπŸ”—

Both Auto Match components query the Textkernel Search environment in the background, and this is the first thing to configure.

Search Configuration

Go to Salesforce Setup --> Textkernel App --> Search and Match Setup --> UI Component Settings

  1. Under Search endpoint, enter the value that Textkernel support provided for your environment.

  2. Under Job search environment enter the values that Textkernel support provided for your environment.

  3. Under Candidate search environment enter the values that Textkernel support provided for your environment.

  4. Be sure to Save all these changes.

Now the Auto Match components can query the Textkernel Search environment.

Textkernel Auto Match Candidates componentπŸ”—

Configure Automatch Candidates

(This procedure assumes you have a Lightning Record page for the Vacancy Page)

  1. Select a specific Vacancy Record
  2. Go to Setup -> Edit Page, to open the Lightning App Builder for your Vacancy Record Page
  3. Drag the Custom-Managed Component Textkernel Auto Match Candidates onto the desired page location
  4. Select the component, so that you see the configuration choices on the right-hand side:

    • Visible Fields: type in a comma-separated list of API field names from your Candidate Object. The first field is special and should be the record name, since it will be the header for each match result. The intent is to include the most critical data, so that the match results can be quickly read by the recruiter

    • Number of Results: pick an integer to configure the limit on how match results you want to display on the page. (You can show up to 20 results)

    • Action Button Label: this is the text label which will appear on the Action button

    • Action Button API Name: this is the Action Name that will be used for the Platform Events generated when the Recruiter presses the action button. Setting this enables you to see that the Platform Event was triggered by this component

    • Click Save to save your changes.
    • Return to your Vacancy record and now users with access to the component will see the match results whenever they view a Vacancy.

Textkernel Auto Match Vacancies componentπŸ”—

The procedure to configure this component is analogous to the other widget. This component should be to the Candidate page. The component is added to the page using the Edit Page process, and the fields are similar, except the visible field list includes field names from the Vacancy object instead of the Candidate object.

Configure Automatch Vacancies

Configuring the Unlocked Sample Component packageπŸ”—

Install Unlocked PackageπŸ”—

Install the unlocked package and enter the password (see package descriptions). This package should be installed for all users.

You should also assign users access to the included permission set: Textkernel - Unlocked Components Access.

Trigger Textkernel Match (from Salesforce Candidate/Vacancy)πŸ”—

Scenario: Recruiter inside Salesforce, viewing a Vacancy record, can click a button, which redirects the user to TK Portal and loads match results displaying the Candidates which are the best match for that Vacancy. The reverse match is also supported (trigger Vacancy match starting from the Candidate record in Salesforce.

Configuration: Add a Quick Action to the Vacancy (or Candidate) Layout inside Salesforce.

The package includes 2 Lightning components which you can reference in your page layouts:

  • searchCandidates: call this from your main Vacancy page layout to find Candidates matching the Salesforce Vacancy record
  • searchJobs: call this from your main Candidate page layout to find Jobs matching the Salesforce Candidate record

Each of these 2 Lightning components constructs a redirect URL to send the Salesforce Recruiter user to TK portal, and adds the Salesforce Candidate/Vacancy record ID as a parameter to pass the Salesforce context into Textkernel so that the user sees appropriate matching search results.

Go to SFDC Setup β†’ Object Manager β†’ Candidate/Vacancy β†’ Buttons, Links and Actions β†’ New Action

Select the following settings:

  • Action Type: Lightning Component
  • Lightning Component: select either searchCandidates or searchJobs
  • Label: pick an appropriate label for the action button
  • Name: pick an appropriate API name for the action

Define Action

Now add the quick action button to your Candidate/Vacancy page layout.

  1. Add created quick actions to Layouts:
  2. Go back to Candidate/Vacancy Object β†’ Page Layouts section β†’ select your Layout
  3. From Mobile & Lightning Actions drag the new quick action and drop it to Salesforce Mobile and Lightning Experience Actions section where you want to display it
  4. Save the layout.

Workflow integration to use Textkernel Portal match results inside SalesforceπŸ”—

When Recruiters are working in TK Portal, they usually want to take a list of interesting Candidates/Vacancies, and take useful workflow actions in Salesforce. They might have started directly in TK Portal, been directed there by opening an email alert, or been redirected there by one of the match components.

This next section describes how to configure these workflows.

Single record workflow actions (from TK search results)πŸ”—

Scenario: user selects a single record in the Textkernel search/match query results, and clicks on a button inside TK Portal to complete the workflow for that record in Salesforce. Supported workflows are listed below. These actions are both implemented as a redirect which opens a new browser tab displaying the appropriate page to the Recruiter.

  • Open Vacancy record detail page inside Salesforce
  • Open Candidate record detail page inside Salesforce

These buttons work without additional configuration needed in Salesforce.

Group record workflow actions (from TK search results)πŸ”—

Scenario: user selects a group of records in the Textkernel search query results, and triggers an action against the set of selected Salesforce records. The workflow is completed when the Salesforce org handles the request which passes the relevant data to Salesforce, and then some workflow action is taken against the group of records. This offers a generic interface to offer workflows for a set of IDs, such as adding a list of Candidates to an email automation workflow, or change a data-field on a set of candidate records inside Salesforce).

For Group records, the package generates a Salesforce Platform Event, called Textkernel Portal Action which includes the following data:

  • Action name (name of the action triggered inside TK Portal, to indicate what to do with the list)
  • Selected records (comma separated list of record ids saved in long text field on platform event)
  • Object API Name of selected records
  • Parent record (Vacancy Id or Candidate Id which initiated the search in Textkernel)
  • UserId (Id of current interactive user)

To integrate with the Platform Event, create a Platform Event-Triggered Flow process that runs in the background to consume the Platform Event when it occurs and feed into the workflow process without user interaction. You can use standard Flow features to send notifications to users, so that they know whether it completed or if there were errors.

New Flow popup

Platform Event popup

An example of a Flow is included in the unlocked package, which is called: Textkernel - Portal Action - Create Textkernel List. This example flow writes the list of IDs to a Textkernel List custom object. You can copy this and change it to suit your needs and build other workflows. For example you could write to other data model elements specific to your ATS, or trigger an email workflow.

Info

More details about monitoring Textkernel Platform Events are provided in the Operational Guide