Type = How-tos, ; 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,

Manage solutions

To manage a solution in OSE, Solution Designers create, configure, and release the solution. By completing these steps, they can effectively manage solutions within the OSE, ensuring that they meet specific business needs and processes.

TraceLink offers three types of solutions:

Standard Solutions - These solutions are preinstalled by TraceLink and are available to all companies. They provide baseline functionality that addresses common requirements across multiple companies. Users cannot configure these solutions, which ensures consistent and reliable deployment.
Marketplace Solutions - These solutions offer a broader range of functionality designed to meet specific business needs. Solution Partners and TraceLink internal teams create Marketplace Solutions to address complex challenges within a company and across trade partners. Users cannot configure Marketplace Solutions.
Company Solutions - These solutions are highly configured for a specific company. Solution Designers configure Company Solutions to meet their company's specific needs and processes. Solution Designers can create and configure a new Company Solution either by saving a copy of a Standard Solution or a Marketplace Solution or by creating a new Company Solution from scratch. Company Solutions support extensive configuration of pages, menus, roles, business objects, and workflows providing a flexible and adaptive solution that can evolve with the company’s changing needs.

A solution moves through three states: Edit, Test, and Released. Assets (such as pages) can be added, updated, or removed only in the Edit state.

State	Editable	Visibility
Edit	Solution assets can be created, updated, and deleted.	The solution appears in the Available menu under Company Solutions but not visible to solution users.
Test	Solution assets cannot be edited.	The solution appears in the Available and Catalog menus under Company Solutions but not visible to solution users.
Released	Solution assets cannot be edited.	The solution appears in the Catalog menu under Company Solutions and is visible to solution users.

Create a Company Solution

Create a Company Solution by saving a marketplace solution as company solution

Select the Main Menu icon.
Select Opus Solution Environment.
Select Catalog in the side menu.
Select Marketplace Solutions in the side menu.
The Marketplace Solutions screen appears.
Select the Filter button.
In the Filters push panel, fill in the following fields:
- Application Name drop-down - The desired application name.
- Solution Name field - The name of the available solution.
Select Apply.
From the list of available solutions, select the hyperlink in the Solution Name column that corresponds to the desired solution.
The Marketplace Catalog Solution Details screen appears.
Select Save As.
In the Save As push panel, fill in the following fields:
- Solution Name field - Required. The desired solution name that is being created. This is a unique identifier for the solution.
- Solution Description field - A description of the solution and its purpose.
Select Apply.
A success message appears after the solution is created.

Tips

To view the created solution, in the side menu, select Available, then Company Solutions and search for the created solution.
The solution is created but not yet active. To activate the solution, create a network in OPUS Administration.

Activate a solution

After creating a company solution, activate it. Activation makes the solution live and usable for company users and networks. When a solution is activated, the configured objects, pages, workflows, roles, and menus are applied to the underlying app or network. This enables solution users to access the full solution experience.

To activate a solution, create a network for the solution in OPUS Administration and then make the network available to users.

Create a network for the solution

Select the Main Menu icon.
Select Administration.
Select Network and Apps in the side menu.
Select the New button.
The New Network screen appears.
In the Network Information section, fill in the following fields:
- Application drop-down - Select the application for which you want to configure the marketplace solution. For e.g. Process Orchestration for Empowered Teams.
- Network Name field - The name of the network being created.
- Network Description field - The description of the network being created.
In the Solution section, fill in the following fields:
- Standard Solution switch - This value must be set to No as the solution for which the network is being created is a Marketplace Solution.
- Company Solution field - Select the solution that was saved as a company solution in the previous procedure.
Select the Save button.
A success message appears stating that the network is created.

Tips

After the network is created or added, the solution automatically becomes activated.

Make the created network available to users

After creating a network for the solution, make the network available to users by defining roles for accessing the network.

Select the Main Menu icon.
Select Administration.
Select Users in the side menu.
Select Network Members in the side menu.
The Search Network Members screen appears.
Select the Filter button.
Apply the desired search criteria to filter the list of network members.
Select the user email of the user who created the network.
Select the Edit button.
In the Roles section, select the required role from the Roles drop-down menu to access the created network.
Select the Save button.
A success message appears stating that the network member details are updated.

Configure a Company Solution

Release a Company Solution

Test a Company Solution

After configuring a solution, move it from the Edit state to the Test state.

Select the Main Menu icon.
Select Opus Solution Environment.
Select Available in the side menu.
Select Company Solutions.
In the Solution Name column, select the hyperlink for the desired solution to view its details of in View mode.
Select the Edit button.
Select the Move To button to change the solution from the Edit state to the Test state.
Select the Save button.

Tips

Moving a solution from the Edit state to the Test state starts the pack process in the background. Packing a solution involves OSE gathering all of the assets of the solution into a package that represents the solution at a specific time. After the pack process is successfully completed, the solution is moved to the Test state and a message appears stating that the solution has been updated.
If the pack process fails, failure message appears and the solution is moved back to the Edit state.
To check the status, on the Solution Details screen, select Action History and view the Status column.

Release a Company Solution

After testing completes, move the solution from the Test state to the Released state to publish it to the catalog.

Select the Main Menu icon.
Select Opus Solution Environment.
Select Available in the side menu.
Select Company Solutions.
In the Solution Name column, select the hyperlink for the desired solution to view its details in View mode.
Select the Edit button.
Select the Move To button to transition the solution from the Test state to the Released state.
Select the Save button.

Tips

Moving a solution from Test to Released triggers the pack process in the background. Packing a solution involves OSE gathering all of the assets of the solution into a package that represents the solution at a specific time.
After the pack process is successfully completed, the released solution appears in the catalog. To view the released company solution, in the side menu, select Catalog and then Company Solutions.
If the pack process fails, failure message appears and the solution is moved back to the Test state.
Users can download or save the released Company Solution.

Promote a solution from validation to production environment

Create and configure the solution in the Validation environment. When the solution is ready, publish it to the Company Catalog to make it available in the Production environment.

In the Production environment, download the solution from the Company Catalog instead of recreating it. This approach promotes validated solutions across environments, reducing setup time and configuration errors.

Promote a solution from validation to production

In the Validation environment:

Create, configure, and test the solution.
For more details, see Create a Company Solution and Configure a Company Solution.
Release the solution.
For more details, see Release a Company Solution.
Confirm that the released solution appears in the Company Catalog.

In the Production environment:

Navigate to the Company Catalog, and select the released solution.
Download the solution to import it into Production.
For more details, see Download a solution.
Activate the solution.
The solution is now live in the Production environment.

Tips

Publishing or releasing the solution to the Company Catalog makes the solution accessible across environments.
This approach keeps Production environment clean and only exposes solutions that have been validated.

Save As or download a solution from a catalog

The Save As and Download options are available for catalog solutions.

Save As creates a configurable copy of the catalog solution and adds it to your company solutions. Use this option to customize or extend the solution to meet specific business needs.

Download retrieves the catalog solution in its current form, with no additional configuration. Use this option to deploy the solution as is.

Perform a Save As operation on a solution in a catalog

Select the Main Menu icon.
Select Opus Solution Environment.
Select Catalog in the side menu.
Select Company Solutions.
Select the Filter button.
In the Filters push panel, fill in the following fields:
- Application Name drop-down - The desired application name.
- Solution Name field - The name of the available solution.
Select Apply.
From the list of available solutions, select the hyperlink in the Solution Name column that corresponds to the desired solution.
The Company Catalog Solution Details screen appears.
Select Save As.
In the Save As push panel, fill in the following fields:
- Solution Name field - Required. The desired solution name that is being created. This is a unique identifier for the solution.
- Solution Description field - A description of the solution and its purpose.
Select Apply.
A success message appears after the solution is created.

Tips

To view the saved solution, in the side menu, select Available, then Company Solutions and search for the created solution. The solution is in Edit state.
To check the solution status, on the Solution Details screen, view the Status column in the Action History section.

Download a solution

Select the Main Menu icon.
Select Opus Solution Environment.
Select Catalog in the side menu.
Select Company Solutions.
Select the Filter button.
In the Filters push panel, fill in the following fields:
- Application Name drop-down - The desired application name.
- Solution Name field - The name of the available solution.
Select Apply.
From the list of available solutions, select the hyperlink in the Solution Name column that corresponds to the desired solution.
The Comany Catalog Solution Details screen appears.
Select Download.
In the Download Solution push panel,slect Apply.
A success message appears after the solution is created.

Tips

To view the created solution, in the side menu, select Available, then Company Solutions and search for the created solution. The solution is in Released state.
To check the solution status, on the Solution Details screen, view the Status column in the Action History section.
Verify the version number before downloading. Attempting to download a lower version fails if a higher version of the solution is already present in the system.

Create a new solution version

After a solution is released and shared across environments, any new changes must be made in a new version and not in the shared version. This ensures users, including those in Production, can clearly distinguish between versions and it reduces the risk of misalignment. After creating a new version, configure the new solution version to include updated fields, workflows, menus, or other changes, without affecting the currently released version.

The following versioning format is used while creating a new solution version:

Major.Minor.Patch

Create a new solution version

Select the Main Menu icon.
Select Opus Solution Environment.
Select Available in the side menu.
Select Company Solutions.
Select the Filter button.
In the Filters push panel, fill in the following fields:
- Application Name drop-down - The desired application name.
- Solution Name field - The name of the available solution.
Select Apply.
From the list of available solutions, select the hyperlink in the Solution Name column that corresponds to the desired solution.
The Solution Details screen appears.
Select Next Version.
In the Next Version push panel, fill in the followin field:
- Version Type drop-down - The type of the solution version
  - Major - Specifies breaking, non‑compatible changes. Major version starts with 1 and increments in ascending order.
  - Minor- Specifies backward‑compatible new features. Minor version starts with 0 and increments in ascending order.
  - Patch - Specifies bug fixes. Patch version starts with 0 and increments in ascending order.
Select Apply.
A success message appears after the new version of the solution is created.

Tips

To check the solution status, on the Solution Details screen, view the Status column in the Action History section.
The solution is moved back to Edit state so that it can be configured to add new fields, workflows, menus, or any other changes.
The system removes the earlier version of the solution from the Available Company Catalog.

Tag end