Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2023-06-23
Concept: Solutions

Concept: Solutions

Share and migrate reporting and analytic, business process, and integration system configurations to reduce the time and effort of recreating configurations from PDF files and page captures. Workday enables you to bundle custom reports, integration systems, business processes, and related configurations into Solutions. You can migrate Solutions between tenants. Example: between Sandbox and Production.
You can't migrate, publish, or import Solutions from tenants in AWS data centers.

Solutions and Configurations

In Workday, a
Solution
 is a single named collection of artifacts, or
Configurations
. You can create, edit, view, publish, and migrate the contents of a Solution in Workday. A Solution is a top-level collection; Solutions can't be part of another Solution. When you publish a Solution, Workday produces one named collection of top-level Configurations that you can share with others.
Solutions can also include one or more page captures or other graphic files. Solutions always include dependent Configurations. Example: if a custom report requires a custom calculated field, the Solution automatically includes it. Solutions never contain certain tenant-specific information, such as the report owner.
Apply tags to a Solution to categorize Solutions by Workday function (such as Cash Management or Integration) and by industry (such as Financial Services or Technology). Applying tags to a Solution enables potential consumers to more easily find Solutions that match their needs.
After importing or migrating a Solution, you resolve exceptions on the imported/migrated configurations that reference tenant-specific information. When you publish a Solution, always review the configurations that you're sharing to ensure that you're not disclosing personal information or other confidential information. You intend to share the Solution with one or more Workday customers when you publish a Solution. When you import a Solution, always review and test the Solution for accuracy, security, and performance issues in a non-Production tenant.

Solutions Security

If you're a member of a security group that has
View
 and
Modify
 access to the
Solution
 domain, you can:
  • View and edit any Solution that anyone created in the tenant previously.
  • View and edit any Solution that anyone migrated into the tenant previously.
  • View any Solution that anyone imported into the tenant.
  • View the associated integration event and Process Monitor data for the Solution migration or import event. This option requires that you're also a member of a security group that has
    View
     access to the
    Integration Event
     domain.
  • View and modify an included Configuration. This option requires membership in a security group that can access the applicable security domain that secures the Configuration.
You can't use Solutions during proxy sessions.

Solution Options

You have these options for Solutions:
  • Publish a Solution for viewing and importing by other Workday customers. Once you’ve published your Solution to the Solution Library, you can make the Solution available to other Workday customers. You can require interested customers to receive approval before receiving your Solution.
  • Import a Solution created by another Workday customer or partner. You can browse for Solutions that other Workday customers and partners published directly in your tenant. When you find a Solution that meets your needs, you can import it into your tenant. The publisher can require you to get approval in advance.
  • Migrate a Solution between 2 of your tenants. You can create and test Configurations in your Sandbox or Implementation tenant. Then you can add them to a Solution and migrate it to your Production tenant.

Types of Solutions: Standard and Bulk

Workday supports the creating of 2 types of Solutions: Standard and Bulk:
Solution Type
Contents
Supports Actions
Standard
  • Configurations of one or more types (such as Custom Reports and Business Process Definitions)
  • Configurations specified in advance when you create or edit the Solution. Contents only change when you edit the Solution.
  • Publishing Solution to Solution Library for use by other Workday customers.
  • Migration of Solution between 2 tenants.
Bulk
  • Configurations of only 1 type (such as Custom Reports
    or
     Business Process Definitions, but not both).
  • Configurations included based on defined filtering rules. Contents can vary depending on when you migrate the Solution, as rules can be time-specific.
Migration of large numbers of Configurations between 2 tenants.

Solution Library

Workday provides a single repository for all Solutions published from any customer tenant. You can access the Solution library from within your tenant without an additional sign-in (this option requires SAML). The Solution library enables you to:
  • View all active published Solutions.
  • View details about a Solution.
  • Request access to protected Solutions.
  • Import Solutions.
Although you can access the Solution library from tenants outside of AWS data centers, it isn't a part of your tenant. While Workday makes every effort to ensure that the Solution library is always accessible, the Workday Service Level Agreement (SLA) doesn’t cover Solution library availability. In addition, Workday doesn’t validate, certify, or support the Solutions that you share.

Solution Requirements for Publishing to Solution Library

Workday reviews publish requests weekly. Shared Solutions are viewable by all customers in the Workday Community, and Workday intends to ensure that all users can easily find Solutions that meet their needs. If the title and description don’t describe the contents and purpose of the Solution in sufficient detail, Workday doesn’t approve a Solution for publication. If Workday doesn’t approve the Solution for publishing to the Solutions Library, Workday sends a notification stating why Workday didn't publish the Solution. You can submit the publish request again after you make any requested changes.

Lifetime of Solutions in Library

Any Solution that no one has downloaded from the Solution library in the past 365 days (except by the publisher) expires. Once the Solution expires, it no longer displays in the Solution library to anyone other than the original publisher.

Interactive Solutions Report

Use the interactive
Solutions
 report to manage all aspects of Solutions, including:
  • View and manage Solutions created in your tenant.
  • View and request Solutions available from the Solution library.
  • View Solutions previously shared with your organization by other customers.
  • View outstanding Solution requests.

Solutions Sharing Workflow

This list displays the complete workflow for creating, publishing, and importing a Solution. It assumes that you’re creating the Solution to share with a
Recipient
.
  1. (Ongoing) You and other users in your tenant create one or more configurations in Workday.
  2. (Optional) You create one or more page captures or other graphic illustrations and supporting documents. You save them in the format of your choice (.gif, .png, .docx, and so on).
  3. You create a Solution in Workday and add the items you created in steps 1 and 2.
    If you don’t have View access to the Domain that secures a specific Configuration, you can’t add it to a Solution.
  4. You save the Solution for later use in Workday.
  5. Either immediately or later, you publish the Solution to the Solution library.
    Optionally, you require that any Recipient request access to the Solution before importing it.
  6. Workday reviews your Solution and either approves or denies the publish request.
  7. The Recipient views the Solution from within their tenant and, if necessary, requests that you grant access to the Solution.
  8. If you required that any Recipient request access, you view the access request in your Notifications.
  9. If you received an access request, you grant or deny the request.
  10. In a Workday non-Production tenant, the Recipient imports the Solution.
  11. Workday imports the selected Configurations. The Recipient reviews and resolves exceptions with the imported Configurations.
  12. After testing the Configurations, the Recipient migrates the Solution into their Production tenant.

Solutions Migration Workflow

This list displays the complete workflow for migrating a Solution between 2 tenants to which you have access.
  1. (Ongoing) You create one or more configurations in Workday.
  2. (Optional) You create one or more page captures or other graphic illustrations and supporting documents. You save them in the format of your choice (.gif, .png, .docx, and so on).
  3. You create either a Standard Solution or a Bulk Solution:
    • Standard Solution: you select and add the Configurations that you created in Step 1.
    • Bulk Solution: you define filtering rules that Workday uses to add the Configurations automatically that you created in Step 1.
    You also add the items that you created in step 2. If you don’t have View access to the Domain that secures a specific Configuration, you can’t add it to a Solution.
  4. You save the Solution for later use in Workday.
  5. Either immediately or later, you migrate the Solution, specifying the destination tenant.
    During migration, Workday includes only Configurations that meet the defined filter rules at the moment that you start the migration.
  6. Workday imports the selected Configurations.