Invoke Workflow vs Flowchart

Hi everyone, I had a question tied to the logic behind using Invoke Workflow vs using Flowcharts within ReFramework or any custom state machine, aside from being able to see everything in multiple tabs.

They can both be setup to do the same thing (ie. you can invoke a Flowchart), but was wondering if there is some functional advantage to one over the others as the original ReFramework is filled with invoking sequences, perhaps even too much. Is it just for ease of replication to other processes or an object oriented philosphy?

Hello @cssc

As you mentioned the invoke workflow can be used for multiple purposes

  • To reduce the complexity of creating a lengthy process.
  • Maintaining the modular concept to execute and check each modules. It will help for easy debugging
  • Easy to understand the logic and flow
  • Reusability

Flow chart can be used whenever if we are handling complex automations including multiple conditioning and all. That’s why we can see flow charts inside reframework.
But included inside sequence.


Invoke Workflow : Here workflow might contains just sequence of activities or flow charts or state machines or combination of three

  • It is always best practise to divide the project into sub modules
    Ex project : Login to some application and download attachments, in this there would be two modules a) Login Application b) Download Attachments
  • For each module it is better to create a workflow
  • To call that workflow we use a concept called Invoking
  • Finally, you can invoke flowchart (that means you can invoke a workflow that contains flowchart) using this activity called Invoke Workflow. Indirectly, invoke workflow or invoke flowchart were same
  • Also, another advantage with invoking is re-usability. Code once call wherever you want