> For the complete documentation index, see [llms.txt](https://releaseowl.gitbook.io/releaseowl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://releaseowl.gitbook.io/releaseowl-docs/releaseowl-user-guide/sap-integration-suite/cpi-management/synchronize-cpi-artifacts.md).

# Synchronize CPI Artifacts

#### SAP CPI Management – Add Packages

1. Navigate to **Build → SAP CPI Management**.
2. Click **Add Packages** to synchronize packages from the registered **SAP Integration Suite** environment.

<figure><img src="/files/hYOhWUnH6WE5yrKJvkVN" alt=""><figcaption></figcaption></figure>

3. The system displays the list of available packages for selection.
4. Select the required packages and click **Add**.

<figure><img src="/files/lmyoCayeOBohBWSUiAJO" alt=""><figcaption></figcaption></figure>

5. After the packages are added, the following details are displayed:

* **Version**
* **Synced On**
* **Synced By**
* **Modified By**
* **Modified On**

<figure><img src="/files/1CtDvPnyRgdR1OcZWKl2" alt=""><figcaption></figcaption></figure>

#### Metadata Behavior

6. For supported artifact types, ReleaseOwl retrieves the **Modified By** and **Modified On** details directly from **SAP Integration Suite**. Supported artifact types include:

* **IFLOW**
* **ODATAAPIPROVIDER**
* **SOAPAPIPROVIDER**
* **RESTAPIPROVIDER**

7. For the following artifact types, **SAP Integration Suite** does not expose metadata details through its public APIs:

* **SCRIPT\_COLLECTION**
* **MESSAGE\_MAPPING**
* **VALUE\_MAPPING**

8. For these artifact types, ReleaseOwl generates the **Modified By** and **Modified On** details based on internal processing activity, indicating when the artifact was last processed or updated within the platform

<figure><img src="/files/GFH9Swjf1DNjHBvjIRUT" alt=""><figcaption></figcaption></figure>

### **Sync History**

Click **Sync History** to view the history of all synchronization activities performed for the **SAP CPI** packages, including previously synced packages and their corresponding sync details.

<div><figure><img src="/files/WUXWNC6QpJXItVHrQkRD" alt=""><figcaption></figcaption></figure> <figure><img src="/files/OmwMuTPI2WFxdO3eveBv" alt=""><figcaption></figcaption></figure></div>

### **Sync Artifacts**

1. After a package is added, click the **Actions** button associated with the package.
2. Select **Sync Artifacts**.
3. Click **Sync Artifacts** to retrieve artifacts associated with the selected package from the registered **SAP Integration Suite** environment.

<figure><img src="/files/YErzcCFvBRBJvOa9Cvep" alt=""><figcaption></figcaption></figure>

### **Remove From Project**

This option is used to remove a package from the project in **ReleaseOwl**. When you select this action, the package is automatically removed from the project and will no longer be available within the project scope.

<div><figure><img src="/files/UwNU5B39gdTnjvIDTXH6" alt=""><figcaption></figcaption></figure> <figure><img src="/files/UhKIsoTftEwNMFrxuBzs" alt=""><figcaption></figcaption></figure></div>

### **Sort**

You can sort the artifacts as per your convenience. To sort them:

1. Click the **Sort icon**.

<figure><img src="/files/R9bIG5MyirqSHry7Ejwr" alt=""><figcaption></figcaption></figure>

2. In the page displayed, choose an option and click **OK**.

<figure><img src="/files/0HXCWLq0YMazRfh4LRke" alt=""><figcaption></figcaption></figure>

### **Actions**

After a package is added to the project, you can view its artifacts and perform various actions on each artifact based on its type.&#x20;

The available actions are described below:

* **Synchronize**\
  Used to sync the latest changes of the artifact from the connected SAP Integration Suite environment into ReleaseOwl. This ensures that the artifact details in ReleaseOwl are up to date.
* **Configure**\
  Used to configure artifact-specific settings required for deployment or execution.
* **Resources**\
  Displays additional supporting information related to the artifact, such as its **type and size**. This helps users quickly understand the nature and storage details of the artifact within the project.
* **Deployment History**\
  Displays the complete history of deployments for the selected artifact, including status and timestamps.
* **Versions**\
  Shows all available versions of the artifact, allowing you to track changes over time.
* **Download**\
  Allows you to download the artifact for offline use or reference.
* **Comment**\
  Enables you to add or view comments related to the artifact for collaboration and tracking purposes.

<figure><img src="/files/PNerqIA2gmMiUYPzR8Vd" alt=""><figcaption></figcaption></figure>

### Synchronize

It is used to retrieve and update the latest artifacts from the connected SAP Integration Suite (CPI) environment into **ReleaseOwl**. This ensures that **ReleaseOwl** reflects the most recent changes made in the source system, including updates to artifact details such as version, configuration, and metadata.

<figure><img src="/files/bZx7bpLBbznGpaYinYE2" alt=""><figcaption></figcaption></figure>

### Configure

You can maintain configuration parameters for IFlows for each environment separately in ReleaseOwl. These will be updated accordingly during the deployment.

#### **To configure an artifact:**

1\. Go to the required artifact, click **Actions** and choose **Configure**.

2\. The following screen is displayed that will show various configuration parameters for the Integration Suite environments that are part of the landscape.

3\. No changes can be made to **Dev** environment.

4\. To make changes in any other environment, click the edit icon on the required name and make changes. Click **Save**.

<figure><img src="/files/xbOWESyzR8HS576Ab1xi" alt=""><figcaption></figcaption></figure>

### **Versions**

1\. To view the versions, go to the required artifact, click **Actions** and choose **Versions**.

<figure><img src="/files/kFny1LQ416g1sL10leOr" alt=""><figcaption></figcaption></figure>

2. &#x20;The following screen is displayed showing the user different versions of the artifact.

<figure><img src="/files/ncBNadGCoNltCSzMDxNg" alt=""><figcaption></figcaption></figure>

#### **Compare Environments**

The **Compare Environments** option is used to compare an iFlow between two different environments. It helps you identify differences between:

* **Source Environment**: Contains the source version of the iFlow
* **Destination Environment**: Contains the active version of the iFlow

#### Steps:

1. Click **Compare Environments**
2. Select the **Source Environment**
3. Select the **Destination Environment**
4. Click **Submit**

<figure><img src="/files/e3GvaYpb1cXLw210ErwH" alt=""><figcaption></figcaption></figure>

5. The system will display the differences between the iFlow versions across the selected environments.

<figure><img src="/files/uHSrr71crUGi7KcTbbBC" alt=""><figcaption></figcaption></figure>

#### Compare Versions

The **Compare Versions** option is used to compare two different versions of the same iFlow within an environment.

**Steps:**

1. Click **Compare Versions**
2. Select the two iFlow versions you want to compare
3. Submit the selection

The system will show a side-by-side comparison highlighting the differences between the selected versions.<br>

<figure><img src="/files/pMz0VWsJ8sqAc3idX64p" alt=""><figcaption></figcaption></figure>

### Assign User Story

The **Assign User Story** option is used to link a specific version of an artifact (such as a configuration or integration flow) to a designated User Story.

This helps maintain traceability between development requirements and artifact versions.

**Steps:**

1. Click **Assign User Story**

<figure><img src="/files/3VLB290KYNHIrXTvUYus" alt=""><figcaption></figcaption></figure>

2. The system will prompt a selection window
3. Select the required **User Story**
4. Confirm the selection

<figure><img src="/files/7kNi8NAyyCBta1u5WQo7" alt=""><figcaption></figcaption></figure>

The current version of the artifact is associated with the selected User Story, creating a traceable link between the implementation and the requirement.

### Download

You can download the required artifact. To download:

1. Go to the required artifact. Click **Actions** and choose **Download**.
2. A zip file of the artifact is downloaded into your computer.

<figure><img src="/files/k6raUJ3ZEgFj7FybZXNo" alt=""><figcaption></figcaption></figure>

### Comment

To add or update a comment for a specific version of an artifact:

1. Navigate to the required artifact.
2. Click the **Actions** button.
3. Select **Comment** from the dropdown.

<figure><img src="/files/S1HUsvQuaaSl8XBufSyJ" alt=""><figcaption></figcaption></figure>

4. Click the **Edit** next to the comment.

<figure><img src="/files/Zi3VdIfVqPW3jWHm0uZ7" alt=""><figcaption></figcaption></figure>

5. Enter  the comment text as needed.
6. Click **Save** to store the comment for the CPI artifact.

<figure><img src="/files/PsZixlVQCFO594PbyTCg" alt=""><figcaption></figcaption></figure>

7. The **Comment** button is located adjacent to the **Version** field.

<figure><img src="/files/0eL15LRukxb8OybauTwC" alt=""><figcaption></figcaption></figure>

8. When clicked, it displays the **Created by**, **Created on**, **Modified by**, and **Modified on** information.

<figure><img src="/files/yHDJjrVkBujOklDzYh25" alt=""><figcaption></figcaption></figure>

### Deployment History

The **Deployment History** option displays the complete history of a package’s deployment activities. It provides detailed tracking of each artifact deployed within the package.

<div><figure><img src="/files/Li0qtlHPOeUlUcvwntpM" alt=""><figcaption></figcaption></figure> <figure><img src="/files/f7ZmG1iWtfSRPkjxHwnU" alt=""><figcaption></figcaption></figure></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://releaseowl.gitbook.io/releaseowl-docs/releaseowl-user-guide/sap-integration-suite/cpi-management/synchronize-cpi-artifacts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.