Icadot docs

Appearance

Example applications ​

This page demonstrates what you can build with Icadot based on the available elements, validations, rules, roles, data views, and workflow components.

Icadot does not function as a traditional app builder focused primarily on designing screens. Instead, it acts as a solution builder where you combine pages, elements, logic, validations, access rules, and data views into a complete working solution.

Below are example applications that align well with the capabilities visible in the codebase.

1. Intake and registration form ​

What it does ​

A user completes a structured form to register, submit a request, or provide information. The solution validates the input in real time, ensures that required and correctly formatted data is entered, stores the data, and then presents a summary or confirmation before or after submission. This ensures both data quality and a clear user flow.

How you can build it ​

Page structure ​

  • Section for logical grouping such as personal details, contact information, and additional input
  • Input Text for names, descriptions, or explanations
  • Input Email for email addresses
  • Input Phone for phone numbers
  • Input Postal Code for address-related data
  • Input Date for birth dates, start dates, or appointment dates
  • Multiple Choice or Single Choice for selection-based questions
  • Attachment for uploading supporting documents
  • Button or Action to save or continue
  • Summary to review all entered data before submission

Validations ​

  • Required for mandatory fields
  • Validation type for email, phone, postal code, or account numbers
  • Validation message for clear field-level feedback

Rules ​

  • Show additional fields based on user input
  • Make fields read-only after submission
  • Enable actions only when all required fields are valid

Roles ​

  • End user can enter data
  • Processor can review and edit
  • Manager can read or approve

Why this fits well ​

The combination of input elements, validation, role-based access, and summary behavior makes Icadot highly suitable for structured intake and registration processes.

2. Worklist or case overview ​

What it does ​

Users are presented with a structured list of records such as cases, requests, or tasks. They can search, filter, sort, and open records, perform actions per item, and manage their workload efficiently. The solution acts as an operational interface for handling ongoing work.

How you can build it ​

Page structure ​

  • Table as the main component for displaying records
  • Query to retrieve data dynamically
  • Section for filters and contextual information
  • Button for creating new records or exporting data
  • Page Element Link or Page Selector for navigation
  • Progress Counter or Score for status or progress indicators

Validations ​

  • Required filters
  • Validation for bulk actions
  • Feedback for empty or invalid results

Rules ​

  • Show only user-related data
  • Enable actions based on status or role
  • Hide functionality based on permissions

Roles ​

  • Employee sees assigned items
  • Coordinator sees team-level data
  • Admin has full access and control

Why this fits well ​

The presence of elements such as Table, filtering, row-level actions, and user-context handling makes Icadot very effective for operational worklist and case management scenarios.

3. Planning or scheduling solution ​

What it does ​

Users manage appointments, tasks, or activities over time. The solution provides visibility into schedules, availability, and assignments, and allows users to create, update, and manage time-based records.

How you can build it ​

Page structure ​

  • Agenda View for calendar-based visualization
  • Input Date and Input Time for scheduling
  • Plan Board for visual planning across teams or resources
  • Task for linked work items
  • User for assigning responsibility
  • Section for structuring planning information

Validations ​

  • Date must fall within allowed ranges
  • End time must be after start time
  • Availability validation
  • Required selections for user, type, or location

Rules ​

  • Show only available time slots
  • Display additional fields based on appointment type
  • Lock planning after approval
  • Restrict creation based on permissions

Roles ​

  • Planner manages planning
  • User sees personal schedule
  • Viewer has read-only access

Why this fits well ​

The combination of Agenda View, time-based inputs, and task-related elements makes this a natural use case for Icadot.

4. Assessment, scan, or maturity model ​

What it does ​

Users answer structured questions and provide ratings or scores. The system processes the input, calculates results, and presents a summary or visual feedback such as scores, charts, or indicators. This supports evaluation, benchmarking, and decision-making.

How you can build it ​

Page structure ​

  • Single Choice and Multiple Choice for answers
  • Rating for scoring
  • Slider for scale-based input
  • Input Text for explanations
  • Score for calculated results
  • Gauge, Chart, or Data Graph for visual feedback
  • Summary for final overview
  • Tab or step-based structure for segmentation

Validations ​

  • Required answers for key questions
  • Minimum selection rules
  • Conditional validation for explanations

Rules ​

  • Show follow-up questions dynamically
  • Calculate scores only when complete
  • Trigger warnings based on thresholds
  • Adjust flow based on results

Roles ​

  • Participant completes assessment
  • Reviewer analyzes results
  • Manager sees aggregated insights

Why this fits well ​

Built-in support for scoring, summaries, and visual data makes Icadot particularly strong for assessments and evaluation tools.

5. Dashboard or management overview ​

What it does ​

Users gain insight into performance, trends, and status through visual and aggregated data. The solution transforms raw data into meaningful information for monitoring and decision-making.

How you can build it ​

Page structure ​

  • Aggregate for totals and averages
  • Chart and Data Graph for trends
  • Gauge for KPI indicators
  • Data Board for grouped visual data
  • Table for detailed records
  • Paragraph for context
  • Grid and Section for layout

Validations ​

  • Filter validation
  • Date range validation

Rules ​

  • Role-based visibility
  • Dynamic filtering
  • Hide sensitive data

Roles ​

  • Employee sees personal data
  • Manager sees team data
  • Executive sees full overview

Why this fits well ​

The combination of aggregation, visualization, and structured data display makes Icadot well suited for dashboards and reporting.

6. Document or evidence-based workflow ​

What it does ​

Users upload and manage files, photos, or visual input as part of a structured process. These inputs act as supporting evidence within workflows such as inspections, approvals, or registrations.

How you can build it ​

Page structure ​

  • Attachment for documents
  • Photo for capturing images
  • Image for displaying visuals
  • Sketch for annotations
  • Markup Template for structured output
  • Button for submission

Validations ​

  • Required uploads
  • File type restrictions
  • File size limits

Rules ​

  • Show uploads conditionally
  • Lock files after submission
  • Display media based on context

Roles ​

  • User uploads
  • Reviewer evaluates
  • Admin manages

Why this fits well ​

The presence of media elements enables Icadot to support evidence-driven workflows effectively.

7. Authentication and self-service environment ​

What it does ​

Users authenticate themselves, register accounts, and interact with personalized data and processes. Access is controlled based on identity and role, ensuring that users only see what is relevant to them.

How you can build it ​

Page structure ​

  • Authentication for login
  • Register for onboarding
  • User for profile or context
  • Input Password for credentials
  • Captcha for security
  • Language Switch for localization

Validations ​

  • Required registration fields
  • Email and password validation
  • Captcha verification

Rules ​

  • Show registration only for anonymous users
  • Show profile only when logged in
  • Redirect users based on role

Roles ​

  • Anonymous user
  • Registered user
  • Administrator
  • Internal staff

Why this fits well ​

Built-in authentication, user context, and role-based access make Icadot suitable for secure, user-specific applications.

8. Integration or search-driven solution ​

What it does ​

Users search for and retrieve data from internal or external sources. The solution uses this data to populate fields, link records, or drive further actions within the process.

How you can build it ​

Page structure ​

  • Query for data retrieval
  • Input Text or Input ID for search
  • Table or Data View for results
  • Link Data for relationships
  • Set Value for auto-fill
  • Button to trigger search

Validations ​

  • Required search input
  • Format validation
  • Error handling for no results

Rules ​

  • Show results only after search
  • Auto-fill based on retrieved data
  • Restrict linking based on permissions

Roles ​

  • User searches and links
  • Viewer reads only
  • Admin manages

Why this fits well ​

The presence of Query, integration logic, and data linking makes Icadot well suited for data-driven and integration-heavy solutions.