BassemE/mulesoft-documentation-embeddings huggingface dataset:
Box Connector 5.3 | MuleSoft Documentation
# Box Connector 5.3
Box is an online file sharing and content management service for businesses. Anypoint Connector for Box (Box Connector) is a RAML-based connector that provides synchronization of data and automation of processes between Box and third party CRMs, CMS, mobile, and social applications. Because this is a RAML-based connector, it only uses REST calls to interact with the Box 2.0 API and supports only a subset of available API services.
## Before You Begin
Before creating an app, you must have access to the Box target resource and Anypoint Platform. You must also understand how to create a Mule app using Anypoint Studio.
You should be familiar with the use of the Box 2.0 API, Mule, Anypoint Connectors, Anypoint Studio, Mule concepts, elements in a Mule flow, and global elements.
To use this connector you need the following:
  * A developer account or other valid Box instance.
  * MuleSoft Enterprise License and necessary entitlements.


## Connection Types
Box Connector uses the following authentication types:
  * JWT Server-side authentication using a keypair. For more information about configuring Box Connector with JWT, refer to JWT Authentication.
  * Oauth2security Access tokens provided by the authorization server.


## Next Step
After you complete the prerequisites, you are ready to create an app with Anypoint Studio.
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * Box Connector on Exchange
  * MuleSoft Help Center
partition | MuleSoft Documentation
# partition
## partition<T>(array: Array<T>, condition: (item: T) -> Boolean): { success: Array<T>, failure: Array<T> }
Separates the array into the elements that satisfy the condition from those that do not.
_Introduced in DataWeave version 2.2.0._
### Parameters
Name | Description  
---|---  
The array of elements to split.  
`condition` | The condition (or expression) used to match an element in the array.  
### Example
This example partitions numbers found within an input array. The even numbers match the criteria set by the lambda expression `(item) → isEven(item)`. The odd do not. The function generates the `"success"` and `"failure"` keys within the output object.
#### Source
```
%dw 2.0
import * from dw::core::Arrays
output application/json
var arr = [0,1,2,3,4,5]
---
arr partition (item) -> isEven(item)
```

#### Output
```
{
 "success": [
  0,
  2,
  4
 ],
 "failure": [
  1,
  3,
  5
 ]
}
```

## partition(array: Null, condition: (item: Nothing) -> Any): Null
Helper function that enables `partition` to work with a `null` value.
_Introduced in DataWeave version 2.4.0._
Reproducible Builds | MuleSoft Documentation
# Reproducible Builds
Being able to build a particular version of your Mule project at any time facilitates maintenance, because the versions of your projects in production are not always the latest ones.
To help achieve this goal:
  * Use source control for all your Mule projects and apply branching, merging, and tagging to them. Do not check in Eclipse-specific files. See Git Source Control documentation for details.
  * Manage dependencies strictly by using Apache Maven and an in-house repository manager, such as Nexus. See Maven Support in Mule documentation for guidelines.
Traits & policies concepts of RAML based APIs | MuleSoft Documentation
# Traits & policies concepts of RAML based APIs
If your API exposes a RAML definition that users might need to reference, then the RAML definition should reliably detail every element that is expected in calls to your API. For example when applying a client ID-based policies implies that all requests coming to your API include a client ID and client Secret (by default expected as query parameters). To prevent user requests from being rejected, create a trait in the RAML root and then reference this trait in every operation of your API. The trait might look like this:
```
traits:
 - client-id-required:
   queryParameters:
    client_id:
     type: string
    client_secret:
     type: string
```

And then you can apply this trait in each individual operation like this:
```
/products:
 get:
  is: [client-id-required]
  description: Gets a list of all the inventory products.
```

  1. Click Policies on the API dashboard.
In the list of policies, the RAML snippet link contains the RAML code you need to add to the RAML.
  2. Click RAML Snippet.
  3. Select RAML 0.8 or RAML 1.0 to match the API RAML version.
  4. Edit the API to add the code.
  5. Redeploy the API.


## See Also
  *
DataFormat Annotations (dw::extension::DataFormat) | MuleSoft Documentation
# DataFormat Annotations (dw::extension::DataFormat)
Annotation | Definition | Description  
---|---|---  
DataFormatExtension |  `@DataFormatExtension()` |  Registration hook that the DataWeave engine uses to discover the variable that represents the custom data format. For an example, see the Custom Data Formats Example README.
Amazon S3 Connector | MuleSoft Documentation
# Amazon S3 Connector
Amazon S3 Connector v5.6.x
Anypoint Connector for Amazon S3 (Amazon S3 Connector) provides connectivity to the Amazon S3 API, enabling you to interface with Amazon S3 to store objects, download and use data with other AWS services, and build applications that require internet storage.
Instant access to the Amazon S3 API enables seamless integrations between Amazon S3 and other databases, CMS applications such as Drupal, and CRM applications such as Salesforce. Use Amazon S3 to store and retrieve any amount of data at any time, from anywhere on the web. You can accomplish these tasks by using the simple and intuitive web interface of the AWS Management Console.
AWS SDK for Java provides a Java API for AWS infrastructure services. The Amazon S3 connector is built using the SDK for Java.
Release Notes: Amazon S3 Connector Release Notes Exchange: Amazon S3 connector in Anypoint Exchange
## About Connectors
Anypoint connectors are Mule runtime engine extensions that enable you to connect to APIs and resources on external systems, such as Salesforce, Amazon S3, ServiceNow, and Twitter.
## Before You Begin
Before creating an app, you must have access to the Amazon S3 target resource, Amazon Web Services, and Anypoint Platform. You must also understand how to create a Mule app using Anypoint Studio, and have AWS Identity and Access Management (IAM) credentials.
For the Amazon S3 operations to work, you need to enable or update the subset of the overall list of actions in the Amazon S3 bucket to specify that the AWS account has access these actions.   
---  
To see a list of Amazon S3 operations, see the Amazon S3 Connector Reference.
## Audience
  * Starting user
Read this Get Started document and create your Mule application in Anypoint Studio. The Additional Configuration Information topic helps extend your understanding of the Amazon S3 connector.
  * Power user
Read the XML and Maven Support and Examples topics.


## Next Step
After you have met the prerequisites, you are ready to create an app with Anypoint Studio.
## See Also
MuleSoft Help Center
today | MuleSoft Documentation
# today
## today(): Date
Returns the date for today as a `Date` type.
_Introduced in DataWeave version 2.4.0._
### Example
This example shows the output of `today` function.
#### Source
```
%dw 2.0
import * from dw::core::Dates
output application/json
---
today()
```

#### Output
SAP S/4HANA OData Connector 2.3 | MuleSoft Documentation
# SAP S/4HANA OData Connector 2.3
Anypoint Connector for SAP S/4HANA OData (SAP S/4HANA OData Connector) provides support for the OData APIs exposed by SAP S/4HANA Cloud and SAP S/4HANA on-premise.
The connector enables you to perform operations to:
  * Create, get, update, and delete entities
  * Retrieve a single entity
  * Query multiple entities
  * Invoke a remote function
  * Execute batch requests that consist of multiple requests


For software requirements and compatibility information, see the SAP S4/HANA Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The SAP S/4HANA OData API
  * Anypoint Connectors
  * Mule runtime (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 SAP S/4HANA OData target resource
  * Anypoint Platform
  * Anypoint Studio 7.3 or later
  * Have a developer account or other valid SAP S/4HANA instance


## Common Use Case for the Connector
Perform CRUD operations on entity types of SAP S/4HANA’s OData API and process the response.
## Exchange Templates and Examples
Anypoint Exchange provides templates you can use as a starting point for your app, as well as examples that illustrate a complete solution.
## Next Step
After you complete the prerequisites and experiment with templates and examples, you are ready to create an app with Anypoint Studio.
## See Also
  * Introduction to Anypoint Connectors
  * SAP S/4HANA OData Connector Release Notes
  * SAP S/4HANA OData Connector on Exchange
  * MuleSoft Help Center
Viewing Salesforce Account and Portal Information | MuleSoft Documentation
# Viewing Salesforce Account and Portal Information
The **Settings** page provides information about the Salesforce account and API portal.
To view information about the Salesforce organization and the portal, from the **Manage your API portal** page, click **Settings**.
Salesforce Org information:
  * Environment
  * Username
  * Sandbox name
  * Organization domain
  * Organization ID


API Portal information:
  * Status
  * Publish status
  * API portal URL


## See Also
  * Disconnecting the Portal
NetSuite Connector 11.4 | MuleSoft Documentation
# NetSuite Connector 11.4
Anypoint Connector for NetSuite (NetSuite Connector) synchronizes data and automates business processes between NetSuite and third-party applications, either on-premises or in the cloud. NetSuite provides cloud-based business management software that helps companies manage core business processes, ERP financials, CRM, e-commerce, inventory, and more.
NetSuite Connector provides the following features:
  * SOAP-based integration
NetSuite Connector 11.0 and later does not support REST-based operations.
  * Generation of NetSuite business objects
  * Different authentication levels
  * Error-handling support


For compatibility information and fixed issues, see the NetSuite Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The NetSuite API
  * 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 NetSuite Web Services
  * Anypoint Studio version 7.3.3 or later


## Common Use Cases for the Connector
  * Quote-to-Cash
Improve cash flow, remove manual order entries, and minimize order errors by leveraging realtime integrations to connect and synchronize data about your customer’s intent to buy from your CRM application, such as Salesforce, into its realization of revenue in NetSuite ERP.
  * Invoice-to-Reconciliation
Automate your Accounts Receivable (A/R) process by automatically applying bank payments against invoices in NetSuite for real-time A/R processing. Streamline accounts payable by automating payment file transfers between NetSuite and your banks.
  * Hire-to-Retire
Build a single view of your employees with realtime synchronization of employee information between Netsuite and your Human Capital Management (HCM) services, such as Workday, Oracle HCM, PeopleSoft, and so on. Automatically trigger employee onboarding processes such as ordering computer equipment, uniforms, system access setup, and so on, while reversing the process upon retirement.


## Authentication types
NetSuite connections use token-based authentication, which uses either a consumer key and token ID or secret pairs to authenticate.
For information about configuring this authentication type, see Using Anypoint Studio to Configure NetSuite Connector.
## Using Exchange Templates and Examples
Anypoint Exchange provides the following templates that you can use as starting points for your apps:
  * Retrieve a List of Customers from NetSuite
  * Salesforce and NetSuite Opportunity Aggrgation


## Next Step
After you complete the prerequisites, you are ready to create your own app and configure the connector using Anypoint Studio.
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * MuleSoft Help Center
Handling API Proxy Status Codes | MuleSoft Documentation
# Handling API Proxy Status Codes
In Mule 4, WSDL, RAML, HTTP, and HTTPS proxies handle errors and requests as described in the following tables. Mule 4 returns different error codes, depending on the proxy type, or no error code in response to problematic requests. This table shows whether or not Mule returns a 504, 400, or 404 error code when your WSDL, RAML, HTTP, and HTTPS proxy receives a problematic request.
Error Code | WSDL | RAML | OAS | HTTP | HTTPS  
---|---|---|---|---|---  
504: request timeout  
400: bad request (validation result)  
404: resource not found  
405: method not allowed in API spec
Registering and Running Flex Gateway in Local Mode | MuleSoft Documentation
# Registering and Running Flex Gateway in Local Mode
Before you can use your Flex Gateway to configure API instances, you must register and start the gateway.
There are three options for registering Flex Gateway in Local Mode:
  * Register and Run using a Username and Password: If you have a username and password for Anypoint Platform, you can use these credentials to register your Flex Gateway.
  * Register and Run using a Connected App: If you do not have a username or password for Anypoint Platform, you can use connected app credentials to register your Flex Gateway.
  * Register and Run using a Token: If you do not have a username or password for Anypoint Platform, you can use a registration token generated by the Runtime Manager UI. The token is valid for four hours.
Publishing Automation Assets to Anypoint Exchange | MuleSoft Documentation
# Publishing Automation Assets to Anypoint Exchange
You can connect RPA Manager with your Anypoint Platform account, which enables you to publish a process automation to Exchange. Connecting RPA Manager with your Anypoint Platform account requires a Connected App with the scope RPA Integrator configured in Access Management.
To publish automation assets to Exchange:
  1. Configure a Connected App in Access Management.
  2. Connect RPA Manager with your Anypoint Platform Account.
See Configure Anypoint Platform Credentials for instructions.
  3. Publish a Process Automation to Anypoint Exchange.
See Publish a Process Automation to Anypoint Exchange for instructions.


## Configure a Connected App in Access Management
To create a Connected App in your Anypoint Platform account:
  1. Log in to Anypoint Platform.
  2. Open **Access Management**.
  3. On the navigation panel, click **Connected Apps**.
  4. Click **Create App**.
  5. Specify a **Name** for the Connected App.
  6. In **Type** , select **App acts on its own behalf(client credentials)**.
  7. Click **Add Scopes**.
  8. In the filter box, type **RPA** and select **RPA Integrator** among the results.
  9. Click **Next**.
  10. Select a **Business Group** and click **Review**.
  11. Click **Add Scopes** to confirm.
  12. Click **Save**.


### See the Client ID and Client Secret of a Connected App
After you create a Connected App, it shows in the **Connected Apps** section of Access Management, where you can see the Connected App’s Client ID and Client Secret.
Click either **Copy ID** or **Copy Secret** to copy the corresponding value to the clipboard for further use.
## See Also
  * Create an Anypoint Platform Account
CLI for Local Cluster Servers | MuleSoft Documentation
# CLI for Local Cluster Servers
Use the `cluster` commands to automate your Local Cluster Servers Processes. For more information about how to use these commands, refer to the Runtime Manager documentation.
Command | Description  
---|---  
runtime-mgr:cluster:add:server |  Adds server to cluster  
runtime-mgr:cluster:create |  Creates new cluster  
runtime-mgr:cluster:describe |  Describes server cluster  
runtime-mgr:cluster:delete |  Deletes cluster  
runtime-mgr:cluster:modify |  Modifies cluster  
runtime-mgr:cluster:list |  Lists all clusters in the environment  
runtime-mgr:cluster:remove:server |  Removes server from a cluster  
## runtime-mgr:cluster:add:server
```
> runtime-mgr:cluster:add:server [flags] <clusterId> <serverId>
```

Adds the cluster in `clusterId` to the server passed in `serverId`.
This command accepts the default flags.
## runtime-mgr:cluster:create
```
> runtime-mgr:cluster:create <name> [flags]
```

This command creates a cluster using the id passed in `name`.
In addition to the default flags, this command accepts the following flags:
Flag | Description | Example  
---|---|---  
Whether cluster should be multicast  
Pair of server ID and IP address IP address is optional for multicast cluster Provide multiple values to add multiple servers |  `--server 903083:192.168.0.1`  
This command has multi-option flags. When using multi-option flags in a command, either put the parameter before the flags or use a `-- ` (two dashes followed by a space) before the parameter.   
---  
## runtime-mgr:cluster:describe
```
> runtime-mgr:cluster:describe [flags] <clusterId>
```

Describes the cluster passed in `clusterId`.
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:cluster:delete
```
> runtime-mgr:cluster:delete [flags] <clusterId>
```

Deletes the cluster passed in `clusterId`.
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:cluster:list
```
> runtime-mgr:cluster:list [flags]
```

Lists all clusters in the environment.
This command has 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:cluster:modify
```
> runtime-mgr:cluster:modify [flags] <clusterId>
```

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

Removes the server passed in `serverId` from the cluster passed in `clusterId`.
This command accepts the default flags.
Anypoint VPC Connectivity Methods | MuleSoft Documentation
# Anypoint VPC Connectivity Methods
You can connect an Anypoint Virtual Private Cloud (Anypoint VPC) to your private network using the following methods:
  * IPsec tunnel
  * Transit gateway attachment
  * VPC peering
To connect your Anypoint VPC using VPC peering, contact your MuleSoft Support representative.
  * AWS Direct Connect
To connect your Anypoint VPC using AWS Direct Connect, contact your MuleSoft Support representative.


A maximum of 95 route table entries is allowed per VPC, regardless of the number of connections. To avoid exceeding the limit, consolidate networks to the fewest number possible.   
---  
## IPsec Tunnel
You can use an IPsec tunnel with network-to-network configuration to connect your on-premises data centers to your Anypoint VPC. An IPsec VPN tunnel is generally the recommended solution for VPC to on-premises connectivity, as it provides a standardized, secure way to connect. This method also integrates well with existing IT infrastructure such as routers and appliances.
If you are using a legacy VPN, migrate to Anypoint VPN before making changes.   
---  
To create an Anypoint VPN connection to your network, see Anypoint VPN.
## Transit Gateway Attachments
AWS Transit Gateway acts as a cloud router in AWS, simplifying network access between VPCs, on-premises data centers, and third-party software, while providing increased visibility and control over the network. Transit gateways effectively merge your organization’s cloud resources and on-premises datacenters into one network topology.
On CloudHub, you can take advantage of this network simplification by securely attaching Anypoint VPC to an AWS Transit Gateway in your AWS account.
To use transit gateway attachments, your Anypoint VPC and AWS transit gateway must be in the same region.
To attach your Anypoint VPC to your transit gateway, see Transit Gateway Attachments.
## VPC Peering
VPC peering provides a connection between two VPCs. In this case, it pairs your private Amazon VPC directly to your Anypoint VPC. This enables you to route traffic between the two VPCs so they can communicate as though they are in the same network.
To use VPC Peering, your AWS and Anypoint VPCs must be located in the same region.  
---  
## AWS Direct Connect
To create a Direct Connect connection to Anypoint VPC, create or leverage an existing AWS Transit Gateway on your AWS account and set up the Direct Connect connection to the Transit Gateway. Then, attach Anypoint VPC to the transit gateway and configure the required routing to enable Anypoint VPC on-premises connectivity.
To use Direct Connect, your AWS Direct Connect Partner and the Anypoint VPCs must be located in the same region. Direct Connect gateways are not supported. Direct Connect requires the use of the Border Gateway Protocol (BGP) for dynamic routing. For high availability, use multiple Direct Connect connections from different AWS Direct Connect Locations.  
---  
## See Also
  * Request VPC Connectivity to Your Network
  *   * Transit Gateway Attachments
isWhitespace | MuleSoft Documentation
# isWhitespace
## isWhitespace(text: String): Boolean
Checks if the `text` contains only whitespace.
_Introduced in DataWeave version 2.2.0._
### Parameters
Name | Description  
---|---  
The input string.  
### Example
This example shows how `isWhitespace` behaves with different inputs and sizes.
#### Source
```
%dw 2.0
import isWhitespace from dw::core::Strings
output application/json
---
{
 "a": isWhitespace(null),
 "b": isWhitespace(""),
 "c": isWhitespace(" "),
 "d": isWhitespace("abc"),
 "e": isWhitespace("ab2c"),
 "f": isWhitespace("ab-c")
}
```

#### Output
```
{
 "a": false,
 "b": true,
 "c": true,
 "d": false,
 "e": false,
 "f": false
}
```

## isWhitespace(text: Null): Boolean
Helper function that enables `isWhitespace` to work with a `null` value.
_Introduced in DataWeave version 2.2.0._
Deployment and Server Scaling | MuleSoft Documentation
# Deployment and Server Scaling
To ensure platform stability and performance, Anypoint Platform provides the following recommended and hard limits on the number of deployments, targets, and servers in a hybrid deployment scenario. These limits are specific to an environment in a business group.
A _target_ is any destination for a Mule app, such as a server group, cluster, or on-premises Mule instance. For example, a server group comprised of 8 servers (Mule instances) constitutes a single target.   
---  
To create additional deployments or servers beyond these limits, you can use different accounts, environments, or business groups. To exceed these limits within the same environment, contact your customer success representative.
The tested and recommended limits on the number of deployments in a hybrid deployment scenario are:
Component | Tested/Recommended Limit  
---|---  
Maximum number of deployments per environment  
Maximum number of deployments per hybrid target (not Runtime Fabric)  
Maximum number of properties per application  
Maximum deployment size for CloudHub and standalone  
Maximum deployment size for CloudHub 2.0 and Runtime Fabric  
The hard limits on the number of servers in a hybrid deployment scenario are:
Component | Hard Limit  
---|---  
Maximum number of servers (not Runtime Fabric)  
Maximum number of servers per server group  
Maximum number of servers per cluster  
You can have a maximum of 500 servers which you can combine in any desired number of clusters or server groups. The maximum number of server group-cluster combinations is also 500.
## See Also
  * Servers, Server Groups, and Clusters
Runtime Manager REST API | MuleSoft Documentation
# Runtime Manager REST API
Private Cloud Edition 
The Runtime Manager REST API enables you to programmatically access these functions of Runtime Manager:
  * Manage servers:
    * Register a server.
    * Get a list of registered servers.
    * Get information about a server.
    * Change the server name.
    * Shut down, restart, or delete a server.
    * Renew server certificates.
    * Get a server registration token.
  * Manage server groups:
    * Create a server group from a list of servers.
    * Get a list of registered server groups.
    * Get information about a server group.
    * Change the server group name.
    * Add or remove a server from a server group.
    * Delete a server group.
  * Manage clusters:
    * Create a cluster.
    * Get a list of registered clusters.
    * Get information about a cluster.
    * Change the cluster name.
    * Add or remove a server from a cluster.
    * Modify clustering information for a server.
    * Delete a cluster.
  * Manage app deployments on your servers:
    * Deploy, redeploy, and undeploy apps.
    * Get application deployment and status information.
    * Manage flows, schedulers, and alerts in a deployed app.


For an interactive reference of all the operations that are supported through the API, see Runtime Manager REST Services.
The Runtime Manager REST API manages only on-prem applications deployed to your servers. To manage apps deployed to CloudHub using the API, see CloudHub API.
## Use the Runtime Manager API
To access operations in the Runtime Manager API, you must:
  1. Generate an authorization bearer token (AUTH_BEARER_TOKEN) to authenticate with the API.
To get the access token, you need the Anypoint Platform username and password of a user assigned the Organization Administrators role. See Authentication in the Access Management API.
Your username specifies the environment to access. For example, if your username is `consuela` and the environment is `Development`, your username is `consuela@Development`. If you don’t specify an environment, the API defaults to `Production`.
  2. Get the organization ID (ORG_ID).
See the `/api/me` endpoint in the Access Management API.
  3. Get the environment ID (ENV_ID).
See the `/api/organizations/_ORG_ID_/environments`endpoint in theAccess Management API.


### Get a List of Applications
To get a list of apps deployed on-premises using Runtime Manager, run the following `curl` command:
```
curl -X GET \
 --url https://anypoint.mulesoft.com/hybrid/api/v1/applications \
 -H 'authorization: Bearer AUTH_BEARER_TOKEN' \
 -H 'X-ANYPNT-ENV-ID: ENV_ID' \
 -H 'X-ANYPNT-ORG-ID: ORG_ID'
```

## See Also
  * Servers, Server Groups, and Clusters
  * Deploy to Your Servers
  * Manage Applications on Your Servers
  * Continuous Deployment
NetSuite Connector 11.1 | MuleSoft Documentation
# NetSuite Connector 11.1
Anypoint Connector for NetSuite (NetSuite Connector) synchronizes data and automates business processes between NetSuite and third-party applications, either on-premises or in the cloud. NetSuite provides cloud-based business management software that helps companies manage core business processes, ERP financials, CRM, e-commerce, inventory, and more.
NetSuite Connector provides the following features:
  * SOAP-based integration
NetSuite Connector 11.0 and later does not support REST-based operations.
  * Generation of NetSuite business objects
  * Different authentication levels
  * Error-handling support


For compatibility information and fixed issues, see the NetSuite Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The NetSuite API
  * 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 NetSuite Web Services
  * Anypoint Studio version 7.3.3 or later


## Common Use Cases for the Connector
  * Quote-to-Cash
Improve cash flow, remove manual order entries, and minimize order errors by leveraging realtime integrations to connect and synchronize data about your customer’s intent to buy from your CRM application, such as Salesforce, into its realization of revenue in NetSuite ERP.
  * Invoice-to-Reconciliation
Automate your Accounts Receivable (A/R) process by automatically applying bank payments against invoices in NetSuite for real-time A/R processing. Streamline accounts payable by automating payment file transfers between NetSuite and your banks.
  * Hire-to-Retire
Build a single view of your employees with realtime synchronization of employee information between Netsuite and your Human Capital Management (HCM) services, such as Workday, Oracle HCM, PeopleSoft, and so on. Automatically trigger employee onboarding processes such as ordering computer equipment, uniforms, system access setup, and so on, while reversing the process upon retirement.


## Authentication types
NetSuite connections use token-based authentication, which uses either a consumer key and token ID or secret pairs to authenticate.
For information about configuring this authentication type, see Using Anypoint Studio to Configure NetSuite Connector.
## Using Exchange Templates and Examples
Anypoint Exchange provides the following templates that you can use as starting points for your apps:
  * Retrieve a List of Customers from NetSuite
  * Salesforce and NetSuite Opportunity Aggrgation


## Next Step
After you complete the prerequisites, you are ready to create your own app and configure the connector using Anypoint Studio.
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * MuleSoft Help Center
Create an APIkit for SOAP Project | MuleSoft Documentation
# Create an APIkit for SOAP Project
Create a new Mule project based on a SOAP API specification.
Before proceeding, ensure that you meet the prerequisites for using APIkit for SOAP.
  1. In Anypoint Studio, from **File** , select **New** > **Mule Project**.


In **Project Name** , enter a name for the project. For example, `soap-implementation`.  
---  
Select the Mule runtime engine version. For example, `Mule Server 4.2.2 EE`.  
In **API Specification** , select **From Design Center or Local Files**.  
Select **Browse files** from the **More actions** menu.  
  2. Select a service and port. For this example, accept the default values, `TshirtService` and `TshirtServicePort`.
  3. Click **Finish**.
The new project appears with the WSDL file in the `src/main/resources/api` folder.
  4. Right-click a blank area of the canvas and select **Run Project**.
  5. In your SOAP UI client, go to `http://localhost:8081/TshirtService/TshirtServicePort?wsdl`.
The SOAP service returns the content of your WSDL file.


If you update your WSDL file, regenerate your flows by right-clicking your WSDL file and selecting **Mule** > **Generate Flows From WSDL**.
## See Also
  * Identify Operations to Implement
Current Bot Status | MuleSoft Documentation
# Current Bot Status
In the **Current Bot Status** widget, you can see at a glance which of your bots are ready for use.
## Data Representation
The numbers of Bots in each case are links displayed together with a graphical representation of the ratio of those Bots ready for use compared to those not ready.
The length of the green line labeled with **Ready** corresponds to the number that are ready for use; the length of the red line labeled with **Not Ready** corresponds to the number not ready.
## Configuration
This widget cannot be configured.
## Drill-down
Click on a number to obtain a list of all Bots or only those Bots with a specific status.
### Data Representation of the Current Bot Status
The Bots are displayed in a list.
### Columns of the **Current Bot Status** List
#### Status
The Bot is ready for use.
##### Stopped
The Bot is not ready for use because it has been stopped.
##### No License
The Bot is not ready for use because it is not licensed.
Name of the bot.
Click on the name of the bot to get to its detailed view.
#### Processing
Shows if a process configuration has been deployed to the bot.
Mule API Javadoc | MuleSoft Documentation
# Mule API Javadoc
MuleSoft provides Javadocs for the Mule Kernel (formerly the called Mule Community Edition). Note that the Mule Kernel does not provide all the functionality of the Mule runtime engine, and development with the Mule Kernel is not supported in Anypoint Studio.
The Javadocs contain definitions for classes, fields and their data types, and it also describes methods, including their usage, parameters, and return values.
Read the Mule SDK documentation if you want an easier way to extend the Mule runtime engine to meet your needs. You can find links to the Javadocs below:
## Java Classes
  *   * Mule 4.2.0 is not available.
  *   * Mule 4.4.0 is not available.


## See Also
  *   *
version | MuleSoft Documentation
# version
## version(): String
Returns the DataWeave version that is currently running.
_Introduced in DataWeave version 2.5.0._
### Example
This example returns the DataWeave version.
#### Source
```
%dw 2.0
import * from dw::Runtime
output application/json
---
version()
```
readLinesWith | MuleSoft Documentation
# readLinesWith
## readLinesWith(content: Binary, charset: String): Array<String>
Splits the specified binary content into lines and returns the results in an array.
_Introduced in DataWeave version 2.2.0._
### Parameters
Name | Description  
---|---  
Binary data to read and split.  
String representing the encoding to read.  
### Example
This example transforms binary content, which is separated into new lines (`\n`), in a comma-separated array.
#### Source
```
%dw 2.0
import * from dw::core::Binaries
var content = read("Line 1\nLine 2\nLine 3\nLine 4\nLine 5\n", "application/octet-stream")
output application/json
---
{
  lines : (content readLinesWith "UTF-8"),
  showType: typeOf(content)
}
```

#### Output
```
{
  "lines": [ "Line 1", "Line 2", "Line 3", "Line 4", "Line 5" ],
  "showType": "Binary"
}
```
Defining Rules for Alerts | MuleSoft Documentation
# Defining Rules for Alerts
Specify the incidents that trigger an alert. Each activated rule be checked while configurations are deployed.
## Before You Begin
  * Ask an organization administrator in Access Management to assign you the required permissions:
Action | RPA Permission | Deprecated RPA Permission  
---|---|---  
Open the **Alerting** module. | RPA Operations Viewer, RPA Operations Manager, RPA Administrator | Alerting Open  
Create, edit, and delete alerting targets and rules. | RPA Operations Manager, RPA Administrator | Alerting Administration  
  * Appropriate alert targets must exist in the **Alert Target** view.


## Create an Alert Rule
Create a rule to trigger an alert. You can create alert rules for these types of incidents:
  * Activity Run Result
Run result of a single bot task.
  * Process Run Result
Run result of a process execution.
  * Bot Status
Status of the bot.


The created alert rule is active upon saving. You can deactivate alert rules by clicking the **Deactivate** icon.
  1. In the **Alert Rules** view of the **Alerting** module, click **Create**.
  2. Select the type of the incident to trigger the alert.
  3. Complete the form **Create new <type> rule**.
  4. Click **Save**.


## See Also
  *   * Creating alerting email templates
Configuring Agent Operations for Agentforce Connector 1.1 | MuleSoft Documentation
# Configuring Agent Operations for Agentforce Connector 1.1
## Configure the Start Agent Conversation Operation
The **Start agent conversation** operation establishes the connection between the app and the agent. This is the first step to enable an external application to interact with the AI agent.
  1. Select the operation on the Anypoint Code Builder or Studio canvas.
  2. In the **General** properties tab for the operation, enter these values:
     * **Display Name**
Display name for the operation.
     * **Connector Configuration**
Select the associated configuration for the connector.
     * **Agent list**
Select the agent to invoke. The list shows only agents that are currently active in the org. The connector filters out any agents that aren’t in the `active` state.


### Output
The operation returns a session ID for the interaction between the app and the agent. The session ID is used as an input for the **Continue agent conversation** operation.
## Configure the Continue Agent Conversation Operation
The **Continue agent conversation** operation surfaces the message from the MuleSoft application to the agent. The agent maintains the context of the conversation and provides a relevant response (or actions) according to the user’s input.
  1. Select the operation on the Anypoint Code Builder or Studio canvas.
  2. In the **General** properties tab for the operation, enter these values:
     * **Display Name**
Display name for the operation.
     * **Connector Configuration**
Select the associated configuration for the connector.
     * **Message**
Enter plain text instructions to help the agent make decisions for different use cases.
     * **Session ID**
Enter the session ID that was returned with the **Start agent conversation** operation. This is required to send the prompt defined in the **Message** field to the agent.


## Configure the End Agent Conversation Operation
Use the **End agent conversation** operation to close the session after the agent responds.
Sessions are closed automatically after three days of inactivity.   
---  
  1. Select the operation on the Anypoint Code Builder or Studio canvas.
  2. In the **General** properties tab for the operation, enter these values:
     * **Display Name**
Display name for the operation.
     * **Connector Configuration**
Select the associated configuration for the connector.
     * **Session ID**
Enter the session ID that was returned with the **Start agent conversation** operation.


## See Also
  * Using Anypoint Code Builder to Configure a Connector
  * Using Studio to Configure a Connector
  * Agentforce Connector Reference
  * MuleSoft Help Center
atan | MuleSoft Documentation
# atan
## atan(angle: Number): Number
Returns an arc tangent value that can range from `-pi/2` through `pi/2`.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
Number to convert into its arc tangent value.  
### Example
This example shows how `atan` behaves with different inputs.
#### Source
```
%dw 2.0
import * from dw::util::Math
output application/json
---
{
 "atan0": atan(0),
 "atan13": atan(0.13),
 "atan-1": atan(-1)
}
```

#### Output
```
{
  "atan0": 0.0,
  "atan13": 0.12927500404814307,
  "atan-1": -0.7853981633974483
}
```
Jira Connector 1.2 | MuleSoft Documentation
# Jira Connector 1.2
Anypoint Connector for Jira (Jira Connector) synchronizes data and automates business processes between Jira and third-party applications, either on-premises or in the cloud.
Jira Connector uses the Jira REST API v3 and is only for the Cloud version of Jira.   
---  
Jira is a software development platform to help agile product development teams triage and track their work from inception to launch. Jira Connector enables organizations of all sizes to establish scalable and sustainable product development workflows by connecting Jira to other tools in the organization such as the customer service platforms, project management tools, and others.
For compatibility information and fixed issues, see the Jira Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The Jira 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 Jira resource
  * Anypoint Studio version 7.3.5 or later


## Common Use Cases for the Connector
Automate business processes by integrating Jira with other IT tools and systems in your enterprise such as messaging, CRM, customer service, and others.
Possible use cases include:
  * Enhance customer experience by connecting Jira with your customer service platform, thereby reducing the cycle times between when a customer raises an issue through a customer service platform, like Salesforce’s Sales Cloud, and when that issue gets added to the product team’s work backlog in Jira.
  * Streamline crossteam handoffs by ensuring that the updated information on every issue is available across all systems and stakeholders. For example, when the engineering team marks a customer issue as resolved, update the status across your CRM and customer support platforms, so the customer-facing teams (sales and support) are notified immediately.
  * Foster team collaboration and improve productivity by automating the flow of information between Jira and your team’s communication platform, so that when a new issue gets added to the backlog or an issue gets updated, relevant team members are notified so the appropriate next steps can be taken.


## Authentication Types
Jira Connector connections use the following authentication methods:
  * Basic authentication Uses a username and password for authentication
  * OAuth2 Delegates user authentication to the service hosting the user account


Jira Connector does not support authentication via personal access tokens (PATs).   
---  
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  *   * MuleSoft Help Center
Apply a Tokenization Policy to the API Gateway | MuleSoft Documentation
# Apply a Tokenization Policy to the API Gateway
In this tokenization implementation, you apply the tokenization policy to the API gateway capability of Mule 4, which serves as the intermediary between the Edge and the Mule app. The tokenization service in this case is implicit and made available through internal integration with the API gateway.
## Prerequisites
To configure and use this implementation of the tokenization service, you must:
  * Have permission to manage policies in API Manager See Granting Permission to Access an Environment
  * Have permission to manage tokenization services. See Grant Tokenization Permissions


## Apply the Tokenization Policy
When the tokenization service policy is applied directly to the API gateway, you don’t need to use the tokenization RAML to expose the tokenization service. You only need to set up the API gateway for the Mule app to serve as the proxy.
To apply a tokenization policy to the API gateway:
  1. Beginning Runtime Fabric Installation on VMs / Bare Metal.
  2. Enable inbound traffic on Runtime Fabric.
  3. Create a tokenization format.
  4. Create a tokenization service.
  5. In API Manager, set up the API gateway for the Mule app to serve as the proxy.
You must use the API gateway version 4.0 or later. The Mule app that implements the API can be any version.   
---  
  6. After you configure the API gateway, in API Manager, click **Apply New Policy** and select the tokenization service policy to apply. Available tokenization service policies appear in **Policies > Tokenization**. You can now use the tokenization service to tokenize and detokenize request and response payloads.


## See Also
  *   *   * Tokenization Service Configurations
Preview Your Site | MuleSoft Documentation
# Preview Your Site
After you edit your Salesforce Experience Cloud site, you can preview the new version to ensure that it meets your expectations:
  1. Open the Anypoint API Community Manager control panel.
  2. Click **Community Builder**.
  3. Click **Preview**.
  4. Verify that your changes are applied and display correctly. APIs that are visible only to administrators appear in this preview.
  5. Click **Back to Builder**.
CIM Market Subject Area | MuleSoft Documentation
# CIM Market Subject Area
This defines who you have trading relationships with and how. For example, a customer & supplier along with contact information such as phone number and email address.
## Model Diagrams
The following diagrams show the entities and relationships in this subject area, organized by entity group.
## Implementation
## See Also
  *   * CIM Design Elements
  *   *
Jira Connector 1.0 | MuleSoft Documentation
# Jira Connector 1.0
Anypoint Connector for Jira (Jira Connector) synchronizes data and automates business processes between Jira and third-party applications, either on-premises or in the cloud.
Jira is a software development platform to help agile product development teams triage and track their work from inception to launch. Jira Connector enables organizations of all sizes to establish scalable and sustainable product development workflows by connecting Jira to other tools in the organization such as the customer service platforms, project management tools, and others.
For compatibility information and fixed issues, see the Jira Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The Jira 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 Jira resource
  * Anypoint Studio version 7.3.5 or later


## Common Use Cases for the Connector
Automate business processes by integrating Jira with other IT tools and systems in your enterprise such as messaging, CRM, customer service, and others.
Possible use cases include:
  * Enhance customer experience by connecting Jira with your customer service platform, thereby reducing the cycle times between when a customer raises an issue through a customer service platform, like Salesforce’s Sales Cloud, and when that issue gets added to the product team’s work backlog in Jira.
  * Streamline crossteam handoffs by ensuring that the updated information on every issue is available across all systems and stakeholders. For example, when the engineering team marks a customer issue as resolved, update the status across your CRM and customer support platforms, so the customer-facing teams (sales and support) are notified immediately.
  * Foster team collaboration and improve productivity by automating the flow of information between Jira and your team’s communication platform, so that when a new issue gets added to the backlog or an issue gets updated, relevant team members are notified so the appropriate next steps can be taken.


## Authentication Types
Jira Connector connections use the following authentication methods:
  * Basic authentication Uses a username and password for authentication
  * OAuth2 Delegates user authentication to the service hosting the user account


Jira Connector does not support authentication via personal access tokens (PATs).   
---  
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  *   * MuleSoft Help Center
sqrt | MuleSoft Documentation
# sqrt
## sqrt(number: Number): Number
Returns the square root of a number.
### Parameters
Name | Description  
---|---  
The number to evaluate.  
### Example
This example returns the square root of a number.
#### Source
```
%dw 2.0
output application/json
---
[ sqrt(4), sqrt(25), sqrt(100) ]
```

#### Output