Skip to content

1.3.0

Latest

Choose a tag to compare

@github-actions github-actions released this 12 Sep 14:08

Branch on an answer from any earlier screen

Your flow can now remember what people answer and use it later. Ask a question on one screen, show a few more screens, and then send people down different paths based on that earlier answer. Until now a split could only look at the screen right before it.

Answers are remembered for the whole flow. Every answer someone gives is kept until the flow ends, so a split can read an answer from any earlier screen. Splits that read the screen right before them work exactly as before.

Saving an answer as a user attribute works the same way. A split that reads an earlier screen saves that answer when the person moves on past the split.

Older app versions take the default path. If your app still runs an older SDK, a split that reads an earlier screen follows its default path. Update the SDK before publishing a flow that relies on it.

More question types can drive a split. Quiz, chip, and segmented control answers can now steer a split, alongside radio group, dropdown, NPS, rating, checkbox, and button.

Fixes worth knowing

  • Multi-select answers are reported as a comma-separated list, so they can be matched by a split and saved cleanly as an attribute.
  • Clearing a selection no longer counts as an answer.

Picking an earlier screen as a split's source is done in the flow editor: open the split and choose the screen and the question it should read.