Release Date: April 15, 2018
Version #: 9.1804150008


New Features / Updates:
  • C&P Settings > Maintenance: A new feature has been added for processing Temporary Contacts automatically every 3 hours. The new process will resolve the Temporary Contact if the contact is found. A use case includes having a lot of contacts pending processing in the C&P Temporary Contact and manually adding the contacts without processing the Temps. Given the contact exists, the new process will identify the contact and will settle the contact without manual intervention. To enable go to: C&P Settings > Maintenance. The option is not available when the Contact Matching is set to "Fully Automatic" in the presence of NPSP and if the Matching is set to "Manual".
  • Various post-installation steps are now included in the C&P Settings > About C&P Apps. Checking for the new release will check the post-installation to ensure all settings, that can be checked, are correct. It is recommended for the synchronization to be verified after each upgrade.
Bug Fixes:
  • A correction update has been made to the <ChargeAmount> node in the C&P Data. The old node <ChargAmount> (missing e) will be deprecated in a future release.
  • Back dated transactions posted using custom payment type were being posted with conversion to the connected time zone. This had resulted in incorrect conversion. The issue was also present for pre-authorization transactions. These transactions post without any time and are posted as the DATE only. Converting from Eastern Time to other time zones that are behind ET resulted in posting of the transaction as the previous date.
  • Items with NO Salesforce Campaign assigned will NOT be assigned any campaign. In the previous releases the Transaction campaign was being assigned to the Item campaign resulting in inconsistencies.
  • Various UI enhancements & minor updates.
Behavior Change:
  • Items with NO Salesforce Campaign assigned will NOT be assigned any campaign. In the previous releases the Transaction campaign was being assigned to the Item campaign resulting in inconsistencies. This change may result in a behavior change from past releases if the transaction campaign was considered for item campaign.