Type = How-tos, API Reference, Courses, Technical Guides, Technical Tools, Design Guides, Explainer Videos, FAQs, Fundamentals, Troubleshooting, Use Cases, What's New,; Topic = OPUS Solution Environment, Multienterprise Information Network Tower (MINT), Administration, Transforms, Link Actions, Reports and Dashboards, Track and Trace, Compliance, Process Orchestration for Empowered Teams (POET), Technical Documentation, OPUS,;Persona = Solution Designer, TraceLink Administrator, User, Orchestration Architect, Solution Partner, Technology Partner,; Orchestration = Manufacturing, Logistics, Commerce, Transportation, Clinical Supply,; Function = Supply Chain, IT, Operations, Regulatory Affairs, Quality, Commercial, Pharmacy, Project Management, Finance, Procurement, Spare 2, Spare 3, Spare 4, Spare 5, Spare 6, Spare 7, Spare 8, Spare 9, Spare 10,

What's new in the user interface

Explore what's new in the OPUS Actions, solution version 1.3.1 release. To learn more about the OPUS Action Builder, version 2026.2.0 app that powers the solution, see What's new in the system.

Release information

This document describes the TraceLink capabilities included in the OPUS Actions, solution version 1.3.1 release, which is available on Validation and Production on 13 Oct 2026.

The following solutions are impacted by this release and will be updated to the version listed:

  • OPUS Actions, solution version 1.3.1

    Apps that support this solution version:

    • OPUS Action Builder, version 2026.2.0

The features below are in order of functional relevance (i.e. the typical order in which a user executes a function or task).

Download the PDF

Revisions

Date Revision Description
13 Oct 2026 01 Initial version.

Features

The following new or updated functionality is included in this release.

Introduction of OPUS Actions: Extend OPUS App Behavior with Custom Automation

This release introduces OPUS Actions, which run custom JavaScript in response to supported OPUS events. Users can extend OPUS app behavior and automate processes across OPUS apps. Actions can add or edit data and invoke Agents. Users can reuse action logic through OPUS Action Definitions in the Catalog.

Create and Configure OPUS Actions with Reusable Action Definitions and GraphQL APIs

Action Builders can create and configure OPUS Actions that run custom JavaScript in response to supported OPUS events. They can also create Actions from reusable OPUS Action Definitions in the Catalog. Additionally, they can use GraphQL APIs in Action JavaScript to perform business operations across OPUS apps.

As part of this feature:

  • Create and configure Actions: Create and configure Actions: Action Builders can select an event and configure the binding level, bindings, environment variables, Integration Principal, and JavaScript for an Action. Actions can be bound at the Solution, Process Network, or Agent level. Only Active Actions execute when their configured events occur.

  • Create Actions from Action Definitions: Action Builders can create a local Action from a reusable, versioned OPUS Action Definition in the Catalog. They provide environment-specific configuration, including local bindings, environment-variable values, and an Integration Principal. The resulting Action is an independent local copy, and changes to the Action or source definition do not automatically affect the other.

  • Use GraphQL APIs in Actions: Action Builders can use GraphQL APIs in Action JavaScript to create or edit data and perform other supported business operations across OPUS apps. They can execute supported GraphQL queries and mutations and configure header overrides when additional context is required.

Impact analysis

  • Interface options:
    • Web UI
  • Business segment impacts:

    • All business segments (both Owners and Partners)

Resolved issues

OPUS Actions, solution version 1.3.1

There are no resolved issues in this release.

Known issues

OPUS Actions, solution version 1.3.1

There are no known issues in this release.

Tag end