Search and Match Mechanism

Revision as of 00:53, 1 December 2022 by Admin (talk | contribs) (Created page with "== Introduction == Not to be confused with the Search Mechanism, this mechanism allows system users to find suitable candidates for a Job Order from the internal candidate pool or find suitable Job Orders for a Candidate to apply to. == Compatibility == The Search and Match mechanism is designed to work equally well with 3B's own Job object or that of our partner ATS systems including TargetRecruit, BH4SF and others. When our system implementers configure the Searc...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Introduction

Not to be confused with the Search Mechanism, this mechanism allows system users to find suitable candidates for a Job Order from the internal candidate pool or find suitable Job Orders for a Candidate to apply to.

Compatibility

The Search and Match mechanism is designed to work equally well with 3B's own Job object or that of our partner ATS systems including TargetRecruit, BH4SF and others. When our system implementers configure the Search and Match mechanism, they can wire the target job object to any object on the system, allowing us to integrate with virtually any ATS system or even a custom object model.

Rules

The Search and Match mechanism does not come configured with any rules out of the box. During the process of scoping and discovery, our team members or SIs will identify the business rules needed to be evaluated by the Search and Match mechanism and they will be responsible for coding these in.

Design

We have designed the rule engine to work with "code block" rules, thus allowing you add virtually infinite complexity to the rules that are evaluated by the engine. Each code block is executed in the front end as a ES6 Javascript Module which is enabled communication to the server via the getData() API, similar to remoteUtils plugin.

Rule Structure

A rule is a code module that will accept a list of evaluated records (jobs or contacts) and will thus check if that list of evaluated records meet the criteria set out in the code.

Design Considerations

Since the rule engine executes in the front end, we cannot schedule background search jobs. Each search session has to be initiated by a user via the web-ui.

Rule Types

Since rules are code blocks, we support evaluating complex comparisons for objects and fields that may or may not belong to the 3B application suite. So, for example, if you use Sirenum by Bullhorn for shift scheduling, you can create a rule that grants points to a candidate that has had a shift for the Job's client in the past 90 days.