Understanding Connected Query Manager
Connected Query Manager enables a report developer to create a new connected query, edit an existing connected query, copy existing connected queries, and delete a connected query object, as well as run connected queries in three modes:
-
Preview XML
-
Run to window
-
Schedule
The queries you defined in a connected query must exist as PeopleSoft queries in the database. In addition, you cannot specify a child query in a connected query that is defined in a union.
Connected Query Manager supports XML output format and user-defined output format (XFORM, which triggers a transformation XSLT). Connected Query structure consists of a set of PeopleSoft queries that are linked by related fields. No limits exist for the number of fields being linked between two queries. Parent and child pairs of queries can be linked together using sets of correlated fields, though those linkages are not required.
Each query being selected in a connected query structure has a set of image icons, which enables you to perform various actions:
| Term | Definition |
|---|---|
|
|
Click the Insert Child Query icon to insert a new query as a child of the selected query. |
|
|
Click the Insert Sibling Query icon to insert a new query as a sibling of the selected query. |
|
|
Click the Delete Query icon to delete a selected query. |
|
|
Click the Select Related Field icon to open a related field selection section. |
|
|
Click the Open Query icon to open a selected query in Query Manager in read-only mode. |
Note:
While deciding which tool to use for reporting purposes, report developer should consider using a single query with joins and unions first. Using Connected Query could affect the performance of the reporting application.
The main contributing factor to the Connected Query performance is the number of nested levels. Application developer should try to minimize the depth of nesting in a Connected Query structure. Another contributing factor is the number of rows being returned from each query. To achieve a better performance, queries that are positioned higher in a Connected Query hierarchy should be limited in the number of rows being returned. This limitation could be achieved by means of using filtering in parent queries.