What's new in the OPUS Solution Environment, solution version 10.0.0 release

Explore what's new in the OPUS Solution Environment, version 10.0.0 release. To learn more about the Solution Builder, version 2026.3.0 app that powers the solution, see What's new in the Solution Builder, version 2026.3.0 release.

Release information

This document describes the TraceLink capabilities included in the OPUS Solution Environment, version 10.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 Solution Environment, version 10.0.0

  Apps that support this solution version:

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

Revisions

Feature

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

Configure Decimal Values for Percent Field

Solution Designers can now configure the Is Decimal property for the Percent field when designing Business Object Types. This property controls whether the Percent field accepts decimal values, providing greater control over instance data validation.

The Is Decimal property is supported for Percent field in the following locations:

• Simple fields
• Collections of simple fields
• Fields within a group
• Fields within a collection of groups

Impact analysis

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

Improve Calendar Date Handling

OPUS now treats date-only fields as calendar dates instead of moment-in-time values.

Previously, OPUS stored date fields as UTC timestamps and applied time zone conversion when storing and displaying values. As a result, date-only fields such as expiration dates, manufacturing dates, and compliance dates could display as different calendar dates for users in different time zones.

The following enhancements provide consistent date handling across all regions:

• Date selections from the calendar are stored without applying time zone conversion.

• Incoming ISO date strings are stored as calendar dates. If an incoming transaction contains an epoch value, OPUS treats it as UTC and removes the time component before storing the date.

• Date-only fields display the same calendar date for all users, regardless of time zone.

• Date filtering uses the same calendar date logic for calendar selections and mnemonic values (e.g. TODAY), providing consistent filtering across time zones.
• Solution Designers can configure a custom date display format by using standard date format tokens. When a custom format is configured, Edge displays dates in that format instead of using locale-based formatting. When a custom format is configured, Edge displays dates in that format instead of using locale-based formatting. For example, the format yy/dd.MMM-EEEE, QQQQ displays as 26/31.Jul-Friday, 3rd quarter.

This enhancement provides consistent display and filtering of date-only fields for all users, regardless of time zone. It reduces date-related discrepancies and improves the accuracy of compliance and business processes.

Impact analysis

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

Improve Page Load Transitions with Skeleton Screens

This release improves the page loading experience by displaying page-specific skeleton screens while content loads. Skeleton screens provide a smoother and more responsive experience when navigating between pages or performing actions in the solution.

Previously, a loading spinner displayed on a blank screen until the requested page loaded. This behavior could make the solution appear unresponsive during navigation and operations.

With this enhancement, Solution Designers see page-specific skeleton screens while page loads in both view and edit modes.

With this enhancement:

• Panel pages including object operation panels, specialized operation panels, and filter panels display skeleton screens.
• When opening a page in edit mode, the corresponding skeleton screen displays while the page loads.
• Skeleton loading is available across all Network pages, including panel pages.

Impact analysis

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

Enable Page Actions on New and View/Edit Pages

This release enables Solution Designers to add dynamic behavior to New and View/Edit pages using Page Actions and Scripts. Solution Designers use Page Actions to define reusable behaviors that run when users interact with UI elements, such as object fields. Solution Designers create a Page Action once at the page level and associate it with one or more UI elements and events, such as click and value change events. Page Actions use Page Action Scripts, a formula language similar to Microsoft Excel, to:

• Validate data
• Retrieve and transform data
• Update the user interface
• Add rows to tables
• Display messages
• Perform asynchronous operations

Because Page Actions are reusable and centrally managed, Solution Designers can update a behavior in one place and have the changes applied wherever the action is used, simplifying maintenance, improving reuse, and reducing duplicated business logic across a page.

For example, in a barcode scanning workflow, a Page Action can verify the scanned item, detect duplicate scans, update tote, case, and each counters, add the scanned item to a table, and display success or error messages in response to a single scan.

With this enhancement, Solution Designers can:

• Define reusable Page Actions at the page level.
• Associate a single Page Action with multiple page elements.
• Trigger Page Actions through configurable events, such as click and value change events.
• Create dynamic page behavior by using Page Action Scripts instead of developing custom application code.

For more information, see Configure Page Actions on New and View/Edit pages.

Impact analysis

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

Improved Compact Collection Lists

This release improves collection lists to make hierarchical data easier to navigate and collection layouts easier to configure.

The enhancements include:

• Navigate to child collections from the detail view – Child collection cards now appear at the bottom of the right-hand detail view, allowing solution users to open immediate child collections without returning to the left navigation panel.

• Two-column field layout – Solution Designers can configure fields in a two-column layout in the right-hand detail panel and use drag-and-drop to rearrange fields. This layout reduces scrolling and makes better use of available screen space, especially for collection items with many fields.

• Configurable composite item keys – Solution Designers can configure one or more fields to create a composite item key, such as Type + Value, that displays for each collection item in the left navigation panel. Composite item keys make collection items easier to identify at a glance.

• Customizable collection labels – Solution Designers can rename labels such as Collection, Sub-collection, and Group to match business terminology, making collection lists more intuitive for users.

Impact analysis

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

Convert Standard Exports to Specialized Export Operations on Pages

This release enables Solution Designers to configure a specialized export experience for Search and View/Edit pages.

Previously, these pages supported only a standard export with a fixed set of fields. Solution Designers could not customize the fields available in the export panel. Solution Designers can now convert the standard export to a specialized export directly on the page. After the conversion, additional object fields can be added to the export panel while the Export button remains in the same location. Each page supports a single export option, preventing duplicate export actions.

With this enhancement, Solution Designers can:

• Configure additional object fields in the export panel to support business processes and reporting requirements.
• Use the existing Export button to access the configured specialized experience.
• Continue using the standard export experience on pages that have not been converted.

Impact analysis

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

Navigate Dynamically to Child New Pages from Parent View Pages

This release adds support to configure dynamic navigation from Search and View/Edit pages to the New page of a sub type of a configured base object. The navigation can also pass contextual information from the parent View/Edit page to the child page. For example, when viewing a Knowledge Base item, a user can select New, choose SOP, Policy, or Guideline, and open the corresponding page immediately. The new page is preconfigured using the context of the current Knowledge Base item.

Solution Designers can configure Dynamic Object Page Navigation on Search and View/Edit pages so that selecting New opens the appropriate child New page based on the current parent object.

Previously, users had to leave the current page, navigate to the appropriate creation page, and select the correct form.

This enhancement streamlines object creation, reduces navigation, and helps users stay focused on their current task.

For more information, see Add and configure dynamic UI operations on Search and View/Edit pages.

Impact analysis

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

Resolved issues

OPUS Solution Environment, solution version 10.0.0

There are no resolved issues in this release.

Known issues

OPUS Solution Environment, solution version 10.0.0

There are no known issues in this release.