Dashboard client is showing exception in log when dashboard server is stopped (since 5.2.0.0).

The following error message will be logged to the dashboard client log file(s) when shutting down the connected dashboard server process(es):

This message merely indicates the disconnection between the dashboard components and the server. Despite being logged as ERROR, these messages are informational only.

Panels deployments can save header when disconnected from webserver (since 4.3).

If panels.ini is used for display server dashboard, then an invalid HTTP session (for example, re-start Tomcat) will result in a sessionExpired page inside the main frame of the dashboard. Clicking on the login link on that page to re-login will not clear the previously displaying tabs/trees. Refresh the web browser or re-visit the dashboard URL to fix the problem.

Filters containing quotes are broken when running with enhanced query mode (since 4.3).

Attachments where the filter value is a string containing a quote do not work in enhanced query mode. In enhanced query mode, attachment filters are turned into SQL WHERE clauses. When using enhanced query mode and having the need to filter by values containing quotes, you need to escape each quote with a quote. Double quotes do not need to be escaped.

Re-deploy of dashboard does not delete cached files (since 4.2.2).If dashboard files were removed between two display server deployments (that is, deploy foo.rtv, then delete foo.rtv from project and re-deploy), the deleted dashboard files will still be available for the re-deployed client. To work around this, delete the reference directory, APAMA_WORK/dashboards/deployed_dashboard, manually before re-deploying.

Improperly defined JDBC connection causes CPU spike in SQL server when using Dashboard Builder (since 4.2.2).

Dashboards using the SQL datasource with invalid JDBC connection parameters can sometimes cause high CPU usage due to numerous failed JDBC connection attempts to the SQL server. This issue can occur if an invalid JDBC password is specified and the Dashboard Builder SQL option Get Tables and Columns is enabled.

Custom window title from Dashboard Builder options is not supported (since 4.2.2).

Setting window titles in the Dashboard Builder using Custom Window Title in Tools > Options > General tab is not supported. Window titles can be set on the command line used to invoke the dashboard viewer.

Apama commands in display server with large amounts of string data may fail (since 4.2).

Executing Apama commands in display server deployments with large amounts of string data may fail if the resulting HTTP GET request exceeds the maximum allowed string length.

Dashboard deployment wizard does not re-sign already signed jars (since 4.2).

The dashboard deployment utility in Software AG Designer will not re-sign jar files that are already signed. If you add jar files to your dashboard deployment that are already signed, you may see errors when accessing the deployed dashboards. When using the dashboard deployment utility, you can sign all jars, or none of them (in this case, they would all need to be signed already), or (if you have a mix of signed and unsigned jars) sign with the same certificate that was used for the jars that have already been signed. If you'd like the deployment utility to sign jars that have been previously signed, you will have to first remove their signatures.

Display server dashboards clearing edited text field on update (since 3.0.2).

Input controls when displayed via the dashboard server may clear any edits when the display is updated. This makes it very difficult to use input forms with the display server. The problem occurs with input controls that are attached to either an Apama scenario, DataView, or dashboard function. When creating input forms in dashboards that will be deployed via the display server, you can follow one of the following techniques:

Delete All with many instances blocks UI (since 3.0).Using the Dashboard Builder's Delete All command to delete large numbers of scenario instances can make the dashboard user interface appear blocked. This is because control is not returned to the user interface until the Delete All operation has completed.