On Premises

Additional configuration CRM Service for Bullhorn

Note

An additional AnywhereNow WebAgent for Voice or for Omnichannel license is required.

Below the optional configuration you can do to the CRM Service for Bullhorn.

PluginSettings

  1. Open the UCC A Unified Contact Center, or UCC, is a queue of interactions (voice, email, IM, etc.) that are handled by Agents. Each UCC has its own settings, IVR menus and Agents. Agents can belong to one or several UCCs and can have multiple skills (competencies). A UCC can be visualized as a contact center “micro service”. Customers can utilize one UCC (e.g. a global helpdesk), a few UCC’s (e.g. for each department or regional office) or hundreds of UCC’s (e.g. for each bed at a hospital). They are interconnected and can all be managed from one central location. Config page on SharePoint

  2. Open the Plugin Settings list

  3. The following optional settings can be added:

Setting Value Scope
ShowStatus

Show what kind of contact is calling. Can be a Contact, Lead or Unknown. Default True.

CrmService
DefaultPhoneNumberRegion

Iso 3166 alpha-2 code. Default ZZ.

CrmService
PhoneNumberFormat

The format used when searching the CRM when a call comes in. There are four values:

  1. E164 The E.164 phone number format is an international (ITU) standard for dialing telephone numbers on the Public Switched Telephony Network (PSTN). Loosely formulated, only "+" and upto 15 digits (0-9) are allowed For example: +4433221100 (For number notation/display and storage see the E.123 standard): e.g. +12345678. See “The International Public Telecommunication Number Plan”.

  2. International: e.g. +1 206-555-1234. Based on the E.123 The E.123 format is an international (ITU) standard for notation and storage of international telephone numbers, email addresses and web addresses. Loosely formulated, "+ ", digits, non alphanumeric characters (like brackets, hyphens) and spaces are allowed For example: +44 (333) 221-100 International format.

  3. Rfc3966 The rfc3966 format defines an international (IETF) standard for dialing (and storing) a telephone number as a URI. Loosely formulated, start the URI with "tel:" followed by an E.164 or E.123 formatted phone number. For example: tel:+44333221100: e.g. tel:+1-206-555-1234. See “The tel URI for Telephone Numbers”.

  4. Wildcard: do a wildcard search. Default.

Important: change this setting if phone numbers are stored in any of the other formats to improve performance. See Phone Number Recognition in Integrations for more information.

CrmService
BaseContactQuery

Contact query format has place holders to fields and filter conditions.

Copy
Query
search/ClientContact?BhRestToken={0}&fields={1}&query={2}&count=100
CrmService
BaseLeadQuery

Lead query format has place holders to fields and filter conditions.

Copy
Query
search/Candidate?BhRestToken={0}&fields={1}&query={2}&count=100
CrmService
BaseAuthCodeQuery

Authorization code query format has place holders to fields and filter conditions.

Copy
Query
/oauth/authorize?client_id={0}&username={1}&password={2}&response_type=code&action=Login
CrmService
BaseTokenQuery

Token query format has a place holder to a field.

Copy
Query
/oauth/token?{0}
CrmService
BaseLoginQuery

Login query format has place holders to fields and filter conditions.

Copy
Query
/rest-services/login?access_token={0}&version=*
CrmService
BaseCaseContactQuery

Case Contact query format has place holders to fields and filter conditions.

Copy
Query
search/JobOrder?BhRestToken={0}&fields={1}&query={2}&count=100
CrmService
BaseCaseLeadQuery

Case Lead query format has place holders to fields and filter conditions.

Copy
Query
search/JobSubmission?BhRestToken={0}&fields={1}&query={2}&count=100
CrmService
ContactCaseFilter

Contact filter format has place holders to filter conditions.

Copy
Filter
clientContact.id:{0}
CrmService
LeadCaseFilter

Contact filter format has place holders to filter conditions.

Copy
Filter
candidate.id:{0}
CrmService
CaseStatus

The mapping of a ticket (incident) status to a WebAgent status.

Copy
Mapping
Active=Open
Resolved=Closed
Canceled=Closed
In Progress=Open
On Hold=Open
Waiting for Details=Open
Researching=Open
Problem Solved=Closed

Left side is the formatted value as configured in SAP, the right side is either New, Open or Closed.

CrmService
UseDefaultPluginAttributes

Setting to overrule the default plugin attributes settings.

If this setting does not exist or the value is set to True then the default plugin attributes settings are used. If you want to overrule the default PluginAttributes settings just add this setting and set the value to False.

All PluginAttributes will have to be added manually if set to False.

CrmService

For the mandatory Settings see Add PluginSettings

PluginAttributes

This list contains the items which are shown to the user in the WebAgent and ID’s used to identity unique entities. All items are grouped by the Category.

Note

Only modify this list if you want to deviate from the default PluginAttributes. See Predefined PluginAttributes for the defaults and how to override these defaults.

The PluginAttributes list contains the following columns:

Column Meaning
DisplayName

Name of the property shown in the WebAgent.

SystemName

Must be an attribute from Bullhorn. If it is part of a linked entity then the alias must precede the attribute.

ShowOnExtensionWindow

Indicate that the property is visible in the WebAgent. The main reasons to set this to ‘No’ and still configure it as an item is when the property should not be shown, but is used in a Hyperlink or it’s an ID.

Order

The order in which the property is to be shown.

Important: counting must restart for each Category.

FieldType

Zero or more field types, these are covered per Category later on.

Hyperlink

Make the property clickable with the Hyperlink specified. It is possible to include the value of a property in the Hyperlink. This is done by putting the value of a SystemName property in square brackets in the Hyperlink. For example if there is a property with the SystemName ‘Example’, then the URL becomes: http://www.example.com/?queryString=[Example]

OpenAutomatically

Ignored by the CrmService.

Category

The Category that determines for which search query it has to be used. Supported are Contact, ContactSearch, Case and CaseSearch.

ShowOnToast

Can be used to force the inclusion of the attribute in the query.

It is possible to combine the values of several properties, for instance when a name is split up in multiple properties, e.g. a FirstName and LastName column. In this case both properties should have the same DisplayName and they should appear after each other in Order, e.g. 1 and 2.

Contact

The items in this category are the properties shown of a single contact. It supports the following field types:

Field type Description
Id

This field type in combination with a value in the Hyperlink column, will be shown as CRM link.

Name

The name of the contact which will be shown as the contact’s title.

PhoneNumber

Column may contain a phone number.

SipAddress

Column may contain a SIP The Session Initiation Protocol, or SIP, is a protocol for multimedia communication (audio, video and data communication). SIP is also used for Voice over IP (VoIP). SIP has interactions with other Internet protocols such as HTTP and SMTP.-address.

Email

Column may contain an e-mail address.

Date

Column contains a date (and time).

Search

Column is searchable. This type should be set for each column containing a PhoneNumber, Email or SipAddress to search for a contact match. This type will also mark a field as a search option if no ContactSearch items are configured.

ContactSearch

This category is used to display a summary of the contact and used for searching contacts. All properties which should be searchable, must have the Search field type. The column containing the values to verify the identity of the caller, e.g. a zip code, must have the field type Verify.

Lead and LeadSearch

See Contact with regards to Lead and ContactSearch for LeadSearch.

Case

Note

Only contacts can have cases.

The DisplayNames in this category are fixed. The following items are supported:

DisplayName Description
Title

Multiple items can have this DisplayName. Must have the Name field type.

Description

Only a single item is allowed to have this DisplayName.

Date

Must have the Date field type to be used.

Status

The case status including the case status colors. The values must match the CaseStatus setting. Add field type FormattedValue to obtain the display name of this property.

It is also possible to add a ID field type to an ID item or any of the other items. The ID field type in combination with a URL in the Hyperlink column will be shown as a CRM link for each case.

CaseSearch

These must have the same items as the Case category. The difference here is that items may have the Search field type.

Predefined PluginAttributes

Note

These predefined attributes may be overwritten/removed by creating a PluginAttribute item in SharePoint with the same SystemName and Category. Do not give it any field types and set both ShowOnExtensionWindow and ShowOnToast to No to remove this attribute from the query. Also make sure that the system name is not included in any hyperlink!

Note

The base queries in the PluginSettings list must also be modified when adding attributes of another entity.

Case

DisplayName SystemName Order ShowOnExtensionWindow FieldTypes HyperLink ShowOnToast
Case ID id 0 No Id [HOSTURL]/BullhornSTAFFING/OpenWindow.cfm?Entity=JobOrder&id=[id] Yes
Title title 1 Yes Name, Search    
Description description 2 Yes      
Date dateLastModified 3 Yes Date    
Status status 4 Yes FormattedValue    

Contact

DisplayName SystemName Order ShowOnExtensionWindow FieldTypes HyperLink ShowOnToast
Id id 0 No Id [HOSTURL]/BullhornSTAFFING/OpenWindow.cfm?Entity=ClientContact&id=[id] Yes
Name name 1 Yes Name   No
Email email 2 Yes Email, SipAddress   No
Phone phone 3 Yes PhoneNumber   No
Occupation occupation 4 Yes     No
Address address 5 Yes     No
Office office 6 Yes     No
Division division 7 Yes     No
PreferredContact preferredContact 8 Yes     No
ReferredByPerson referredByPerson 9 Yes     No
Category category 10 Yes     No
Description description 11 Yes     No
ReportToPerson reportToPerson 12 Yes     No
Comments comments 13 Yes     No
Phone2 phone2 14 Yes PhoneNumber   No
Phone3 phone3 15 Yes PhoneNumber   No
Mobile mobile 16 Yes PhoneNumber   No
Email2 email2 17 Yes Email, SipAddress   No
Email3 email3 18 Yes Email, Sipaddress   No

Contact Search

Category Contact is used to map fields from the Bullhorn record. Category ContactSearch is used to define which fields will be used in a search.

DisplayName SystemName Order ShowOnExtensionWindow FieldTypes HyperLink ShowOnToast
Name name 0 No Name, Search   Yes
Email email 1 No Email, Search   Yes
Email2 email2 2 No Email, Search   Yes
Email3 email3 3 No Email. Search   Yes
Phone phone 4 No PhoneNumber, Search   Yes
Mobile mobile 5 No PhoneNumber, Search   Yes
Phone2 phone2 6 No PhoneNumber, Search   Yes
Phone3 phone3 7 No PhoneNumber, Search   Yes
Id id 8 No Id, Search   Yes

Lead

DisplayName SystemName Order ShowOnExtensionWindow FieldTypes HyperLink ShowOnToast
Id id 0 No Id [HOSTURL]/BullhornSTAFFING/OpenWindow.cfm?Entity=Candidate&id=[id] Yes
CompanyUrl companyURL 1 No     Yes
Name name 2 No Name   Yes
Email email 3 Yes Email, SipAddress   No
Phone phone 4 Yes PhoneNumber   No
Occupation occupation 5 Yes     No
Address address 6 Yes     No
Salary salary 7 Yes     No
CompanyName companyName 8 Yes     No
Type type 9 Yes     No
EmploymentPreference employmentPreference 10 Yes     No
PreferredContact preferredContact 11 Yes     No
Owner owner 12 Yes     No
Comments comments 13 Yes     No
Description description 14 Yes     No
TravelMethod travelMethod 15 Yes     No
TravelLimit travelLimit 16 Yes     No
ReferredBy referredBy 17 Yes     No
Phone2 phone2 18 Yes PhoneNumber   No
Phone3 phone3 19 Yes PhoneNumber   No
Mobile mobile 20 Yes PhoneNumber   No
WorkPhone workPhone 21 Yes PhoneNumber   No
WillRelocate willRelocate 22 Yes PhoneNumber   No
Email2 email2 23 Yes Email, SipAddress   No
Email3 email3 24 Yes Email, Sipaddress   No

LeadSearch

Category Lead is used to map fields from the Bullhorn record. Category LeadSearch is used to define which fields will be used in a search.

DisplayName SystemName Order ShowOnExtensionWindow FieldTypes HyperLink ShowOnToast
Id id 0 No Id, Search   Yes
Name name 1 No Name, Search   Yes
Mobile mobile 2 No PhoneNumber, Search   Yes
Email email 3 No Email, Search   Yes
Email2 email2 4 No Email, Search   Yes
Email3 email3 5 No Email. Search   Yes
Phone phone 6 No PhoneNumber, Search   Yes
Phone2 phone2 7 No PhoneNumber, Search   Yes
Phone3 phone3 8 No PhoneNumber, Search   Yes
WorkPhone workPhone 9 No PhoneNumber, Search   Yes

Submission

DisplayName SystemName Order ShowOnExtensionWindow FieldTypes HyperLink ShowOnToast
Submission ID id 0 No Id, Search [HOSTURL]/ BullhornSTAFFING/OpenWindow.cfm?Entity=jobOrder&id=[id] Yes
Title jobOrder.title 1 Yes Name, Search    
Description jobOrder.description 2 Yes      
Date dateLastModified 3 Yes Date    
Status status 4 Yes FormattedValue    

SubmissionSearch

DisplayName SystemName Order ShowOnExtensionWindow FieldTypes HyperLink ShowOnToast
Submission ID id 0 No Id, Search [HOSTURL]BullhornSTAFFING/OpenWindow.cfm?Entity=jobOrder&id=[id] Yes
Title jobOrder.title 1 Yes Name, Search