Last Updated on

What’s New In Transact 4.5?


Batch Instance Management | Batch Instance Priority Setting from Web Scanner and Upload Batch Screens

 

In previous versions of Transact, the user could change the default priority of a batch instance only from the Batch Instance Management screen.

In Ephesoft Transact v4.5.0.0, you can also set the batch instance priority when creating batches on the Web Scanner and Upload Batch screens. The priority of a batch instance is a numerical value from 1 to 100, with 1 being the most urgent case and 100 being the least urgent. By default, all batch instances receive the priority defined for a batch class on the Batch Class Management screen.

A batch can have the following priorities:

Value Priority
1 – 25 Urgent
26 – 50 High
51 – 75 Medium
76 – 100 Low

 

When processing batches with different priorities, the system will pick up the higher priority batches first.

When processing batches with same priority, you can use one of the two workflow batch picking algorithms: Round Robin (default) and FIFO, which can be selected in the application.properties file (<Ephesoft Installation Directory>\Application\WEB-INF\classes\META-INF folder).

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\app-prop.png

Round Robin

Here, batch instances are processed in a cyclic manner. Suppose, there are two batch classes, each having two batch instances. The system will pick up the batch instance for batch class 1, then move on to pick up the batch instance for batch class 2. This process will continue, with system picking one instance of each batch class at a time in a circular manner.

FIFO (BatchInstancePriority)

Here, batch instances are processed in the order they have been created as new, irrespective of their batch class. Batches that have been created earlier will be picked up first, followed by batches that have been created later.

 

To set the batch instance priority on the Web Scanner screen:

1. Enter the priority in the Priority text box.

Note: By default, the priority in the text field is set to the priority of the batch class.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\webscan1.png

2. Click on the Start button to start the scanning and batch execution process. On the Batch Instance Management screen, the batch instance is run with the priority 5.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\batch instance screen.png

 

To set the batch instance priority on the Upload Batch screen:

1. Enter the priority in the Priority text box in the top right corner of the screen.

Note: By default, the priority in the text field is set to the priority of the batch class.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\uploadscreen.png

Make sure to enter a valid value from 1 to 100, otherwise the system will throw the following exception:

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\error.png

2. Click on the Start Batch button to start batch execution. The batch instance is processed with the priority 5.

C:\Users\Ephesoft\AppData\Local\Microsoft\Windows\INetCache\Content.Word\BIMupload.png

 

You can also change the Batch Instance priority on the Batch Instance Management screen by clicking on the BI priority cell and entering the appropriate number. If you enter any invalid value, the cell will be highlighted and an error message “Priority should be between 1 and 100” will be displayed as a tool tip.

If you change the priority of a RUNNING batch, the change will take effect from the next Ready state. This means that the new priority will be reflected in batch processing after completion of the currently running Review phase or Validation phase. The new priority will also be applied if the batch is restarted from any selected module.

Let’s consider the following example:

Suppose we have created two batch classes, “SF86” and “Invoices”, with a priority of 10 and uploaded two batch instances for each of them without changing the default priority.

Batch Class Priority Timestamp
Batch Instance 1 SF86 10 2017-06-29_11-08-51
Batch Instance 2 SF86 10 2017-06-29_13-01-21
Batch Instance 3 Invoices 10 2017-06-29_11-38-11
Batch Instance 4 Invoices 10 2017-06-29_12-15-51

 

If the Round Robin algorithm is selected, one batch instance of each batch class will be picked up one at a time in a cyclic manner, irrespective of its time stamp:

1 Batch Instance 1 SF86
2 Batch Instance 3 Invoices
3 Batch Instance 2 SF86
4 Batch Instance 4 Invoices

 

If the FIFO algorithm is selected, the batches will be picked up according to their time stamps, i.e. the time they have been created as NEW, irrespective of their batch class:

1 Batch Instance 1 2017-06-29_11-08-51
2 Batch Instance 3 2017-06-29_11-38-11
3 Batch Instance 4 2017-06-29_12-15-51
4 Batch Instance 2 2017-06-29_13-01-21

 

If you change the default priority of these batch instances on the Upload Batch, Web Scanner or Batch Instance Management screens, they will be picked up and processed according to their new priority:

1 Batch Instance 1 Priority 1
2 Batch Instance 2 Priority 5
3 Batch Instance 3 Priority 7
4 Batch Instance 4 Priority 10

 

Batch priority can also be defined when uploading batches with the new AdvancedUploadBatch API or enhanced UploadBatch API.