Add custom queries xml files (.ccq files) to application or reporting file folders.
The custom menus will appear under the Custom Views menu in the main toolbar.
The custom view configurator allows you to create custom query views and menu's.
The custom view configurator is in theConfiguration menu.
Click New configuration to create a new configuration file. For maintaining an existing configuration file click on Open and browse for the appropriate file (extension is .ccq). The default path where configuration files are stored is the reports folder.
Click the New button on the tab to create a new custom view.
The system asks for a key that will identify the data for this view.
Click OK to confirm the creation of the new view.
Note: To change the view's unique key select the view concerned and click on Edit.
Enter a new unique key and click OK to confirm.
A new row in the grid display is shown with an automatically generated display name.
The display name can be changed and a description can be added (these fields are mandatory).
Double click the row to display the view data. (The General, Bindings and Security tab).
To save the newly created view click the Save button in the toolbar.
The file should be saved in the reporting path or the application path in order for the menu's to appear in the Custom Views menu. In case the file is saved in another folder it does not appear in the Custom Views menu, however it can be manually opened using the Open button.
The application path is the path that has the application executable.
Display query : when checked the sql statement is shown when the view is selected from the Custom Views menu.
Menu text box: allows to add a menu that is displayed in the Custom Views main menu in Accelerator.
A menu is a string of text, a sub menu is defined by adding '\' between the submenu and its parent.
(For example : Domains Menu\Domains Selection will add the Domains Selection sub menu)
SQL textbox: is used for defining a SQL select statement or call to a stored procedure.
The Test view button in the toolbar allows to directly test the appropriateness of the SQL statement or the views' output.
A binding indicates which key object key should be used to open the key object.
The key object field is the key that is used to open the key object, when a row is double clicked.
The bind column can be prefixed with "ZZ" so it won't show in the grid when opening the custom query (this prefix can be used for any column that should not be displayed).
When multiple columns are bound to the same key object ButtonText can be used to change the caption of the buttons shown in the popup (which is only shown when multiple bindings exist) when double clicking a row. In case ButtonText is left empty (default) then the key object description is used.
Example:
In the query "Select Risk AS ZZRisk from dbo.rrProcessProcessRisk", Risk is the key object that will open the risk related to the process node.
The ZZRisk alias will hide the key in the selection of rows in the grid.
In the Binding tab the Key object field will become Risk and the Bind column field will become ZZRisk
On this tab user groups can be selected that are allowed displaying the view in the Custom Views menu.
These are the same groups a user can have selected in the User Management module. In case no user groups are selected then everyone is allowed to display this view.
Click the Open button on the toolbars menu to select a custom configuration (.ccq file).
The views contained are listed in the grid, double click the view to show its attributes.
Custom views can be found in the Custom Views menu that appears automatically when custom views are available and
when they are within the user's authorizations.
The Custom Views menu only appears on the main toolbar when a custom configuration file id found in the reporting path or the application path.
The user must be in at least one user group that appears in the ccq file's security.
A graphical representation of the main tables related to Authorization Organizer and Control Organizer modules can be found here:
This document is up to date with version 11.1.10.20 of CSI Accelerator