The Report Parameters Editor form is used to configure reports on an individual basis. These reports display query results found in the fields of tables within the data source.
Reports are given access through the default connection key. If required, they may also be configured using an alternate connection key. As long as the alternate connection key has been defined in the Connection Key Management form, it will be available in the Alternate Connection Key list. See Alternate Connection Key Properties group for details about alternate connection keys. In Release 6.0 of GNA, there is enhanced support for SQL Server Reporting Services (SSRS)™. SSRS reports and Crystal Reports™ are configured in the OpenForms General Settings form, see OpenForms™ General Settings for details.
Intelligent Scanning in Reports Editor
There is an underlying intelligence in the functioning of the Reports editor. Both SQL Server Reporting Service (SSRS) and Crystal Reports reports are read, and the data sources are scanned.
Connection options to the database are by default specified as the current connection. If required, secondary sources can be selected from a list of alternate Connection Keys. During the initial scanning phase, if a report is determined to be invalid, i.e. incompatible, a warning is displayed in the form of a window with a list of the offending reports.
NOTE: When there is no backwards compatibility with a report, the default connection setting will be used. |
Details of the Report Scanning Process
When the Report Editor is launched, each report that is selected from the List of Reports list is scanned. The report connection key is tested. When the system encounters either a Crystal Report or an SSRS report that is not associated with a Govern connection key, the system will ask to associate the report with…:
- The current Connection Key (Default) OR
- The user can see the path to the data source, and may select a connection key from the list of available Alternate Connection Keys.
During the “Database Verification” process…
After performing an update / general maintenance, or defining database connections, running the Database Verification process is recommended as it will update the database for access by Govern applications.When this process is run in GNA, during the Misc. Corrections phase a script performs the following:
- Conversion of Alternate Connection Key information (i.e. server, database names, etc.) into the Connection Key in the new table.
The following four (4) fields will be set to NULL:
- [DTSRC_SERVER]
- [DTSRC_DBNAME]
- [DTSRC_UID]
- [DTSRC_PASSW]
Note: In the SY_REGISTRY screen, four key names were removed,
- [DTSRC_SERVER]
- [DTSRC_DBNAME]
- [DTSRC_UID]
Record Set Key: This option provides the ability to run the report by dataset, e.g. current P_ID, current dataset, or database. In the drop down menu list, select the primary key that will be used by this report, otherwise the user will not be prompted to select a dataset for the report.
NOTE: A Record Set Key should be specified. |
The report dataset will be filtered with a list of values for the selected key.
Example: SELECT * FROM pc_parcel WHERE p_id = ‘123’ OR p_id = ‘456’ etc.
Report Criteria: Click Report Criteria (A) to display the editor. The Report Criteria Editor is used to configure prompts for reports that require user input. See Report Criteria Editor on page 85 for details on configuring prompts.
The report dataset will be filtered with a unique value for the selected keys.
For Example…
SELECT * FROM pc_parcel WHERE p_id = ‘123’
Criteria Key group
Add Criteria Key: Click Add Criteria Key to display the criteria key list; select one or more criteria to be added, click OK or Cancel.
Remove Criteria Key: Select a criteria key from the Criteria Key list and click Remove Criteria Key to remove it from the list.
Alternate Connection Key Properties group
Although database connection parameters are set in the Govern DeployEZ™, they can be overridden on a report by report basis. If required, each report can be configured with an alternate connection key.
NOTE: All settings made in this section override the current, default, connection key. Users should ensure that the alternate connection
key required has been entered in the Connection Key Management form. See The Connection Key Management form. |
Data Source: This is the path to the server that the report will be accessing.
Alternate Connection Key: Select an alternate Connection Key from the list.
Report Group
This parameter contains the Report Grouping for the Report Explorer in Govern.
Upper/Lower Level: Select configure these parameters to indicate the location of the report in the Treeview pane in Govern.
For Example…
When the following report, Mass App.- Inventory Report is configured to appear in the following Report Group; Upper Level: List & Reports, and Lower Level: CAMA. In Govern, the report will appear in the List & Report upper folder (A) and CAMA lower folder (B):
See Also
Report Criteria Editor