Publishing & Update Strategy

In this article, we'll walk through:

• creating and updating your Program using Workshop.
• strategies for coordinating updates post-launch.

After reading this documentation, you will:

• know when to use your Testing environment and why.
• know how to make changes pre and post-launch.
• know the best use case for using Workshops’s prototyping capabilities.

Unlike other tools— which make you dependent on a different team to implement software changes—Workshop allows you to iterate, test, and refine your configuration.You can review your changes from the user’s perspective, helping you to develop your configuration so it aligns and grows with your program.

Workshop includes a Test environment, which is a safe place for you to verify and test your changes before you commit them to your final program by publishing to your Live environment. Read more about Workshop Testing.

Whether you’re building your initial Program for launch, or refining your configuration to improve your Program, we always recommend that you verify your changes in the Test environment before proceeding to publish in your Live environment. Read more about Publishing to Live.

Important note: You do not have to publish each individual change you make to Live. You may choose to build, verify, build more, verify and then publish to Live.

Making changes pre-launch

Before the launch of your Program, you have more flexibility to make changes and iterate without repercussions to real patients.

During this phase of your program design, we recommend that you use your Test environment for iteration and verification. Publish to your Live environment when you are ready for real users to interact with your Program, or when you are have verified your changes and are happy with them

Coordinating updates post-launch

At this time, Workshop does not support choosing specific changes from the list of Unpublished Changes to publish to the Live environment. Everything on the list of Unpublished Changes is published to the Live environment in unison.

For example, if Autumn updated 4 Email Templates, and Bob created a new Alert, you would not be able to publish only the new Alert without also publishing the Email Template update.

We recommend that you and your team plan your changes in chunks, if there are multiple sets of work that need to be published but not at the same time.