Skip to main content
Kofax

Prioritizing automatic activities

Article # 3036511 - Page views: 150

Issue

By default, Kofax TotalAgility (KTA) will process automatic Transformation Server, Core Worker & Export activities based on the activity due date and priority. This is a First In First Out (FIFO) structure.

Is there any way to prioritize the automatic activities of one process over another? 

 

Solution

It is possible to change the order in which automatic activities are processed.  The options are below

  • Activity Priority - Process activities based on activity priority. Enumeration = 0
  • ActivityDueDate - Process activities based on activity due date. Enumeration = 1
  • ActivityPriorityDueDate - Process activities in the order of activity priority and activity due date. Enumeration = 2
  • ActivityDueDatePriority (Default) - Process activities in the order of activity due date and activity priority. Enumeration = 3
  • JobPriority - Process jobs based on job priority. Enumeration = 4
  • JobDueDate - Process jobs based on job due date. Enumeration = 5
  • JobPriorityDueDate - Process jobs in the order of job priority and job due date. Enumeration = 6
  • JobDueDatePriority - Process jobs in the order of job due date and job priority. Enumeration = 7

 

This change can be made using the Configuration Utility by updating the Activity Order setting in the Core Worker, Export Worker & Transformation Server tabs

clipboard_e33f5bb7accf003b012c48458c7aa3c18.png

 

Testing

This example will illustrate the difference between using the default activity order (enumeration = 3) and processing based on job priority and job due date (enumeration = 6).

 

I have 2 processes with identical logic called Primary Process & Secondary Process. The process logic classifies the document via .NET (Core Worker) before performing Extraction (Transformation Server). The Primary Process has a job priority of 1 and an SLA of 30 minutes.  Whereas, the Secondary Process has a job priority of 2 and a job SLA.

 clipboard_e0f87d1bc5cd73b51f932e5ff7879291a.png

I created 25 jobs on each process one after another i.e. Job 1 = Primary Process, Job 2 = Secondary Process, Job 3 = Primary Process, etc

Results

When using the default activity order, the Core Worker queue for the Classify (.NET) activity looks as shown below.  The activities are ordered based on the activity due date and priority.  This is the order in which the Core Worker will take and complete these activities.

clipboard_ea3d39784db3d67bd40ff07ad2aa08ec2.png

When changing the activity order to job priority and job due date, the Core Worker queue is shown below.  The Core Worker will prioritize the Classify (.NET) activities of the Primary Process as the job has a higher priority and a more urgent SLA.

clipboard_e6cec2285d4b1016934f239798084fc4a.png

The same logic applies to Transformation Server activities.  When using the default activity order, Extraction activities are processed based on activity due date and priority. 

clipboard_e4e611602fa7bf8c0441041a99cfb3294.png

By changing the activity order to job priority and job due date, the Transformation Server will prioritize Extraction from the Primary Process as shown below.

clipboard_e0c7d8ebc5108ff10d9c2679bf1d5720b.png

Level of Complexity 

High

 

Applies to  

Product Version Build Environment Hardware
KTA ALL      

 

  • Was this article helpful?