MuleSoft® provides many connectors to help businesses develop API-led connectivity solutions. Out of all of those connectors, the “For Each” loop is a commonly used connector. This connector iterates through each element of a collection, or in other words, each element of an array. 

There are two different For Each connectors that MuleSoft provides. There is the “For Each” and the “Parallel For Each.” They have key different functionalities and serve different purposes. Knowing when to use each one is crucial for the success of the API’s you are building. 

When to use ‘For Each’

The For Each connector gets an array of elements and processes, each one at a time, so if there are 60 elements and each one takes one-second to process, making the total run for this connector one-minute. That’s something to keep in mind when using this connector since it could slow down your entire flow.

This is why the For Each connector should be used with a small amount of elements, or when performance isn’t critical.

The other thing to keep in mind when using this For Each connector is that if one element fails to process, the connector stops processing the rest of the records and moves on to the next connector. For example, let’s say that out of 60 records the connector fails at record 29, the remaining 31 records won’t process since the connector failed on record 29.

Another important piece to keep in mind is that this connector doesn’t return a processed payload. Whichever payload is given to this connector gets passed through to the next connector.

In the above example, the Collection field in For Each is set to iterate over an array stored in payload.topics:.

Key ‘For Each’ Takeaways:

• The For Each connector should be used when there are a few items to loop for per call.
• Use when performance isn’t crucial.
• Use when one payload fails the rest should stop processing.
• Use when a processed payload isn’t returned.

When to use ‘Parallel For Each’

Since the For Each connector doesn’t return a processed payload, one of the common patterns with the connector is to use Object Store to store the processed data for each element. This can be used successfully, but is not recommended since the Object Store has limitations on how many records it can process on a timeframe. It also can fail if you try to get elements from it at a pace faster than its limits. 

One of the ways to avoid this pattern is to use the Parallel For Each connector. With this connector each element is processed individually and the end result is all the payloads for each processed element are merged into one payload. You can then iterate through each one and run the logic that’s needed to run on each element. This case can’t be used for all scenarios, but it’s a way to avoid the Object Store pattern.

Parallel For Each works by processing each element in its own thread. There is a limit on how many threads it can run at one time (see the links below for more info). You can also set the limit yourself, which gives you flexibility and control on the amount of threads it can run at one time.

Parallel For Each processes all records and the result is their payload – regardless of failure or success – will return the same amount of payloads that match the elements given. This is useful when you want all records to process, regardless of the status. You can then use your own logic afterwards on what to do with success and failure payloads. 

Another key component to the Parallel For Each connector is that the end results are returned as a combined payload. So it actually returns the payload and you can do with it what you want. The For Each connector doesn’t return a payload and you have to use a variable or Object Store in order to store and retrieve the payload processed on the connector.

Key ‘Parallel For One’ Takeaways:

• Avoid using Object Store in a loop, since Object Store drops messages sometimes.
• Use when performance is necessary.
• Use when all should be processed, regardless if one of them fails.
• Use when you want to see the end result of all elements passed.

For Each vs. Parallel For Each

Summary

Both For Each loop connectors are great tools for building a MuleSoft API. Each project will have different requirements. Based on your project requirements, you will now be able to figure out which connector to use.

Ad Victoriam’s certified, experienced and passionate MuleSoft consultants team up with businesses to turn legacy point-to-point integrations into a scalable architecture that your business can grow with. Let’s talk about a solution for your company today.

Related Resources:

The For Each Scope

The Parallel For Each Scope

Set Up Your Salesforce Org for Integration with MuleSoft

Subscribe to the AdVic Salesforce Blog on Feedly:

The post MuleSoft’s ‘For Each’ Connectors Explained appeared first on Ad Victoriam Solutions.

MuleSoft Account Executive Wes Disher was a recent guest on Ad Victoriam’s “Salesforce Simplified” podcast, where he detailed how with Robotic Process Automation (RPA), companies can capture and automate their teams workflows instantly – whether through a UI, document or image – and do it with point-and-click tools.

So, what specifically is Robotic Process Automation?

MuleSoft’s Disher explained, “Robotic process automation is a software technology that combines robotics and automation to perform repetitive tasks. RPA is a method for business process automation that uses an application or bot that replicates an employee’s desktop actions by interacting with an interface in the same way that a human traditionally would.”

According to a Deloitte Global RPA survey, 53% of respondents have already started their RPA journey. This is expected to increase to 72% in the next two years. If this continues at its current level, RPA will have achieved near-universal adoption within the next five years.

The Benefits of Implementing RPA

“I think there’s really four main benefits that we’ve identified here at MuleSoft,” Disher explained. “The first one is essentially reducing the overall cost and improving that customer and employee experience. And so, how can we automate the processes for the customer? Shorten their time manually entering a claims process or a loan process. And then, also, taking that task and not putting that on as the responsibility of those agents or those customer success reps and streamlining it.”

Conversely, MuleSoft will tell you that challenges to RPA include: 

– Displace human workers: One of the biggest criticisms of RPA and other automation technology is its potential to eliminate the need for data entry and clerical-style roles.

– Lacks intelligent capabilities: RPA as a standalone technology can only perform tasks that it can copy from a script — lacking the ability to learn and improve the script it’s performing. The next generation of AI and intelligent automation tools are now being introduced to address this pitfall of RPA.

– Project complexity: Transformative RPA projects tend to be complex and require a time commitment to see the return on investment — as a result, some RPA projects fail before the value is realized.

Seamless Integration with Anypoint Platform and Composer

And if you were wondering, yes, RPA seamlessly integrates with MuleSoft’s Anypoint Platform and Composer.

According to Disher, “The way we’ve actually built our RPA solution was through an acquisition of Servicetrace just about two years ago. Our product team has really put a massive emphasis on bringing these three technologies together. The best news and the best part about it is it’s all built on the Anypoint Platform. What you’re building and what you’re creating in RPA or Composer allows you to be able to reuse that going forward.”

Building a Successful Automation Strategy

AdVic also asked Disher to give us his thoughts on how companies should go about constructing a successful automation strategy.

“I truly believe as companies continue to adopt digital platforms,” Disher remarked. “It’s extremely important to have top-down alignment on these strategic initiatives that you’re looking to enable for not only the company, but also deliver to your customers, and putting the customers at the center of everything that you do. That’s truly where MuleSoft is allowing these organizations and empowering them to really automate everything and empower everyone on a single platform.”

There is much more to our conversation with MuleSoft’s Wes Disher, including a discussion of how RPA creates better customer and employee experiences, the training that MuleSoft offers around RPA, and much more. Listen here, or wherever you listen to podcasts.

Ad Victoriam’s certified, experienced and passionate MuleSoft® consultants team up with businesses to integrate Robotic Process Automation (RPA) into a scalable architecture that can help your business grow. Let’s start talking about it today!

Related Resources: 

What is Robotic Process Automation  (RPA)?

MuleSoft RPA

Replace Repetitive Processes and Tasks with MuleSoft RPA (Podcast)

MuleSoft Consulting Services

Subscribe to the AdVic Salesforce Blog on Feedly:

The post Replace Repetitive Processes and Tasks with MuleSoft RPA appeared first on Ad Victoriam Solutions.

When setting up your Salesforce Org for an effective and efficient integration with MuleSoft, there are a few integration tools that will be helpful in your integration journey. 

In this article, we will be going over how to set up a Connected App with MuleSoft, and two ways to send messages regarding data changes from your Salesforce Org to MuleSoft. 

Set Up a MuleSoft Connected App

First, let’s begin by setting up the MuleSoft Connected App in your org. 

From Setup, search “App Manager” in the quick find box. This is where you will create a new connected app to host the secure connection between Salesforce® and MuleSoft®

The scopes that will allow this kind of access will: 

1. Provide access to your data via the web.
2. Allow access to your unique identifier.
3. Access and manage your data.

Once the connected app for MuleSoft has been created, you can search “Manage Connected Apps” and find the MuleSoft app there as seen below:

When you click “View” on your MuleSoft app in the Manage Connected App page, you will find the “Consumer Key” and “Consumer Secret,” which is required for connecting MuleSoft and Salesforce. Like the Integration User’s username and password, this will be in the configuration file in MuleSoft to establish a secure integration. 

Quick Tip: To view the Consumer Secret, you will be asked to click “Click to Reveal” as it is a confidential key and crucial in establishing a secure connection.

With your connected app set up, you are ready to begin the journey of sending messages between MuleSoft and Salesforce. 

Sending Messages Between MuleSoft and Salesforce

In order to explain this most thoroughly, let’s follow this example:

Your Salesforce org would like to have all contacts created or edited in Salesforce to be integrated with your legacy database system via MuleSoft. Each time a contact is created or edited in Salesforce, you need MuleSoft to make those changes in the legacy system as well. There are two ways to set this up inside of Salesforce: 

1. Platform Events and Process Builders
2. APEX Classes

We will now go over the benefits and potential pitfalls of each of these.

Platform Events and Process Builders

A platform event is a component of the event-driven software architecture of Salesforce and external systems (in our case, MuleSoft). These systems pass messages through platform event messages, which are listened for in MuleSoft. Platform events must have a trigger inside of Salesforce to send that message to MuleSoft. This is where the Process Builder comes in. 

Create a Process Builder to be triggered each time a Contact is created or edited. This will trigger the process whenever there is activity related to Contacts.

The Contact is either new or any of the fields are updated, so you should have a branch for each of those options.

Quick Tip: Make sure you are listing each of the fields on the object you want to trigger an update in your integrated system. If someone updates a field that is not listed as part of the process builder, the message to update the contact will not be sent to MuleSoft. 

These two options will go to an immediate action of either New Contact or Update Contact using the sObject (Platform Event) as a Record Type. This will fire the Platform event to send a message to MuleSoft with the Key, Method, and Object Type.

On MuleSoft’s end, there is a listener that is waiting for one of these Platform Event messages to come across and will fire the appropriate flow in response to the message it receives. 

APEX Classes

An APEX Class can be configured to be an HTTP callout using the Salesforce REST API we talked about earlier. The HTTP callout will be easier to use, but will still require Salesforce development. An APEX Class is created in the Developer console and is written to receive the request from Salesforce regarding the change in data and send that message to a listener in MuleSoft, similar to the way the first option works. We highly recommend using Platform Events and Process Builders because they require significantly less Salesforce development time and are easier to maintain in the long run. 

In addition, APEX Classes are only a good option for a limited number of profiles. The caveat of using APEX Classes is that each user must have permission to use the class. If you are using APEX Classes, this permission can be added in the profile permissions as seen below.

Once you click edit on the APEX Class Access page, you will be brought to the screen below, where you can change the selected Classes that the profile has permission to use. In order to trigger the APEX Class, the user must have a profile with access to the APEX Class.

Summary

Connected Apps, Platform Events and APEX code allow for efficient communication between Salesforce and MuleSoft. Connected Apps allow Salesforce to recognize the connection to MuleSoft. Platform Events or APEX code allow for communication to MuleSoft. This explicit process for setting up communication with your integration platform will allow for a manageable integration with MuleSoft. Following this article will allow you to fast track your integration setup. These steps will ensure that you have the foundation of your integration and the communication between MuleSoft and Salesofrce configured. With an effective integration foundation, you will be set up for a successful integration.

Ad Victoriam’s certified, experienced and passionate MuleSoft consultants team up with businesses to turn legacy point-to-point integrations into a scalable architecture that your business can grow with. How can we help your business today?

Related Resources:

• What Can MuleSoft Do for Your Salesforce Org?
• Create Better Integrations with MuleSoft Flow Designer
• MuleSoft Composer’s Ease of Use Reduces the Need for IT

Follow in a Reader

The post Set Up Your Salesforce Org for Integration with MuleSoft appeared first on Ad Victoriam Solutions.

Thousands of Salesforce® customers utilize MuleSoft® to create a 360-degree view of their customer data, or to boost productivity with automation, or for other purposes related to enhancing their CRM. You may be wondering why? 

In a recent AdVic “Salesforce Simplified” podcast about such a CRM enhancement, our MuleSoft Practice Director, Tom Minton, explained the many benefits of MuleSoft Composer.

“The main advantage to MuleSoft Composer for Salesforce, Minton says, “is that it allows Salesforce admins the ability to create inner integrations with external systems using no code.”

He added, “Without having to concern IT departments, Salesforce admins can connect an assortment of connectors with just clicks. Even without having a vast knowledge of MuleSoft coding ability, they can achieve the results they need and  the information they need in a much more efficient way.”

MuleSoft Composer or MuleSoft Anypoint?

MuleSoft Composer and MuleSoft’s API/integrations flagship tool, Anypoint, share some of the same features. 

Minton explains, “Anypoint comes with a bigger financial investment and may not be ideal for medium or rising businesses. MuleSoft Composer, however, is a lighter version of Anypoint that packs the same power, is user-friendly to Salesforce admins, and it’s efficient.”

Integrate, Streamline, and Automate with MuleSoft Composer

MuleSoft Composer integrates with products such as Workday, ServiceNow and Slack, and enables the use of Salesforce directly from an app. With these integrations, sales and procurement receive automated messages that notifies them of inventory when they are selling to customers. 

Mitigating Sales Forecasting Risk

Whether it is Tableau, or those infamous Excel/Google Sheets, data can be pulled from these sources to forecast for the following months using historical data and past performance. Integrating Google sheets into Tableau or Salesforce can actually map out data in a more usable and visually appealing way. 

Another one of the many benefits of MuleSoft Composer is the ability to synchronize orgs. As your business grows and you decide to collaborate with competitors or acquire brands with their own org, MuleSoft allows you to come together as one. Thus allowing orgs to pass information without having to swivel back and forth between systems.  

Streamlining Operations with MuleSoft Composer

MuleSoft Composer streamlines everything. That means less keyboard time and more time making sales.

Here’s some additional streamlining Composer helps with:

• You could have inventory information.
• You can view the throughput.
• You’re able to send information out about a new opportunity via a Slack message. In that Slack message, it could have a link back to the Salesforce opportunity for whether your salespeople are in house or on the road.
• There’s a connector for a service called Stripe, which is a cash reconciliation ecommerce tool. 
• You can get the information into the system that it needs without having to type it.

The Future of MuleSoft Connectors

All-in-all, MuleSoft enables its users to have multiple sources of customer information at their fingertips. 

“They come out with a new set of features every three to six months,” Minton says, “with plenty more to come.” 

As a certified MuleSoft Anypoint and Composer, and Salesforce multi-cloud consulting partner, Ad Victoriam’s integration experts understand the complexities of enterprise integrations, both on-premise and in the cloud. We simplify complex integration scenarios, integrate disparate systems, and provide a scalable architecture that your business can grow with – whether or not you are using Salesforce. So, if you are ready to connect your systems, we’re ready to talk to you today.

Related Resources:

How Salesforce and MuleSoft Create a Seamless Customer Experience
What Can MuleSoft Do for Your Salesforce Org?
MuleSoft Composer’s Ease of Use Reduces the Need for IT
MuleSoft Integration Creates Customer 360-Degree View

Follow in a Reader

The post MuleSoft Composer for Salesforce vs. MuleSoft Anypoint Platform appeared first on Ad Victoriam Solutions.

Flow Designer is used to design and develop fully-functional MuleSoft® applications in a hosted development environment. 

Designed to be used by Senior Architects as well as Junior Admins, Flow Designer is a simple alternative to creating full-blown APIs by hand within Anypoint Studio. With Flow Designer being packed with numerous features, it’s an obvious choice to consider when planning projects.

Design Center

To start creating a Flow Designer project, you simply opt to build a MuleSoft application rather than write a RAML within Design Center. Design Center differs from traditional RAML creation by showing what you make, as well as the processes graphically with easy to follow indicators displaying order,  hierarchy of elements, and triggers. Another benefit to using Flow Designer is that all work is automatically saved to the cloud for later continuation, collaborative editing, and safe-keeping.

Triggers and Connectors

The vast selection of triggers and connectors created by MuleSoft, as well as other users, allow for an ever-expanding number of uses and implementations. These triggers and connectors reduce the work required to duplicate processes you have already made, or processes others have already made. Saving both time and energy, by reducing redundancy and possible errors when working with a new system or CRM. Additionally, these triggers and connectors are all free to use and available to everyone through MuleSoft’s Anypoint Exchange.

Mapping and Transforming Data

Gone are the days of fumbling around with data mapping documentation. Flow Designer has a built in automatic data mapping feature that takes the hard work out of transforming and mapping data.  And with an easy drag and drop-style editor, editing the automated mappings is a breeze. Adding custom fields or functions to your transformations or mappings is simple using MuleSoft’s native DataWeave language. In as little as a few clicks and a little reading, you can create lightweight and versatile code to meet every task’s unique needs.

Error Handling and Debugging

Unfortunately, errors are almost impossible to avoid entirely. Luckily, debugging and fixing errors are easy to do within Flow Designer. With a dedicated “Problems” button that displays any errors in layman’s terms, understanding and resolving the issue can be accomplished without an extensive knowledge of MuleSoft.

Summary

All of these features, as well as Automatic Data Mapping and more, were designed to facilitate the complex and time consuming process of creating integrations. Though a traditional creation strategy may be more efficient for complex projects possibly not supported by Flow Designer, Flow Designer should still be an option seriously considered by project planners and businesses looking to get their desired results more efficiently.

Ad Victoriam’s certified, experienced and passionate MuleSoft consultants team up with businesses to turn legacy point-to-point integrations into a scalable architecture that your business can grow with. Let’s talk about a solution for your company today.

Related Resources:

• Product Spotlight: Anypoint Flow Designer
• Anypoint Platform: Flow Design FREE Course
• What Can MuleSoft Do for Your Salesforce Org?

Follow in a Reader

The post Create Better Integrations with MuleSoft Flow Designer appeared first on Ad Victoriam Solutions.

Developments in technology continue to progress and are furthering to improve human lives through convenience and recreation. In the 21st century, it is safe to say that “data is the new oil.” With everything being digitized, data is the key for smooth functionality and happy customers. However, data management can become quite complex and acts as a double-edged sword, thus it is extremely crucial for organizations to have the right tools and services to manage their data.

Integration, a subject not widely understood, has become the present and the future of digital transformation. Here’s how Salesforce® and MuleSoft® are transforming data and delivering a seamless customer experience.

MuleSoft as a Catalyst to Making Your Data Available

MuleSoft serves as a catalyst to communicate between applications and services via integration. It offers multiple components and a centralized platform to ensure connectivity and data simplification throughout the business. The enterprises are heterogeneous, as they are composed of many different systems with their own data structures and requirements. And while these systems are used as integrated solutions to drive business processes, they can create data-related complications due to disparate structures. Data processing, such as migration and synchronization, will be difficult to maintain when there are large amounts of data. 

There is also the issue of managing the links between those systems and modifying them without disrupting the entire working ecosystem. MuleSoft, as a catalyst, provides a tool called Anypoint Platform, which provides accessibility to the essential components in providing integration solutions.

Here is an overview of some core components of MuleSoft as an integration tool:

• CloudHub: An enterprise-class cloud-based integration platform that allows organizations to utilize Anypoint Connectors to develop integration flows that connect applications and create new APIs, in addition to existing data sources. CloudHub makes it possible to connect with SaaS and on-premises applications and services at cloud speed.

• Anypoint Connector: A library of reusable extensions that allow MuleSoft to integrate with both legacy and SaaS systems to enable seamless data processes. With access to multiple APIs, businesses can build connectivity and deliver real-time data across the business ecosystem.

• DataWeave: This is powered by the data language and is designed to filter, extract, and transform one or more different types of data together to create another data format, such as XML and Java to JSON. DataWeave does support a wide range of file types, including flat and structured data, which provide a flexibility that can help the businesses cope with systems using different data formats per process.

• Database Connectivity: The Database Connector can be downloaded from Anypoint Connectors to establish a connection with almost any relational database and perform SQL queries. This allows the organizations to access the data in the database without writing additional code to bypass the authentications.

 Visualize Your Data in Real Time

Salesforce, one of the world’s leading cloud-based CRM software, offers the best user-friendly interface along with a variety of tools that make it easy to visualize and analyze real-time customer information from multiple organizations. While some of Salesforce’s tools are not suitable for all businesses, it does provide AppExchange to fit specific organizations, departments and roles. Additional visualization tools are located in AppExchange and integrated into Salesforce to meet business needs.

What are the Challenges in Understanding the Data and Why Salesforce?

Raw data are being captured on a daily basis to establish baselines, benchmarks, and goals for the organizations. However, most of these data have no value unless properly analyzed. It is also a challenge that the data is being captured and retained infinitely, leading to an enormous amount of data needing many resources to do the comprehension. The difficulty increases as there are multiple risks contributing to the process that can cause organization more harm than good.  For example, there is the potential of confusion and diverse outcomes of the same data set due to different individuals’ analyses. Salesforce is the key to handling all customer information within a few clicks. It offers effective tools for data visualization and analysis, in which it can help organizations make decisions and leverage business growth.

Instead of using the traditional reports and dashboards that are limited and require manual modifications, Salesforce can produce visualizations based on the criteria information, such as payments by month or sales by period. These visualizations are real-time, customizable and interactive for users. They are presented in a dashboard format that includes data tables, graphs and criteria-based measures. 

The bottom line is that Salesforce is able to view data in real-time and produces real results. It provides a better picture of the organization overall as the insights, causes, and trends are explicitly displayed. Salesforce and its visual data tools also save companies time and money while improving their efficiency.

At a glance, these are some of the popular tools for data visualization:

• Einstein Analytics
• Tableau
• Datorama

Business Partners Make Each Other Better

MuleSoft’s partnership with Salesforce is revolutionary as it accelerates digital transformation and transcends the connected customer experience. MuleSoft is capable of creating APIs that can connect to any system, application, and data source. This makes it easier for Salesforce to retrieve real-time data across systems, either in the cloud or on-premises, and produce a unified customer view on a single platform. With MuleSoft as the data link, Salesforce can end data siloing in disparate systems and prioritize the ultimate customer experience value proposition – integrations. Essentially, MuleSoft and Salesforce are the best combination when dealing with complex integrations and helping organizations to build an integrated approach that is scalable and reliable.

As a Salesforce and MuleSoft Partner, AdVic is uniquely qualified to provide your business with a scalable architecture so it can grow. Fill out the brief form below, or click here to learn more about how the combination of Salesforce, MuleSoft and AdVic can empower your teams to lead your business to VICTORY. 

[gravityform id=5] 

 Related Article

What Can MuleSoft Do for Your Salesforce Org?

Follow in a Reader

The post How Salesforce and MuleSoft Create a Seamless Customer Experience appeared first on Ad Victoriam Solutions.

Integration is the future. In an increasingly technology-driven world, it is crucial that there is a single source of truth for your company’s information. If your employees must go to multiple different places to get the information they need, you have wasted time, money, and energy. 

Salesforce® and MuleSoft® can create a powerful, real-time integrated experience in your Salesforce org. This article will explain what it means to have an integrated experience in your Salesforce org and how to acquire that experience with MuleSoft. In addition, we will cover some of the basic integration tools in Salesforce, a high-level overview of MuleSoft architecture and how these tools work together. 

Salesforce Integration Tools for MuleSoft 

Salesforce is built to be integrated with your legacy systems to create a 360 degree view of your customers for your Salesforce users. MuleSoft can be added to your Salesforce org by adding a Connected App in the App Manager settings. 

The best way to allow MuleSoft to have access to your Salesforce org is by creating an integration user. When the user is set up, save the username, password, and security token that is sent to the related email. These credentials will be used in MuleSoft to login to Salesforce and make changes to the data via the Salesforce REST API. 

Salesforce can communicate changes to the data to MuleSoft in a few different ways. The most common and simple way being via Platform Events and Process Builders. A Platform Event can be created in Salesforce and triggered to send a message to MuleSoft via a Process Builder. In this way, you can create the trigger to respond to whatever changes in the data suit your business needs. 

In addition, an APEX Class can be configured to use the Salesforce REST API mentioned earlier. An APEX Class is created in the Developer console and is written to receive the request from Salesforce regarding the change in data, then that message is sent to a listener in MuleSoft, similar to the way the first option with Platform Events works. However, it is highly recommended that you use Platform Events and Process Builders because they require significantly less Salesforce Development time and are easier to maintain in the long run. 

MuleSoft Architecture – How Does it Work? 

MuleSoft architecture is unique from other integration platforms because it is an Enterprise Service Bus architecture model. This means that MuleSoft is the translator between many different systems. You can create APIs unique to your systems that only change when that system changes. Then, these system APIs speak to each other through MuleSoft processing APIs. As you can see in the diagram below, systems do not connect directly to each other. Rather, they are connected through MuleSoft. 

In MuleSoft, there are three kinds of APIs that are created: 

• Experience API (Channels): Produces what the end user needs to see and interact with.
• Process API (Processes): Performs the transformations between systems.
  • Translates each of the systems to Salesforce or other systems that need to communicate.
• System API (Data): Represents what is held in each system.

Below is an example of how these APIs can be structured: 

As you can see, the system layer represents the two systems that need to be integrated. These system API’s do not contain any of the business logic to “translate” Salesforce to the ERP system. The process layer APIs contain the business logic for Products, Orders, and Customers so that this data can be translated from one system to another. The top layer, Experience APIs, create what the end users interact with. These APIs generally contain schedules for when the other API’s should run in order for the data to move from system to system.

This kind of architecture creates many significant benefits to integrating with MuleSoft. To start, it creates reusable, scalable, and secure integrations. Once you have created a System API, you do not need to ever create it again. You may need to make small additions, but you will be able to connect that system to any other system via a Process API by reusing the System API. This leads to increased agility on projects, less time wasted, and more money saved. Similar to the App Exchange, there is an Anypoint Exchange for MuleSoft. Here you can find connectors, accelerators, integration patterns, etc., that you can use in your projects instead of starting from scratch yourself.

Salesforce + MuleSoft: Catalyze Your integrated Experience

The combination of Salesforce integration tools and MuleSoft can create the integrated experience you’ve been looking for in your Salesforce org. It can be difficult to fully transition from legacy systems to Salesforce and with MuleSoft you can implement Salesforce at your own pace. This will allow you to slowly retire your legacy system operations while keeping your data up to date in real time and creating a future-proof implementation. MuleSoft can be updated in an extremely agile manner to keep your systems up-to-date and avoid technical debt build up.

With a MuleSoft integrated experience, your Salesforce users will be able to see the data they need in one place. This will create an increased level of trust in your Salesforce org from the start and make the transition away from legacy systems as painless as possible. The future is integrated and MuleSoft can take you there.

As a certified MuleSoft Anypoint and Salesforce multi-cloud consulting partner, Ad Victoriam’s integration experts understand the complexities of enterprise integrations, both on-premise and in the cloud. We simplify complex integration scenarios, integrate disparate systems, and provide a scalable architecture that your business can grow with – whether or not you are using Salesforce. So, if you are ready to connect your systems, we’re ready to talk to you today.

*This article also appears on Salesforce Ben

Related Articles

YANMAR Returns for a MuleSoft Integration

Highlights from MuleSoft’s CONNECT: NOW

Subscribe in a Reader

The post What Can MuleSoft Do for Your Salesforce Org? appeared first on Ad Victoriam Solutions.

Members of the Ad Victoriam MuleSoft® Consulting Team attended the virtual conference and chose a few session highlights to share.

Session: Streamline and Scale Lending with API-led Integration

This breakout session provided a good understanding of how lending companies have addressed the need to deliver products and services with the use of a digital platform.

API-led connectivity plays a big part in lending-type MuleSoft applications, as this helps to define or refactor current business processes to help improve the overall end to end customer experience.

During the session, Truist Bank CIO, Ken Meyer, talked about how adopting MuleSoft is not just a technology effort, it requires the business to define all the requirements for the APIs that can then be implemented using MuleSoft.

With the use of APIs and MuleSoft, companies within the lending industry can unlock data from other systems, automate manual business processes, and drive innovation with more speed and agility.

Session: Revolutionize the Patient Journey in Life Sciences Through APIs

This session focused on how in today’s healthcare world patients are seeking virtual engagement.

Due to COVID19 healthcare companies are having to rapidly change and adapt to the growing virtual needs of patients.

The MuleSoft Anypoint platform is helping healthcare providers to quickly combine disparate systems with builder block APIs to drive interoperability. Traditionally IT teams would not be efficient enough to quickly build out new interrogations.

To support the healthcare industry’s needs, such as those that COVID19 has presented, the API building block approach with MuleSoft allows IT teams to build upon past phases to narrow the development timeline.

Session: Manage Changing Retail Operations with Real-Time Data

The main subject of the presentation was how retail has changed significantly in the last few months due to COVID19.

Kreena Mehta, Lead Software Engineer of Asics Digital showed how they used SAP and MuleSoft to streamline their operations and quickly adjust their supply chain to a more delivery-based model as opposed to the traditional brick and mortar.

MuleSoft made this easy with its API-Led approach because the existing processes did not have to be changed from the top down, just the targeted areas dealing with shipping/receiving.

The digital shopping experience is now the number one priority in the retail space due to more online shopping by consumers.

As a certified MuleSoft Anypoint and Salesforce multi-cloud consulting partner, Ad Victoriam’s integration experts understand the complexities of enterprise integrations, both on-premise and in the cloud. We simplify complex integration scenarios, integrate disparate systems, and provide a scalable architecture that your business can grow with – whether or not you are using Salesforce. So, if you are ready to connect your systems, we’re ready to talk to you today.

Related Articles
YANMAR Returns for a MuleSoft Integration

The post Highlights from MuleSoft’s CONNECT: NOW appeared first on Ad Victoriam Solutions.

So, what’s happening behind the scenes in each of these interactions? APIs (application programming interfaces) are… And that’s why it’s increasingly critical for innovative retailers that want to reach customers in new ways to develop and execute successful API strategies.

So, when developing your API strategy, here are several steps retailers should consider:

Build a Single View of the Customer

A common problem with a growing business is that you often outgrow the systems that track your customers. With the limited capacity to upgrade and properly synchronize these sources of customer data, many times you end up with small silos of specific data: customers, orders, loyalty, etc. Retrieving that data into a single view is difficult to achieve with conventional tools that are used by most retail businesses.

MuleSoft® is a top platform that can bring these disparate systems together and present them in a single, 360-degree view. This gives you the insight your business needs to truly know your customers. MuleSoft’s API-led architecture allows systems to be brought together as needed and utilized as one single powerful tool for retailers.

Optimize the Supply Chain

Develop Better Data Orchestration for Reporting

In addition to an omnichannel view of your customers, the same tools and APIs that were created to allow for customer insight can be reused to create an accurate and timely data source for your reporting, accounting, or auditing needs. MuleSoft’s reusability means quicker to-market times for your development. That translates into a better bottom line for your IT needs. The power of unlocking your data can take your business to the next level.

Offer Contactless Engagement

As you go about developing your API strategy, double-down on digital commerce. Also, plan on offering your customers the ability to take advantage of contactless engagement (mobile/wearable payments, inside and curbside pickup, tap-and-go card payments).

Nowadays, not only are your customers expecting the ease of a contactless engagement experience with you, it makes them feel safe and secure while completing their transactions.

And beyond offering your customers a convenient, secure method of payment, mobile payments can also help expand your customer base. This ensures your business achieves greater success on its journey to growth.

As a certified MuleSoft consulting partner, Ad Victoriam’s integration experts understand the complexities of enterprise integrations, both on-premise and in the cloud. We simplify complex integration scenarios, integrate disparate systems, and provide a scalable architecture that your retail business can grow with. So, are you ready to get connected? Talk to a certified MuleSoft consultant today!

Related Article
Anypoint Community Manager builds Effective API’s

Subscribe in a Reader

The post Income-Generating API Strategies for Retailers appeared first on Ad Victoriam Solutions.

And in case you missed the sessions, the Ad Victoriam team captured many of the highlights and we’re thrilled to present Part 2 of our recap below. You can catch up and read Part 1 here.

The Sessions

Session: Financial Services: Digitize and Connect Mission-Critical Processes with Anypoint Platform

Highlights:

1. Customer and client onboarding, large firms using an AP-led approach to integrate old and new systems.
2. IT team can be shown the capabilities of MuleSoft and re-using APIs.
3. How to accelerate IT delivery.

Benefits to MuleSoft Users: This session explained real use cases for implementing MuleSoft with Financial Service companies that need to digitize and connect their systems together using APIs. This helps users by having more capabilities and security which helps tremendously in the Financial industry.

Session: How API’s Enable Digital Transformation in Government

Highlights:

1. Increased agility and innovation, simplified security, and monitoring.
2. FedRAMP certified — removing data centers for cloud infrastructure.

Benefits to MuleSoft Users: Real-world use case for government using MuleSoft for cloud-native API-led network. FedRAMP certified.

Session: Food Delivery-in-a-Box: Restaurant Ordering Made Easy

Highlights:

1. Food delivery market growing; need for quick-service restaurants and delivery-service providers.
2. Use API-led architecture and the ability to re-use APIs.
3. Implement an all-in-one solution that uses pre-built APIs and connectors, and standardizes the processes that require end-user input.

Benefits to MuleSoft Users: This session showed how to implement the re-use of APIs and create a fast integration using MuleSoft. This helps all users in the Food industry (employees, customers, vendors, etc.) when it comes to capabilities inside the store, for online delivery or using a delivery service.

Session: How a Service Mesh Fits Into Your Microservices Strategy

Highlights:

1. Ninety-nine percent of organizations are adopting microservices and report challenges.
2. Service Mesh is an architectural pattern for microservices deployments.
3. Service Mesh can be used for microservices outside of MuleSoft.

As a certified MuleSoft Anypoint and Salesforce consulting partner, Ad Victoriam’s integration experts understand the complexities of enterprise integrations, both on-premise and in the cloud. We simplify complex integration scenarios, integrate disparate systems, and provide a scalable architecture that your business can grow with – whether or not you are using Salesforce. So, if you are ready to connect your systems, we’re ready to talk to you today.

Related Articles
Highlights from MuleSoft Connect 2020 – Part 1
YANMAR Returns for a MuleSoft Integration

Subscribe in a reader

The post MuleSoft Digital Connect 2020 Highlights – Part 2 appeared first on Ad Victoriam Solutions.