Ask AI
Skip to main content

Get next step

Function: Get next step​

This action helps you navigate through multi-step processes, often called "Steppers," by identifying the next step in the sequence. It retrieves the unique identifier (code) of the step that comes immediately after the one currently open in your chosen Stepper UI element. This is useful for automating navigation or displaying upcoming steps to your users.

Input​

  • Stepper UI element: The specific Stepper component on your page for which you want to find the next step. This is a required input.

Output​

  • Result: The name of a variable where the unique code of the next step will be stored. By default, this variable is named NEXT_STEP. The stored value will be a number representing the code of the next step.

Execution Flow​

Real-Life Examples​

Here are some ways you can use the "Get next step" action in your applications:

Example 1: Automating Step-by-Step Forms​

Imagine you have an application form with multiple sections (Personal Details, Address, Employment, Review). After a user completes one section, you want to automatically move them to the next.

  • Inputs:
    • Stepper UI element: ApplicationFormStepper (your form's stepper component)
  • Result: The variable NEXT_STEP will contain the code for the next section, for example, 2 (representing the "Address" step if "Personal Details" was step 1). You can then use this value to programmatically open the next step.

Example 2: Displaying "Next Up" Information​

You want to show your users what the next stage of a process is, even before they click a "Continue" button.

  • Inputs:
    • Stepper UI element: OnboardingProcessStepper (your user onboarding flow)
  • Result: The variable NEXT_STEP will contain the code for the next step, for example, 3 (representing "Set up Profile" if the current step is "Welcome"). You can then display this information on your page, like "Next up: Set up Profile".

Example 3: Conditional Navigation Logic​

In a complex workflow, you might have different paths depending on user choices. This action can help you get the default next step, which you can then override with your custom logic.

  • Inputs:
    • Stepper UI element: ProductConfigurationStepper (a stepper for customizing a product)
  • Result: The variable NEXT_STEP will contain the code for the next sequential step, for example, 4 (representing "Choose Accessories"). You can then use a conditional statement: "If user selected 'Premium Package', then navigate to step 5 (Special Features), otherwise navigate to NEXT_STEP."