MuleSoft | Read the latest blogs, news and views from Infomentum.

Everyone has, at one point or another, experienced a period of agonising waiting. Whether it be awaiting the results of a job interview, exam results or even waiting in an online queue to get the chance to grab some concert tickets, I’m sure that everyone can agree waiting around for things to happen is a deeply unpleasant feeling. Certainly for me, sitting through the week before A-Level results day felt (almost) worse than taking the exams did! Now imagine how stressful it must be for victims of crimes who are awaiting updates to their investigations.

Understandably, many people want to check in on the progress of their ongoing investigations: in fact, one of our clients found that 20% of inbound calls were from victims seeking updates to their cases. If victims of crime were able to access this information in a more timely manner, it would open up police time that could be allocated to support additional tasks, as well as help reduce stress for people going through the post crime journey.

Working in the automation space is both exciting and challenging. In a recent hyperautomation project with a client, I was provided invaluable insights into the complexities and nuances of automating business processes using MuleSoft RPA.

Here's a detailed look at my experience, the challenges faced and the lessons learned, along with a project glance on automating quotes in Excel and PDF formats.

It’s been some time since my last blog on Anypoint Code Builder, so today I'll be guiding you through the most recent changes that have been made to it. The latest release was in June, and to say it was a big one is an understatement!

Occasionally, I’ll come across a project where I encounter an interesting challenge or two. In one of these instances, I was working on an automation project for a customer who wanted to ingest all of their quotes from different suppliers into their Salesforce application. The quote documents were highly unstructured PDFs and Excel files, requiring the design of a bot which would extract data from these files and ensure that mandatory information was loaded into the Salesforce application using OCR technology.

Introduction

When I embarked on my latest project involving MuleSoft's Robotic Process Automation (RPA), little did I know it would be one of the most challenging yet rewarding experiences of my professional journey. As someone who enjoys solving complex puzzles, I was eager to dive into the intricacies of RPA; however, I soon realised this project would test my skills and patience in ways I hadn't anticipated. Balancing work and personal life became crucial, as late nights and early mornings became routine. However, with a steadfast commitment to overcoming each obstacle, the end result was immensely satisfying.

It’s been some time since my last blog on Anypoint Code Builder. Since then, there have been a number of changes made to the IDE, so I will guide you through the recent updates that have been made and compare it to previous versions. 

Throughout the last three years of an engagement with one of our customers, we’ve migrated many interfaces to Mule 4. In this blog, I’ll share insights into my experience working on the design and development of Mule 4 interfaces.

Composer Flows may be configured to be triggered by a scheduler, an event in the target system or HTTP invocation. Salesforce Flow actions can make HTTP callouts, so in this blog we will be demonstrating step-by-step how to integrate MuleSoft Composer with Salesforce Flow Builder for dynamic system interactions.

Introduction

These days, data is everything. Organisations are always looking for new methods to use big data to make decisions in today’s environment. However, managing massive amounts of data is easier said than done. Never fear! This is where MuleSoft, an advanced integration platform, comes into play.

Introduction

Robotic Process Automation (RPA) progresses through distinct phases in its project life cycle. When it enters the production deployment phase, the bots are deployed onto dedicated machines to carry out end-to-end automation. It is at this stage that scheduling comes into the picture, guiding bots on when to run and on which machine.

The scheduling step is relevant for bots that run in an unattended/automatic way at specific intervals (often many times a day!). However, it does not apply to bots that are attended or triggered by human or system actions.