Solution Designer has been deprecated in favor of Opus Solution Environment (OSE).

Manage solutions and packages

Solution Administrators and Solution Developers use solutions to apply certain functionality to apps and their networks on the Opus Platform. Solutions pull together configurable assets (i.e. object types within the data model, workflows, user experience tasks, roles, and policies) that define certain elements of an app's behavior. Each solution is developed for use with a specific type of app (e.g. Agile Process Teams), and TraceLink can apply a solution to that app or one of the app's networks on behalf of the company, deploying the solution’s functionality to the company's users. Contact TraceLink Support to apply a solution to an app or network.

Make a solution available in an environment

Install a solution from a package to make the solution and its assets available in the current environment (e.g. Validation). When installed, the solution is available for customization, and TraceLink can apply the solution to an app or network on behalf of the company.

Verify a package with a Status of Ready to refresh the package's Status and confirm whether the package can be installed as a solution.

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select Saved Packages.
    • Status – Indicates the verification status of the package and whether the package can be installed as a solution:
      • Ready – TraceLink has verified the package and found that the package can be installed as a solution.
      • Verifying Package – TraceLink is verifying the package to ensure that the package can be installed as a solution.
      • Invalid Package – TraceLink has verified the package and found an issue (e.g. the package is corrupt).
      • Incompatible App Version – TraceLink has verified the package and found that the solution's app has a lower version number than the minimum supported version number for the package. To install the package as a solution, the app version must be the same as or higher than the minimum supported version.
    • Package Name – The name of the package.
    • Description – The description of the package.
    • Version – The version number for the package.
    • Date Added – The date and time that the package was added to the Saved Packages tab.
    • Reports – The number of reports generated as a result of the previous verifications for this package.

      Select the link in the Reports column to view the result of previous verifications for the package.

  4. Select the Application with the packages to view.
  5. Select the Action icon in a row for a package with a Status of Ready.
  6. Select Verify Package.

    TraceLink begins verifying the package, and the package's Status changes to Verifying Package. When verification completes, the package's Status changes to one of the following:

    • Ready – TraceLink has verified the package and found that the package can be installed as a solution.
    • Invalid Package – TraceLink has verified the package and found an issue (e.g. the package is corrupt). The package cannot be installed as a solution.
    • Incompatible App Version – TraceLink has verified the package and found that the solution's app has a lower version number than the minimum supported version number for the package. To install the package as a solution, the app version must be the same as or higher than the minimum supported version. The package cannot be installed as a solution.
  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select Saved Packages.
    • Status – Indicates the verification status of the package and whether the package can be installed as a solution:
      • Ready – TraceLink has verified the package and found that the package can be installed as a solution.
      • Verifying Package – TraceLink is verifying the package to ensure that the package can be installed as a solution.
      • Invalid Package – TraceLink has verified the package and found an issue (e.g. the package is corrupt).
      • Incompatible App Version – TraceLink has verified the package and found that the solution's app has a lower version number than the minimum supported version number for the package. To install the package as a solution, the app version must be the same as or higher than the minimum supported version.
    • Package Name – The name of the package.
    • Description – The description of the package.
    • Version – The version number for the package.
    • Date Added – The date and time that the package was added to the Saved Packages tab.
    • Reports – The number of reports generated as a result of the previous verifications for this package.

      Select the link in the Reports column to view the result of previous verifications for the package.

  4. Select the Application with the packages to view.
  5. Select the Action icon in a row for a package with a Status of Ready.
  6. Select Install as Solution.

    To be certain that the package can be installed, verify the package before installing it.

  7. Fill in the fields on the Name and Description step:
    • Solution Name – The name for the installed solution, which must be unique across all solutions for the app in the current environment.
    • Description – The description of the installed solution.
  8. Select Next.

    TraceLink confirms that the solution name is unique and verifies the package to ensure that the solution can be installed. TraceLink also identifies whether any assets in the package have the same name as an existing asset in the environment and whether those existing assets have been modified since they were installed.

  9. If one or more assets have the same name as an existing asset in the environment and those existing assets have been modified since they were installed, specify which asset to associate with the installed solution on the Installation step:
    • Select Use Existing to associate the installed solution with the existing asset in the environment that has the same name.

      or

    • Install the asset in the package with a unique name:
      1. Select Add New.
      2. Enter a New Name for the asset, which must meet one of the following uniqueness requirements:
        • For object types in the Data Model, the New Name must be unique across all object types in the environment.
        • For Workflows, the New Name must be unique across all workflows for the object type that the workflow is associated to.
        • For Experience tasks, the New Name must be unique across all tasks in the environment.
        • For Roles, the New Name must be unique across all roles for the app in the environment.

    Tips:

    • If a type of asset (e.g. Workflows) has at least one asset that is not unique, the Assets Not Unique icon displays next to the collapsible section.
    • Installation conflicts never occur for Policies.
  10. Select Install.

    TraceLink begins installing the solution and specified assets as follows:

    • The solution is installed with the entered Solution Name and Description.
    • If an asset with the same name does not currently exist in the environment, the asset from the package is installed with its original name.
    • If an asset with the same name currently exists in the environment but has not been modified, the installed solution uses the existing asset with that name, and the asset from the package is not installed.
    • If an asset with the same name currently exists in the environment and has been modified since it was installed and Use Existing is selected, the installed solution uses the existing asset with that name, and the asset from the package is not installed.
    • If an asset with the same name currently exists in the environment and has been modified since it was installed and Add New is selected, the asset from the package is installed with the New Name.

    The Solutions screen displays when the installation completes with a new row for the installed Solution.

Move a solution from Validation to Production when your company is ready to make customizations live.

  1. Coordinate with an Application Administrator for the solution's app to determine which app versions are in use in Validation and Production. To move a solution from Validation to Production, the version of the app in Production must be the same as or higher than the app version in Validation. See the Administer Help Center for more information.

    Contact TraceLink Support for assistance, if needed.

  2. Perform the following steps in Validation:
    1. Save the solution as a package.
    2. Select Saved Packages.
    3. Select the Action icon for the Package generated from saving the solution, which has a Status of Ready.
    4. Select Download Package.

      The package downloads to your local system as a .slnpkg file.

  3. Go to Production, and perform the following steps:
    1. Import the package file downloaded in Validation.
    2. Install the package to make the solution and its assets available in Production.
    3. Apply the installed solution to an app or network to use the solution with that app or network in Production.

Manage solutions and packages

Save a package from the list of available packages to make the package available for installation by your company in the current environment (e.g. Validation). The Available Packages tab displays packages for apps your company has licensed. For example, if a company owns Agile Process Teams (APT), the Supply Chain Work Management package, which is licensed with APT, is available for that company.

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select Available Packages to view the packages available to your company.
    • Package – The name of the package.
    • Description – The description of the package.
    • Version – The version number for the package.
    • Date Released – The date that the package provider made the package version available in the available packages.
  4. Select the Application with the packages to view.

  5. Select the Save icon for the Package to save.

    TraceLink begins saving the package in the environment. The package then displays on the Saved Packages tab where it can be installed, making the package's solution and assets available in the environment.

Save an installed solution as a package to preserve the current state of the solution and the assets that the solution uses. For example, consider saving a solution as a package before modifying the solution's assets to maintain a version that can be installed later, in case the changes need to be reverted. You might also save a solution as a package to move the solution from Validation to Production.

  1. Select Customize in the side menu.
  2. Select Solutions.

    The Installed Solutions tab displays by default.

    • Status – Indicates whether the solution is applied to the Application or one of the app's networks in Administer. Displays icons that represent one of the following statuses:
      • Applied – The solution is currently applied.

        An app or network can have only one solution applied to it at a time.

      • Not Applied – The solution is not currently applied.
    • Solution – The name of the solution.

      Select the link Solution column to view the number of each asset that the solution is using, and then select the Go To icon in the Details panel to view those assets.

    • Description – The description of the solution.
    • Installed From – The name of the package that the solution is installed from.
    • Last Modified – The date and time that one of the solution's assets was last modified.
  3. Select the Application with the solutions to view.
  4. Select the Action icon for the solution to save as a package.
  5. Select Save as Package.

    TraceLink begins saving the solution as a package in the environment. The package then displays on the Saved Packages tab.

Tips

  • Select the Action icon for a solution, and then select Edit to customize the solution's assets. This option is only available to users with the Solution Developer role.
  • If a solution has a Status of Not Applied, select the Action icon for a solution, and then select Remove to remove the solution. Removing a solution does not remove the assets that the solution uses.

Import a solution package (.slnpkg) file from your local system to make the package available for installation by your company. You might import a downloaded package to make it available in another environment (e.g. to move the solution from Validation to Production).

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select Saved Packages.
    • Status – Indicates the verification status of the package and whether the package can be installed as a solution:
      • Ready – TraceLink has verified the package and found that the package can be installed as a solution.
      • Verifying Package – TraceLink is verifying the package to ensure that the package can be installed as a solution.
      • Invalid Package – TraceLink has verified the package and found an issue (e.g. the package is corrupt).
      • Incompatible App Version – TraceLink has verified the package and found that the solution's app has a lower version number than the minimum supported version number for the package. To install the package as a solution, the app version must be the same as or higher than the minimum supported version.
    • Package Name – The name of the package.
    • Description – The description of the package.
    • Version – The version number for the package.
    • Date Added – The date and time that the package was added to the Saved Packages tab.
    • Reports – The number of reports generated as a result of the previous verifications for this package.

      Select the link in the Reports column to view the result of previous verifications for the package.

  4. Select the Application for the solution you want to import.
  5. Select the Import Package icon.
  6. Attach the file to upload in the Import Package panel.
  7. Select Import.

    TraceLink begins importing the file. The package then displays on the Saved Packages tab where it can be installed, making the package's solution and assets available in the environment.

Download a solution package as a package (.slnpkg) file. You can download a package so you can import it into another environment (e.g. to move the solution from Validation to Production).

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select Saved Packages.
    • Status – Indicates the verification status of the package and whether the package can be installed as a solution:
      • Ready – TraceLink has verified the package and found that the package can be installed as a solution.
      • Verifying Package – TraceLink is verifying the package to ensure that the package can be installed as a solution.
      • Invalid Package – TraceLink has verified the package and found an issue (e.g. the package is corrupt).
      • Incompatible App Version – TraceLink has verified the package and found that the solution's app has a lower version number than the minimum supported version number for the package. To install the package as a solution, the app version must be the same as or higher than the minimum supported version.
    • Package Name – The name of the package.
    • Description – The description of the package.
    • Version – The version number for the package.
    • Date Added – The date and time that the package was added to the Saved Packages tab.
    • Reports – The number of reports generated as a result of the previous verifications for this package.

      Select the link in the Reports column to view the result of previous verifications for the package.

  4. Select the Application with the packages to view.
  5. Select the Action icon for the package to download.
  6. Select Download Package.

    The package downloads to your local system as a .slnpkg file.

Remove a solution package when it is no longer needed.

  1. Select Customize in the side menu.
  2. Select Solutions.
  3. Select Saved Packages.
    • Status – Indicates the verification status of the package and whether the package can be installed as a solution:
      • Ready – TraceLink has verified the package and found that the package can be installed as a solution.
      • Verifying Package – TraceLink is verifying the package to ensure that the package can be installed as a solution.
      • Invalid Package – TraceLink has verified the package and found an issue (e.g. the package is corrupt).
      • Incompatible App Version – TraceLink has verified the package and found that the solution's app has a lower version number than the minimum supported version number for the package. To install the package as a solution, the app version must be the same as or higher than the minimum supported version.
    • Package Name – The name of the package.
    • Description – The description of the package.
    • Version – The version number for the package.
    • Date Added – The date and time that the package was added to the Saved Packages tab.
    • Reports – The number of reports generated as a result of the previous verifications for this package.

      Select the link in the Reports column to view the result of previous verifications for the package.

  4. Select the Application with the packages to view.
  5. Select the Action icon for the package to remove.
  6. Select Remove Package.

  7. Select Remove in the confirmation dialog.
    The package is removed from your company's local library. This does not remove or affect any solutions already installed from the package.