How to refine a process that makes use of multiple Workflows that input and test a website

As the title states I wanted to try and refine my project that made use of multiple workflows that i then invoked within the main workflow.
I previously worked on a small project as part of a course i am taking. It required us to use UiPath to take data from an excel sheet and test the abilities of a website we had created and hosted on Azure. It created new items, tested the editing of the items and then deleted the items to confirm the website functions properly.
Now my process was rather large and a bit unwieldly. I created a separate workflow for each different page, that corresponded to a table in the database on azure. I then invoked each of these workflows in the order i wanted to test.

This resulted in the website i was using as well as the excel file being opened and closed constantly. Is there a way to keep using the website for each of the separate workflows without it opening and closing like that? Or is that just something that’s par for the course since i chose to put them in separate workflows?

It’s really just to help my understanding of UiPath, as this was my first experience using it. It’s really quite an interesting program, if i can call it that. So i’d appreciate any input in this matter.
Thank you in advace.

@StudentHere

Consider the following strategies:

  1. Utilize argument passing when invoking workflows to exchange data between them, reducing the need to repeatedly open and close resources like Excel files.

  2. Maintain the website session open in your main workflow and pass it as an argument to the invoked workflows, eliminating the necessity of reopening the site for each task.

  3. Restructure your workflows. Rather than using separate workflows for each webpage or task, create a single workflow using Sequence or Flowchart activities.

  4. For projects with distinct stages or steps, implement State Machine workflows. Each state represents a different phase of the process, permitting smooth transitions without closing your website.

  5. Establish robust error handling to gracefully recover from errors without repetitive resource reopening.

I hope this helps.

1 Like