A Better Way to Run Your Business

• You can create a saved view that enables you to filter grids using the saved filtering criteria. You can expand or collapse a section that reveals the saved criteria
• When the filter section is expanded, you can add additional filters to the saved view, remove filter badges and save a new view, and clear all badges associated with the current saved view.
• Filter values are hidden by default; however, user's selection to show or hide the filters is set in the data store and applied to all grids (new or changed)
• Saved Views become the new default state.

Many customers need to be able to upgrade to Java 8, update 241 in their production environments to address security vulnerabilities. This version of BBC has been certified to run with Java 8, update 241, which was released January 14, 2020.

Change Summary

• User permission report has an improved look and feel
• Report runs in background – A message will pop up when system realizes that the report will run for a while

• While some countries have always required a beneficiary address, the application did not clearly indicate that the beneficiary address field was required
• When choosing either the country (such as Canada) or the SWIFT code belonging to such country, the beneficiary address line will be indicated with red asterisk to show that the field is required

• You can download multiple e-Statements at once
• Export file will be created in a zip file format and available under ‘Download’ menu
• Zip file will contain multiple e-Statements with export date as file name(s)

Steps to Reproduce:

• Log in to the Client application, and navigate to Payments Management > Templates listview.
• Click Add a new template.
• Select Loan Payment
• Select Recurring - In the Repeat Every section, select Month/Select a day of the month in the "On The" section. For example, select Day 10 to have the payment made on the 10th of every month.
• Save the template.
• View the template.

Actual Result:

• The transaction date reverts to Day 1 instead of Day 10 in the example.

Expected Result:

• The transaction date should remain Day 10.

Note: This occurs during a Modify action as well. If the user modifies the amount in the template, for example and doesn’t notice that the date has reverted, saving the template will result in a change to the value date as well since the template doesn’t retain the original setting

Steps to Reproduce:

• Log in to the Client application and navigate to Payments List View.
• Filter on Value Date, and enter a date range.
• Expose the filter by clicking the Show/Hide Filter icon.

Actual Result:

• The filter just shows the Value Date as 08/10/2020.

Expected Result:

• The filter should show an actual range, for example, Is Between 08/10/2020 –08/14/2020.

Steps to Reproduce:

• Log in to the Client application.
• Navigate to Payments &Transfers > Payment Management.
• Navigate to Template List View > Active Templates.

Actual Result:

• Template Code, Template Description are not fully visible.

Expected Result:

• The columns are sized properly and are visible.

Steps to Reproduce:

• Log in to the Client application, and navigate to PaymentManagement.
• Add a new payment, and select Tax Payment.
• Enter or select a tax authority (for example, Hawaii).
• Enter the tax type code (for example, 04610, General ExciseTax).
• Enter beneficiary details.
• Click Submit.
• Select Print > Print Detail Report.
• Navigate to Report Management> Payment Detail Report.
• Print the report.

Actual Result:

• The transaction detail amount appears as a debit (enclosed with parentheses).

Expected Result:

• The transaction details should appear as a credit.

Steps to Reproduce:

• Log in to the Client application, and navigate to Account Summary > Customer Reporting
• Create your desired report using the parameters
• Sort the column on the screen such as amount (small to largest)
• Click Print

Actual Result:

• On print screen, the sort is not reflected and it sorts with default sorting criteria

Expected Result:

• The sort order you have set in the screen will be reflected in printed version of the Print screen

Steps to Reproduce:

• Rejected transfer notification retention was too long and therefore old transfer, which rejected, remained in the notification window.

Actual Result:

• The counter which shows the number of rejected transfers stays the same from the first time rejected transfer occurred and not show just the new rejected transfers.

Expected Result:

• Rejected Transfer notification is taken out of the home page

Note:

• “Rejected” is a final status of a payment and therefore, you are not able to delete these records.
• It is recommended you set up alerts for rejected transfers if notification is required.

Steps to Reproduce:

• Go to template management and select ACH template "in repair" status
• Delete the template

Actual Result:

• ACH templates in "in repair" status cannot be deleted

Expected Result:

• ACH templates in "in repair" status can be deleted