Tech | Read the latest blogs, news and views from Infomentum. (4)

In the second part of my blog about MuleSoft RPA in action, I’d like to show the complete automation process - from process evaluation to design, build and execution. I hope it will help you see the potential of Mulesoft RPA and how you can apply it to improve the efficiency of your processes.

After testing MuleSoft RPA (Robotic Process Automation), the new automation tool released only a few weeks ago, I cannot wait to share my thoughts. But let me start with a few tips for creating a stable RPA automation:

Robotic Process Automation (RPA) tools are designed to carry out all human repetitive tasks. Bots can retrieve information from legacy and modern applications and extract data from emails, documents and even web pages. They interact with applications using keyboard and mouse clicks just like we humans do. MuleSoft is a new player in the RPA market. MuleSoft RPA was released only a few weeks ago, and the great news is that it is fully integrated with MuleSoft Anypoint Platform and Composer.

Navigating the world of manufacturing can be a complex and exciting experience. Whilst this could be said for most companies and industries, this proved more so the case when Infomentum recently delivered a proof of concept. This organisation not only finds itself at the heart of UK-based manufacturing but also at a junction between academia and government research. A solution was required to bridge the gap from both a technological and operational perspective.

Event-Driven Architecture allows you to create more resilient and scalable integrations for an infinite number of uses-cases. This approach enables us to develop modular and decoupled solutions providing real-time (or near real-time) connections.

The highlight of my week? My first MuleSoft Connect 2022! It was the first in-person event in almost 3(!)years. So, in case you missed it, I would like to share what I learned and enjoyed the most during that eventful day.

'We are planning to upgrade to Mule 4 in a few months. Meanwhile, the development is on hold because it is impossible to find any Mule 3 certified resources. Can you help us?' The head of the integration programme was crying for help. Looks like it is a common problem as many organisations still rely heavily on the old Mule 3 version. 

When the connected digital experience has become "a must" rather than "a nice to be", integration solutions are in high demand. APIs are now almost the de factor way for various platforms and systems to communicate and exchange information. So, what happens when a public API fails? In 2014 Gartner estimated it to be about $300,000 per hour!

As a Test Analyst at Infomentum, I generally follow a formal structured test process, one that is promoted by certification bodies such as ISTQB. It ensures that we adhere to the best practices and verify that the software under test meets our requirements. But is it always enough? In my experience, no. On occasion, a more experimental method of testing is a more suitable approach for that given project. Great news, it also fits nicely with an agile development cycle!

We developers love to use and create automated processes! If something is repetitive, we have an urge to write a bash script, a gulp/grunt task, etc. It is in our nature! If we can automate, we will automate.