Fix Readme
Abstract
This document contains V3.2.0 release information for Financial Transaction Manager for Digital Payments for Multiplatforms. Included are known issues and changes from previous releases.
Content
Financial Transaction Manager for Digital Payments V3.2.0 Release Information
Contains release information for:
- Financial Transaction Manager for Digital Payments for Multiplatforms V3.2.0
Described are known issues and changes from previous releases. Start with the section for the release version you’re currently working with and review each subsequent release for the changes.
Release Number
Common Across Releases
3.2.0.1 Release
... 3.2.0.1 iFix 1
... 3.2.0.1 iFix 2
3.2.0.0 Release
| Back to top | Common Across Releases |
Known Issues
None.
Changes
Fix list and new feature summary
For the list of fixes refer to Financial Transaction Manager for Digital Payments V3.2.0 Fix list.
Data Setup Utility
The following documentation describes the changes for the data setup utility (DSU) and the import and export workbooks:
DSUmigration_v3.0.6_to_v3.2.0.pdf 
DSUMigrationBR_v3.0.6_to_v3.2.0.pdf
Database migration
For database migration instructions, refer to the migration instructions in {Install location}\shared\vnnn\pfs\Database\db2\{os}\doc
Transaction Server Scheduler XML
The following documentation describes the changes to the scheduler XML for the Transaction Server component:
TransactionServerSchedulerChanges_v3.2.0.pdf
General Instructions
Migration
Upgrade procedure
To upgrade an existing installation for a fix pack or interim fix (iFix) the following tasks need to be performed:
Pre-installation
Note: Installation Manager won’t update a file that has been modified after Installation Manager originally installed that file.
- Ensure that the following components in the install location aren’t running: RMI Service, Business Rules Distribution Manager, Business Rules Process Server, Gateway, Transaction Server.
- Ensure that your installation doesn’t have any updated files from test fixes or modifications that you may have made. Known directories or files that may have test fixes are:
- Install location\shared\v320\pfs\BusinessRules\manager\lib\pdrmgrfx.jar
- Install location\shared\v320\pfs\BusinessRules\server\lib\pdrsvrfx.jar
- Install location\shared\v320\pfs\Gateway\lib\izxfix.jar
- Install location\shared\v320\pfs\ITS\lib\txfix.jar
Installation
- Start IBM Installation Manager.
- Add the location of the repository containing the installation package:
- Select File->Preferences.
- Click Add Repository.
- Browse to the directory containing the repository .zip file and select the file and click Open button, then OK.
- Click Test Connections and click OK.
- Click OK.
- Install the FTM product installation files to your installation directory:
- On the main panel, click Update.
- Select IBM Financial Transaction Manager for Digital Payments, IBM Financial Transaction Manager for Check Services, or IBM Financial Transaction Manager for Corporate Payment Services and click Next.
- Select the fix pack or interim fix and click Next.
- Follow the rest of the prompts.
- Confirm the "Update packages" page shows success.
Deployment
- Perform database migration. Refer to the Database migration section in this document.
- Note: The run time components can’t be running during the database migration.
- Note: Files can continue to be delivered to the Gateway inbound source folder.
- J2SE components: Install will overlay the J2SE applications so no special migration instructions are needed. Restarting those applications will update them with the fixes.
- WebSphere Application Server (WAS) components: You may use the Automated Deployment Utility (ADU), manually upgrade (refer to the update instructions in each WAS component doc folder), or in a WAS Network Deployment configuration use the Deployment Manager.
- All WebSphere Servers must be restarted after all components have been updated.
- For an interim fix refer to the Fix List for the modules to deploy. Note: Interim fixes are meant to be deployed on an existing WAS profile deployment. If this is a new WAS profile and you have already installed the interim fix onto the prior installation, then you must perform two deployment passes. The first pass will be for the initial full product deployment and the second pass will be for those components affected by the interim fix.
- Update your Transaction Server Scheduler.xml. Refer to the Transaction Server Scheduler XML section in this document for documentation. Note: this may not be required for your installation.
- Refer to the release specific section for changes that may affect your installation.
- At this point you can start up your runtime components.
- If you’re using the Data Setup Utility (DSU) worksheets capability for managing your data then update your worksheets. Refer to the Data Setup Utility section in this document for documentation.
| Back to top | 3.2.0.1 iFix 2 |
Known Issues
None.
Feature Changes
None.
Migration
None.
| Back to top | 3.2.0.1 iFix 1 |
Use the following document to migrate from V3.2.0.1 to V3.2.0.1 iFix 1:
FTM_DigitalPayments_v3.2.0.1_ifix1_Migration.pdf
Feature Changes
77317
Request for Return of Funds
This change allows a bank's operator to respond to a request for return of funds. The operator will have three actions that they can perform on a camt.056 message.
They are:
- Reject - refuse the request for return of funds.
- Accept - inform the requester that the request for return of funds is being accepted and the funds will be returned.
- Accept and Return - inform the requester that the request for return of funds is being accepted and initiate a pacs.008 message.the operator must be given permission for each of these actions to perform them. If Approvals is enabled for Transaction Server, the request associated with these actions will be sent to Approvals prior to being submitted. The bank can generate approval rules for these actions. By default the approval is set to zero, meaning that no approvals are required.
For the Reject action, the operator is shown a page where they can select from the reject reasons defined by TCH. Optionally, they can select the comment tab and add information that will be included in the audit log that is generated.
For Accept, the operator is shown a page where they can select the comment tab and add information that will be included in the audit log that is generated.
For Accept and Return, the operator is shown a page where they can select the amount to return and the account information for the sender and receiver of the pacs.008. Optionally, they can select the comment tab and add information that will be included in the audit log that is generated.
82372
Create Credit Transfer on Fraud Cancel
This change allows a bank's operator to return funds to the sender when payment is received and accepted without posting, and then rejected. The operator will have an action to return the funds. The operator must be given permission for the return action.
If Approvals is enabled for Transaction Server, the request associated with these actions is sent to Approvals prior to being submitted. The bank can generate approval rules for these actions. By default the approval is set to zero, meaning that no approvals are required.
For the Return action, the operator is shown a page where they can select the account information for the sender and receiver of the pacs.008. Optionally, they can select the comment tab and add information that will be included in the audit log that is generated.
82373
Originate Request for Return of Funds
This change allows a bank's operator to initiate a Request for Return of Funds for a TCH Payment that was originated by the bank's customer. The pacs.008 message must be in the complete state and the operator must have permission to perform a Request Return of Funds action. If these are both true, the operator can select this transaction and will be presented with a page where they can select from the return reasons defined by TCH and input a comment that will be included in the request. Optionally, they can select the comment tab and add information that will be included in the audit log that is generated.
If Approvals in enabled for the Transaction Server UI, the request is sent to Approvals where the bank can assign levels of approval that are needed for this request. By default it’s set to zero (no approval required).
This request is sent to FTM for Immediate Payments for processing. The Request for Return of Funds will be related to the original payment.
| Back to top | 3.2.0.1 Release |
Note: This section contains changes since the V3.2.0.0 release.
Known Issues
None.
Feature Changes
74516
WBM Dashboards
Converted the previous WBM Dashboards to utilize Cognos Analytics.
83612
Reports
The reports listed below have been validated for TCH data:
1) Alerts By Interval
2) Detailed Failures By Day
3) Exception Decision Report
4) Unauthorized Payments Report
5) Unhandled Exceptions Report
6) Payment Authorization Configuration Report
7) Risk Monitor - Override Report
8) Risk Monitor - Suspended Items
9) Risk Monitor - Rejected Items
10) Risk Monitor - Reviewed Items
11) Percent Failed Payment Transactions Report (From FTM Base Package)
77309
FTM for Immediate Payments Errors
All of the FTM for IP errors are now included in the Digital Payments validation results.
77790
TCH Sign On/Off Status
Added the ability to issue and display the status for the TCH sign-on/sign-off command from the Digital Payments user interface.
76337
Account Qualifier
A new column was added to the ACCOUNT_QUALIFIER that can be used by the bank to help qualify the account for them. It’s a field of up to 15 characters. The field is available to be updated via the Participant Directory Accounts Tab on the Control Center user interface and the Partner Account Tab of the DSU import spreadsheet.
76892
Inbound and Outbound Raw Data Views
Enhanced the inbound and outbound raw data views so that the current inbound and outbound views are more legible.
76342
Non Payment TCH Transactions
Non payment TCH transactions are now displayed in the Digital Payments user interface.
82776
Participant Detail Services (web services)
Augmented the 'Participant Detail Services' Web services by adding the Risk Management and Originator fields.
83448
Updated List for TCH Support of Receive Services in the Route Table. Adding three new mapping of Receive Services to message types.
Introducing new values to the Receive Services Definition (XML Field Name = “ReceiveServices” and CSV Field Name = “Receive services”) in the routing table—the defect was that these services should have already been available. Below is an explanation of the added services (in red) and the updated combinations of values you might now see in this field. The question we had is whether including these new services would impact your [the bank’s] ability to use/process the routing table.
Receive Services Definitions
The values provided in this field indicate which messages a Routing and Transit number (and therefore the associated Participant) are able to receive. Before sending a message, the originating Participant should confirm that the RTN they are originating a transaction to is able to receive the transaction. The mapping of Receive Services to message types is as follows:
· CRDT: permits receipt of Credit Transfer pacs.008
· RFP: permits receipt of Request for Payment pain.013
· ACK: permits receipt of Payment Acknowledgement camt.035
· RMT: permits receipt of Remittance Advice remt.001
· RFI: permits receipt of Request for Information camt.026
· RFRF: permits receipt of Request for Return of Funds camt.056
· (NEW) RFPR: permits receipt of Request for Payment Response pain.014
· (NEW) RFIR: permits receipt of Request for Information Response camt.028
· (NEW) RFRFR: permits receipt of Request for Return of Funds Response camt.029
The Receive Services field may include any of the following combinations of the above:
· [CRDT, RFRF]
· [CRDT, RMT, RFRF]
· [CRDT, RFP, RMT, RFRF, RFIR]
· [CRDT, RFP, ACK, RMT, RFI, RFRF, RFIR, RFRFR]
· [CRDT, ACK, RMT, RFRF, RFIR, RFRFR]
· [CRDT, RFP, ACK, RMT, RFI, RFRF, RFPR, RFIR, RFRFR]
77793
Alerts
Alerts raised by FTM for IP now cause a corresponding alert on the Digital Payments Alert user interface.
79075
SQL Replication
Added a sample of how to replicate tables using SQL Replication for a Reporting/Analytics database.
81038
TCH Recieve Remittance
Added TCH Receive Remittance Advice into the Digital Payments user interface.
APAR PH03027
SOAP Web Services
SOAP Web Services with RESTful Web Service equivalents have been removed. The following table contains the SOAP Web Services that have been removed and their RESTful Web Service equivalents:
| SOAP Web Service | RESTful Web Service |
| listOutboundTransmissions | OutboundTransmissionInfo |
| listInboundProducts | InboundProductServices |
| listInboundTransmissions | InboundTransmissionInfo |
| listInboundBatches | InboundBatchInfo |
| listInboundTransaction | InboundTransaction |
| listValidationResults | ValidationResults |
| listTransmissionTypes | TransmissionType |
| listBatchTypes | BatchType |
| listMesssageStandards | MessageStandard |
| listMessageTypes | MessageType |
| listBusinessDay | BusinessDate |
| listPaymentRecordTypes | PaymentRecordType |
Migration
FTM_DigitalPayments_v3.2.0.1_Migration.pdf
| Back to top | 3.2.0.0 Release |
Note: This section contains changes since the V3.0.6.1 release.
Known Issues
Participant Configuration
The participant configuration information below isn’t available in this release for viewing and updating using the Control Center user interface.
- Originator attributes: billing account number, administrative returns customer, company identifier
- Account rules for defining Risk authorization checks and positive pay auto-decision configuration
- Alias definitions
- Logo upload
DB2 for z/OS
Implementation of FTM for Digital Payments with Db2 for z/OS isn’t recommended at this time. Fixes for incompatible queries issued from the application are planned for a future fix pack.
Column titles misaligned when using the Chrome browser
Use of the Chrome browser at zoom levels other than the default 100% may cause certain tables in the user interface to not display properly. When this issue occurs, table headers are misaligned with their data below. For example, if a user increases zoom level to 120% and navigates to Origination & Receipt > Transmissions, headers in the first few columns of the grid are shifted slightly left of their corresponding data. The offset progressively increases from left to right.
Same-Origin Check
There’s a known issue with Same-Origin Check enabled where Internet Explorer can’t open spreadsheets. Sample actions that will fail:
- Inbound Transmission Hierarchy, Download Transmission
- Processing Batches/ICLs, More > Actions > View as spreadsheet
- Inbound Batches/ICLs, More > Actions > View as spreadsheet
- Inbound Transactions, More > Actions > View as spreadsheet
- Processing Batches/ICLs, select Rejects and Warnings link, Generate Report
As a work-around customers should do one of the following:
- Use Firefox
- Disable same origin verification via the UI at Administration > Components > Payment Feature Services > Properties. Set property XSRF Same Origin Check Enabled to false. Save. Restart FrameworkUI_EAR.
DSU
When using the DSU, the following tables are able to Insert but unable to Update.
- Depositor Subscribed Services
- Endpoint Subscribed Services
- Partner Item Grouping
- Partner Restrictions
- Risk Monitor Rules Partner
- Risk Monitor Conditions Partner
- Risk Monitor Cond Attr Partner
The work around is to update using the user interface.
Installation
For the update.txt file located in install folder ..\ftm\shared\v320\pfs\FrameworkUI\doc\updates the Help System Update section needs the following correction
- Update file: izgui_help.zip (this should have said pfs_txs_dependencies.zip)
Feature Changes
User Interface
A new UI for Local (Partner-specific) Risk Monitors has been created. For migrated environments, permission assignments will have to be reviewed.
A new UI has been created: Participant Directory - General > Accounts
this screen manages accounts for the selected participant. Customers should review their custom participant validation user exit requirements to determine whether enhancements are needed in support of this new page.
Cognos Reports
All Cognos Reports have been refreshed with Cognos Analytics v11.0.10.
For out-of-box reports, customers simply need to import report packages into their new Cognos environment. No additional changes are required.
If customers have developed custom reports based on product report packages, they'll need to open the report once to refresh and upgrade the custom reports to latest Cognos version.
Related Information
Was this topic helpful?
Document Information
Modified date:
24 July 2019
UID
swg22016180