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,

Explore what's new in the OPUS Solution Environment, solution version 7.0.0 release. To learn more about the Solution Builder, version 2025.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 Solution Environment, solution version 7.0.0 release, which is available on Validation and Production on 26 Aug 2025.

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

  • OPUS Solution Environment, solution version 7.0.0

    Apps that support this solution version:

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

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
26 Aug 2025 01 Initial version.

Features

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

Instructions for performing the tasks described in the following sections will be available in a future release of the OPUS Solution Environment documentation.

Support for Media Attachment Rich Field Type

Solution Designers can add the Media component to network pages to enable users to attach image or video content by uploading from their device or capturing it directly through an embedded camera.

Solution Designers can define the following specifications:

  • Supported media types
  • Maximum file size
  • Whether to compress the media before saving
  • Whether to display a thumbnail of the attached media

On the New and View/Edit pages, solution users can use the Attach Media drop-down to capture or upload media. The drop-down includes the following options:

  • Open Camera – Capture a photo or video using the device’s camera.
    When selected, a modal opens with a live camera view. Solution users can switch between Photo and Video modes. After the media is selected, the modal enters preview mode. Solution users can either save the captured media or they can discard it and return to capturing.
  • Browse – Select a file from the device to upload.

Impact analysis

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

Support for Auto Number Rich Field Type

Solution Designers can add the Auto Number field to business objects and network pages to enable automatic, sequential numbering of records. This feature is useful for scenarios such as ticketing or order processing where numbers must be assigned without user input. It enforces consistent record tracking across workflows.

The Auto Number field:

  • Generates a system-assigned value based on a predefined format.
  • Automatically increments for each new record, ensuring uniqueness.
  • Cannot be edited.

Solution Designers can configure the following Auto Number field properties:

  • Object Prefix - Customizable string that precedes the generated Auto Number (e.g. use INC to denote a category of records).
  • Seperator - Single character used to divide parts of the Auto Number format (e.g. hyphen -)
  • Minimum Digits With Padding - Minimum number of digits for the generated number. If the number has fewer digits, leading zeros are added (e.g if set to 4, the number 1 displays as 0001).

In this example, INC-0001, INC inidicates the object prefix (e.g. incident category) and the number is automatically generated, starting at 0001 and incrementing by one for each new record.

Impact analysis

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

Copy Standard or Marketplace Solution into Company Solution

Solution Designers can copy existing standard or marketplace solutions into a company solution. This enables organizations to tailor solutions to their specific requirements while reusing existing assets. They can choose to copy assets at the object level or menu level, which in turn copies the following related assets:

  • Menus
  • Page types
  • Roles
  • Subtypes
  • Subworkflows

Impact analysis

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

Configure Solutions to Display TTS or LSC Pages

Solution Designers can configure menu and sub-menu items to display TTS or LSC classic pages within an iFrame. When a solution user selects a menu item for an LSC page, a session is initiated, and the solution user is redirected to the login screen. The system automatically authenticates the solution user using existing credentials, enabling a seamless experience across OPUS and classic pages. This feature supports Single Sign-On (SSO) token sharing, allowing solution users to stay authenticated without re-entering login credentials.

Impact analysis

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

Simplified Authorization Setup for Company and Marketplace Solutions

This release simplifies authorization setup for company and marketplace solutions. When Solution Designers create a company or marketplace solution from scratch, the system automatically applies the same authorizations as the active standard solution for the associated application (e.g. When a new POET company solution is created, all authorizations from the corresponding standard solution are automatically copied into the new company solution). The newly created solution includes all authorizations configured in the standard solution.

This enhancement reduces manual setup, prevents misconfiguration, and enables Solution Designers to implement consistent authorization policies with minimal effort. In addition, Solution Designers can reconcile all authorizations from a standard solution into a company or marketplace solution. Solution Designers can always change these if needed.

 

Impact analysis

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

 

Resolved issues

OPUS Solution Environment, solution version 7.0.0

The following issues are resolved in this release. The prefixes are for internal TraceLink tracking purposes and do not mean anything to customers.

ID Interface Issue Description
TL-48807: Unable to Sort Authorizations on Search Page Web UI

The Authorizations on Search page does not support sorting by Enforcement Point Name or Policy Type.

This issue is resolved.
TL-48810: No Results Display After Editing an Authorization Web UI

The Authorization Details screen does not display any results after editing an authorization.

This issue is resolved.
TL-49965: Missing Confirmation Message After Creating a Release Candidate Web UI

The system does not display a confirmation message after a new release candidate is created.

This issue is resolved.
TL-50347: Incorrect Field Type Properties Display After Adding a New Field Web UI

After adding a new field on the Business Object Type Details screen, the system incorrectly displays field type properties that are unrelated to the new field.

This issue is resolved.
TL-50350: Promote Button Enabled During Edit State Web UI

The Promote button appears enabled even when the solution is in the edit state.

This issue is resolved.
TL-55203: Unable to Add Fields to Groups Containing Nested Levels Web UI

When editing the Business Object Type Details screen, Solution Designers are unable to add fields to groups that contain multiple nested levels.

This issue is resolved.

TL-56965: System Fields Listed as Available

Web UI

System fields incorrectly appear in the Available Object Fields list for drag-and-drop in the Edit Object Operation panel.

This issue is resolved.
TL-58047: No indication whether Workflow is Configured Correctly Web UI

The Workflow Details screen does not include the Is Valid switch, which indicates whether the workflow is configured correctly.

This issue is resolved.
TL-60184: The Report or Dashboard Version Shows when Use Latest is Selected Web UI

When configuring a menu item to display a report or dashboard, selecting the Use Latest switch shows the report version or dashboard version even though it should be hidden.

This issue is resolved.
TL-62585: Non relevant Properties Display for Rich Field Type Web UI

On the Business Object Type Details screen, when rich field type is selected, the Add Field, Edit Field, and View Field panels display the properties that do not apply to the selected rich field type.

This issue is resolved.
TL-65033: Reportable Field is Hidden when Searchable Switch is Set to True Web UI

On the Business Object Type editor, setting the Searchable switch to True, hides the Reportable field on the Add, Edit, and View panels.

This issue is resolved.
TL-66032: Invalid Authorization Saved Web UI

The user can save an authorization even if the solution and enforcement point belong to different apps.

This issue is resolved.
TL-66248: Unable to Remove Existing Collections Web UI

Removing all instances from a collection and saving the View/Edit page does not clear previously saved collection data.

This issue is resolved.
TL-66501: Current Solution State Not Visible in View Details Panel Web UI

Solution users can not view the current state of standard, marketplace, or company solutions in the Catalog section after opening the View Details push panel.

This issue is resolved.
TL-66970: Cannot Perform the Pack or Unpack Action when the Solution has no Objects Web UI

Solution users can not perform pack or upack actions if the solution does not have any objects.

This issue is resolved.
TL-70706: Invalid Object Types appear in Lookup Field Selector Web UI

When adding a Lookup field, users can select the invalid object types from the system apps.

This issue is resolved.
TL-72096: Field Type Field is Not Marked as Required Web UI

The Field Type field is not marked as required in the Add Field and Edit Field panels of the Business Object Type editor.

This issue is resolved.

Known issues

OPUS Solution Environment, solution version 7.0.0

There are no known issues in this release.

Tag end