What's new in the user interface

Type = What's New,; Topic = Reports and Dashboards,;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,

Explore what's new in the OPUS Agent Manager, solution version 3.0.0 release. To learn more about the OPUS Agent Manager, version 2026.3.0 app that powers the solution, seeWhat's new in the system.

Release information

This document describes the TraceLink capabilities included in the OPUS Agent Manager, solution version 3.0.0 release, which is available on Validation and Production on 16 Jul 2026.

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

• OPUS Agent Manager, solution version 3.0.0

  Apps that support this solution version:

  • OPUS Agent Manager, version 2026.3.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
16 Jul 2026	01	Initial version.

Features

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

OPUS Agent Manager, solution version 3.0.0

Additional Outcome Definition Fields

Agent Developers can now add more context to an agent’s Outcome Definition using three optional fields: Display Name, Create Upon, and Complete Upon. These fields describe the outcome, specify when it should be created, and define when it is considered complete.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments (both Owners and Partners)

Promote and Retire Agent Experience Definitions

Agent Developers can promote Patterns, Interfaces, and Interface Elements (PIE) when they are ready for use and deprecate them when they should no longer be used for new agentic experiences.

Promoting an experience definition makes it available for live use, while deprecating an experience definition clearly signals that it is no longer recommended. This helps teams avoid using unfinished, outdated, or retired experience definitions when designing how users interact with agents.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments (both Owners and Partners)

OPUS Agent Manager, solution version 2.0.0

Create Agent Experience Definitions

Agent Developers can create experience definitions using Patterns, Interfaces, and Interface Elements, also referred to as PIE, to guide how agent responses are rendered in the UI. These objects help determine how agent responses should be structured, and which UI elements should appear for users.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments (both Owners and Partners)

Create a Company Agent in Development

OPUS Agent Manager now allows Agent Developers to create a Company Agent In Development from the Agent Profile section. This gives developers a draft workspace where they can define a company-specific agent profile before making it available for live agent creation.

Agent Developers can define the agent’s purpose, expected outcomes, tasks, rules, metrics, and guardrails in a controlled development state before promoting the profile for broader use. This provides organizations a test environment to ensure that an agent is ready and can be assigned to a live project.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments (both Owners and Partners)

OPUS Agent Manager, solution version 1.0.0

Standardized User Interaction with Agents

OPUS Agent Manager now supports reusable experience components that define how users interact with agents. These components include Patterns, Interfaces, and Interface Elements (PIE), which help define the structure, layout, and interaction flow that users see when working with agents.

Standardizing user interaction makes agent experiences consistent, reusable, and easier to manage across different business contexts. Instead of designing each agent interaction separately, teams can create reusable PIE objects that guide how agents present information, collect input, and support user actions. This helps reduce repeated design work and creates a more consistent experience for users who work with agents.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments (both Owners and Partners)

AI Assistant Support for Solutions

This feature introduces Assistants as solution assets, allowing Solution Developers to include an AI assistant as part of a solution. Solution Developers can define and manage the assistant’s objectives that guide what the assistant can help users accomplish within the solution. By defining assistant objectives within the solution, organizations can make AI-guided help more relevant, controlled, and reusable across environments.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments (both Owners and Partners)

Create and Manage Agent Profiles and Instances

This feature introduces the end-to-end lifecycle for creating, releasing, and managing agents on the OPUS platform.

Agent Developers can create Company Agent Profiles, either from scratch or by using an existing Standard Agent Profile as a starting point. Agent Developers first create an Agent in Development and define the agent’s intent, objectives, outcomes, tasks, decisions, rules, metrics, and guardrails. Agent Developers can then test the profile and promote it, making the agent profile available for use in the Company Agent Profile.

Agent Administrators can browse available Standard and Company Agent Profiles and create Agent Instances from supported profile types. During agent instance creation, Agent Administrators can assign the agent to the required users, configure access, and link the agent to the appropriate process network so that it can operate in the correct business context.

Human Managers can view the agents assigned to them and manage those agents through their operational lifecycle. This includes testing agent behavior, enabling or disabling agents, and retiring agents when they are no longer needed.

Impact analysis

• Interface options:
  • Web UI
• Business segment impacts:
  • All business segments (both Owners and Partners)

Resolved issues

OPUS Agent Manager 3.0.0

There are no resolved issues in this release.

Known issues

OPUS Agent Manager 3.0.0

There are no known issues in this release.

Tag end