studio
2023.4
false
- 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
- Trigger-based attended automation
- Overview
- Contact Centers and Trigger-based Attended Automation
- Creating a guided product tour
- Designing validation for existing apps
- 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
Designing validation for existing
apps
Studio User Guide
Last updated Nov 4, 2024
Designing validation for existing apps
To enhance the user experience and productivity, you can use the Trigger-based Attended Automation solution to design custom validation for existing applications. This tutorial demonstrates how to design validations using callouts, forms, and triggers, for a smooth user experience while using the UiDouble sample application.
The steps below show an overview on how to create validation for the UiDouble
application:
- Create a callout with only a Label/Header component, meant to display the validation message at runtime (callout.uiform).
- Create a general workflow that
validates the value typed in the On Cash In and On Us Check UI
elements (validate.xaml). Whenever the validation condition is broken (in
this example,
elDouble > minValue
), a callout with the appropriate message (for example,text
) shows. - Create a trigger workflow to validate the data inside the On Us Check field. It should contain an Application Event Trigger activity and an Invoke Workflow File activity. This means that when the user adds data into the field, the validate.xaml file is invoked to perform validation (on us check changed.xaml).
- Create a trigger workflow to validate the data inside the Cash In field. It should contain an Application Event Trigger activity and an Invoke Workflow File activity. This means that when the user adds data into the field, the validate.xaml file is invoked to perform validation (on cash in changed.xaml).
- Create another trigger workflow that validates both fields, when user clicks Accept. You can achieve this using an Application Event Trigger activity. If both fields are valid, then you can replay the user event that clicked the Accept button (on accept clicked.xaml).
Learn how to create validation for the UiDouble app, using this sample project as inspiration. You can download the UIDouble application here.