Upgrade Checker

AMT 8

• The minimum requirement for .NET version has become 4.5 For every machine that runs the Web Client and every machine that runs the LionDevGenerator.

AMT 9

• The minimum requirement for .NET version has become 4.6.1. Asysco has started compiling against .NET 4.6.1. This will lead to better memory management. Our release notes and helpfiles now reflect this requirement as well.

• The Webdeployment tool must be upgraded On environments that don’t have Visual Studio 2015 installed, web deployment targets VS 2015 & Microsoft .NET Framework 4.6.1 Developer Pack will need to be installed. Asysco provides these packages on the selfservice­desk here.

AMT 10

• .NET 4.6.1 is now the minimum requirement. This will lead to better memory management.  Our release notes and helpfiles now reflect this requirement as well. -The Webdeployment tool must be upgraded On environments that don’t have Visual Studio 2015 installed, web deployment targets VS 2015 & Microsoft .NET Framework 4.6.1 Developer Pack will need to be installed.  Asysco provides these packages on the selfservice­desk.

AMT 11

• Added possibility to cleanup station/session in the Control Center. Sometimes due to not logging out correctly, sessions would remain in the system table, effectively locking up a session of a station. It is now possible to delete hanging sessions within the control center. This makes it easier to control the connections to the Application Server.

• Component Activation – Access to the Control Center. Access to the Control Center can now be regulated in the Component Activation section of the Control Center. Roles can be granted or denied the rights to access the Control Center. In the past, it was only possible to deny specific components within the Control Center.

• Control Center: Disallow automatic creation of users. Users were automatically created in the system database when connecting to LionScreens for the first time. They can now be rejected from the system when they try to access the environment. This behaviour can be set in the Control Center.

• Panel with Align = Client will now behave the same in Webclient and LionScreens. When used as a background, a panel with the property “align = Client” was not covering the whole of the screen in the webclient, as it did in LionScreens. This behaviour has been corrected, and it should now appear the same in both environments.

• Various security fixes. We have implemented extra security measures for the Control Center and Application Center.

AMT 12

• The parser for generating in AMT Development Studio has been enhanced. The purpose was to enable more multi threaded generations, to produce better syntax errors and better generation errors and to get the parser future ready for more OO programming, like the classes that we recently introduced. The new parser is better and somewhat more strict than the old one. Meaning it may happen in specific coding implementations at customers, that the new parser will detect syntax errors which were not caught by the old parser. Needless to say, it is important that these syntax errors are solved by the customer. Therefore please do an extra check on the first generations’ results after upgrading to AMT 12.

AMT 13

• The Winlogon web site is no longer used for the Control Center, and has been replaced by IIS Integrated Windows Authentication. This will require changes to be made to IIS Authentication. Information about the correct settings can be found in our Helpfiles here. Please note that the web.config will also be changed automatically. These changes will also need to be reflected in other environments.

• Internet Explorer 11 is now natively supported. The support of older versions of the IE browser has been removed, i.e. IE8, IE9 and IE10. If a browser is no longer supported, a message will appear in the browser. This includes Internet Explorer 11 in compatibility mode.

AMT 16

• The stack size to be used when creating new threads was hard coded. It is now configurable. This impacts BatchController and TransactionServer, they now use the configured stack size in Control Center under System Configuration -> System Setup -> Runtime Behaviour Configurations.

• The generator accepted a generation set parameter “STACKSIZE=”. This could be specified on the GS tab in AMT Developer Studio. Doing so no longer has any effect, this parameter is now ignored. The stack size configured in Control Center is used instead.

AMT 20

• Roslyn Compiler is now default for Amt. After a preview period of several sprints without any problems, the default compiler for Amt is now Roslyn. There is a setting DISABLEROSLYN in Lion.ini available to disable the Roslyn Compiler, but we strongly discourage use of this setting because it will be removed over several sprints. The generation set and Lion.ini setting “ROSLYN”  has been removed.

• Remove support for “DEFINE” inside insertable global  logics. The “DEFINE” function was outdated, not documented and only used by some customers. They have been contacted individually on the usage and replacement of this function. Its no longer allowed to use it.

AMT 26

• Possible change to web.config is needed. AMT 26 contains ticket 325083, which patches sorting features within Control Center. If you are updating an existing install, you will need to backup your production web.config prior to the change to prevent the file from being overwritten. This can be done by renaming the file, and by comparing it afterwards with the new web.config file. We’ve added the following line to the web.config of the Control Center in AMT 26.
  

      <endpoint name="AmtSecurityService" 
            address="http://localhost/8000/ControlCenterBLDev/AmtSecurityService.svc" 
            binding="basicHttpBinding" 
            bindingConfiguration="basicHttpBinding_Normal" 
            behaviorConfiguration="AmtEndpointBehavior" 
            contract="Asysco.Amt.Framework.Interfaces.Security.IAmtSecurityService">
      </endpoint>  
             

Please note that this will depend on which version you currently run. So, we always advise you to do a comparison.

AMT 27

• Note that the underscore won’t always be visible, as you can see in the change 325910. This depends on the level of zoom you’ve applied. When you scroll up (enlarge the code), the underscore will again appear. We’ve tried to match the old font size, but you might see slight differences.

• Secondly, we’ve made some changes to localizations settings, as you can see in change 324237. These settings are now moved to the AmtLocalisation.xml. You would need to make a manual copy before installing the newest version.

AMT 28

• The license check function has been changed such that a new Lion.lic and AmtRuntime.lic file are mandatory for this upgrade. The AMTRuntime.lic must be present in the system root directory in order to run Control Center.

AMT 30

• Attention, this release does include changes that require your action:
  • As of this release, we made some changes to the password hashes. A rollback won’t unhash the password leaving you with unusable content in password table, therefore, we urge you to create a backup. Nevertheless, we do encourage you to always create a backup before implementing a newer version.
  • Of course, you are able to restore the previous version by making use of the rollback, but this will imply that all passwords need to be added again.

AMT 34

• We’ve rebuilt the list boxes and comboboxes. This may require additional adjustments if you have customized them outside the AMT solution.

AMT 38

• Starting from this release, it is mandatory to set one of the available options for the Numeric Sign Encoding Type. The default option is ‘not set’, and generation requires one of the options to be selected. Therefore you will need to right-click on the application, chose options and change the option Numeric Sign Encoding. Then open revision control, by entering rev in the open-box, go to system > application options and check-in the Application. If you forget this, you will get an error message in the generator that warns you about changing the Numeric Sign Encoding Type.

AMT 39

• The AMTscreen preview can be added by adding the preview parameter to the setup. Make a shortcut to the setup and add /preview or run the command in the commandline (E.G. C:\AMT\AMTTESTNEW\Setup\Setup.exe /preview).
  Important information: Every client will now need .NET framework to be installed.

AMT 40

• Due to changes to the AMT framework tables the REO will throw a warning with the message: “The field length is smaller” and “this field will be truncated”. Note that this is thrown due to changes in the AMT Framework tables and they will be truncated due to this change. This won’t affect user data. The REO does need to perform changes to all databases.

AMT 43

• As of AMT 43, the retained variable will not be stored by default anymore for Webservices. To store the retained variables the setting, STORESESSIONDATA=TRUE, should be added in the .ini files. See ticket 326498.

AMT 44
This version contains a few importantant changes!

• For former MicroFocus customers, only the default is now set to ORGANIZATION RECORD SEQUENTIAL, because that is the Microfocus COBOL default. Records have no cr and/or lf line ending unless the ORGANIZATION clause is line sequential is specified. As a work around you can add these line yourself:
  • ACCESS IS SEQUENTIAL
  • ORGANIZATION IS SEQUENTIAL
    Read more on this change in ticket: 327403.
• When you have installed the preview of AmtScreens (used the setup.exe with the parameter PREVIEW), then you need to remove the old folder of AmtScreens. This is located in \\Apps\\Binaries\ClientGUI The new preview of AmtScreens is in the folder ClientGUI. The AmtScreens.exe and its dlls are located in this ClientGUI folder.

AMT 46
A major change is necessary for AMT 46 and the subsequent versions for AMT Cobol customers.

• Due to continuous changes in the product, a manual change will be needed in the web.configs. This is necessary because the web.configs will not be overwritten. Due to this change:
  • The WCF port is now the only option and must be set in the Control Center.
  • In addition, changes must be made to the web.config and every client must also update web.config (configuration code/file) that refers to the server.
• Customers to whom this change applies, will be informed about this change. Please see Customer Support if you have any questions.

AMT 47

• AMT Screens has moved out of preview and into the mainstream AMT release. The mainstream functionality is complete, however, there are still some areas to address in future AMT releases, that may not be impactful in your particular install. These areas include:

• Dynamic forms.
• RTQuery.
  • The use of a semicolon (; ) needs to be added to RTQuery for Oracle.
• Printing is only of the visible part of the screen.
• Memory creeps can appear in some specific cases.
• Maskeditbox
  • Can show squares when you add in too many values
  • Removing a value can change how the Maskeditbox appears on the screen.
  • Support for backspace and xmit in maskeditboxes in macros.
• The messages page auto closes when you click into the screen.
• In multi-language, some labels do not change on the language setting.

The new AMT screens will need the .NET framework to be installed on all thin clients. If you want to know more about the configuration of AMT Screen, please visit the helpsite.

AMT 49 –

• In AMT 49, we have added the new AmtReorganize as a preview. We do want to warn you about the fact that, although the new REO is tested with Microsoft SQL Databases and Oracle Databases, we anticipate that more in depth tests are needed for Oracle Databases still. This is only meant for early preview.

AMT 50 –

• Please be aware of the following notes concerning the webservice changes related to ticket 327564:
  • For generated classes the WSDL resulted in class names with _Web. We have changed the behavior that _Web is not used anymore in the WSDL for class names. -This change requires changes in the end users interface, removing _Web, when the provided webservices are regenerated. If no changes are made then consuming providers with the style RPC/encoding will receive a soap server error.

AMT 51 –

• The new style web services have been introduced in Lion 6.net Patch 8 fix 5. If you have old style provided web services, these can cause issues when upgrading to AMT 51. You can recognize these in the AMT Developer in the overview of provided web services by the type: (Old Style) Web Service Provided. This will be addressed in the next AMT version.

AMT 52

• In AMT 52, we have made changes to the number of days that a warning for an expiring license appears in the logfiles.
• We have reduced the number of days from 60 to 30 days.
• Furthermore, the Printer option ‘Trim trailing spaces’ has been set back to its original default value.
• Unfortunately, the default value was changed in previous releases. This has been restored.

AMT 53

• Please note: due to changes in the AMTSYSTRANSACTION table, the REO can take longer than expected, approximately up to an hour.

AMT 55

• Please note: due to the fact that tables will become nullable, as mentioned in ticket 328198 (and C1906-080), the REO can take longer than expected, even several bours.
• Furthermore, we would like to warn you about the fact that “Old style webservices” cannot be generated or edited anymore because they have been phased out (C1905-090) . Therefore, you might want to migrate them to the new webservices before upgrading to this release or beyond.

AMT 58

• AMT Reorganize will now be removed from Preview-mode and will be added to our regular Release. Please read the following important notes before testing this Release and always create a backup first.
• Please note that, once the new Reorganize is used, you cannot use the old REO.exe again as it will undo the changes made by the new Reorganize.

AMT 59

• Does not include any changes that require changes to your software, with the exception of the jQuery update (C1809-072), which may require your attention!

AMT 60

• Several batch executables have been decommisioned in this release: StartJob.exe, StartReport.exe, StopReport.exe, LionMessage.exe, LionSort.exe, LionScript.exe and LionPrint.exe. This may require some customers to replace the calls to these executables with calls to Powershell or the Comscript.dll.
• Furthermore, REO.exe has been replaced by the AmtReorganize executable. Existing REO services will not work anymore, and have to be reinstalled. The REO has been removed from the AMT Control Center, and can only be run from outside the CC from now.

AMT 62

• Make sure that with use of the new AMT Screens, the DLL files of the older version have all been deleted from the ClientGUI folder!
• If you use the new File Uploader, you have to re-add the object to the form for it to work.

AMT 64

• Support for IE 11 has been discontinued as of this release!
• Please keep in mind that from AMT 64, version 4.8 of the .NET FrameWork is the mandatory version!
• Also required for installation of AMT 64 are the Visual Studio 2019 Build tools.

AMT 69

• AMT File Controller (.NET Core/gRPC):
  As a first step In the gradual migration of our complete AMT source to .NET Core, the AMT File Controller is now targeting .NET Core 3.1 when running ‘normally’ or stand-alone. The assemblies it relies on all target .NET Standard 2.0. This switch may need additional installation of .NET Core components or configurations for Oracle.
• .NET Core Runtime 3.1.x needs to be installed on all servers where an AMT File Controller is running. Customers are advised to install this version on all AMT servers since more components will be Core enabled in future AMT releases. It can be found here.
• For gRPC to work, VC_Redist.X64 needs to be installed. This is a C++-Library from Microsoft, which is commonly used, so it may already be installed on your systems. It can be found here.
• The web.configs for the AMT Application Center, AMT Control Center and the client web application have extra assembly dependencies. Please make sure the following lines are in your web.configs:

<dependentAssembly>
  <assemblyIdentity 
    name = "Newtonsoft.Json" 
    culture = "neutral" publicKeyToken="30ad4fe6b2a6aeed" 
  />
  <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="12.0.0.0" />
</dependentAssembly>
<dependentAssembly>
  <assemblyIdentity 
    name="System.Runtime.CompilerServices.Unsafe" 
    culture="neutral" publicKeyToken="b03f5f7f11d50a3a" 
  />
  <bindingRedirect oldVersion="0.0.0.0-4.0.6.0" newVersion="4.0.6.0" />
</dependentAssembly>

• For Oracle only: the AMT File Controller needs a .Net Core version of the wrapper. This has been delivered and requires an extra environment variable AMT_ORACLE_WRAPPER_CORE.
• AMT File Controller settings:
  A gRPC server and port number must be set in the File Controller options in the Control Center upon upgrading. If this is not done, the File Controller and Batch Controller will crash. Customers are advised to use IP addresses instead of DNS in all applications that use the new .NET Core and gRPC based AMT File Controller, as this works more efficiently. Settings can be changed in the AMT Control Center, under Services.

AMT 72

• If you want to use the new .NET Core AMT Print Controller remotely, make sure:
  • you have .NET Core 3.1 installed on your remote system
  • your configuration file is ‘AmtPrintService.dll.config’ rather than ‘AmtPrintService.exe.config’.
• AMT Batch Controller: If there are projects targeting a specific .NET Framework version while the BatchController is running in .NET Core, this will cause issues in the running of reports. Turning off the ‘Call .NET Assemblies’ setting in the Control Center Runtime Behavior Configuration resolves the issue.

AMT 73

• All AMT Products:
  • On every server with an AMT product, the following must be installed (both the 32-bit and 64-bit versions need to be added):
    • VCRedist X64 (64 bit)
    • VCRedist X86 (32 bit)
• The latest versions can be found here.
• AMT Print Controller (.NET Core/gRPC):
  • .NET Core Desktop Runtime 3.1.6 needs to be installed on all servers where an AMT Print Controller is running. It can be downloaded here.

AMT 74

• All AMT Products:
  • A number of changes have been made in preparation for the .NET Core and gRPC implementation. The full details of these changes will be provided in the AMT 75 release notes.

AMT 75

• Reports are now generated as .dlls instead of .exes. To view all reports with the correct extensions in the Control Center, you are required to execute ‘Read all jobs from system’ after installing AMT 75 and generating the reports.
• Due to a change in the AMTSYSDATABASESETTING table, a reorganize of the system database is required after installing AMT 75.
• The Reorganize service is now supported by .NET Core. A small change has been made to the format of the config file. The "<ReoServiceAddress>" format has changed from "net.tcp://<Server>:<Port>/ReoService" to "<Server>:<Port>".
• For the OpCon service, installation of ASP.NET Core 3.1.0 Runtime is required!

AMT 78

• For Prodinstall installation of ASP.NET Core 3.1.0 Runtime is required!

AMT 79

• For Oracle users: in order to get setting SEQ_AMTPRINTREQUEST correct, sequence SEQ_AMTPRINTREQUEST must be dropped manually from the database before running AMT Reorganize.

AMT 80

• C2012-018 – Support for Azure SQL Managed Instance: An AMT Reorganize is required for this change!
• C2010-064 – AMT Developer and Generator to .NET Core: Developers may need to test programs and scripts depending on the LionRepository.dll!
• Developers wanting to use the .NET Core based AMT Developer should make sure they have .NET Core 3.1.0 Runtime installed on their end-system!

AMT 82

• C2101-043 – Moving a multi-item array into a single variable is not allowed anymore. Please check your AMT COBOL programs to see if this affects your code!
• 330168 – Array-items now set as elements instead of array-items if ElementFormDefault is set to unqualified. A ‘Reload WSDL’ is required for all your CWS!

AMT 83

• Since AMT Screens is now .NET Core compliant, it is important that end-users’ systems contain .NET Core Desktop Runtime (version 3.1.x)!
• If you experience any problems with Consumable Web Services, please do a reload of the WSDL first, as this may solve your problem immediately! For more information, please look at this help page.

AMT 85

• Please refer to this help page for more details on the new .NET Core based AMT Control Center and AMT Application Center. This includes information about the required Hosting Bundle.
• Use of the .NET Core based AMT File Controller requires PowerShell 7. You can download PowerShell 7 here. More information about debugging PowerShell scripts with PowerShell 7 can be found here. Customers used to working with the PowerShell ISE should find this page useful.

AMT 86

• Setup of the AMT Product Suite allowed settings to be moved from http to https and back in ‘web.config’ files. With the new websites and web APIs, https settings are in ‘appsettings.json’ files.
• Starting from AMT 86 the .NET Framework version(s) of the AMT Oracle database wrappers are removed from the AMT releases, and environment variable AMT_ORACLE_WRAPPER for setting up the .NET Core Oracle wrapper has to be used. The environment variable AMT_ORACLE_WRAPPER_CORE is no longer supported.
• LionScreens (based on Delphi technology) has now officially been removed from the AMT Product Suite and has been replaced by AMT Screens (based on WPF technology).

AMT 87

• The creation of charts in screen and print layouts in AMT LION depended on deprecated .NET features. Charts are now rendered using OxyPlot, an open source library supported in .NET Core.
  Important note: charts will not look identical to the way they looked before this change. Customers should make sure to check their charts when they upgrade to AMT 87.

AMT 88

• Command SENDTOTABSHEET has now been implemented in the Web Client and in AMT Screens.
  Important: only one tab can be opened at a time in AMT Screens!
• FTP connections made by AMT ComScript used .NET’s FtpWebRequest, which was deprecated in .NET Core, so a third-party replacement was needed. The FluentFtp library is now used for FTP connections.
  Important: The format of file names returned by the FTP client has changed to include the directory path. Other responses might also have a different format. It is important that customers check any scripts and programs that use the AMT FTP functionality for discrepancies, and adjust them where necessary.
• Transaction Server agents were restarted automatically if a new version of a loaded form or program had been generated. This cleared the state of ‘Shared’ (also known as ‘Reentrant’) programs, which could cause issues. It is now possible to disable the automatic restarting mechanism in the AMT Control Center.
  Important: Because of this change, it is necessary to do an AMT Reorganize of the the system database!

AMT 90

• Images in the DateTimePicker are now visible.
• To resolve an issue in existing environments, the web.config located in ControlCenterCore needs to be modified: the line ‘img-src ‘self’;’ should be changed to ‘img-src ‘self’ data:;’. After that, an IISReset fixes the issue.

AMT 91

• A REO of the AMT system database is required after installing this release.

AMT 92

• C2108-018: Please note that where it says ‘negative number’ you should read ‘negative number or 0’ for this change!

AMT 93

• A Reo of the AMT system database is required after installing this release.

AMT 98

• After a Patch or Fix or Web-Deployment, it is important to compare the contents of the Web_Default.config file to the web.config file, as there may be new suggested default settings in Web_Default.config that need to be incorporated in web.config files.

AMT 99

• No Log4j software has been detected in a complete scan of the AMT product suite!
• 2 New items come with AMT 99:
  • Kill/WakeUp/Stop/Interrupt commands in the ‘Job Management’ tab of AMT Screens. They can be activated by right-clicking a running job. Please refer to this help page for more information.
  • Sequences have been introduced, to help making rows in tables and views unique. This only works for MS-SQL databases so far, a version for Oracle is in development. Find out more about Sequences in this help page.

AMT 100

• 3 New items come with AMT 100:
  • It is possible now to chain classes, which makes for more concise and better readable code.
  • The ‘MAX’ parameter has been added to the AMT File Controller, which limits the number of files read by _FileControl.FindFiles(). This may have performance benefits with large number of files.
  • A column has been added to the AMT Control Center > Job Management, which shows the name of the AMT Batch Controller processing the jobs. This column is invisible by default.

AMT 101

• 3 New items come with AMT 101:
  • IntelliSense has been added to the recently added possibility of chaining classes, making coding even easier and faster.
  • ClassName has been added in the Object Inspector for Consumable REST APIs, allowing to manually choose a class in case multiple classes have been defined.
  • Extra filtering options have been added to the AMT Control Center tabs ‘File Monitor’ and ‘Clean Sessions’, for selections on user and machine name.
    Note: When the details of the AMT File Controller connections are inspected, exception ‘Error getting data’ is raised, but the overview still functions. This is a known error, which will be solved in AMT 102.
• Attention: AMT Screens crashed when an ALT-key shortcut of ‘<’ or ‘>’ was specified, and in AMT 101 the handling of ALT-key shortcut specification of special characters has been improved to include special characters.
  Note: an ALT-key shortcut specification is now case insensitive!

AMT 102

• AMT 102 is built on .NET 6! Also ComScript and ComModule have been upgraded from .NET Framework to .NET 6.
  Please note:
  • .NET 6 needs to be installed on both servers and workstations
  • Web.config needs to be checked/updated for the AMT Application Center and AMT Control Center, as versions have been changed
  • all the Nuget packages have been upgraded to the latest possible version, unless breaking changes were encountered.
• Upgrade details:
  • Instead of registering the normal dll the new xxx.comhost.dll needs to be registered.
    
  • ComModule.dll -> ComModule.comhost.dll
    
  • ComScript.dll -> ComScript.comhost.dll
    
  • LionRepository.dll -> LionRepository.comhost.dll (only required if the Repository is approached through VBScript)
    Note: PowerShell needs to be upgraded to at least 7.2 for .NET 6 support!
• For more information on packages needed for installation, please refer to this help page.
• AMT 102 also contains several new items:
  • ‘Find’ functionality in the AMT Developer Studio for REST API web services
  • Statistics logging for REST API web services
  • Trace/debug logging for REST API web services
  • A codepage can be added to the AMT Control Center.
    CAUTION: only to be used for new installations, as a codepage may alter the contents of existing files!
  • Function ‘GetQueuedJobs’ has been added to the AMT Developer Studio. It has the same functionality as in the AMT ComScript module.

AMT 103

• AMT 103 is fully qualified for Windows 11!

AMT 104

• AMT 104 is fully qualified for Windows Server 2022!

AMT 107

• C2108-018 (AMT 92) Start position in Replace: Start position should not be a negative number, but it should not be ‘0’ either!
• C2207-107 AMT Screens as a self-contained executable: Make sure you have adequate rights for %USER%\Appdata\Local\Temp!

AMT 109

• Changes in the AMT Generator ensures AMT COBOL former A-Series non-unique indexes are now created exactly like the AMT LION ones. On an AMT COBOL ASeries application with non-unique indexes the AMT Reorganize will rebuild these indexes.
• 333147 / C2208-105: The CommManager and CommServer now only load necessary files. Please manually update the CommServer and CommManager once to get them back to the correct state!

AMT 110

• A new runtime behavior option called ‘Security checking GOTOFORM’ has been added to the AMT Control Center. When this option is enabled the runtime Business Logic checks if a user has rights to access the requested form if a GOTOFORM is executed.
• Audit logs are now implemented and enabled by default for starting, stopping, halting, and resuming Controllers or Servers.
• Please make sure you have upgraded the .NET Microsoft Windows Desktop app to the latest version 6.0.10. In version 6.0.3 there may be problems with the online help texts. To install:
  1. Go to https://dotnet.Microsoft.com/en-us/download/dotnet/6.0/runtime
  2. Select the ‘Windows’ section (default)
  3. Select the ‘Download x64’ section option from section ‘Run desktop apps’
  4. Install the update.

AMT 112

• C2103-122: In the current .NET version, it is not possible anymore to provide an XML config to a SOAP binding. To prevent confusion about settings that are used or not used for a Web Consumable, it has been decided to create fields with the implemented settings.
  
  In this change, fields for the Web Consumable settings have been added to the AMT Control Center. Also, the REO has been extended so that the necessary data conversion can be executed.
  
  IMPORTANT: Please remember to do an AMT Reorganize after installation of this release!

AMT 113

• C2203-016: Since the introduction of .NET Core, the AMT Reorganization application didn’t exit with the correct exit codes in batch mode anymore. Also, failed executed SQL statements didn’t lead to an exit code indicating the error.
  
  Now, a separate AMT Reorganization console application has been created, which can be used in, for example, scripts or DevOps pipelines. This separate console app makes exit codes work properly again. Furthermore, the use of exit codes has been improved so that failed SQL statements result in an exit code indicating an error.

• C2210-067: In case of exceptions within Reports, the Manual Recovery run failed due to a wrong job state.
  
  The handling of exceptions during running of reports has been improved, especially where deadlock and out of bound exceptions are concerned. These errors now result in a newly introduced job state named ‘ErrorWithRecover’. This state indicates that a job did raise an error at execution but it can be recovered manually.
  
  Note: Automatic recovery will be improved in AMT 114.

AMT 114

• Please be aware of the maximum size of XML documents (2147483647 bytes), which is set by .NET Runtime, and cannot be configured. If you run into problems with these documents, the solution can therefore only be found in splitting up input files or rearranging your processes!
  
  For more information, please go to our help pages.

AMT 118

• The OpConService has been revisited and the following has been changed:
  • Configuration of endpoint (including https and certificated) is now done within appsettings.json instead of the AmtOpConService.dll.config.
  • Http redirection functionality has been added.

IMPORTANT NOTE FOR UPGRADES: The settings have been moved from the .dll.config to appsettings.json!

AMT 119

• In the previous AMT product release, AMT 118, Provided Web Services were upgraded to .NET Core using CoreWCF. Please note that this change is still in preview!
• The Help Files have also been updated with documentation about .NET Core Provided Web Services: Creating a provided web service
• To find out how to upgrade Provided Web Services from .NET Framework to .NET Core, please visit the following page: Upgrading to .NET Core

AMT 120

• Please note that the ‘TransactionRenderer’ has been replaced by the ‘TransactionRendererBlazor’ in this release. Both renderers are available to you. Visit the following page to view the updated documentation: https://help.myasysco.com/lion/adding-the-necessary-websites-to-the-iis-core.html

AMT 121

• In this release, both the Blazor Web Client and the new Datagrid are in preview. For more information, please refer to this and this help page.

AMT 122

• Warning: As of December 13 2022, .NET Core 3.1 is no longer supported by Microsoft. This means that AMT versions starting at AMT 103 are no longer supported by the AMT Support team, either. For more information, please refer to this Microsoft page.

AMT 123

• Please be aware that the upcoming replacement of ASPX Web forms by Blazor based websites affects your automated test scripts, especially with regard to the IDs that are used to identify the different web elements!

AMT 125

• Please be aware that the COM services (comhost library) of the COM Module that is delivered with this AMT version only works for 64-bit applications! A version that works for 32-bit applications can be obtained from AMT Customer Support.

AMT 128

• The Blazor Web Client is out of preview! The ASPX Web Client is going to be phased out in the coming releases. For more information, please refer to this help page.

AMT 129

• Support for ASPX type Web Clients is going to be phased out in coming releases.

AMT 132

• CoreWcf usage for SOAP based AMT Provided Web Services is now out of preview. The sys.ini COREWCF=TRUE setting has been removed, as the usage of CoreWcf for SOAP based AMT Provided Web Services is currently standard AMT behavior.
  
• AMT used packages System.Data.SqlClient and System.IdentityModel.Tokens.Jwt have been updated to their latest versions.
  
• A session hijack vulnerability has been detected, you are affected if the Blazor Web Client is used in any version below AMT 132 (see #80670).
  
• Due to an upgrade of System.Data.SqlClient, earlier versions of PowerShell 7 cannot access this SqlClient anymore. To avoid conflicts, please update PowerShell 7 to the most recent version (currently 7.4.1), which will support the System.Data.SqlClient again.
  

AMT 133

• The authentication of the Blazor WebAPI’s NotifyHub component has been improved and secured. See release note item #80974 for more information.

AMT 134

• AMT now officially supports Microsoft SQL Server 2022.
• For users of the ASPX web client in AMT Cobol, web.config needs to be checked/updated, as the ‘System.Memory’ version has been updated. Please, add the following in the web.config (this has already been done in Web_Default.config):
  
  

<dependentAssembly>
        <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.1.2" newVersion="4.0.1.2" />
      </dependentAssembly>

AMT 137

• The AMT Blazor web client rendering has been thoroughly refactored in period leading up to this release. It has undergone several changes to improve performance, stabiliby and maintability of the product. The base and most common AMT controls are now feature complete. In the coming releases, more complex controls, such as the COBOL BMS Terminal, Dynamic Form control, SwitchTo and the Datagrid control, will be improved. Although the AMT Blazor web client has been rigorously tested, we advise you to do the same on your own specific environment.

AMT 140 -

• The refactoring of the AMT Blazor web client, first communicated in AMT 137, is nearing its end. With the exception of the Datagrid control (still in preview), the Mifo terminal and Macro functionality, work on the AMT controls and other functionality is complete. In the coming releases, the focus will shift to extensive testing, resolving edge cases and to implementing Macro functionality.

AMT 141 -

• ASPX Web Client is now replaced by the new Blazor Web Client. The ASPX Web Client is not deployed anymore and Web Deploy is skipped in this release. In a next release, Web Deploy will be removed completely.
• .NET Core needs to be upgraded to version 8.0.7. to support upgraded packages.

AMT 143 -

• Loading WSDL in a Consumable Web Service is no longer possible from this release.

AMT 146

Warning:

• As of November 12 2024, .NET 6 is no longer supported by Microsoft. This means that AMT versions starting at AMT 103 up up to and including AMT 134 are no longer supported by the AMT Support team, either. For more information, please refer to this Microsoft page.

Important changes have been made to External DLL Calls with LION Call Syntax:

• 32-bit calls are now obsolete for AMT – the parameters x86 or x64 have been removed.
• External DLL targets for .NET 8 are now always loaded internally within AMT. Therefore, the runtime behavior setting for this has been removed.
• New configuration settings in the sys.ini file:
  • AMTCALLDLLNET48 indicates which external DLLs are based on the .NET 4.8 framework.
  • AMTCALLDLLNET is used for external DLLs targeted at .NET 6.
  • The FIXEXTERNALCALL setting has been removed from the sys.ini file.

AMT 148

OpenID Connect authentication:

For the AMT Control Center, AMT Application Center and AMT Blazor WebClients, the OpenID Connect (OIDC) authentication method has been added.
OIDC replaces the Windows and Cookie authentication methods, and requires the addition of an OpenID Connect identity provider to the AMT system.

• The introduction of the OIDC method requires substantial changes to the appsettings files of the AMT web applications. Therefore, we strongly recommend you to merge the content of the existing appsettings files into a new copy of the sample appsettings files, instead of merely changing the existing files. See the OpenID Connect Authentication help page for configuration information.
• To facilitate existing AMT users, a translation table between OIDC identities and AMT user names has been added. This feature necessitates a reorganization of the AMT system database. See Identity Translation.
• Finally, an admin restore feature has been added to the AMT Reorganization tool, which adds a translation to the in-built Admin user in order to regain access to the AMT Control Center if required. See Restore admin.

Database wrappers change:

The Oracle, DB2 and PostgreSQL wrapper path and file names have been changed in this AMT release. This change requires an update of the database wrapper system variable value.

• AMT_ORACLE_WRAPPER : ..\AMTTools\OracleWrapper\Asysco.Amt.AmtOracleWrapper.dll
• AMT_DB2_WRAPPER : ..\AMTTools\DB2Wrapper\Asysco.Amt.AmtDb2Wrapper.dll
• AMT_POSTGRESQL_WRAPPER : ..\AMTTools\PostgreSqlWrapper\Asysco.Amt.AmtPostgreSqlWrapper.dll

AMT 149

• The Blazor WebAssembly Web Client has been removed, for security reasons and maintainability. Clients using the Blazor WebAssembly Web Client now have to use the Blazor Server Web Client.

AMT 150

• The naming of generated Consumable REST API classes has been changed.
  The class name is now derived from the operation path in the OpenAPI JSON file, instead of the tag name. If the JSON file of a Consumable REST API created before AMT 150 is reloaded, it is possible that the class names will be changed, which requires an update of the calls to the consumable.

AMT 153

• During an upgrade of the Repos database (‘Sync repository’ button), a process is started which removes all object relations to non-existing gensets from the database. This makes it possible for orphaned objects to be removed from the repository.