A Guide to App Transitions

An explainer on transitions in triggers

Many triggers in Apps will end with a Transition. This article outlines how Transitions operate, the capability of Transitions, and what to expect when running Transitions.

What are Transitions?

Transitions are what allows the user to navigate between steps and Apps. Within any kind of trigger, a Transition can be added to appropriately route the user through the Apps you create.

By clicking Add new transition, there are a few options:

Go to Step

• Previous
• Next
• Specific Step
• Go To Step By Name

App

• Cancel App
• Cancel App Then Log Out Current User
• Cancel Then Change To App
• Cancel Then Change To Step App, Step
• Complete and Go to Splash Screen
• Complete App
• Complete App Then Log Out Current User
• Complete Then Change To App
• Complete Then Change To Step App, Step
• Complete Then Change To Step By Name Step
• Complete App Then Go To First Step Of App By Name App

Using Transitions

Identifying the options available is very important, as only one can be added to a Trigger's Then statement. To clarify this point further, it is possible to add a Transition to each Then in a trigger containing multiple conditions, or else statements.

Other notes for Transitions include:

• A Transition must go at the end of the Then Actions. This ensures all data is captured, and the Transition is the last action for that Trigger.
• If using multiple of the same trigger type (i.e multiple triggers on the same button), it is necessary to ensure all Transition based logic is held within a single trigger.

Trigger Interactions with Transitions

When a Transition occurs, Step and App Level Triggers may both be activated. For example, a complete trigger on a step may activate a On Step Close, and an On App Complete trigger to fire. The following diagram outlines various examples to display the flow of events with transitions.

How to Migrate from Pre-Transition Runtime to Transition Runtime

Apps that are still on the pre-transition runtime will see the following notice:

The Start Migration will open up a modal with step-by-step instructions on how to migrate their app. This process can be started and stopped at any point. In some cases, apps will be able to migrate automatically and no action is required. All the user must do is click Convert my app!

However, in many cases, we will not be able to migrate the app automatically, this means they will need to make changes to their app to migrate. The migration process will provide the following instructions to enable them to migrate their app:

FAQ

Can the customer rely on it to resolve the issue and not impact the proper functioning of their setup? I.e. will app routing still be possible afterwards?

Yes, for most triggers we can automatically transfer them over and functionality is preserved. For triggers with pre-transition runtime, it will be a manual migration process.

Verbal Walkthrough of Triggers?

When you click on start migration, you can back out and there will be no changes to the app. The start migration button will walk them through and point them to the triggers that need to be changed. It is expected then that they will fix the triggers in their development version of the app. Once they have tested and verified it all works as expected, they will then need to publish the app. They can then run through the start migration flow again which will ensure they are ready to convert the app which can't be undone afterward. But they can test their apps without impacting published apps until they do the final conversion (which requires to publish a new version anyway).

Did you find what you were looking for?

You can also head to community.tulip.co to post your question or see if others have faced a similar question!