What's new in the Opus Solution Environment, version 2.0 release

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

Release information

This document describes the TraceLink capabilities included in the Opus Solution Environment, version 2.0 release, which is available on Validation and Production on 19 Sep 2024.

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

• Opus Solution Environment, version 2.0

  Apps that support this solution version:

  • Solution Builder, version 2024.3

The features below are in order of functional relevance (i.e. the typical order in which a user executes a function or task).

Revisions

Features

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

Create and Configure Business Object Types

Solution Designers can create, search for, view, and configure business object types, which define the structure of a business object. Business objects are digital representations of the real-world entities that are part of a company's business processes. For example, the business objects for a procurement process include, but are not limited to, purchase orders, purchase order acknowledgments, and invoices. The TraceLink Network leverages business objects and their workflows to facilitate business processes. Business object types define the contents of a business object. They encompass the actions that users can perform and the workflow states and transitions that make up the business object's lifecycle. By leveraging robust business object types, companies ensure that every instance of a business object in their solution include the same types of data and follow the same lifecycle, ensuring consistency while reducing the need for repetitive work and opportunities for human error. In this release, Solution Designers can configure existing business object types by adding fields and collections.

Impact analysis

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

Configure Workflows

Solution Designers can search for, view, and configure workflows in a Company Solution. A workflow defines a series of states, or steps that an object goes through over the course of a business process, and the transitions between these states. Workflows enhance business process management by ensuring efficiency and consistency, guaranteeing that objects of the same type move through the same base states and transitions without users needing to configure separate workflows for each object. At the same time, configuring workflows also provides flexibility, allowing the workflows in a Company Solution to continue to evolve in conjunction with the company's processes and business needs. TraceLink provides standard workflows that are predefined sequences of states and transitions for out-of-the-box business objects, and serve as the starting point for Solution Developers to configure their company's workflows.

TraceLink offers two types of workflows:

• Business object workflows are configured by Solution Designers to ensure the business process associated with an object type meets their company's specific needs. As Solution Designers configure business objects and their workflows, they create a digital representation of a lifecycle that closely mirrors their real-world business practices. Users manually move business objects through their steps in a businesss object workflow in their solution.
• Transaction workflows are automated workflows tied to transactions, and handle transactional data across multiple contexts (e.g. managing CSV imports for Master Data). Transaction objects move through transaction workflow steps automatically, without user intervention, and can be paused to temporarily stop automatic processing.

Solution Designers configure workflows to more closely match their company's business processes by configuring substates, transitions, and post-transitions actions. A substate is a more granular state that exists within a base state to provide greater control and tracking of a business object's progress through a workflow. When a substate is added, new transitions must also be added to reflect how a business object moves to or from the substate. Transition conditions define the criteria that must be met for a transition to be considered valid, and therefore for the workflow to proceed to the next step (e.g. a field cannot be left blank). Post-transition actions contain additional logic to be executed when a transition is successful, allowing the workflow to automatically perform post-processing activity. By defining transition conditions and post-transition actions, Solution Designers ensure their workflows properly incorporate substates to reflect their company's business processes and automatically perform any necessary tasks that are not included in the workflow.

This release provides the following functionality for workflows:

• View a list of available workflows: Solution Designers can search for and view the active workflows for all available business object types, including the solution name, solution version, and business object type associated with each workflow.
• View an instance of a workflow: Solution Designers can view the workflow for a business object. Details shown include the workflow's name, business object type, solution, default start state, states, substates, and transitions.
• Add substates and transitions to a workflow: Solution Designers can add substates and transitions to a workflow.
• Configure transition conditions and post-transition actions in a workflow: Solution Designers can configure transitions in a workflow by adding transition conditions and post-transition actions.

Impact analysis

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

Resolved issues

Opus Solution Environment 2.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.

Known issues

Opus Solution Environment 2.0.0

There are no known issues in this release.