ReFramework official

[Florent_Salendres]

Hi,

ReFramework is meant by design, As-Is, to handle transactional processes and with Queues however, It is possible with some minor tweaks to adapt it to a non-queue process (based on a datatable for example) or even an Attended/One time non transaction job.

• Transactional with datatable/Datarows

You have example here, including xaml from our dear @loginerror.
The academy advanced training is also showing on the first assignement how to do so.

Reframework help

@Learner Sure, see below post for reference. Entire test framework is attached at the end. Let’s consider a framework that will take a list of numbers from the input Excel file and is supposed to multiply them by 2. The input file will be placed within the Framework in the /Input folder: [image] [image] The information about this file will be placed in the Config file: [image] Now, let’s adapt the framework to work based on this input data. It goes like this: Change the type of the va…

Attended/One Time (non-transactional)

1. Connect all transitions going from “Process Transaction” State to “End Process”
2. Delete the getTransaction State
3. Connect the “Success” transition from “Init” to “Process Transaction State”

This should look like the screenshot bellow.
Of course you can tweak it a little more and remove some unused pieces inside the invoked workflow but this should be working like this.

This will permit you to keep most of the advantages of the Framework such as:

• Out of the box exception handling/logs
• Screenshot on exception
• Credentials
• Reusability of the CloseApplications
• Config file

Cheers