7.x Documentation

features description for

Query based content

A report may also contain chapters that are based on a query (or the results from the query builder). Here is an example from our demo model. We want to generate a report with the following structure, as shown on a special handbook diagram:


First, we want to generate a list of all processes of “process group diagrams”. For example, such diagrams as “(RACI) After Sales Process”:


We have created a query “process group diagrams” using the Query Builder, which creates the list with the names and the diagrams ID: 


Then we want to list all process objects with some of their properties for each “process group diagram”. We have created another query “processes of a process group.” The query uses a parameter to list all the objects that are used on diagrams with the ID of the query “process group diagrams”.


Finally, we want to list all child diagrams describing relevant processes using the RACI method. The query “Activities responsibilities” also includes a parameter to list only those objects which are used with the corresponding ID on the RACI diagram. You can enter in the parameter “ID1” the name of the RACI diagram.


Now we can define a query-based report in Document Composer - Wizard. The structure of the report is taken from the special handbook diagram. For the chapter “Process Group diagrams”, we activate the tab “Query-based content”. Then we select a base query on which our report will be based. In our case it is the query “group process diagrams” that lists all the diagrams with processes: “(QM) 0. developing and implementing a QM-system”, “(RACI) After Sales Process”, “sales”.


Important condition: only the queries listing diagrams (and not objects) can be used as base query, i.e. those which have the source type “Generic diagram” in the Query Builder.


We activate in Document Composer - Wizard the following options:
• Create a report series
This option allows you to generate multiple outputs of the same report, each with different values or content. Each report contains a diagram of the base query and all data from the subordinate queries. The structure of each document will be the same here, only the content will be diagam-specific to each report. In our example, we get 3 reports: the first with the diagram “(QM) 0. developing and implementing a QM-system”, the second - “(RACI) After Sales Process”, the third - “Sales”. If this option is disabled, we only get one report with all these contents in serial arrangement.
• View as tree diagram 
This option not only allows you to export the basic diagram, but all its children diagrams; with the levels option you can define how many levels should be published. We thus become the following diagrams tree for the diagram “(RACI) After Sales Process” in the report: 


and for the diagram “Sales” another tree:


If this option is disabled, only the parent diagrams, i.e. only the first level, will be added to the report.
In the lower window you can add items similarly to the object-based content (see separate chapter paragraph types): text block diagram, query, page/section break.

Here is an example:


  1. Text Block: contains columns from the base query, in our example “Process group diagrams”. This query consists of two columns: “Diagram Name” and “diagram ID”. One of these columns can be added to the report.


  1. Diagram: adds a diagram image to the report that is either taken from the base query or from the tree of the diagram of the base query, when the option “View as tree diagram” is enabled.
  2. Query: You can add two types of queries:
    a) ordinary query
    b) query with parameter (for this purpose see the Query Builder Manual). In our example, we have two queries with parameters: “processes of a process group” and “Activities responsibilities”. If a query with parameters is used, then the DocumentComposer will analyze all the diagrams added to the report and use their IDs as a parameter in the query. As a result we will get a report with queries showing specific data for each diagram data; for example, with the activities and roles that are used on each RACI diagram.
    Here you can see the structure of our sample report for the diagram “(RACI) After Sales Process”:


  1. Page/section break: You can add a page or section break within the Document Composer Reports.

1.You can activate the “Query-based content” in a DocumentComposer report for several chapters. However, it is only possible for parallel chapters and not for (interconnected) subchapters. 
2.The option “Create a Report Series” can be activated only once per report. Thus a series report cannot be published in a series report.