LogoLogo
Documentation
DocumentationUptiq Agents
Documentation
DocumentationUptiq Agents
  • Getting Started
    • Introduction
    • Sign up to Developer Edition
    • Build Your First Agent
    • Developer Support
  • Core Concepts
    • Agent
      • Knowledge
      • Webhook
    • PII Masking
    • Sub-Agent
    • Intent
    • Workflow
      • Node
        • Input
        • Output
        • Loader
        • Display
        • API Node
        • Web Crawler
        • Table Write
        • Table Read
        • Ruleset
        • Upload Document
        • Javascript
        • Workflow
        • Loop
        • Document To Image
        • External Database
        • Storage Write
        • Storage Read
        • Fetch Document
        • Prompt
        • RAG Query
        • Vector Search
        • Emit Event
    • RAG
    • Model Hub
      • Entity Recognizers
    • Data Gateway
    • Rulesets
    • Code Snippets
    • Tables
    • Storage
    • Widget
  • Overview of GenAI
    • Introduction
    • Key concepts
      • Intent Classification
      • Inference
      • Generative AI Models
      • Large Language Models (LLMs)
      • Prompt Engineering
      • AI Agents
      • RAG (Retrieval Augmented Generation)
      • AI Workflow Automation
      • AI Agents vs LLM-based APPs
Powered by GitBook
On this page
  • Overview
  • Configurations
  • Example Use-Cases
  • Key Takeaways for Developers
Export as PDF
  1. Core Concepts
  2. Workflow
  3. Node

Loader

Overview

The Loader Node in UPTIQ Workbench is designed to enhance user experience by displaying a processing message when a workflow involves a time-consuming operation.

When workflows require retrieving external data, running computations, or executing multi-step processes, the Loader Node ensures that users are aware of ongoing activity rather than experiencing delays with no feedback.

This helps to reduce user frustration, improve engagement, and create a smoother conversational flow by keeping users informed during system processing.

Configurations

Field
Description

Text

The message displayed to the user while the process is ongoing. It should be concise, clear, and informative to ensure the user understands the system is actively working.

Best Practices for Loader Messages:

✅ Keep messages short and direct to avoid unnecessary user confusion. ✅ Use clear phrasing to indicate that the process is in progress and will complete soon. ✅ Avoid vague terms like “Processing…”—instead, provide context such as “Retrieving loan details, please wait…”

Example Use-Cases

1. Indicating Data Retrieval from an External API

A financial assistant workflow fetches credit score details from an external API. Since this might take a few seconds, the Loader Node is used to notify the user while waiting for the API response.

  • Configuration:

    • Text: "Fetching your credit score, please wait..."

  • Outcome:

    • The message displays to the user while the API retrieves the data.

    • Once the API call is completed, the workflow proceeds to display the credit score.

2. Handling a Long Computation for Risk Assessment

A workflow in a loan approval system performs a complex risk analysis, which involves checking multiple financial parameters.

  • Configuration:

    • Text: "Analyzing financial data, this may take a moment..."

  • Outcome:

    • The user remains informed that the system is processing their risk assessment.

    • The workflow seamlessly continues once computation completes.

Key Takeaways for Developers

✅ Improves User Experience – Prevents confusion by clearly informing users that their request is being processed.

By incorporating the Loader Node, developers can manage user expectations, enhance workflow responsiveness, and create AI-driven interactions that feel fluid and natural. 🚀

PreviousOutputNextDisplay

Last updated 20 days ago