Skip Form Logic Guide

Click Boarding allows full admin users to configure “Skip Form Logic” rules to provide efficient, candidate-specific workflow experiences. For example, a set of candidates might all complete the same process workflow but require different forms within the tax credit step. On this step, Skip Form Logic rules can be utilized to present each candidate with just their own state’s form, alleviating the need to create a workflow per state.

Fields

An important prerequisite to building Skip Logic rules is to know the field name(s) that you are using. The field name is what comes back in the API when the candidate, location, or process is called, and is visible in the admin portal “Data Fields” section. This name can also be provided through your support channel if you can’t find the name of the field that you are using in a form. Some fields in Click Boarding are considered standard, because they are part of the base candidate profile: name, email, phone, address, etc. Other fields may be custom fields that you have created specifically for your company.

Liquid Language

Liquid is an open source language that provides a safe and flexible way to write logic statements. Because the syntax can look a bit technical, we have provided a basic tutorial and example set so you can copy, paste, and edit as needed without having to start from scratch.

This liquid expression says if the candidate’s process location region code isn’t Alberta, skip the form. The entire expression is a “comparison statement” starting with “if” and ending with “endif.” We are comparing a field (regionCode) to an expected value (AB) with some logic (not equals) and outputting a result (true). Implied in this logic is if we do get AB, then the statement is false—which can be written into the expression, but it is not required. Then the “endif” says we are done.

Field path examples:

Candidate home address postal code	candidate.addresses.home.postalCode
Candidate home state	candidate.addresses.home.regionCode
Candidate work state	candidate.addresses.work.regionCode
CandidateProcess Location name	location.name
CandidateProcess Location city	location.address.city

REMEMBER:

When the rule evaluates to true, the form is skipped, and when it evaluates to false, the form is shown.
Skip Form Logic can only be used on a data field that existed on a candidate at the time their process workflow was assigned. If a candidate enters data on a form mid-process, that data cannot be used in Skip Form Logic within the same process flow because it was added after the process was assigned.
Skip form logic can only be used on data that resides within certain candidate objects. This includes the candidate, location, and process.