Translating reports
A report can contain several elements that require translating in order to display the report in more than one language.
-
Database columns used in the report definition.
Translate database columns with the Language Editor in the Designer.
-
Display name/ReportAlias.
The report's display name used when a report is created as ReportAlias. The display name is entered in the report properties dialog. Translate the given text using the 
button.
-
Text elements on the report form.
Translate the text elements directly in the Report Editor with the Globalization Editor.
To translate all text elements in a report
-
In the report, select the report list and open it with double-click or with Edit from the context menu.
This opens the report form in the Report Designer.
-
Start the Globalization Editor.
-
Click on the 
button in the Report Designer toolbar.
- OR -
-
In the Report Designer’s properties view, select the report from the menu on the Properties tab and use Globalization Strings to open the Globalization Editor.
NOTE: You can only start the Globalization Editor from the Report Designer’s properties view if you have selected Professional. You can change the configuration type later in the edit view using the context menu in the property view.
-
Ensure that the Auto Localize Report on Run button is set.
This means the report is generated in the current language.
-
Enter a culture for the language using Add Culture and translate each entry.
To translate single captions
-
Select the report in the report list and open it with double-click or with Edit from the context menu.
This opens the report form in the Report Designer.
-
Select the caption on the report form.
-
Open the dialog box using the in the Report Designer toolbar.
-
Translate the text and confirm the changes with OK.
Related topics
Embedding reports in the user interface
In order to display a report in a One Identity Manager administration tool, such as Manager, you need to link in the report as a custom interface form.
In the Manager's info system, you can display reports that you create in the Report Editor as statistics. To do this, you must alter the Manager's user interface. The report opens when you double-click on the statistic's header.
To create a user interface form
-
In the Designer, select the User interface > Forms > User interface forms category.
-
Select the Edit form task.
-
Select the Form > Insert menu item.
-
Edit the interface form's main data.
Take the following cases into account:
-
Use the VI_Report form definition.
This form definition is configured for displaying in the graphical user interface and in web applications. You only need to set up one interface form for this. Which form template will be used to display the interface form is decided dynamically, depending on usage.
-
In the form’s configuration data, enter the name of the report to be run and the report parameters in the Properties section.
Syntax:
<DialogSheetDefinition FormatVersion="1.0">
<Properties>
<Property Name="ReportName">ReportName from the DialogReport</Property> table
<Property Name="ReportParameter.Parameter1">value1</Property>
<Property Name="ReportParameter.Parameter1">value</Property>
</Properties>
</DialogSheetDefinition>
Example:
<DialogSheetDefinition FormatVersion="1.0">
<Properties>
<Property Name="ReportName">CCC_Employee_by_Department</Property>
<Property Name="ReportParameter.UIDDepartment">%UID_Department%</Property>
</Properties>
</DialogSheetDefinition>
-
Assign the user interface form to the applications and permissions groups.
-
(Optional) Assign the user interface form to the object definitions.
-
(Optional) Assign the user interface form to the menu items.
Related topics
Generating and exporting reports on a cyclical basis
You can create customer-specific processes to control the creation of reports and perform the export on a cyclical or event-controlled basis.
You can use the ReportComponent process component to create reports and export them to different file formats. The following formats are supported: HTML, PDF, RTF, TEXT, XLS, TIFF, XML, CSV, XPS, DOCX,and XLSX.
To exports reports in CSV format, you can also use the ScriptComponent process component with the CSVExport or CSVExportSingle process tasks.
NOTE: Use the default report server as executing server in the processes.
Related topics
Adding custom tables or columns to the One Identity Manager schema
The object technology implemented in One Identity Manager makes it possible to add customer-specific columns and tables to the existing application data model at the database level. These are, therefore, available at the object level with all corresponding tasks. A custom extension to the system data model is not recommended.
Basic knowledge of the database system's SQL Server in use is a prerequisite for making schema extensions. It is assumed that you understand the concept and the architecture of One Identity Manager.
To implement a custom extension of the One Identity Manager schema, use the Schema Extension program. You can make the following extensions using the Schema Extension:
The Schema Extension program creates the schema extensions in the database and ensures that the necessary extensions are made in the One Identity Manager schema. The basic table definitions and column definitions of the custom tables are entered in the DialogTable, DialogColumn, QBMRelation and DialogValidDynamicRef tables. You must then adjust the properties in the Designer to the desired requirements.
The Designer contains a variety of consistency checks. Run these consistency checks and apply the repair methods after carrying out a schema extension and after making changes to table and column definitions. For more information about checking data consistency, see the One Identity Manager Operational Guide.
You cannot create custom functions, triggers, or database procedures with the Schema Extension program. If you need custom functions, triggers, or database procedures, add these to the database in a suitable program for running SQL queries. Keep to the following conventions for name database components.
-
Name begin with the CCC_ string.
-
All names are a maximum of 30 characters long.
-
One Identity recommends using UpperCamelCase as notation for the names.
Detailed information about this topic
Related topics
