The Microsoft Word Active X control is now built into the version 7 Akcelerant Browser Control that is included with version 15 of the Framework. This allows the Microsoft Word Active X control to be used in the Framework without posing a security threat, as the default Internet Explorer Trusted Site security settings marks this control as unsafe.
After upgrading to version 15, each user is prompted to download the new control when running a send letter workflow, accessing Batch Letter Printing or creating/editing a letter template for the first time after the upgrade.
For institutions using the Collections Externally Serviced Accounts extract program: In order for the Collections Externally Serviced Accounts extract program file to be compatible with a person centric version of the Framework, an updated file including the TIN field must be imported. Please contact Fiserv for an updated version of the Collections Externally Serviced Accounts extract program file that includes the TIN field. There are costs associated with this update.
In Framework version 15, the DTS wrapper has been replaced with a BCP wrapper for core and connector executables. As a result, various core and connector executables have been renamed from what they were in previous Framework versions. Additionally, core/connector executable process logs have been enhanced to display records of each core/connector process that has run and whether it completed successfully or failed. Previously, only one record was recorded in the process log to indicate the overall success or failure of the entire core/connector process.
The following table provides a list of version 14 executables that were renamed in version 15.
Core/Connector Process | Version 14 Executable Name | Version 15 Executable Name |
3rd Party Letter Export | caLetterExport.exe | Akcelerant.AccountServicing.Exe.LetterExport.exe |
Account Import (Aftech) | caaftAccountImport.exe | Akcelerant.Connector.AFTECH.Exe.AccountImport.exe |
Account Import (Certegy) | caCertegyAccountImport.exe | Akcelerant.Connector.Certegy.Exe.AccountImport.exe |
Account Import (Miser) | camsrAccountImport.exe | Akcelerant.Connector.Miser.Exe.AccountImport.exe |
Account Import (OSI) | caosiAccountImport.exe | Akcelerant.Connector.OSI.Exe.AccountImport.exe |
Account Import (OTS) | SolutionOTSAccountImport.exe | Akcelerant.Connector.OTS.Exe.AccountImport.exe |
Account Import (Users) | causrAccountImport.exe | Akcelerant.Connector.Datasafe.Exe.AccountImport.exe |
Account Import (Symitar) | casymAccountImport.exe | Akcelerant.Connector.Symitar.Exe.AccountImport.exe |
Account Import (Summit) | casmtAccountImport.exe | Akcelerant.Connector.Summit.Exe.AccountImport.exe |
Account Import (XP) | caxpAccountImport.exe | Akcelerant.Connector.XP.Exe.AccountImport.exe |
Account Number Change | caAcctNumChange.exe | Akcelerant.AccountServicing.Exe.AccountNumberChange.exe |
Aftech Payment Import | caaftPaymentImport.exe | Akcelerant.Connector.AFTECH.Exe.PaymentImport.exe |
Allied CPI Data Export | AlliedInsuranceImportExport.exe | Akcelerant.Connector.Allied.Exe.InsuranceImportExport.exe |
AP Account Services Client Export | PRSClientExport.exe | Akcelerant.Connector.APAS.Exe.ClientExport.exe |
AP Account Services Client Import | PRSClientImport.exe | Akcelerant.Connector.APAS.Exe.ClientImport.exe |
AP Account Services Comment Import | PRSSWBCCommentImport.exe | Akcelerant.Connector.APAS.Exe.CommentImport.exe |
AP Account Services Export | PRSSWBCExport.exe | Akcelerant.Connector.APAS.Exe.Export.exe |
AP Account Services Import | PRSSWBCImport.exe | Akcelerant.Connector.APAS.Exe.Import.exe |
Automated Workflow | caAutomatedWorkflow.exe | Akcelerant.AccountServicing.Exe.AutomatedWorkflow.exe |
CBS Import | CBSImport.exe | Akcelerant.Connector.CBS.Exe.Import.exe |
Collection Advantage Import | CollectionAdvantageImport.exe | Akcelerant.Connector.CollectionAdvantage.Exe.Import.exe |
Comment Export | CommentExport.exe | Akcelerant.AccountServicing.Exe.CommentExport.exe |
Comment Import | CommentImport.exe | Akcelerant.AccountServicing.Exe.CommentImport.exe |
Dialer Export | asDialerExport.exe | Akcelerant.AccountServicing.Exe.DialerExport.exe |
Dialer Import | asDialerImport.exe | Akcelerant.AccountServicing.Exe.DialerImport.exe |
Dialer Update | asDialerUpdate.exe | Akcelerant.AccountServicing.Exe.DialerUpdate.exe |
Falcon Import | FalconImport.exe | Akcelerant.AccountServicing.Exe.FalconImport.exe |
FICS Account Import | caFICSAccountImport.exe | Akcelerant.Connector.FICS.Exe.AccountImport.exe |
GRANT & WEBER Client Export | GWClientExport.exe | Akcelerant.Connector.GrantWeber.Exe.ClientExport.exe |
GRANT & WEBER Client Import | GWClientImport.exe | Akcelerant.Connector.GrantWeber.Exe.ClientImport.exe |
GRANT & WEBER Export | GWExport.exe | Akcelerant.Connector.GrantWeber.Exe.Export.exe |
Income Interruption Import | IncomeInterruptionImport.exe | Akcelearnt.AccountServicing.Exe.IncomeInterruptionImport.exe |
Initialize | caInitialize.exe | Akcelerant.AccountServicing.Exe.Initialize.exe |
Intellect Notes Import | caIntellectNotesImport.exe | Akcelerant.Connector.Datasafe.Exe.IntellectNotesImport |
Miser ALTIN File | camsrALTINExport.exe | Akcelerant.Connector.Miser.Exe.ALTINExport.exe |
Monitor Update | caMonitorUpdate.exe | Akcelerant.AccountServicing.Exe.MonitorUpdate.exe |
Payment Import (Miser) | camsrPaymentImport.exe | Akcelerant.Connector.Miser.Exe.PaymentImport.exe |
Payment Import (OSI) | caosiPaymentImport.exe | Akcelerant.Connector.OSI.Exe.PaymentImport.exe |
Payment Import (OTS) | SolutionOTSPaymentImport.exe | Akcelerant.Connector.OTS.Exe.PaymentImport.exe |
Payment Import (Summit) | casmtPaymentImport.exe | Akcelerant.Connector.Summit.Exe.PaymentImport.exe |
Payment Import (Symitar) | casymPaymentImport.exe | Akcelerant.Connector.Symitar.Exe.PaymentImport.exe |
Payment Import (Users) | causrPaymentImport.exe | Akcelerant.Connector.Datasafe.Exe.PaymentImport |
Payment Import (XP) | caxpPaymentImport.exe | Akcelerant.Connector.XP.Exe.PaymentImport.exe |
Profile Export | ProfileExport.exe | Akcelerant.AccountServicing.Exe.ProfileExport.exe |
Profile Import | ProfileImportAccount.exe | Akcelerant.AccountServicing.Exe.ProfileImportAccount.exe |
Profile Import Payment Import | ProfileImportPayment.exe | Akcelerant.AccountServicing.Exe.ProfileImportPayment.exe |
Promise Check | caPromiseCheck.exe | Akcelerant.AccountServicing.Exe.PromiseCheck.exe |
PSCU ACDEX Import | caPSCUACCDEXImport.exe | Akcelerant.Connector.PSCU.Exe.ACCDEXImport.exe |
PSCU Account Import | caPSCUAccountImport.exe | Akcelerant.Connector.PSCU.Exe.AccountImport.exe |
PSCU Total Collections Client Export | PSCUFSTotalCollectionsExport.exe | Akcelerant.Connector.PSCUFSTC.Exe.ClientExport.exe |
PSCU Total Collections Client Import | PSCUFSTotalCollectionsImport.exe | Akcelerant.Connector.PSCUFSTC.Exe.ClientImport.exe |
SoundBite (Genesys) Export | asSoundBiteExport.exe | Akcelerant.Connector.Genesys.Exe.Export.exe |
SoundBite (Genesys) Import | asSoundBiteImport.exe | Akcelerant.Connector.Genesys.Exe.Import.exe |
Summit CC Vehicle Import | casmtVehicleImport.exe | Akcelerant.Connector.Summit.Exe.VehicleImport.exe |
Summit Legal Info Import | casmtLegalImport.exe | Akcelerant.Connector.Summit.Exe.LegalImport.exe |
Summit Notes Import | casmtHistoricalNotesImport.exe | Akcelerant.Connector.AFTECH.Exe.NotesImport.exe |
Summit Repo Info Import | casmtRepoImport.exe | Akcelerant.Connector.Summit.Exe.RepoImport.exe |
SWBC Insurance Data Exchange | SWBCInsuranceDataExchange.exe | Akcelerant.Connector.SWBC.Exe.InsuranceDataExchange.exe |
Symitar System Parameter Import | casymSysParamImport.exe | Akcelerant.Connector.Symitar.Exe.SystemParameterImport.exe |
Users (DataSafe) Check Data | causrCheckData.exe | Akcelerant.Connector.DataSafe.Exe.CheckData.exe |
Feature | Title | Description | ||
Core/Connector Processes | ||||
7070
9707 |
Microsoft SQL Server 2012 and 2014 Support |
Microsoft SQL Server 2012 and SQL Server 2014 are supported in version 15.00.00 of the Framework.
|
||
10708 | System Management Screen for Branches |
A Branches screen has been added to System Management where administrators can create and maintain branches in the Framework. Branches can be configured for use in loan origination rules authored for disbursement to determine which GL's are allocated and which branch gets credit for creating the loan upon disbursement.
|
||
Fields | ||||
8879 | Lookup Items to be Corrected |
The Field List used throughout the Framework has been cleaned up to resolve discrepancies and inconsistencies with how the fields were listed. As part of this feature, the long display (Location) for Lookup fields has been changed, making them easier to locate within the Field List. For example, in the pre-version 15 Field List, the Account Type - Lookup field had a long display of "Account > Account Information > Account Type > Account Type - Lookup." Now in version 15, the Account Type - Lookup field has a long display of "Account > Account Information > Account Type - Lookup." For updated field lists, please consult the institution's core and connector guides for version 15.
|
||
Rules Management | ||||
6756 | Rule Trace Analyzer |
Rules Management has been enhanced to include a Rule Trace Analyzer. The Rule Trace Analyzer provides the ability to quickly and more efficiently uncover issues within a business rule that prevent successful execution of the rule. With this feature, an Analyze button has been added to the Edit Rule window that enables rule authors to run a trace on a rule directly within the Rules Management Application. Clicking this button runs the rule on a specified object to generate a rule trace and display execution details for rule analysis within the Rule Trace Review screen. From this screen, object values before and after rule execution can be compared and a color-coded visual representation of each rule that ran is provided to identify rule conditions that evaluated to true, evaluated to false or did not execute.
Additionally, a new field, Person ID, is a read-only field that has been added to the Field List for Collection screens. This field can now be configured to appear within a Person screen to display the Person ID value from the database required to run a rule trace on a Person. For more information on this functionality, please see the Akcelerant Framework Administrator Guide. |
||
Screens | ||||
7916 | Screen Preview Capabilities |
A preview button has been added to the screen designer for administrators to view how the screen will appear in the workspace, while the screen is still being configured. This provides administrators with the ability to quickly view how the screen will render without having to leave the Screen Designer, saving time spent on configurations and reducing the chance of configuration errors.
|
||
9510 | Screen Designer - Format Fields |
While configuring screens, administrators have the ability to easily define field Label and Value styles using the new Edit Style window available on a panel's Fields tab. Font size, color, bold and italics can be chosen from drop-downs and check boxes and advanced CSS code can be manually entered.
|
Feature | Title | Description | ||
Core/Connector Processes | ||||
8489 | Connector Naming Convention | Third Party Connector folders have been added to the System Management > Connectors to provide in depth organization and seamless navigation when searching for a connector. Connection pages are contained within the Third Party folder that owns the connector. For example, all Fiserv connectors are located within System Management > Connectors > Fiserv. To view a complete list of the new connector locations, please see the Navigational Changes section of the version 15.00.00 Upgrade Guide. | ||
9351 | Auto Dialer - TCPA Consent Tracking |
The Standard Dialer Interface and the Genesys connector have been enhanced to provide account holders the ability to opt out of future contact because of new TCPA regulations. For more information on configurations that can be made using the opt-out functionality, please see the respective connector guide for the dialer being used.
|
||
9631 10011 10403 10938 10952 |
Luxor Credit ++ Toolkit Support | The Framework has been enhanced to support version 5.1.0.39 of the Luxor Credit ++ Toolkit. Prior to this enhancement the most recent version supported by the Framework was version 5.1.0.34. | ||
Framework Functionality | ||||
10442 | Processes Install - BCP Utility Validation | A validation has been included to confirm that the minimum version of BCP utility is installed. The validation is performed while installing the Processes components during both an initial and upgrade installation. To install the Processes component the BCP utility for SQL Server 2008 and above must be installed. For more information on this installation, please see the Microsoft SQL Server Command Line Utilities requirements in the Hardware and Software Requirements documentation. | ||
Rules Management | ||||
10875 | InRule Support | The Framework now supports version 4.6.13 of InRule. Prior to this enhancement, the most recent version supported by the Framework was version 4.1.9. |
Defect | Core | Description |
Core/Connector Processes | ||
31147 | All/Luxor Credit ++ |
Resolved an issue with Luxor Credit ++ where the value for %Rank displayed incorrectly within TransUnion credit reports.
|
InstallShield | ||
28384 | All | Resolved an issue in the InstallShield Wizard where the name in the Installation/Upgrade completed message box appeared as Configuration Manager instead of Server Manager. |
Rules Management | ||
31089 | All | Resolved an issue with Rules Manager where changes made to a Decision Table were saved when the Cancel button was clicked within the Decision Table edit window. |
Server Manager | ||
31058 | All | Resolved an issue with Server Manager where the Process list did not display the processes in order of start time. To correct this, the Process list now displays the processes in chronological order of start time, beginning with Initialize. |
Miscellaneous | ||
29971 | All |
Resolved an issue that occurred when a user's First or Last name contained an apostrophe (') where a backslash (\) appeared alongside the apostrophe in the user name displayed in the ribbon bar.
|
30444 | All | Resolved an issue where a success pop-up displayed with a validation error message when an invalid format of phone number or email address was populated within a screen. |
Feature | Title | Description | ||
Framework Functionality | ||||
9389 | Screen Validation Rules for Account Servicing | The Validation category has been added to Rules Management to allow administrators to author rules that can be assigned to Account Servicing screens through the Rules tab available in the screen designer. Validation rules can be configured to present warning, error or informational messages to a user upon adding or editing information and clicking Save on the screen in the workspace. | ||
9468 | Account Workflow History and Case Workflow History Combined into a Single Workflow History Screen |
The Account Workflow History and Case Workflow History screens have been combined into a single Workflow History screen. The new Workflow History screen contains an Accounts drop-down and a Cases drop-down that provides users with the ability to filter the data that appears within the screen according to the account and/or case selected within the drop-down(s).
|
||
9768 | Related Loan Application Panel | A new panel has been included in the Collection solution to display loan applications related to a person. To use this panel the Loan Origination solution also has to be active. This panel displays loan applications based on matching the TIN of the person open in the workspace and the TIN on the loan application in Loan Origination. | ||
10348 | Remove Reference to MSXML4 in Akcelerant Browser Control | A feature has been implemented to remove the reference to MSXML4 from the Akcelerant Browser Control, as it is no longer supported or required for Framework version 15. | ||
10409 | Akcelerant Browser Control Marked "Safe for Scripting" | The Microsoft Word Active X control is now built into version 7 Akcelerant Browser Control that is included with version 15 of the Framework. This allows the Microsoft Word Active X control to be used in the Framework without posing a security threat, as the default Internet Explorer Trusted Site security settings marks this control as unsafe. | ||
Core/Connector Processes | ||||
9539 10437 10439 10440 10876 | Corelation KeyStone Connector | The Framework's Collection solution now offers the ability to integrate with Corelation's KeyStone core interface. The KeyStone connector provides financial institutions with a daily batch import of person, loan, share, collateral and payment information along with real time updates of this information when an account is accessed in the Framework workspace. The connector also supports write-back of person information to the KeyStone core and includes three system screens and a Transfer workflow step. For more information about the KeyStone interface, please see the Corelation KeyStone Connector Guide. |
||
10536 | CU Student Choice Connector | A new connector to Credit Union Student Choice (CUSC) has been introduced in the version 15 release of the Framework. This connector allows student loans to be imported into the Framework to allow the information to be viewed and used in functionality throughout the Framework. For more information about CUSC, please see the CU Student Choice connector guide. | ||
10008 | Fields Removed from DataSafe Interface | To improve the performance of the Account import into the Framework, the following DataSafe fields are no longer being populated with data during the import into the Framework: acct_lqd_assets, acct_lqd_worth, acct_tot_assets, acct_tot_lblty, acct_tot_worth and sd_chk_dgt. The changes made to these fields through this feature have no impact to financial institutions; these fields are calculated by DataSafe and are not necessary for use in the Collections or Service solutions. | ||
10090 | SureTrack Connector for the Framework |
The Framework's Collection solution now offers the ability to integrate with the SWBC SureTrack connector. The SureTrack connector provides financial institutions with access to SWBC's insurance claims, auto loan and mortgage processing directly from within the Framework, through SWBC's Insurance Tracking and Claim Service and Loan File Transmission Service. SureTrack also provides the import of collateral protection and mortgage protection insurance policy information from SWBC into the Framework through their Insurance Data Exchange. For more information about the SureTrack, please see the SWBC SureTrack Connector Guide.
|
||
8624 | Symitar Connector Page - Account Import Tab |
A new Account Import tab has been added to the Symitar connector page in System Management to provide administrators with the ability to enter the field paths and file names of the import files from Symitar.
|
||
10406 | XP2 - Change to XP2 Real Time for External Credit Cards |
A new parameter called "Read External Credit Cards" has been added to the XP2 Connector page to prevent or allow external credit cards to update through the real time refresh.
|
Feature | Title | Description | ||
Framework Functionality | ||||
9150 | Restricted Persons on Related Accounts | The Restricted Persons functionality has been enhanced to not display a restricted person in the related person panel. Also, if a person is restricted, any accounts or cases related to the person do not display in the related accounts or related cases panels. | ||
10167 | Enhanced Change Field Workflow Step | The Change Field workflow step has been enhanced to allow a field to have its value changed by copying the value of another field. | ||
10968 | Configuration Manager Dependency Logic |
Configuration Manager export processing has been modified to no longer track dependencies. Previously, Configuration Manager export processing kept track of the item(s) to which an entity in the export package belonged, which would allow administrators to easily see why a related item was included in an export package, but allowed for potential "out of memory" errors to occur during processing of larger export packages. To prevent any possible errors, the dependency logic has been removed from Configuration Manager. The Dependency column has also been removed from the Configuration Manager Export Configurations page in System Management, which does not cause any loss of functionality to Configuration Manager users.
|
||
Rules Management | ||||
9441 | Rules Management Home Screen | The Rules Management home screen has been enhanced to have the same look and feel across all Framework solutions. The Collections and Service Rules Management home screens in System Management now contain a modification history grid to display a record of each action performed within the Rule application along with the date, time and user who performed the action. The Collections and Service Rules Management home screens now also provide the ability for system administrators to view the Rule Application Difference Report, which provides additional details on the changes made within the Rule application. Prior to these enhancements, Collection and Service system administrators were unable to audit or track the changes made within the Rule application. For more information on the Rules Management home screen and the Rule Application Difference Report, please see the Rules Management topics within the Framework Administrator Guide. |
||
Core/Connector Processes | ||||
10735 | Accurint Connector | The Skip Tracing tool has been enhanced to include a new Comprehensive Report (FCRA), and a new Comprehensive Report (Non-FCRA) to comply with FCRA requirements. The BPS Search has also been modified to return results with FCRA requirements. Additionally, new permissions for Accurint skip tracing searches have been added to the Users and Security Groups permissions. For more information on these Products, please see the Accurint Connector Guide. | ||
10865 | Accurint Connector | The Skip Tracing tool has been enhanced to provide complete person-centric skip tracing. Previously, when initiating skip tracing, a prompt was displayed to select an account to perform a skip trace on the primary person related to that account. In version 15.00.00, when initiating skip tracing, the new skip trace is automatically applied to the person that is opened in the workspace. | ||
10210 | Person Centric Support in Fiserv Advantage | The Advantage connector has been updated to support Framework version 15 person centric functionality. Changes include updates to the Advantage batch import process to update and create records according to the person centric architecture. For more information on how Advantage works with Framework version 15, please see the Advantage Connector Guide. | ||
10012 | Allied CPI Blank Service Request | The Allied Repossession workflow step has been enhanced to allow a Blank Repo and Remarketing service request to be used. When executing the workflow, if the account in context is not found within Allied using the Allied Loan Search functionality, the user is now presented with the option to proceed with submitting the service request using a claim form that does not contain any pre-populated information from Allied. | ||
10074 | Allied CPI Blank Claim Form | The Allied File Claim workflow step has been enhanced to allow a Blank Claim Form to be used. When executing the workflow, if the account in context is not found within Allied using the Allied Loan Search functionality, the user is now presented with the option to proceed with submitting the claim using a claim form that does not contain any pre-populated information from Allied. | ||
9650 | AP Account Services - Charge Off and User Defined fields | The AP Account Services connector has been enhanced to allow an institution to map Charge Off and User Defined fields and include them in the export sent to SWBC. | ||
10213 | Person Centric Support in Fiserv CBS | The CBS connector has been updated to support Framework version 15 person centric functionality. Changes include updates to the CBS batch import process and real time refresh to update and create records according to the person centric architecture. For more information on how CBS works with Framework version 15, please see the CBS Connector Guide. | ||
10214 | Person Centric Support in Fiserv CUBE | The CUBE connector has been updated to support Framework version 15 person centric functionality. Changes include updates to the CUBE batch import process and the real time interface. For more information on how CUBE works with Framework version 15, please see the CUBE Connector Guide. | ||
10264 | CU Recovery Connector | The CU Recovery connector has been enhanced to automatically transmit the nightly batch account export file and the nightly batch notes import file via a secure FTP. A financial institution can now create a CU Recovery queue within the Framework to identify and house the accounts to send to CU Recovery, rather than manually generating a report of this information, as done in previous versions of the Framework. For more information on the new CU Recovery functionality, please see the CU Recovery Connector Guide. | ||
9455 | Equifax, Experian, TransUnion |
The Framework has been enhanced to run soft credit report inquiries for collection efforts to avoid affecting credit scores that are used for new financing.
|
||
10866 | Equifax, Experian, TransUnion | The Credit Reporting tool has been enhanced to provide complete person-centric credit reporting. Previously, when initiating credit reporting, a prompt was displayed to select an account. In version 15.00.00, when initiating credit reporting, the new credit report is automatically applied to the person that is opened in the workspace. | ||
10758 | Account Number sent to Genesys | The person's account number has been included at the end of the export file sent to Genesys to be used in text message scripts. The person number is sent to Genesys in lieu of the account number if an institution's core does not import the account number in to the Framework. | ||
9238 | Grant & Weber Connector | The import process for the Grant & Weber connector has been enhanced to automatically update the connector's version number at Grant & Weber. Prior to this enhancement, this version number had to be manually updated in order to import files after a version upgrade, requiring support from an Akcelerant Customer Care Representative. Now, the version number for the Grant & Weber connector automatically updates in the Grant & Weber database when files are imported. | ||
9169 | IBS Transaction Code Improved Handling | The IBS interface has been enhanced to provide system administrators with the ability to create and edit IBS Transaction Codes from within the Framework. The new IBS Transaction Codes page is enabled in System Management upon activation of IBS in the Framework and lists all Transaction Codes currently configured for the financial institution. From this page, administrators can edit the Transaction Codes as well as create new Transaction Codes for deposits and loans. For more information on the new Transaction Codes page, please see the IBS Connector Guide. | ||
10068 | IBS Import Additional Loan File Attributes |
The IBS connector has been enhanced to import the following fields into the Framework:
|
||
9392 | Miser | The process that sets the Delinquent Flag for an account in the Framework has been updated to set the flag when the Delinquent (DQ) Amount is greater than zero and the Due Date is in the past. | ||
10212 | Person Centric Support in FIS Miser | The Miser connector has been updated to support Framework version 15 person centric functionality. Changes include the addition of the Account Import tab on the connector page in System Management and updates to the Miser batch import and real time refresh processes to update and create records according to the person centric architecture. For more information on how Miser works with Framework version 15, please see the Miser Connector Guide. | ||
9642 | NACHA Connector Enhancements | The NACHA Connector has been enhanced to provide the ability to export files in a Combined Credit and Debit NACHA format. With this enhancement, institutions are able to export information in a single output file including multiple credit and debit transactions as separate batches. To support this, a Combined Debit and Credit NACHA Format option has been added to the ACH File connection parameter that appears in the NACHA connector page. Additionally, the NACHA connector now also supports the ability to transfer an export file to a secure FTP. The NACHA connector page in System Management has been enhanced to include a Transfer Method drop-down that enables the ability to set the transfer method as Network, FTPS via SSL or SFTP via SSH. If FTPS or SFTP are selected, additional parameters appear to identify the URL, Username, Password and Port values required for connection. |
||
7081 | OTS | The OTS connector has been updated to support Framework version 15 person centric functionality. Changes include updates to the OTS batch import and real time refresh processes to update and create records according to the person centric architecture. For more information on how OTS works with Framework version 15, please see the OTS Connector Guide. | ||
9115 | Person Master Support in PSCU Total Collections | The PSCU TotalCollections connector has been enhanced to work with person-centric Framework version 15. While there are no changes to the functionality of this connector in the Framework, person records are now created upon import into the Framework and information is now stored at the person-level within the database. | ||
9431 | State National CPI Connector Additional Account Holder Mapping |
The CPI State National/CUNA Mutual connector has been enhanced to provide financial institutions with the ability to define how account matches are found between State National and the Framework. An Account Number Matching section has been added to the CPI State National/CUNA connector page for administrators to define the formats of their Account Numbers and Loan Numbers within the Framework and State National. During daily batch processing and while working within the State National screens and workflow steps, the formula defined on the connector page is used to update and present the correct State National account information within the Framework. If an account match is not found, the account is displayed within the new State National CPI Unmatched Accounts report that institutions can provide to State National to help resolve any unmatched accounts. For more information on this new functionality, please see the CPI State National/CUNA Mutual Connector Guide.
|
||
10747 | Symitar Payment Reversal Support |
The Symitar daily batch import process and real-time refresh have been enhanced to handle reversed payments. Prior to this enhancement, payment reversals in Symitar were imported and displayed as regular payments in the Framework. If the original payment had been applied to a promise, rather than subtracting the amount reversed from the promise payment, the payment amount was incorrectly added to the Amount Paid. Now, payment reversals are recorded as reversals (Adjustments) on the Payment History screen and the Symitar Payment Import process has been enhanced to collect additional details about payment transactions during the import into the Framework.
|
||
10215 | Person Centric Support in D+H UltraData | The UltraData connector has been updated to support Framework version 15 person centric functionality. Changes include updates to the UltraData batch import process and the real time interface. For more information on how UltraData works with Framework version 15, please see the UltraData Connector Guide. | ||
8453 | Support for XP2 APEX | The Framework's interface with XP2 has been enhanced to use XP2's APEX real time architecture to update information within the Framework in real-time. This enhancement does not change any functionality within the Framework; it only updates the real time architecture to use a web service call instead of dll's. |
Defect | Core/Connector | Description | ||||||
Core/Connector Processes | ||||||||
30147 | All/Accurint | Resolved an issue with the Accurint connector where only User Permissions were applied when permissions were split between User and Group permissions. | ||||||
30273 | All/Accurint | Modifications have been made to the tool tip for the New button and Submit button on the Accurint Skip Tracing Screen to provide more clarity about the function of the button. | ||||||
28726 | All/Advantage | Resolved an issue with the Advantage connector where the account import process was unable to complete successfully and an error was received when trying to run the import. | ||||||
28518 | All/Allied CPI |
Resolved an issue with Allied CPI connector screen where a user was required to enter information within the required fields when trying to disable the connector and save the changes to the connector screen.
|
||||||
28607 | All/Allied CPI |
Resolved an issue with the Allied CPI Connector where an error message was received upon execution of a workflow including the Allied Repossession Workflow Step.
|
||||||
28725 | All/Allied CPI |
Resolved an issue with the Allied CPI connector where an error was received when trying to add an attachment with a Pre-Skip request Type to the Allied Repossession Workflow Step.
|
||||||
28877 | All/Allied CPI |
Resolved an issue with the Allied Repossession Workflow step where the right-hand side of the fields within the Vehicle Information section appeared cut off.
|
||||||
31568 | All/Allied CPI | Resolved an issue where incorrect field mappings appeared within the Auto File and Mortgage File tabs of the Allied CPI connector page. | ||||||
32042 | All/Allied CPI | Fixed an issue where the Status field value for an Allied CPI Skip or Pre-Skip request appeared twice within the Allied Request Status screen. | ||||||
32059 | All/Allied CPI |
The Production and Test CHub and RHub URL's for the Allied CPI connector have been updated as follows for the version 15.00.00 release of the Framework:
|
||||||
32020 | All/Certegy | Resolved an issue with the Certegy account import where an error did not appear in the Process log, nor was the status of the import updated to reflect an import failure, when the import process failed due to the import file containing a null character in the Certegy version. Now, when a Certegy import file has a Certegy version that is not a number, an error is recorded within the Process Log. | ||||||
31505 | All/ Credit Solutions | Resolved an issue with the Credit Solutions Client Export where the output files on the FTP site generated credit card numbers instead of account numbers. | ||||||
27768 | All/Evans - Simpson | Resolved an issue with the Evans Simpson connector where the ESA Data Import executable function restarted after the process was already run for the day and failed. To correct this, the ESA Data Import executable function now increments NextRunTime to the day after the executable is run when the process fails to complete. | ||||||
30895 | All/Evans - Simpson | Resolved an issue with the Evans Simpson connector where data was not populating for the Expiration/Cancel Date and Status fields within the search results displayed on the ESA Status Notification Screen. | ||||||
30896 | All/Evans - Simpson | Resolved an issue with the Evans-Simpson connector where incorrect Status Information populated within the Status field in the Coverage Information section of the ESA screen's Borrower Information tab. | ||||||
30898 | All/Evans - Simpson | Resolved an issue with the Evans-Simpson connector where data did not populate within the Date and Balance fields that appear in the Balance Information section of the ESA screen's Borrow Information tab. | ||||||
31829 | All/Evans - Simpson | Resolved an issue with the Evans Simpson connector where the Evans Simpson Report was not able to be run successfully. | ||||||
29157 | All/FICS |
Resolved an issue with the FICS connector where the customer configuration for when to create mortgage accounts from a third party was being ignored. To resolve this, the code has been changed to read the parameter in the database and create or not create mortgage accounts according to that configuration.
|
||||||
31794 | All/Grant & Weber |
Fixed an issue with the Grant & Weber connector where All Accounts were not being sent to Grant & Weber when the parameter was set on the connector page.
|
||||||
24104 | All/OTS | Resolved an issue with the OTS connector where Account fields could not be created and mapped within the OTS User Field Mappings screen in System Management. | ||||||
29610 | All/PSCU - Collection | Corrected a defect where the PSCU - Collection connector page did not contain enough information in the Person Linking section. The Person Linking section of the connector page now clearly explains which linking options apply to what PSCU files. | ||||||
30520 | All/PSCU - Collection | Resolved an issue with the PSCU - Collection connector where the Account Type drop-down on the connector page defaulted to Mortgage instead of Credit Card. | ||||||
31077 | All/PSCU - Collection | Resolved an issue with credit cards in the PSCU import where the account number on accounts created at the core processor was changed to the credit card number during the import. This resulted in the masked credit card number being displayed in the Related grid though the credit card number should only return in the Credit Card Number field, not in the Account Number field, when the credit card is created by the Core Processor. | ||||||
15767 | All/ PSCU TotalCollections | Resolved an issue with the PSCU Total Collections import where comments were not being imported into the Framework. | ||||||
31445 | All/ PSCU TotalCollections |
Resolved an issue with the PSCU TotalCollections connector where duplicate records appeared in the Related Accounts export file.
|
||||||
31506, 31491 | All/ PSCU TotalCollections | Resolved an issue with the PSCU TotalCollections connector where credit card numbers were being sent in the Accounts and Related Accounts files rather than the account number when the account included one or more credit cards. Now, the Accounts and Related Accounts files contain a masked value for Account Number, if the Account Number is the same as Credit Card Number. | ||||||
28715 | All/ SWBC AP Account Services | Fixed an issue in the SWBC AP Account Services Connector where Masked Credit Card numbers sent to SWBC, that included the same last four digits, but belonged to different people, were all linked to the same accounts. To correct this, the linking has been modified to ensure that Credit Cards are related to the correct accounts. | ||||||
30068 | All/ SWBC AP Account Services | Fixed an issue with the APACCOUNTSERVICESCLIENTEXPORT process where the Framework did not correctly generate PRS files in the old format when tblGlobalParameter.PRSVERSION was set to an old/previous PRS version. | ||||||
31508 | All/ SWBC AP Account Services | Resolved an issue with the APAS connector where credit card numbers were sent in the Accounts/Collaterals/Payments file rather than the account number when the account included one or more credit cards. Now, these files contain a masked value for Account Number, if the Account Number is the same as Credit Card Number. | ||||||
31570 | All/SWBC Insurance | Resolved an issue where incorrect field mappings appeared within the Auto File and Mortgage File tabs of the SWBC Insurance connector page. | ||||||
32130 | All/SWBC Insurance |
Resolved an issue in the SWBC Auto Collateral screen where the Credit Life field was incorrectly labeled as "Credit Lift" and was displayed as a text box rather than a check box. To correct this, the Credit Life field is now labeled correctly and appears as a check box within the screen. The value of this field is set to false in the database when the check box is blank and true when it is enabled.
|
||||||
Field Configurations | ||||||||
28532 | All |
Corrected the spelling of fields that displayed "Sourceentifier" instead of "SourceIdentifier."
|
||||||
32156 | All | Resolved an issue where values deleted from the Department lookup in Field Configurations appeared in the Department drop-down for Case Queues. | ||||||
Profile Import | ||||||||
28678 | All | Fixed an issue with Profile Import where the "Should Overall Process Fail" flag in the profile import configuration was not being honored correctly. | ||||||
29616 | All | Resolved an issue with Profile Import where addresses marked as the default address were not being set correctly after the import. To correct this, a Default Address Flag is now available for addresses to enable the Profile Import to set an address as the default address through this flag. | ||||||
29782 | All |
Resolved an issue where a Profile Import failed and no accounts were imported when an invalid year for a date was included in the import file. Now, when an invalid year is in a date field in an import file, the Profile Import no longer fails; the invalid date is omitted, the accounts are imported, and the Profile Import completes successfully. |
||||||
31091 | All | Resolved an issue where Profile Imports that were set with the Collections Processing Flag set to true received an error when trying to build the import. | ||||||
31400 | All |
Fixed an issue where profile imports failed when the import contained a field with a data type of DECIMAL or PERCENT.
|
||||||
31518 | All | Resolved an issue with Profile Import where the import type could be changed after the import was created. | ||||||
32147 | All | Resolved an issue with Profile Import where an error was received upon import due to the profile import failing to create demographics when data was missing in the person creation key field in the import file. | ||||||
Queues | ||||||||
31036 | All | Resolved an issue with Collection Queues where numbers appeared in the bottom left corner of the person workspace after the Get Next button was clicked when working a queue. | ||||||
32052 | All | Resolved an issue with Queues that occurred after the queue type was changed from a Dialer queue to an Internal Queue where accounts continued to be excluded from the queue when related accounts were assigned to other queues. | ||||||
Reports | ||||||||
13967 | All | Resolved an issue with the Akcelerant Report Viewer where scroll bars were inserted within the frame when the report included multiple pages and was in Landscape View. | ||||||
24781 | All |
Resolved an issue in Reports where a field to display a vendor name was not available to add to a Report. To correct this, the following two fields have been added to the Field List and can now be added to a report:
|
||||||
31175 | All | Resolved an issue with Reports where the results returned within a report did not match the results returned within a View and/or the database. | ||||||
31426 | All | Resolved an issue with Reports where an error stating "The Report Server could not be reached" was received when trying to run or access a report in the Framework. | ||||||
Screens | ||||||||
15607 | All | Resolved an issue where manual changes to the Next Contact Date value on an Account screen required two saves to be retained | ||||||
26258 | All | Resolved an issue where the Recovery Overview screen in the View Screen Workflow Step did not properly display in 1024x768 screen resolution. | ||||||
26465 | All |
Resolved an issue with the Third Party Field Audit screen where an error was received when trying to open the screen.
|
||||||
28393 | All | Resolved an issue with the Judgment Amount Field where decimal values were being rounded to the nearest whole number. | ||||||
28739 | All | Resolved an issue with the Workflow History screen where the From and To date range fields could not be manually edited without selecting the calendar. | ||||||
29019 | All |
Resolved an issue where the Created by, Created Date, Modified by and Modified Date fields were not available to add to the following screens and panels:
|
||||||
30537 | All | Fixed an issue where an error was received when a comment was changed by adding text that included angled brackets (<>). | ||||||
30540 | All |
Resolved an issue with screen panels where a horizontal scroll bar did not appear in panels that contained a simple grid.
|
||||||
30739 | All |
Resolved an issue in the Recovery Overview screen where an error was received when trying to open the Documents screen.
|
||||||
30835 | All | Resolved an issue with the Account and Case Documents screen where an error was received when trying to upload Microsoft Word or Excel documents. | ||||||
31302 | All |
Resolved an issue with the Account Documents screen where all accounts related to the person did not appear within the Select an Account drop-down list when trying to upload a document.
|
||||||
31752 | All |
Resolved an issue with the Payment Amt value field where a money symbol ($) was not prefixed to the payment amount in the Related Accounts grid panel in the person workspace.
|
||||||
32198 | All | Resolved an issue with the Documents screen where Microsoft errors were received when trying to open a .docx or .xlsx file that was uploaded to an account or case. | ||||||
Workflows | ||||||||
28569 | All |
Resolved an issue with the Next Contact Date workflow step where an error was received upon executing the workflow step.
|
||||||
28677 | All | Resolved an issue where an error was received when executing a workflow that included an automatic Create Case step as a Batch workflow. When this occurred, no Event log exceptions appeared and the batch workflow was marked active within the Workflow History screen as expected. | ||||||
28708 | All |
Resolved an issue where comments populated in Post comments section were cut off after the special characters ' & ' or ' # ' when a workflow was executed from the Workflow tab in the left navigation panel. |
||||||
29994 | All | Resolved an issue that occurred when a workflow was run as a batch workflow where users were able to complete workflow tasks belonging to workflow queues they were not assigned permission. Now when a user tries to a complete workflow task that belongs to a workflow queue they are not assigned permission, a message displays informing that 'The next step is assigned to another user. You cannot make any further progress on this workflow.' | ||||||
30280 | All |
Resolved an issue with automated workflows where an error was received when trying to run an automated workflow that included address criteria.
|
||||||
31057 | All | Resolved an issue that occurred when running a multi-account workflow from a case process where duplicated accounts appeared within the account selector window. | ||||||
31469 | All |
Resolved a typographical error in the Queuing tab of the Send Email workflow step where the first user permission displayed the word "Allows" instead of "Allow."
|
||||||
Workspace | ||||||||
28006 | All | Resolved an issue where the Links drop-down in the workspace did not include a scroll bar, which prevented access to hyperlinks at the bottom of the list when multiple hyperlinks appeared. To correct this, a scroll bar has been added to the list to enable the ability to easily access all hyperlinks within the Links drop-down. | ||||||
29732 | All | Resolved an issue where an error was received when a comment including angled brackets (<>) was added in the Post Comment section of the workspace. | ||||||
30020 | All |
Resolved an issue with the Notepad where lines or carriage returns in the comments added were not represented as HTML tags.
|
||||||
30422 | All | Resolved an issue where the cancel button within the max number of workspaces open pop-up did not function when a user tried to open a seventh person workspace. | ||||||
31410 | All | Resolved an issue that occurred when a multi-line comment was added to the Workspace Notepad where HTML tags appeared for the line breaks in the comment. This prevented users from adding additional notes until the tags were removed. | ||||||
Miscellaneous | ||||||||
26568 | All | Corrected an issue where configured workflows were not being run on accounts based on matching Dialer Return Code values. | ||||||
28690 | All | Resolved an issue with Case Processes where a new case process could not be created with the same name as a deleted case process. | ||||||
28702 | All |
Resolved an issue where custom fields created as a zero decimal Number appeared as Money fields with a "$" symbol in Views.
|
||||||
30057 | All | Resolved an issue with the User Performance Dashboard where the To date could not be set to a date in the past, or the same day as the From date, when the From date was set to a date in the past. | ||||||
30062 | All | Corrected an issue where multiple instances of a Framework process were kicked off via Process Manager, when only one instance of an executable should be running at a time. | ||||||
30999 | All | Resolved an issue that occurred when two or more roles were assigned to a letter and the letter was being sent on an account with a case selected, where a letter was generated for each person in the Send Letter workflow step, but the primary person's name populated next to each letter. | ||||||
31526 | All | Corrected an issue where a custom field could not be saved if another field in a different Category had the same Field Label value. | ||||||
31631 | All | Corrected an issue that occurred during a basic search where the default address for a person appeared in the Search screen instead of the account holder's home address. | ||||||
31808 | All |
Resolved an issue where companies were not listed alphabetically within the Export Company drop-down when creating an Account Assignment Export in System Management > Exports.
|
||||||
Core Specific | ||||||||
24267 | Advantage (AFTECH) | Fixed an issue in Advantage (AFTECH) where data was imported into the Framework and Database when the DTS_FLAG parameters were set to 0 (or disabled). | ||||||
29517 | DataSafe |
Resolved an issue where E-Statements in DataSafe were changed from a Yes to No value when a phone number on an account was deleted in the Framework.
|
||||||
31591 | DNA |
Resolved an issue in DNA where the password was missing from the password tag when Auth Method 1 was selected on the Collections-DNA connector page.
|
||||||
26532 | IBS (Metavante) |
Resolved an issue in IBS (Metavante) where the Last Extension Date field did not provide a calendar to select a date and displayed an error upon saving the screen when an invalid value, such as 13/18/2014, was entered in the field.
|
||||||
31477 | IBS (Metavante) | Resolved an issue with the IBS (Metavante) account import where delinquency data was cleared on a failed import due to missing files. | ||||||
22237 | Miser | Fixed an issue with the Miser Account Import where the Email address did not populate when creating or updating an account. | ||||||
26691 | Symitar |
Resolved an issue in Symitar where the Overdraft Tolerance field was not updating correctly within the Framework after the value was updated within the Symitar.
|
||||||
29047 | Symitar |
Resolved an issue in Symitar where delinquent Charged Off Shares were not being marked as delinquent during the batch Symitar Account Import.
|
||||||
29361 | Symitar |
Fixed an issue in Symitar where Closed Accounts were refreshed when the workspace was rendering. Since the account was closed, the refresh was causing an error.
|
||||||
29602 | Symitar | Resolved an issue with Symitar Warning Codes where duplicate account records appeared in a View when a Symitar warning code was configured to appear in the View criteria. | ||||||
30479 | Symitar | Resolved an issue in Symitar where the Symitar account import process failed due to the Collateral Tracking information from the Account and Loan Tracking files configured in the Framework. | ||||||
31412 | Symitar |
Resolved an issue with the Symitar Real Time Refresh process where an "invalid card" error was received when trying to refresh a Closed account related to a person that no longer existed in Symitar.
|
||||||
31809 | Symitar |
Resolved an issue in Symitar where a screen mapped to the View screen workflow step as a part of a multi-account workflow appeared broken in the person workspace when the multi-account workflow was executed.
|