Akcelerant Collections Guide
Known Issues

Known Issues Scheduled to be Fixed

The following table lists known issues that are scheduled to be fixed in the next update:

ID Core/Connector Description
15607 All A manual update of the Next Contact Date or Next Contact Time on a Detail screen requires the Save button be clicked twice in order for the change to take effect. To get the date/time to save correctly, change the value and click Save. Confirm that the screen was saved and click Save again before clicking the screen's refresh button.
22856 All/Connectors URLs, usernames and passwords for all third parties should be blank in the Framework by default.
23221 All When saving a letter template with a Letter Code greater than 20 characters, an error is received by the user rather than a validation message.
23257 All The Automated Workflow description located at the top of the Automated Workflow Grid List screen is in need of revision.
23269 All When a Workspace Comment is added to an account and a view is created to display all comments, the comment is visible in the view but a message stating "case cannot be found" returns when the account is selected from the newly created view.
23444 All Creating or modifying a Dialer Return Code in the Framework does not update the timestamp for Created or Modified By.
24781 All When running a report using the field Account > Specialty Processes > Charge Off > Transactions > Vendor, it shows the Vendor ID instead of the Vendor Name. There is no option in the Field List to display the Vendor Name.
25704 All/SWBC, Grant and Weber, PSCU Audit flags need to be enabled for SWBC, Grant and Weber and PSCU fields so they are available for the Third Party Field Audit screen.
25821 All The Create button on the View Screen workflow step uses a drop-down to list the screen types rather than using a pop-up.
28123 All When an on demand report is edited to run on a schedule, the ScheduleTypeID in tblReport does not change to "4." ScheduleTypeID does not change after initial report creation.
30081 All In Configuration Manager, the import into the target system cannot process a file that has a dot (.) in the file path location. If there is a dot in the file path (C:\Framework.Default, for example), an error is received stating a valid file cannot be found. As a workaround, prior to import, save the file in a location that does not have any dots in the file path.

Known Issues Not Scheduled to be Fixed

The following table lists known issues that are not scheduled to be fixed:

ID Core/Connector Description
25894 All When a read-only lookup field is configured to appear in a screen, the drop-down arrow for the field can be clicked and the options are briefly displayed before the list is collapsed.
26997 All When authoring a Business Rule in Rules Manager, Library Method and UDF Library Method items are visible within the Create Rule drop-down on the Definition tab in the Edit Rule window.
29877 All In order for Configuration Manager to work, collation must be the same in both the source and target environments' server and database. If collation is not the same, an error is received upon import of the package in the target environment, preventing the import from completing successfully.
30123 All In order to successfully upgrade from Framework version 10.31.20 to 14.02.00, an update record for version 10.31.15 needs to be added to tblUpdateHistory in the database. If a record for 10.31.15 does not exist, an error is received and the upgrade does not complete.
34614 All When the Edit Rule window is opened after saving and closing a new rule, values within the rule may appear red and are unable to be modified by clicking on the value. If this issue occurs, save the rule application and then close and reopen Rules Manager; the rule and its values should again be able to be modified.

Known Issues for Third Parties

The following table lists known issues for Third Party Connectors:

ID Third Party Connector Description
34188 Allied CPI With the Allied CPI connector, the Add/Remove Hold and Close Request buttons on the Allied Request Status screen should only be active when an institution is connected to PAR. However, due to a known issue at Allied, these buttons are also enabled when an institution is connected to ROA or Roquemore. Since the functionality is not available for institutions connected to ROA or Roquemore, clicking the Add/Remove Hold or Close Request button returns an error on the screen. For more information, please contact Allied Solutions.

 

 


©2017 Akcelerant Software LLC. All Rights Reserved.