Procedures Step
individual action or prompt that guides the AI or system through a specific part of a workflow within a larger procedure. In structured interactions, procedure steps serve as building blocks that define the exact flow of tasks, helping to create a seamless, goal-oriented conversation or process.
Purpose
Logic
A Step represents an individual action or prompt in a conversation that the AI or system should follow within a procedure. Creating these steps allows the AI to:
Guide the Interaction: Steps provide structured prompts or actions for the AI to follow in a specific order.
Follow a Workflow: Steps support a Standard Operating Procedure (SOP)-like logic, allowing for orderly, adaptable task sequences.
Resume with Context Awareness: If the user exits mid-procedure and returns, the AI can continue from the last completed step using stored context and chat history.
Each step can be enhanced with sub-steps, providing additional granularity and control over the procedure.
Components and Features
1. Steps
Each step includes fields and features to guide the setup process:
Field Type: Single-line text input with reorder functionality.
Label: "Steps"
Placeholder Text: "Describe step-by-step how to guide conversation in this procedure."
Step Features and Configuration Options
Add Step
Button Type: Action button.
Purpose: Allows users to add a new step to the procedure, helping define a sequence of actions for structured workflows.
Functionality: Each step can include logic to review context and chat history, ensuring proper flow through each stage of the procedure.
How to Add a Step:
Click the + Add Step button in the Steps section.
Enter a name and description for the step, outlining its purpose within the procedure.
Define the step order (e.g., Step 1, Step 2) to establish sequence.
Reorder Controls
Button Type: Drag-and-drop functionality.
Purpose: Enables users to adjust the sequence of steps by dragging them into the desired order.
Functionality: Adjust the procedure’s flow to fit different scenarios, providing flexibility in conversation direction.
How to Reorder Steps:
Drag and drop steps to adjust their order, ensuring that the procedure follows a logical progression.
Sub-Steps
Purpose: Break down a single step into detailed actions or prompts, allowing for granular control within a single step.
CRUD Functionality: Users can Create, Read, Update, and Delete sub-steps, giving flexibility to build out each step with multiple actions.
How to Add Sub-Steps:
Within each main step, click Add Sub-Step.
Enter a name and description for each sub-step, explaining its role.
Set the sequence of sub-steps to establish order within the main step.
Repeat for additional sub-steps as needed.
Edit
Button Type: Action button.
Purpose: Allows editing and reordering of steps and sub-steps to ensure accuracy and clarity.
How to Edit Steps and Sub-Steps:
Click Edit next to a step or sub-step.
Modify any details, including the step’s name, description, or order.
Click Save to apply changes.
Save
Button Type: Action button.
Purpose: Saves any edits made to the steps or sub-steps, ensuring changes are recorded.
Discard
Button Type: Action button.
Purpose: Discards unsaved changes, preserving the previous configuration if modifications are unnecessary or incorrect.
Notes on Step Logic
The Step Logic controls the procedure’s flow, ensuring each step is executed in order while handling conditions and dependencies effectively. The key aspects of step logic include:
Multiple Steps Addition
Users can add multiple steps to manage various aspects of the conversation flow.
Conditional Logic: Steps can be configured with conditions to adapt based on user inputs or system data, enhancing responsiveness in the interaction.
Sub-Steps Addition: Within each step, users can break down complex actions into sub-steps, making intricate workflows manageable.
Context and Chat History Check
Context Check: Verifies if essential context (e.g., required data) is met before proceeding to the next step.
Example: If the procedure requires the user’s name before collecting contact details, the system checks that "UserName" context is filled.
Chat History Check: If the user exits and returns, the system reviews chat history to identify the last completed step, resuming from this point.
Example: If the AI asked the user’s gender and the user exited, the conversation will resume from this question upon their return.
Returning to Last Completed Step
If the user exits after completing Step 2, the system will resume from Step 2 (e.g., asking for gender) upon return, ensuring continuity in the procedure.
Tips for Setting Up Effective Steps
Clear Naming: Use descriptive, action-oriented names for each step to ensure clarity.
Logical Order: Arrange steps thoughtfully, as the procedure will follow the sequence during execution.
Review for Accuracy: Double-check each step’s details and logic to ensure a smooth workflow.
By following this guide, you can effectively build structured, adaptable steps in the Procedure Interaction module, supporting consistent workflows and responsive AI interactions
Last updated