Jobrock Apex classes
This article provides a comprehensive overview of the available Jobrock Apex classes.
Available Apex classes in Jobrock SF package
Send Vacancy
Purpose:
By default, a user can sync a job manually to Jobrock via the Hub widget located on the Job page in SF. If you want to sync a job to Jobrock based on a different kind of trigger, for example, a status field of a job, this flow needs to be set up
Details:
| Action Name | Send Vacancy Details |
|---|---|
| Apex Class | Send Vacancy Details |
| Apex Variables | Vacancy Id ---> Your ATS Job ID |
| Status & Client Code | Offline ---> The status of the job. By marking it offline, Jobrock will not consider it anymore. The value should be True/False Client Code ---> SelectedBrand (if multi-brand is enabled) |
SendApplicationStatus
Purpose:
This is needed so Jobrock can listen to these status changes and use them as triggers for several processes. When you set this up, ensure not only workflow status changes are sent, but also the initial status allocation e.g. New.
Details:
| Action Name | Send Application Status |
|---|---|
| Apex Class | Send Application Status |
| Apex Variables | Vacancy Id ---> Your ATS Job ID |
| Application Id ---> Your ATS Job Application ID | |
Status ---> The name of the status that got updated in the job application Client Code ---> Selected Brand (if multi-brand is enabled) Workflow ---> Workflow label |
SendGAApplication
Purpose:
In case the UTM information was not passed along with the job application information, you can use this as a fallback to retrieve UTM information from the Google Analytics API connection configured in Jobrock.
Details:
| Action Name | Sync GA Lead |
|---|---|
| Apex Class | Sync GA Lead |
| Apex Variables | Application Id ---> Your ATS Job application ID |
GA Client Id ---> The GA client ID. This is a numeric value Client Code ---> SelectedBrand (if multi-brand is enabled) |
SendAutomationAppointment
Purpose:
You can use this to send a flow template that is desired to be triggered at a particular trigger moment. E.g. send an automation when somebody has started their new job for 3 weeks, an NPS at a certain moment, etc.
Details:
| Action Name | Send Automation/Appointment |
|---|---|
| Apex Class | Send Flow Template |
| Apex Variables | Record Ids ---> Comma-separated Application or Candidate Id (eg. a,b,c) |
| Action Type ---> This is a fixed value: Automation or Appointment | |
| Configuration Id ---> Available in JR Flow Templates Configuration Page | |
Object Type ---> This is a fixed value: Application or Candidate Client Code ---> Selected Brand (if Multibrand is enabled) |
JobrockApplicationHandler
Purpose:
You can use this to send a status that is desired to be triggered at a particular trigger moment.
Details:
| Action Name | Send Status |
|---|---|
| Apex Class | Send Status |
| Apex Variables | Record Ids |
| Vacancy Id | |
| Vacancy Title | |
Status Client Code ---> SelectedBrand (if multi-brand is enabled) |
JobrockSendContact
Purpose:
You can use this to update a contact that is desired to be triggered at a particular trigger moment.
Details:
| Action Name | Update Candidate |
|---|---|
| Apex Class | Update Candidate |
| Apex Variables | Candidate Id Client Code ---> SelectedBrand (if multi-brand is enabled) |
SyncPoolContact
Purpose:
You can use this to sync contacts that are desired to be triggered at a particular trigger moment.
Details:
| Action Name | Sync Pool Contact |
|---|---|
| Apex Class | Sync Pool Contact |
| Apex Variables | Contact Id |
| Pool Name | |
| Team Id | |
| Task Id | |
| Task Date (YYYY-MM-DD) | |
Recruiter Email Client Code ---> SelectedBrand (if multi-brand is enabled) |
Sync Profile
Purpose:
You can use this to sync a user that is desired to be triggered on a particular trigger moment.
Details:
| Action Name | Sync Profile |
|---|---|
| Apex Class | Sync Profile |
| Apex Variables | User Id |
Is Deleted -> True/False Client Code ---> SelectedBrand (if multi-brand is enabled) |
Send Message
Purpose:
You can use this to trigger email, sms, and WhatsApp to the contact.
Details:
| Action Name: | Send Message |
Required |
|---|---|---|
| Apex Class: | Send Message | Required |
| Contact Id -> | Contact record id or job applicant record ID. | Required |
| Recruiter Id-> | Only relevant for email communication. This will add the recruiter-specific signature. Use the relevant SF user record ID for this field. The signature is only supported when the user is already synced to Jobrock. | (optional) |
| Communication Type-> | Whatsapp, SMS, Email | Required |
| Message-> | Content of the message |
Required (when sending SMS or email) |
| Subject-> | Email subject |
Required (when sending email) |
| Object API Name-> | The Salesforce contact object API name or the job applicant object API name. |
Required |
| Email-> | Only used for email messages | Required (when sending email) |
| Phone-> | Only used for Whatsapp and SMS | Required (when sending Whatsapp or SMS) |
| TemplateLanguage-> | NL-NL en-EN de-DE nl-BE pl-PL fr-FR it-IT Etc.. |
Required (when sending WhatsApp messages) |
| TemplateName-> | This is the Whatsapp template name found in the Jobrock admin (lowercase only and no spaces). | Required (when sending Whatsapp) |
| Variable 1-> | Only relevant for Whatsapp messages. If you leave this field empty, it will check what variable is configured in Jobrock Admin section. If a variable is already given in the Apex, then Jobrock will not check the configured mapping in the admin for this particular variable. | (optional) |
| Variable 2> | See variable 1 | (optional) |
| Variable 3-> | See variable 1 | (optional) |
| Variable 4-> | See variable 1 | (optional) |
| Variable 5> | See variable 1 | (optional) |
| Variable 6-> | See variable 1 | (optional) |
Sync Records
Purpose:
You can use this to sync all types of records.
Available:
In the managed package: 1.59
Details:
| Action Name | Sync Records | Required |
|---|---|---|
| Apex Class | Sync Records | Required |
| JR Object Type | User, Vacancy, Event, Partnership, Contact, Lead, Publication | Required |
| RecordId | Record id | Required |
| Action | Upsert, Active, InActive, Delete … (it could be flexible with any text upto 10-15 characters) |
Required |
| ClientCode | ClientCode | Only required in case of multi-brand |
Delete Contact Data
Purpose:
Delete the contact’s personal info from the hub.
Available:
In the managed package: 1.69
Details:
| Action Name | Delete Contact Data | Required |
|---|---|---|
| Apex Class | Delete Contact Data | Required |
| Contact Id | Record id | Required |
| Record Email | Not Required | |
| Phone | Record Mobile Phone | Not Required |
| Client Code | ClientCode | Only required in case of multi-brand |
Sync Publication
Purpose:
Details: