Sigma FAQs
- Vaishnavi Sridhar (Unlicensed)
- DevaDarshini.S
- Ravikumar Babu CTOO (Unlicensed)
Not enabled as of now. It is always turned ON.
Yes.
Yes. The App Designer feature in the 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.
It is currently on road map. A filter shall be enabled to generate older reports.
HTML editor is provided in the design area to modify your reports.
Record is a combined selection of rows in the table.
Object is an individual selection of an item in the table.
A dummy column which can be used for computation purpose to deduce a value and use in report. Refer Displaying Collated Headers in reports for more information.
Yes, based on system filter and default filter.
You can add columns without limits, however column length should be specified appropriately to avoid error scenarios.
For example, if your specify 10 characters for an address column, the entry should not exceed it.
When the data is updated, it gets reflected when you run the report. However, the structure of the database should not be changed.
Currently not supported.
Currently the End of Report option is enabled for all. You can however modify the End of report message.
You can combine multiple report outputs into single file using the Group Reports feature. Refer Grouping Reports in Sigma for more information.
Yes. Refer Linked Widgets in Report Filters for more information.
Yes. Refer Sub-Reports for more information.
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
- 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
- If the latest release revision is 19.1.7.11 19679 and above, refer to the following steps:
Perform the following steps to use the CT release as-is without the need to update the CanvasApplicationContext.json file in the CTResources.jar.
- Update web.xml in Canvas Studio WAR
File Location: ...\webapps\ctmodelhouse\WEB-INF\web.xml
The following snippet provides the sample values of the necessary elements and attributes that are to be configured within web.xml.
<context-param> <param-name>appId</param-name> <param-value>MODELHOUSE</param-value> </context-param>
The param name should remain unchanged. Only "appId" should be used.
If the context-param attribute is already present in the web.xml for a different param-name, the new context-param attribute has to be added after that to configure the value of appId.
Refer to the following snippet for sample values of the necessary elements and attributes that are to be configured within web.xml.
<context-param> <param-name>ModelHouseInitializeBundle</param-name> <param-value>MyImplementation</param-value> </context-param> <context-param> <param-name>appId</param-name> <param-value>MODELHOUSE</param-value> </context-param>
The following snippet provides the sample values of the necessary elements that are to be configured within context.xml if file upload is not working for Sigma:
<Context allowCasualMultipartParsing="true">
Copyright © Intellect Design Arena Limited.
All rights reserved. These materials are confidential and proprietary to Intellect Design Arena Limited and no part of these materials should be reproduced, published in any form by any means, electronic or mechanical including photocopy or any information storage or retrieval system nor should the materials be disclosed to third parties without the express written authorization of Intellect Design Arena Limited.