AMT 133
Released: 16 Feb 2024.
For availability, please contact the Avanade Service Portal for information on downloading new releases.
Special attention items:
AMT 133
- The authentication of the Blazor WebAPI’s NotifyHub component has been improved and secured. See release note item #80974 for more information.
Product | Cat | Subcat | Description | Type | Version | Priority |
---|---|---|---|---|---|---|
AMT LION | Runtime | AMT Screens | #27669 In AMT Screens, when a password input field was exited that had the 'numeric can be empty' property set to 'false', the field was erroneously cleared. The password handling process has been expanded for additional functionality. |
FIX | AMT 133 | MEDIUM |
AMT LION | Runtime | Forms | #79004 The text alignment of an AMT Label was not reinstated after the REFRESH command was executed. The text alignment of an AMT Label is now preserved after the REFRESH command is executed. |
FIX | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Libraries | Various | #79678 The next steps towards loosely coupling of AMT Libraries have been taken. Over the coming AMT releases, more libraries will be refactored in order to optimize touch points of generated code with the libraries. See the roadmap in Service Now for more information. |
CHANGE | AMT 133 | LOW |
AMT LION | AMT COBOL | Runtime | Blazor Web Client | #80446 Usage of the BlazorWebApi in the AMT Blazor Web Client has been simplified and enhanced for better maintainability. This modification paves the way for a smoother implementation of OpenIdConnect in the near future. |
CHANGE | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Blazor Web Client | #80566 The ZOrder for several Blazor components was undefined until now. The ZOrder is now adheres the configuration defined by the developer. |
FIX | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Code Logic | #80573 New components were added to the Blazor Web Client and SelectScreen's functionality was re-implemented to separate the AMT application and the AMT Framework logic. |
CHANGE | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Blazor Web Client | #80690 In the Blazor Web Client, the AmtComponent IDs of the following controls have been updated to align with the current ID standard: DataGrid, ButtonGroup, Image, Chart, GroupBox, Shape, Fileuploader. |
FIX | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Blazor Web Client | #80703 Certain necessary properties for form definitions were missing until now, which resulted in incorrect control behaviour when the Blazor Web Client was used with AMT VS or AMT COBOL. Form definitions have been updated to include all the necessary properties. |
FIX | AMT 133 | MEDIUM |
AMT COBOL | Runtime | Code Logic | #80704 In the continuing process of adding XGEN features to AMT-GO, several more have been implemented and improved. |
CHANGE | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Blazor Web Client | #80780 In the Blazor Web Client, popups were not responding to click-and-drag actions on their edges. Modifications have been made to the Blazor and JavaScript methods, restoring click-and-drag functionality. |
FIX | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Blazor Web Client | #80823 In the process of refactoring the Blazor Web API, some issues related to timing were inadvertently introduced. Additionally, it was discovered that SMEs executed in the Display Main were not displayed in the AMT Blazor Web Client. These issues have now been resolved. |
FIX | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Security | #80974 The NotifyHub component of the Blazor WebApi used for pushing messages to stations lacked authentication. This allowed potential attackers to intercept messages intended for specific stations. Additionally, the SignalR hub incorporated a method that permitted message transmission to a particular station without requiring authentication. This method was implemented only for debugging purposes and remained in place post-development. Authentication has been activated on the SignalR hub to prevent unauthorized connections. Additionally, the method for station message transmission has been removed. |
FIX | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Blazor Web Client | #80852 In the Blazor Web Client, subsessions were not consistently assigned to all components. By adding cascading parameters into Blazor, it is ensured that all components receive the correct subsession ID. |
CHANGE | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Generator | Various | #80868 INC: 1079533 The license verification process for operating the AMT Generator on Azure virtual machines, which are automatically recreated, utilized an outdated method for obtaining Azure information. The license verification process now employs the updated Azure API to retrieve the required information. |
CHANGE | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Code Logic | #80884 INC: 1078724 Within form and batch executions, there where instances when the original exception could not be retrieved from an exception thrown during an SQL execution. The exception handler has been enhanced to throw the original exception as well. |
CHANGE | AMT 133 | MEDIUM |
AMT LION | AMT COBOL | Runtime | Web Services | #80885 INC: 1135367 If a call was made to a REST Provider, and the Application Server was unreachable, the REST Provider had a bad connection. The connection remained locked, with the result that all subsequent concurrent calls to the API Service failed, until the Application Pool (AppPool) was recycled. The system now disregards bad connections and cleans the connection to address the issue. This ensures smooth operation of the API Service, without the need to recycle the AppPool. |
FIX | AMT 133 | MEDIUM |
AMT LION | Runtime | Blazor Web Client | #80886 In the AMT Blazor Web Client, images were downloaded and refreshed each time a transmit event was triggered. Also, the list of available languages was fetched after every transmit. These unnecessary API calls negatively affected performance. These issues have now been resolved. Images are only re-downloaded and updated if they have been changed. |
FIX | AMT 133 | MEDIUM |
AMT LION | Runtime | Application Server/Manager | #80915 INC: 1078754 If the Application Server was inadvertently started under a temporary profile, the startup process failed due to an expired license message. The exception provided insufficient information, which complicated the identification of the issue's cause. In the event of an exception during the license verification process, the details of the exception are now recorded in the log. |
CHANGE | AMT 133 | MEDIUM |
AMT LION | Runtime | Blazor Web Client | #80930 The MaskEdit functionality in the Blazor Web Client no longer worked due to a modification in the process of reading definitions. This led to an asynchronous reading of the MaskEdit and the data, rendering the MaskEdit invisible. The issue has been addressed by correcting the definition reader. |
FIX | AMT 133 | MEDIUM |
AMT LION | Runtime | Blazor Web Client | #80963 In the Blazor Web Client, the AmtComponent IDs for the Menu component and its sub-elements are now consistently unique, rather than being randomly generated. |
CHANGE | AMT 133 | MEDIUM |
AMT LION | Runtime | Various | #81088 In AMT Screens, the Chart object caused an 'index out of bounds' error when using the 'Legend' property. The generator has been corrected to produce the appropriate runtime C# code for the 'Legend' property of the Chart object. |
FIX | AMT 133 | MEDIUM |