Table of contents
Explore what's new in the OPUS Solution Environment, version 6.0.0 release. To learn more about the Solution Builder, version 2025.1.0 app that powers the solution, see What's new in the Solution Builder, version 2025.1.0 release.
Release information
This document describes the TraceLink capabilities included in the OPUS Solution Environment, version 6.0.0 release, which is available on Validation and Production on 08 Apr 2025.
The following solutions are impacted by this release and will be updated to the version listed:
- OPUS Solution Environment, version 6.0.0
Apps that support this solution version:
- Solution Builder, version 2025.1.0
The features below are in order of functional relevance (i.e. the typical order in which a user executes a function or task).
These release notes are subject to change based on the deployment of the release. In the event of changes, the release notes and any related documentation will be updated within one week of release deployment. Deployment completion can be confirmed in the TraceLink Release Notice email.
Revisions
| Date | Revision | Description |
|---|---|---|
| 08 Apr 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.
Simplified Creation of Lookup by Reference and Lookup by Value Fields
This release removes index map configuration properties when adding Lookup By Reference (LBR) and Lookup by Value (LBV) fields to pages, groups, collections, and group collections. By automatically populating the index map configuration properties, OSE improves the user experience for creating and editing LBR and LBV fields by automatically performing some configuration steps.
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- Owners
Add Standard Pick List Fields to All Page Types and Business Object Types
Solution Designers can add and configure Standard Pick List fields on business objects and on New, View/Edit, and Search pages. This allows users to select a value from a list of options that is maintained by TraceLink and dynamically populated. This differs from Pick List fields, where the list of options is maintained by the Solution Designer, or Multi Pick List fields, where the user can select more than one option.
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- All business segments (both Owners and Partners)
Create a Subtype by Copying an Existing Subtype
Solution Designers can create a new subtype by making a copy of an existing subtype. Previously subtypes could only be created based on business object types, which was time-consuming when Solution Designers needed several similar subtypes but had to apply the same configuration changes manually to each subtype. By copying an existing subtype, Solution Designers can concentrate on only the configurations that are unique to a specific subtype.
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- Owners
Configure Properties of Custom Fields in Subtypes Without Changing the Base Object
Solution Designers can modify the properties of custom fields, fields in groups, field collections, and fields in group collections within subtypes, allowing them to further configure subtypes to accurately reflect their company's business objects. Solution Designers cannot change base fields, base fields within groups, or base fields within any collection, ensuring that any changes to field properties in subtypes will not affect the base object.
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- Owners
Disable Save Button in Released Solutions
This release disables the button for any solution in the Test or Released state, preventing Solution Designers from attempting to edit any assets in a released solution. Previously, Solution Designers could make changes to these solutions and attempt to save them, and the system displayed an error message. By disabling the button, this update prevents Solution Designers from wasting time and effort by attempting to make updates.
Impact analysis
- Interface options:
- Web UI
- Business segment impacts:
- Owners
Resolved issues
OPUS Solution Environment 6.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-49964: Next RC Button Should Be Disabled for Solutions in Edit State | Web UI | The button is enabled for solutions in an edit state when they cannot become release candidates. This issue is resolved. |
| TL-50114: Not Able to Filter Business Object Types by Application Name | Web UI | The View/Edit pages for business object types do not allow users to filter by application name. This issue is resolved. |
| TL-60492: Released Company Solution Shows as Test in UI | Web UI | When releasing a solution to the company catalog, the state of the solution is updated to Released, but the OSE UI shows a state of Test. This issue is resolved. |
| TL-64567: Cannot Add All Items to Pick List Field | Web UI | When creating a Pick List field, the character limit on the field prevents all required items from being added. This issue is resolved. |
| TL-58049: Need to Show Flag Indicating Whether a Workflow is Valid | Web UI | Instead of displaying an error when a Solution Designer tries to save an invalid workflow, the View/Edit pages for workflows should include a field showing whether the workflow is valid. This issue is resolved. |
| TL-59751: Field Properties in Business Objects Should Not Be Editable | Web UI | Solution Designers should not be able to edit the name, type, scope, and provider properties for a field in a business object, or the location for a field in a group in a business object. This issue is resolved. |
Known issues
OPUS Solution Environment 6.0.0
There are no known issues in this release.
