You can download it here.
Release note:
Features:
- Added support for ODBC data sources to the Import Definitions.
Improvements:
- CATS SSVS plugin improvements to cater for
- Altering the file date
- Setting either the Account Details or "Creditor or Debtor Code" not both at the same time.
Bug Fixes:
- When importing transactions with 4 decimal places hashes were failing, since CP uses 2 decimal places. (This will only occur if your import definition query returns amounts to more than 2 decimal places.)
NOTES:
- When using the ODBC data sources one should choose the option in the "Query Type" field. The query that one generates will need to specify the key field parameter as a '?' as shown in the sample screenshot below.
You can download it here.
Release note:
Improvements:
- Added an extra config to map Creditor or Debtor code in CATS SSVS
- Downgrade .Net Framework to 4.0 so that CP will work on Windows Server 2003
- Updated WebHelp link.
-
Update to the OMNI Payments plugin to not drop off leading 0's on BeneficiaryAccountNumber and Debit Account.
Bug Fixes:
- Critical bug fix dealing with Consolidated Instruction hashes. When consolidated instructions exceeded the Transaction Payments Limit or Transactions Collection Limit on a bank account the split instructions did not have correct hashes.
- Fixed bug on Run Process screen when filters were applied to Doc Gen Process Definitions.
- Fixed icon on Run Process screen that was showing "disabled" when the checkboxes were actually enabled.
NOTES:
With this build we have fixed a critical bug with the hashing during consolidation.
We have also had to downgrade to .Net Framework 4.0. This was due to the fact that .Net Framework 4.5 is not supported on Windows server 2003. In case there are any issues when upgrading here are samples of the web config and service config. Values for <SERVER>, <DATABASE>, <USERNAME> and <PASSWORD> must be set.
You can download it here.
Release note:
Improvements:
- Update to the OMNI Payments plugin to not drop off leading 0's on
Bug Fixes:
- Fixed bug on Run Process screen when filters were applied to Doc Gen Process Definitions.
- Fixed icon on Run Process screen that was showing "disabled" when the checkboxes were actually enabled.
You can download it here.
Release note:
Improvements:
- Updates / additional config to the StandardBankCATSSSVS plugin.
Bug Fixes:
- Critical bug fix on the Run Process screen when loading Document Generation process definitions. The filter conditions were interfering with other features.
You can download it here.
Release Note:
- Added a new plugin called StandardBankCATSSSVS. This plugin is different to the the existing StandardBankCATS format as it is not a Host-to-Host format.
This build replaces version 1.8.2620 as there were some problems with clean installs in that version.
You can download it here.
A feature that will allow clients to have some control over user access to CentralPark from Active Directory has been added.
The concept is that domain administrators can create a group in Active Directory and set domain users as members of this group. When using CentralPark, with Windows Authentication, users can additionally be validated against this group. If the user exists in CentralPark but does not exist in the Active Directory group they will not be allowed access to the application. This assists domain administrators in controlling users access to CentralPark without having to access CentralPark.
To use the feature the administrator should:
- Create a group in Active Directory
- Add the required users as members of the group
- Confirm that CentralPark is using Windows Authentication
- Access CentralPark and navigate to Setup -> Options
- At the bottom of the page is an Active Directory Settings section (Shown below)
- Set the value for the LDAP server and Allowed User Groups.
- Only 1 server name can be specified
- Multiple user groups can be specified and must be separated by a ;
- Test the settings and confirm that a success message is received.
- If there is a failure message the values will not be allowed to be saved since that could prevent ALL users from accessing the system, including admins.
- Save the settings.
Now, when users access CentralPark they will first be validated in CentralPark. If they exist in CentralPark they will be validated against the list of groups in the Allowed User Groups field and if they exist in one of those groups they will be allowed access to CentralPark.
