Toll Free 1-877-506-2744
How can we help?

2017-10-10 - Release Notes

Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Important New Features

 

Fixes

  • Fixed an issue where copying a custom scenario name with special characters in it created irregular scenario names.
  • Fixed an issue that prevented custom scenario and loan names from showing on Opportunity printouts.
  • Fixed an issue that caused Facility Ratings to show in the default loan and scenario name when using a different calculation method.
  • Fixed an issue that prevented Prime from showing as the Funding Curve Family for Fixed Rate Spread Lock in certain cases.
  • Fixed an issue that prevented some Administrators from adding or editing Activity Types for Activity Based products.
  • Fixed an issue that allowed users to see information from the administrative section without the required administrative rights.
  • Fixed an issue where using capital letters caused SSO login to fail.

 

Improvements

  • Changed the "Copy Scenario" menu option in the Scenario Builder to "Duplicate Scenario" to clarify that this option creates a new duplicate scenario.
  • Made an improvement to preserve the order of scenarios within the Scenario Builder.
  • Advanced Analytics users now have access to an Information tab within the Advanced Analytics popup, which contains a unique, searchable Short Code for each commercial loan account on the opportunity. For more details, please contact our Support team.
  • In the past, if Administrative users didn't have the security rights to edit the Regions, Security Profiles, Users and Funding Packages parts of the Administrative section, the user could still see (but not access) those sections. We've improved this so that if an Administrative user doesn't have rights for a particular part of the Administrative section, then that section will not be displayed.

 

API & Integrations

  • Fixed an issue where PrecisionLender didn't attach the Default Salesforce Relationship to an opportunity if the relationship sent from Salesforce did not exist.
Was this article helpful?
Have more questions?