Using Form Specifications

You can use form specifications to help the agent verify forms. Normally, the agent infers the expected behavior of forms. Form specifications allow you to more precisely state requirements for forms and form fields such as each field name, label, data type, required/optional setting, tip text, min/max length or value, and more.

Detailed Steps

• Create a form specification. If you have existing form specifications, we have services to convert them to the format used by ASTA.
• Upload form specification. Upload your specification using the Form Specs page.
• Write a flow. Create a flow that navigates to your form and opens it.
• Run the flow. Run the flow with the "Stop run after flows" option off. The agent will take over form spec testing after your flow.

Form Specification Format

Forms are specified using JSON in the following format:

{ formTitle: "string", formId: "string", formVersion: "string", fields: [ { fieldNumber: "string", fieldLabel: "string", fieldId: "string", required: true | false, minimumOccurences: number, maximumOccurences: number, agencyFieldName: "string", fieldType: "string", globalLibraryFieldName: null, fieldTypeSource: null, dataType: ["string" | number], listOfValues: "string", minCharsOrMinValue: number, maxCharsOrMaxValue: number, fieldImplementation: [" Button | TBD "], helpTip: "string", mandatoryMessage: "string", validationMessage: "string", } ] }

Form specifications can also be tailored to your specific forms through customization services.