AMT 61
Released: 14 Nov 2019.
For availability, please contact the Avanade Service Portal for information on downloading new releases.
Special attention items:
There are no special attention items for this release.
Product | Cat | Subcat | Description | Type | Version | Priority |
---|---|---|---|---|---|---|
AMT LION | Runtime | Web Client | 327068 The Enabled property on a timer was used to determine whether to start or not start a timer before changes from the DISPLAY_MAIN had been applied. Whether a timer should be started is now determined on the client-side. The value of the Enabled property is rendered after the DISPLAY_MAIN has been executed. |
FIX | AMT 61 | |
AMT LION | AMT COBOL | Developer | Revision Control | 328009 When an existing label was imported, an error was raised that the label already existed. This blocked the rest of the import. Now, when the import file is selected, it is possible to select how duplicate labels are to be dealt with. The following options are available: Stop: Stops the import altogether; Skip: Skips all duplicate labels but still imports all other labels and other objects; Copy: Creates a new label ending in _Copy and Copy() assigns the objects to this new label; Merge: Assigns all atttributes assigned to the duplicate label to the existing label. |
CHANGE | AMT 61 | |
AMT LION | Runtime | AmtScreens | C1909-043 Dynamic forms were not supported in AmtScreens. A first version of Dynamic forms has been implemented in AmtScreens, in which all basic functionality is working. |
NEW | AMT 61 | |
AMT LION | AMT COBOL | Runtime | Jobs/Batches | 328404 When records were read, it could happen that a record did not have the size defined in the layout used, especially when one program was writing to the file while another program was reading it. This could result in multiple records being read into the receiving record,which found a record where it expected a file-record-ending. Now a new code option has been introduced that can be passed to the file from which the record is read: Fixed = 0, Always read the file using record size; Dynamic = 1, Always read the file using the defined file-record-ending; FindOut = 2, (Default) Identical to the current situation. |
NEW | AMT 61 | |
AMT COBOL | AmtTools | Debugger | C1910-027 Multidimensional structures were not generated correctly in the debug file (.dbg). This caused errors to appear in the watch window when these variables were inspected. This has been corrected in this change. Also, the description of the COMP-3 type has been modified. |
FIX | AMT 61 | |
AMT LION | AMT COBOL | Developer | Code Logic | C1910-045 When the extra option on XML.Save for the BOM marker was introduced, the option was not shown in the code completion scrollbox. Also, the tooltip for the properties was not shown in the code completion scrollbox. The extra option for the BOM marker is now shown in the code completion scrollbox and the properties tooltip comes up now, too. |
CHANGE | AMT 61 | |
AMT COBOL | Runtime | Web Client | C1910-069 In the webclient, keys F13...F24 don't work for numeric editboxes and had to be accessed through shift+F1...F12, but these were blocked. The shift+F1...F12 keys have now been unblocked. |
FIX | AMT 61 | |
AMT COBOL | Developer | Code Logic | 328521 A line of data on the screen was missing because the DATAONLY option for the CICS SEND command had not yet been implemented. The DATAONLY option for the CICS SEND command has been implemented, which resolves the missing data issue. |
NEW | AMT 61 | |
AMT LION | Control Center | Various | 321830 1. In the TransactionViewer, radio buttons take on the styling of their parent. If that parent has a border, this causes the radiobuttons to have distorted borders since the styling is applied to both the parent and each button. 2. If elements on a form with a parent element (like labels in a panel) were created before their parent element, the TransactionViewer added them to the page without a parent, causing errors. 1. After the styling of the parent has been applied to the radiobutton groups, the border width is set to 0, which is also used by the radiobuttons. In both cases the value can be overridden by styling the control itself. 2. If a TransactionViewPage is created, elements for which a parent cannot be found are remembered and added later. AmtScreens works in the same way. |
FIX | AMT 61 | |
AMT LION | Runtime | Various | C1910-078 Temporary files created for sorting were not deleted when the sorting had finished. The files were not actually specified as temporary files internally, which caused them to be saved instead of deleted. This has been fixed, the files are now marked as temporary which ensures that they are deleted. |
FIX | AMT 61 | |
AMT COBOL | Runtime | Web Client | C1910-080 In AMT COBOL it isn't possible to determine the difference between a ZERO and an EMPTY value in a numeric field with a blank-when-zero format. Both values result in an empty (SPACES) memory buffer. To determine the difference between ZERO and EMPTY, the NUMERIC-EMPTY function has been added in AMT COBOL. This new function is only usable in AMT COBOL Forms. |
NEW | AMT 61 | |
AMT COBOL | Runtime | Various | C1910-086 Not all calculation in AMT COBOL was done using INT64. For AMT COBOL calculations are now done using INT64 where possible. This improves the performance of applications that do not have the COBOLCALCULATION=TRUE set. |
CHANGE | AMT 61 | |
AMT COBOL | Runtime | Various | C1910-089 When a form was (re)sent from the business logic to the client, and the cursor position wasn't set explicitly, the cursor had to be set to the initial field of the form manually. This was related to A-Series AMT COBOL only. This issue has been resolved in AMT COBOL, by resetting the cursor to its initial position. |
FIX | AMT 61 | |
AMT LION | AMT COBOL | Generator | Various | C1910-091 After a succesful FIND, an UPDATE raised error NOT A CURRENT RECORD. This was because the RECNO index was not used for the UPDATE. Now the RECNO index is used when an UPDATE is done. |
FIX | AMT 61 | |
AMT LION | AMT COBOL | Runtime | Web Client | C1910-098 Log off in the Application Center after an application had been opened would take more than 2 minutes, because it would in fact be performed twice, once for the log off itself and once for the unloading. A check is now done, which causes any second attempt to log off to be ignored. |
FIX | AMT 61 | |
AMT LION | AMT COBOL | Runtime | Various | 328160 The display of SME messages with formatting codes for trimming and colors was not the same in AmtScreens and in the Application Center. Formatting of SME messages on the messages tab has been corrected to resemble more closely that in the Application Center. |
FIX | AMT 61 | |
AMT LION | Runtime | AmtScreens | C1910-101 If there were no available screens, pressing the 'select screen' button in AmtScreens showed a useless dialog. AmtScreens will now properly display an error message that access has been denied, since no forms are available to the user. |
CHANGE | AMT 61 | |
AMT COBOL | Runtime | Web client | 328519 In Chrome, a numeric field with a format and decimals was not formatted correctly when a function key was pressed while the field still had focus. Now the value is formatted correctly so that when 12 is entered and transmitted, it's shown as 12.00, for example. |
FIX | AMT 61 | |
AMT LION | Runtime | AmtScreens | C1910-103 In AMT Screens, RTQuery sometimes raised errors when the user changed tabs, due to permission issues on table headers. The issue has been resolved by setting 'CanExecute' to false when the user leaves the RTQuery tab. |
FIX | AMT 61 | |
AMT COBOL | Runtime | Various | 328574 Using ERASEAUP and DATAONLY together in a CICS SEND MAP statement cleared the whole form. Now when the field buffer is hex 00 it's cleared (if the field is unprotected), else it shows the new value. |
FIX | AMT 61 | |
AMT LION | AMT COBOL | Control Center | Security | 328550 After an upgrade, an error was raised about an invalid Salt version at log in when form authentication was used. This was caused by inconsistent use of encryption. The log in functions have been corrected so that the hashvalue of password is always stored encrypted. |
FIX | AMT 61 | |
AMT COBOL | Runtime | Various | 328545 When a screen copy was sent without clearing its data first, and the set cursor from a previous transaction (using MOVE -1 to LENGTH FIELD) was still active, the wrong focus was set. This occurred when the cursor fields value had not been changed on the next transmit. Now on receive the LENGTH FIELD is always (re)set, so the cursor is set to the right field. |
FIX | AMT 61 | |
AMT COBOL | Generator | Various | C1910-108 The cursor could not be put on the first field with invalid input in AMT COBOL, when input validation was done in the FORM-TO-WS section of the COBOL program. This situation has been resolved. |
CHANGE | AMT 61 | |
AMT COBOL | Runtime | Web Client | 328508 For AMT COBOL IBM applications, the high intensity property was not applied to protected fields (labels) in the web client. The high intensity property is now applied to protected fields (labels) in the web client. |
FIX | AMT 61 | |
AMT LION | Runtime | AmtScreens | C1910-113 When you tabbed out and in of AMT Screens RTQuery and executed a wrong custom query, AMT Screens crashed. This was caused by duplicate column creation in the RTQuery listview. The issue has been resolved by creating a new Observablecollection item for the RTQuery listview. |
FIX | AMT 61 | |
AMT LION | AMT COBOL | Developer | Various | 328477 If F1 was pressed to request help on syntax, the wrong URL was resolved for access to help. This was caused by defining HTTPS instead of HTTP for the HELPURL in the Lion.ini., for example: HELPURL=https://help.myasysco.com/lion/ Now HTTPS can also be defined for the HELPURL in the Lion.ini. |
FIX | AMT 61 | |
AMT LION | AMT COBOL | Runtime | Scripts | C1910-115 The AMT PowerShell Sort library didn't support (one of) the input file(s) being the same as the output file. This resulted in error 'Cannot access a closed file', returned by the FileController. The AMT PowerShell Sort library has been updated to support (one of) the input file(s) being the same as the output file. When this situation is detected the result of the sort is first stored in a temporary file which is renamed to the output file when the sort has finished. |
FIX | AMT 61 | |
AMT COBOL | Runtime | Various | 328211 On a Swedish keyboard, the decimal separator was not correctly translated if it was entered as a comma in a textbox in the web client. The translation of the decimal separator has been fixed to correct the numpad comma on a Swedish keyboard layout. |
FIX | AMT 61 | |
AMT LION | Runtime | AmtScreens | C1910-118 In AmtScreens, the stationname on a virtual desktop could be the virtual hostname, if it had been retrieved from DNS (depending on how the virtual hosts were configured). In LionScreens, the NETBIOSNAME was always used as the stationname. Since the computername was no longer limited to the 15 characters of the NETBIOSNAME, AmtScreens has used the DNS retrieval by default. From now on, if the NETBIOSNAME differs from the DNS name, the NETBIOSNAME (retrieved from environment variable COMPUTERNAME) is always used. If this environment variable is empty, USERNAME is used for the stationname. Tip: If USERNAME should always be used as the stationname, set the stationname resolution to 'User' in the Control Center" |
CHANGE | AMT 61 | |
AMT LION | Runtime | AmtScreens | 328596 When AMT Screens was started, an error could pop up saying that AMT Screens could not access its settings file. Now, if there is no access to the settings file, AMT Screens doesn't show the error popup anymore. The settings file does not contain vital information (mostly data about screen dimensions). Also, AmtProdInstall has been changed to copy the required folders to the Common directory. |
FIX | AMT 61 | |
AMT LION | Runtime | AmtScreens | 328591 If there was a hyphen in a fieldname, SetFocus was not executed in AMT Screens. Fieldnames with a hyphen in the name are generated at runtime with the hyphen replaced by an underscore. The SetFocus function now also makes sure a fieldname is generated with an underscore, if required. |
FIX | AMT 61 | |
AMT COBOL | Runtime | Various | 328615 When low-values were sent to a numeric field in a BMS map, the first transmit sent the low-values to the logic but further transmits sent spaces. Now, further transmits send low-values to the logic, until the logic updates the field with a different value. |
FIX | AMT 61 | |
AMT COBOL | Runtime | Web Client | C1910-135 The description of a COBOL application in the caption of the tab in the Application Center was not shown even though this option was enabled in the Control Center. This has been fixed for COBOL applications. The description of an application can be set in 'System Configuration' -> 'Architecture' -> 'Applications'. This description can be shown as a caption of the tab page by setting option 'Show application description in caption' to 'true' (under 'System Configuration' -> 'Runtime behaviour configurations' -> 'Form appearance'). |
FIX | AMT 61 | |
AMT LION | AmtTools | Reo | 328569 AMT Reorganize could not run in batch mode, nor could it be connected to AMT Reorganize service. These issues have now been fixed. To run Amt Reorganize connected to the Amt Reorganize service you need to specify the startup /REOSERVICEADDRESS=NB1306:61002 where NB1306 is computer name and 61002 is the port of the Reo-service. |
NEW | AMT 61 | |
AMT LION | Runtime | AmtScreens | C1911-001 Force decimal key set to 'none' did not provide the proper amount of zeros for an AMT edit box. Now, force decimal key set to 'true' autofills the value in the same way as when set to 'none'. |
FIX | AMT 61 | |
AMT LION | AmtTools | Reo | C1911-002 Creation of a new system database with AMT Reorganize did not work in all cases. The creation of a new system database with AMT Reorganize has been improved; the test if the database is empty is now done by checking if Amt Table is present, not by checking if there are any tables at all. |
FIX | AMT 61 | |
AMT LION | AMT COBOL | Runtime | Web Client | 328600 When a decimal key was forced on a non decimal control that didn't have any decimals in it, an error message would pop up. The checking mechanism no longer forces decimal keys on controls without decimals. |
FIX | AMT 61 |