---
schema_version: "1"
id: 6888005f10eee0b5f8bd19a98a8082ac9c448d67556b576602f861b4e445b0e9
title: Adding Policy Implementation Files to Published Policy Definition
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/exchange/add-policy-implementation-files-to-published-policy-definition.md
canonical_url: https://docs.mulesoft.com/exchange/add-policy-implementation-files-to-published-policy-definition
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 0397ae73261cc53df61b52574aa371edd03c5b45509d902326757159bfa1ff49
description: MuleSoft Documentation Site
latest: true
---
---
product: Exchange
---

# Adding Policy Implementation Files to Published Policy Definition

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

When a policy definition asset is published in Exchange, the asset details page displays a
**Pending** flag next to **Implementations** in the left navigation bar. The flag indicates that the
policy implementation has not been added. Add the policy implementation files to the policy
definition to enable the policy to be available in runtime. The required implementation files are a
binary file such as a WebAssembly (WASM) file for Omni Gateway or JAR for Mule 4 runtime and a YAML
metadata file.

Before adding the policy implementation files, ensure that the policy definition asset is in the
Stable state.

To add the policy implementation files:

1.  In Exchange, select the policy asset to open the asset details page.

2.  Click **Implementations** in the left navigation bar.

3.  Click **Add implementation**.

4.  Enter the name for the implementation.

5.  Click **Choose file** to select the JAR or WebAssembly file.

6.  Click **Choose file** to select the YAML file.

7.  To edit the GroupId, AssetId, Version, and API version, click **Advanced**.

    Exchange generates the group ID, asset ID, and version. You can change these values. You can
    also change an API asset’s version and API version separately. The advanced settings are most
    often used to change the asset version.

8.  Click **Add implementation**.

    The implementation displays in the **Manage implementations** table. From this table, manage the
    implementation versions of a policy asset. See [Manage Versions](https://docs.mulesoft.com/exchange/manage-versions) for more
    information.