BassemE/mulesoft-documentation-embeddings huggingface dataset:
Documents | MuleSoft Documentation
# Documents
RPA Recorder creates three document types at the end of a recording session:
RPA Recorder stores all created documents in the directory you specify in the settings. RPA Recorder groups recordings by date and tags them with the timestamp of the recording session.
## BPMN
The BPMN is a graphical representation of a business process model. It is a crucial element of an automation project in the Mulesoft RPA platform. It also includes the recorded documentation, which can be viewed in RPA Manager.
You can open BPMN with any workflow and decision automation platform that supports the BPMN v2.0 standard, specified by the Object Management Group.
The created PDF is an additional documentation of a recording and contains the following information:
  * Recording time
  * Process name (if opened from a web client, otherwise default name **New Process** is assigned)
  * BPMN graphic
  * A table with the following information:
    * Element name: Start Event, Activity (Service Task), End Event
    * Application window title
    * Action type: System, mouse, keyboard, clipboard, window state, variable, comment, screenshot
    * Screenshots: Either screenshots taken on mouse clicks or manual screenshots
    * Info: Detailed information based upon the action type


The table in the PDF displays a gray background row whenever a new activity is created. Subsequent rows have a white background to indicate that the sub-elements are part of this activity.
XES is the standard format for process mining. You can open the created XES file with any process mining tool that supports the XES 1.0 format. XES is used for further process mining purposes.
## Logs
RPA Recorder creates and stores multiple log files in the **Logs** subdirectory, within the directory you define in the settings. If the RPA Recorder directory does not exist, it is automatically created together with a log file.
The log file contains valuable information about the recording, but also warnings and errors that may have happened.
If any unexpected behavior arises, you can provide feedback to MuleSoft by sending the log file. == See Also
  *
Tables With AWS | MuleSoft Documentation
# Tables With AWS
The Tables with AWS action step enables you to recognize the text values inside a table by sending a local file to the AWS Textract service, which returns the extracted values.
This action step processes the document in a synchronous fashion (Amazon does not store the document) and automatically converts PDF files to PNG images. You can adjust the fidelity of the conversion in the properties grid.
## Inbound Variables
  * **Directory Path**
  * **File Name**
  * **Password**
  * **Read text from page**
  * **Read text to page**
  * **AWS Credentials**
Or, if **Use custom settings** is activated in the wizard:
    * **Client Id**
    * **Client Secret**
    * **Session Token**
    * **Use Session Token**
    * **Region Endpoint**
  * **Json Path**


## Outbound Variables
  * **Raw Text**
The extracted raw text of the document.
  * **Normalized Json**
The parsed result based on the normalized result and defined Json path.
  * **Raw Json**
The complete AWS response.


## Wizard
  * **Authentication Settings**
The AWS credentials to use for authentication
    * **Pin credentials**
Use this option to reference an existing **Credentials for AWS** configuration.
    * **Use custom settings**
Use this option to manually specify an AWS **Cliend ID** , **Client Secret** , **Region Endpoint** , and **Session Token** for this action step.
  * **Response settings**
    * **JsonPath Expression**
The Json path to the property of the response object.
  * **File Settings**
    * **Directory path**
The path to the directory where the file is located.
    * **File name**
The name of the file to analyze. Supported file types: PDF, JPEG, and PNG.
  * **PDF Settings**
These settings show when the selected file is a PDF.
    * **PDF file is password protected**
Specifies if the selected PDF file is password protected. When selected, specify the password to open the file in the **Password to open PDF file** filed.
    * **Read entire file**
Instructs the service to read the entire file.
    * **Read page range**
Instructs the service to read the selected range of pages.
      * **From page**
Specify from which page the service starts reading the file.
      * **To page**
Specifies until which page the service reads the file.
      * **Read to end of file**
Instructs the service to continue reading until the end of the file.


## See Also
  *   *   * Building JSONPath Expressions
Exchange Platform APIs | MuleSoft Documentation
# Exchange Platform APIs
Anypoint Exchange provides API features for publishing and consuming assets by using the Exchange API, publishing and consuming assets by using the Exchange Maven Facade API, and searching for assets by using the Exchange Graph API.
The Maven facade also enables you to publish federated assets.
Exchange APIs:
  *   * 

Topics:
  * Publish and Deploy Exchange Assets Using Exchange API
  * Publish and Deploy Exchange Assets Using Maven
  * Search Using the Graph API


## See Also
  * Anypoint Platform APIs - Developer Portal
  *   * Configure API Instances
Advanced Usage | MuleSoft Documentation
# Advanced Usage
Private Cloud Edition 
Usually, all you need to do with the Runtime Manager agent is install it and configure it according to Install or Update the Runtime Manager Agent.
If you are curious about the underlying architecture and the advanced configuration settings for the Runtime Manager agent, explore these topics:
  * Runtime Manager Agent Architecture
  *   * Internal Handler Buffering
  * Extend the Runtime Manager Agent
  * Application Validator Service
    * JAR Signature Validator
atBeginningOfMonth | MuleSoft Documentation
# atBeginningOfMonth
## atBeginningOfMonth(dateTime: DateTime): DateTime
Returns a new `DateTime` value that changes the `Day` value from the input to the first day of the specified _month_. It also sets the `Time` value to `00:00:00`.
The day and time in the input changes to `01T00:00:00`.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
The `DateTime` value to reference.  
### Example
This example changes the `Day` value within the `DateTime` input to the first day of the specified month and sets the `Time` value to `00:00:00`.
#### Source
```
%dw 2.0
import * from dw::core::Dates
output application/json
---
{
 "atBeginningOfMonthDateTime": atBeginningOfMonth(|2020-10-06T18:23:20.351-03:00|)
}
```

#### Output
```
{
 "atBeginningOfMonthDateTime": "2020-10-01T00:00:00-03:00"
}
```

## atBeginningOfMonth(localDateTime: LocalDateTime): LocalDateTime
Returns a new `LocalDateTime` value that changes the `Day` and `LocalTime` values from the input to the beginning of the specified _month_.
The day and time in the input changes to `01T00:00:00`.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
`localDateTime` |  The `LocalDateTime` value to reference.  
### Example
This example changes the `Day` and `LocalTime` values within the `LocalDateTime` input to the beginning of the specified month.
#### Source
```
%dw 2.0
import * from dw::core::Dates
output application/json
---
{
 "atBeginningOfMonthLocalDateTime": atBeginningOfMonth(|2020-10-06T18:23:20.351|)
}
```

#### Output
```
{
 "atBeginningOfMonthLocalDateTime": "2020-10-01T00:00:00"
}
```

## atBeginningOfMonth(date: Date): Date
Returns a new `Date` value that changes the `Day` value from the input to the first day of the specified _month_.
The day in the input changes to `01`.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
The `Date` value to reference.  
### Example
This example changes the `Day` value within the `Date` input to the first day of the specified month.
#### Source
```
%dw 2.0
import * from dw::core::Dates
output application/json
---
{
 atBeginningOfMonthDate: atBeginningOfMonth(|2020-10-06|)
}
```

#### Output
```
{
 "atBeginningOfMonthDate": "2020-10-01"
}
```
Authentication Errors | MuleSoft Documentation
# Authentication Errors
Cloud IDE 
Desktop IDE 
**Open Beta Release** : The **cloud IDE is in open beta**. Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions, available from the IDE.
In Anypoint Code Builder, authentication errors sometimes occur when you attempt to perform actions that require a connection to Anypoint Platform or to services that the cloud and desktop IDEs rely on.
## Failed to Authenticate to Git
All commands that involve `git` actions, such as publishing to Exchange and committing changes to an API specification, require authentication with the correct Anypoint Platform host cloud. If authentication fails, the action throws this VS Code error:
```
Failed to authenticate to git remote
```

To address this issue, cancel the error notification, and ensure that your IDE is set to the correct region for your project and that you are logged in to Anypoint Platform.
Azure Cosmos DB Connector 1.0 | MuleSoft Documentation
# Azure Cosmos DB Connector 1.0
Where possible, we changed noninclusive terms to align with our company value of Equality. We maintained certain terms to avoid any effect on customer implementations.  
---  
Anypoint Connector for Azure Cosmos DB (Azure Cosmos DB Connector) enables you to use basic Azure Cosmos DB operations to create and access objects in the Azure Cosmos DB system.
For information about compatibility and fixed issues, refer to the Azure Cosmos DB Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The Azure Cosmos DB API
  * Anypoint Connectors
  * Mule runtime engine (Mule)
  * Elements and global elements in a Mule flow
  * How to create a Mule app using Anypoint Studio


Before creating an app, you must have:
  * Credentials to access the Azure Cosmos DB target resource
  * Anypoint Platform
  * Anypoint Studio version 7.3.5 or later


## Common Use Cases for the Connector
Some common use cases for Azure Cosmos DB Connector include:
  * Support for documents
    * Creating or updating a document
    * Deleting a document
    * Getting a document or getting all documents
    * Replacing a document
    * Querying documents
  * Support for stored procedures
    * Creating a stored procedure
    * Deleting a stored procedure
    * Executing a stored procedure
    * Getting (listing) a stored procedure
    * Replacing a stored procedure
  * Support for permissions
    * Creating a permission
    * Deleting a permission
    * Getting a permission
    * Listing a permission
    * Replacing a permission


## Connection Types
Azure Cosmos DB connections use the following authentication types:
  * Key Token authentication
Provides an all access key token.
  * Resource Token authentication
Provides temporary (1-5 hours), limited access to resources in your account without providing direct access to the master key.


## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * Azure Cosmos DB Connector Reference
  * MuleSoft Help Center
Migrating API Gateways | MuleSoft Documentation
# Migrating API Gateways
This section covers the migration of API Gateway related features. Following topics will be explained:
  * Migrating API Gateways: Autodiscovery
  * Migrating Mule 3 Applications Managed in API Manager
  * Migrating API Gateways: Policies
  * Migrating API Gateways: Proxies
  * Migrating API Gateways: Mule Runtime Configuration


## See Also
Core Components Migration
Microsoft Teams Connector 1.1 | MuleSoft Documentation
# Microsoft Teams Connector 1.1
Anypoint Connector for Microsoft Teams (Microsoft Teams Connector) gives you access to the Microsoft Teams APIs. This connector exposes the most commonly used operations provided by the Microsoft Teams APIs.
For compatibility information and fixed issues, see the Microsoft Teams Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The Microsoft Teams APIs
  * Anypoint Connectors
  * Mule runtime engine (Mule)
  * Elements and global elements in a Mule flow
  * Creating a Mule app using Anypoint Studio (Studio)


Before creating an app, you must have:
  * Credentials to access the target resource
  * Anypoint Studio version 7.3.5 or later


## Common Use Cases for the Connector
  * Send notifications
Users are notified in Microsoft Teams when a new resource is created or modified in another service, for example, when a new Salesforce case is created.
  * Onboard employees
When a group of people are hired at the same time, and human resources has an email in Gmail or a spreadsheet in Google Sheets that contains information about the new hires, HR can use the email or spreadsheet to trigger different actions:
    * Add users to a workspace
    * Create a channel for all new hires and use it to instantly share important onboarding information with them
    * Archive the new hire channel after onboarding is completed
After the onboarding process is completed, resources can be freed or reused for the next onboarding process.
  * Create new teams for business projects
Create teams for new business projects to streamline and automate the management of team members, for example:
    * After a new team is created for a new business project, the client can quickly and automatically integrate this new team by using Microsoft Teams.
    * After teams are created, as each new employee is hired, the client can automatically execute a series of actions to integrate the new hire by using Microsoft Teams.
    * When a team member is either removed or moved to another team, the client can execute a series of automated steps to reflect this change within Microsoft Teams.
    * When the business project ends, the resources allocated for that business project in Microsoft Teams can be reused or removed.
    * If a manager is hired or replaced, the corresponding group owner of the team can be changed.


## Authentication Types
Microsoft Teams Connector connections use the following OAuth 2.0 grant types:
  * OAuth 2.0 authorization code grant type, which uses an access token from the Microsoft identity platform for authentication
  * OAuth 2.0 client credentials grant type, which uses the identity of the application to access web-hosted resources


## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * Microsoft Teams Reference
  * MuleSoft Help Center
Update InfluxDB License | MuleSoft Documentation
# Update InfluxDB License
To update the InfluxDB license, contact MuleSoft Professional Services for the new license and the update instructions.
Configuring Ingress Endpoints for Mule App Deployment | MuleSoft Documentation
# Configuring Ingress Endpoints for Mule App Deployment
To configure ingress endpoints for a Mule app deployment, complete these tasks:
  1. Create an ingress resource template and apply it in the cluster.
  2. Configure ingress for a Mule app.


## Before You Begin
Before configuring ingress in Runtime Fabric, set up an ingress controller. For a list of ingress controllers, refer to the Kubernetes documentation.
## Create an Ingress Resource Template and Apply it in the Cluster
Use one of the example templates to create an ingress resource.
  1. Copy the example template into a new file and modify it according to the notes.
  2. Include a `.yaml` extension in the file name.
  3. To apply an ingress template, run:
```
kubectl apply -f <TEMPLATE_FILENAME.yaml>
```



If there is an issue in the template, Kubernetes `api-server` returns an error and the command fails.
After you apply a template successfully, you can view it with:
```
kubectl describe ingress [Ingress Name] -n rtf
```

## Configure Ingress for a Mule App
You configure ingress for an application when you deploy it to Runtime Fabric using Runtime Manager. Available hosts and paths for an application come from the ingress resource template configured by the Runtime Fabric administrator.
You can also use this procedure to deploy a test application to validate your ingress resource template.
The following provides an overview of how to configure ingress for an application. Refer to Deploy a Mule Application to Runtime Fabric for complete deployment instructions. If you are using the Mule Maven plugin to deploy applications to Runtime Fabric, the deployment settings parameter `publicUrl` in the block `http` can accept a comma-delimited string of multiple endpoints. For more information, see deploymentSettings Parameters Reference.  
---  
  1. Navigate to Runtime Manager and follow the documentation to deploy an application to Runtime Fabric.
  2. Select **Ingress**.
  3. From the **Host** drop-down list, select a host for the application.
  4. If the hostname uses a wildcard, add a subdomain in the **Subdomain** field.
The **Subdomain** field is only available if the hostname uses a wildcard.
  5. In the **Path** field, add a URL path to the application’s endpoint:
  6. To preview the endpoint, click the generated preview link.
  7. To add additional endpoints, click **+ Add Endpoint**.
  8. When ready, click **Deploy application**.


## See Also
  * Configure Ingress in Runtime Fabric
Automatic App Restarts | MuleSoft Documentation
# Automatic App Restarts
CloudHub 2.0 restarts your Mule applications during infrastructure failure or maintenance, security patching, replica crashes, or replica rebalancing.
The CloudHub 2.0 infrastructure performs a graceful shutdown by draining connections before transitioning traffic to a new instance of your application replica and terminating the older instance. If your application configuration explicitly sets the `shutdownTimeout` attribute to a value greater than two minutes and thirty seconds, the total shutdown grace period is five minutes. Otherwise, the grace period is twice the configured `shutdownTimeout` value. By default, `shutdownTimeout` is five seconds. See Global Configurations Reference.
```
<mule ...>
 <configuration shutdownTimeout="150000" /> <!-- This sets shutdownTimeout to 2 minutes, 30 seconds. Default is 5 seconds. -->
</mule>
```

To ensure business resiliency, design your application to be idempotent and deploy across multiple replicas with clustering enabled with a layer of persistence (Object Store v2).
## Infrastructure Failure and Maintenance
If the compute infrastructure suffers a failure, CloudHub 2.0 moves your application to a healthy infrastructure and restarts the application replicas. Likewise, during infrastructure maintenance, the platform moves application replicas running on a compute infrastructure that becomes impaired or end-of-life onto a new infrastructure to ensure availability.
## Security Patching
To mitigate security vulnerabilities, CloudHub 2.0 patches and restarts applications every month. See the Critical Security Vulnerabilities policy.
## Replica Crash
If an application replica crashes for any reason, CloudHub 2.0 automatically restarts it. If it continues to fail to start, the platform attempts to restart it using an exponential backoff policy.
## Replica Rebalancing
The CloudHub 2.0 infrastructure optimizes application efficiency through replica rebalancing. This process gracefully moves and restarts replicas, provided there are at least two replicas available.
During rebalancing, a maximum of 30% of an application’s replicas are rebalanced concurrently. The system rounds up this percentage to the number of replicas that can be disrupted. For example, if your application has two replicas, a disruption affects one replica, exceeding the configured 30%.
This method ensures that the application’s configuration, including the Mule runtime version and the infrastructure, remains consistent after all restarts, except for restarts occurring after a security patching. For more details about security patching, see CloudHub 2.0 Operating System Patch Updates.
SAP S/4HANA OData Connector 2.9 - XML and Maven Support | MuleSoft Documentation
# SAP S/4HANA OData Connector 2.9 - XML and Maven Support
Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Studio.
If you manually code a Mule runtime engine (Mule) app in XML either from the Anypoint Studio XML editor or from a text editor, you can get access to the connector in your app by adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file.
When you install the connector in Studio, Studio automatically populates the XML code with the connector’s namespace and schema location. It also adds a dependency to the `pom.xml` file.
## Add a Reference Namespace Statement for the Connector
Paste the following code inside the `mule` tag of the header of your configuration XML:
```
http://www.mulesoft.org/schema/mule/s4hana
http://www.mulesoft.org/schema/mule/s4hana/current/mule-s4hana.xsd
```

This example shows how the namespace statements are placed in the XML:
```
<mule xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core"
xmlns:s4hana="http://www.mulesoft.org/schema/mule/s4hana"
xmlns:http="http://www.mulesoft.org/schema/mule/http"
xmlns="http://www.mulesoft.org/schema/mule/core"
xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core
http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/http
http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/s4hana
http://www.mulesoft.org/schema/mule/s4hana/current/mule-s4hana.xsd
http://www.mulesoft.org/schema/mule/ee/core
http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">
```

## Add a POM File Dependency
The Apache Maven `pom.xml` file generated by Anypoint Studio contains Mule app connector dependencies. When you code a Mule app manually, include this XML snippet in your POM file to enable access to this connector:
```
<dependency>
 <groupId>com.mulesoft.connectors</groupId>
 <artifactId>mule-sap-s4hana-cloud-connector</artifactId>
 <version>x.x.x</version>
 <classifier>mule-plugin</classifier>
</dependency>
```

Verify that the connector `version` corresponds to the one you are using.
To obtain the most up-to-date `pom.xml` file information:
  1. Go to Anypoint Exchange.
  2. In Exchange, click **Login** and supply your Anypoint Platform username and password.
  3. In Exchange, search for `SAP S/4HANA OData`.
  4. Click **Dependency Snippets**.


## Next Step
After completing your namespace and pom.xml file, you can try the Examples.
## See Also
  * Using Anypoint Studio to Configure SAP S/4HANA OData Connector MuleSoft Help Center
Receive HTTP Requests | MuleSoft Documentation
# Receive HTTP Requests
Anypoint Connector for HTTP (HTTP Connector) has a Listener operation that receives requests over the HTTP or HTTPS protocol. Receiving a request and other incidents initiate a Mule event. The event passes the request body to the next element of the flow as the message payload. In addition to the payload, the Mule message includes attributes. You can refer to attributes, such as headers, query parameters, and so on using HttpRequestAttributes syntax.
When you configure an HTTP request, do not set the Content-Type header. The Mule runtime engine (Mule) automatically infers the header from the message payload. If you set the Content-Type header for payload formatted as `multipart/form-data`, the HTTP request fails with a 400 error status.
## HTTP Request Mapping
The following diagram explains how to access information about the request.
You use DataWeave syntax to access this information.
## HTTP Responses
The response to a request can include the following information:
  * Status code
  * Reason phrase
  * Headers


You can configure a response for a successful or failed execution of the flow of the listener. By default, the former presents the payload as a body and yields a 200 status code. By default, the latter presents the error description as a body and yields a 500 status code.
## Securing Requests and Responses
The HTTP method most often configured for an HTTP or HTTPS Listener operation is GET. The HTTP Listener default allows all the HTTP Methods. Follow the best practice to limit the allowed HTTP methods to only the method or methods for your app.
Configure Allowed Methods in Advanced:
## TLS Configuration with Keystores and Truststores
You can use Transport Layer Security (TLS) and configure HTTPS by providing a key store with your certificate. You can also enable 2-way authentication by providing a trust store. For details, see Configure TLS with Keystores and Truststores.
## See Also
  * HTTP Connector XML Reference
  * HTTP Connector Reference
MuleSoft Accelerators Release Notes | MuleSoft Documentation
# MuleSoft Accelerators Release Notes
The following release notes are available for Accelerators:
  * MuleSoft Accelerator for Consumer Goods Release Notes
  * MuleSoft Accelerator for Financial Services Release Notes
  * MuleSoft Accelerator for Healthcare Release Notes
  * MuleSoft Accelerator for Life Sciences Release Notes
  * MuleSoft Accelerator for Manufacturing Release Notes
  * MuleSoft Accelerator for Retail Release Notes
  * MuleSoft Accelerator for Salesforce OMS Release Notes


## See Also
  * MuleSoft Accelerators Overview
Salesforce Pub/Sub Connector | MuleSoft Documentation
# Salesforce Pub/Sub Connector
Anypoint Connector for Salesforce Pub/Sub (Salesforce Pub/Sub Connector) enables you to connect to the Pub/Sub API, which provides a single interface for publishing and subscribing to platform events, including real-time event monitoring events and change data capture events. This connector complements Anypoint Connector for Salesforce (Salesforce Connector) and provides additional ways to interface with Salesforce’s ecosystem. The Salesforce Pub/Sub API enables you to publish and subscribe to events and request schemas and topic information with one API.
For information about compatibility and fixed issues, refer to the Salesforce Pub/Sub Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The Salesforce Pub/Sub Connector’s API
  * Anypoint Connectors
  * Mule runtime engine (Mule)
  * Elements and global elements in a Mule flow
  * How to create a Mule app using Anypoint Studio


Before creating an app, you must have:
  * Credentials to access the Salesforce Pub/Sub target resource
  * Anypoint Platform
  * Anypoint Studio version 7.3.5 or later


## Common Use Cases For the Connector
These are some common use cases for Salesforce Pub/Sub Connector:
  * Subscribe to event monitoring real-time events
  * Subscribe to a standard or high volume platform event, such as `AppointmentSchedulingEvent`
  * Publish a platform event (high volume only) back into Salesforce to restrict a user’s profile when they log in to Salesforce after working hours
  * Subscribe to change data capture events and syn order data in an external inventory system


For examples of these use cases, refer to Salesforce Pub/Sub Connector Examples.
## Connection Types
Salesforce Pub/Sub connections use the following authentication types:
  * Basic Authentication Uses a username and a password for authentication
  * OAuth v2.0 Delegates user authentication to the service hosting the user account
  * OAuth JWT Uses OAuth 2.0 with a JSON Web Token (JWT) request for user authentication
  * OAuth Username Password Uses OAuth 2.0 with a username and a password for authentication
  * OAuth SAML Uses OAuth 2.0 with a signed SAML 2.0 assertion to request an access token


For information about configuring authentication types, refer to Configure a Global Element for the Connector.
## Next Step
After you complete the prerequisites, you are ready to create an app and configure the connector using Anypoint Studio.
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * Salesforce Pub/Sub Connector Reference
  * MuleSoft Help Center
Process Execution Plans | MuleSoft Documentation
# Process Execution Plans
The process execution plans show you the times processes are executed.
Processes are executed if following prerequisites are fulfilled:
  * The current time lies inside the time interval defined by at least one schedule in the run configuration.
  * The current time lies inside the time interval defined by at least one service time of the bot.
  * The current time lies outside of all downtimes of all applications used by this process.


## Before You Begin
  * Ask an organization administrator in Access Management to assign you the required permissions:
Action | RPA Permission | Deprecated RPA Permission  
---|---|---  
Open the **Process Execution Plans** view and see all processes for which you are part of the process team. | RPA Operations Viewer, RPA Operations Manager, RPA Administrator | Process Execution Plans Open  
Open the **Process Execution Plans** view and see all processes of all teams. | RPA Operations Manager, RPA Administrator | Global Process Execution Plans View  


## View the Execution Timetable of a Process
View the execution timetable to see the effective run time of a process.
If there are more sessions assigned than free sessions available, the number of runs of a process within this timeframe depends on its priority.
  1. In the **Process Execution Plans** view of the **Process Operations** module, click the icon **Execution timetable** in the row of the process you want to view.
  2. Click on the Gantt chart of a configuration to view the composition of the effective runtime.


## See Also
  * Deploying Automations
  * Queuing Process Sessions
CLI for Local Servers | MuleSoft Documentation
# CLI for Local Servers
Use the `servers` commands to automate your Local Servers Processes. For more information about how to use these commands, refer to the Runtime Manager documentation.
Command | Description  
---|---  
runtime-mgr:server:describe |  Describes server  
runtime-mgr:server:delete |  Deletes server  
runtime-mgr:server:list |  Changes an standalone application artifact  
runtime-mgr:server:modify |  Modifies server  
runtime-mgr:server:token |  Gets server registration token. This token needs to be used to register a new server  
## runtime-mgr:server:describe
```
> runtime-mgr:server:describe [flags] <serverId>
```

Describes the server passed in `serverId`.
This command accepts the `--output` flag. Use the `--output` flag to specify the response format. Supported values are `table` (default) and `json`.
This command accepts the default flags.
## runtime-mgr:server:delete
```
> runtime-mgr:server:delete [flags] <serverId>
```

Deletes the server passed in `serverId`.
This command accepts the default flags.
This command does not prompt twice before deleting. If you send a delete instruction, it does not ask for confirmation.   
---  
## runtime-mgr:server:list
```
> runtime-mgr:server:list [flags]
```

Lists all servers in your environment.
This command accepts the `--output` flag. Use the `--output` flag to specify the response format. Supported values are `table` (default) and `json`.
This command accepts the default flags.
## runtime-mgr:server:modify
```
> runtime-mgr:server:modify [flags] <serverId>
```

Modifies the server passed in `serverId`.
In order to update the id for the cluster, you need to pass the `--name` flag.
This command accepts the default flags.
## runtime-mgr:server:token
```
> runtime-mgr:server:token [flags]
```

Gets server registration token. This token needs to be used to register a new server.
This command accepts the default flags.
time | MuleSoft Documentation
# time
## time(parts: TimeFactory): Time
Creates a `Time` value from values specified for `hour`, `minutes`, `seconds`, and `timezone` fields.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
`Number` values for `hour`, `minutes`, and `seconds` fields, and a `TimeZone` value for the `timezone` field. Valid values are 0 through 23 for the `hour`, 0 through 59 for `minutes`, and 0 through 59 (including decimals, such as 59.99) for `seconds` fields. The `timezone` must be a valid `TimeZone` value, such as `|-03:00|` You can specify the name-value pairs in any order, but the output is ordered as a default `Time` value, such as `10:10:10-03:00`. The input fields are parts of a `TimeFactory` type.  
### Example
This example shows how to create a value of type `Time`.
#### Source
```
%dw 2.0
import * from dw::core::Dates
output application/json
---
{
 newTime: time({ hour: 12, minutes: 30, seconds: 40 , timeZone: |-03:00| })
}
```

#### Output
```
{
  "newTime": "12:30:40-03:00"
}
```
View Server Information (Hybrid) | MuleSoft Documentation
# View Server Information (Hybrid)
Private Cloud Edition 
The **Servers** tab in Runtime Manager enables you to view a list of the servers, server groups, clusters, and API gateways in an environment. From this tab, you can also perform actions on these components.
  1. From Anypoint Platform, select **Runtime Manager**.
  2. Click the **Servers** tab.
Runtime Manager displays a list of servers, which includes the following information:     
Displays the name of the server, API gateway, server group, or cluster.     
Displays the current status.     
Indicates whether the component is a Mule server, API gateway, server group, or cluster. 

**Version**
    
Displays the version of API gateway or Mule.
  3. Click the **Type** column to view additional properties and actions in the details pane.
  4. Click the name of the component to view its dashboard.


## Details Pane
The details pane includes:
  * Status of the component
  * Mule or API gateway version
  * Runtime Manager agent version
  * **Manage Server** , **Manage Group** , or **Manage Cluster** button, which takes you to the **Settings** page
  * **View Dashboard** button, which takes you to the server’s dashboard page
To view the dashboard for a server in a server group or cluster, click the server name in the details pane.
  * For clusters, the type (unicast or multicast)


The tabs in the bottom provide more detail:
  * Server groups and clusters display the list of servers and their statuses
  * The applications running and the status of each
  * Any plugins, such as Splunk and ELK


Figure 1. The screen shows the **Applications** tab, servers list, and **Plugins** tab.
## Server Dashboard
The server dashboard provides detailed performance metrics, including heap memory and CPU performance:
Figure 2. The screen shows the **Heap Memory** graph, applications list, and **CPU** graph.
This dashboard also provides the following information:
  * A list of applications deployed to the server
  * The status of each application
  * Mule messages for each application
  * Error messages for each application


## See Also
  *   * Server Groups Status States
  *   * Export Data to External Analytics Tools
  * Monitoring Dashboards on Runtime Manager
countCharactersBy | MuleSoft Documentation
# countCharactersBy
## countCharactersBy(text: String, predicate: (character: String) -> Boolean): Number
Counts the number of times an expression that iterates through each character in a string returns `true`.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
The string to which the `predicate` applies.  
`predicate` | Expression to apply to each character in the `text` string. The expression must return a Boolean value.  
### Example
This example counts the digits in a string.
#### Source
```
%dw 2.0
import * from dw::core::Strings
output application/json
---
"42 = 11 * 2 + 20" countCharactersBy isNumeric($)
```

## countCharactersBy(text: Null, predicate: (character: Nothing) -> Any): Null
Helper function to make `countCharactersBy` work with a `null` value.
_Introduced in DataWeave version 2.4.0._
Delete File | MuleSoft Documentation
# Delete File
_Delete File_ will delete a file located at the specified path. The action step can be used, for example, to delete files which were generated within a _Workflow_. If the file for deletion does not exist, the action step does **not** terminate the Workflow with an error. There is however an option that enables the generation of an error message in the event of a non-existent file.
## Properties
**File Operation Settings**
  * **Directory path** Enter the path to the directory from which the file is to be deleted. You can specify an absolute or relative path. If a relative path is used, then the path relates to the _Base Path_ variable.
  * **File Name** The name of the file to delete.
This field does not support placeholders. For further information, see Path / file name / invalid characters.
  * **Force error if file does not exist** If this option has been enabled, an error message will interrupt the _Workflow_ if the file for deletion does not exist. If this option is not enabled and the file does not exist, the _Workflow_ will continue and no error message will be generated.


Other Properties that are the same in all action steps are described in the section on **Common Properties**. For reasons of clarity they are not shown here.
## Inbound Variables
  * **Directory path** Enter the path to the directory from which the file is to be deleted. You can specify an absolute or relative path. If a relative path is used, then the path relates to the _Base Path_ variable.
  * **File Name** Enter the name of the file that is to be deleted.


## Outbound Variables
**IsDeleted** The _Delete File.IsDeleted_ variable indicates whether the file could be deleted or not (True/False).
**File Name** The _Delete File.File Name_ variable provides the name of the file that is to be deleted.
**Directory path** The _Delete File.Directory Path_ variable provides the path that is used.
## Wizard
  * **Directory path** Specify the path to the file that is to be deleted. You can create an absolute path or a path relative to the _Base Path_. The initial value is %STWS_BASEPATH%. Select an existing path. You can also insert variables from the _Workflow_ in order to construct the path. To do so, click on the pin and select one of the available variables.


  * **File name** Enter the name of the file that is to be deleted. You can also insert a variable from the Workflow as the _File Name_. To do so, click on the pin and select one of the available variables.
  * **Force error if file does not exist** If this option has been enabled, an error message will interrupt the _Workflow_ if the file for deletion does not exist. If this option is not enabled and the file does not exist, the _Workflow_ will continue and no error message will be generated.
MQTT Connector Examples | MuleSoft Documentation
# MQTT Connector Examples
To fully benefit from using Anypoint Connector for MQTT (MQTT Connector), see the following examples of configuring the connector:
  * Configure Quality of Service Configure the quality of service (QoS) to specify levels of delivery assurance for inbound or outbound messages.
  * Configure the Last Will and Testament Message Configure the Last Will and Testament message to notify all the topic subscribers of the client’s disconnection from the broker.
  * Set a client ID with MQTT Connector Configure client ID generators that enable you to set a client ID.
  * Listen for New Messages Configure the **On New Message** source to listen for messages on a unique or multiple topics, and listen for messages on multiple topics using single-level or multilevel wildcards.
  * Publish a Message Configure the **Publish** operation to publish a message to the desired topic with a specific quality of service.
  * Listen and Publish Messages Configure the **On New Message** source and the **Publish** operation to listen and publish messages to a specific topic.
  * Deploy MQTT Connector Apps in a Cluster Understand the client ID behavior of MQTT Connector when deploying Mule apps in a cluster.


## See Also
  * Introduction to Anypoint Connectors
  * MuleSoft Help Center
Dates (dw::core::Dates) | MuleSoft Documentation
# Dates (dw::core::Dates)
This module contains functions for creating and manipulating dates.
To use this module, you must import it to your DataWeave code, for example, by adding the line `import * from dw::core::Dates` to the header of your DataWeave script.
_Introduced in DataWeave version 2.4.0._
## Functions
Name | Description  
---|---  
| Returns a new `DateTime` value that changes the `Time` value in the input to the beginning of the specified _day_.  
| Returns a new `DateTime` value that changes the `Time` value in the input to the beginning of the specified _hour_.  
| Returns a new `DateTime` value that changes the `Day` value from the input to the first day of the specified _month_. It also sets the `Time` value to `00:00:00`.  
| Returns a new `DateTime` value that changes the `Day` and `Time` values from the input to the beginning of the first day of the specified _week_.  
| Takes a `DateTime` value as input and returns a `DateTime` value for the first day of the _year_ specified in the input. It also sets the `Time` value to `00:00:00`.  
Creates a `Date` value from values specified for `year`, `month`, and `day` fields.  
Creates a `DateTime` value from values specified for `year`, `month`, `day`, `hour`, `minutes`, `seconds`, and `timezone` fields.  
| Creates a `LocalDateTime` value from values specified for `year`, `month`, `day`, `hour`, `minutes`, and `seconds` fields.  
Creates a `LocalTime` value from values specified for `hour`, `minutes`, and `seconds` fields.  
Creates a `Time` value from values specified for `hour`, `minutes`, `seconds`, and `timezone` fields.  
Returns the date for today as a `Date` type.  
Returns the date for tomorrow as a `Date` type.  
Returns the date for yesterday as a `Date` type.  
## Types
Extract Pages from PDF File | MuleSoft Documentation
# Extract Pages from PDF File
Extract pages from a PDF file, customize the output, and create a new PDF file with the configured settings. Use this action step to split PDF files, combine multiple PDF files into one, or extract specific pages to create a new PDF file.
## Properties
  * **File Settings**
    * **Create Target PDF if it doesn’t exist**
Select this option to create the PDF file if the specified output file name doesn’t exist. Otherwise, the action step fails if the file doesn’t exist.
    * **Extraction Page Range**
The pages to extract from the input PDF. Use commas (`,`) to separate multiple ranges and `EOF` to specify the end of the file. This action step reads the pages in the specified order. For example, the value `1-5, EOF-6` outputs a file that contains pages from one to five in the original order and the remaining pages in reverse order, from last to six.
    * **Input File Directory Path**
Path to the input file directory.
    * **Input File is Password Protected**
If the input file is password protected, select this option and specify the password in the wizard.
    * **Input File Name**
Name of the input file.
    * **Insert Mode**
Select where to insert the extracted content in the output file. Available options: `StartOfDocument`, `SpecificPage`, or `EndOfDocument`.
    * **Insert Position**
Select the page after which to insert the extracted content. If the PDF file doesn’t exist, and **Create Target PDF if it doesn’t exist** is selected, the action step inserts the pages at the beginning of the document.
    * **Output File Directory Path**
Path to the output file directory.
    * **Output File is Password Protected**
Select this option if the output file is password protected and specify the password in the Wizard.
    * **Output File Name**
Name of the output file.


## Inbound Variables
  * **Input File Directory Path**
  * **Input File Name**
  * **InputFilePassword**
  * **Extraction Page Range**
  * **Output File Directory Path**
  * **Output File Name**
  * **OutputFilePassword**
  * **Insert Position**


## Outbound Variables
The _Extract Pages from PDF File_ action step has no outbound variables.
## Wizard
  * **Input File Settings**
Configure the settings for the input file to read: **Directory path** , **File name** , **Page Range** , and **Password** (if the file is password protected).
  * **Output File Settings**
Configure the settings for the output file to write: **Directory path** , **File name** , **Page Range** , and **Password** (if the file is password protected). Also specify if the action step creates the output file if it doesn’t exist and select where to insert the pages in the output file.
Prerequisites for MuleSoft Accelerator for Financial Services | MuleSoft Documentation
# Prerequisites for MuleSoft Accelerator for Financial Services
This page provides a summary of the guides available for configuring the various systems and products required to implement the use cases provided by this solution. The individual systems needed, and amount of configuration required, depend on which assets are to be deployed in your target environment(s) - refer to the use case pages for more details.
## Available Guides
The following setup and configuration guides are available for this accelerator:
  * Anypoint MQ setup guide
  * Payments modernization demo setup guide
  *   * Salesforce Data Cloud setup guide
  * Salesforce Financial Services Cloud setup guide
  * Salesforce Marketing Cloud setup guide


Most of the implementation templates also contain details on requirements specific to those applications.
## See Also
  *   * MuleSoft Accelerator for Financial Services
Text Recognition | MuleSoft Documentation
# Text Recognition
Text Recognition enables you to use different methods of Optical Character Recognition(OCR) to analyze images and extract text from them.
  * Using the AI OCR (file-based) action step, existing images such as document scans can be recognized.
  * The AI OCR (screen-based) action step attempts to extract texts from screenshots of the currently active desktop.
  * Intelligent OCR (2020)
The Intelligent OCR (2020) action step supports the following additional languages: Arabic, Greek, Hebrew, and Thai.
hammingDistance | MuleSoft Documentation
# hammingDistance
## hammingDistance(a: String, b: String): Number | Null
Returns the Hamming distance between two strings.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
The first string.  
The second string.  
### Example
This example shows how `hammingDistance` behaves with different strings.
#### Source
```
%dw 2.0
import hammingDistance from dw::core::Strings
output application/json
---
"holu" hammingDistance "chau"
```
Google Workspace | MuleSoft Documentation
# Google Workspace
Access your Google Drive and perform operations such as downloading or exporting, uploading, or searching for files or folders.
These action steps require you to provide your Google API Service Account Credentials. You can specify these credential in the corresponding activity parameter and then link them through a pin variable or specify the values inline in each action step.
  * Download from Google Drive
Download files from your Google Drive. You can also export files to a different format.
  * Search for files or folders in your Google Drive.
  * Upload files to your Google Drive.