- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Forms
In Studio, a Form is a file with a .uiform extension that contains the design and layout information for creating customized user interfaces using the Form Builder. When you create a new Form, the Form Builder opens in the Designer panel.
The Form Builder is a customized implementation of the form.io engine that allows you to create customized forms for your attended automation workflows. It provides a drag-and-drop interface for designing forms and callouts, which you can then integrate into your projects.
The Form Builder has a variety of form elements available, including text boxes, dropdowns, checkboxes, radio buttons, and more. Users can easily add these elements to their forms and customize them with labels, default values, validation rules, and other properties.
Once a form has been created, you can integrate it in your automations as a form (using the Show Form activity) or as a callout (using the Show Callout activity). You can define triggers for when the form should be displayed, such as when a certain activity is executed or when a specific condition is met. You can also specify what data should be passed between the form and the workflow, enabling bi-directional communication.
To learn about the components and controls of a Form visit the Form Builder page, and learn how to build your first form with the Building your first form tutorial.