Custom Report Window (Query tab)
When creating, you can specify two types of parameters before running a report:
- Search Parameters
Use these to filter the SQL results. Data View result rows that do not match the filter will not be sent from Unifier to BI Publisher/Oracle Analytics Publisher.
- Additional Parameters
Use these to pass additional parameters for BI Publisher/Oracle Analytics Publisher to consume at runtime. All values are sent from Unifier to BI Publisher/Oracle Analytics Publisher for further operation. See Parameters tab below.
Search Parameters
Search parameters allow the report runner to filter the data that gets sent to BI Publisher/Oracle Analytics Publisher. For example, a Contract Report may need to be filtered by Vendor or Contract Type. A Ball-in-court report may be filtered for a specific task assignee, or task type.
At runtime, the report runner can select or multi-select from a list of values based on the search parameters specified in the report configuration. This means that Unifier basically runs the Data View before the report is run to give the report runner a list of the SQL results. He or she can then select or multi-select values from this initial run to filter what will appear in the report output.
On this tab, you can add query parameters to the configuration. The query parameters are created on the columns of the main view, selected for the Custom Report. At runtime, these parameters appear in the Search Parameters block.
To add query parameters to the custom report
- On the Custom Reports window, click the Query tab.
- Click the Add button. The Add Query window opens. Complete the window:
- Element Name: Click the drop-down list and choose from the elements (all columns from the main view).
- Label: Enter a label to use for the Element Name. This label appears to the user at runtime.
- Operator: Select the appropriate operator to use for the query. The operators will depend on the data type of the element chosen.
- Source Type: This is the source of the value. Choose one of the following:
- Data Definition: Lets you choose a data definition. The following field becomes available:
- Select Definition: Select from the drop-down list. The list displays data definitions defined in the company that apply to the type of element chosen. (For example, if you choose a drop-down [pull-down] or radio button, the data set values defined for the data definition will be displayed to the user at runtime.) This lets you use existing data definition values, rather than entering them manually (see Ad Hoc below).
- View: Lets you compare columns in your current view against another view chosen here. The following fields become available:
- Select View: Lists all published data views. Choose the view to compare.
- Value Column: Lists the columns for view chosen in Select View. This is the column that will be compared.
- Label Column: What you choose here will be displayed to the user at runtime.
- Context Sensitive: If this check box is selected, the results will automatically apply the filter for project_id at runtime (results will be for the current project only).
- Ad Hoc: Allows user to select values in User mode from selection list. If you choose this option, you must specify the list of values here. This is similar to defining a data definition data set.
- Click the Add button. The Ad Hoc window opens.
- Click Add. A new row is added.
- Enter a Value and Label.
- You can modify the query parameters by doing the following:
- Delete a row by selecting it and clicking Remove.
- Modify parameter by selecting a row and clicking Modify.
- Change the order of the query parameters (as they appear in User mode), by selecting a row and clicking Move Up or Move Down.
- When done, click Apply to save changes. You can click OK to save and exit, or click another tab to continue to define the configuration.
Last Published Tuesday, December 12, 2023