The MuleSoft development team at Northern Trail Outfitters creates a Mule application that interacts with several APIs and RPA processes. The team needs to share this application with other teams to help them create similar applications.
How should the Mule application be published in Anypoint Exchange to meet this requirement?
To share a Mule application that interacts with several APIs and RPA processes with other teams for creating similar applications, publishing it as a Template asset is the best approach:
Template Asset:
A Template in Anypoint Exchange is designed to provide a reusable solution that can be easily adapted for different use cases. It includes predefined integration logic and configurations that can be used as a starting point for new projects.
By publishing the Mule application as a Template, other teams can leverage this pre-built solution, customize it to their specific needs, and ensure consistency in integration practices across the organization.
Anypoint Exchange Templates Documentation
Northern Trail Outfitters (NTO) uses Flow Orchestration to automate quote development. The "Review Quote" work item is performed by their team of technical writers but can be fulfilled by any technical writer on the team.
How can NTO ensure the "Review Quote" work item is assigned to the correct Salesforce user?
To ensure the 'Review Quote' work item is assigned to the correct Salesforce user within the team of technical writers, the following approach can be used:
Creating a Group:
Create a Group in Salesforce that includes all the technical writers who are eligible to perform the 'Review Quote' work item. This group acts as a collective resource pool.
Assigning the Work Item to the Group:
When the 'Review Quote' work item is created in Flow Orchestration, assign it to the group rather than an individual user. Salesforce will then allow any available technical writer within the group to pick up and complete the task.
Ensuring Flexibility and Availability:
This method ensures that the work item can be completed by any technical writer in the team, providing flexibility and improving the chances of timely completion by utilizing the group's collective availability.
A non-technical employee from AnyAirlines creates a hyperautomation solution. The solution needs to meet the following criteria:
The process needs to begin when a record is created in Salesforce.
Then, it needs to pass data to a pre-existing RPA process which includes a User Task for data integrity purposes.
The output of the RPA process needs to be used to create a record in NetSuite.
According to best practices, how should this automated process be structured?
To structure the automated process to meet the given criteria, the following approach is recommended:
MuleSoft Composer Flow Triggers on Record Creation:
Use MuleSoft Composer to create a flow that is triggered when a new record is created in Salesforce. This is done by setting up a trigger event in MuleSoft Composer that listens for new record creation events in Salesforce.
Call the RPA Process:
Once the flow is triggered, it should call the pre-existing RPA process. MuleSoft Composer can invoke MuleSoft RPA bots, and you can pass the necessary data from the Salesforce record to the RPA process.
The RPA process will include the User Task for data integrity purposes.
Use the RPA Process Output to Create a Record in NetSuite:
After the RPA process completes, the MuleSoft Composer flow can capture the output from the RPA process.
The same MuleSoft Composer flow will then use this output to create a record in NetSuite, ensuring a seamless data transfer and process automation.
MuleSoft Composer Documentation
MuleSoft RPA Documentation
Northern Trail Outfitters needs to update multiple systems outside of Salesforce based on record updates within Salesforce. A hyperautomation practitioner needs to configure Salesforce to call several APIs created by the MuleSoft development team from within a Salesforce flow.
What specifications must be imported into Salesforce to make external services available to a Salesforce flow that enables external invokable actions?
To enable Salesforce to call external services within a flow, the appropriate specifications must be imported to make these external services available as invokable actions. The correct specification is Open API specifications. OpenAPI Specification (formerly known as Swagger) is a standard for defining APIs which can be easily imported into Salesforce to facilitate the integration and invocation of external services.
Import OpenAPI Specifications: Salesforce allows the import of OpenAPI specifications, which define the available endpoints and operations of an API, making them accessible as invocable actions in a Salesforce flow.
Creating External Services: By importing an OpenAPI definition into Salesforce, it creates an External Service, which you can then use within Flow to interact with the defined APIs.
Flow Integration: Once imported, these services can be integrated into Salesforce Flows to automate processes that require interaction with external systems.
AnyAirlines has MuleSoft Composer installed on their production Salesforce environment.
To test flows with data in multiple non-production environments, what does the hyperautomation specialist need to do?
Create Connections: To test flows with data in multiple non-production environments, creating connections to each environment within the MuleSoft Composer UI is necessary. This allows the Composer to access and manipulate data across different environments, ensuring comprehensive testing.
Installing Composer in Non-Production Environments: While installing Composer in each environment is technically possible, creating individual connections is more efficient and aligns with best practices.
Using Mocked Data: Mocked data can be useful for initial testing, but connecting to actual non-production environments provides more realistic test scenarios.
Proxy Setup: Creating a proxy to other environments is complex and unnecessary when Composer supports direct connections.
