Imagine you use a case management system that looks something like this:
Although these are all free-form text fields, from experience you actually know that there are some constraints:
Issue Type: is always going to be one of "Pricing", "Product", or "Documentation"
Reporter: is always going to be yourself and your own email
Description: your company has a standard template for these they want you to follow
Given this setup, there is a lot of duplicate typing you have to do every time you enter a new case. You can simplify this using Text Blaze snippets. However, normally you would need at least three different snippets to handle this form (one for each of the Issue Type, Reporter and Description fields)
Fortunately, there is a better way: Text Blaze's autopilot feature.
Text Blaze has three powerful commands that form the basis for Autopilot: key, click and wait.
The key command will simulate a key press in the web page. The most common use case for this is to tab between fields in the page.
The click command will click the currently focused item. This is useful if you have tabbed to a button element. For example if you have tabbed to the submit button in the Case form, the click will trigger the submission.
The wait command will delay for a set time period before continuing. This is useful if you need the page to complete some action (like loading some data) before continuing with your script.
Automating the Case
Let's attempt to automate the Case form. We will use both autopilot commands and Text Blaze forms to turn this into a streamlined workflow:
Anything that depends on the specific order of fields on a page is sensitive to changes in that page. If you use the autopilot feature, you may need to make changes to your snippet when the underlying page is redesigned or modified.