In the Query data window you can create mini databases – small tables with tailored translation information or mapping. The mapping can be used to check data, such as a call parameter having an approved value. You can also, from one or more given values for call parameters, look up and assign other parameters. Some examples:
From supplied zip code number, the IVR can set task and menu choice for region based routing.
From community ID or area code number, community name, task, menu choice, and fallback numbers are specified.
For phrase recording, phrase ID is set from supplied code.
The Query data window is opened from the Dialogue flows start view, using the 
button or the Ctrl Shift Q keyboard combination.
To look at and edit query data you require the Own dialogue flows access function.
Edit Input/Output data labels for query data
When you have selected a row in the table to the left you see the associated so-called data labels on the Query data tab to the right.
What you enter under Data label on the Edit input/output data labels tab is then seen on the Query data label as column headers, under Input and Output respectively. You can have up to twenty input parameters and twenty output parameters, and each string can have a maximum of 255 characters.
To change the relative order of the columns on the Query data tab, you select the parameter you want to move on the Edit input/output labels tab and then you click on the up or the down arrow. Save with OK.
Procedures
At the bottom left of the Query data window you find the 
Procedures... button.
Procedures is another name for calls to other integrated systems or programs, to fetch or send data from the IVR. A procedure can e.g. be to via a query object look up information about the caller from a CRM system from the Ano or CID parameters. (the calling customer’s telephone number or another identifier).
The Procedures window is used by the person who is creating organisation unique integrations between IVR dialogues and the various systems that can be connected to an ACE solution.
Existing procedures cannot be changed, only removed. Procedures used by any query object must, however, first be disconnected from their query objects before they can be removed.