A/B Testing Process Definitions

The A/B Test activity enables customers to configure Process Definitions with weighted outcomes to test multiple paths. This document will describe the steps required to configure the A/B Test activity and apply it to a simple two-path outcome within a Process Definition.

The A/B Test Activity

The A/B Test Activity is available from the Process Designer when creating Process Definitions in the Backoffice. This activity features to configurable input parameters:

Sample Process Definition

In this example, a typical document capture flow will be modified to include an A/B test between Capture Document Image - Front v3 and Capture Document Image - Front v4.

A standard document capture implementation

During a standard document capture process, a single 'Capture Document Image - Front' and/ or 'Capture Document Image - Back' is used to prompt the end-user to capture a document image. In some cases, multiple versions of the activities may be available in TrustX, providing different benefits or updated configurations. In such cases, it may be desired to test various versions using an A/B test to determine which activity is best suited for the process.

To implement this use case, see the steps outlined below.

1. In the Process Designer, add an A/B Test Activity to the Process Designer.

2. Click the 'A/B Test Activity' to open the right-side contextual menu to configure the input parameters. In this example, the input parameters are set accordingly:

   1. Name - docFront
   2. Path Weights - Map Entries: [pathA, 60], [pathB, 40]

3. From the example above, two paths will be available (pathA and pathB). Each path has a weight value that determines the likeliness of this path being chosen by the random. In this example, pathA has a weight of 60% and will be more likely to be chosen by the randomizer.
4. After the activity is configured, create a new Gateway and connect it to the 'A/B Test' activity. This will serve as the brand between that connects the two paths.

5. From the Gateway, create a sequence flow arrow using the that connects to the existing 'Capture Document Image - Front v3' activity. Once connected:

   1. Click the arrow to open the contextual menu.

   2. Expand the 'Condition' section and create a new Expression with the value: ${abTesting["docFront"]["path"].equals("pathA")}

   3. This expression is described as follows:

      1. abTesting - Denotes the abTesting session tables will be accessed.
      2. "docFront" - The name of the A/B Test defined in the activity input parameters.
      3. "path" - Accesses the collection of paths created in the Path Weights input parameter.
      4. .equals("pathA") - checks that the path is equal to "pathA" defined under within the Paths Weights list.

   4. As such, this expression will check to see whether the path is equal to pathA. If so, the process will proceed to perform the 'Capture Document Image - Front v3' activity.

6. Add the 'Capture Document Image - Front v4' activity to the Process Definition and connect it to the Gateway as previous described in step 5.

   1. As before, configure a new expression on the sequence flow arrow and add the following Condition Expression: ${abTesting["docFront"]["path"].equals("pathB")}

7. Each of the activities are connected to the 'Change document type?' Gateway before the process resumes with the usual capture document process.