Front End & Back End Organization & Hierarchy for Custom Data Fields

Disclaimer: Depending on your configuration, custom data field functionality may not be available. While we strive to ensure our product features are available for everyone, there are some configurations that are currently incompatible with certain features. To see if this feature is available for your company, please send an email to support@clickboarding.com.

Front End

In Click Boarding platform, Data Fields are stored in the form of a path – similar to how files are stored on your computer. For example:

Desktop
- Screenshots
  - 123.jpg
  - ABC.jpg
- Frequently Referenced Docs
  - Guides.docx
  - Spreadsheet.xlsx

When condensed to one line, the path to access a specific file/area from the example above looks like this:

Desktop > Screenshots > 123.jpg

Data Fields in Click Boarding are structured in a similar way to computer folders and files. The organization of these fields is sometimes called the “Candidate Shape,” for example:

Candidate
- Education (collection)
  - Completion Date – (date)
  - Degree Attained - (text)
  - Institution Name - (text)
- Mobile Phone Number - (phone number)
- Preferred Computer Operating System - (text)

When condensed to one line, the path to access a specific file/area from the example above looks like this:

Candidate > Education > Degree Attained

Now knowing what a candidate shape is, let’s look at a larger example candidate shape:

Example Candidate

Candidate Data/Shape
- Driver’s License - (data field group)
  - Class/Type - (text)
  - Expiration Date - (date)
  - Issued By - (text)
- Education (collection)
  - Completion Date – (date)
  - Degree Attained - (text)
  - Institution Name - (text)
- Mobile Phone Number - (phone number)
- Preferred Computer Operating System - (text)
- Preferred Name - (text)
- Question for Your Manager - (text)
- Today's Date - (date)

For the above Candidate Shape, this is how some of the fields would display in the Data Field Area inside Click Boarding.

For the above Candidate Shape, this is how some fields could be used to create a form that collects this data.

The image above is the view a Candidate would see in order to be able to complete.

Backend

The backend stores data for given candidates. In the below example, we’ll borrow from a similar Candidate Shape that we referred to in our Front-End example.

Example Candidate

Candidate Data/Shape
- Driver’s License - (data field group)
  - Class/Type - (text)
  - Expiration Date - (date)
  - Issued By - (text)
- Education (collection)
  - Completion Date – (date)
  - Degree Attained - (text)
  - Institution Name - (text)
- Mobile Phone Number - (phone number)
- Preferred Computer Operating System - (text)
- Preferred Name - (text)
- Question for Your Manager - (text)
- Today's Date - (date)

If we were to refer to or access a candidate’s Driver’s License Info, it might look like this:

Notes:

The Driver’s License fields (Expiration Date, Issued By, Type) are nested under the parent object of Driver’s License.
On the backend, candidate data only exists for data that has been passed from an integration or collected on a candidate form.
- For example, even if “Education” is a collection for your instance of Click Boarding, if a candidate has not been presented on a form or passed in an integration, any “Education” field will not be present for the Candidate via the API/backend.