BassemE/mulesoft-documentation-embeddings huggingface dataset:
ServiceNow Connector 6.11 | MuleSoft Documentation
# ServiceNow Connector 6.11
Anypoint Connector for ServiceNow (ServiceNow Connector) provides connections between Mule runtime engine (Mule) and ServiceNow apps. Use the ServiceNow operations with the custom ServiceNow tables, along with any operations available through the installed plugins.
For compatibility information and fixed issues, see the ServiceNow Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * Anypoint Connectors
  * Mule runtime engine (Mule)
  * Elements in a Mule flow and global elements
  * How to create a Mule app using Anypoint Studio


Before creating an app, you must have access to the ServiceNow target resource and Anypoint Platform.
## Common Use Cases for the Connector
Common use cases for ServiceNow Connector include:
  * **IT Service Management (ITSM)**
Sync ServiceNow data and extend IT service management (ITSM) capabilities to SaaS and on-premises applications, such as Salesforce, SAP, Workday, and Microsoft Dynamics 365, to help with data migration and replication, application integration, and consolidation. For example, you can bidirectionally sync workers data between Workday and ServiceNow or aggregate employees from Workday and users from ServiceNow into a CSV file.
  * **Integrated Business Processes**
Fully integrate business processes across HR, legal, procurement, operations, marketing, and facilities departments.
  * **Record Creation and Retrieval**
Transform enterprise IT by automating and managing IT service relationships to create a single system of records that you can retrieve.


For examples of these use cases, refer to ServiceNow Connector Examples.
## Audience
  * New users, read:
    * Using Anypoint Studio to Configure the Connector to create your Mule app
  * Advanced users, read:
    * XML and Maven Support
    * Examples, which provides one or more use cases for the connector


## Connection Types
The following authentication types are supported:
  * Basic
  * OAuth 2.0 Authorization Code


### Limitations
  * OAuth 2.0 Authorization Code authentication works only with the following versions of Mule:
    * 4.1.5
    * 4.2.1 and later
  * Metadata does not work with OAuth 2.0 Authorization Code authentication.


## Use 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.
  * Workday and ServiceNow Worker Bidirectional Sync
  * Workday Worker to ServiceNow Service Request Migration
  * Workday and ServiceNow Employee Aggregation
  * Workday to ServiceNow Service Worker Migration
  * Workday Worker to ServiceNow Service Request Broadcast


## 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
  * Use Anypoint Exchange to Discover Connectors, Templates, and Examples
  * ServiceNow Connector Release Notes
  * ServiceNow Connector on Exchange
  * MuleSoft Help Center
Viewing the Flex Gateway API Status in Runtime Manager | MuleSoft Documentation
# Viewing the Flex Gateway API Status in Runtime Manager
To view basic information about APIs associated with Flex Gateway instances:
  1. From Anypoint Platform, select **Runtime Manager**.
  2. Select **Flex Gateway** in the navigation menu.
  3. Click the name of the gateway whose APIs you want to check.
  4. Click **APIs**.
For each API, Runtime Manager shows the name, version, instance ID, label, and date on which it was added.


To see more detailed information and perform actions on your APIs, click **View details** to be redirected to API Manager.
System Validation | MuleSoft Documentation
# System Validation
_System Validation_ compares various parameters (see Section **Checking System Parameters**) between the system the _Workflow_ was created on and the system where it is executed. It does not have any additional properties on the _Properties grid_.
## Properties
_System Validation_ has no further properties _._
## Variables
_System Validation_ possesses no variables.
## Wizard
The wizard shows a list of all system parameters that are available to be checked; these can all be selected separately. The _Compare Value_ column shows the current value that will be checked against. Click _Reset_ to set the value to the system’s current value. Finally, you can choose what happens when two values differs. You can either select to display an _Info_ , _Warning,_ or _Error_ message, or set an actual _Error State_ that causes the _Workflow_ to fail and throw a warning or error. For example, you could prevent a system with a different desktop resolution from executing the _Workflow_.
Configure the Service URI | MuleSoft Documentation
# Configure the Service URI
When using a load balancer in front of a RAML or OAS API implementation, to ensure that the URL specified in the proxy matches the one in your API, enable the **Keep RAML/OAS base URI** flag.
To edit the code, set the `keepApiBaseUri` to `true`:
```
<apikit:config name="api-config"
        api="api.raml"
        outboundHeadersMapName="outboundHeaders"
        httpStatusVarName="httpStatus"
        keepApiBaseUri="true" />
```
SAP S/4HANA SOAP Connector 2.2 - Get Started | MuleSoft Documentation
# SAP S/4HANA SOAP Connector 2.2 - Get Started
Anypoint Connector (SAP S/4HANA SOAP Connector) provides full support for the SOAP APIs exposed by SAP S/4HANA Cloud ERP, and starting with version 2.1, also provides support for SAP S/4HANA on-premise ERP. This connector enables you to automatically discover SOAP services enabled on your SAP S/4HANA instance and to invoke the SOAP service and associated operations.
For software requirements and compatibility information, see the SAP S/4HANA SOAP Connector Release Notes.
## Before You Begin
Before you create an app and use this connector, you must:
  * Have a developer account or other valid SAP S/4HANA instance.
  * Have a MuleSoft Enterprise license.
  * Enable discovery service in your SAP S/4HANA instance.
  * Have a communication user that is assigned to the corresponding communication arrangements for the desired APIs.
  * Be familiar with:
    * SAP S/4HANA SOAP
    * Mule runtime engine (Mule)
    * Anypoint Connectors
    * Anypoint Studio essentials


## Common Use Cases For the Connector
Send an XML request to SAP S/4HANA’s SOAP API and print a response.
## Using 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 SOAP Connector Release Notes
  * SAP S/4HANA SOAP Connector on Exchange
  * MuleSoft Help Center
MuleSoft Automation Credits 1.0 | MuleSoft Documentation
# MuleSoft Automation Credits 1.0
Your MuleSoft Automation subscription plan includes a quota of Automation Credits that you can use with MuleSoft Composer, MuleSoft IDP, MuleSoft RPA, or a combination of these products. As you use processes to create automations, your total credit quota is depleted.
The following table shows the conversion rate between Automation Credits and different activities:
RPA Bot Minutes | RPA API Calls | Composer Tasks | IDP Document Pages  
---|---|---|---  
1 MuleSoft Automation Credit = 2 | 1 MuleSoft Automation Credit = 100 | 1 MuleSoft Automation Credit = 50 | 1 MuleSoft Automation Credit = 6  
You can use any combination of these activities, which aggregate over the term of your subscription (not per session), and are then converted to credits as shown. Then, the credits are deducted from your assigned quota for the subscription period.
For detailed definitions and more information, see the MuleSoft Product Subscription Plans.
## See Also
  * Automation Credits Usage and Rates
Set Payload Transformer | MuleSoft Documentation
# Set Payload Transformer
The Set Payload (`set-payload`) component lets you update the payload of the message. The payload can be a literal string or a DataWeave expression. The `set-payload` component, however, is not recommended for complex expressions or transformations but rather, simple ones, such as selections. You should use Transform Message Component for complex scenarios.
Field | Usage | Description  
---|---|---  
Value (`value`) | Required | Accepts a literal string or DataWeave expression that defines how to set the payload, for example, `"some string"` or `#[now()]`.  
Mime Type (`mimeType`) | Optional | The mime type of the value assigned to the payload, for example, `text/plain` or `application/json`.  
Encoding (`encoding`) | Optional | The encoding of the value assigned to the payload, for example, `UTF-8`.  
The `mimeType` and `encoding` attributes will not affect a DataWeave expression used as `value`. They only affect the output Mule Message. If a transformation is required, the DataWeave expression must contain an explicit output directive.  
---  
This XML example sets a payload with static values:
Static Content Example:
```
<set-payload value="{ 'name' : 'Ana', 'office' : 'BA' }" mimeType="application/json" encoding="UTF-8"/>
```

The next example sets the message payload to "Hello, World" appending today’s date using a DataWeave expression: `#['Hello World!' ++ ' Today is ' ++ now()]`
Expression Content Example:
```
<set-payload value="#['Hello World!' ++ ' Today is ' ++ now()]"/>
```

## See Also
  * Mule Message Structure
  * DataWeave Language
Unrecognized partner transaction reported | MuleSoft Documentation
# `Unrecognized partner` transaction reported
You might occasionally see tracking information such as this in the Activity section of Anypoint Partner Manager:
```
<identifier> from Unrecognized partner
<date> control #
Partner not found for <identifier> with <value>
```

## Causes
This information appears in the Activity section when one of the following occurs:
  * Partner Manager cannot identify the sender of the transmission either because the partner is not configured in Partner Manager, or because the identifier associated with the partner is not configured.
  * Partner Manager cannot identify the receiver for the transmission because the identifier associated with the receiver is not configured.
  * Partner Manager cannot identify both the sender and the receiver of this transmission.


## Solutions
Verify partner and host identifiers.
### Verify Partner’s Identifiers
Verify that your partner has the appropriate identifiers configured as needed to support the transmission.
  1. From within your Anypoint Partner Manager, Sandbox or Production environment select **Partners** <name of your specific partner related to this transmission>.
  2. From the Partners profile, scroll to the Identifiers section and verify that the identifier you are looking for is present in the table.
  3. If the desired partner identifier is not present, click **New** and select an identifier type from the Type list to uniquely identify your partner.
  4. Provide a value for your identifier (and a qualifier for X12-ISA) and click **Create identifier** to save your changes. See X12 - ISA Identifier Values for more information about X12-ISA settings.


### Verify Organization (Host) Identifiers
Verify that your organization (the host) has the appropriate identifiers configured as needed to support the transmission.
  1. From within your Anypoint Partner Manager, Sandbox or Production environment select **Partners** <name of your organizations / sub-organizations related to this transmission>.
  2. Within the Host’s profile page, scroll to the Identifiers section and verify that the identifier you are looking for is present in the table.
  3. If the desired host identifier is not present, click **New** and select an identifier type from the Type list to uniquely identify your partner.
  4. Provide a value for your identifier (and a qualifier for X12-ISA) and click **Create identifier** to save your changes. See X12 - ISA Identifier Values for more information about X12-ISA settings.
atBeginningOfWeek | MuleSoft Documentation
# atBeginningOfWeek
## atBeginningOfWeek(dateTime: DateTime): DateTime
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_.
The function treats Sunday as the first day of the week.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
The `DateTime` value to reference.  
### Example
This example changes the `Day` and `Time` values (`06T18:23:20.351`) within the `DateTime` input to the beginning of the first day of the specified _week_ (`04T00:00:00`).
#### Source
```
%dw 2.0
import * from dw::core::Dates
output application/json
---
{
 atBeginningOfWeekDateTime: atBeginningOfWeek(|2020-10-06T18:23:20.351-03:00|)
}
```

#### Output
```
{
 "atBeginningOfWeekDateTime": "2020-10-04T00:00:00-03:00"
}
```

## atBeginningOfWeek(localDateTime: LocalDateTime): LocalDateTime
Returns a new `LocalDateTime` value that changes the `Day` and `Time` values from the input to the beginning of the first day of the specified _week_.
The function treats Sunday as the first day of the week.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
`localDateTime` |  The `LocalDateTime` value to reference.  
### Example
This example changes the `Day` and `Time` values (`06T18:23:20.351`) within the `LocalDateTime` input to the beginning of the first day of the specified _week_ (`04T00:00:00`).
#### Source
```
%dw 2.0
import * from dw::core::Dates
output application/json
---
{
 atBeginningOfWeekLocalDateTime: atBeginningOfWeek(|2020-10-06T18:23:20.351|)
}
```

#### Output
```
{
 "atBeginningOfWeekLocalDateTime": "2020-10-04T00:00:00"
}
```

## atBeginningOfWeek(date: Date): Date
Returns a new `Date` value that changes the `Date` input input to the first day of the specified _week_.
The function treats Sunday as the first day of the week.
_Introduced in DataWeave version 2.4.0._
### Parameters
Name | Description  
---|---  
The `Date` value to reference.  
### Example
This example changes the `Day` value (`06`) within the `Date` input to the first day of the week that contains `2020-10-06` (a Tuesday), which is `2020-10-04` (a Sunday). The `Day` value changes from `06` to `04`.
#### Source
```
%dw 2.0
import * from dw::core::Dates
output application/json
---
{
 atBeginningOfWeekDate: atBeginningOfWeek(|2020-10-06|)
}
```

#### Output
```
{
 "atBeginningOfWeekDate": "2020-10-04"
}
```
Revoke and Delete API Contracts | MuleSoft Documentation
# Revoke and Delete API Contracts
As the Organization Administrator of the root organization, you can revoke or delete a contract that is providing an application access to your API. When you revoke a contract, you can restore the contract at any time.
Deleting a contract deletes the approved contract from Anypoint Exchange. Revoking a contract blocks the client application from accessing the API. When you revoke a contract, you can either restore or delete the contract anytime. Before you delete a contract, you must first revoke it.
To delete a contract with an application:
  1. Navigate to **Anypoint Platform** > **API Manager**.
  2. In **API Administration** , click the name of the API instance for which you want to revoke access.
  3. Click the `<api version>:<api instance or label>` link, for example, `v1:16046365`.
  4. Click **Contracts**.
  5. For the application for which you want to revoke access, click **Revoke**.
The **Restore** and **Delete** options appear.
  6. To delete the contract, click **Delete**.


## See Also
  * Requesting Access to API Instances from Exchange
  * Removing API Instance Contracts
  * Obtaining Client ID and Client Secret Credentials of a Client Application
Amazon Lambda Connector 1.0 | MuleSoft Documentation
# Amazon Lambda Connector 1.0
Anypoint Connector for Amazon Lambda (Amazon Lambda Connector) enables you to execute AWS Lambda operations within your Mule flows. You can then use the response of the Lambda operation to process another Mule flow as needed.
For compatibility information and fixed issues, see the Amazon Lambda Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The AWS Lambda 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:
  * AWS Identity and Access Management (IAM) access key credentials
  * Access to the AWS Lambda target resource
  * Anypoint Studio version 7.3 or later


## Common Use Case for the Connector
When your app manages large amounts of streaming data from various sources, Amazon Lambda Connector enables you to send the data stream to an AWS Lambda application that is specifically designed to quickly pull and process the required information. This enables you to manage necessary realtime tasks without slowing down your main application.
## Authentication Types
AWS Lambda Connector supports AWS Lambda authentication.
## See Also
  * Introduction to Anypoint Connectors
  * Use Exchange to Discover Connectors, Templates, and Examples
  * MuleSoft Help Center
replace | MuleSoft Documentation
# replace
## replace(text: String, matcher: Regex): ((Array<String>, Number) -> String) -> String
Performs string replacement.
This version of `replace` accepts a Java regular expression for matching part of a string. It requires the use of the `with` helper function to specify a replacement string for the matching part of the input string.
### Parameters
Name | Description  
---|---  
A string to match.  
A Java regular expression for matching characters in the input `text` string.  
### Example
The first example in the source replaces all characters up to and including the second hyphen (`123-456-`) with an empty value, so it returns the last four digits. The second replaces the characters `b13e` in the input string with a hyphen (`-`).
#### Source
```
%dw 2.0
output application/json
---
["123-456-7890" replace /.*-/ with(""), "abc123def" replace /[b13e]/ with("-")]
```

#### Output
```
[ 7890, "a-c-2-d-f" ]
```

### Example
This example replaces the numbers `123` in the input strings with `ID`. It uses the regular expression `(\d+)`, where the `\d` metacharacter means any digit from 0-9, and `+` means that the digit can occur one or more times. Without the `+`, the output would contain one `ID` per digit. The example also shows how to write the expression using infix notation, then using prefix notation.
#### Source
```
%dw 2.0
output application/json
---
[ "my123" replace /(\d+)/ with("ID"), replace("myOther123", /(\d+)/) with("ID") ]
```

#### Output
```
[ "myID", "myOtherID" ]
```

## replace(text: String, matcher: String): ((Array<String>, Number) -> String) -> String
Performs string replacement.
This version of `replace` accepts a string that matches part of a specified string. It requires the use of the `with` helper function to pass in a replacement string for the matching part of the input string.
### Parameters
Name | Description  
---|---  
The string to match.  
The string for matching characters in the input `text` string.  
### Example
This example replaces the numbers `123` from the input string with the characters `ID`, which are passed through the `with` function.
#### Source
```
%dw 2.0
output application/json
---
{ "replace": "admin123" replace "123" with("ID") }
```

#### Output
```
{ "replace": "adminID" }
```

## replace(text: Null, matcher: Any): ((Nothing, Nothing) -> Any) -> Null
Helper function that enables `replace` to work with a `null` value.
_Introduced in DataWeave version 2.4.0._
Optionally Configure Search in CMS Content | MuleSoft Documentation
# Optionally Configure Search in CMS Content
Anypoint API Community Manager stores some content, such as news articles and blog posts, in a content management system or _CMS_. To include this content in search results, enable the Salesforce CMS content manager.
## CMS Application Permissions
Open your administrator profile and ensure that it has the following CMS application permissions:
  * **Manage Content Permissions** : Create, edit, and delete library permissions in Salesforce CRM Content.
  * **Manage Content Properties** : Create, edit, and delete custom fields in Salesforce CRM Content.
  * **Manage Record Types and Layouts for Files** : Create, edit, and delete content types in Salesforce CRM Content.
  * **Manage Salesforce CRM Content** : Create, edit, and delete libraries and library memberships.


## Enable Salesforce CMS
To enable Salesforce CMS for API Community Manager:
  1. In the administrative interface, open **CMS Administrator**.
  2. If the interface shows a message that you have no content available yet, create content:
    1. Open the control panel.
    2. Click the apps icon in the top left and use the **Search apps and items…​** box to find and open the Salesforce CMS app.
    3. Select **CMS Workspaces**.
    4. Click **Add Workspace**.
    5. Enter the name and description of the workspace.
    6. Click **Next**.
    7. Select the channel for each community that has CMS content to include in your community’s search results.
    8. If you have contributors, add them.
    9. Choose the languages for your translated content.
    10. Click **Next**.
    11. Verify the information.
    12. Click **Done**.
    13. Create a new collection and upload content.
  3. Enable search in the community channel:
    1. Open the control panel.
    2. Click the apps icon in the top left and use the **Search apps and items…​** box to find and open the Salesforce CMS app.
    3. Open the **CMS Home** tab and use the drop-down menu to open **CMS Channels**.
    4. Find your site on the list and, in the **Search** column, open the drop-down menu and click **Edit**.
    5. In the **Channel Settings** menu, open the **Search** tab and click **Enable Search**.
    6. In the **Search By Content Type** menu, select which content types are enabled and disabled for search.
    7. Click **Save**.
  4. Add your community URL to remote site settings:
    1. Open **Setup**.
    2. Use the **Quick Find** box to find and open **Remote Site Settings**.
    3. Click **New Remote Site**.
    4. Choose a **Remote Site Name** for your site.
    5. Copy and paste your community’s URL into the **Remote Site URL** field.
    6. Click **Save**.
  5. Verify that your user has the option **Salesforce CMS Content User** enabled.
  6. Open the community builder, open the Lightning component **ACM Search Box** , and enable the option **Search in Managed Content**.
  7. Open your community, use the site search, and verify that the **Managed Content** tab is visible.


## See Also
  *   * Publish Content and CMS Articles
A2A Schema Validation Policy | MuleSoft Documentation
# A2A Schema Validation Policy
**Policy Name** | A2A Schema Validation  
---|---  
Validates Agent requests to ensure they conform to the A2A specification  
**First Flex Gateway version available**  
**Returned Status Codes**  
This policy supports Agent2Agent Protocol (A2A) versions v0.2.3 and earlier. To learn more about A2A versions, see A2A Releases.   
---  
## Summary
The A2A Schema Validation policy validates that every request to the A2A server complies with the A2A schema. If validation fails it will report a Policy Violation.
There are no configuration parameters for this policy.
### Flex Gateway Local Mode
The A2A Schema Validation policy isn’t supported in Local Mode.
Manage Categories | MuleSoft Documentation
# Manage Categories
Process team members organize projects into categories.
Manage a set of categories from which process team members can choose one when they create a process evaluation or an automation project.
A category describes the environment of a process in a few keywords, for example `Customer Support Mythical University` or `Finance`.
A process can only belong to a single category.
First, create a standard category, so the process team can start with process automation quickly. The team can change the category of a process later. After the team automates the first few projects, create an archive category to move the completed projects there.
## 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 Automation** module. | RPA Automations Designer, RPA Automations Contributor, RPA Automations Manager, RPA Administrator | Process Automation Open  


## View All Categories
To view all existing categories for automation projects, open the **Process Management** view of the **Process Automation** module.
## Create a Category
Create a category that process team members can choose when they create a process evaluation or an automation project.
The name of a category should consist of a unique set of distinct keywords that describe the common environment of a set of processes.
To create a category:
  1. Open the **Process Management** view of the **Process Automation** module.
  2. Click **Create**.
  3. Enter a name in the **Create a category** window.
  4. Click **OK**.


The category panel shows the number of contained projects and how many are in development and in production.
## Edit a Category
Edit a category to render its name more precisely:
  1. Open the **Process Management** view of the **Process Automation** module.
  2. Click **Edit** () on the panel of the category to edit.
  3. Change the name in the **Edit the category** window.
  4. Click **OK**.


## Remove a Category
Remove categories that are no longer needed.
You can only remove categories that do not contain processes.
To remove a category:
  1. Open the **Process Management** view of the **Process Automation** module.
  2. Click **Remove** () on the panel of the category to delete.


## Open a Category
To view the contained projects, open the category:
  1. Open the **Process Management** view of the **Process Automation** module.
  2. Click the name of the category.


The project panels show the data and actions of the project.
## See Also
  * Assign a Category to a Process Evaluation
  * Assign a Category to an Automation Project
Replacing Mule License Keys | MuleSoft Documentation
# Replacing Mule License Keys
When your Mule license expires, you must replace your Mule license key. Also use this procedure if you entered an incorrect license key during installation.
Perform the following steps on the controller node used to start the installation. For Azure and AWS installations, this node is named `rtf-controller-1` by default.
## Install rtfctl
The `rtfctl` utility is required to replace your Mule license key on Runtime Fabric. Follow the steps in Install rtfctl before continuing.
Confirm that the `rtfctl` binary is present in the current working directory and in the user `$PATH`.
Run `rtfctl` commands as a privileged user.
## Procedure
  1. Base64 encode the new Mule `.lic` license file provided by MuleSoft:
     * On MacOS, run the following command in the terminal:
```
BASE64_ENCODED_LICENSE=$(base64 -b0 -i license.lic)
```

     * On Unix, run the following command:
```
BASE64_ENCODED_LICENSE=$(base64 -w0 license.lic)
```

     * On Windows, choose one of the following:
       * Use a WSL or Cygwin shell that includes the base64 tool and use the above Unix command.
       * Use the `base64.exe` program included with Windows git (`C:\Program Files\Git\usr\bin`).
       * Use the following Powershell command:
```
$BASE64_ENCODED_LICENSE=[convert]::ToBase64String((Get-Content -path "license.lic" -Encoding byte))
```

  2. Use the `rtfctl` utility to apply the Base64 value of your license key. For more information on the `rtfctl` command, refer to rtfctl commands.
```
rtfctl apply mule-license $BASE64_ENCODED_LICENSE
```

  3. To verify the Mule license key has applied correctly, retrieve the contents using the `rtfctl` utility:
```
rtfctl get mule-license
```



You need to restart your Runtime Fabric Mule apps to take the latest changed license.   
---  
## Get License Expiry Date
The `GET` fabric API `(/organizations/{organizationId}/fabrics/{id})` response includes an optional `licenseExpiryDate` field:
```
{
  "id": "fabric_id",
  "name": "anna-qa-gke-rtf-1",
  "region": "us-east-1",
  "vendor": "gke",
  "vendorMetadata": {},
  "organizationId": "organization_id",
  "version": "2.2.9",
  "status": "Active",
  "desiredVersion": "2.2.9",
  "availableUpgradeVersion": "2.2.29",
  "createdAt": 1679684859167,
  "secondsSinceHeartbeat": 192,
  "kubernetesVersion": "v1.24.11-gke.1000",
  "licenseExpiryDate": 1653523200000,
  "isManaged": false,
  "isHelmManaged": true,
  "clusterConfigurationLevel": "production",
  "features": {
    "enhancedSecurity": true,
    "persistentStore": false
  },
  "ingress": {
    "domains": []
  }
}
```

The Runtime Fabric **Mule License Expiry Date** is also exposed in the Runtime Manager UI, with a warning notification of **License is expiring soon** :
## See Also
  *
Creating New Projects Synchronized from Existing GitHub Repositories | MuleSoft Documentation
# Creating New Projects Synchronized from Existing GitHub Repositories
You can create a new API Designer project and synchronize it with an existing GitHub repository.
## Before You Begin
Before you create and synchronize a project, ensure you have:
  * The Design Center Developer permission within Anypoint Platform
  * Installed and authorized the GitHub Synchronization application
  * Signed into GitHub


## Synchronize A New Project
  1. On the Design Center **Projects** page, click **Create new**.
  2. Select **Sync from existing GitHub Repo**.
  3. In the **New Project** dialog, specify a name in the **Project Name** field.
  4. Select an organization and repository from which to synchronize your new project.
The **GitHub Organization** dropdown list displays GitHub organizations that have the GitHub Synchronization application installed. No organizations or repositories are listed if the application is not installed.   
---  
  5. Click **Import As**.
  6. Choose the type of API project to sync: **API Specification** or **API Fragment**.
You are navigated to the new project’s text editor.


## See Also
  * Create an API Specification with the Text Editor
  * Helpful Features in the Text Editor
  * Publish an API Specification
Intelligent OCR (2020) | MuleSoft Documentation
# Intelligent OCR (2020)
The _Intelligent OCR (2020)_ action step represents a good alternative to the previous OCR (Legacy OCR). The new OCR contains the languages Arabic, Greek, Hebrew, and Thai.
## Properties
**Color Depth** (bpc) In documents with many images and colors, a setting with low color depth leads to faster search results. You can select a value between 0 and 8. Value 0 means that the color depth remains unchanged compared to the original.
**Enhance Contrast** Adjusts the image contrast so that the legibility of the text is improved.
**Image Type**
  * **Auto** (default) The document type is determined automatically
  * **Document** Can improve the OCR operation of a document (PDF)
  * **Snippet** Can improve the OCR operation of selected text sections


**Recognition Strategy**
  * **Fast** The OCR operation is carried out faster but this can lead to poorer scan quality
  * **Advanced** (default) The OCR operation can take longer but the results are optimal


## Outbound Variables
The outbound variables are identical to those in the Legacy OCR.
## Wizard
**Scaling Mode**
**Auto Scale by Engine** (default) Scaling to a higher resolution takes place automatically if this improves the OCR operation. This can lead to slightly longer search operations and also requires more main memory.
**Scale by 1** The scaling of the recorded image is set to 1.
**Manual scale** In the _Manual scale_ mode, you can determine the scaling factor yourself. You can enter an enlargement value of between 1 and 4 in each case. It is **not** recommended to use a high value (4) in combination with a large image excerpt.
**Dictionary**
The following languages are available here
Arabic | Italian  
---|---  
Chinese (simplified) | Japanese  
Chinese (traditional)  
Norwegian  
Portuguese  
In contrast to the situation with action step _Legacy OCR,_ here you can combine the Asian languages with each other, and also with the other languages.
You can select a maximum of two languages at any time.
**Retries [0..5]** (Default: 3) With this menu option, it is possible to repeat the search recognition up to 5 times. If the text recognition is successful, no further attempt is carried out. This option only appears if you have selected text, Regex, or fuzzy comparison in search mode.
Common Mistake in Specifying Required Fields in JSON Schemas | MuleSoft Documentation
# Common Mistake in Specifying Required Fields in JSON Schemas
Design Center supports both JSON Schema Draft 3 and JSON Schema Draft 4. The method of specifying fields as `required` differs in Draft 3 from the method used in Draft 4. In your API specifications, an error is indicated if you mix the method that you are using with a declaration of the wrong draft.
In Draft 3, you specify fields as `required` in the definition of each field, as in this example:
```
{
 "$schema": "http://json-schema.org/draft-03/schema#",
 "type": "object",
 "properties": {
  "pageNum": {
   "type": "integer",
   "title": "Page number",
   "description": "...",
   "default": 1,
   "required": true
  },
  "pageSize": {
   "type": "integer",
   "title": "Page size",
   "description": "...",
   "required": true,
   "default": 50,
   "enum": [
     10,
     20,
     30,
     40,
     50
     ]
   }
...
```

In Draft 4, you specify that fields are `required` by creating an array that is at the same level as the definitions of the fields, like this:
```
{
 "$schema": "http://json-schema.org/draft-4/schema#",
 "type": "object",
 "properties": {
  "pageNum": {
   "type": "integer",
   "title": "Page number",
   "description": "...",
   "default": 1
  },
  "pageSize": {
   "type": "integer",
   "title": "Page size",
   "description": "...",
   "default": 50,
   "enum": [
     10,
     20,
     30,
     40,
     50
     ]
   },
 "required": [
   "pageNum",
   "pageSize"
   ]
  },
...
```

Here is another example of the method used in Draft 4:
```
{
 "$schema": "http://json-schema.org/draft-4/schema#",
 "type": "object",
 "properties": {
  "address": {
   "type": "object",
   "properties": {
    "streetAddress": {
     "type": "string"
    },
    "city": {
     "type": "string"
    },
 "required": [
     "streetAddress",
     "city"
    ]
   },
   "phoneNumber": {
...
```

If you have used the Draft 3 method after declaring that the schema uses Draft 4, or vice versa, in most cases you can simply change the schema declaration. For example, if you declared that your schema uses Draft 3, but the schema uses the method from Draft 4, you can change your schema declaration to point to Draft 4.
Data Sheets | MuleSoft Documentation
# Data Sheets
These data sheets offer further information about Anypoint API Community Manager.
  *   * Connectivity with MuleSoft Government Cloud
  * 

For the list of supported browsers, see Browser Support for Anypoint Platform.
API Community Manager is not certified for use on mobile devices. Some functionality works on mobile devices, but some functionality such as the API console does not.
Upgrading and Migrating Cassandra Connector to Version 4.x | MuleSoft Documentation
# Upgrading and Migrating Cassandra Connector to Version 4.x
Upgrade Cassandra Connector to version 4.x to use mutual TLS authentication.
## Supported Upgrade Paths
From Version | To Version  
---|---  
## New Features in This Release
This release supports Mutual TLS authentication.
## Changes in This Release
This release contains the following changes:
  * Removed the **SSL** field from the configuration and replaced it with **TLS**
  * Refactored error handling and error types


## Upgrade Prerequisites
Before you perform the upgrade, create a backup of your files, data, and configurations in case you need to restore to them.
## Upgrade Steps
Follow these steps to perform the upgrade:
  1. In Anypoint Studio, create a Mule project.
  2. In the **Mule Palette** view, click **Search in Exchange**.
  3. In **Add Dependencies to Project** , enter `cassandra` in the search field.
  4. In **Available modules** , select **Cassandra** and click **Add**.
  5. Click **Finish**.
  6. Verify that the Cassandra Connector dependency version is `<4.0.0>` in the `pom.xml` file in the Mule project.


Studio upgrades the connector automatically.
### Verify the Upgrade
After you install the latest version of the connector, follow these steps to verify the upgrade:
  1. In Studio, verify that there are no errors in the **Problems** or **Console** views.
  2. Verify that there are no problems in the project `pom.xml` file.
  3. Test the connection to verify that the operations work.


## Revert the upgrade
If it is necessary to revert to the previous version of Cassandra Connector, change the `cassandra-connector` dependency version in the project’s `pom.xml` file to the previous version.
You must update the project’s `pom.xml` file in Anypoint Studio.
## See Also
  * Introduction to Anypoint Connectors
  * MuleSoft Help Center
Using the Command Palette | MuleSoft Documentation
# Using the Command Palette
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.
The Command Palette in Anypoint Code Builder is the control center for all commands you use to perform tasks. Knowing how to open it is important for your productivity.
  1. Open the Command Palette in one of the following ways:
     * Use the keyboard shortcuts:
       * Mac: Cmd+Shift+p
       * Windows: Ctrl+Shift+p
     * In the desktop IDE, select **View** > **Command Palette**.
     * In the cloud IDE, click the (menu) icon, and select **View** > **Command Palette** :
  2. Type `MuleSoft:` and browse the available commands:


For a list of MuleSoft commands, see Command Reference.
## See Also
  * Learn Anypoint Code Builder UI
  * Customize Look and Feel
Click Web Element | MuleSoft Documentation
# Click Web Element
Simulate mouse input on a website element.
The available click types are:
  * **Single Left Click**
  * **Single Left Click (Wait for page load)**
Waits for the page to finish loading and then simulates the click. If the page does not load, the action step fails.
  * **Double Left Click**
  * **Single Right Click**
  * **No Click (Hover)**
Simulates a mouse hover.


## Properties
Organization Management Overview | MuleSoft Documentation
# Organization Management Overview
This topic is affected by the Anypoint Platform integration.
If you use an Anypoint account to login to RPA Manager, refer to the **Settings** documentation.
If you use an RPA account to login to RPA Manager, the **Organization Management** module enables you to configure the currency and decimal sign to show in RPA Manager modules and configure your Anypoint Platform credentials, which enables you to publish a process automation to Anypoint Exchange.
Gmail Connector 1.0 | MuleSoft Documentation
# Gmail Connector 1.0
Anypoint Connector for Gmail (Gmail Connector) enables the management of your Gmail account, including sending and receiving emails and reacting to received emails.
For information about compatibility and fixed issues, see the Gmail Connector Release Notes.
## Before You Begin
To use this connector, you must be familiar with:
  * The Gmail 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 Gmail target resource
  * Anypoint Platform
  * Anypoint Studio version 7.0 or later


## Common Use Cases For the Connector
Some possible uses for this connector include:
  * Sending an email to thank customers for a new purchase.
  * Organizing all emails related to an event.
  * Receiving attachments via email to verify an ID.


## Connection Types
Gmail connections use the Oauth2c authentication type, which uses access tokens provided by the authorization server to access protected data.
For information about configuring authentication types, see Using Anypoint Studio to Configure Gmail 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
  * Gmail Connector Reference
  * MuleSoft Help Center
Configuring Client Management with OpenAM | MuleSoft Documentation
# Configuring Client Management with OpenAM
  1. Sign in to Anypoint Platform using an account that has the Organization Administrator permission.
  2. In the navigation bar or the main Anypoint Platform page, click **Access Management**.
  3. In the **Business Groups** menu, select your root organization.
  4. In the Access Management navigation menu, click **Client Providers**.
  5. Click **Add Client Provider** , and then select **OpenAM**.
The **Add OpenAM client provider** page appears.
  6. Fill in the following required fields:
     * Version
OpenAM version 14.
     * Admin Token Provider
       * Create URL
The endpoint that creates an access token for OAuth authentication.
       * Username
The name of the user requesting access.
       * Password
The password of the user requesting access.
     * OAuth2 Authorization Provider, Authorize URL
`/oauth2/authorize`, relative to the base path of the OpenAM application. Provide the absolute URL (base URI and path).
     * OAuth2 Token Provider, Create URL
`/oauth2/access_token`, relative to the base path of the OpenAM application. Provide the absolute URL (base URI and path).
     * OAuth2 Token Validation Provider
       * Validate URL
The token validation endpoint is `/oauth2/tokeninfo` relative to the base path of the OpenAM application.
       * Username Token Mapping
Name of user with privileges for creating new clients within the target OpenAM system.
     * OAuth2 Client Provider
       * Create URL
The URL at which the OpenAM client management API resources are served. Normally the endpoint is located at `/oauth2/client`. Confirm with your OpenAM administrator.
       * Delete URL
URL destination for sending a DELETE request to delete a test client.
       * Scopes
Supported OAuth capabilities, such as READ and WRITE.
       * Default Scopes
Default OAuth capabilities to use in the event the client app does not specify any.
  7. Save your configuration.


Now, you can apply the OpenAM OAuth Token Enforcement policy to your APIs.
## See Also
  *   * OpenAM and PingFederate OAuth Token Enforcement Policies
Java Module 1.2 | MuleSoft Documentation
# Java Module 1.2
Release Notes: Java Module Release Notes Exchange: Java Module
Mule 4 is built to:
  * Minimize the need for custom code.
  * Avoid the need for you to know or understand Java.


However, some advanced uses cases require integration with custom Java code, such as:
  * Reuse of a library, such as a tax calculation library.
  * Reuse of a canonical object model that is standard in the organization.
  * Execution of custom logic using Java.


In Mule 3, MEL served as a bridge for creating instances of Java classes and executing Java methods. In Mule 4, interoperation with Java changed, due to the replacement of MEL by DataWeave, which is a functional language. Functional languages do not have side effects on their input arguments, so it does not make sense for DataWeave to execute random instance methods on random object instances. Therefore, pure DataWeave supports calling only static Java methods, without use of the Java module.
## Java Module Versus the Scripting Module
You can use the Java module, or execute Groovy code through the Scripting module. However, the Scripting module does not offer DataSense support, user interface support, visual aids for methods available for each class, autocompletion, and so on. See Java Integration.
## See Also
  * Create an Instance of a Class
  *   * Test for an Instance of a Class
  * Work With Throwables
  * Java Module Reference
  * Java Module Argument Transformation
  * MuleSoft Help Center
Process Recording Editor | MuleSoft Documentation
# Process Recording Editor
If you start the recorder from RPA Manager, you can view the current process BPMN and all new recorded BPMNs by selecting them from the drop-down menu.
To open the Process Recording Editor, select a process and click **Edit, Merge and Upload Recordings** ().
## Process Recording Editor Panels
The Process Recording Editor consists of two main panels:
  * **Automation**
This panel provides a fully integrated BPMN modeler to edit the BPMN of the recording. The previously selected Recording session is automatically loaded into the modeler to start editing.
  * **Documentation**
This panel shows the recorded documentation of each activity. Select an element in the **Automation** panel to view its recorded documentation and show the **Edit** option.
The Documentation panel provides a fully integrated text editor. To edit the documentation of any activity, click **Edit**. After editing the documentation, click **Done** to apply the changes.


## Load BPMNs for Edit and Merge
To load additional BPMNs into the BPMN modeler:
  1. Click **Load File** ().
  2. Select the BPMN or BPMNs you want to add and click **Open**.
All recordings are stored in a separate folder per process and recording date.
  3. A dialog asks if you want to merge the selected BPMN into the present BPMN in the modeler, or if you want to create a new BPMN with the selected one. 
  4. To merge the selected BPMN into the existing BPMN, click **Yes** . After the import, you can edit and rearrange the new BPMN via drag and drop.


## Save Edited BPMNs
To save the edited and merged BPMN locally:
  1. Select a directory in the **Save As** dialog and specify a file name if different from the auto-generated file name.
  2. Click **Save**.


## Upload BPMN to RPA Manager
After merging and editing the BPMN and documentation, click the **Upload to RPA Manager** icon () to upload the new process BMPN. A message opens confirming that the upload is completed.
To close the Process Recording Editor and RPA Recorder, click **Close** ().
## See Also
  *