Admin 

• An Elasticube schema sync fails if a Custom object is created in TeamConnect with Unique Code starting with numeric value.
  Tracking code: TC-24611
• When a user changes the ElastiCube in the Report Integration tool and clicks Update Report Integration, the system returns an error stating that one or more fields were left blank. If this happens, verify that the integration is shared with the same Sisense administrator you have listed in the Sisense.properties file (part of the Reporting Tool).
  Tracking code: TC-18188, TC-18576
• Upon initial setup of the report integration, a client ID and environment is entered. TeamConnect uses this information to create a unique identifier for users on the report server and the information must not be changed after it is saved in the Report Integration Tool.
• In the Report Integration tool, you must re-type any secured fields such as Password or SharedSecret when you are updating an integration.
• Each TeamConnect user with an automatically created Sisense account must have a unique email address per Sisense server. This means that an on-premise client with a single Sisense server cannot have a TEST ElastiCube  and a PROD ElastiCube with users with the same email. The second time an email account is used, the user will not be created automatically on the Sisense server.
  Tracking code: TC-16847
• Renaming a group with the special characters '#' and '& and then renaming it back to the original name does not delete the group in Sisense with the special characters.
  Workaround: Sisense admin can remove the additional group.
  Tracking code: TC-19343
• When editing a script for a widget, clicking the Apply button on the Edit Script window does not save the changes made to script. Workaround: After saving the script on the Edit Script window, refresh the page. Tracking code: TC-15263, Issue #55178
• If a user is logged into Sisense as an admin, the user must log out or TeamConnect uses that session. The user would recieve a "service not found" error or the dashboard shell appears but the data does not load. Tracking code: TC-21628
• Users who have been granted the right to Perform other Actions in System Rights are granted Designer reporting rights.
  Tracking code: TC-21483, TC-21483
• After the cube name or cube set name has been changed, existing users data security is not applied to the new cube or cube set.
  Workaround: Add the users to the data security for the cube manually.
  Tracking code: TC-26500
• Schema syncs fail if database tables have objects with 5 levels of nested categories.
  Workaround: Make the object non-reportable.
  Tracking code: TC-30068

User  

• Only a field that has unique values can be used to identify the proper record on a click through link.
  Workaround: When creating a click-through link via scripting on a report, do not have the link appear on values that are non-unique.
  Tracking code: TC-25545
• Incorrect links are created on pivot reports because Primary key is added as Value rather than Row during report creation. Because Primary key is a numeric, it is totaled in the report instead of having a separate row.
  Workaround: Manually move the Total Contact Primary Key to the "Rows" section to display the column as Contact Primary Key.
  Tracking code: TC-25546
• Clicking Edit Script after navigating to Advanced Configuration makes the reporting page freeze.
  Workaround: Instead of Advanced Configuration, click the Edit Widget icon and then click Edit Script.
  Tracking Code: TC-25544
• Account Spend for invoices with a status other than Posted is not displayed accurately.
  Tracking code: TC-23586
• The Reports tab landing page does not display when using Microsoft Windows 7 with Internet Explorer Version 11.0.9600. As a workaround, open Microsoft Windows Settings >  Internet Options > Privacy > Advanced  and select Check Override automatic cookie handling and Check Always allow session cookies.
• Tracking code: TC-15105
• If a user opens the Reports tab in TeamConnect in a Google Chrome browser and then opens the Reports tab a new session on the same instance in Microsoft Internet Explorer, if the user tries to access the Reports tab again in Chrome, the login screen appears but returns an Error 404.
  Tracking code: TC-14337
• While attempting to open the Reporting tab, certain browser security extensions may cause TeamConnect Business Intelligence to loop, preventing it from loading properly.
  Workaround: Disable the extension.
  Tracking code: TC-17855
• When a user clicks the Reports tab after viewing a report from the Report List, TeamConnect will display the legacy reports tab with a list of TeamConnect Business Intelligence reports.
  Workaround: Click Reports tab again to open the TeamConnect Business Intelligence reporting interface.
  Tracking code: TC-19403
• Legacy button disappears from landing page when a dashboard is deleted.
  Workaround: Refresh the page or click the Reports tab again.
  Tracking code: TC-18802
• When a user tries to share a dashboard with the admin and enters the admin's email into the text box, no option of invitation or auto-suggested list to include the admin appears. 
  Workaround: After typing the admin's email address, press <Enter> and the dashboard will be shared with the admin.
  Tracking code: TC-17894
• The report name does not display on a report embedded in a portal pane. 
  Workaround: Name the portal pane with the name of the report that you want to display in the portal pane.
  Tracking code: TC-18482
• The Reports tab does not work with Safari. Use another browser.
  Tracking code: TC-21743
• When a widget's type is change from pivot to table, multiple duplicate entries are displayed in table.
  Tips: To resolve duplicate entries, any contact related reports need to be created as pivot tables. In general, try not to create a report with aggregation for pivot type reports; these reports will sum your Identifiers.
  Tracking code: TC-25543

Software Requirements 

Supported Platforms 

The following prerequisites and supported platforms are required for working with Sisense.

Capacity and Hardware Requirements 

Actual capacity requirements are provided after consultation with Mitratech. The requirements of your configuration may vary depending on the number of concurrent users, builds running in parallel, ElastiCubes hosted on a server, and additional factors specific to your server, for example, non-Sisense applications running on the same server.

Average server requirements for a single-node, on-premise configuration include the following: