Delete a step

Function: Delete a step

This function allows you to remove a specific step from a "Stepper UI element" in your application. A Stepper UI element is a visual component that guides users through a sequence of steps, often used for multi-part forms, onboarding processes, or complex workflows. By using this action, you can dynamically adjust the steps presented to your users based on their choices or data.

Input

• Stepper UI element (PART): This is the visual component in your application that displays a sequence of steps. You need to select or specify which Stepper UI element you want to modify.
• Step code (STRING): This is a unique identifier (a piece of text) for the specific step you wish to remove from the Stepper UI element.

Output

This action does not produce any direct output. Instead, it modifies the specified "Stepper UI element" by removing the designated step from its sequence.

Execution Flow

Real-Life Examples

Example 1: Removing an optional step in an application form

• Scenario: Imagine you have an online job application form with several steps: "Personal Details", "Education", "Work Experience", and "Review & Submit". If an applicant indicates they are a student with no prior work experience, the "Work Experience" step becomes irrelevant. You can use this action to remove it.
• Inputs:
  • Stepper UI element: JobApplicationStepper (the name of your stepper component)
  • Step code: WORK_EXPERIENCE (the unique identifier for the 'Work Experience' step)
• Result: The "Work Experience" step is removed from the JobApplicationStepper, and the applicant proceeds directly from "Education" to "Review & Submit".

Example 2: Dynamically adjusting a product configuration process

• Scenario: You have a product configurator where users build a custom computer. If a user selects a "Laptop" model, the "Choose Monitor" step is not needed.
• Inputs:
  • Stepper UI element: ComputerConfigurator
  • Step code: CHOOSE_MONITOR
• Result: The ComputerConfigurator updates, and the "Choose Monitor" step is no longer displayed, streamlining the configuration for laptop users.

Example 3: Removing a completed onboarding task

• Scenario: A new user onboarding flow includes steps like "Set Up Profile", "Connect Integrations", and "Explore Dashboard". Once a user successfully connects all their required integrations, you might want to remove the "Connect Integrations" step from the stepper to show progress and prevent them from revisiting it.
• Inputs:
  • Stepper UI element: NewUserOnboarding
  • Step code: CONNECT_INTEGRATIONS
• Result: The NewUserOnboarding stepper updates, and the "Connect Integrations" step is no longer visible, indicating that task is complete.