Edit

Set up FIFO

warning

Dynamic Task Rendering (DTR) is not supported since IA Cloud Enterprise version 10.2.0. You must not enable it, otherwise custom sorting will not work.

FIFO (first in, first out) is the prioritizing strategy when the oldest (first) entry is processed first. The FIFO strategy helps to improve adherence to the service-level agreement (SLA) for the record processing time.

FIFO logic

Record priority and order are determined based on the record date (primary parameter) and record order (secondary parameter). All records from the same Manual Task have the same date. If the record date is not set, it equals to the Manual Task start date.

Basic flow

Let's say a Manual Task contains five records: record1, record2, record3, etc. As they have the same date (= MT start date), they appear in WorkSpace in the very same order:

1. record1
2. record2
3. record3
4. record4
5. record5

Gateway flow

Let's say, the Manual Task from the previous example is a part of a Business Process with a Decision Rule, where record1, record3, and record5 are rerouted to a 10-second processing step, and records 2 and 4 are processed in a 30-second step:

For the first 20 seconds, only record1 and record3 appear in WorkSpace:

1. record1
2. record3

On the 30-second mark, record2 appears after record1 because of its record order, and the list looks as follows:

1. record1
2. record2
3. record3
4. record5

On the 60-second mark, the list looks as follows:

1. record1
2. record2
3. record3
4. record4
5. record5

FIFO in Control Tower

Control Tower sets hits ordering during the hits creation.

When a hit is created, Control Tower adds a JSON object to it. This JSON object is stored in the _sys_record_order column of Business Process or Manual Task data and contains parameters for ordering. BP or MT data is used to start a BP or an MT and to transfer data from step to step in BP.

These parameters are passed to WorkSpace during the hit submission operation in the CreateHITRequest#customAttributes field.

{
"hitOrder" : {number of record in csv file },
"hitOrderDate" : { date from csv file column, in case date is missed in input record, current time will be used. }
}

Here's an example of a JSON object:

{
"hitOrder":1,
"hitOrderDate":"2020-03-11T10:15:55.935"
}

The hitOrderDate parameter value should be formatted according to the ISO-8601 specification:

"YYYY-MM-DDThh:mm:ss[.sss]" - "2019-09-15T15:00:28.638"

Here's an example of a CSV:

_sys_record_order,task_id,_sys_mt_hit_title
"{hitOrder:1,hitOrderDate:'2021-08-25T06:52:44.048'}",WF_Aug,WF_Aug
"{hitOrder:1,hitOrderDate:'2021-07-25T16:52:44.048'}",WF_Jul,WF_Jul
"{hitOrder:1,hitOrderDate:'2021-11-25T06:52:44.048'}",WF_Nov,WF_Nov
"{hitOrder:1,hitOrderDate:'2021-09-25T06:52:44.048'}",WF_Sep,WF_Sep
"{hitOrder:1,hitOrderDate:'2021-10-25T06:52:44.048'}",WF_Oct,WF_Oct

tip

For FIFO in WorkSpace, see details here.