What do I have to do to transition?

Important

This article has been archived.

 

Effective January 1, 2020, Box no longer offers Relay Classic, and your workflows or workflow templates are lost.  As for any Box files you may have used in Relay Classic workflows, these remain in Box and you can continue to access them as you normally do.


Here are more details on the new and improved Box Relay and Relay Lite that have replaced Relay Classic.

If you’re currently using Relay Classic, you must officially update your subscription to the new Box Relay. If you are a full Relay Classic customer (that is, the number of Relay seats you've purchased matches the number of Box seats you've purchased), there is no cost to do this. You can do this any time up until December 30th, 2019, regardless of your Relay renewal date. Your Box account executive or renewal manager can help you update your subscription.

 

Because Box Relay Classic is to be permanently discontinued at the end of 2019, you must transition to the new Box Relay.  After December 31, 2019:

  • Relay Classic shuts down and is no longer available or accessible. This includes all templates and workflows.
  • You can no longer access the Relay Classic link.
  • All historical data is deleted
  • The Relay Classic icon in the user interface is removed

When you have the new Relay provisioned, it becomes available to your Box admins and co-admins. At that point, you can in turn enable it for additional managed users in your organization. You can also begin moving all of the data and workflows from IBM's operating environment in Relay Classic to Box Relay.  This involves manually recreating selected workflow templates in the new Relay builder, and downloading .csv files of historical activity.  Admins can view all the workflow templates created within their enterprise, as well as who owns the template.

 

Regardless of when you provision the new Relay, you have Relay Classic access until December 31st, so you can continue to access historical data and run your workflows as necessary.

Note

The actual files related to the workflows were never stored in IBM, so that content remains in Box.

 

To transition from Relay Classic to Relay, you must do three things:

  1. Take the workflows you currently have in Relay Classic and manually rebuild them in new Relay.
  2. Download and save historical data, such as workflow history, for audit trail purposes
  3. Remove all calls to the Relay Classic APIs.
Notes

The new Box Relay is substantially more powerful and feature-rich than Relay Classic.  New APIs you can use to interact with this product are currently under development.  However, they will not be immediately available to use as part of the deprecation effort.

There is no release date yet for these new APIs.

 

Rebuilding Relay Classic workflows

 

To rebuild current Relay Classic workflows in New Relay

  1. Open Relay Classic. The Active Workflows page displays.
  2. Click the down arrows for Status, Templates, Task Assignee, and Owner, and select All for each.
    • Alternatively, you can work with each workflow owner to identify which templates he or she wants to continue to use in the new Relay, and then rebuild only those.
  3. In the new Relay, manually recreate the workflows you want. Find details for using the new Relay workflow builder in the new Relay knowledge base.

 

Keep in mind, you have a lot of time to re-create all of your workflows in Relay.  You have access to both Relay Classic and the new Relay through the end of 2019.

 

Downloading and saving historical Relay Classic data

You can download a report listing all of the templates used in your organization, and also download full workflow history for specific Relay Classic templates.

 

To download a report listing all of the templates used in your organization

  1. Open Relay Classic. The Active Workflows page displays.
  2. In the top navigation, toward the right, click New

 

RelayClassicTransition_NewReport_71298.png

 

  1. From the menu that displays, click Report.  The Create a Report window opens.

RelayClassicTransition_CreateReportWindow_71298.png

    • If you do not see the Create Report option, contact your Box account representative or open a support ticket.
  1. In the Create a Report window, enter a report name.
  2. Click the Report Type down arrow. From the menu that displays, click Template Current State.
  3. Optionally, enter the name of the template owner. You can omit this step, but specifying owners may make it easier for you to track the various templates you wish to migrate.
  4. Click Create. Box generates the report in .CSV format and sends it to your default Box Relay Reports.

 

To download a full workflow history for specific Relay Classic templates

  1. Open Relay Classic. The Active Workflows page displays.
  2. In the top navigation, toward the right, click New
  3. From the menu that displays, click Report.  The Create a Report window opens.
    • If you do not see the Create Report option, contact your Box account representative or open a support ticket.
  4. In the Create a Report window, enter a report name.
  5. Click the Report Type down arrow. From the menu that displays, click Workflow Current State.  Then:
    • For a history of all the workflows, or discrete runs, of a particular template, in the Template Name box click the down arrow and then click the name of the template you want.
    • For a history of all the workflows, or discrete runs, for every one of your templates, leave the Template name box blank.
  6. Optionally, enter the Workflow owner, and provide a start date and an end date if you wish to limit the report to a specific date range.
  7. Click Create. Box generates the report in .CSV format and sends it to your default Box Relay Reports.

 

Removing calls to Relay Classic APIs

This section helps developers update their apps to remove all reliance on Relay Classic API endpoints.  The endpoints affect the following functions:

  • Get list of published Relay Classic templates
  • Get list of Relay Classic workflows
  • Launch a Relay Classic workflow.

For additional support, file a support ticket.

 

For more information

 

Version history
Revision #:
14 of 14
Last update:
‎01-07-2020 03:02 PM
Updated by:
 
Labels (2)
Contributors