Description:
FX01929 is a cumulative hotfix and includes the following fixes:

MFCC-959 Resolves a problem with #(Date) and #(Time) tokens in the server file name when using checkpoint restart if a transfer is interrupted and then restarted.  After the transfer completed, the server file name was correct, but the audit and alerts were incorrectly displaying the server file name with the updated date and time of when the transfer was restarted.

MFCC-958 Resolves a problem where the file size was displayed as -1 when uploading large files with the HTML mode Internet Transfer Client.

MFCC-956 Resolves a problem with the HTML mode Internet Transfer Client where clicking the upload button again after the transfer started would restart the transfer.

MFCC-950 Updates the Internet Transfer Client Help to include the Thin, Java and HTML mode browser clients.

MFCC-949 Resolves missing permissions and Codebase manifest attributes warnings when using the Thin or Java Internet Transfer Clients and running JRE 1.7 update 45.

MFCC-948 Resolves a problem when using Chrome browser where the HTML Mode Internet Transfer Client incorrectly prompted that Java needs your permission to run.  

MFCC-942 Resolves a problem with Java Mode Internet Transfer Client downloading files when the transfer definition is not a directory transfer and the server file name is the path including the file name.

MFCC-935 Resolves a problem where clicking the "Refresh" button in the HTML or Java mode Internet Transfer Clients did not pick up changes made to the transfer definition or global changes after logging into the clients.

MFCC-931 Fixes a spelling error in a Command Center message when no Internet Server is installed and you navigate to Administration > Transfer Servers > FTP Server > Configure FTP Server.  The error now correctly reads "No Internet Server instances installed."

MFCC-871 Resolves a problem when using IE8 where the HTML mode Internet Transfer Client "Cancel" button was not working on uploads after a transfer was started.

The following fixes are included from FX01927:
==============================================

MFCC-932 Resolves a problem when using the MFT Java client to upload files to an MFT Server configured with SSO. Clicking on the transfer upload or download buttons returned an error "Your session has expired. Please click refresh button to login again." If you clicked the refresh button then the same error was displayed.

MFCC-892 Resolves a problem where alerts were not being processed when multiple wildcards were defined in the alert trigger criteria.  The problem was introduced in FX01902 which addressed an issue with special characters in the alert trigger criteria.  To use multiple wildcards the user must enter the data in this format:
<.*abc.*>.  When data is entered between brackets < and >, the data is treated as a JAVA regex (regular Expression).  Note that the rules for JAVA regex are different from standard UNIX regex.  
In  this example an alert will be triggered if the string "abc" appears anywhere in the field.
We will perform a Java regex compare on the data inside <>.  This applies to the following fields:
                : Platform server Node Name
                : Client File Name
                : Server File name
                : Transfer User Id
                : Process name
                : Transfer Description
If the data is not enclosed within <>, Java regex checking will not be performed; the standard checking will be performed.

MFCC-888 Resolves a problem when attempting to view the detailed audit record from the Platform Server Manual Poll. Clicking on the transaction ID resulted in the error: &ltTransaction ID> is an invalid Local Transaction Id.

MFCC-850 Resolves a problem with the Java client.  Message “Error: Session ID has expired” was displayed when the session timed out due to inactivity.  You are now brought to the logon page when the session times out.

MFCC-792 Resolves an SFTP issue when a key exchange is initiated.  There was a small window where it may have been possible for the client to send a message that was not allowed during key exchange. The following exceptions may result:
    Exception: com.maverick.ssh.SshException: Protocol error: expected packet type 30, got 94 [Unknown cause]
    Exception: com.maverick.sftp.SftpStatusException: Invalid file handle.: The handle is not valid!

Please contact TIBCO Support to download this hotfix.

TIBCO Managed File Transfer Command Center hotfix FX01929 is now available

Product: TIBCO Managed File Transfer Command Center Version: 7.2.1 OS: --------------------