Integrations Table Options

In the integrations table, environments group together (e.g., DEV, QA, PROD) and act as one instance. You can expand the group to manage the environments individually.
To manage the table view, use the standard table options or apply Collapse All / Expand All for the table rows. Save your preferred view using Preferences.

Top Level Options

• New IntegrationManager – You can either connect an existing IM instance ("manual IM") or create a new one ("provisioned IM").

• Export CSV – Allows you to download the list of integrations in the CSV format.

Group Level Options

• Permissions – Allows you to manage access to a Git repository where the integration code is stored. You can add here PlatformManager users and grant them user access to Git with the Developer role. 

  • To do this, you need the Integration - GIT Manager permission.

  • All actions are recorded in the Activity Log.

  • This functionality is available only for cloud provider IM instances.

⚠️ Assignable users must meet all of the following conditions:

• they are invited to the project

• they have active status

• they are not already included in the integration project

Only users matching these criteria appear in the list of assignable users.

• Edit – Allows you to add a new environment and/or modify existing instance resources (processor, memory, storage). After changing the resources, restart of all affected environments of the instance might be required. You can also update here the integration architecture information (ERP/CRM system to integrate with, integration direction, used technology etc.) and see who made the last change. For options description see How to Create IM Instance. 

Individual Instance Options

• Start and stop the provisioned IM instance (if you have the Integration Instance - edit permission).

• Restart the provisioned IM instance created with the cloud provider (if you have the Integration Instance - edit permission).

• Show detail – Opens a panel with summary information about the IM instance. It also provides links to server log and Git log. 

• Settings – Opens the IM instance Settings.

• Version History – Shows a table with used IM versions and dates of upgrade. (Versions are stored since May 2024; no historical data is provided.) It is available only to users with the account permission Integration Instance - Edit or Integration Instance - Admin.

• Update – Redirects you to the Settings > Update section where you can select IM version to upgrade to.

• Transport to – Allows you to transport code between environments, e.g. from DEV to QA or from QA to PROD. 

• Delete the selected IM instance (if you have the Integration Instance - edit permission). When an IM instance is deleted, the user who initiated the deletion is notified in the Notifications center (and by an email if it was the last IM instance in the given Git repository).

• Force delete an IM instance which is in an inconsistent state (originated during creation or decommissioning and so there is no point in keeping the instance). This option is available only to users with the global Permissions power user permission.

For options related to a specific IM instance, see Integration Overview and Integrations Menu.

To work with the table, in addition to all the standard table options you can also use Collapse All / Expand All for the table rows. Once you apply one of these options, you can save the view using Preferences.  

Automated Stop and Start

PlatformManager can automatically stop connected IntegrationManager instances when the corresponding Core instance (cluster) goes offline, preventing the integrations from sending data to unavailable partitions.

When a cluster is manually hibernated or scheduled to shut down, the system checks the Manage Connected Integrations setting.

• This option is selected by default.

• When enabled, connected IntegrationManager instances stop automatically. For scheduled cluster shutdowns, the stop sequence triggers 10 minutes before the scheduled downtime.

• Monitoring alerts are temporarily disabled before the stop sequence initiates to prevent email spam regarding the unavailability.

• When the cluster wakes up, the connected IntegrationManager instances automatically restart and monitoring is restored to its original state.

• If you unselect the option, the connected IntegrationManager instances remain running when the cluster hibernates.