RE Framework is the name of a specific template. There are many different available templates or you can build your own. For an automation like this, and especially when you’re still learning UiPath, I suggest building from scratch to get familiar with how it all works and to build out your organizational standards and requirements.
Thank you for the response.
I would like to understand if you mean that uploading the message ID to the orchestration queue is the one you are referring as date(1st column) in the test.xlsx correct? Also I am getting a value of -4 in the date field while extracting data? any idea?
Also just trying to understand why is this approach suited only for Dispatcher and Performer workflow, and not for other workflows (batch framework and Transactional not sure whether have any).It would be helpful if you could show the difference, as I am trying to better understand this Reframework using this as example.
For your workflow—where you need to process daily Outlook emails, extract CRNs, update an Excel file, send notifications, and keep your data fresh—UiPath stands out as a great choice for automation. It’s designed to handle exactly the kind of repetitive, rule-based tasks you’re describing, and it does so with a user-friendly interface and plenty of built-in features.
Why UiPath Works Well for Your Needs
Outlook Integration: UiPath comes with ready-to-use activities that let you read, filter, and extract information from Outlook emails with just a few clicks. You can easily pull out details like CRNs from the body of each message.
Excel Automation: Whether you need to open, update, or clear data in your Excel file, UiPath has straightforward activities to get the job done. Updating the status column or resetting your spreadsheet for the next day is simple.
Email Sending: Sending out emails, even with attachments like your updated Excel file, is just as easy. UiPath supports both Outlook and other email protocols, so you can notify customers without any hassle.
Reliability: With built-in error handling and scheduling, you can trust that your process will run smoothly every day, even if something unexpected happens.
How You Can Build This Automation Step by Step
Read and Extract Emails from Outlook
Start by using the “Get Outlook Mail Messages” activity to collect emails from your inbox or a specific folder.
If you only want to process certain emails, filter them by date, subject, or sender.
Use string manipulation or regular expressions to extract the CRN from each email’s body.
Process Each CRN in Your Application
Use UiPath’s UI automation features to launch your application.
Enter each CRN for processing—this can be done with activities like “Type Into” or “Click.”
Update Your Excel File
Open your test.xlsx file using UiPath’s Excel activities.
For each processed CRN, update the status column to “completed.”
Optionally, log any issues or skipped CRNs for troubleshooting.
Send an Email to the Customer
Use the “Send Outlook Mail Message” activity to create a new email.
Attach the updated Excel file.
Send the email to the customer.
Prepare for the Next Day
At the start of each new day, clear the previous day’s data from your Excel file using a “Clear Range” or similar activity.
This keeps your data organized and ready for the next batch of emails.
Tips for a Smooth Implementation
Use Variables: Store things like CRNs, email addresses, and file paths in variables. This makes your workflow easier to maintain and update.
Add Error Handling: Include retry logic and try-catch blocks so your automation can recover if something goes wrong.
Log Your Steps: Keep a record of what happens at each stage. This helps with troubleshooting and ensures nothing gets missed.
Schedule Your Automation: Use UiPath Orchestrator or even Windows Task Scheduler to run your process automatically every day.
In Summary
UiPath is a strong fit for your use case, offering all the tools you need to automate your Outlook, Excel, and email tasks reliably. With its intuitive design and robust features, you can set up a solution that not only works today but is also easy to maintain and adapt as your needs change.
Dispatcher and Performer workflow is suited for separation of logic as well as scaling of the process when needed. Let’s suppose now business receive 100 emails/day and you are using 1 robot license to process those record, if in future emails/day grows to 1000 or more you just need to allot more the robots to performer process. By this approach you wont be needed to make any or verry little changes to your code.
If you could elaborate your process more we could suggest better.
Use Case Mapping to REFramework