Sigma FAQs

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.

Sigma Studio facilitates quick configuration of reports using single-click and drag-and-drop interface. Sigma Studio users are expected to have knowledge 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.

You need to clear online Sigma assessment with minimum 75% score. Reach out to ravikumar.babu@intellectdesign.com for training and assessment.

The assessment will have 30 questions (multiple-choice and fill-in-the-blank). The duration for assessment is 30 minutes. A maximum of three attempts are provided to clear the assessment.

Sigma Studio is for configuring the reports and their functional data entities. Sigma Application is a portal for report consumers to generate and schedule reports that were configured in Sigma Studio. Typically, Sigma Studio is used by the operational or IT staff who have access and aware of the functional data entities and need to create reports for end-users. Sigma Application is used for end users (report consumers) who need to generate ad-hoc reports or schedule reports. Sigma Application can be used by operational staff who need to generate reports on behalf of customers. 

Sigma enables generation of reports in following formats - CSV, DOCX, HTML, PDF, TXT, XLS, and XML.

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.

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).

• WTRN0006W: Transaction {0} has timed out after {1} seconds
  
  
  For example:
  

  WTRN0006W: Transaction 00000188D7CBD648000000455D953708CCA97D4013E3EDB45FD179E3597A7D478393378300000188D7CBD648000000455D953708CCA97D4013E3EDB45FD179E3597A7D478393378300000001 has timed out after 120 seconds

  Solution: Increase the total transaction lifetime timeout and maximum translation timeout in seconds. These settings can be updated through the WebSphere Application Server console, using Servers > Server Types > WebSphere application servers > server_name > [Container Settings] Container Services > Transaction Service
  

  Reference links : https://www.ibm.com/support/pages/troubleshooting-java-transaction-service-jts-problems

  https://www.ibm.com/docs/en/was-nd/8.5.5?topic=server-transaction-service-settings
  
  
• WTRN0037W: The transaction service encountered an error on an xa_recover operation. The resource was com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl@1f5b7ee3. The error code was XAER_RMERR.
  
  
  Solution:
  Run the following commands as user SYS:

  grant select on pending_trans$ to <user>;
  grant select on dba_2pc_pending to <user>;
  grant select on dba_pending_transactions to <user>;
  grant execute on dbms_system to <user>;  //If using Oracle 10.2.0.3 or lower JDBC driver 
  grant execute on dbms_xa to <user>; //If using Oracle 10.2.0.4 or higher JDBC driver 

  In the above commands, <user> is the username configured in the Oracle datasource's authentication alias.

  Reference link : https://www.ibm.com/support/pages/exception-occurs-during-recovery-oracle-database-transactions

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.

No. Sigma fetches the functional data from the configured data entities at the time of report generation.

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.

Sigma Studio provides following integration options for fetching functional data - Database, JNDI, REST Web Services, Excel Import, and Google Sheets.

Yes, in Sigma Studio you can create datasource with SQL statements. Alternatively, you can create datasource for DB tables, views and stored procedures.

Yes, you can execute stored procedures as pre-hooks before a report is generated. Refer Using Stored Procedure as pre-hook for Creating Reports.

Using Sigma Studio you can configure the following for report columns:

• Column positions
• Column alignment (by default number/amount columns of float data type are automatically right-aligned)
• Column width
• Column data aggregation (average, count, maximum, minimum, and sum)
• Display names for columns
• Column visibility
• Column datatype
• Date and time, currency formats

Not enabled as of now. It is always turned ON.

Yes. Sigma Studio provides following options for aggregating report columns' data:

• Average
• Count
• Maximum
• Minimum
• Sum

Yes.

Yes. The App Designer feature in the Sigma Studio can be used to create the chart as a individual app (widget). The Template Designer in Report configuration can be used to map the chart to the report. The generated report displays the chart and the report data. Refer Improve Business Reports with Charts.

Yes. Password protection can be enabled for PDF, DOCX, and XLS formats. Refer Configuring Password Protection for Reports for more information.

In Sigma Studio, the HTML editor in Template Designer can be used to design the reports. Refer Template Designer Configuration.

Record is a combined selection of rows in the table.

Object is an individual selection of an item in the table.

A custom column that can be used for computation purpose to deduce a value and use in report. Refer Adding Formulas in Data Aggregator for more information.

Yes and it achieved in two ways:

• Using the CASE WHEN expression in the SQL select statement itself.

OR

• Using the Java Expression Language (JEXL) conditional statements in the Derived Column field in Sigma Studio.

Yes, based on system filter and default filter.

You can add columns without limits. However, the column length (width) must be specified appropriately to avoid error scenarios.

For example, if your specify 10 characters for an address column, the values for that column should not exceed that limit. Also, depending upon the number of columns, the report page size and orientation needs to be configured accordingly.

When the data is updated, it gets reflected when you run the report. However, the structure of the database should not be changed.

Yes. Open the report in Sigma Studio, in the Report Parameters tab use the Generate output for no data drop-down to control report generation.

Currently the End of Report option is enabled for all. However, you can modify the End of Report message in the Add Labels screen with report configuration.

Yes. Refer Enabling Drop-downs for Report Filters for more information.

Yes. Refer Sub-Reports for more information.

Refer the CT_DATA_SOURCE_METRICS table, to view the Data builder and SQL query data source performance metrics collection in detail:

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.

Report consumers can perform the following on Sigma Application (portal):

• Generate and download reports
  • Choose report formats from among those configured
  • Change column positions
  • Add or remove configured columns
  • Change column-level configurations
  • Change report orientation and page size
  • Use sort and group by columns if configured
  • Choose contacts and notification channels
• Save base reports with customizations
• Regenerate executed reports
• Schedule reports
  • Configure multiple schedules for a report
  • Configure retry frequency in case of failures
  • Pause, resume and delete report schedules
• Create group reports

In Sigma portal, on the Generated Reports tab, you can use the 24 Hours, 3 Days, and 7 days filters to view older reports.

Once a report is generated successfully, it can be downloaded from the 'Generated Reports' tab in Sigma Application.

You can combine multiple report outputs into single file using the Group Reports feature. Refer Grouping Reports in Sigma for more information.

Report consumers can schedule reports in the Sigma Application (portal) in the following frequencies:

• Minute
• Hourly
• Daily
• Weekly once
• Monthly

Refer Scheduling Reports for more information.

Yes. In Sigma Application (portal), multiple schedules can be set for a report.

The logs for the Report Schedule is displayed in ctschedulerLog.log file in Sigma.

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.

When report generation fails in Sigma Application (portal), users can view the failure reason upon which they can take further action. Sigma also offers options when scheduling reports to specify the  number of times for retrying report generation in case of failures.