Articles in this section

Integration Lifecycle terminology

Common terms

Below are common terms used throughout ILM documentation and in integrator.io.

Term

Definition

Clone

A clone is an identical copy of an integration that you can modify independently of the original integration.

Conflict

Conflicts are competing changes between your current integration and the remote integration.

Current

A current integration is an integration that you work on and into which you pull changes from a remote integration.

Merge

When you merge integrations, you accept changes and update resources from the remote integration to your current integration. Merge is a part of a pull.

Original

An original/source integration is an integration from which you create a copy or a clone.

pageGenerators (PG or Exports)

Exports are called pageGenerators (PG) in the JSON structure of your integration flow.

Pull

When you pull from a remote integration, you compare the fetched data and merge changes into your current integration.

pageProcessors (PP or Imports)

Imports and Lookups are called pageProcessors (PP) in the JSON structure of your integration flow.

Remote

A remote integration is an integration from which you’re pulling changes.

Resource

A resource is any import, export, flow, script, or another part of an integration.

Restore

If you restore your integration, you’re recovering a previous revision and rolling back to it.

Revert

A revert undoes changes and allows you to roll back to a previous revision. You can roll back to any previous pull, snapshot, or revert revision.

Revision

A revision can be any of the following types: snapshot, pull, or revert.

Sandbox/Non-production

A non-production environment is available for testing. If your Celigo license doesn’t include a non-production environment, you can test in your existing environment or contact Celigo to learn more about adding a non-production environment.

Legacy production and sandbox licenses

In legacy Production and Sandbox environments, changes in one environment affect both environments. The Production and Sandbox environments share the same underlying resources. Any resource you create, edit, or delete in one environment is immediately reflected in the other.

This includes connections, imports, exports, flows, scripts, and API tokens. Use caution when editing resources in either environment.

This behavior doesn't apply to accounts on the multi-environment license, where each environment maintains its own isolated resources.

Migrations from the legacy Production/Sandbox license to the new multi-environment license are underway. Your account has not migrated to the new multi-environment license if you can toggle between environments.

Toggle to Sandbox environment.png

Snapshots

A snapshot is a copy of an integration state that you create at any point to use as a backup when required.

Source

A source/original integration is an integration from which you create a copy or a clone.