As explained in the website integration scenarios, you will use this method in scenario 1. Please know that the technology used is considered a Beta technology by Salesforce.
A Byner Administrator can provide you with an example javascript snippet that can be included on the website along with a set of parameters (see example table below). The javascript for each form is unique and should be built op dynamically.
Please do not hard-code any urls or parameters as they are subject to change and most likely will differ if different environments are in use like PRODUCTION and TEST. It is recommended that these urls and parameters can be adjusted easily. This helps scenario’s where multiple environments are in use (production vs test vs development) or environments are refreshed. Variables may or may not be the same.
The form can be included on the website via the following steps. Ensure that all website domain(s) that are being used in test and production are added as allowed domains in the cross-origin resource sharing (CORS) settings in Salesforce by providing these to the Byner Administrator to avoid CORS errors. Add both the www and the non-www domain.
Include the javascript snippet that the Byner Administrator provides you with on your website and make sure all urls and parameters are built up correctly. An example snippet can be retrieved by a Byner Administrator by navigating to the Byner Setup > ATS Settings > Configure application forms > 'Select the right form' > Click Lightning Out Snippet. Before doing so, make sure they've set up their Salesforce site correctly otherwise incorrect url's might show. This is especially important when using sandboxes.
- url’s: Depending on the setup, one or more urls might be used. A use case for using more than one url could be a multilingual setup. In a multilingual setup the url’s will differ depending on the language needed. If a multilingual setup is configured, multiple urls will be provided.
- the first url is in the script src: the correct url(s) will be provided to you
- the second url is a parameter in the javascript called siteUrl: the correct url(s) will be provided to you
- the third url is at the bottom of the script: the correct url(s) will be provided to you
- other JS parameters
-
formId (18 char, text, optional): a unique ID that identifies the form containing the fields that should be loaded → the formIds to use will be provided to you
- if no jobId is not provided, the formId is required
- emailTemplateId (18 char, text, optional, legacy support, better configuration option available for admins): a unique ID that identifies the emailtemplate to be sent after applying via the form. Sending the email is handled via Byner → the emailTemplateIds to use will be provided to you if applicable. If no instructions are provided, the parameter should be not populated.
-
jobId (18 char, text, optional): a unique ID that identifies the Job that the application should be registered to → the jobId to use is either empty, fixed and provided to you or is included in the job feed.
- if no formId is provided, the jobId is required
- jobDescriptionId (18 char, text, optional): a unique ID that identifies the Job Description that the application should be registered to → in the job feed you can find the jobDescriptionId, this can be one or multiple id's per job, this could be used to support A/B testing of job descriptions
- recruitmentEventId (18 char, text, optional): a unique ID that identifies the Recruitment Event that the application should be registered to → to populate the recruitmentEventId an instruction needs to be provided to you. If no instructions are provided, the parameter should be not populated.
-
formId (18 char, text, optional): a unique ID that identifies the form containing the fields that should be loaded → the formIds to use will be provided to you
Simplified Byner application form html example
Please replace all <<var..>> tags with the variables provided to you by the Byner Project Team.
<html> <head> <title>Example Byner application form</title> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no" /> </head> <body> <script src="<<var1>>/lightning/lightning.out.js"></script> <div id="lightningLocator"></div> <script> $Lightning.use ( 'byner:ApplicationFormApp', () => { $Lightning.createComponent ( 'byner:applicationForm', { formId : <<var2>>, emailTemplateId : '<<var3>>', jobId : <<var4>>, jobDescriptionId : <<var4a>>, recruitmentEventId : '<<var5>>', siteUrl : '<<var6>>' }, 'lightningLocator', component => {} ); }, '<<var7>>' ); </script> </body> </html>
Example handover table from Project Team
Description | Production | Acceptance / Test | Development |
---|---|---|---|
var1 - script src domain | https://byner-17e4413a9bb.secure.force.com/ | ||
var2 - formId | a0V8d000001oqEoEAI | ||
var3 - emailTemplateId (, legacy support, better configuration option available for admins) | 00X8d009870gyOr | ||
var4 - jobId | a158d000000h876AAY | ||
var4a - jobDescriptionId | a1609000000B4D2AAK | ||
var5 - recruitmentEventId | a1L8d000000aRaaEAM | ||
var6 - siteUrl | https://byner-17e4413a9bb.secure.force.com/ | ||
var7 - bottom url | https://byner-17e4413a9bb.secure.force.com/ |
Related articles
You can also check out the following articles related to Application Form:
Comments
0 comments
Please sign in to leave a comment.