Query forms

<< Click to Display Table of Contents >>

Navigation:  Bizagi Studio > Process wizard > Define Forms > Where to create Forms >

Query forms

Overview

Bizagi allows the definition and customization of special forms to consult information of ongoing and closed cases, as well as information stored in specific entities. With the search results of these queries you can create useful analysis reports. These special Forms are known as Query Forms.

 

The controls included in Query Forms serve as search criteria. They can be defined to perform powerful searches over created cases or over specific entities (Master and Parameter). Your search criteria can be business data and it can also be general process information (case creation date, creator user, case state, etc). You can customize the search criteria within ranges (for dates or numbers) and to be exact or approximate (for texts), etc.

 

Query10

 

Query Forms are related to two types of queries:

 

Process Queries: these are the queries executed over ongoing or closed cases.

In the Forms related to Process Queries you can include search criteria associated to the Data Model (business data) and Process filters (information not stored in the data model like the case creator, the case number, etc.)

Entity Queries: allow searching for information stored in specific entities (Master or Parameter), regardless of the processes they are involved in.

Entity Queries enable end users to look for information, for example, about Customers, Products, not related to particular cases but to their behavior i.e., business information. The Forms related to Entity Queries can include controls associated to the specified Entity. Process filters cannot be applied to Entity Queries (since they do not bring cases' information as the Context is not the Process entity).

 

Please refer to the following link to learn how end users execute Queries.

 

Process Queries information and tips

 

The Forms related to Process Queries are available for Process Queries exclusively. They contain special controls and properties that are only required in Queries. Thus, they are not available to be used as Process Forms.

 

By default all Queries created are shown in the Work Portal. If you need to hide a Query form you can change the Authorization settings and select a role that no user has. For more information refer to Queries' Work portal security.

 

Controls included in Queries serve as search criteria. When end users select a value for a control, Bizagi will look for cases where the attribute related to that control contains that value.

 

Controls included in Queries can also be used as result criteria. Every control in a Query has a check-box in front. If end users select the check-box, the control will display in the search results as a column.

 

QueryForms3

 

You can define queries to display search results for all the existent cases that meet specific criteria or only for those cases in which the logged end user has pending activities. To define this behavior, Query Forms use the Search for all Users property.

oSearch for all users enabled: the Process Query search results will display all cases that meet the criteria, regardless who is the allocated user.

oSearch for all users disabled: the Process Query search results will display only the cases that meet the criteria that are allocated to the logged user.

 

 

QueryForms1

 

 

There are some controls that are not allowed in the query form. Therefore they will not be displayed when a new control is selected for the Form.

These following are the controls that ARE SUPPORTED: Cascading combo, Combo, Date, Label, List, Money, Number, Radio, Suggest, Table, Text box, Yes/No.

 

Query Forms can include search criteria from tables (Collections). The actual table will not be available to be included. You can drag and drop the collection's attributes as regular attributes. These controls will be available as searching criteria exclusively, that is, the collection's information cannot be included as a result of the query. Note in the image below that the control from the table has no check-box in front to select as result.

 

QueryForms14

 

 

 

You can use nested (or reusable) Query Forms, if the form you are nesting is also a Query form. That is, in order to include a nested form in a Query it is necessary for that from to be also a Query.

Since all query forms are displayed in the Work Portal by default, the Query forms that are used only as nested queries can be hidden selecting the Only nested query property.

 

QueryForms18

 

Process Queries have special controls that serve as search criteria, additional to the business data, to enhance the performance of the queries. These special controls are found below the Data model attributes:

oProcess: include Application, Process, Task  and Cases controls.

oUsers: include Creator, Current and Previous users.

 

QueryForms2

 

note_pin

We recommend using the Process control as a filter to define each Query specific on a process.

To do so, include the Process control. In the Advanced tab select the Default value. This way you are defining a filter to search for that specific process chosen.

Define the control as not editable to avoid users from changing the filter.

 

 

QueryForms28

 

Text Controls can be defined to be searched with an approximate or an exact match.

oExact: The text has to be written exactly as it was entered for Bizagi .

oApproximate: End users can type a part of a string and Bizagi will display all cases containing it.

 

QueryForms4

 

Numerical and Date controls can have lower and upper limits to search for ranges.

Select whether the control is the lower limit (from) or upper limit (to). In this case, the same field is called on twice in the same form, and the display name is changed to indicate the initial and final range, respectively.

 

 

QueryForms27

 

 

 

When you change the query's name it will not be automatically updated. To see it click the Refresh button on the ribbon.

 

When a process is cloned the new process will be related to THE SAME query, not a new one. That is, queries are inherited, not duplicated.

 

Once Queries have been deployed to the Production environment, and to guarantee their correct performance, they will not be available to edit or delete. If new queries are needed, you can create new ones and associate them.