Workflows

Overview

Workflows are a pre-defined set of rules and parameters used to perform automatic collection of subject data for determining liveness. Workflows are created by the Face Capture library using their name. Capture Sessions are started using a Workflow and Camera to manage its settings. Some settings are available for modifcation through the Workflow such as:

• A username to identify the subject in the transmitted JSON for reporting purposes.

• A timeout duration which stops the Capture Session once the specified amount of time has passed. Setting a zero second timeout disbales the Capture Session from timing out.

• A capture profile specifying the criteria used to determine when to automatically capture the subject’s face.

Please see the (Face Capture Workflow Summary) table below for a general overview of the available Workflows.

Face Capture Workflow Summary:

Feature	Charlie	Foxtrot
Device Type	Mobile Device	Mobile Device

Device Type - The type of device to use this workflow with. Different workflows perform captures differently based on device type. For example, using a mobile device workflow when capturing with a kiosk will result in inaccurate or poor performance.

Note : The Charlie workflow is only available through the Android JAVA and iOS Swift interfaces.

Workflow Package Types

After a successful capture session, the back-end request package will be available through the Workflow. There are three different types of back-end package that can be obtained:

• High Usability - A request for the back-end focussed on usability.

• High Security - A request for the back-end focussed on security.

• Balanced - A request for the back-end with a mix of security and usability.

It is recommended to start with a Balanced approach and adjust to either High Usability or High Security based on testing.