10 June 2009 - 3.0-beta-2 |
![]() |
|
The form editor attempts to dynamically build a user friendly input form from the underlying XML Schema definition for the current request message. The following screenshot shows the form created for one of the PayPal API calls;
The toolbar contains buttons to Validate and Clear the current form. Clear will recreate an empty underlying request contain only required elements. Validating will show a clickable list of errors below the editor that can be used to move focus to the corresponding field that caused the error:
By default, the editor creates fields for all elements and attributes in the underlying schema for those structures that are available in the underlying message, which can both be useful for inspection purposes but also annoying for testing purposes. Therefore, the toolbar contains a "View Type" combo which offers the following options:
For example the following shows the above request with the "Data" value selected
This setting will be remembered between editing sessions.
The Form Editor uses validating editors for all native XML Schema data types and provides popup dialogs for easy entry of dates, durations, etc.
The editors will discard values not allowed by the schema, if it is still required to enter "invalid" values the right-button menu for these fields contains a "Set Value" action for entering any text into the field:
The soapUI Pro Form Editor supports most commons XML Schema constructs but may have trouble displaying, editing, or validating more complex schemas. Therefore, it is advisable to initially double check the XML generated by the editor in one of the other editors. Since it is our ambition to fully support XML Schema, please let us know if you have schema constructs that are giving you or the editor trouble...
The following constructs should currently work fine:
A '*' after a field name denotes that it is required. All fields can show a small green question-mark which will show documentation information from the associated type in a tooltip.