Table of contents Release Notes for Aternity on-premise 12.0 (Released on September 2020) Version 12.0 of Aternity on-premise offers significant steps forward in functionality and features. This article covers the following sections: Deploy Aternity on-premise 12.0 Aternity 12.0 resolves several known issues related to dashboards and setup. You can deploy a clean setup of Aternity on-premise 12.0 (learn more). For the new features in Aternity on-premise 12.0 release, learn here. Resolved Issues Description Issue ID Salesforce ID Resolved in Version The NOT_REPORTING_ACTIVITIES REST API view returns activities that were reported last week. DE23006 1301601 12.0 In the Monitor Application dashboard, the Application widget title does not always change when you select a different breakdown filter. DE23263 1320824 12.0 An incident email notification will not be sent, if the incident URL link is broken. DE23198, DE23436 1301384 12.0 When logging in to the Aternity console, the local domain shows first instead of the last used LDAP. DE22687 1228459 12.0 Known Issues Description Issue ID In Version In rare cases, dashboard library may not appear until the Management Server restarts. DE23949 12.0 In Chrome, when as administrator of Aternity you go to the Advanced Tools > Backup and Restore section and download the backup file of the saved dashboards, the session may expire and return you to the login screen. Note that the file properly downloads, and in case the session unexpectedly expires, login to Aternity again. DE23932 12.0 IdP metadata update sometimes takes few hours or requires a restart in order to work with the new configuration. DE23825 12.0 You should not set a dashboard that is based on a specific device (a single device dashboard) as your console Home page. If the device will be removed, you will not be able to log in. DE23735 12.0 There is a limitation to configure SAML on a SSL secured system when full hierarchy keystore (JKS) is in use. The limitation is that expected entry of type PrivateKeyEntry cannot be automatically selected from list of the keys in keystore. Workaround: Refer to the details in this article. DE23868 12.0 In the saved dashboards, no data will be shown until you manually remove the automatically added Month filter.Workaround: Create a custom calculated Month field in the following way: Month - left(str(DATETRUNC('month',[Timeframe])),3) + left( right(str(DATETRUNC('year',[Timeframe])),13),5) DE23828 12.0 On some servers, the Database Verification tool throws exception during discovery. DE23948 12.0 In some cases, there are issues with Aternity Dashboard Server deployment on drive D:\. We recommend deploying on C:. If you wish to install on any other drive, please follow Tableau 2019 documentation. 12.0 Product tours may not be available with default server settings if there is no internet connection. (The default internet connection settings are that both server and browser have access to the internet.) Under the Gear Icon > aternity/account/hasInternetConnection/, configure server connection to No and browser to Yes. N/A 12.0 Running a lot of docker containers may cause high memory consumption of Linux NetworkManager. To resolve, Aternity recommends disabling NetworkManager service on the Docker Components machine (run as a privileged OS user systemctl mask NetworkManager). N/A 12.0 In the Agent Administration screen, the version column sorting does not work as expected and does not display the versions in the numeric order. DE23890 12.0 If password of the Aternity Messaging Broker Docker Component (Kafka) includes special characters, the Aternity Management Server cannot connect to it. N/A 12.0 Changing Messaging Broker password causes Vertica Writer to lose connection to the Messaging Broker. To resolve, restart both servers. N/A 12.0 After a fresh installation, if no Agents have been connected within 4 hours, Vertica Scheduler may enter the Failing state. As soon as Agents are connected and data starts flowing to Vertica Database Server, the issue gets resolved. N/A 12.0 The Aternity Docker Components Server stores truststore and keystore passwords in clear text in the container definitions for those containers that can be configured with ssl. N/A 12.0 Compatibility Aternity on-premise 12.x requires that devices run Agent for End User Devices 11.0.x, 12.0.x or Agent 12.1.x. Aternity on-premise 12.x is compatible with Aternity Mobile package 11.0.x. Aternity on-premise 12.x is compatible with Agent for Mac 3.3. Parent topic What's New with Aternity on-premise 12.0 (Released on September 2020) SavePDF Selected topic Selected topic and subtopics All content Related Links
Release Notes for Aternity on-premise 12.0 (Released on September 2020) Version 12.0 of Aternity on-premise offers significant steps forward in functionality and features. This article covers the following sections: Deploy Aternity on-premise 12.0 Aternity 12.0 resolves several known issues related to dashboards and setup. You can deploy a clean setup of Aternity on-premise 12.0 (learn more). For the new features in Aternity on-premise 12.0 release, learn here. Resolved Issues Description Issue ID Salesforce ID Resolved in Version The NOT_REPORTING_ACTIVITIES REST API view returns activities that were reported last week. DE23006 1301601 12.0 In the Monitor Application dashboard, the Application widget title does not always change when you select a different breakdown filter. DE23263 1320824 12.0 An incident email notification will not be sent, if the incident URL link is broken. DE23198, DE23436 1301384 12.0 When logging in to the Aternity console, the local domain shows first instead of the last used LDAP. DE22687 1228459 12.0 Known Issues Description Issue ID In Version In rare cases, dashboard library may not appear until the Management Server restarts. DE23949 12.0 In Chrome, when as administrator of Aternity you go to the Advanced Tools > Backup and Restore section and download the backup file of the saved dashboards, the session may expire and return you to the login screen. Note that the file properly downloads, and in case the session unexpectedly expires, login to Aternity again. DE23932 12.0 IdP metadata update sometimes takes few hours or requires a restart in order to work with the new configuration. DE23825 12.0 You should not set a dashboard that is based on a specific device (a single device dashboard) as your console Home page. If the device will be removed, you will not be able to log in. DE23735 12.0 There is a limitation to configure SAML on a SSL secured system when full hierarchy keystore (JKS) is in use. The limitation is that expected entry of type PrivateKeyEntry cannot be automatically selected from list of the keys in keystore. Workaround: Refer to the details in this article. DE23868 12.0 In the saved dashboards, no data will be shown until you manually remove the automatically added Month filter.Workaround: Create a custom calculated Month field in the following way: Month - left(str(DATETRUNC('month',[Timeframe])),3) + left( right(str(DATETRUNC('year',[Timeframe])),13),5) DE23828 12.0 On some servers, the Database Verification tool throws exception during discovery. DE23948 12.0 In some cases, there are issues with Aternity Dashboard Server deployment on drive D:\. We recommend deploying on C:. If you wish to install on any other drive, please follow Tableau 2019 documentation. 12.0 Product tours may not be available with default server settings if there is no internet connection. (The default internet connection settings are that both server and browser have access to the internet.) Under the Gear Icon > aternity/account/hasInternetConnection/, configure server connection to No and browser to Yes. N/A 12.0 Running a lot of docker containers may cause high memory consumption of Linux NetworkManager. To resolve, Aternity recommends disabling NetworkManager service on the Docker Components machine (run as a privileged OS user systemctl mask NetworkManager). N/A 12.0 In the Agent Administration screen, the version column sorting does not work as expected and does not display the versions in the numeric order. DE23890 12.0 If password of the Aternity Messaging Broker Docker Component (Kafka) includes special characters, the Aternity Management Server cannot connect to it. N/A 12.0 Changing Messaging Broker password causes Vertica Writer to lose connection to the Messaging Broker. To resolve, restart both servers. N/A 12.0 After a fresh installation, if no Agents have been connected within 4 hours, Vertica Scheduler may enter the Failing state. As soon as Agents are connected and data starts flowing to Vertica Database Server, the issue gets resolved. N/A 12.0 The Aternity Docker Components Server stores truststore and keystore passwords in clear text in the container definitions for those containers that can be configured with ssl. N/A 12.0 Compatibility Aternity on-premise 12.x requires that devices run Agent for End User Devices 11.0.x, 12.0.x or Agent 12.1.x. Aternity on-premise 12.x is compatible with Aternity Mobile package 11.0.x. Aternity on-premise 12.x is compatible with Agent for Mac 3.3. Parent topic What's New with Aternity on-premise 12.0 (Released on September 2020)
Release Notes for Aternity on-premise 12.0 (Released on September 2020) Version 12.0 of Aternity on-premise offers significant steps forward in functionality and features. This article covers the following sections: Deploy Aternity on-premise 12.0 Aternity 12.0 resolves several known issues related to dashboards and setup. You can deploy a clean setup of Aternity on-premise 12.0 (learn more). For the new features in Aternity on-premise 12.0 release, learn here. Resolved Issues Description Issue ID Salesforce ID Resolved in Version The NOT_REPORTING_ACTIVITIES REST API view returns activities that were reported last week. DE23006 1301601 12.0 In the Monitor Application dashboard, the Application widget title does not always change when you select a different breakdown filter. DE23263 1320824 12.0 An incident email notification will not be sent, if the incident URL link is broken. DE23198, DE23436 1301384 12.0 When logging in to the Aternity console, the local domain shows first instead of the last used LDAP. DE22687 1228459 12.0 Known Issues Description Issue ID In Version In rare cases, dashboard library may not appear until the Management Server restarts. DE23949 12.0 In Chrome, when as administrator of Aternity you go to the Advanced Tools > Backup and Restore section and download the backup file of the saved dashboards, the session may expire and return you to the login screen. Note that the file properly downloads, and in case the session unexpectedly expires, login to Aternity again. DE23932 12.0 IdP metadata update sometimes takes few hours or requires a restart in order to work with the new configuration. DE23825 12.0 You should not set a dashboard that is based on a specific device (a single device dashboard) as your console Home page. If the device will be removed, you will not be able to log in. DE23735 12.0 There is a limitation to configure SAML on a SSL secured system when full hierarchy keystore (JKS) is in use. The limitation is that expected entry of type PrivateKeyEntry cannot be automatically selected from list of the keys in keystore. Workaround: Refer to the details in this article. DE23868 12.0 In the saved dashboards, no data will be shown until you manually remove the automatically added Month filter.Workaround: Create a custom calculated Month field in the following way: Month - left(str(DATETRUNC('month',[Timeframe])),3) + left( right(str(DATETRUNC('year',[Timeframe])),13),5) DE23828 12.0 On some servers, the Database Verification tool throws exception during discovery. DE23948 12.0 In some cases, there are issues with Aternity Dashboard Server deployment on drive D:\. We recommend deploying on C:. If you wish to install on any other drive, please follow Tableau 2019 documentation. 12.0 Product tours may not be available with default server settings if there is no internet connection. (The default internet connection settings are that both server and browser have access to the internet.) Under the Gear Icon > aternity/account/hasInternetConnection/, configure server connection to No and browser to Yes. N/A 12.0 Running a lot of docker containers may cause high memory consumption of Linux NetworkManager. To resolve, Aternity recommends disabling NetworkManager service on the Docker Components machine (run as a privileged OS user systemctl mask NetworkManager). N/A 12.0 In the Agent Administration screen, the version column sorting does not work as expected and does not display the versions in the numeric order. DE23890 12.0 If password of the Aternity Messaging Broker Docker Component (Kafka) includes special characters, the Aternity Management Server cannot connect to it. N/A 12.0 Changing Messaging Broker password causes Vertica Writer to lose connection to the Messaging Broker. To resolve, restart both servers. N/A 12.0 After a fresh installation, if no Agents have been connected within 4 hours, Vertica Scheduler may enter the Failing state. As soon as Agents are connected and data starts flowing to Vertica Database Server, the issue gets resolved. N/A 12.0 The Aternity Docker Components Server stores truststore and keystore passwords in clear text in the container definitions for those containers that can be configured with ssl. N/A 12.0 Compatibility Aternity on-premise 12.x requires that devices run Agent for End User Devices 11.0.x, 12.0.x or Agent 12.1.x. Aternity on-premise 12.x is compatible with Aternity Mobile package 11.0.x. Aternity on-premise 12.x is compatible with Agent for Mac 3.3. Parent topic What's New with Aternity on-premise 12.0 (Released on September 2020)