RE Framework - Larger Projects

Hello everyone,

I had a question concerning the RE Framework. While I have dabbled with it on smaller 2 to 5 step projects, I am curious to know how to implement it with much larger projects that have several branches, loops, clicks, and other misc events. Certainly we don’t just throw our 20 step long click paths or flowcharts of branches into the Process transaction section.

So essentially at the moment I have a large project broken into modular (sequences) pieces all of which might have 2 to 3 steps inside of them. How would I implement these modular pieces into RE Framework while keeping the flow conditions and logic in tact.

Any explanation here would be helpful as I often find tutorials to be too basic. Example code of a larger project implemented in such a fashion would also be extremely helpful!

Thank you in advance!

1 Like

Kindly have a view on this thread


Cheers @developer120

1 Like

Thank you for the reply. I have seen this post and have gone through it. I understand the basics of all of it. However my confusion occurs when trying to implement large portions.

For example: Lets say I have a process where I need to grab the queueItem, do 15 clicks / types / control flows to figure out if I am interested in the data it produces. Then If I am interested I continue down another 15 steps of clicks and types, all having different branches throughout, based on certain conditions, then finally saving the produced file.

For sake of simplicity lets say I already have a single flowchart in another project that is not RE Framework, with all of these steps broken into small modular sequences and flow conditions all mapped out, how would this be set up in RE Framework? I cant fathom it makes sense to import my entire flowchart into the RE Framework “Process Transaction” piece and stop there.

Any help would be appreciated! Thank you!

2 Likes

Hi @developer120

Well, actually, this is how you would approach it. The REFramework is basically a shell for the actual process logic that is hosted in the Process.xaml file.

It allows you to easily catch exceptions that happen within your process, in a way that you don’t have to worry about that part and you can focus on the actual process logic.

In your situation, it would look like the parts where you fetch the queue item and then when you set it’s status to Completed would be the ones that are handled by REFramework outside of the Process.xaml file.