A bug was fixed in the TD that did not allow use of a defined BLANK page as the last screen in the recovery transaction.

Transcription

1 RELEASE NOTES Cleo Transaction Designer (TD) Version CD Contents install.exe - Transaction Designer installer - README.txt - these release notes - TDUserGuide.pdf - instructions for use of functions - QuickStart.pdf - instructions for installation, licensing, using sample - Conversion/convt.exe - installer for conversion utility Fixed in Version Version of Passport upgraded from to Fixed in Version The TD can now be installed on Windows 10 and Windows 2012 platforms. The Install Anywhere script was modified to handle the new platforms. Install Anywhere 2014 is used. Registration of the TD is no longer done. Instead assoc and ftype commands are used to set the.zws files to use Passport.exe as the default application to use. A new version of Rocket Software s TN3270 Emulator, Passport, was needed to work with Windows 2012 and Windows 10. Version 21.1 is now used. The TD Launcher and Validator had to be modified to use a different HLLAPI Session mapping table, and to update.zws tn3270 configuration data before launching Passport in the background. The.zws file format changed with the Version 21.1 Passport release, so this was necessary. clips and validate transactions was set to expire on 8/31/16. The license now has been extended to expire on 7/31/17. A bug was fixed in the TD that did not allow use of a defined BLANK page as the last screen in the recovery transaction. Fixed in Version A bug was fixed in the TD that did not allow use of a defined BLANK page as the last screen in the recovery transaction. Fixed in Version clips and validate transactions was set to expire on 8/31/15. The license now has been extended to expire on 8/31/16.

2 Fixed in Version The TD was modified to not allow a formatted field or unformatted field to be defined that has a start cursor position greater than the end cursor position. Instead the field is ended at the end of the screen. Allowing a field to wrap around the screen caused problems in creating illegal fields with negative lengths in the transaction xml files. So that when the TP or TD Validator tried to run the transaction, a fatal error occurred. Fixed in Version clips and validate transactions was set to expire on 8/31/14. The license now has been extended to expire on 8/31/15. Fixed in Version clips and validate transactions was set to expire on 8/31/14. The license now has been extended to expire on 8/31/15. Fixed in Version clips and validate transactions was set to expire on 8/30/13. The license now has been extended to expire on 8/31/14. The Cleo TD s TN3270 Emulator, from Zephyr, Passport.exe expired for Version on September 1, Zephyr had incorrectly sent us a Passport.exe license file with an expiration date, when they should have sent us a PERMANENT Passport.exe License File. Had to create with the new License File as part of the passport.key file that gets installed with the Cleo TD Version to correct the problem. New in Version Now whenever the TD opens an existing Transaction Set, all the.xml and.htd files are checked to see if they have an attribute of READ ONLY, and if so, they are all changed to have an attribute of WRITABLE. Some customers encountered problems in earlier versions of the TD with transaction sets that had READ ONLY.xml and/or.htd files. As a result the TD was unable to open the transaction set. Now the files are set to WRITABLE when the transaction set is opened. This enhancement required the use of JAVA 1.6 to build the TD. Fixed in Version

3 The Cleo TD now correctly checks an existing transaction set when it is opened when the TD starts up or when it is opened from the FILE/OPEN menu selection, to see if it has ENCRYPTED recordedclips and/or hosttrans.htd files. If so, the files are converted to non-encrypted format. Also, each existing transaction set is checked for READ ONLY.xml and/or.htd files, and if READ ONLY.xml and/or.htd files are found, they are changed to WRITABLE. clips and validate transactions was set to expire on 7/31/12. The license now has been extended to expire on 7/31/13. Fixed in Version The Cleo TD s TN3270 Emulator, from Zephyr, Passport.exe expired for Version on September 1, Zephyr had incorrectly sent us a Passport.exe license file with an expiration date, when they should have sent us a PERMANENT Passport.exe License File. Had to create with the new License File as part of the passport.key file that gets installed with the Cleo TD Version to correct the problem. Fixed in Version The Cleo TD Validator would not work for SSL Host Connections. When doing RUN NOW a Java Stack Trace would be output and a message about not being able to connect to the host would be output. Now the TD Validator correctly handles SSL Host Connections. The Validator will now run transactions when using a SSL Host Connection. New in Version The Cleo TD now no longer encrypts the recordedclips.htd and hosttrans.htd files. The Cleo TD will automatically try to convert old transaction sets that have encrypted recordedclips.htd and hosttrans.htd files and decrypt those htd files. NOTE: When installing on Windows 7 and Vista it is recommended to install in a directory other than the "Program Files" directory, since writing data in that directory is restricted on Windows 7 and Vista. Fixed in Version The Cleo TD now closes opened recording Host Sessions when a new Recording Host Session is opened. The Cleo TD throws exceptions now for SAXBuilder routines since a newer Java JDOM is being used.

4 New in Version The Cleo TD can now be installed on the following Windows Operating Systems Windows 7, Windows 2008, Windows 2008 R2, Windows Vista, Windows XP Professional, Windows 2000 Advanced Server, Windows 2000 Server, Windows 2000 Professional. New in Version Terminal screen sizes mod3 (32x80), mod4 (43x80), and mod5 (27x132) are now supported in the recorder and validator functions. Note that the host setting file (sess<n>.zcc) in the folder where the TD was installed must be edited to change the screen size (3270ScreenSize) used when connecting to the host. New in Version Added tn3270/tn5250 SSL support to the recorder and validator functions. Problem Fixed in version Using right-click on a transaction name to add an Any screen no longer corrupts previously added Any screens having branch commands. New in Version Licensing has been modified to use the host name instead of the generated host id. This requires that all 3.1.3, 3.3 and users of 3270 Transaction Designer upgrading to obtain a new license based on the host name. Capability added to import unrecognized screens captured by Transaction Processor, version or later. The screens are saved in *.htp files in the CleoTP/scr_dump folder. To import using TD, select File/Import/Recorded Clips and specify location of *.htp file(s) containing captured screens. Modified the parked screen in the sample transaction set, resulting in changes to the Login, Park, and Logout transactions. Added getallscreens transaction to provide an example of a rule; it must be run after the Search transaction. Problems Fixed in Version Now handles tohost fields that wrap from the bottom of the screen to the top.

5 New in version Licensing no longer requires network connection. "Optional" checkbox added to tohost field definition to designate the field as not requiring input before sending to the host. That is, the TP will not populate the tohost field value unless the addinput function has been executed for the field. Use of this feature requires version or later of the Transaction Processor. New in Version Added concept of global screens whereby a screen containing text identifiers can be used as a base screen for any other transaction screens having the same contents. This simplifies the screen identification process since the user is only required to specify text identifiers on a particular screen once. - A new feature allows a user of the Transaction Designer to create and publish the minimum VoiceXML code necessary to invoke the VoiceXML Connector. (The VoiceXML connector provides VoiceXML applications with the capability to invoke transactions through the Transaction Processor.) NOTE: This is not a general purpose VoiceXML editor and does not generate a full VoiceXML application. See the Transaction Designer User's Guide, Appendix D, for details. - Now supports importing one or more transactions from other transaction sets into the current transaction set opened using the Transaction Designer. Known Problems Importing transactions containing branch and rule commands is faulty. When importing a transaction with a screen containing a branch command, double clicking on the tohost branch command value shows blanks for all screens and transactions. This is because the imported screens and transactions have been renamed, but not in the branch command. Also, it is possible to import a screen with a rule command, but not the associated transactions within the rule, and a publish works. The rule command contains an undefined transaction, not reported until run by the TP. Workaround: Rule and branch commands in imported transactions must be recreated TD does not prevent renaming or deleting a from host field used in a rule. If a from host field is deleted or renamed AFTER a rule was defined using it, the rule command will not work as expected when run by the Transaction Processor.

6 If a transaction set containing BLANK and/or ANY screens is imported, an error is reported, "There was an error importing recorded clips." even though the import function was successful Recorder and Validator cannot connect to the host using emulation software on a Unix system From host fields should not be added to blank screens, yet the TD allows it Once the user changes a base screen to an "ANY" screen, it cannot be changed back. Workaround: Delete the "Any" screen and re-add the transaction screen using copy/paste, or by copying a recorded screen into the transaction and setting the base screen "Cancel" button does not function in the host setting dialog of the Validator Workaround: Close the dialog box by clicking the "X" in the upper right corner TD Recorder does not display host PROG checks on the status line All fields on the TD recorder screen are considered alphanumeric, meaning that non-numeric characters can be typed into numeric fields without causing the keyboard to lock If the recorder attempts to connect to an invalid host address or port using the local settings, there is no indication in the status line that the connect failed. Workaround: Check for a blank screen and a status line with no indicators. If the starting host screen should not be blank, retry using Connect under the Session menu and recheck recorder host settings Removing TD Conversion Utility results in inability to run the TD on some platforms. Workaround: Do not remove the TD Conversion Utility. If it is removed, the TD must be re-installed.