What is it?

The Unit21 Logic Provider can process verification data that's stored in the custom_data of an entity.

This allows customers to upload legacy verification data, or verification data from providers that are not supported by Unit21 and use this data in a Verification Workflow.

Custom data is processed periodically and different keys are then cached per org so they can be used in the Verification Workflow editor.

How do I use it?

First, your developers must update or create an entity with custom_data as documented here.

The Verification Provider to select is the Unit21 Logic Provider.

Drag and drop the Unit21 Logic in the window:

Double click the Unit21 Logic:

Double clicking on the Logic Provider allows the custom data provider to be selected.

Here is where you will find fields from the custom_data your developers have added to your Unit21 dashboard.

Let's select twitter_verification_request in this example:

Next add the Reject and Accept conditions from the Select final states widget by dragging and dropping them in the window:

Connect the Unit21 Logic to to the Reject and Accept using your mouse:

Select the connector between Unit21 Logic and Accept and click on the Edit Condition button:

De-select default case. This will bring up a prompt to create additional logic:

Editing the conditions for the connector link from the logic provider will give a list of all the available keys that exist in every entity for the given logic provider (i.e custom data).

In the dropdown, you can select twitter_verification_request->requester_account_type. Then create the logic requester_account_type == verified.

The available data types are boolean, string and number. In this example for the twitter account type, the verification will be accepted when the requester_account_type is equal to verified.

Verify and save your workflow.

The Verification Workflow can be saved and used right away.

Custom data and Unit21 Logic workflow examples:

Custom Data from Developers in json	Logic Provider UI	Data Type	Logic Example:
`{"identityMind": {"state": "A"}}`	Shows in the interface as `indentityMind→state`	text field	`indentityMind→state` == A
`{"onfido": {"results": {"confidence": 80}}}`	Shows in the interface as `onfido → results → confidence`	numeric field	`onfido → results → confidence` >= 50
`{"jumio": {"ok": true}}`	Shows in the interface as `jumio → ok`	boolean field	`jumio → ok` != false