Our take on today's integration tech
Legacy systems are operational software that was designed and used for various business and tech-related landscape solutions. Notice how we mentioned “designed” and “used”. The reason is that legacy
The world has seen a large-scale digital transformation in recent years. While many different sectors have moved on with the times, others have lagged far behind. This is especially
Running a business is not an easy task. Especially considering the numerous logs and cross-checks required for a particular product or business item. With the inception of digitization techniques,
Imagine yourself as a service agent for retail giants like Amazon or Alibaba. What is the first thing you notice? Customer queries and service demands. Handling such a huge
The energy sector is all about improving the processes that aid in efficient energy production and consumption. This in turn requires constant changes in the way data is managed
In MULE 4 when a event is processed Messaging errors happens within the flow when there is some kind of processing issue and the flow execution stops. This post
This short tutorial discusses how the objects in a Mule event change when an external source is called through the flow. A Mule event consists of Mule message, attributes,
Remember those old days, when you need to add the correlationId as a prefix in each and every log messages in Mule 3 just to keep track of an
Once upon a time, there was a Microsoft SQL Server named DB007 running in a data center in an enterprise organization in Toronto. DB007 was sad. It doesn’t get
Wondering how to do MuleSoft 4.0 environment setup? We will need appropriate tools and proper environment set up to work with MuleSoft. This writing describes the components and sets
In MuleSoft we will use the Anypoint Platform and write RAML (RESTful API Modeling Language) code to design and manage the RESTful APIs. It requires permission from the owner
Problem: Sometimes to work with MuleSoft Anypoint Studio, we have payload with fields contain a null value.For example:Input Payload: { “id”: 001, “firstName”: “John”, “lastName”: null, “phoneNumber”: null, “email”:
We pride ourselves on swift communication and prompt responses. Let us know what you're thinking and how we can help you.
Head Office
18 King Street E, Suite 1400, Toronto ON M5C 1C4, Canada
Durham Office
Unit 265, 1099 Kingston Rd. Pickering, ON. L1V1B5, Canada
Austin Office
5900 Balcones Dr, STE 4000 Austin, TX 78731, USA
Dallas Office
Suite 1103, 2370 Victory Avenue, Dallas, TX 75219, USA
Phone: +1(877) 855-8775
Email: info@plektonlabs.com
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
