Follow

PensionPro Release Notes Beta 1.31.1.76

5/23/2019: PensionPro version 1.31.1.76

This article contains a brief description of the tweaks and fixes in version 1.31.1.76

Tweaks and Fixes 

PensionPro: 

Blast Email: Resolved an issue where the Participant Statement Delivery field was missing from the Blast Email filters and selections menu. The Participant Statement Delivery field will now be displayed in the Blast Email filters and selections window successfully.

Blast Email: Resolved an issue where the Plan Cycle Period Start was being added to Blast Email selections when only the Project Start was being selected. The Blast Email Recipients tab will now populate the correct filters and selections successfully.

FTW Integration: Resolved an issue where users were receiving an error message when attempting to link an FTW 5500 Signer. Users can now link 5500 signers successfully without error.

Tasks: Fixed a typo in the Confirm Completion Date Removal pop-up when removing task completion.  

Power Tools: Resolved an issue in Power Tools where users could execute changes successfully, but when returning back to the Selections tab and changing a value selection, records would not populate. The records will now populate successfully after returning to the Selections tab.

Dashboards: Made enhancements to the efficiency of the Global Reassignment tab of the Management Dashboard so users can now access and utilize the Global Reassignment tab without error.

 

Fetch Web: 

Fetch Web: Resolved an issue where toggles were being returned to Null upon adding any filters. Toggles will no longer be returned to Null values when adding filters.

Fetch Web: Resolved an issue where the Trading Platform field were missing. The Trading Platform field has been added and will populate successfully.

Fetch Web: Resolved an issue where the screen was freezing, disabling functionality when attempting to duplicate a query. Queries can now be duplicated successfully without timing out.

 

API: 

API: Resolved an issue where users were receiving errors when attempting to make calls to the Fee Schedule endpoints. Users can now make calls to Fee Schedule endpoints successfully.

Was this article helpful?
1 out of 2 found this helpful
Have more questions? Submit a request

Comments