General
Expand | ||
---|---|---|
| ||
Reports are configured in Sigma Studio by operation or IT users. Report consumers log-on to Sigma Application (portal) and generate or schedule the reports that they have access to based on their entitlement. |
...
Expand | ||
---|---|---|
| ||
Sigma Studio enables easy facilitates quick configuration of reports using single-click and drag-and-drop interface. Users of Sigma Studio users are expected to have knowledge or and access to the functional schema or web services so that they can configure the data entities required for the reports. Report consumers can easily access the reports they are entitled to view in the Sigma Application (portal) and can either generate ad-hoc reports or schedule reports. |
...
Expand | ||
---|---|---|
| ||
Sigma enables generation of reports in following formats - CSV, DOCX, HTML, PDF, TXT, XLS, and XML. |
Expand | ||
---|---|---|
| ||
The generated reports are stored in the server where Sigma is deployed. However, you can specify custom location to store the reports, such as a specific target folder, FTP directory or cloud storage. |
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Multiple emails get triggered even though only one entry in the table (OD_PENDING_MAIL) from where CT picks up records to be sent as email. In such cases refer these kind of errors found in the SystemOut.log (WebSphere log).
|
Sigma Studio (for Configuring Reports)
Expand | ||
---|---|---|
| ||
No. The report designers (Sigma Studio users) can configure or enable specific formats for each reports. Report consumers or generators (Sigma Application users) can generate the reports in the enabled formats only. |
Expand | ||
---|---|---|
| ||
No. Sigma fetches the functional data from the configured data entities at the time of report generation. |
Expand | ||
---|---|---|
| ||
The users and roles must be defined in the authentication and authorization system. The roles must be re-defined and mapped to the entitlements in Sigma Studio. The entitlement must be configured for the reports. Sigma provides role-based access to reports in Sigma Application based on the entitlements configured for the reports. When users log-on to Sigma Application (portal), they get to see the reports that they are entitled to view. |
...
Expand | ||
---|---|---|
| ||
Sigma Studio provides following integration options for fetching functional data - Database, JNDI, REST Web Services, Excel Import, and Google Sheets. |
Expand | ||||
---|---|---|---|---|
| No. Sigma fetches the functional data from the configured data entities at the time of report generation
| |||
Yes, in Sigma Studio you can create datasource with SQL statements. Alternatively, you can create datasource for DB tables, views and stored procedures. |
Expand | ||
---|---|---|
| ||
Yes, you can execute stored procedures as pre-hooks before a report is generated. Refer Using Stored Procedure as pre-hook for Creating Reports. |
Expand | ||
---|---|---|
| ||
Using Sigma Studio you can configure the following for report columns:
|
...
Expand | ||
---|---|---|
| ||
Yes. Password protection can be enabled for PDF, DOCX, and XLS formats. Refer Configuring Password Protection for Reports for more information. |
Expand | ||
---|---|---|
| ||
In Sigma portal, on the Generated Reports tab, you can use the 24 Hours, 3 Days, and 7 days filters to view older reports. | ||
Expand | ||
| ||
In Sigma Studio, the HTML editor in Template Designer can be used to design the reports. Refer Template Designer Configuration. |
...
Expand | ||
---|---|---|
| ||
Yes and it achieved in two ways:
OR
|
...
Expand | ||
---|---|---|
| ||
Yes. Refer Sub-Reports for more information. |
Expand | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||
Refer the CT_DATA_SOURCE_METRICS table, to view the Data builder and SQL query data source performance metrics collection in detail:
|
Expand | ||
---|---|---|
| ||
Report bursting schedules are executed like a normal report scheduling. Pausing the report-bursting process essentially puts it on hold. The process stops at the point where it was paused. If report bursting is resumed, it fires the missed schedules once and continues with the next upcoming instances based on the given frequency. For example, when a report bursting is paused on August 1 and resumed on August 15, it kick-starts the report bursting on August 15 and continues with the next upcoming instances based on the given frequency. |
Sigma Application (Portal for Generating Reports)
Expand | ||
---|---|---|
| ||
Report consumers can perform the following on Sigma Application (portal):
|
Expand | ||
---|---|---|
| ||
In Sigma portal, on the Generated Reports tab, you can use the 24 Hours, 3 Days, and 7 days filters to view older reports. |
Expand | ||
---|---|---|
| ||
Once a report is generated successfully, it can be downloaded from the 'Generated Reports' tab in Sigma Application. |
Expand | ||
---|---|---|
| ||
You can combine multiple report outputs into single file using the Group Reports feature. Refer Grouping Reports in Sigma for more information. |
...
Expand | ||
---|---|---|
| ||
Yes. In Sigma Application (portal), multiple schedules can be set for a report. |
Expand | ||
---|---|---|
| ||
The logs for the Report Schedule is displayed in ctschedulerLog.log file in Sigma. |
Expand | ||
---|---|---|
| ||
Sigma Application (portal) users can choose either SMS or email notification and select contacts or contact groups that must receive the notification when the report is generated. The contacts and contact groups must be defined in Sigma Studio. |
...