AMT Release Notes

AMT 71

Released: 19 Jun 2020.
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 319989

Object fields on insertable forms did not work with LoadAndRun.js files.

LoadAndRun.js files now also work with object fields on insertable forms.
FIX AMT 71 Low
AMT LION | AMT COBOL AmtTools Reo 329244

When an application was analysed and reorganized the logs didn't consistently place the threadID in the log, making it harder to read the logs correctly.

Now the AMT Reorganize logs always contain a threadID.
CHANGE AMT 71 Low
AMT LION | AMT COBOL Services Print Controller C2004-090

As a preparation for the move to .NET Core, the WCF web service used for communicating between the system database and remote AMT Print Controllers had to be replaced, as WCF is not supported in .NET Core.

The WCF web service has been replaced by an ASP.NET Core web API. Unlike the WCF web service, this is not hosted as part of the AMT Control Center Business Logic, but as a separate application in IIS. For security reasons, the web API is not configured in new installations by default. Customers who wish to use a remote AMT Print Controller will have to follow some configuration steps, which are described in the AMT help files.
CHANGE AMT 71 Low
AMT COBOL Runtime Various C2005-009

The AMT Transaction Server would go down randomly with a message that the connection to an agent was lost.

There was a threading problem with the named pipe connection between the AMT Transaction Server and AMT Transaction Agent. The threading issue has been solved, the AMT Transaction Server no longer crashes.
FIX AMT 71 Low
AMT LION | AMT COBOL Runtime Various C2005-019

AMT now generates all assemblies as .NET Standard, in preperation for the move to .NET Core.
CHANGE AMT 71 Low
AMT LION Runtime Various C2005-031

The current solution for drawing charts at runtime was not supported in .NET Core.

As a temporary solution, the drawing of charts at runtime is handled via the AmtCallDll process, which will remain in .NET Framework.
CHANGE AMT 71 Low
AMT LION | AMT COBOL Runtime Various C2005-038

.NET Core does not support the method used to run reports inside the AMT Batch Controller. As this was part of the move to .NET Core, an alternative solution was needed.

The AMT Batch Controller now uses an agent process to run reports. New agents are automatically started when new files are generated.
CHANGE AMT 71 Low
AMT LION Runtime AmtScreens 329389

The sign in Editboxes with signed values was taken into account in the logic that triggered the Autotab.

The sign is now ignored when a value's length is calculated, so Autotab is triggered correctly.
FIX AMT 71 Low
AMT COBOL Runtime Various C2005-045

Initialization of memory was incorrect for SET ADDRESS OFF on group levels, which caused members to get separated from the group.

Group Level members are now initialized correctly.
CHANGE AMT 71 Low
AMT LION Runtime AmtScreens 329388

If a Label in AMT Screens was empty, an underline character was shown.

No character is shown now if a Label is empty.
FIX AMT 71 Low
AMT COBOL Developer Code Logic C2005-049

Right-clicking a Boolean in a COBOL program defined in a COBOL copy resolved the line number of the Boolean inside the COBOL copy incorrectly.

Clicking the Boolean inside the popup that appears if the Boolean is right-clicked now results in the correct line in the COBOL copy being shown.
FIX AMT 71 Low
AMT LION Developer Web Services 329379

Reading the WSDL did not process Enum types, and empty Complex types were ignored. An exception was thrown for unknown types right after reading the WSDL, which crashed the AMT Developer.

Enum types and empty Complex types are now processed correctly. Also the AMT Developer crash has been corrected and errors are shown in the logging as expected .
FIX AMT 71 Low
AMT LION Developer Web Services 329380

Consumable Web Services gave an error when the WSDL was loaded because the order of operations and bindings did not match.

The bindings are now loaded by name and it is no longer presumed that the index is the same for both.
FIX AMT 71 Low
AMT LION Developer Web Services 329381

A C# error was raised if the operation name and parameter name were the same in a Consumable Web Service. The generated class was incorrect as C# does not allow for member names and their enclosing type to be the same.

The generated class has been corrected.
FIX AMT 71 Low
AMT LION Developer Web Services 329039

The generated WSDL for Provided Web Services was incomplete, Complex types were missing.

Generation of the WSDL has been removed, it now needs to be fetched from the deployed service directly by using '?singlewsdl' as postfix.
CHANGE AMT 71 Low
AMT LION Developer Web Services C2005-056

Web service enabled forms were not shown in the provided webservice if the name was mixed-case.

Mixed-case forms that are web service enabled are now also shown.
FIX AMT 71 Low
AMT LION | AMT COBOL Developer Various 329334

ILionApplicaton.GetGenSets() only returned the first generation set of an application instead of all the generation sets.

This has been resolved, all generation sets belonging to the application are now returned.
FIX AMT 71 Low
AMT COBOL Runtime Various C2005-060

SQL cursors with the 'WITH HOLD' option used a separate DB connection if the USEAMTCURSOR setting was used. This caused locking issues in some situations, because of the READ COMMITTED isolation level that is used for DB2 migrations.

This issue has been resolved.
FIX AMT 71 Low
AMT COBOL Runtime Various C2005-065

Doing transmits in quick succession caused the screen not to be responsive anymore.

This issue has been resolved in the AMT Transaction Server. The list of active transactions is now updated immediately after the COBOL program has finished (in the return method). This enables the AMT Transaction Server to handle a new transaction sooner.
FIX AMT 71 Low
AMT COBOL Runtime Various 329417

If an IBM COBOL numeric field hex 00 was sent through the ComModule it was not received as hex 00 but as spaces.

Now the transaction server receives hex 00 correctly and makes the attribute value hex 80.
FIX AMT 71 Low