Professional Documents
Culture Documents
Access7120 Win32 RL
Access7120 Win32 RL
20
Release Letter
02 September 2016
Alliance Access 7.1.20
Release Letter Table of Contents
Table of Contents
Practical Information............................................................................................................................... 4
1 Release Overview.......................................................................................................................... 5
1.1 Purpose of this Document............................................................................................................. 5
1.2 Enhancements and Features........................................................................................................ 5
1.3 Resolved Problems..................................................................................................................... 12
1.4 Software Distribution................................................................................................................... 12
1.5 System Requirements................................................................................................................. 12
1.6 Documentation............................................................................................................................ 17
1.7 Warnings and Known Issues....................................................................................................... 18
1.8 Obsolete Functionality................................................................................................................. 19
1.9 Other Information........................................................................................................................ 20
3 Support......................................................................................................................................... 26
02 September 2016 2
Alliance Access 7.1.20
Release Letter Table of Contents
Legal Notices......................................................................................................................................... 47
02 September 2016 3
Alliance Access 7.1.20
Release Letter Practical Information
Practical Information
Installation type Mandatory by 20 November 2016
02 September 2016 4
Alliance Access 7.1.20
Release Letter Release Overview
1 Release Overview
1.1 Purpose of this Document
This document contains release information for Alliance Access 7.1.20 (including Alliance Web
Platform Server-Embedded GUI package and Alliance Workstation).
Alliance Access 7.1.20 supports the Standards MT November 2016 release.
If you have not yet started to use the browser-based GUI on Alliance Web Platform Server-
Embedded, this is a good moment to plan ahead. This update brings the final functionality in
Alliance Web Platform Server-Embedded that will allow every remaining Alliance Workstation
user to complete the migration. Deploying Alliance Web Platform Server-Embedded will reduce
the effort you need to deploy Alliance Workstation on the different end-user systems. Alliance
Workstation end-of-life was announced in March 2015 and is planned for March 2017, without
any support extension foreseen. Alliance Web Platform Server-Embedded and Alliance
Workstation can be used in parallel to ease the transition.
First read this release letter, and then use the other documentation provided for more detailed
information (for a complete list of the documentation, see Documentation on page 17).
1.2.1 Overview
Alliance Access 7.1.20 includes all changes introduced since release 7.1 (7.1.10, 7.1.11, 7.1.12,
7.1.13, 7.1.14, and 7.1.15). If you are upgrading from a version earlier than 7.1.15, please read
the 7.1.15 Release Letter, where significant enhancements are described.
This update contains the following enhancements and new features:
• Updates for Standards MT November 2016
• Support for two-factor authentication
• Password policy changed
• CREST over SWIFTNet enhancement
• Global payments innovation initiative (gpii)
• New XMLv2 revision
• Change the syntax version on multiple LTs simultaneously
• Locked message in text_modification, change in behaviour
• Alarms visibility and actions, change in functionality
• New licensing configuration application
• Additional validation of existing RMA
• Local printer support
• RESTful API available to provide browser-based GUI
02 September 2016 5
Alliance Access 7.1.20
Release Letter Release Overview
02 September 2016 6
Alliance Access 7.1.20
Release Letter Release Overview
Note For more information on TOTP technology see RFC 6238 for formal specifications
or Wikipedia for a less technical description.
Parameter Description
System – Disable The number of calendar days after which an operator is disabled if there
Period was no successful sign-on.
Change: minimum value increased to 1, maximum value reduced to 63
(from 999). Default value is 30.
If your current value was 0 before the upgrade, it will become 30 after the
upgrade.
Signon – Timeout The number of seconds that an operator can be inactive. Change:
maximum value reduced to 1800 (from 28800).
Signoff - Timeout The number of seconds after an inactivity time out before an operator
signed on using Alliance Workstation is automatically signed off.
Change: minimum value increased to 60 (from 0).
02 September 2016 7
Alliance Access 7.1.20
Release Letter Release Overview
Parameter Description
Password – Master The number of days after which the Master password has to be changed.
Period
Change: minimum value increased to 1, maximum value reduced to 120
(from 365).
Password – User Period The number of days after which the user password has to be changed.
For more information, see the section User Management in the Configuration Guide.
02 September 2016 8
Alliance Access 7.1.20
Release Letter Release Overview
For this purpose two new fields have been added in the block 3 of the FIN messages:
• Field 111 Service type identifier – a new field in FIN block 3
• Field 121 Unique end-to-end transaction reference – also known as UETR – a new field in
FIN block 3
02 September 2016 9
Alliance Access 7.1.20
Release Letter Release Overview
to select one or multiple LT and assign a new syntax to all the LTs’ list in one operation. The
operator will be prompted to select the syntax to be applied from a list of available syntax
versions.
For more information, see the section Modify the Syntax Table Assigned to One or More Logical
Terminals in the Configuration Guide.
In Alliance Access 7.1.15, the new concept of Locked Templates was introduced, allowing to
create templates where only some fields can be edited by the person who creates a message
from the template.
The behaviour of messages created from a locked template has been changed in 7.1.20. When
such a message arrives in the modification queue it will now be fully editable.
The “locked-template” functionality was introduced to limit what a user can enter in a message,
and this user is not expected to be able to modify it afterwards. The operator who only creates
messages from locked template should not have the permission to make modifications.
However, another operator who has the credential to modify messages should be able to repair
the message should it arrive in the text modification queue. This is why the change has been
introduced.
For more information, see the section Locked Message Templates in the Message Management
Guide.
02 September 2016 10
Alliance Access 7.1.20
Release Letter Release Overview
02 September 2016 11
Alliance Access 7.1.20
Release Letter Release Overview
This document covers recommended security control guidelines which are designed to assist
customers in protecting the deployment, access to, and use of, Alliance products. Broadly, the
document contains information on:
• SWIFT security governance for customers, including the definition of security roles and
segregation of duties
• Securing local server environments, including the physical and logical access controls that
secure the Alliance servers with servers they communicate with
• Securing local client environments, including the physical and logical access controls that
secure end user workstations connections with servers hosting Alliance software
• Securing local application environments, including support for 2FA, management of RMA
control, and enhanced confidentiality, integrity and authentication
• Local network security controls, including network segregation
• Other security recommendations, including detection, backup, resilience and incident
management.
02 September 2016 12
Alliance Access 7.1.20
Release Letter Release Overview
02 September 2016 13
Alliance Access 7.1.20
Release Letter Release Overview
For UNIX and Linux, Alliance Access 7.1.20 has specific system requirements. For more
information, see the user limit requirements in the Installation Guide for AIX, Linux, or Oracle
Solaris.
02 September 2016 14
Alliance Access 7.1.20
Release Letter Release Overview
02 September 2016 15
Alliance Access 7.1.20
Release Letter Release Overview
02 September 2016 16
Alliance Access 7.1.20
Release Letter Release Overview
1.5.7.6 IBM MQ
If you want to use the IBM MQ Host Adapter integrated in Alliance Access 7.1.20, then one of
the following IBM MQ software versions must be installed:
• IBM MQ 7.0.1 (not supported by IBM since September 3, 2015)
• IBM MQ 7.0.1.3
• IBM MQ 7.5.0.2
Note The MQ versions are not necessarily supported by IBM on all the OS versions that
we qualify against. Only the MQ/OS combinations supported by IBM are supported
by SWIFT. See the OS Levels and Patches Baseline document, dated 27 March
2015, for information in which versions are supported on which platforms.
Even if the IBM MQ software is installed in the default directories, then you must
specify the environment variable to indicate the location of the IBM MQ libraries.
For more details, see the installation directory for IBM MQ in the Configuration
Guide. See also Knowledge Base tip 5020614.
In order to use Alliance Access with IBM MQ 8.0 Server, you need to install an IBM
MQ 7.x client on your Alliance Access system that is compatible with your IBM MQ
8.0 server environment. For compatibility details, see the IBM website. Alliance
Access 7.1.20 is not compatible with IBM MQ 8.0 client. For more information, see
Knowledge Base tip 5020656.
1.6 Documentation
This lists the documentation and addiitonal resources for Alliance Access.
The following documents have been updated to describe additional functionality (and change
requests) addressed in Alliance Access 7.1.20 :
• Administration Guide - AIX
• ADK GUI REST API Developer Guide (limited distribution)
• Administration Guide - Linux
• Administration Guide - Oracle Solaris
• Administration Guide - Windows
02 September 2016 17
Alliance Access 7.1.20
Release Letter Release Overview
The following table lists the known issue that was identified during the qualification phase and
that has a potential impact on the main message flow, or on specific activities such as daily
operations or configuration.
02 September 2016 18
Alliance Access 7.1.20
Release Letter Release Overview
02 September 2016 19
Alliance Access 7.1.20
Release Letter Release Overview
02 September 2016 20
Alliance Access 7.1.20
Release Letter Installation and Upgrade
Important After the installation, you will need to install the Alliance Security Update 2016-08.
Important If you are upgrading from a version earlier than 7.1.15, please read the following
information.
Important After the upgrade, you will need to install the Alliance Security Update 2016-08.
02 September 2016 21
Alliance Access 7.1.20
Release Letter Installation and Upgrade
The number of user preferences has been reduced. For the user preferences which have been
removed, the last used value will be used the next time you use the application or field. In
several other places the last used value is proposed by default to enhance the user experience.
For example, in the 7.1.20 Message Management GUI, the user Preferences does not contain
the Default Sender Logical Terminal and the Default Fin Category. The last selected values are
used instead in Message Creation.
Changes to Permissions
New permissions
Compared to Alliance Access 7.1.1x, the following permissions have been introduced to support
the new features described earlier:
Permission Description
Mesg Creation, Add/ Mod/ Rem Templ, locked Controls whether an operator can create MT/MX
messages from locked templates
Mesg Creation, Create Message, From Locked Controls whether an operator can only manage
Templates only MT/MX message templates that are locked.
Changed permissions
Compared to Alliance Access 7.1.1x, the following permissions have been changed:
Permission Change
Removed permissions
Permission Description
Message Search count The count permission was linked to the search
permission. The count feature is now available to all
users that have access to the message search
screens (message search permission).
02 September 2016 22
Alliance Access 7.1.20
Release Letter Installation and Upgrade
Changes to Parameters
The following parameters have been introduced to support the new features:
Parameter Description
Receive LAU Grace period Operators with the Security Definition permission (that is, LSO and
RSO), can define a grace period duration (in days) during which
both the new and the previous LAU keys are valid at reception. The
grace period starts when a new LAU key is assigned to a message
partner.
Possible values: 0 through 90. Default value is 0.
Msg Templ Approval Controls whether messages can only be created from approved
normal templates (set to On) or created from approved or non-
approved templates (set to Off).
Possible values: On or Off. Default value is Off.
Ref data upload auditing When set to On, events are logged when audit records are added,
updated or deleted during BIC upload/ SWIFTRef data upload.
Possible values: On or Off. Default value is Off.
Store Message Content When activated (parameter set to "Yes"), the full content of the
messages are stored in the messages interventions.
• A Message as Transmitted, Message Content intervention is
created when sending a message to a Message Partner, to
SWIFT, or to SWIFTNet
• A Message as Received, Message Content intervention is
created when receiving a message from a Message Partner,
from SWIFT, or from SWIFTNet
Note This feature has been developed specifically for test
purposes only. Due to the nature of this feature and
the disk I/O it needs, performance will be significantly
reduced when this feature is switched on.
Maximum Message Age If a message instance stays longer in the queue than the value set,
then this triggers an event and puts the queue in an exceptional
state.
Changes to Events
See Knowledge Base tip 5021028 for a detailed list of added, updated and removed events.
02 September 2016 23
Alliance Access 7.1.20
Release Letter Installation and Upgrade
2.2.1 Overview
See the Alliance Web Platform Server-Embedded 7.0.65 Installation Guide (AIX, Linux, Oracle
Solaris, Windows) for information about the installation and configuration of the GUI packages.
Note New versions of these guides will be published for Alliance Web Platform Server-
Embedded 7.0.70.
If you have not installed Alliance Access 7.1.15, Alliance Access 7.1.20 introduces a new default
application group, which combines the four existing application groups into one, so all
operations can be handled from the same menu without the need to create custom application
groups.
To locate the packages in the downloaded file, navigate to the GUIPackages directory. The
packages are locate in a single .ear file: access_7_1_20.ear.
Note To preserve user preferences, ensure that you install the 7.1.20 GUI packages
before removing the 7.1 or 7.1.1x package.
02 September 2016 24
Alliance Access 7.1.20
Release Letter Installation and Upgrade
02 September 2016 25
Alliance Access 7.1.20
Release Letter Support
3 Support
Support for SWIFT customers
By default, SWIFT is the single point of contact to report all problems and queries that relate to
SWIFT services and products. Support is available to all SWIFT customers.
Individuals within a customer organisation must register to use the Support service.
For more information about the different services that SWIFT offers as part of the support
packages and the procedure to order support, see Comparison of support packages on
swift.com.
Related information
For more information about Support services, see the service description related to the
applicable support package:
Support documentation
02 September 2016 26
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
F32A,F32B, F19,F32A,F
102 Seq A.F20 Seq C.F32A Seq C.F32A Seq C.F32A F33B,F71F, 32B,F33B,F F32A
F71G 71F,F71G
F32A,F32B, F19,F32A,F
102.
Seq A.F20 Seq C.F32A Seq C.F32A Seq C.F32A F33B,F71F, 32B,F33B,F F32A
STP
F71G 71F,F71G
F32A,F33B, F32A,F33B,
103 F20 F32A F32A F32A F32A
F71F,F71G F71F,F71G
103.
F32A,F33B, F32A,F33B,
REM F20 F32A F32A F32A F32A
F71F,F71G F71F,F71G
IT
F19,F32B,F
F32B,F33B,
104 Seq A.F20 Seq C.F32B Seq C.F19 F30 33B,F71F,F F30
F71F,F71G
71G
105 F20
02 September 2016 27
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
F19,F32B,F
F32B,F33B,
107 Seq A.F20 Seq B.F32B Seq C.F19 F30 33B,F71F,F F30
F71F,F71G
71G
192 F20
195 F20
196 F20
198 F20
199 F20
202.
F20 F32A F32A F32A F32A,F33B F32A,F33B F32A
COV
204 Seq A.F20 Seq B.F32B Seq A.F19 Seq A.F30 F32B F19,F32B F30
205.
F20 F32A F32A F32A F32A,F33B F32A,F33B F32A
COV
F32A,F71F, F19,F32A,F
F71G,F71H, 71F,F71G,F
256 Seq A.F20 Seq C.F32A Seq C.F32A Seq C.F32A F32A,F30
F71J,F71K, 71H,F71J,F
F71L 71K,F71L
02 September 2016 28
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
292 F20
295 F20
296 F20
298 F20
299 F20
F32B,F33B, F32B,F33B,
303 Seq A.F20 Seq B.F32B Seq B.F32B Seq B.F30V Seq B.F30V
F34B,F39P F34B,F39P
F32B,F33B, F32B,F33B,
305 F20 F32B F32B F34P,F34R
F34P,F34R F34P,F34R
F32B,F33B, F32B,F33B,
Seq Seq
306 Seq A.F20 Seq B.F30X F33E,F34B, F33E,F34B, Seq B.F30X
B1.F34B B1.F34B
F71F,F32H F71F,F32H
F32B,F32H, F32B,F32H,
320 Seq A.F20 Seq B.F32B Seq B.F32B Seq B.F30V F33B,F33E, F33B,F33E, Seq B.F30V
F34E,F71F F34E,F71F
02 September 2016 29
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
Seq
F32B,F71F, F32B,F71F,
340 Seq A.F20 Seq B.F32B Seq B.F32B Seq B.F30F B.F30F,Seq
F32H F32H
F.F30F
341 Seq A.F20 Seq B.F32B Seq B.F32B Seq B.F30F F32B,F34E F32B,F34E Seq B.F30F
F32B,F33B, F32B,F33B,
350 Seq A.F20 Seq B.F32B Seq B.F32B Seq B.F30V F33E,F34B, F33E,F34B, Seq B.F30V
F71F F71F
F32B,F32M, F32B,F32M,
360 Seq A.F20 Seq A.F32B Seq A.F32B Seq A.F30V Seq A.F30V
F32U,F71F F32U,F71F
F32B,F32M, F32B,F32M,
361 Seq A.F20 Seq A.F32B Seq A.F32B Seq A.F30V F32U,F33B, F32U,F33B, Seq A.F30V
F71F F71F
F32H,F32M, F32H,F32M,
362 Seq A.F20 Seq B.F33F Seq B.F33F Seq A.F30V Seq A.F30V
F33E,F33F F33E,F33F
F32B,F32G, F32B,F32G,
364 Seq A.F20 Seq A.F32B Seq A.F32B Seq A.F30V Seq A.F30V
F32M F32M
F32B,F32G, F32B,F32G,
365 Seq A.F20 Seq A.F32B Seq A.F32B Seq A.F30V F32M,F33B, F32M,F33B, Seq A.F30V
F33E F33E
370 Seq A.F20C Seq B.F19A Seq B.F19A Seq B.F98A Seq B.F19A Seq B.F19A Seq B.F98A
Seq Seq
381 Seq A.F20C Seq B.F19B Seq B.F19B B.F98A:VAL B.F98A:VAL
U U
392 F20
395 F20
396 F20
398 F20
02 September 2016 30
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
399 F20
Seq Seq
B.F32A, B.F32A,
F32A,F32B, F32A,F32B,
416 Seq A.F20 Seq Seq Seq B.F32A F32A
F32K,F71F F32K,F71F
B.F32B, B.F32B,
Seq B.F32K Seq B.F32K
Seq Seq
A.F32A, A.F32A,
Seq Seq
F32A,F32K, F32A,F32K,
430 Seq A.F20 A.F32K, A.F32K, Seq A.F32A F32A,F33A
F33A,F33K F33A,F33K
Seq Seq
A.F33A, A.F33A,
Seq A.F33K Seq A.F33K
F32A,F32B, F32A,F32B,
456 F20 F32A,F32B F32A,F32B F32A F32A,F33D
F33D F33D
492 F20
495 F20
496 F20
498 F20
02 September 2016 31
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
499 F20
Seq
500 Seq A.F20C B.F98A,
Seq B.F98C
Seq
501 Seq A.F20C B.F98A,
Seq B.F98C
Seq Seq
B.F19A:OR B.F19A:OR
502 Seq A.F20C DR, Seq DR, Seq
B.F19A:CA B.F19A:CA
NC(1) NC(1)
Seq
505 A.F20C:SE
ME
Seq
506 A.F20C:SE
ME
Seq
507 A.F20C:SE
ME
Seq
508 A.F20C:SE
ME
Seq
B.F98A:RR
510 Seq A.F20C EG, Seq
B.F98C:RR
EG
02 September 2016 32
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
Seq
Seq Seq C.F98A:TR
C.F19A, C.F19A, AD, Seq
513 Seq A.F20C Seq Seq C.F98C:TR
D3.F19A:SE D3.F19A:SE AD, Seq
TT TT C.F98E:TR
AD
Seq
Seq Seq B.F98A:TRA
B.F19A:SET B.F19A:SET D, Seq
514 Seq A.F20C T, Seq T, Seq B.F98C:TR
C3.F19A:SE C3.F19A:SE AD, Seq
TT TT B.F98E:TRA
D
Seq Seq
516 Seq A.F20 B.F32A, B.F32A, Seq B.F32A F32A,F32B F32A,F32B F32A
Seq B.F32B Seq B.F32B
Seq
519 Seq A.F20C B.F98A,
Seq B.F98C
Seq
524 Seq A.F20C B.F98A,
Seq B.F98C
Seq
Seq Seq Seq A.F98A:EX
527 A.F20C:SE B.F19A:TRA B.F19A:TRA RQ, Seq
ME A A A.F98C:EX
RQ
02 September 2016 33
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
Seq
B.F98A:SET
540 Seq A.F20C T, Seq
B.F98C:SET
T
Seq
Seq Seq B.F98A:SET Seq Seq
541 Seq A.F20C E3.F19A:SE E3.F19A:SE T, Seq E3.F19A:SE E3.F19A:SE
TT TT B.F98C:SET TT TT
T
Seq
B.F98A:SET
542 Seq A.F20C T, Seq
B.F98C:SET
T
Seq
Seq Seq B.F98A:SET Seq Seq
543 Seq A.F20C E3.F19A:SE E3.F19A:SE T, Seq E3.F19A:SE E3.F19A:SE
TT TT B.F98C:SET TT TT
T
Seq
B.F98A:ESE
544 Seq A.F20C T, Seq
B.F98C:ES
ET
Seq
Seq Seq B.F98A:ESE
545 Seq A.F20C E3.F19A:ES E3.F19A:ES T, Seq
TT TT B.F98C:ES
ET
02 September 2016 34
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
Seq
B.F98A:ESE
546 Seq A.F20C T, Seq
B.F98C:ES
ET
Seq
Seq Seq B.F98A:ESE
547 Seq A.F20C E3.F19A:ES E3.F19A:ES T, Seq
TT TT B.F98C:ES
ET
Seq
Seq Seq B.F98A:SET
548 Seq A.F20C B.F19A:SET B.F19A:SET T, Seq
T T B.F98C:SET
T
Seq
Seq Seq Seq A.F98A:EX
558 A.F20C:SE B.F19A:TRA B.F19A:TRA RQ, Seq
ME A A A.F98C:EX
RQ
F32G,F32M F19,F32G,F
559 F20 F34A F19 F34A
,F34A 32M,F34A
Seq
564 A.F20C:SE
ME
Seq Seq
565 A.F20C:SE D.F98A,
ME Seq D.F98C
Seq
Seq Seq Seq D1.F98A:P
566 A.F20C:SE D2.F19B:PS D2.F19B:PS OST, Seq
ME TA TA D1.F98C:P
OST
Seq
567 A.F20C:SE
ME
02 September 2016 35
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
Seq
568 A.F20C:SE
ME
574. Seq
W8B A.F20C:SE
ENO ME
577 F20
Seq
Seq Seq B.F98A:SET Seq Seq
578 Seq A.F20C E3.F19A:SE E3.F19A:SE T, Seq E3.F19A:SE E3.F19A:SE
TT TT B.F98C:SET TT TT
T
579 F20
592 F20
595 F20
596 F20
598 F20
599 F20
F33G,F34P,
600 Seq A.F20 F33G F33G Seq B.F34P F34P,F34R F34P,F34R
F34R
02 September 2016 36
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
F32B,F32H, F32B,F32H,
F34E, F34E,
620 F20 F32B F32B F30V F30V
F33B,F33E, F33B,F33E,
F71F F71F
F32A,F32B, F32A,F32B,
F32P,F33B, F32P,F33B, F32A,F32P,
643 Seq A.F20 Seq A.F32A Seq A.F32A Seq A.F32A
F33P,F33R, F33P,F33R, F33P,F33R,
F34P,F34R
F34P,F34R F34P,F34R
692 F20
695 F20
02 September 2016 37
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
696 F20
698 F20
699 F20
701 F20
711 F20
721 F20
F32A,F33A, F32A,F33A,
734 F20 F32A F32A F32A F32A,F33A
F33B F33B
F32B,F33B, F32B,F33B,
742 F20 F32B F32B F34A
F34A,F34B F34A,F34B
F32B,F33B, F32B,F33B,
750 F20 F32B F32B
F34B F34B
F32A,F32B, F32A,F32B,
754 F20 F32A,F32B F32A,F32B F32A F33B,F34A, F33B,F34A, F32A,F34A
F34B F34B
02 September 2016 38
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
760 F20
767 F20
F32B,F32D, F32B,F32D,
769 F20 F32D
F33B,F34B F33B,F34B
792 F20
795 F20
796 F20
798 F20
799 F20
F32A,F33B, F32A,F33B,
800 F20 Seq B.F32A Seq B.F32A Seq B.F32A F32A
F34B F34B
892 F20
895 F20
896 F20
898 F20
899 F20
02 September 2016 39
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
F60F,F62F,F F60F,F62F,F
F60F,F62F,F
941 F20 F62F F62F F62F 64,F65,F90 64,F65,F90
64,F65
C,F90D C,F90D
F34F,F90C, F34F,F90C,
942 F20 F34F F34F
F90D F90D
973 F20
985 F20
986 F20
992 F20
995 F20
996 F20
998 F20
02 September 2016 40
Alliance Access 7.1.20
Release Letter Routing Keyword Extraction and Verifiable Fields
999 F20
(1) The value with the CANC qualifier will be extracted only if the function of the message (F23G) is equal to CANC.
02 September 2016 41
Alliance Access 7.1.20
Release Letter Switch-over Planning for Standards MT
02 September 2016 42
Alliance Access 7.1.20
Release Letter Switch-over Planning for Standards MT
• When your business week is finished, log out from the SWIFT network and log back in for
reception only. In this way, you can still receive and correctly process messages from other
correspondents.
• Close all your "from" message partners and open all your "to" message partners. In this way,
all received messages can still follow automatic processing.
Note On 19th November 2016 at 16:00 GMT, SWIFT will disconnect all users and
activate the new Standards MT November 2016.
02 September 2016 43
Alliance Access 7.1.20
Release Letter Standards Switch-over Planning for InterAct Services
02 September 2016 44
Alliance Access 7.1.20
Release Letter Standards Switch-over Planning for InterAct Services
will process all messages through the routing you set up to distribute the messages to your back
office. So it is important that you know how your back office will behave when receiving new
message versions for the pilot service.
In order to allow manual processing (create, modify, verify, authorise), and printing in human
readable format, you need to download the appropriate message standards Deployment
Package from the download centre on www.swift.com or from mystandards.swift.com. If you are
using specific usage guidelines for the service, also download the usage guideline specific
deployment package from mystandards.swift.com.
From the Alliance Access Configuration GUI package, install the new deployment packages. If a
previous version of the deployment package was installed, the installation process will mark all
messages types for that service as obsolete, and merge the message types from the new
deployment package with this. As a result of this process, all message types already loaded,
and no longer occuring in the latest deployment package will still be there and marked as
obsolete, while all messages in the latest deployment package will be marked as not obsolete
and will be available to the users. If there were some messages that should not be used by your
users, you can mark these manually as obsolete to prevent message creation. The release
letters of the deployment packages provide the details of what message versions are included in
the deployment package.
If you have usage guidelines installed, you need to do the same for each usage guideline linked
to the same service. It is possible that a specific usage guideline does not yet support the new
message standards version, and will not have an updated deployment package. For more
information, contact the publisher of the usage guideline.
In case you have created manually defined verifiable fields for a message in this service that got
a new version, you will need to configure the new version of the message to also have the
appropriate verifiable fields.
Once the deployment package is installed, the new message standard can be used both for the
production and all pilot/test versions of the service. If one of your users would create a message
using the new version before it has been activated on the SWIFT network a NACK will be
returned.
If you try to create a message using a template that is linked to an obsolete message version,
Alliance Access will automatically try to convert it to the latest version available.
When no manual processing or human readable printing is required, the deployment package
installation is not necessary.
02 September 2016 45
Alliance Access 7.1.20
Release Letter Standards Switch-over Planning for InterAct Services
can start monitoring usage to make sure that you have no business need for the old version by
the time that the message version reaches end-of-support.
In order to enforce the usage of the latest message version during manual processing you can
use the Alliance Access Configuration GUI package to configure the message version as
obsolete.
During this period, however, your back-office systems are expected to still be capable of
processing older message versions until they are removed from the service.
02 September 2016 46
Alliance Access 7.1.20
Release Letter Legal Notices
Legal Notices
Copyright
SWIFT © 2016. All rights reserved.
Restricted Distribution
Do not distribute this publication outside your organisation unless your subscription or order
expressly grants you that right, in which case ensure you comply with any other applicable
conditions.
Disclaimer
The information in this publication may change from time to time. You must always refer to the
latest available version.
Translations
The English version of SWIFT documentation is the only official and binding version.
Trademarks
SWIFT is the trade name of S.W.I.F.T. SCRL. The following are registered trademarks of SWIFT:
the SWIFT logo, SWIFT, SWIFTNet, Accord, Sibos, 3SKey, Innotribe, the Standards Forum logo,
MyStandards, and SWIFT Institute. Other product, service, or company names in this
publication are trade names, trademarks, or registered trademarks of their respective owners.
02 September 2016 47