Inconsistency between FIXT.1.1 Errata Release Notes and Spec Documents

, ,
1

Imported from previous forum

2

[ original email was from Francesc Prats - fprats@meff.com ]
Looking at FIXT.1.1 Errata Realese Notes (March’08) I see:

“… Logon - added the following fields: New Password (925), EncryptedPasswordMethod (1400), EncryptedPasswordLen (1401, EncryptedPassword (1402), EncryptedNewPasswordLen (1403), EncryptedNewPassword (1404), DefaultApplExtID (1407), DefaultCstmApplVerID (1408), SessionStatus (1409), Text (58), EncodedTextLen (354), EncodedText (355), RefApplExtID (1406), DefaultVerIndicator (1410)”

But I can’t see these changes in the corresponding specs documents (pdf or word)

3

Looking at FIXT.1.1 Errata Realese Notes (March’08) I see:

“… Logon - added the following fields: New Password (925),
EncryptedPasswordMethod (1400), EncryptedPasswordLen (1401,
EncryptedPassword (1402), EncryptedNewPasswordLen (1403),
EncryptedNewPassword (1404), DefaultApplExtID (1407),
DefaultCstmApplVerID (1408), SessionStatus (1409), Text (58),
EncodedTextLen (354), EncodedText (355), RefApplExtID (1406),
DefaultVerIndicator (1410)”

But I can’t see these changes in the corresponding specs documents
(pdf or word)

Capture the issue as #SPEC-298 - I will take a look today - thanks for reporting this Francesc.

4

The page has now been updated with the correct documentation. Apologies for the confusion. The release notes and FIXimate had the correct content, but the docs weren’t properly updated. If you find any further discrepancies please let us know.

Looking at FIXT.1.1 Errata Realese Notes (March’08) I see:

“… Logon - added the following fields: New Password (925),
EncryptedPasswordMethod (1400), EncryptedPasswordLen (1401,
EncryptedPassword (1402), EncryptedNewPasswordLen (1403),
EncryptedNewPassword (1404), DefaultApplExtID (1407),
DefaultCstmApplVerID (1408), SessionStatus (1409), Text (58),
EncodedTextLen (354), EncodedText (355), RefApplExtID (1406),
DefaultVerIndicator (1410)”

But I can’t see these changes in the corresponding specs documents
(pdf or word)

Capture the issue as #SPEC-298 - I will take a look today - thanks for
reporting this Francesc.