42288f9e-ac67-409d-9759-e914f051f7dc.png

RPA Developer / CoE

e620c702-e06e-437a-b4ca-383230f01aa1.nupkg

The Template is an enhanced version of the **Robotic Enterprise Framework**, which includes a mechanism that gets **pending jobs** in between **processing transaction items**. The framework will then **stop the running job in favor of the pending job** based on '**JobPriority**' and reschedule it to be resumed after successful processing of the prioritized job. 

  

By default **the mechanism is deactivated**, so that the template can be used as a normal REFramework. 

  

The template also includes several configurable attributes in the config file to customize the mechanism for increased performance and efficiency: 

  

\- **OrchestratorFolder**: Defines a specific folder in Orchestrator which should be checked for pending jobs with its respective subfolders. By default, the workflow will get pending jobs from all folders. 

Note: getting Jobs from different folders than the running folder will only work in case of modern folders. 

\- **JobPriority**: Defines the priority of pending jobs which causes the running process to interrupt. By default this will be the value 'High'.

\- **TransactionCounter**: Defines after how many transactions the workflow should get jobs from Orchestrator. By default the worflow will get pending jobs after every transaction.

  

**Exemplary Use Case:** 

  

**Process A**: You have an unattended Performer Process which processes multiple transaction items from the queue and takes a total of 3 hours to process all items but is not time-sensitive. 

**Process B**: You have another Process, which has to process a smaller number of transaction items, but has to be executed within 2 hours after the request as per company SLA (i.e. a certain ticket). This job could be triggered manually from Orchestrator, via the Orchestrator API (i.e. by a chatbot or via a schedule that interferes with the running job. 

  

As the license will be blocked for 3 hours by Process A, Process B will be stuck in 'Pending' State and be started after the successful execution of Process A, causing it to **miss the SLA** of 1 hour processing time by 2 hours. Alternatively you would require an **additional license** to enable immediate execution and avoid missing SLA in case of blocked license.  

  

Using the present Template for Process A, Process A will check Orchestrator for pending jobs with high priority after defined number of transactions, then interrupt Process A in favor of Process B and resume with Process A after successful execution. 

  

Having heard this kind of requirement multiple times in the forum, I thought I would share my solution with you. 

This is my solution to a recent requirement, which I am sharing hoping to help some of you.

The template allows the interruption of the current job in favor of a higher prioritized pending job in Orchestrator and reschedules the interrupted job for later resuming.

03afd693-4d37-4c45-b97a-6c514be0415d.jpg

a4a552c1-a5c4-4e12-96f7-921433a07682.jpg

9ab78e63-ca3e-40d1-9f2e-6fa5a39ea2da.jpg

029e4426-44b0-4978-86d3-65aad8b0105c.jpg

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Version	Release Date	Download Link
1.0.0	May 5, 2022
Initial Release of v1.0

Prioritized Processing Enhanced REFramework