Hacking the UiPath RE-Framework | Advanced Tutorial | Non-queue, non-repetitive and background

This video offers an advanced tutorial for tweaking and modifying the standard RE-Framework in UiPath. It showcases modifying an example build with the standard framework to work with data tables instead of queues. It then shows a simple change to make the framework non-repetitive. In the end it shows how to make a framework run in background and how to save it as a new template in Studio.

00:01 Topic and summary of the video
00:43 UiPath Hacks intro theme
01:08 Contents of the tutorial
01:31 How to configure the Framework to work with data tables rather than Queues
16:40 How to configure the Framework for a Non-Repetitive process
18:59 How to configure the Framework to run in background
29:02 Publishing our own Framework for our specific needs
31:47 Wrap-up and conclusion

Checklist configure the framework to use datatables:
- Make TransactionItem, out_ or in_ TransactionItem of type DataRow instead of QueueItem - in the WFs: GetTransactionData, Main, Process, SetTransactionStatus
- Remove the three SetTransactionStatus activities from the SetTransactionStatusworkflow
- Delete the GetQueueItem activity and replace it with two IF conditions (one for the first run, the other for the next runs)

Checklist for making the framework run in background:
- Remove UiPath.UIAutomation package dependency
- Change the project settings - “Starts in background”: Yes
- Get rid of take screenshot xaml and run all tests xaml (and all Tests folder)

Link to the "The UiPath RE-Framework - Full Tutorial for Beginners" video:

Link to the "Most useful new features in Cloud Orchestrator in 2020" video:

Let us keep in touch:

[UiPathHacks]

If you enjoy this video, check out my Beginner RE-Framework tutorial:

[mohamedelbedewy]

Very informative video
Thank you for sharing

[rpadeweloper]

This is why we need to reassigne nothing value in End Process activity: "This will signal that the process should stop execution. This can be Nothing for many data types as QueueItem, DataRow, DataTable, String, Object, etc.; 0 for Integer, Double, Decimal or other numeric types; False for Boolean. This means that we cannot have a valid transaction with value of Nothing, 0 or False. If that is a valid value, we need to find out another value for the stop signal. Even if we want to keep the Nothing value, to make sure the new type is properly reflected, we need to recreate the activity – remove the value, click outside, and retype Nothing.". This is note from: