Onboarding Custom Settings
Intro
3B Onboarding is delivered with configurable settings under the hood that help implementers configure the application.
There are two types of under the hood configuration settings – Custom Settings and Custom Metadata*** and they are both available to system administrators to configure by navigating to Salesforce Setup.
Custom Settings
Using Custom Settings, we can configure things such as default behaviour and private keys for integrations. The application is delivered with the following custom settings:
Broad Bean Integration
These settings are for configuring the Broadbean integration.
Logic Melon Integration
These settings are for configuring the LogicMelon integration.
Onboarding Trigger Control
These settings help us control the APEX Trigger flow and enable/disable triggers to aid the data migration process and to allow better debugging.
Onboarding Default Settings
These settings should only be configured by system administrators.
- New Applicant Account – not used anymore for new implementations, however, implementers can use to soft-code new registrants default account assignment
- New Appliacnt Record Type – not used anymore for new implementations, however, implementers can use to soft-code new registrants default record type assignment
- Theme – not used anymore for new implementations
- Job Post Page – default html page name for job posts. Only used for OOTB implementation of the onboarding product.
- Google API Key – this is the API key for google address autocomplete services. When supplied, the job board will allow users to search for jobs based on address keyword search
- Visualforce External Site URL – this is the salesforce site*(link to article) URL that is enabled for APEX Rest communication. This is used in numerous locations.
- Site URL – similar to Visualforce External Site URL, but only enabled for API communication
- Use Community Licenses – not used anymore for new implementations
- Default Job Board – this is the ID of the Job Board *(link to article). Only used for OOTB implementation of the onboarding product.
- My Docs: Show Expanded Details on Load – only used when My Documents is hosted on Salesforce Visualforce. Allows you to pre-determine whether document sections are expanded or collapsed by default when the My Documents page loads.
- Job Board Max Search Distance – this is the default search distance selection when Google Address API is provided and address autocomplete is implemented on the job board
Custom Metadata
Using Custom Metadata, we can configure default behaviour for integrations and app workflows.
Filter Condition
Filter Conditions custom metadata type is used to define the matching conditions and rules for expression builder types. An example usage is for defining the filtering options on a Custom Rule
| Field | Description | Options | Example |
|---|---|---|---|
| Label | This is the rule label. | Certificate | |
| Type | The type of search condition | Related Object, Text, Date, Boolean, Picklist | Related Object |
| Search Icon | The SLDS icon's name for the selected condition in the expression builder | standard:collection | |
| Order | A number that helps us order conditions in the expression builder | 1 | |
| Group | What expression builder target this condition rule is for | User configurable. "Compliance" ootb | Compliance |
| Condition Object | Target comparison object | Certificate Type | |
| Condition Object Title Field | Target comparison field's title | Certificate Name | |
| Condition Object Subtitle Field | Target comparison field's sub-title | ||
| Match Object | Compliance Rule | ||
| Match Object Field | Compliance Rule Name |