Skip to main content
Register for FutureLink Barcelona 2026 Today→
TraceLink — Network for Greater Good
AI Mode Agents AI Solutions Network Resources About
LOG IN TraceLink Classic OPUS Platform
Tracelink University

Breadcrumb

  1. Home
  2. Resources
  3. TraceLink University

Add Integration Configuration Objects in Integration Catalog

  • Download PDF
  • Share
    • LinkedIn
    • Facebook
    • Mail
    • Twitter

Table of contents

Integration Configuration Objects (ICO), JSON based configuration entity, managed in Integration Catalog, that a Transform can read at runtime (via JavaScript) to get customer, partner, or environment‑specific settings instead of hardcoding them.

  • A company-scoped ICO can be used with both Company and Marketplace transforms.

  • ICOs can be used in JavaScript steps or transform steps that include child JavaScript steps that consume configuration values.

  • If a transform uses ICOs and the required configuration is not available, the transform returns an error unless fallback logic (e.g., hard-coded values) is implemented.

  • An ICO version in a Released state can be implemented in the transforms in either Edit or Released state.

Add and update Integration Configuration Objects

ClosedCreate, update and release a Integration Configuration Object
  1. Select the Main Menu icon.

  2. Select Integration Catalog.

  3. Select Integration Configuration Objects in the side menu.

  4. Select the Add button. The New Integration Configuration Object page displays.
  5. In the General section, fill in the following information:

    • Name field – Required. The unique name of the Integration Configuration Object.
    • Used With drop-down – Indicates whether the Integration Configuration Object is used with a Transform.

      Future releases will also support Link Actions.

    • Used by drop-down – The name of the Transform used by the ICO.

      The selected transform binds the ICO exclusively to that transform. All subsequent versions of the ICO must continue to use the same transform and cannot be associated with a different one.

    • Description field – Required. A brief description explaining what the Integration Configuration Object contains.
  6. Select the Save button.

    The screen is directed to the Integration Configuration Object Details page with the ICO in the Edit state and with the required sections populated.

  7. In the General section, the following fields can be edited when the Transform is in Edit status:

    • Name field – Required. The unique name of the Integration Configuration Object.
    • Description field – Required. A description explaining what the Integration Configuration Object contains.
    • Used With drop-down – Indicates whether the Integration Configuration Object is used with a Transform.

      Future releases will also support Link Actions.

    • Used by drop-down – The name of the Transform used by the ICO.

      The selected transform binds the ICO exclusively to that transform. All subsequent versions of the ICO must continue to use the same transform and cannot be associated with a different one.

    • Created By User drop-down – The name of the user who created the ICO. This field is auto-populated and cannot be edited.

    • Version Description drop-down – A brief description for the version.

    • Version field – The current version of the ICO. This field is auto populated and read-only.

  8. In the Configuration JSON section, upload the JSON-based Integration Configuration Object.

  9. Select the Move To button at the top of the screen to release the Integration Configuration Object to make it available in all other environments i.e. Prod, Val, and OLL.

    By default, the ICO is set to Edit Status unless it is manually changed to Released Status.

    The submit status indicator circle is filled in with green to indicate the ICO is in Released status.

  10. Select the Save button.

    The Integration Configuration Object is created with Version as 1.

ClosedCreate a new version for Integration Configuration Objects
  1. Select the Main Menu icon.

  2. Select Integration Catalog.

  3. Select Integration Configuration Objects in the side menu.

  4. On the Search Integration Configuration Objects screen, select the row of a ICO and select New version.
  5. On the New Version side panel, select Apply.

    An incremented version of Integration Configuration Object with the same ICO name is created.

Tips

  • An ICO in Released status cannot be updated. To upgrade an ICO, create a new version.
  • A new version can be created for ICOs in Edit and Released status.

Search and view all Integration Configuration Objects

ClosedView all Integration Configuration Objects
  1. Select the Main Menu icon.

  2. Select Integration Catalog.

  3. Select Integration Configuration Objects.
  4. Select the Filter button.

    In the Filters panel, fill in one or more of the following fields to filter the results:

    • Name field – The unique name of the Integration Configuration Object.
    • Status drop-down – The status of the ICO.
      • Select All – Displays ICOs in Released and Edit state.
      • Edit – Displays ICOs in Edit state.
      • Released – Displays ICOs in Released state.

    • Used With drop-down – Indicates whether the Integration Configuration Object is used with a Transform.
    • Used by drop-down – The name of the Transform used by the ICO.

  5. Select Apply.

    The results will be displayed in a table based on the filter results.

  6. Select the link on the ICO name from the results table.

    ClosedSee the information that displays for each Integration Configuration Object
    • The General section displays the following information:
      • Name field – Required. The unique name of the Integration Configuration Object.
      • Description field – Required. A description explaining what the Integration Configuration Object contains.
      • Used With drop-down – Indicates whether the Integration Configuration Object is used with a Transform.

        Future releases will also support Link Actions.

      • Used by drop-down – The name of the Transform used by the ICO.

        The selected transform binds the ICO exclusively to that transform. All subsequent versions of the ICO must continue to use the same transform and cannot be associated with a different one.

      • Created By User drop-down – The name of the user who created the ICO.

      • Version Description field – A brief description for the version.

      • Version field – The current version of the ICO. This field is auto populated and read-only.

      • The uploaded JSON based ICO in the Configuration JSON section.

Table of contents

Cookie Settings

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies or similar tracking technologies. Please see below for an overview of the categories of cookies and similar technologies used on this site. You can allow or deny some of all of them, except Strictly Necessary Cookies which are required to provide the site to you. However, blocking some types of cookies may impact your experience of the site and services we are able to offer.

Please see our Cookie Policy for more details, including a list of the cookies we use. You can change your consent options at any time by following the “Cookie Settings” link in the Cookie Policy.
'Strictly Necessary' cookies let you move around the Site and use essential features like secure areas, shopping baskets and online billing. Without these cookies you would not be able to navigate between pages or use certain vital features of our Site, so we do not require your consent for their use. These cookies don't gather any information about you that could be used for marketing or remembering where you've been on the internet. For example, we use these Strictly Necessary cookies to identify you as being logged in to the Site. You can set your browser to block or alert you about these cookies, but if you do so, some parts of the Site will not work.
'Performance' cookies collect information about how you use the Site, such as which pages you visit, the time spent on the Site and if you experience any errors. We use performance cookies to provide aggregated statistics on how the Site is used and help us improve the Site including by measuring any errors that occur.
'Functional' cookies are used to provide services or to remember settings to improve your visit. We use 'Functionality' cookies to remember your settings and choices and show you when you're logged in to the Site.
‘Targeting' cookies are linked to services provided by third parties, such as 'Like' buttons and 'Share' buttons. The third party provides these services in return for recognizing that you have visited the Site. We also use 'Targeting' cookies to gather information that could be used to display content that we think may interest you.
Register for FutureLink Barcelona 2026 Today→
TraceLink — Network for Greater Good
Log In OPUS Platform · TraceLink Classic
AI Mode
Featured Report The Agentic Supply Chain Operating Model →

Agentic Business Processes

External Manufacturing Logistics Transportation Commerce Compliance

Products

Digital Transaction Exchange Process Collaboration Global Track-and-Trace Regulatory Compliance Real-Time Intelligence

Resources

Resource Center TraceLink University Partners Community Customers Events

About TraceLink

Company Overview Newsroom Culture & Careers Open Jobs Legal & Trust Center Corporate Social Responsibility Network Directory Glossary

Hot Topics

Eliminate Stockouts Improve OTIF Reduce Costs Increase End-to-End Visibility Accelerate Order-to-Cash Optimize Inventory Levels Scale Cross-Partner Execution
Need assistance? Contact Technical Support→

Contact Us Today

Transform your supply chain operations with a human-agent workforce.

Contact Us →

Stay Up-to-Date

Subscribe to receive industry insights and evolving trends.

Thanks — you're subscribed.

© TraceLink Inc. 2009–2026 All Rights Reserved