Important Upgrade Information
Configuration Manager Import User
The user running a Configuration Manager import via Server Manager must have SQL access to the database, as Configuration Manager only uses trusted connections to connect to the target database.
DNA - Person Centric file for Collections Externally Serviced Accounts Extract Program
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 may be costs from Fiserv for this update. Please contact Fiserv for details. |
Symitar - External Loan Record PowerOns
After upgrading to version 15.01, three new PowerOns must be installed to include external loan records in the Symitar batch interface. For more information, please see feature 10967 within this document as well as the Symitar Connector Guide.
Framework Core
New Features
| Feature | Title | Description | ||
| Event Processing | ||||
| 11091 | Custom Event Type |
The ability to define a custom event is now available from the Event Processing page in System Management. A new event titled Custom Event has been added to the Events tab which provides the ability to fire an event/action pair according to a custom event code. This enables administrators to customize when an action occurs in an application according to the unique business needs of their institution.
|
||
| Server Manager | ||||
| 11147 | AkcelerantTemplatingPlugin | An Akcelerant Templating Plugin executable file has been included in the Website\session\AkcelerantTemplatingPluginSetup folder. This plugin is used to install 32 bit Active X controls that are required for Framework Letter templates and provides the ability to install controls for users that do not have administrator access to system settings. | ||
| 11464 | Server Manager to Force Running as Administrator | A feature has been implemented to prevent Server Manager from opening if it is not run as an administrator. If Server Manager is not run as an administrator, an error is received stating it must be run as an administrator and Server Manager cannot be accessed. | ||
| Upgrade Specific | ||||
| 11141 | Install Visual C++ Redistributable 2012 | The CUNA Calculator requires Visual C++ Redistributable 2012 to be installed on the Framework server. To accommodate this, an Install Visual C++ Redistributable 2012 task has been added to the Installation Summary screen allowing Visual C++ Redistributable 2012 to be installed during the Framework installation process. | ||
| 11155 | Support for Custom MVC Views and Controllers |
The Framework has been enhanced to prevent custom routes, controllers and views from having to be reinstalled after an upgrade to version 15.01. The files in which routes, controllers and views are stored are no longer overwritten during the upgrade process.
|
||
| 11315 | Support for Custom Exe's | A feature has been implemented to enhance the Framework installer to retain custom executables during an install of 15.01. Prior to running the 15.01 installer, a file named Custom.xml can be created in the Framework's Exe directory by Akcelerant or the financial institution, depending on who created the custom executables. The Custom.xml file lists the file names of all custom executables installed at the financial institution, and the file names listed within this file are not deleted from the Exe directory during the installation process. The Custom.xml file is also not deleted during the installation process. Prior to these enhancements, the installation process would delete any custom executables and they would have to be recreated. For more information and directions on how to create the Custom.xml file, please see the Important Notes Regarding the Upgrade topic of the Framework 15.01 Upgrade Guide. | ||
Enhancements
| Feature | Title | Description |
| Rules Management | ||
| 11372 | InRule Version | The Framework has been enhanced to support version 4.6.27 of InRule. Prior to this enhancement, the most recent version supported by the Framework was version 4.6.16. |
Defects
| Defect | Core | Description |
| Reports | ||
| 33619 | All | Resolved an issue with Reports that occurred after being upgraded to version 10.31.20 or later of the Framework where an error was received when trying to 'Save And Edit' a report that was created in a version prior to 10.31.20 and included one or more fields with an underscore character ( _ ). |
| Rules Management | ||
| 34834 | All | Resolved an issue with Rule Trace Analyzer where an error was received after entering a value for the rule to run on an clicking Analyze. |
| Miscellaneous | ||
| 32415 | All | Corrected an issue where no search results were returned if a space was added to the beginning or end of a search field value. |
| 32526 | All | Corrected a defect where creating a 1,024th field within System Management > Custom Fields caused an unfriendly error message to display within the Framework interface and Error Log. Now, when attempting to create and save a 1,024th field within Custom Fields, a friendly error message is displayed to indicate that only 1,023 custom fields can be created. |
| 33681 | All | Corrected an issue where a custom lookup field could be modified to point to a different lookup list after it was created. Now, once a custom lookup field has been created, the lookup list associated with that field cannot be changed. |
| 32961 | All | Corrected an issue with User Credential configuration where a user could be saved with a missing Credential Password even though the password was required. |
Collection
New Features
| Feature | Title | Description |
| Core/Connector Processes | ||
| 10837 | Symitar - Include Suffix in Full Name Field | The Symitar batch import has been enhanced to include Suffix in the Full Name field. Prior to this enhancement, the Full Name field created during the batch import included First Name, Last Name and Middle Name. Now, the Full Name field includes First Name + Last Name + Middle Name + Suffix. |
| 10967 | Symitar - External Loan Record Support | A new method for importing external loan records from Symitar into the Framework has been implemented. This method, called the External Loan Module, imports external loan records such as mortgages and credit cards into the Framework in files using three new PowerOns - AKSW.EXTERNALLOAN, AKSW.EXTERNALLOANTRACKING and AKSW.EXTERNALLOANNAME. Previously, external loan information could only be imported into the Framework through Account Tracking Records. These new PowerOns and files provide financial institutions with more robust, better organized external loan information as well as the ability to import data into the Framework that is not available in the Account Tracking Record method. Financial institutions interested in using the External Loan Module to import external loan records should contact Symitar. Once an agreement is in place with Symitar, Akcelerant will assist with implementing the module according to the financial institution's needs. |
| 11518 | Support for Symitar 2015.00 SP5 | The Framework has been tested against and is compatible with Symitar version 2015.00 SP5. |
| 10888 | TransUnion - Collection Prioritization Engine Connector | The TransUnion Collections Prioritization Engine connector introduces the ability to score account batches to show which accounts you are most likely to collect from. By using the CPE connector, an institution is able to prioritize their collection efforts and resources by focusing on accounts that are more likely to be collected from rather than pursuing uncollectible accounts. |
| 11083 | PSCU TotalCollections Queue Exclusions | A Queue Exclusions section has been added to the PSCU TotalCollections connector page to provide administrators with the ability to define the accounts that are included in and excluded from the export to PSCU based on related accounts in non-PSCU queues. If the "Exclude from TotalCollections" check box is selected for a queue within the Queue Exclusions list, related accounts in the queue as well as the account in the TotalCollections queue, are not sent to PSCU. If the "Exclude from TotalCollections" check box is not selected for a queue within the Queue Exclusions list, related accounts in the queue and the account in the TotalCollections queue are sent to PSCU. For more information on this functionality, please see the PSCU TotalCollections Connector Guide. |
Enhancements
| Feature | Title | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Core/Connector Processes | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 10738 | SWBC ECM MoneyGram | The ECM Payment workflow step has been enhanced to include a Payment in Person tab. This tab allows for cash transactions to be accepted, rather than ACH or Credit, and provides a method of locating a MoneyGram near the financial institution. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 10624 | DataSafe- Encryption of Host and User Passwords |
The DataSafe interface has been enhanced to encrypt the values of the Host and User Passwords in the database. Prior to this enhancement, Host and User Password values were not encrypted, which posed a security risk for financial institutions. Now, the value of the Teller and User Passwords configured on the Fiserv DataSafe connector page are automatically saved to the database in encrypted form. Additionally, a new credential titled DataSafe - Collection has been added to the Credentials tab in the Edit User window to enable the ability to configure a DataSafe credential for each user that is automatically encrypted.
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| 10697 | PSCU - Expanded Balance and Status Account Import |
The PSCU Balance and Status Account import has been enhanced to include a new Expanded Balance and Status file type. The Expanded Balance and Status file contains additional fields for the total cash out, annual cash rate and annual purchase rate.
With this enhancement a new File Type connection parameter has been added to the PSCU - Collection Connector page to provide administrators the ability to select the standard Balance and Status import or the Expanded Balance and Status Account import. |
||||||||||||||||||||||||||||||||||||||||||||||||||
| 10890 | Allied CPI Enhancements | The Allied CPI connector has been enhanced to provide Framework users with the ability to view additional details regarding a service request, such as repossession and remarketing information, within the new Service Request Details screen accessed through the Allied Request Status screen. The Allied Claim Tracking screen has also been enhanced to include the Confirmation Number of the claim in context. Previously, these details were not included in the Allied interface. Additionally, the Allied CPI connector page has been modified to replace the CHub and RHub URL fields with one Service URl field, in which administrators can input the Test and Production Allied URLs. For more information on these enhancements, please see the Allied CPI Connector Guide. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 11064 | Include User Defined Fields in UltraData Write Back | This feature has corrected an issue where the write back to the UltraData core was erasing data within User Defined fields in UltraData. Now after updating address and/or phone information in the Framework, the updates are sent to UltraData through real-time write back functionality without erasing any information in UltraData. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 11520 | Associate Symitar Joint Account Persons to Loans |
The Symitar loan import has been enhanced to add Joint Name records to loans based on the ECOA Code field. Previously, Joint Name records could not be added to the Framework through the ECOA Code field. Now, when the ECOA Code field contains a value of 02 (Joint Contractual), 03 (Joint User) or 04 (Joint), joint account holder information is automatically added to the loan if the Joint Name record does not already exist in Symitar and the Framework.
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| 11528 | Person Centric Support in FIS IBS |
Updates have been made to the IBS interface to support the successful import of person and account information during the batch and real time imports. With this feature, several issues have been corrected which impacted the import of certain person and account information after the switch from account-centric to person-centric Framework functionality.
The following issues have been corrected with this feature:
Additionally, this feature has enhanced how promise and payment information is imported and updated for Loans and Deposits. A financial institution now has the ability to control how much promise and payment information is loaded into the Framework by configuring the METAVANTE_PAYMENT_MONTH_SEED parameter during the implementation process. For example, if the Seed value is set to 24, two years of promise and payment information is imported from IBS into the Framework. After the first time the account is viewed in the Framework, the Effective Date is set and with subsequent views of the account, any additional promise and payment information added to IBS since the Effective Date is imported. |
||||||||||||||||||||||||||||||||||||||||||||||||||
| 12015 | NCD Workflow Step to Not Hardcode User ID Assignment |
The Collections module has been enhanced to provide institutions with the ability to allow individuals utilizing the Next Contact Date workflow step to assign the account in context to other Lifecycle Management Suite users. Previously, when a user would set an assigned user ID during the Next Contact Date workflow step, the user who ran the workflow would automatically be assigned to the account. Now, if Hide return setting options on the Next Contact Date Step is not selected in System Management > Administrative Settings, users have the following options when running the Next Contact Date workflow step
In addition to this enhancement, the Collections module has been enhanced to further support skip record functionality. Prior to this enhancement, upon completing a workflow for an account, the account, any related accounts in the same queue, and any related accounts in a different queue would be marked as skipped even if the workflow was completed. Now, the Skip Record on an account in a queue only occurs when a user is working in a queue and clicks Get Next without taking any actions. Any related accounts for the person in context, regardless of whether they are in the same queue being worked or not, will not be skipped. |
||||||||||||||||||||||||||||||||||||||||||||||||||
| Reports | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 10891 | Add Collateral Code and Purpose Code to Workflow/Comment and Promise Report Types |
The following fields have been added to the field list used on the Fields and Criteria tabs for the Promise and Workflow/Comment Report types, providing the ability for additional account workflow fields and promise data to be included in user-defined reports:
|
||||||||||||||||||||||||||||||||||||||||||||||||||
| Screens/Panels | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 11507 | Related Persons Field for Related Accounts Panel | The Related Accounts panel has been enhanced to provide quick and easy access to the persons related to each account listed in the panel. A new Related Persons field is now available to be added to the Related Accounts panel which displays an alphabetical, comma delineated list of all persons related to each account associated with the person-in-context. The name of each person appears as a hyperlink that, when clicked, navigates directly to the workspace of the selected person. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Upgrade Specific | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 11343 | Readiness Report Enhancement to Prevent Data Loss for Property Fields | A new Readiness Report test titled "Property Address data may be lost during upgrade" has been implemented to determine if property address data for an account exists across tblAccountCollateral, tblAccountMortgage and tblAccountSecured in the database, as data in these tables is consolidated into a single record after the upgrade. This is a warning test that lists the accounts that have property address information stored within the three tables that are combined after the upgrade. For the accounts that are returned in the test results, the property address data must be migrated to custom fields prior to the upgrade or data will be lost. For more information on this Readiness Report test and how to resolve it, please see the 15.01 Upgrade Guide. | ||||||||||||||||||||||||||||||||||||||||||||||||||
| 11517 | Enhancements to Upgrade Process for Importing Address, Phone and Email Records and Phone Information Displayed in Person Summary Panel |
The upgrade process for importing Address, Phone and Email records from the following Cores has been enhanced to set the Source ID of a record based on whether it was added in the Framework or imported from the Core during the upgrade:
Prior to this enhancement, the Source ID for all records, even those manually added in the Framework, was set to "Core," resulting in records being deleted after an upgrade since they did not exist in the import file. The table below provides an overview of the Address, Phone and Email records imported from each Core during the daily batch import:
Now, when an Address, Phone and/or Email record that was added prior to an upgrade does not include one of the aforementioned types imported from the Core, the Source ID of the record is set to "Framework" during the upgrade to prevent the record from being deleted during the next nightly import. With this feature, the Modified Date for each Address, Phone and Email record is also now imported during an upgrade. In prior versions, the value of the Modified Date was not updated in the Framework after an upgrade. Now, the Modified Date for each record is imported and set to the value of the Created Date during the upgrade in order to easily determine whether a record for a person is valid. Additionally, the Person Summary panel in the person workspace has been enhanced to only display the phone numbers related to the record for the person- in-context. Prior to this enhancement, all phone numbers related to an account holder's Person Master record were displayed, which resulted in outdated phone numbers appearing in the workspace. Now, only the phone numbers for the person record in context are displayed in the Person Summary panel. A new icon appears next to the first phone number listed in the panel to provide easy access to any additional phone numbers included for the person in the Person Master record. For institutions using DataSafe, Miser, OTS and Spectrum: As a part of this feature, the daily batch import process has been enhanced to delete any Address, Phone and Email records that include a Source ID of "Core,” but are not imported from the Core during the Daily Batch Import. For institutions using Advantage, CBS, Corelation Keystone, DNA, IBS, Symitar and XP2: The same behavior that is noted above for Address, Phone and Email records occurs during the daily batch import process, however, the enhancement was made as a part of other features. |
||||||||||||||||||||||||||||||||||||||||||||||||||
Defects
| Defect | Core | Description | ||
| Core/Connector Processes | ||||
| 34879 | All/Accurint | Resolved an issue with the Accurint connector where the value configured for the BPS Search check box was not maintained after an upgrade. | ||
| 32107 | All/ApplicationXtender | Resolved an issue with the ApplicationXtender Export process where the process was able to run and complete, but no documents were exported. | ||
| 32112 | All/ApplicationXtender | Resolved an issue with the ApplicationXtender Documents screen where all documents in ApplicationXtender were displayed in the screen, rather than the documents related to a specific account in the workspace.To correct this, the ApplicationXtender Documents screen has been made an Account level screen and now only displays the documents related to the account in context in the workspace. | ||
| 33210 | All/Banko | Corrected an issue where the Banko Is Monitored flag was missing from the field list for screens, reports and workflow criteria. | ||
| 34990 | All/Banko | Resolved an issue with the BANKO History screen where data that existed in the screen prior to an upgrade did not appear in the screen after the upgrade. | ||
| 33058 | All/Certegy, PSCU | Corrected an issue where the Certegy and PSCU imports did not process due to the Person Linking parameters upgrading incorrectly. | ||
| 33709 | All/Certegy | Corrected a defect where the Days DQ Adjust parameter on the Certegy connector page was a check box instead of a text box. Previously, when the Days DQ Adjust check box was selected, the days delinquent calculation on credit card accounts in the 300 file would only adjust by 1 day. Now, the days delinquent calculation can be adjusted by an administrator-defined number of days. | ||
| 33948 | All/Certegy | Resolved an issue with the Certegy connector where the DaysDelq columns in the database were populated with an incorrect scale of the amounts during the Certegy Account Import. | ||
| 34515 | All/Certegy, FICS, PSCU | Resolved an issue with the Certegy, FICS and PSCU connectors where the default ACCOUNT_TYPE was set as a string value, rather than a numeric value, which caused the connectors' imports to fail. | ||
| 34075 | All/CPI State National/CUNA |
Resolved the following issues that occurred upon opening the Insurtrak screen:
|
||
| 32689 | All/Credit Solutions | Resolved an issue where files were not archived correctly during the Credit Solutions Client Import. | ||
| 33668 | All/Credit Solutions | Resolved an issue with the Credit Solutions Client Export process where flag values were represented with a value of 'TRUE'/'FALSE' rather than '1'/'0'. | ||
| 34103 | All/Evans-Simpson | Resolved an issue with the Evans Simpson Connector where an existing ESA Claim was not able to be associated to a new or updated Policy number (CreditorPlacedId field). Now, an ESA claim that was originally filed under one policy can be updated with a different policy number. | ||
| 34442 | All/Evans-Simpson | Corrected a defect where documents could not be uploaded to Evans-Simpson using the Framework's Evans-Simpson File Transfer functionality. | ||
| 32408 | All/Experian | Resolved an issue where credit model scores did not populate within an Experian credit report when a credit report with Risk Models RM-BQ and RM-AF was pulled. | ||
| 33547 | All/Experian | Fixed an issue with the Experian connector where Experian Credit Reports failed with the message "Cannot find Credit Reports path." | ||
| 32963 | All/Grant and Weber | Resolved an issue where an error was received when trying to test the connection on the Grant and Weber connector page. | ||
| 32964 | All/Grant and Weber | Resolved an issue where an error was received upon trying to save the Grant and Weber connector page when the Charged Off Date or Charged Off Amount field was set to any field present in tblAccountInfo. | ||
| 30975 | All/PSCU - Collection | Resolved an issue with the PSCU - Collection connector where Days DQ for delinquent accounts did not increment when an account was not included in the PSCU file on a given day. | ||
| 33094 | All/PSCU - Collection | Resolved an issue with the PSCU - Collection connector where the value for AccountNumber was overwritten with the value of the CreditCardNumber from PSCU during the PSCU Account Import. | ||
| 33508 | All/PSCU - Collection | Resolved an issue with the PSCU - Collection connector where the PSCU ACCD Import failed with a "File Name cannot be null" error. | ||
| 33718 | All/PSCU - Collection | Resolved an issue with the PSCU - Collection connector where PSCU Host Payments were not updated in the payment history after the PSCU Account Import was run. | ||
| 33809 | All/PSCU - Collection | Resolved an issue with the PSCU - Collection connector where AccountRelationships for Coborrowers created from core were deleted during the PSCU Import when the coborrower was not in the PSCU import file. | ||
| 33986 | All/PSCU - Collection | Resolved an issue with the PSCU - Collection connector where the PSCU ACCDEX process failed after being run due to the size of the SpouseName and PSCUBehaviorScore columns in the staging table. | ||
| 34878 | All/PSCU - Collection | Resolved an issue with the PSCU - Collections connector where the PSCU import process failed due to a NULL value in the Time Zone field included in the import file. | ||
| 34027 | All/ PSCU TotalCollections | Resolved an issue with the PSCU TotalCollections connector where the export process failed when line feed and carriage return characters were included in the comments file. | ||
| 32341 | All/SWBC AP Account Services | Resolved an issue with the SWBC AP Account Services connector where the Import and Export processes were not tied to a solution in the database and Client Processes were not set to automatically activate. | ||
| 32916 | All/SWBC AP Account Services | Resolved an issue with the SWBC AP Account Services connector where promises were not created properly after the APAS client import and old promise-to-pays from SWBC were being used rather than a newly created promise. | ||
| 33584 | All/SWBC AP Account Services | Resolved an issue with the SWBC APAS Client Export where cents were not included in the value of monetary fields in the account file. | ||
| 33688 | All/SWBC AP Account Services | Resolved an issue with the SWBC AP Account Services connector where addresses were not exported when an account included a related person who did not have a 'Home' type or 'Work' type address. Now, addresses with a type of 'Other' type are exported. | ||
| 34998 | All/SWBC AP Account Services | Fixed an issue in the AP Account Services Client Payment Export where payments in excess of 99999.99 caused the APAS process to fail. To correct this, when the payment amount exceeds 99999.99, the max amount of 99999.99 (8 characters) is now returned in place of the of the exact payment amount. | ||
| 34417 | All/SWBC Insurance | Resolved an issue with the SWBC Insurance connector where Collateral Address data did not populate in the SWBC Insurance Mortgage file. | ||
| Cases | ||||
| 34233 | All | Resolved an issue that occurred upon creation of a new case where duplicate accounts for that case were created in the Framework. | ||
| 34692 | All | Fixed an issue where errors were received when the CaseTaskProcessor EXE was executed in Workday Schedules. | ||
| Custom/Calculated Fields | ||||
| 33666 | All | Resolved an issue where the Loan Balance field was not available in the field list to build a calculation for a Case or Case Repossession type calculated custom field. To correct this, Loan Balance is now an available field to add to a Case or Case Repossession type calculated custom field under the Case > Repossessions > Assignments folder. | ||
| 33681 | All | Corrected an issue where a custom lookup field could be modified to point to a different lookup list after it was created. Now, once a custom lookup field has been created, the lookup list associated with that field cannot be changed. | ||
| 34205 | All | Resolved an issue where calculated custom fields created as a decimal were saved as an integer and were displayed as an integer in the Framework. | ||
| 34488 | All |
Fixed an issue where custom fields with apostrophes were not displaying in the Screens field list due to these fields not converting properly after the upgrade to version 15.00.
|
||
| Dashboards | ||||
| 33138 | All | Resolved an issue with the Collector Production dashboard where information for individual collectors was not being updated for the current date. | ||
| 33187 | All | Resolved an issue with Dashboards where the Bar Chart configured in a dashboard displayed negative values. | ||
| Fields | ||||
| 32301 | All |
Resolved an issue where the Account > Description and Account > Specialty Processes > Charge Off > Charge Off Type fields did not appear in the Field List. To correct this, both fields have been added to the Field List and are available to be assigned within the following locations:
|
||
| 32302 | All | Resolved an issue where the Cost Center field did not appear in the Field List for Reports. To correct this, the Cost Center field has been added to the Field List and is now available to add to an Account type report. The field path for this field is as follows: Account > Account Information > Expenses > Cost Center. | ||
| 32968 | All | Corrected an issue where collateral values for RetailValue and ValuationAmount from the Vehicle file did not display correctly within the Account Collateral screen. | ||
| 33126 | All | Corrected an issue where fields appeared to be mapped incorrectly after an upgrade from version 10 due to Short Display values for fields not matching across field lists. To correct this, a new Readiness Report Test titled Field List Inconsistencies has been created to show the variations in Short Displays that are associated to a single field. | ||
| 33245 | All | Resolved an issue where values for Late Charge Due, Last Amount Paid and Payment Frequency did not populate within the fields on an Account Panel when an Account screen including the panel was opened in the workspace. | ||
| 33267 | All | Resolved an issue where the Date Created field did not appear in the Field List after an upgrade. To correct this, Account > Date Created is now available within the Field List. | ||
| 33437 | All | Resolved an issue where the Loan Number field did not appear in the Field List. To correct this, the Expense > Account > Loan Number field has been added to the Field List. | ||
| 33832 | All | Resolved an issue where the value entered for the PlanInterestRate field in the Repayment Information panel on a Bankruptcy Case screen was rounded to a whole number and did not maintain the decimal value when the screen was saved. To correct this, the value for the PlanInterestRate field is now rounded to two decimal places. | ||
| Letters/Emails | ||||
| 33380 | All | Fixed an issue where an "Unterminated string constant" error was received when trying to run Batch Letter Printing on a letter that included a carriage return. | ||
| 33552 | All | Resolved an issue with Batch Letter Printing where the Batch Print Letter selected in a manual Send Letter workflow step did not appear in the Batch Letter Printing screen after the workflow was complete and the letter's XML was generated. | ||
| 34177 | All | Resolved an issue that occurred when a letter included a field with multiple lines of data where the data did not print in multiple lines in the letter when the letter was printed from Batch Letter Printing. | ||
| Profile Import/Other Batch Imports | ||||
| 32406 | All | Resolved an issue that occurred when using Profile Import to import data for an AccountIndentifier where the Profile Import failed if duplicate AccountIdentifiers were found in the database. | ||
| 33281 | Al | Resolved an issue with Profile Import where the credit card import failed due to a missing field in the AccountMassage stored procedure. | ||
| 33306 | All | Corrected an issue with Profile Import where the import failed when the file contained Integer fields due to a formatter conflict. | ||
| 33961 | All | Corrected an issue in the Profile Import file layout generator where the Third Party ID field was not being upgraded correctly. | ||
| 34091 | All | Resolved an issue where the Profile Import and QueueRefreshBatch processes failed when the values of QueueRefreshBatchID and AccountID were too large. | ||
| 34109 | All | Resolved an issue that occurred when more than 1000 accounts were in a Profile Import where imported accounts after the 1000th had mixed up data. | ||
| 34460 | All | Resolved an issue that occurred when an account in the Profile Import file did not exist in the Framework where the Profile Import (Update) failed and the account was not added to the Profile Import's Skip table. Now, when a file containing an account that does not exist in the Framework is imported through an Update Profile Import, the account is logged to the Profile Import's Skip table and the process continues without failure. | ||
| 34618 | All | Fixed an issue with batch import processes where the import failed when carriage returns were included between rows of data in the import file. To correct this, the Framework now accepts carriage returns between full rows of data in the import file. Rows separated mid-field or mid-row by a carriage return no longer prevent the import process from completing and are now skipped and logged in the BCP log file. | ||
| 34702 | All | Resolved an issue with Profile Import where creating an update only Profile with Phone fields broke the Profile build. | ||
| 34727 | All | Resolved an issue with Profile Import where the profile import failed when trying to import data that included percentage fields. | ||
| 34902 | All | Resolved an issue with Profile Import where the Created By value for person records was incorrectly set during the import. Now, the value of Created By is set to System User for person records that are imported via Profile Import. | ||
| Promises | ||||
| 32188 | All | Fixed an issue where new promises were assigned Promise IDs of Closed/Broken promises. | ||
| 34258 | All | Resolved an issue where payments imported via real-time on an account with an open promise were not properly applied to the Amount Paid on the promise since the cents portion of the amount was removed during the refresh and only the full-dollar amount was applied to the promise. | ||
| Reports | ||||
| 33174 | All | Resolved an issue where Advanced reports containing a graph with a pie chart were reset to a regular chart type when the report was opened with the Report builder. | ||
| 33377 | All | Resolved an issue with the predefined report Task Performance Summary by Department, Chart where an error was received after populating the Dates, Ticket Types and Ticket status and trying to generate the report. | ||
| 33639 | All | Resolved an issue where statistics were updating incorrectly within the Collector Production report. | ||
| 34777 | All | Resolved an issue with the Collector Production report where an error appeared in the Date Created column when the report was generated in a CSV file format. | ||
| 34807 | All | Resolved an issue where an error was received when trying to run a Report including the "Claim Paid Date" field. | ||
| 34943 | All | Resolved two issues that occurred after an upgrade when the "Workflow/Comment > Created By > Lookup" field was included in a Report where selecting the field did not display both the last name and first name of the user and Reports that used the field in its criteria could not able to be saved if the Report came over from the Upgrade. | ||
| 35014 | All |
Fixed an issue with Reports where duplicate results were returned in a Report when both a custom account field and the fields listed below appeared in the Report fields and/or criteria:
|
||
| Rules Management | ||||
| 35041 | All | Resolved an issue in Rules Management where the action template Stop Executing Actions was not available for rules authored under the Root.Person and Root.Account entities. | ||
| Screens | ||||
| 32754 | All | Resolved an issue where an error was received when trying to save a Case screen that included Service Request fields. | ||
| 32797 | All | Resolved an issue where the Mortgage ID field was not available to be added to any screen/panel types within the Collection screen designer. | ||
| 34132 | All | Resolved an issue that occurred when uploading a document to the Account Documents screen where the 'Select an account' drop-down defaulted to the first account in the list rather than the account currently in context for the screen. | ||
| 34302 | All | Resolved a performance issue with the Workflow History screen where the screen took an extended amount of time to load in the workspace when a large amount of records were included in the workflow history. | ||
| 34468 | All | Resolved an issue with the Related Loan Application Panel where applications were only listed in the panel when the person in context was the primary applicant. | ||
| 34474 | All | Resolved an issue where the contents in pre-loaded account type screens did not update when the account was changed in the screen's account selector drop-down. | ||
| 34566 | All | Fixed an issue on the Merge Accounts screen where the workspace automatically opened when a single account was returned in the search results. | ||
| 34763 | All | Resolved an issue where duplicate messages were displayed in the Rules driven Messages panel configured to appear in a Person type screen. | ||
| Upgrade Specific | ||||
| 33799 | All | Resolved an issue with the Readiness Report that runs to make sure all values in float fields are valid to be converted to a decimal where a value with more than three decimal places was not being returned as a bad value. | ||
|
34016 |
All | Resolved an upgrade issue where an error was received when running the Readiness Report for Field List Inconsistencies. | ||
| 34125 | All | Resolved an issue where collateral fields, such as Collateral Value and Collateral Value Date, were not updated in the Framework after an upgrade. | ||
| 34598 | Al | Resolved an issue that occurred during an upgrade where an error was received when an existing record for a process dependency appeared in the database. | ||
| 34986 | All | Resolved an upgrade issue where PH4 Phone and PH5 Phone fields were not mapped to the correct values after an upgrade. Now, PH4 Phone fields are mapped to a value of Fax and PH5 Phone fields are mapped to a value of Other after an upgrade. | ||
| 35098 | All | Resolved an issue where blank Phone records were created during an upgrade when the original record in version 10 was blank. Now, the upgrade script has been modified to exclude phone records with blank phone numbers. | ||
| Workflows | ||||
| 32472 | All | Corrected an issue where the screen in a view screen workflow step appeared blank when a user navigated away from the workflow to a different workspace screen and then returned to the workflow. | ||
| 32710 | All | Resolved an issue where Automated Workflows including fields with alias names in the criteria failed upon execution. | ||
| 33055 | All | Fixed an issue where Automated letters were duplicated during execution of an Automated workflow that included a Person field in the workflow criteria. | ||
| 33175 | All | Resolved an issue where Non-Person workflows could not be opened from a workflow queue. | ||
| 33283 | All | Fixed an issue with the Reason workflow step where Reason Codes did not display within the Reason drop-down when a workflow including the Reason step was run in a Case Task. | ||
| 33304 | All | Resolved an issue where Automated letters generated from an Automated workflow including a Person field in the workflow criteria were duplicated when the workflow was manually run. | ||
| 34107 | All | Resolved an issue where the Workflow Design tab failed to load when the ServerHTTPRequest property was not set to true. | ||
| 34148 | All | Resolved an issue with the Post Comment workflow step where the workflow step could be created with an automated comment that included invalid characters. Now, when invalid characters are entered for an automated comment, an error message is displayed upon saving the Post Comment workflow step. | ||
| 34353 | All | Resolved an issue with the Change Field workflow step where the specified field was not updated to the correct value in each account when the workflow step was run in a multi account workflow. | ||
| 34447 | All | Resolved an issue that occurred when the View Screen workflow step was configured in a multi-account workflow where the screen in the workflow step did not display information pertaining to the account identified within the Account Selector drop-down. | ||
| Workspace | ||||
| 32703 | All | Resolved an issue where addresses for joints/coborrowers did not appear within the Related Persons grid or the Person Information screen in the workspace. | ||
| 33996 | All | Resolved an issue where an error was received when opening the person workspace when the user had a NULL value in the label for one or more favorites. | ||
| 34242 | All | Resolved an issue where an error was received upon opening a workspace for a person with a large number of related accounts. | ||
| 34279 | All | Resolved an issue where space breaks added to a comment were not maintained after the comment was posted in the Post Comment section of the workspace or through a workflow. | ||
| 34390 | All | Resolved an issue that occurred when getting the next current, delinquent account in a queue where the account appeared as In Process by the user who just accessed the account. | ||
| 34391 | All | Resolved an issue that occurred when getting the next current, delinquent account in a queue where the account appeared as In Process by "SYSTEM SYSTEM" though the account was not currently being worked. | ||
| 34392 | All | Resolved an issue where a timeout error was received when trying to open a workspace with over 700 related accounts. | ||
| 34471 | All |
Resolved the following two issues that occurred upon opening multiple workspaces in the Framework:
|
||
| 34568 | All | Resolved an issue where an error was received in the workspace when text including newline characters (Enter) appeared in the Notepad. | ||
| 34744 | All | Resolved an issue where the HTML name of some special characters was displayed in the Comment window when it was opened from the Workflow History tab in the workspace. | ||
| 35126 | All | Resolved an issue that occurred when multiple collectors were working the same queue where the next account presented in the workspace with Get Next was not skipped if the account was assigned to another collector. | ||
| Miscellaneous | ||||
| 32720 | All | Resolved an issue where the ObjectId and ObjectTypeId associated with the Collections.CollateralObjectMap table were audited when an account including a collateral was accessed in Framework. | ||
| 33059 | All | Corrected an issue where a user was unable to edit their own comments unless Change permission to "Edit All Comments" was granted. | ||
| 33237 | All | Resolved a queuing issue where accounts/persons were not presented to be worked in a queue when the Next Contact Date for an account was set to the same date, but different time on the same date. When one account/person was being worked in a queue, and the user navigated away to work another account/person in the same queue, the previously worked account was skipped and an automated comment was added to the account's Workflow History screen to identify the account as skipped. | ||
| 33287 | All | Resolved an issue where a large amount of workflows could not be assigned to the View & Execute permission for a Security Group at one time. | ||
| 33496 | All | Resolved an issue where addresses, phone numbers and email addresses for persons with no open accounts were displayed in the Framework. | ||
| 33580 | All | Resolved an issue in Server Manager where the Initialize process was not setting the SYSTEMCURRENTDAYSTART global parameter to midnight of the current day. To correct this, after the Initialize process is run, the global parameter value 'SYSTEMCURRENTDAYSTART' is now set to the date the process is run and a time of Midnight. | ||
| 33731 | All | Corrected an issue where the Source Identifier field was not displayed for each person within the Resolve Multiple Persons Found exception window in Third Party Exceptions. | ||
| 33793 | All | Resolved an issue where an error was received when trying to run an Account Export in System Management > Exports. | ||
| 34111 | All | Fixed an issue where an error was received when performing an initial search for an account. | ||
| 34267 | All | Resolved an issue in Archive Data where a blank error message was displayed upon clicking Perform Archive when the criteria included the "Date Last Paid" field. | ||
| 34497 | All | Resolved an issue where the MonitorUpdate process was unable to complete and could only be ended by stopping the process in Windows Task Manager. To correct this, the MonitorUpdate process has been modified to run at user-specified interval, rather than staying open throughout the day. The Monitor parameters within the Collection Setting tab in System Management > Solutions > Collections have also been updated to ensure the Monitor process has sufficient time to run, even when Batch mode and the latest Monitor Last Run Time are selected. | ||
| 34651 | All | Resolved an issue where the error that appeared in tblProcessLog due to aGetProcess timeout was recorded as a LoadConfig error and did not include complete information for the reason the error was recorded. To correct this, a more detailed explanation of the error now appears in tblProcessLog when a GetProcess timeout occurs. | ||
| 34814 | All | Resolved an issue that occurred in the Default Values tab in Field Configurations where the drop-down value in the Select Value section of the Configure Default Value screen did not update when different status codes were selected. | ||
| Core Conversion | ||||
| 33222 | DataSafe to Corelation KeyStone | Resolved an issue that occurred upon switching an interface from DataSafe to Corelation KeyStone where errors were received during the real time refresh for a person/account imported via the DataSafe account import process when the DataSafe connector was de-activated with the real time and write flags ON and the KeyStone core activated. | ||
| Core Specific | ||||
| 33998 | Aftech | Corrected an issue in Aftech where deposit accounts were not assigned the correct Account Type during the batch account import from the Core. | ||
| 24647 | CBS | Resolved an issue in CBS where insufficient information was included in the uspSolutionCBSProcessImport stored procedure which resulted in the failure of the CBS Import in both test and production when the stored procedure was called. | ||
| 32410 | CBS | Resolved an issue in CBS where payments were not imported during the CBS Import process. | ||
| 33819 | Corelation KeyStone | Resolved an issue in Corelation KeyStone where the Account Number did not populate within the Loan Number field in the ECM workflow step when the account's primary person did not have a record in Core.Person.Account. | ||
| 34796 | Corelation KeyStone | Resolved an issue in Corelation KeyStone where the Delinquent Date & Delinquent Flag were updated during Real Time Refresh though no payments were made. | ||
| 33527 | DataSafe | Resolved an issue in DataSafe where the account import process for members failed when the CollectorAlert field included carriage return characters. | ||
| 33582 | DataSafe | Resolved an issue where the DataSafe Account Import failed at the Loan step due to the mapping of some field values being set to an incorrect data type. | ||
| 33614 | DataSafe | Resolved an issue where the ThirdPartyID for ThirdParty Mortgages was updated to an incorrect value during the DataSafe Account Import. | ||
| 33839 | DataSafe |
Resolved mapping issues in the DataSafe Loan Import where some of the field values imported into the Framework were not formatted correctly. To correct this, updates have been made to the format of following fields:
|
||
| 34006 | DataSafe | Corrected an issue in DataSafe where deposit accounts were not assigned the correct Account Type during the batch account import from the Core. | ||
| 34397 | DataSafe | Resolved an issue that occurred when a report in DataSafe included UserFields where accounts without any records in a UserField database table did not appear in the report though they met report criteria. | ||
| 34577 | DataSafe | Resolved an issue with the DataSafe Account Import where the value for Interest Accrued was incorrectly imported as a scientific notation when the value included more than 15 decimal places. | ||
| 34898 | DataSafe | Resolved an issue with the DataSafe Transfer Workflow Step where an Event Log exception was received though the workflow step completed successfully. | ||
| 34999 | DataSafe | Resolved an issue in DataSafe where Joint owners that were removed from accounts in DataSafe continued to appear as a Joint owner on the account in the Framework after the DataSafe Account Import. | ||
| 33495 | DNA |
Resolved an upgrade issue in DNA where the upgrade failed when any of the following fields appeared in the criteria for a queue, automated workflow, etc:
To resolve this, the aforementioned fields have been modified from a string field to a lookup field. |
||
| 33632 | DNA | Resolved an issue with the DNA Account Import where records with the same PersonNumber but different OwnerFlag value were removed from the Member Staging table when the import was run. | ||
| 33769 | DNA | Resolved an issue with the DNA account import where real estate collateral was not being imported from the account file. | ||
| 34004 | DNA | Corrected an issue in DNA where deposit accounts were not assigned the correct Account Type during the batch account import from the Core. | ||
| 34218 | DNA | Resolved an issue that occurred during the DNA Account Import where addresses for the imported accounts/persons were mapped as 'Other Address' type and did not appear in letters generated with the Send Letter workflow step. | ||
| 34248 | DNA | Resolved an issue where the DNA Account Import failed due to records not being cleared from the caApplication.StagingHostPersonMapping table in the database prior to the import. | ||
| 34344 | DNA | Resolved an issue with the DNA Account Import where a primary person's relationship to the accounts in the import was not updated or created during the import. | ||
| 34359 | DNA | Resolved an issue in DNA where person records were updated with address information from business records during the real time refresh. | ||
| 34631 | DNA | Fixed an issue that occurred after the DNA Account Import where the AddressType for the Address 1 field was set to a value of Other Address rather than Home Address. Now, after the DNA Account Import, the Address 1 field is set to an Address Type of Home and the Address 2 field is set to an Address Type of Other. | ||
| 34731 | DNA | Resolved an issue that occurred during the DNA import where duplicate person records were created for accounts imported via profile import. | ||
| 34733 | DNA | Fixed an issue in DNA where the PersonNumber was imported with an incorrect pre-fix for Business and/or Non-Business accounts. | ||
| 34858 | DNA | Resolved an issue that occurred when an additional applicant was added to an application in DNA where demographic information for the additional applicant was not imported from the Core. | ||
| 32812 | IBS (Metavante) | Resolved two issues with the IBS (Metavante) account import process where Role Types for Primary and Joint were not created during the import and the person workspace of a person/account imported via the IBS (Metavante) account import could not be opened from Search, Views or Queues. | ||
| 33276 | IBS (Metavante) | Corrected an issue in IBS where the real time promise check process failed due to data type discrepancies. | ||
| 33503 | IBS (Metavante) | Corrected an issue with the real time refreshing of IBS accounts where the SourceIdentifier was being used to retrieve Person information rather than the PersonNumber. Now, only the PersonNumber is used when requesting the refresh from the IBS. | ||
| 34000 | IBS (Metavante) | Corrected an issue in IBS where deposit accounts were not assigned the correct Account Type during the batch account import from the Core. | ||
| 33521 | Miser | Resolved an issue in Miser where the Account Import process was unable to complete successfully due to issues with the Account Import Stored Procedures. | ||
| 33828 | Miser | Resolved an issue in Miser where the BCP Import failed when the import file included a ASCII value of NULL. | ||
| 33984 | Miser | Resolved an issue in Miser where the payment import failed when the value for payment due date or effective date was NULL. | ||
| 34003 | Miser | Corrected an issue in Miser where deposit accounts were not assigned the correct Account Type during the batch account import from the Core. | ||
| 34059 | Miser | Resolved an issue where CONNECT.Miser did not appear as an option in the Application Services section of Server Manager, preventing the connector from being activated or deactivated using Server Manager. | ||
| 34074 | Miser | Resolved an issue that occurred after an upgrade in Miser where Primary role codes were not created with the Miser Account Import. | ||
| 34384 | Miser | Resolved an issue in Miser where the Miser service did not take in the IP Address from the database during a real time refresh which resulted in the real-time refresh connection failing. | ||
| 27560 | OTS | Resolved an issue with the OTS Post Comment Workflow step where user-entered Expiration Dates were ignored though the value for "allow user to change Expiration Date and Comment Text at run time" was set to true. | ||
| 32486 | OTS | Resolved an issue in OTS where information for related accounts was not displayed within the OTS real time Related Accounts Screen. | ||
| 34008 | OTS | Corrected an issue in OTS where deposit accounts were not assigned the correct Account Type during the batch account import from the Core. | ||
| 32871 | Spectrum (Summit) | Corrected an issue with the Framework Spectrum batch import where persons from the JOIN file were not properly created when the SSN appeared to have less than 9 digits due to Spectrum not padding the SSN value with leading zero(s) if the SSN began with zero(s). | ||
| 33003 | Spectrum (Summit) | Resolved an issue with the Spectrum Batch Import where account relationships for Secondaries were not created correctly during the import when a Secondary was created through a Profile Import. | ||
| 33006 | Spectrum (Summit) | Corrected an issue in Spectrum where secondary borrowers on first party Credit Cards were not identified as secondary borrowers in the Framework after the standard Spectrum batch account import. | ||
| 33690 | Spectrum (Summit) | Corrected an issue where the Summit core-specific screens were not consistently named. Now, all Summit screen names are prefixed with "Spectrum." | ||
| 34071 | Spectrum (Summit) | Resolved an issue with the Spectrum Account Import where duplicate records were imported for charged off credit card accounts. | ||
| 34093 | Spectrum (Summit) | Resolved an issue where the wrong Balance Amount was displayed in the Spectrum Transaction History screen when the balance was less than $1.00 and greater than $0.00. | ||
| 34449 | Spectrum (Summit) | Fixed an issue in Spectrum where Charged Off payments were not recorded in the Payment History screen after the Spectrum Account and Payment imports were executed. | ||
| 34654 | Spectrum (Summit) | Resolved an issue in Spectrum where the same joint owner was added to an account each time the Joint file was imported during the Spectrum Account Import. | ||
| 34714 | Spectrum (Summit) | Resolved an issue where joint owners that were deleted from Spectrum were not deleted from the Framework after the Spectrum Account Import. | ||
| 34719 | Spectrum (Summit) | Resolved an issue that occurred due to the Record Type field not being used to differentiate the Loan account from the Share account in Spectrum where payments imported via the Spectrum Payment Import process did not post to a Loan account when the Loan account had the same account number as a Share account. | ||
| 34861 | Spectrum (Summit) | Resolved an issue in Spectrum where incorrect Payment values were imported due to incorrect field lengths for payment fields in the Spectrum Payment Import file. | ||
| 34870 | Spectrum (Summit) | Resolved an issue with the Spectrum Payment Import where account numbers were imported as a scientific notation when the payment record in the Spectrum Payment Import file included an account number with eight or more digits. | ||
| 34871 | Spectrum (Summit) | Resolved an issue where the Spectrum Payment Import did not fail if the PaymentMassage or PaymentMove stored procedures were not found. To correct this, an error is now received if these stored procedures are not found during the Spectrum Payment Import. | ||
| 33024 | Symitar | Fixed an issue where the Symitar Tracking Records configuration tool did not use the mapping in the database and all values from tracking records were sent to the same fields. | ||
| 33247 | Symitar | Resolved an issue in Symitar where the value for Delinquent Days Past Due for credit card accounts was not updated correctly due to the DaysSincePayment column including a NULL value after the import. | ||
| 33253 | Symitar | Fixed an issue in Symitar where the Warning Code 4 field in the Framework was not updated with the value from the AKSW.ACCOUNT file. | ||
| 33539 | Symitar | Resolved an issue that occurred in Symitar where an error was received that prevented the Akcelerant.Connectors.Symitar.Exe.CollectionHistoryImport exe from importing historical collection data including comments and Next Contact Date successfully. | ||
| 33971 | Symitar | Fixed an issue in Symitar where negative balances in the AKSW_LOAN file did not maintain the "-" when the amount displayed in the Framework. | ||
| 33983 | Symitar | Resolved an issue that occurred when a Symitar Warning Code Flag was added to the criteria for a Collection Queue where number of accounts in the queue updated to zero when queue was refreshed. | ||
| 33992 | Symitar | Resolved an issue in the Symitar Transfer Records screen where a transfer type of "Off Cycle" did not display within the Transfer Record grid. Now, when "Off Cycle" is the selected transfer type, a value of "Off Cycle" populates within the Transfer Type column on the Transfer Records screen. | ||
| 34005 | Symitar | Corrected an issue in Symitar where deposit accounts were not assigned the correct Account Type during the batch account import from the Core. | ||
| 34025 | Symitar | Fixed an issue in Symitar where Views pulling collateral records failed due to duplicate records in Collateral that were added with the Tracking Records Import. | ||
| 34315 | Symitar | Fixed an issue in the Symitar Account Import where all business accounts were linked to one TIN. | ||
| 34458 | Symitar |
Fixed an issue where the Symitar Account Import failed when the Credit Balance Limit Diff field was set to a money value, such as 1.00. |
||
| 34755 | Symitar | Fixed an issue in the Symitar Payment Import where payments with decimal amounts (ie. 1060.54) were rounded during the import and populated in Payment History with a rounded down amount (ie. 1060.00). | ||
| 34851 | Symitar | Resolved an issue in Symitar where new email addresses were not being created during the Symitar Account Import. | ||
| 34951 | Symitar | Resolved an issue in Symitar that occurred when the Save and Close button was clicked without editing person information in the Symitar Name Records screen where duplicate person records were created in the database and displayed in the Related Persons panel in the Framework. | ||
| 35026 | Symitar | Resolved an issue in Symitar where only the first two digits of Credit Reporting Code was imported during the Symitar Account import process. | ||
| 35055 | Symitar | Resolved an issue that occurred during the Symitar Account import process where the value for the ACCMEMGR Field in the Symitar Account Import file was not imported into the Core.Person > MemberCode field. | ||
| 30636 | UltraData | Resolved an issue in UltraData where accounts including a code of ‘Hsa’ and sub code of ‘HsaShare’ did not real time refresh. | ||
| 34009 | UltraData | Resolved an issue in UltraData where deposit accounts were not assigned the correct Account Type during the batch account import from the Core. | ||
| 33087 | XP2 | Resolved an issue with XP2 batch import where non-Deposit accounts were not being mapped to the Miscellaneous Account Type after the import. | ||
| 33885 | XP2 | Resolved an issue with the XP2 Account Import where the import failed when a carriage return was included at the end of the import file. | ||
| 34007 | XP2 | Corrected an issue in XP2 where deposit accounts were not assigned the correct Account Type during the batch account import from the Core. | ||
Maintenance Release Features
Enhanced in 15.01.32| Feature | Core | Description | |
| ActiveX Controls | |||
| 11855 - Installer to Deploy ActiveX Control | All | The Framework has been enhanced to include an automatic method of installing the Akcelerant Active X Browser Control. This control is required to use certain functionality such as that for Letter Generation and Batch Letter Printing. Prior to this enhancement, an institution's IT department had to individually install the Akcelerant Active X Browser Control for each user that did not have administrator rights to download the control within the Framework. Now, an installer is available for this control which provides an institution's IT department with the ability to run an EXE on the Framework web server to install the control for multiple users at once. For more information, please see the Help section of the Desktop and Ribbon Bar Overview topic in the Administrator guide. | |
| Feature | Core | Description | |
| Upgrade Readiness Report | |||
| 11688 - Readiness Report to evaluate number of custom fields | All | The Upgrade Readiness Report has been enhanced to include a new test that evaluates if an institution has created an excessive number of custom fields. Prior to this enhancement there was no validation performed to evaluate if too many custom fields were created. As a result, upgrades have failed due to an excessive number of custom fields. With the addition of the Number of Custom Fields test, the Upgrade Readiness Report now evaluates if the system has more than 550 custom fields. If more than 550 custom fields exist, institutions are warned that the upgrade may fail without a Customer Care Specialist performing a full evaluation. | |
There were no enhancements made for the Account Servicing solutions in the 15.01.35 release.
There were no enhancements made for the Account Servicing solutions in the 15.01.36 release.
| Feature | Core | Description | |
| Configuration Manager | |||
| 11970 - Add dashboards to Configuration Manager | All | The Configuration Manager functionality has been enhanced to fully support the export and import of Dashboard Data. Previously, Configuration Manager had provided options to export dashboard data in limited types of web parts requiring linkage to other types of data. Embedded data was stored within the WebPartParameter field as XML that had not been processed. Now, Configuration Manager has the XML-processing capabilities necessary to extract particular ID values from the WebPartParameter field in tblDashboardDetail records, as well as replace these values during import. | |
There were no enhancements made for the Account Servicing solutions in the 15.01.40 release.
There were no enhancements made for the Account Servicing solutions in the 15.01.41 release.
| Feature | Core | Description | |
| Core Specific | |||
| 12069 - Ability to Alter Data in the DNA Account Import File Prior to the Import | DNA |
The DNA Account Import has been enhanced to include a new stored procedure titled uspSolutionOSIImportAccountMassageCustom which provides institutions with the ability to update data in the import file before it is imported. This stored procedure is now the first procedure to be called after data is loaded from the import files into the database staging tables during the DNA Account Import. By default, the stored procedure is empty and no information is updated during the Account Import process. In order for data to be updated in the import file, institutions must have custom statements to modify the data added to the uspSolutionOSIImportAccountMassageCustom stored procedure by a Temenos Product Support Representative. After the DNA Account Import process completes, the modified data appears in the Lifecycle Management Suite. |
|
There were no enhancements made for the Account Servicing solutions in the 15.01.44 release.
| Feature | Core | Description | ||||||||||
| Source Identifiers | ||||||||||||
| 12278 - Populate Source Identifiers to match the core if blank in 10.31.xx | DataSafe, Symitar, |
The Collection module has been enhanced to support de-duplication of person records not imported from the Core by applying Source Identifiers based on the following three processes:
The Person Master Identifier, Person Source Identifier, and Source Identifier Description are used in the upgrade to the 15.01 release and provide significant improvement in upgrade stability. The cores and connectors that have been updated are as follows:
|
||||||||||
| Upgrade Readiness Report | ||||||||||||
| 12260 - Readiness Report to inform the need to upgrade to 10.31.21 (based on Cores) and run an import before they can upgrade to 15+ | Summit, Symitar, OSI, DataSafe, XP2, IBS, Profile Import, Coast Capital, Miser, Fiserv Advantage, Fiserv CBS, Fiserv CUBE, UltraData, OTS |
The Upgrade Readiness Report has been enhanced to include the new Current Version and Core Import Validation report, which assesses whether an upgrade to 10.31.15 or 10.31.21 is required before proceeding to version 15.01. Prior to this enhancement, upgrades from pre-version 10.31.15 to 15.01 would result in the creation of duplicate person records. Now, the addition of this report evaluates if the financial institution has upgraded to the appropriate release, depending on their core and connectors, to correctly set source identifiers prior to upgrading to 15.01. |
||||||||||
Maintenance Release Defects
| Defect | Core | Description | |
| Exports | |||
| 35249 | All | Fixed an issue in the Standard Dialer Export where an error caused the export to fail and no file was generated. | |
| 35250 | All | Fixed an issue in Exports where the Export process failed when the file was configured to have a Money, Date, Decimal, Integer, or Boolean field type as the last field in the file. | |
| Profile Import | |||
| 35224 | All | Resolved an issue where Person and Account information fields were not updated during an Update Profile Import. | |
| 35205 | All | Resolved an issue with Profile Import where fields set to a NULL value were not cleared during the Profile Import. | |
| Upgrade Specific | |||
| 35222 | All | Fixed an issue in the upgrade script that caused an upgrade from version 10.31.21 to version 15.01 to fail. | |
| Defect | Core | Description | |
| Connector Processes | |||
| 35353 | All/LexisNexis | Fixed an issue that occurred when trying to run the LexisNexis workflow step on an account that had a case attached where information was taken from the case rather than the account being worked during execution of the workflow step. | |
| Upgrade Specific | |||
| 35390 | All | Resolved an issue with the Upgrade process where custom fields used in Account Exports in version 10.xx were not migrated during the upgrade to version 14 or higher. | |
| Core Specific | |||
| 35353 | Symitar | Fixed an issue that occurred when trying to run the Symitar Run RepGen workflow step on an account that had a case attached where information was taken from the case rather than the account being worked during execution of the workflow step. | |
| Defect | Core | Description | |
| Connector Processes | |||
| 35289 | All/Grant & Weber | Fixed an issue with the Grant & Weber Client Export where ChargedOffDate was not exported for Grant & Weber files of version 3 through 5. | |
| Configuration Manager | |||
| 35397 | All | Resolved an issue with Configuration Manager where a Validation error was received when trying to import an Entity that was used in View criteria, deleted, then recreated with the same value imported into the target system. The Validation error occurred when both the Entity and the View were being imported into the target system. | |
| Server Manager | |||
| 35280 | All | Resolved an issue in Server Manager where changes made to Reporting Services parameters did not update in real time. Now, when values are modified in Reporting Services, the parameters update in real time and a message is received upon clicking Update to inform that Reporting Services have been updated. | |
| 35362 | All | Resolved an issue in Server Manager where an error was received when starting or stopping services for a Non-Akcelerant Scheduled task. | |
| Workflows | |||
| 35366 | All | Fixed an issue where an error was received when previewing an Automated workflow that included the "Is Monitored for Banko" field in its criteria. | |
| Workspace | |||
| 35337 | All | Resolved an issue where an error was received when trying to open the System Management menu in the Framework. | |
| Core Specific | |||
| 35414 | XP2 | Resolved an issue in XP2 where space characters appeared between the loan number value and the closing quote in the XP Import file. | |
| Defect | Core | Description | |
| Connector Processes | |||
| 35433 | All/SWBC AP Account Services | Resolved an issue where duplicate records were created in the database during the APACCOUNTSERVICES Comment Import Process which resulted in the same comment being displayed multiple times to a user. | |
| 35434 | All/SWBC AP Account Services | Resolved an issue with the APACCOUNTSERVICES Comment Import Process where old and/or duplicate comments were being imported. | |
| Configuration Manager | |||
| 35505 | All | Resolved an issue where reports including fields with special characters or numbers in the field display name could not be regenerated in Configuration Manager. | |
| 35508 | All | Resolved an issue in Configuration Manager where a validation error was received when trying to import Account Types that included the same AccountTypeCode but different AccountTypeBaseID. Now, validation for Account Types has been modified in Configuration Manager to allow Account Types with the same AccountTypeCode and different AccountTypeBaseID to be imported into the target system. When both AccountTypeCode and AccountTypeBaseID are the same, a validation error is received and import into the target system fails. | |
| Exports | |||
| 35472 | All | Resolved an issue with Dialer Profile Exports where the export failed when a CLIENTDATE field type, such as Next Contact Date, was included in the file. | |
| 35573 | All | Resolved an issue where Dialer Exports took an extended amount of time to run in System Management > Exports. | |
| 35574 | All | Resolved an issue that occurred when the last field assigned to an export record included a NULL value where the record including the field had a smaller length than the rest of the records in the generated file after the export was run. | |
| Workspace | |||
| 35318 | All | Resolved an issue where deadlock errors occurred in various areas of the Framework when a large number of users were working in the Framework. | |
| Core Specific | |||
| 35296 | IBS | Corrected an issue in IBS where the IBS Real Time Promise Check process failed when data returned from the core did not include a data type value accepted by the Framework. Now, all values for Deposit transaction history are converted to the correct data types that are returned from the service request. | |
| 35570 | Symitar | Fixed an issue in Symitar where the Symitar Account Import failed when importing the AKSW.SHARENAME file. | |
| 35396 | XP2 | Resolved an issue with APEX Realtime where person information was not updated correctly on a loan when an account holder had both personal and business accounts that used the same TIN. | |
| Defect | Core | Description | |
| Exports | |||
| 35612 | All | Resolved an issue with Dialer Exports where an error was received when trying to run an export that included fields with a NULL value in the export file. | |
| Upgrade Specific | |||
| 35314 | All | Resolved an issue where an upgrade from version 10.31.20 to version 15.01 failed during the 15.00.00 part of the Upgrade script when a database constraint included an incorrect name. | |
| 35835 | Resolved an issue that occurred during an upgrade to a version higher than 10.31.21 where Lookups 1-9 were not converted correctly which resulted in functionality such as workflows and screens that included the lookups to fail after the upgrade. | ||
| Core Specific | |||
| 35706 | DataSafe | Resolved an issue with the DataSafe Account import process where the temp files created in the following location were not removed during the import: C:\Users\[Username running the exe]\AppData\Local\Temp location on the Framework web/app server. | |
| 35671 | DataSafe | Resolved an issue in DataSafe where the bldMembers step failed during execution of the DataSafe account import process. | |
| 35708 | IBS | Fixed an issue in IBS where an error was received upon accessing a Person or Account from a Search or Queue when Real-Time Refresh was running. | |
| 35811 | IBS | Resolved an issue in IBS where an error was received during the METAVANTEREALTIMEPROMISECHECK process, which prevented the process from completing. | |
| 35812 | XP2 | Resolved an issue in XP2 where incorrect loan types were set during the XP2 Account Import. | |
| Defect | Core | Description | |
| Core Specific | |||
| 35805 | Symitar | Fixed an issue in Symitar with where the Approval Code field was not saved to the database and the Loan Officer field was cleared during the Symitar batch import. | |
| Defect | Core | Description | |
| Installshield | |||
| 35967 | All | Resolved an issue with InstallShield where an error was received during the Uninstall process that prevented the process from completing successfully. | |
| Core Specific | |||
| 35844 | DataSafe | Resolved an issue in DataSafe where information that was updated in the Framework was not written back to DataSafe after a real-time refresh was performed. | |
| 35809 | IBS | Resolved an issue in IBS where an error was received when trying to create an account in the Framework. | |
| 35771 | Symitar |
Resolved an issue in Symitar where the promise status was not adjusted when a payment was reversed. To correct this, modifications have been made to the AKSW.PAYMENT Power On to bring in the negative amount for a payment when it is reversed. Once the updated AKSW.PAYMENT Power On has been uploaded at an institution, the following occurs in the Framework:
|
|
| 36073 | Symitar | Corrected an issue in Symitar where account level joints did not populate on loans during the Symitar core batch import. | |
| 35925 | UltraData | Resolved an issue in Server Manager where a record for UltraData Collection did not appear in Application Services tab. | |
| Defect | Core | Description | |
| Profile Import | |||
| 36186 | All | Resolved an issue with Profile Import where new collaterals were incorrectly created each time the import process was run when the import file included blank values for Collateral fields. | |
| 36196 | All | Resolved an issue that occurred when a User Defined Flag field was only used in a profile import where the field was removed from the profile import layout during an upgrade. This issue occurred when the User Defined Flag field was only used in a profile import and did not appear in any screens, views, reports or queues. | |
| 36197 | All | Resolved an issue with Profile Import where an error was received when building a profile with the Customer Code In File Extension option set to true. | |
| 36210 | All | Resolved issues with the Profile Import Massage, Update and Create stored procedures that were preventing profiles from building successfully. | |
| Reports | |||
| 36226 | All | Resolved an issue with some Pre-defined reports where the names of inactive users wrongly appeared within the Last Modified By column in the report after an upgrade to 15.01. | |
| Core Specific | |||
| 36245 | IBS | Resolved an issue that occurred during the IBS Account Import where deposit accounts were created for both the Primary and Joint on an account, which resulted in duplicate accounts being imported from IBS. | |
| 36333 | IBS | Fixed an issue in IBS where loans were not imported during the Account Import process. | |
| 36143 | Symitar | Resolved an issue with Symitar real-time where accounts were marked as delinquent when the Due Date was set to the current date. | |
| Defect | Core | Description | |
| Exports | |||
| 36381 | All | Resolved an issue with Account Exports where the fields in Delimited Export files were not trimmed according to the length configured for the field in the Exports page in System Management. | |
| 36404 | All | Resolved an issue where no rows were returned in the export file generated for an Account Export when one or more fields in the export did not include a value. | |
| 36405 | All | Resolved an issue with the text that appears in the process log when the Profile Export EXE for Account Exports executes where the text was incorrectly displayed as " rows affected." This text has been updated to now display as " rows exported." | |
| Profile Import | |||
| 36344 | All | Resolved an issue with Profile Import where Collaterals were created with duplicate Source Identifiers during the import process. | |
| 36389 | All | Resolved an issue with Profile Import where the import process failed when the profile import included an UpdateCreate stored procedure. | |
| 36396 | All | Resolved an issue with Profile Import where files with extensions other than the one included in the import file were archived during the import process. | |
| 36523 | All | Resolved an issue with Profile Import where new addresses were imported incorrectly and not associated with the correct person during the import process. | |
| Reports | |||
| 36154 | All | Resolved an issue with Standard Reports where an error was received when trying to generate a report that included fields with multiple spaces and/or underscore characters in the Display Name. | |
| Upgrade Specific | |||
| 36332 | All | Resolved an issue that occurred during a database upgrade from version 10 to version 15.01 where an error was received due to a default schema not being identified for tblMetaDataInfoBackup. | |
| Core Specific | |||
| 3600 | DataSafe | Fixed an issue where DataSafe customers who upgraded to DataSafe Service Pack 2016.1.0 received a "specified cast is not valid" error when completing a real-time refresh of the workspace. | |
| Defect | Core | Description | |
| Exports | |||
| 36531 | All | Resolved an issue with Account Custom Exports where incorrect values for integer fields, such as Days to Close, appeared in the export file when the field included more characters than the field length. | |
|
36543 36584
|
All | Resolved an issue with Account Custom Exports where Date fields did not include the correct time-stamp and were not set to the correct format and length in the Export file. | |
| 36566 | All | Resolved an issue with Account Custom Exports where constant fields were not exported when they appeared in the last column of the export file. | |
| Profile Import | |||
| 36561 | All | Resolved an issue with Profile Import where the ModifiedByID column was updated to an incorrect UserId in the Core.Address,Core.Email and Collections.Collateral database tables when an update to an address or Email ID for a secondary person or an update to a Collateral was made. | |
| Readiness Report | |||
| 36482 | All | Resolved an issue with the Field Elimination Readiness Reports where the reports continued to show warnings for a field on a Queue, Report, Letter, Email or Automated Workflow after the item was deleted. | |
| Screens | |||
| 36581 | All | Fixed a performance issue that caused Account Servicing screens to take an extended amount of time to load in the person workspace. | |
| Upgrade Specific | |||
| 36557 | All | Fixed an upgrade issue where errors for “Akcelerant.Framework.Common.dll" were received during the install which prevented the install from completing successfully. | |
| 36623 | All | Resolved an issue with the Certegy connector where the value of the Include 5 Days Delinquent parameter was not maintained after an upgrade. | |
| Core Specific | |||
| 36578 | DNA | Resolved an issue with the DNA Account import where the import process failed when a "\" character existed in the Vehicle import file. | |
| 36580 | DNA | Resolved an issue in DNA where the AddresstypeID was not updated during the DNA Account import process. | |
| 36602 | IBS | Fixed an issue that occurred during the IBS Account Import where loan accounts were created for both the Primary and Joint on an account, which resulted in duplicate accounts being imported from IBS. | |
| Defect | Core | Description | |
| Cases | |||
| 36759 | All | Resolved an issue where the value of the Case Status and Case Stage fields were not updated in a Case screen after the values were modified by clicking the corresponding button in the screen. | |
| Event Processing | |||
| 36776 | All | Corrected an issue in Event Processing where the Field Changed Event did not fire when Account fields were updated. | |
| Exports | |||
| 36570 | All | Resolved an issue with Account Custom Exports where space characters did not appear for date fields in the export file. | |
| Workspace | |||
| 36636 | All | Fixed an issue where users could view restricted accounts when their user Restriction Code was blank/NULL. | |
| Core Specific | |||
| 36586 | Spectrum | Resolved an issue in Spectrum where the DQ flag was set incorrectly during the Spectrum Account Import and real-time refresh when the Due Date was set to today's date and current time. | |
| Defect | Core | Description | |
| Performance | |||
|
36667 36668
|
All |
Corrected the following issues that resulted in diminished system performance:
|
|
| Workflow Queues | |||
| 36621 | All | Fixed an issue where Workflow Queues that a user/security group did NOT have permissions to were displayed in Dashboards with the Workflow Queue Summary web part. | |
| Core Specific | |||
| 36744 | DataSafe | Fixed an issue in DataSafe where the Account Import failed when the FASBEffectiveInterestRate field contained a value larger than 99999.999. | |
| Defect | Core | Description | |
| Connector Processes | |||
| 36713 | All/SWBC AP Account Services | Resolved an issue with the SWBC AP Account Services (APAS) connector where the Open Promise flag did not update after the APAS Import process was complete. | |
| Configuration Manager | |||
| 36802 | All | Fixed an issue where Collections > Case Process entities were not available to add to an export package in Configuration Manager. | |
| 36890 | All | Resolved an issue in Configuration Manager where the import process failed when a Result Code was included in the package. | |
| Exports | |||
| 36807 | All | Resolved an issue with Exports where the timestamp for date fields was not included in the export file when the field was formatted as date and time. | |
| Performance | |||
| 36794 | All | Resolved a performance issue by adding indexes to several database tables in order to increase workspace load time performance. | |
| 36881 | All | Resolved a performance issue where the Workflow History panel took an extended amount of time to load in the workspace when there was a large amount of information in the workflow history. | |
| Screens/Panels | |||
| 37005 | All | Fixed an issue where an error was received when loading an Account and/or Case screen that was created in version 10. | |
| Core Specific | |||
| 36888 | DataSafe | Fixed an issue in DataSafe where Joint Owners were not related to non-deposit accounts during the import process. | |
| 36780 | Symitar | Fixed an issue where the Symitar Account Import failed due to the SymitarWarningCodeFlagId data type (Integer) not accepting a value bigger than 2^31 (2,147,483,648). | |
| 36849 | Symitar | Resolved an issue that occurred in Symitar when a workflow was run on an account with a NULL Loan number and an interface code of S or L where clicking Go to Next step in the Contact Method workflow step did not load the Symitar Transfer workflow step if that was the next step configured in the workflow. | |
| 36809 | UltraData | Fixed an issue in UltraData where accounts were not updated with Real Time Refresh. | |
| Defect | Core | Description | |
| Connector Processes | |||
| 37013 | All/Certegy, FICS, PSCU | Resolved an issue where imports for the Certegy, FICS and PSCU connectors took longer than an hour to run. | |
| Browser Controls | |||
| 37051 | All | Fixed an issue where Windows Update – KB3123 triggered an error when trying to install Akcelerant Browser Controls. | |
| Performance | |||
| 37090 | All | Corrected a performance issue for databases with large volumes of information where deadlock errors were received during real time refresh and workflow execution. | |
| Workflows | |||
| 36958 | All | Resolved an issue where the View Screen workflow step did not allow users to easily identify the screen assigned to each screen step. To correct this issue, an Active check box has been added to Screen tab of the View Screen workflow step to enable the ability to quickly identify the active screen in the workflow step. When the Active check box is selected, the screens are filtered and only the active screen is displayed within the Screen tab. | |
| Core Specific | |||
| 37032 | IBS | Fixed an issue with Real-time in IBS where an error was received when refreshing a Closed or Paid Off account. | |
| 37056 | UltraData | Fixed an issue where the Primary's Address and Phone numbers were not writing back to UltraData. | |
| 36866 | XP2 | Resolved an issue that occurred when a mobile phone number was added for an account holder in XP2 where duplicate home phone numbers were populated during the real time refresh rather than the mobile phone number. | |
| Defect | Core | Description | |
| Exports | |||
| 37091 | All | Fixed an issue where any related tables and/or stored procedures for Exports with a ProfileID of 30-39 were deleted when the Profile Export with ProfileID 3was executed. | |
| 37224 | All | Fixed an issue with Exports where quote marks (“) were appended to each row in the export file. To correct this issue, quote marks (“) are now included as text qualifiers around text fields in the export file. | |
| Letters/Emails | |||
| 37107 | All | Fixed an issue where duplicate letters were created when a letter was allowed to be imported with the same name as an existing letter in that environment. To correct this issue, an error is now displayed in the Configuration Manager Import process to stop the duplicate letter from importing. | |
| Performance | |||
| 37342 | All | Fixed an issue that occurred when saving data on non-system screens of any type, where the save appeared to hang due to background cleanup processes running and locking the tables during execution. | |
| Profile Import | |||
| 37228 | All | Fixed an issue where zeroes (0's) were populated in the Column Index for all fields when Profile Imports were created with Account/Person Mode set to "Update." | |
| Search | |||
| 37221 | All | Corrected an issue where no search results were returned when performing a credit card search, and where the 16-digit credit card number was not fully displayed on the Overview tab. | |
| Core Specific | |||
| 37141 | IBS | Fixed an issue with the IBS Real Time Refresh where related deposit accounts were updated with the Loan Account Account Identifier when real time refresh executed in the workspace. | |
| 36712 | UltraData | Fixed an issue where Real-time and Writeback functionality were not working in UltraData. | |
| Defect | Core | Description | |
| Connector Processes | |||
| 37471 | All/Certegy | Fixed an issue within Certegy where SourceId was being set to NULL in Collections.AccountRelationship after running third-party imports. | |
| 37489 | All/Certegy | Fixed an issue where an incorrect datatype for AccountTypeBaseCode was causing errors in the Certegy Account Import process. | |
| Cases | |||
| 37370 | All | Resolved an issue where cases were not appearing within Case views and reports after upgrading from 10.31 to 15.xx. | |
| Configuration Manager | |||
| 37271 | All | Fixed an issue where the incorrect Workflow models, Pricing models, Workspace Summaries, and Decision models were assigned to lending sub-products after import. | |
| Letters/Emails | |||
| 37275 | All | Fixed an issue where the Collection Summary screen was not displaying the correct number of Letters Sent, nor did the amount on the Collection Summary screen match the number of letters listed on the Letter History - Account Screen. | |
| Screens/Panels | |||
| 37409 | All | Corrected an issue where where the Workflow Name did not display on the Workflow History screen when the workflow was run against both an account and a case, and the Workflow History filter was set to Accounts-None/Cases-All. | |
| Transactions | |||
| 37486 | All | Fixed an issue where the IBS Transaction Codes page within System Management was not available even when the IBS/Metavante solution and connector were turned on. | |
| 37212 | All | Fixed an issue where Custom Indexes and Floats to Decimals tests failed with a syntax error when running the upgrade readiness report for customers using v. 10 in a SQL 2005 database. | |
| Workflows | |||
| 37384 | All | Fixed an issue where deadlocks were occurring due to the AccountServicing.uspSetLastContactDate stored procedure being called after the execution of every workflow step. Now, a call is made to another stored procedure, Collections.uspWorkflowContactAttemptsSave, and only when the Contact Method workflow step is completed using a valid contact. | |
| 37388 | All | Resolved an issue where sporadic performance issues, timeouts, errors, and deadlocks occurred when users were working with Workflow Queues. To correct this issue, NOLOCK was added to the stored procedure spWP_GetTaskQueueDetail to improve the performance of Workflow Queues grid. | |
| Core Specific | |||
| 37194 | DNA | Fixed an issue where an error was triggered when trying to complete the DNA Transfer Funds workflow step on a credit card account. | |
| 37522 | DNA | Fixed an issue where an error was returned when the DNA Transfer workflow step was loaded in the workspace. | |
| 37459 | UltraData | Fixed an issue in UltraData Refresh where the DQ Amount field was refreshed and set to zero rather than the current DQ Amount. | |
| Defect | Core | Description | |
| Connector Processes | |||
| 37147 | All/Banko | Resolved an issue with the testing of Imports and Exports by updating the SFTP site to use the batchtransfer.seisint.com URL for testing. | |
| 37389 | All/Banko | Fixed an issue where the Banko Import created and assigned cases incorrectly during import. | |
| 37461 | All/Banko | Fixed an issue where the Banko Import failed due to the excess amount of data in the import file. | |
| 37149 | All/CU Recovery | Fixed an issue where the CU Recovery Comment Import was not picking up and deleting the Comments file from the CU Recovery FTP site. | |
| 37114 | All/DNA | Fixed an issue where the Fiserv DNA (OSI) SAF Authentication logon screen did not exist, resulting in an error when the user would try to log into the Lifecycle Management Suite via SAF authentication. | |
| 37612 | All/FIS IBS | Fixed an issue on the FIS IBS connector page where the Read Flag, Write Flag, Write to Log File flag, Read from Log File flag, and Read Payments flags were not saved in the database when set on the connector page. | |
| 37543 | All/Grant and Weber | Fixed an issue where the Grant and Weber import process was failing and causing a truncation error due to a formatter issue within the Birth Date (datetime) field. | |
| 37286 | All/XDI | Fixed an issue where the External Letter Identifier (GUID) was not included on each record of the XDI letter export file. | |
| Batch Core Interface | |||
| 37796 | All | Resolved an issue where all persons in the ACKLJOIN file with a Social Security number of ' 0' (eight spaces and 0) were seeing all accounts in their workspaces imported for all coborrowers with that same SSN. | |
| 37849 | All |
Corrected a defect where Source Identifiers and Source Identifier descriptions were not calculated correctly for Symitar Collateral tracking records (both T Records and External Loan Records).
|
|
| Batch Transaction Import | |||
| 37795 | All | Fixed an issue where USERS/Datasafe Members and Loans account imports failed when both were executed at the same time. | |
| Exports | |||
| 37499 | All | Fixed an issue where the charge off date failed to export/import due to the format being set to datetime (mm/dd/yyyy hh:mm:ssss) rather than date (mm/dd/yyyy). | |
| Installshield | |||
| 36604 | All | Resolved an issue where PDFSplitMergeX.dll was not registered as part of the installation process when installing the Lifecycle Management Suite on a server. | |
| Profile Import/Other Batch Imports | |||
| 37366 | All | Fixed a defect where the NumMonthsPastDue field was not properly updated in the Certegy staging table after a Certegy Account Import. | |
| 37714 | All | Fixed an issue where the Loan Step (or process) which is part of the USERS/Datasafe Account Import was failing due to an exponentially formatted value populated in the "Interest Accrued to Date" field but the Account Import was falsely completing and not erroring out. | |
| Upgrade Specific | |||
| 37537 | All | Fixed an issue where server manager was causing service accounts to lock when processes were run manually using a logged in service account user ID with no password. | |
| Core Specific | |||
| 37634 | Symitar | Fixed an issue where a person was deleted if a user attempted to save a Mailing Only Name Record on the Symitar Name Records screen. | |
| 37839 | Symitar | Fixed an issue where Symitar tracking records were being assigned incorrectly formatted source identifiers after an upgrade from v10 to v15+. | |
| 37857 | Symitar | Fixed an issue where Symitar Account import tracking records had blank collaterals created for them after an upgrade to v15+. | |
| Defect | Core | Description | |
| Upgrade Specific | |||
| 38053 | All |
Corrected an issue where duplicates were being created post-import after the upgrade for customers using a core import and a third party (FICS/Certegy/PSCU/Profile). |
|