Goldibots was developed in the trenches on a range of RPA software. Literally last 10 years in the making of this unique development style. The approach enables creativity, innovation, while enforcing a structured approach to your build. Truly create cutting-edge solutions, smash through known issues with its own breadcrumb error handling.
With a focus on collaboration and continuous improvement, Goldibots will push you towards being leaders in the industry. I have built robots monitoring robots and can automate a robot building a robot. Your whole team will have the knowledge to build robots that talk to you via the logs, handles errors pin pointing with breadcrumbs through the objects called.
The attached file appears to be a UiPath workflow template that follows a structured approach to executing a series of steps. Here's a comprehensive summary of what the file does:
1. **Initialization**:
- The workflow starts by logging the start of the workflow.
- It retrieves the name of the current workflow and stores it in the `strWF` variable.
2. **Sequence Test**:
- This section is commented out, but it demonstrates how to create a transaction item and pass it as an argument to the workflow.
3. **Flowchart MAIN**:
- The main logic of the workflow is implemented in a Flowchart.
- The Flowchart starts by logging the current step number and the workflow name.
- It then checks the value of the `intStep` variable and branches the flow accordingly.
- The workflow has 10 steps, each represented by a FlowDecision node that checks the current step number.
- For each step, the workflow performs various actions, such as logging comments, assigning values to variables, and throwing exceptions if necessary.
- The workflow also includes a mechanism to handle exceptions and retries.
4. **Exception Handling**:
- The workflow uses a TryCatch activity to handle exceptions.
- If an exception occurs, the workflow logs the exception message and source, and then checks if the step number is -1.
- If the step number is not -1, the workflow sets the `boolRetry` variable to `True` and logs the `boolRetry` and `IntRetry` values.
- The workflow then checks if the `boolRetry` is `True` and `IntRetry` is less than 3. If so, it increments the `IntRetry` variable and restarts the workflow from the beginning.
- If the `boolRetry` is `False` or `IntRetry` is greater than or equal to 3, the workflow assigns a detailed error message to the `strException` variable and throws an `ApplicationException`.
5. **Completion Handling**:
- If the workflow completes successfully (i.e., `boolComplete` is `True`), the workflow logs a message indicating the completion status.
- If the workflow does not complete successfully, the workflow logs the `boolRetry` and `IntRetry` values and then checks if the workflow should be retried.
- If the workflow should be retried, it increments the `IntRetry` variable and restarts the workflow from the beginning.
- If the workflow should not be retried, it assigns a detailed error message to the `strException` variable and throws an `ApplicationException`.
Overall, this workflow template provides a structured and robust approach to executing a series of steps, with built-in exception handling and retry mechanisms. It can be used as a starting point for developing more complex UiPath workflows.
I came from a career in Graphical Information Systems (GIS), SQL basically data, but originally left school and started an apprenticeship as an Avionic Electronic Engineer. This is where I gained my knowledge of process, the importance of manuals and clear work instructions. Step 2 follow step 1 if step 2 has an issue go back to step 1…
I started in RPA using Blue Prism (BP) and shortly after UiPath (UiP) at a small start-up called Genfour back in late 2015.
The company quickly grew from 6 of us to over 50 with a mix of Business Analyst, Developer, Consultant and robot monitors or controllers. The company found a gap in the market where current skills were not available in house, monitoring is a task in itself, simple process scoping/mining to select the correct ones for quick ROI i.e. ‘low hanging fruit’ and lack of content around via search engines before the academies started. Once your processes are running they are instantly removing that manual time from that team. You can easily estimate an ROI on these before you start and then measure from the queue data the robots process in real time.
I left in 2018 train and mature a newly formed team as the Lead Consultant Developer at CGI. I started training via my templated approach in BP. I hadn’t named it, but it was first designed against BP. My greatest achievement at CGI was using my previous SQL and current robotic software experience and qualifications to develop a self-running, self-monitoring, self-ticket raising platform called BOSS (Bot Optimising System Scheduler). That’s another book…….
In mid 2019 I changed my career and became an RPA Consultant contractor. I have since worked up and down the country for large financial institutes, IT providers, banks and volunteered at NHS during COVID. I have literally worked with and/or trained 100s of developers and have built 1000s of robots and pieces of across some cutting edge technologies, companies and teams.
Every company I start at will have their best practice (best endeavours) around the build of code around logging, nested ifs, logging, etc, but….BUT not a single developer in any of those teams would build the same piece the same way. Every developer’s mind is different and this software essentially allows you to do what you like. Other software, mature software, like SQL code or dot.net has structure and global standards of best practice adopted globally.
Ultimately this will enable you to use robots to build robots….IMAGINE THAT!?
Tech debt (i.e. all pieces are understandable) – GONE
Low quality documentation often ignored just a box ticking exercise (documents are lift and shift of the design that match step to step to the build) – GONE
Long process builds (typically done in days / weeks not weeks / months) – GONE
Code not reusable (every piece has its own searchable library so developers can just take a peek and tweak in a new object) – GONE
Code untestable in objects (test harnesses form part of the templates) – GONE
Robots running with bad logging (template covers error handling and step by step logging that bubble up as breadcrumbs to tell you exactly what called what from where in each step along the way as part of the templates) - GONE
My son in the summer of 2023 (2 hours) built his very own Roblox robot using this technique he was 8 years old! Then it hit me keep it simple any idiot can make this hard.
Trust me its been quite grim trying to educate and improve RPA programs when its overcomplicated from just early days learning. Agile is the key one suit does not fit all you will find that out at your peril.
Tier 1 - Functions (newbies)
Everyone has to start somewhere this is how to build re-usable functions to add to your RPA object library.
Tier 2 - Components (mid level experience)
Building on the knowlegde of low level functions, error handling and Args vs variables build these into easy to use step by step component templates all with test harnesses.
Tier 3 - Solution Design (senior level experience)
Once you understand functions and components you can then design all your robots, doing all the time thinking ahead of build. This uses object orientated design to build the flows that will then then map 1-1 to all documentation. Taking out the sting of that as have I not mentioned I have robots that document robots.
©Copyright. All rights reserved.
We need your consent to load the translations
We use a third-party service to translate the website content that may collect data about your activity. Please review the details in the privacy policy and accept the service to view the translations.