Table of contents

• Introduction
• Test and Persist Overview
• Test Functionality
  • For Desktop Client
  • For Autonomous Component
• Persist Functionality
  • When to Use Persist:
• How Persist Works
  • Desktop Client:
  • Autonomous Component:
• Conclusion

Introduction

In IDE, a Connector acts as a bridge between your tenant and various host systems such as Safran, SAP, Primavera P6, ILAP Analytics, and Microsoft Project. Once a connector is configured, it's crucial to verify that it works correctly. That’s where the Test and Persist features come in.

This article explains what these features do and how to use them based on the connector's execution component Desktop Client or Autonomous Component.

Note: To access the connector grid and perform Test or Persist actions, your account must have the Setup Admin role.

Test and Persist Overview

After creating a connector, the first step is to validate whether it is functioning correctly. The Test feature checks the connection health and Persist ensures that relevant data like schedules and host fields are synchronized between IDE and the host system.

Test Functionality

The Test action verifies that the connector can successfully communicate with its target host system. It's especially useful for confirming the connector is correctly configured.

For Desktop Client

If the connector was created using the Desktop Client as its execution component:

1. Open the IDE Desktop Client.

2. Navigate to the Connectors tab.

3. Find the connector you just created.

4. Click the Test button.

• If the connector is healthy, you'll receive a successful response, indicating a successful connection to the host system (e.g., Safran).

• If the connector is misconfigured or the host is unreachable, you’ll see an error status, which helps you identify the issue quickly.

Safran connector test

Safran connector successfully connected

For Autonomous Component

If the connector was created with the Autonomous Component, test operations are performed automatically by IDE’s background health-check process.

However, you can also test the connector manually:

1. Go to the IDE Desktop Client.

2. Navigate to the Connectors tab.

3. Locate and filter for your connector.

4. Click the Test button.

Safran connector test

This lets you manually verify the connection without waiting for the next scheduled health check.

Persist Functionality

The Persist action synchronizes schedule data and host field definitions from the host system into IDE. This is essential for keeping your connector aligned with changes made in the host system.

When to Use Persist:

• A new schedule has been added to the host system (e.g., Safran or P6)

• Configurations of existing schedules or host field have changed.
  
  

How Persist Works

When Persist is triggered:

• IDE calls host-specific APIs (e.g., for Safran, P6, ILAP Analytics).

• It fetches updated schedules and host fields.

• This ensures the connector has the most current data for transfers.

Think of Persist as a sync operation that keeps IDE up to date with your host system.

Desktop Client:

1. Open the IDE Desktop Client.

2. Navigate to the Connectors tab.

3. Locate your connector and click the Persist button.

   Safran connector successfully persisted

Autonomous Component:

For connectors using the Autonomous Component, Persist can be performed in two ways:

Option 1 – Desktop Client

1. Open the IDE Desktop Client.

2. Find your connector.

3. Click the Persist button.
   
   

Option 2 – IDE Web Application

1. Log into the IDE web app.

2. Go to Setup > Connectors.

3. View details of the connector created with the Autonomous Component.

4. Click the "Persist within 3 mins" button.
   
   

After clicking Persist, IDE will begin syncing with the host system. When the process completes, a green circle indicator appears next to the button, along with an option to run Persist again if needed.

Safran connector before persisting 

Safran connector after persist is triggered 

Safran connector successfully persisted

Conclusion

Both Test and Persist are essential steps after setting up a connector in IDE. Test ensures the connector can reach its host system, while Persist pulls in the latest schedules and host fields. Performing these actions helps you confirm that the connector is ready for data transfers and reduces errors during execution.

Always test and persist your connectors after creation—and again if the host system changes—to ensure seamless integration.