Financial Transaction Manager for ACH Services and Check Services V3.0.5 Release Information

Feature Changes


141734
Database changes to use FTM Base 3.2.11 database structure.

 

 

 

Back to top

V3.0.5.5 interim fix 3

 

Known Issues


133462
Settlement accumulator update (edit) issue

Use the following file to merge into core property:

3.0.5.5_ifix3_133462.ddl

Which can be downloaded from Fix Central at 3.0.5-FTM-Check-MP-Documents.

 

---

 

Feature Changes


None.
 

---

Migration


None.
 

 

 

Back to top

V3.0.5.5 interim fix 2

 

Known Issues


131687
Payment Repair and Amount Keying - Second finalization prompt is displaying misinformation in MICR fields.

This has been successfully validated against the Firefox and Internet Explorer browsers. Another issue has been opened to address the same fix for Chrome and Edge browsers for later interim fix.

 

---

 

Feature Changes


None.
 

---

Migration


None.
 

 

Back to top

V3.0.5.5 interim fix 1

 

Known Issues


None.

 

---

 

Feature Changes


None.
 

---

 

Migration


None.

 

---

 

Back to top

V3.0.5.5

 

Note: 3.0.5.5 is Check only (not ACH or CPS)

 

Compatibility Matrix

If you are on:	To successfully upgrade to 3.0.5.5 you must be no later than:
3.0.0.15	3.0.0.15 interim fix 19.1
3.0.2.1	3.0.2.1 interim fix 23
3.0.5.0	3.0.5.0 interim fix 1
3.0.5.1	3.0.5.1 interim fix 5
3.0.5.2	3.0.5.2
3.0.5.3	3.0.5.3 interim fix 1
3.0.5.4	3.0.5.4 interim fix 12

 

Known Issues


None.

 

---

 

Feature Changes


27221
Image Review integration into Payment Repair structure.


Over the years, many features have been added to Payment Repair that were not added to Image Review. To solve this problem, Image Review and Payment Review and Payment Repair have been merged to give Image Review additional functionality.

Permissions

The Lock Management screen permissions for Payment Repair and Image Review will now be used on the generic Lock Management Screen. Note that to see the Remediation Lock Management screen, view permission must be given under the Transaction Server application as shown in the following screen captures.








Image Review now supports hot key mappings, which can be configured on the generic hot key mappings page. Note that to see the page, view permission must be given under the Admin application.






Image Review screen sizes will be configured under the generic screen. Note that to see the screen, the view permission must be given under the Admin application.

 





Priority Management will now be handled under the generic Priority Control Configuration screen. Note that to see the Priority Control Configuration screen, the user must have the View permission under the Admin component shown below.










A permission has been added for the new Review UOW Status screen.


A permission has been added for the new Review Worklists screen.




A new permission has been added for Image Review to control saving of rotated images on the Operator Review / Deferred Item Review screens.




Operator Review Screen
 

Now located at Processing & Remediation -> Image Review -> Operator Review

The new Operator Review screen will look very similar to the existing Payment Repair screen. Operators will be able to accept, reject, defer, and skip reviewing images for each payment and call recall previously decisioned items by click Redo Pending Item in the lower right. Error codes and a log will be displayed to give additional information. Images that need review will be displayed with an X above the name and will automatically be selected. Images that are accepted will change to a checkmark. When all images have been reviewed, the next item will be displayed. Skipped items will not display for this user again for the given session.



Deferred Item Review Screen

Now located at Processing & Remediation -> Image Review -> Deferred Item Review
This screen functions identically to the Operator Review screen but displays items that have been deferred. Users will be unable to defer items on this screen.

Item Count Screen
 

Now located at Processing & Remediation -> Monitoring -> Item Counts

The item counts screen has been combined into one. Payment Repair and Image Review item counts can be viewed on this screen. Payment Repair and Image Review have separate view permissions for this item counts screen, controlling what counts are visible.

Lock Management Screen
 

Now located at Processing & Remediation -> Monitoring -> Lock Management

Image Review and Payment Repair items can be unlocked on the Lock Management screen. Payment Repair and Image Review have separate permissions to control viewing and unlocking of items.

Forward UOW Status Screen
 

Now located at Processing & Remediation -> Monitoring -> Forward UOW Status.

Return UOW Status Screen
 

Now located at Processing & Remediation -> Monitoring -> Return UOW Status.

Review UOW Status Screen
 

Located at Processing & Remediation -> Monitoring -> Review UOW Status.

A new Image Review screen has been added to view the status of Image Review items.

Forward Worklist Screen
 

Now located at Processing & Remediation -> Monitoring -> Forward Worklists.

Return Worklist Screen
 

Now located at Processing & Remediation -> Monitoring -> Return Worklists.

Review Worklist Screen
 

Now located at Processing & Remediation -> Monitoring -> Review Worklists.

A new Image Review screen has been added to see what items are in the worklist for a given priority control configuration.

Priority Control Configuration Screen
 

Located at Configuration -> System -> Priority Control.

Payment Repair and Image Review have been added to the generic priority control configuration screen. The old Payment Repair and Image Review priority management screens have been removed.

Hotkey Mapping Screen
 

Located at Configuration -> System -> Hot Key Mapping

Payment Repair and Image Review were added to the generic hot key mapping page. The old Payment Repair hot key mapping page was removed.

Screen Size Screen
 

Located at Configuration -> System -> Screen Size.

Payment Repair and Image Review have been added to the generic screen size screen. The old Payment Repair screen sizes screen has been removed.

Image Compliance Properties Screen
 

The Image Compliance core properties screen has been updated to be more in line with Payment Repair so that it can support the new features.

Exposure Limit Monitoring Screen
 

Now located at Processing & Remediation -> Monitoring -> Exposure Limit Monitoring.

Task Activity Screen
 

Now located at Processing & Remediation -> Monitoring -> Task Activity.

Lock Expiration Task
 

Image Compliance will now have its own lock expiration task which will expire locks that have been held for too long without being worked. This helps prevent work from being stuck or held up. This task is automatically scheduled.

Transaction Server Scheduler Updates
 

With the integration of Image Review into the Payment Repair structure, some scheduler events needed modification.

For the Image Review Business Day close event (Image Compliance Review - Business Day Close) changed from BDAY_STATUS_CHANGE to CLOSE_BUSINESS_DAY_REQUEST

For the Image Review Business Day close event (Image Compliance Review - Business Day Reactivate) changed from BDAY_STATUS_CHANGE to REACTIVATE_BUSINESS_DAY_REQUEST

The Image Review Business Day purge event (Image Compliance Review - Business Day Purge) is no longer supported. Data purging for Image Review items is handled automatically.

128588
Payment Repair: Disconnect image height and width core properties from image size during "Save" function.


The image with large size in tiff was exaggerating its size when home-grown image JAI transformed due to an incorrect ImageFormatter type. Such has been corrected to produce the same size images.

In addition, the LOCAL image creation mode in distribution is ensured to create the file with the updated images from IMAGE_DATA.



129036
Support CPCS Sequence ID as a single column on Transactions Screen.


The CPCS Sequence Number field is added to the Inbound Transaction screen. The value of the field is the combination of the existing Item Sequence ID, Item Sequence Sorter, and Item Sequence Number.

The field can be filtered and sorted.

---

 

Migration


The following document contains the instructions that are needed to migrate from 3.0.5.4 to 3.0.5.5:

FTM_Check_V3.0.5.5_Migration.pdf

Which can be downloaded from Fix Central at 3.0.5-FTM-Check-MP-Documents.

 

 

---

 

Back to top

V3.0.5.4 interim fix 28

 

Known Issues

None
 

---

 

Feature Changes


None.
 

---

 

Migration


None.

 

 

---

Back to top

V3.0.5.4 interim fix 27

 

Known Issues


None
  

---

 

Feature Changes


None.
 

---

 

Migration


None.

 

 

---

 

Back to top

V3.0.5.4 interim fix 26

 

Known Issues


FTM Check 3.0.5.4 iFix 26 is compatible with MQ 9.3

152567
Transaction (Item) Version Tab shows two Payment Repair Versions for select items. 

Use the following file to update the Repair Forward Corrected Items View:

3.0.5.4_ifix26_152567.ddl

It can be downloaded from Fix Central at 3.0.5-FTM-Check-MP-Documents.

 

---

 

Feature Changes


None.
 

---

 

Migration


None.

 

 

---

• Use a minimum Payment Repair Preload Buffer Size of "20".
• Enable the Fetch Payments in groups feature of Payment Repair.
• Enable the Shuffle Items feature of Payment Repair.

Known Issues

100593 (fixed with the information provided below)
New Core Property for Payment Repair to fetch Payments in groups

Feature Changes

None

Migration

None.

Known Issues

None.

Feature Changes

None.

Migration

None.

Known Issues

None.

Feature Changes

None.

Migration

None.

Note: 3.0.5.4 is Check only (not ACH or CPS)

Compatibility Matrix

Known Issues

None.

Feature Changes

95156
TCR Inbound Transmission Hierarchy Filtering Enhancements

The TCR Inbound Transmission Hierarchy filtering has been enhanced to exclude the File, Cash Letter, Processing Cash Letter and Bundle Records from the Total Item Count at the Top of the Tree View and Filter Results.

The hierarchy screen will now display a new checkbox with the label "View Bundles". This checkbox will be checked by default. If unchecked, any filter applied to the hierarchy will cause the results to display without any bundle records. Instead, transactions will be grouped by processing presentment. The new checkbox value can be saved in preferences, and now the filter can be saved as well. Therefore, leaving the page after saving preferences and returning will load the filter and checkbox value that were saved.

95819
Transmission Hierarchy Transaction Details screen enhancements

In the Transmission Hierarchy Screen, the user will now see the Details Header in the UI change from the default color to yellow when the user has the first credit of a Transaction Group selected. This way, the user can easily discern when they have navigated to the beginning of a Transaction Group, even when the Tree Grid pane is minimized.

84725
Payment Repair Randomization for multiple users

A new core property named izq.repairui.shuffleItems (Shuffle Items) was added with a default value of N for disabled. When enabled with a value of Y, this property activates the reordering functionality.

The shuffle items function uses the existing Preload Buffer Size and Pending Buffer Size properties to reorder the list of repairable items that are loaded in Payment Repair. The reordering is done so that repairable items with the same amount or with consecutive IDs are not displayed back-to-back.

This helps prevent back-to-back credit and debit (single transactions) from being displayed.

Limitations: if there are more payments with sequential payment IDs and/or same amounts than the configured "Preload Buffer Size" (Payment Repair core property), this function will not shuffle the items and present them in a normal, sequential order.

95157
Amount Keying - ability to configure additional debits

Amount Keying makes items available for Priority Control Configuration (PCC) to select in three waves:

• The credits in an Out of Balance (OOB) transaction.
• The "most likely" debits in an OOB transaction.
• The remaining debits in an OOB transaction.

The ability to configure additional debits to be made available in OOB transactions during the second wave when determining the "most likely" debits has been added. This functionality was included in the second wave selections when determining the "most likely" debits.

When configuring the likely-debits PCC, it will require the user to input the Authorizations allowed for the PCC in order to create the new PCC. This is a known defect that will be fixed in a future version as this criterion does not actually apply to the logic in the product.

The BALANCE PCC runs to determine which items to present to a user. The Likely-Debits PCC runs in the background during the balance analysis. The Likely-Debits PCC does not run when gathering items to present to a user like most PCCs do. The Likely-Debits PCC will run during the balance analyzer to change an item's dispositions from "loaded" to "new" so that the items can then become eligible to be selected when the BALANCE PCC is looking for items.

The items are simply changed to "new" and the next time an item gets added for that user, those items will be eventually displayed - PRIOR to the items that were not part of "likely debits" processing and are still in "loaded" state.

Migration

The following document contains the instructions that are needed to migrate from V3.0.5.3 to V3.0.5.4:

FTM_Check_V3.0.5.4_Migration.pdf

Which can be downloaded from Fix Central at 3.0.5-FTM-Check-MP-Documents.

Known Issues

None.

Feature Changes

None.

Migration

None.

Note: 3.0.5.3 is Check only (not ACH or CPS)

Compatibility Matrix

Known Issues

None.

Feature Changes

85390
Payment Repair:  Corrected Image should be "saved".

If a check image is displayed in the incorrect orientation, the image can be rotated, then saved. The Save Rotated Image button must be activated with permissions. Saving the rotated image is only allowed after a rotation occurs.

88503
TCR:  Clear Delineation added between Transactions

When viewing a transaction in the tree structure of the Inbound Transmission Hierarchy, there will now be a solid bold line delimiter above the first credit in that transaction. This gives an operator a visual separator to signal the beginning of a transaction when the operator does not have visibility to the file hierarchy in the first column of the left pane.

85393
Transmission Hierarchy UI: Payment Repair information added to the attributes section.

The Transmission Hierarchy UI was changed to display the Repair Reviewed ID, which is the user ID of the user who either repaired or rejected the item in Payment Repair. This field is in the Attributes section under the General Tab, and appears directly underneath the Repairable field.

89313
Transmission Hierarchy "Expand All" function improved for performance

Two new buttons (hot-key mappable) were added to the Inbound Transmission Hierarchy screen to allow an operator to expand (>>) or collapse (<<) a record in the tree structure as well as all child elements. This function, when used at a hierarchy level lower than a Cash Letter, improves the response time to expand the substructures of the tree.

The new Expand/Collapse Record buttons as well as the existing Expand/Collapse All are now permission-based so that an operator can be given only one or both of the options of buttons.

NOTE: When used at the file level, using the Expand/Collapse Record is equivalent to using Expand/Collapse All function.

91742
Payment Repair: Operator allowed to fix the MICR Line on a Rejected IIA Item

A new button has been added alongside the “Update IIA Flagged Item” button, which has the text “Reject IIA Flagged Item”. This will only appear for IIA flagged items, and will perform two functions:

• Validate the item. This validation is equivalent to the process used when repairing an item normally. Fields with validation errors will be indicated with a red border and the rejection will not be saved until these are corrected and the button is pressed again.
• If the edits to the item pass validation, reject the item. This is equivalent to the regular reject process, thus any changes made will be saved and the item will be rejected and marked with the disposition “Remorse Unresolved” (s).

Upon finalizing items, any items marked this way will be finalized in the same way as a typical rejected item. Changes made will be saved to the Payment, and the disposition will be set to “Unresolved” (U).

82369
TCR: Added the ability to detach images to see multiple items at one time

To detach an image, a user can right-click a debit or credit in TCR and select the 'Detach Image' action to bring the image up in a separate window. A separate window is made for each image that is detached in this way. Each window must be closed manually when no longer needed.  The ability to detach an image in TCR is assigned through permissions.

Migration

The following document contains the instructions that are needed to migrate from V3.0.5.2 to V3.0.5.3:

FTM_Check_V3.0.5.3_Migration.pdf

Which can be downloaded from Fix Central at 3.0.5-FTM-Check-MP-Documents.

Note: 3.0.5.2 is Check only (not ACH or CPS)

Compatibility Matrix

Known Issues

87559
Errors while WebSphere Application Server 9 server is starting up

Deploying V3.0.5.2 with WebSphere Application Server 9.0 results in errors such as the following on startup:

[11/9/18 8:54:22:133 UTC] 00000056 ServletWrappe I com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [FrameworkUI_EAR] [/businessrule] [CoreServicesStartupServlet]: Initialization successful.
 [11/9/18 8:54:22:148 UTC] 00000056 0(id=121)]    W   No resource methods have been found for resource class com.ibm.fxh.core.ui.jaxrs.resources.EmptyResource
 [11/9/18 8:54:22:148 UTC] 00000056 0(id=121)]    E   No resource classes found
 [11/9/18 8:54:22:148 UTC] 00000056 ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0271E: Uncaught init() exception created by servlet [JAX-RS Servlet] in application [FrameworkUI_EAR]: org.apache.cxf.service.factory.ServiceConstructionException
     at org.apache.cxf.jaxrs.JAXRSServerFactoryBean.create(JAXRSServerFactoryBean.java:219)
     at com.ibm.ws.jaxrs20.server.JaxRsWebEndpointImpl.init(JaxRsWebEndpointImpl.java:69)
     at com.ibm.websphere.jaxrs.server.IBMRestServlet.init(IBMRestServlet.java:90)
     at com.ibm.ws.web

The errors do not appear to affect the use of the product, but deploying with WebSphere Application Server 8.5.5 resolves the issue.  This defect will be fixed in a later fix pack.

87990
OFAC simulator

Starting with V3.0.5, Fix Pack 2, Check Services users that want to use the OFAC simulator must first contact the FTM for Check Services Support team using a support case.

Feature Changes

79091
Add Support for New Middleware Levels

This release includes support for the middleware bundled in FTM base V3.2.0.  Customers may chose to stay on existing middleware or upgrade to the new versions found in FTM base V3.2.0:

• WebSphere Application Server 9.0.0
• Db2 Enterprise Server 11.1.2.2
• IBM MQ 9.0.0
• IBM Integration Bus 10.0.0.11
• IBM Transformation Extender 9.0.2
   

In addition, the application has been tested with WebSphere Application Server V9/Java V8 and now ships with Java V8 for the J2SE servers.
This release also introduces support for RHEL V7.4 and V7.5.

79094
Additional User State Flags

Additional user states have been added for customers that choose to configure them. If no additional user states are needed, nothing changes.

The following files describe how to add the additional user state:

79094.readme.txt

Which can be downloaded from Fix Central at 3.0.5-FTM-Check-MP-Documents.

85392
Check Data UI:  Display CPCS Record ID
A new entry called 'User Code' was added to the Check Data grid on the Inbound Transmission Hierarchy page. On the Inbound Transmission Hierarchy page, select a transaction level entry and then the Check Data tab on the right side of the page. The User Code entry is displayed after 'Posted' on the Check Data tab. This user code entry shows the information that is stored in the database for the user code.

83426
Integrate third-party IQA Engine
The Gateway Image Compliance post-analysis user exit now has support for a developer to modify Image Compliance results to set IQA scores and add a Type 54 addenda record.  Sample code can be found in SamplePostAnalysisUserExit.java. Commented out sample implementations exist to show how to use the new exposed objects as well as an additional example on how to set an error code on the Image Compliance results.  These examples are marked with the tag "88192".

83424
Add Attributes to TCR Active Units of Work Page
Three new columns have been added to the TCR Active Units of Work page: CPCS Entry ID, CPCS Entry Number, and CPCS Cycle. The CPCS Entry ID column is visible by default, and can be sorted and filtered. CPCS Entry Number and CPCS Cycle are hidden by default, and cannot be sorted and filtered. When no CPCS Entry ID is associated with the Batch / ICL, a blank entry is displayed for all three fields. Otherwise, data is retrieved for all three fields that are relevant to the Batch / ICL.

When filtering on CPCS Entry ID, the filter works at the parent level unless the UOW Type is also filtered to display Batch/ICL. For example, if the parent UOW Type is CPCS Entry and the filtering criteria is "CPCS Entry ID is empty", the CPCS Entry UOW is shown in the results, even if the children of that entry have a CPCS Entry ID. However, if the filtering criteria consists of "UOW Type equals Batch/ICL and CPCS Entry ID is greater than 0", any record that has a CPCS Entry ID is shown, regardless of the UOW Type of its parent.

83422
Add TCR Configuration to Not Allow Block or Batch Control Documents to be Deleted 
With this latest release, two new permissions have been added to TCR:

    (Action) Delete Control Document
    (Action) Move Control Document

When a user right clicks on an item in TCR on the Inbound Transmission Hierarchy page, the menu options displayed will take into consideration whether the item is a Control Record and, if so, does the user have the Delete or Move permissions to show the actions on the menu.

83286
Add CPCS Sequence Number to Inbound Transmission Hierarchy page
The 'CPCS Sequence Number' column was added to the Inbound Transmission Hierarchy page. The CPCS Sequence Number field is the tracking number that is assigned to the transaction and used internally by Check Services. If it was assigned by CPCS, it is made up of the item sequence ID, item sequence sorter, and item sequence number. By default, this column is hidden to the user, can be filtered dynamically, and cannot be sorted. Filtering on this column is determined by two aspects: View Mode and Lock Status. For the column to be shown in the filter dialog box, TCR View Mode must be enabled. When view mode is enabled, CPCS Sequence Number is an option on the drop-down selection menu. While filtering on this field, the results are composed of transactional items that belong to a Batch / ICL that is locked. In the case that the Batch / ICL is not locked, it results in no transactional data being displayed.

When the operator has a filter that includes the CPCS Sequence Number field and disables TCR View Mode, the criteria containing that field are removed from the filters and a message that has details about the field, operator, and value that was originally in the filter is logged.

79097
Payment Repair Priority Control improvements

The Payment Repair Priority Control pages are no longer stand-alone and are now a part of the remediation framework. This changes the way that a priority control configuration, which determines the items that operators receive when they are using the repair pages, is created, viewed, and modified. Also, the Payment Repair lock management functionality was moved to the remediation framework and uses the Processing & Remediation > Remediation Lock Management page. The Processing & Remediation > Payment Repair > Monitoring > Locked Items page was removed.

Previously, Payment Repair had a page that was used to create priority control configurations (PCC) for forward items and a different page that was used to create priority control configurations for return items. These pages were accessed by using the following menu items:

• Processing & Remediation > Payment Repair > System > Forward Priority Control
• Processing & Remediation > Payment Repair > System > Return Priority Control

After moving priority control to the remediation framework, the page used to create priority control configurations is accessed by using the following menu item:

• Configuration > System > Priority Control

The create priority configurations page in the remediation framework supports creating the forward and return priority control configurations that are needed by Payment Repair. When "PaymentRepair" is selected for the application name, you can select forward or return for the type field. In addition, the following selection filtering criteria were added for Payment Repair:
    -IIA Repair
    -Amount Repair
    -Process Control Repair
    -Account Repair
    -Process Control Repair
    -Account Repair
    -Field 4 Repair
    -Routing Number Repair
    -EPC Repair
    -Aux On Us Repair

The new selection criterion corresponds to the flags for certain types of repairs, either due to IIA verification or MICR field repairs. All of the new criteria are similar to the previous 'Holdover' criterion because no Operator selection or Value is required, or allowed. When one of these criteria is selected, the Operator list and  Value field are hidden from the page and only the 'Add' actions are available.

The following example shows the fields for a Payment Repair forward repair configuration that is created using the priority control configuration in the remediation framework.
Application Name: PaymentRepair
Type: Forward
Name: Sample Forward Payment Repair Configuration
Description: Sample Forward Payment Repair Configuration
Filtering Criteria Set:
    - (Batch / ICL Receipt Time > 30) order by (Batch / ICL Receipt Time DESC) auth for (Payment Repair Administrators, Payment Repair Supervisors, Payment Repair Users)
    - (Batch / ICL Receipt Time > 10 and Amount Repair) order by (Amount DESC) auth for (Payment Repair Administrators, Payment Repair Supervisors, Payment Repair Users)
    - (IIA Repair) order by (Amount DESC) auth for (Payment Repair Administrators, Payment Repair Supervisors, Payment Repair Users)
    - auth for (Payment Repair Administrators, Payment Repair Supervisors, Payment Repair Users)

In this sample configuration, items that were received more than 30 minutes ago are assigned to authorized operators first; in the order of the oldest received to the newest; until the 30 minute limit is reached. After these first items were assigned and repaired, items that were received at least 10 minutes ago and require the Amount (MICR Field 1) field to be repaired are assigned to authorized operators for repair. After the completion or assignment of all relevant items, items that require IIA repair are assigned to authorized operators for repair. Finally, any remaining items will be assigned to authorized operators for repair.

The previous versioning system that kept a record of previous and current configurations was removed with the change to the remediation framework. You can now copy a selected configuration, which shows the create priority configuration page with the current details from the selected configuration already in the fields on the page.

Migration

The following document contains the instructions that are needed to migrate from V3.0.5.1 to V3.0.5.2:

FTM_Check_V3.0.5.2_Migration.pdf

Which can be downloaded from Fix Central at 3.0.5-FTM-Check-MP-Documents.

115387
Duplicate file error when processing with a routing Gateway