What's new in the user interface

Type = What's New,; Topic = OPUS Solution Environment,;Persona = Solution Designer,; Orchestration = Manufacturing, Logistics, Commerce, Transportation, Clinical Supply,; Function = Supply Chain, IT, Operations, Regulatory Affairs, Quality, Commercial, Pharmacy, Project Management, Finance, Procurement, Spare 2,

Explore what's new in the OPUS Solution Environment, solution version 11.0.0 release. To learn more about the Solution Builder, version 2026.4.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 Solution Environment, solution version 11.0.0 release, which is available on Validation and Production on 15 Oct 2026.

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

  • OPUS Solution Environment, solution version 11.0.0

    Apps that support this solution version:

    • Solution Builder, version 2026.4.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

This Help Center is subject to change based on the deployment of the release. In the event of changes, the Help Center will be updated within one week of release deployment. Deployment completion can be confirmed in the TraceLink Release Notice email.

Revisions

Date Revision Description
15 Oct 2026 01

Initial version.

Feature

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

Upgrade Company SubTypes with New Base Object Types Fields

Solution Designers can upgrade existing custom business object types (company subtypes) to include updates from the latest version of their base object type. TraceLink owns and maintains the base object types and configures them as needed.

To upgrade a company subtype, use the Upgrade functionality. TraceLink compares the company subtype with the latest version of its base object type. TraceLink then adds any missing base fields, field groups, and collections introduced after the company subtype was created.

The upgrade does not change existing custom configurations. If a field or field group with the same name already exists in the company subtype, TraceLink does not overwrite it. After the upgrade is complete, a notification confirms that the company subtype was successfully upgraded.

Upgrading company subtypes keeps them aligned with changes to their base object types. It reduces the need to add new base fields manually and helps prevent configuration errors.

Impact analysis

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

Support IS IN LIST and IS NOT IN LIST Conditions

In this release, Solution Designers can configure field rules using the IS IN LIST and IS NOT IN LIST conditions. These conditions evaluate multiple values in a single condition instead of requiring multiple conditions.

  • IS IN LIST — Applies when the triggering value matches any value in the list.
  • IS NOT IN LIST— Applies when the triggering value does not match any value in the list.

For example, configure a field rule to make a field required based on values selected in a MultiPickList field:

  • Triggering field — A MultiPickList field with Red, Blue, Green, and Yellow as available values.
  • Affected field — Paint Code.
  • Condition — Configure IS IN LIST with Red and Blue as the values.

If Red or Blue is selected in the triggering field, Paint Code is required. If Green or Yellow is selected, Paint Code remains optional.

The IS IN LIST and IS NOT IN LIST conditions are currently supported for Picklist, Multipicklist, Standard Picklist and Standard Multipicklist as triggeringAttributeName.

Impact analysis

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

Move Company Solutions from Test to Edit State

In this release, Solution Designers can transition a Company solution from Test back to Edit. This transition allows Solution Designers to incorporate feedback identified during testing and make changes to the existing solution version.

Solution Designers can transition Company solutions between Edit and Test multiple times during development and testing without creating a new version.

Supported transitions depend on the solution type. Standard and Marketplace solutions cannot transition from Test back to Edit.

Impact analysis

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

View the Parent Solution for Company Solutions

Solution Designers can identify the source of a Company solution in Solution Builder. When a Company solution is created from a Standard or Marketplace solution using Save As, the Solution Details screen displays the source in the read-only Parent Solution field.

The Parent Solution field displays the source solution name and version in the following format:

[Solution Name]:[Version]

For example, MINT Purchase Order:1.0.0

A Solution Designer creates a Company solution by using Save As on the Standard MINT Purchase Order solution. On the Company solution’s Solution Details screen, the read-only Parent Solution field displays MINT Purchase Order:1.0.0.

TraceLink automatically records the parent solution when the Company solution is created using Save As. No manual entry is required. The parent solution information remains associated with the Company solution when Solution Designers add subsequent versions or download the solution. The Parent Solution field is read-only and cannot be edited.

This enhancement improves solution traceability by automatically preserving the Standard or Marketplace solution and version used to create a Company solution. Solution Designers can quickly identify the source for auditing and other traceability purposes.

Impact analysis

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

Configure Navigation Menus to Open Scheduled Reports

Solution Designers can add Scheduled Reports as the target page type when configuring navigation menus. In the Submenu or Menu Item section, from the Target Page Type drop-down, select the Scheduled Reports option. When a user selects the configured menu item, the corresponding scheduled reports page opens.

This enhancement enables Solution Designers to provide direct access to scheduled reports from a solution menu, reducing the time users spend navigating.

Impact analysis

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

Configure and Edit Solution Help Link in the UI

Solution Designers can configure and edit a solution's custom Help link from the Solution Details screen.

On the Solution Details screen, in edit mode, specify a value in the Solution Help Center Link field using either a full URL (e.g. https://opus.tracelink.com/documentation/prod/en-US/ose/Content/top_nav/manage_solutions.htm) or a relative path (e.g. documentation/prod/en-US/ose/Content/top_nav/manage_solutions.htm). The link identifies the documentation or Help Center resource associated with the solution.

A valid value must:

  • Match the supported URL or path format.
  • Contain at least one directory separator (/) followed by valid characters.
  • Use only supported characters, including periods (.), commas (,), and hyphens (-).
  • Not contain leading or trailing slashes, consecutive slashes, or spaces.

If the value does not meet the validation requirements, the system displays a validation error and prevents the changes from being saved.

This enhancement provides direct access to relevant Help Center documentation, reducing the time users spend searching for solution-specific help.

Impact analysis

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

Resolved issues

OPUS Solution Environment, solution version 11.0.0

The following issue is resolved in this release. The prefix is for internal TraceLink tracking purpose and does not mean anything to customers.

ID Interface Issue Description
TL-85529: Policy Bundles not Generated Automatically after Access Policy Changes Web UI

Creating, editing, or deleting access policies in an active solution did not automatically trigger policy bundle generation.

Solution Builder now automatically generates the required policy bundle when access policies are created, edited, or deleted. Solution Builder also groups multiple policy changes made within a short period to reduce unnecessary policy bundle generation requests.

This issue is resolved.

Known issues

OPUS Solution Environment, solution version 11.0.0

There are no known issues in this release.

Tag end