Causeview Release: Q2 2017

Salesforce Lightning Compatibility

Causeview pages have been converted to the new Salesforce Lightning experience, so that when Lightning is enabled for a user, it automatically displays the revised version of an existing page. Learn more about Salesforce Lightning here.

Notes: Lightning must be enabled in order for a user to be able to access the Lightning pages in Causeview. If a user is in Classic, Causeview will continue to display the Classic version of a page. The New Gift Interface and Enhanced Gift Batch Interface remain in Classic.

New Lightning Homepage

A new Lightning Homepage is now available, which gives users the ability to quickly access Causeview support pages, view relevant Causeview news and notices, and see their organization’s donation summary.

Notes: The Lightning Homepage is only visible to users where Lightning is enabled.

New Matching Gift Interface

The new Matching Gift interface gives users the ability to modify allocation information for the matching gift.

Notes: The new Matching Gift interface will be available to users who remain in Classic but the page will be styled in Lightning. To access the new Matching Gift interface, edit the page layout for Transaction, remove the “New Matching Gift” button and replace with “Match Gift” button.

New “Aggregate Donation” and “Sponsorship Donation” fields added to Payment Record for Gift Aid (UK Customers)

New fields called “Aggregate Donation” and “Sponsorship Donation” have been added to the Payment object. This will allow users to specify whether the payment is part of an aggregate or sponsorship gift.

Notes: To make these fields visible, edit the page layout for Payments and add the fields “Gift Aid Aggregate Donation” (causeview__Gift_Aid_Aggregate_Donation__c) and “Gift Aid Sponsorship Donation” (causeview__Gift_Aid_Sponsorship_Donation__c).

These fields have been added to the “Full Causeview UK User” Permission set. The user must be assigned this permission set to see all UK-specific features. In addition to these new fields, a new validation rule called “Aggregate or Sponsorship” has been added to the Payment Object which prevents users from selecting both at the same time.

New EziDebit Settlement Report (Australia customers)

A new Settlement report containing Ezidebit payments has been added.

New Job to detach payments where the payment type is no longer Gift Aid eligible  (UK Customers)

When you make changes to Gift-Aid eligible Payment Types, a job is now available on the "Gift Aid" tab in Causeview Settings to allow you to detach payments where the payment type is no longer considered Gift Aid eligible.

New field added called “Special Instructions” on Transaction Object (UK Customers)

A new field called “Special Instructions” has been added to the Transaction Object. The special instructions field on the Direct Debit form is mapped to this field.

Notes: To make this field visible on the page, edit the page layout for Transactions and add the “Special Instructions” field (causeview__Special_Instructions__c). This field has been added to the “Full Causeview UK User” Permission set. The user must be assigned this permission set to see all UK-specific features.

Ability to navigate to recurring gift not available when entering a recurring gift with a future start date

In the success page for the New Gift interface, when a new recurring gift is entered with a future start date, the button to navigate to the recurring gift record was previously missing, and is now available.

Receipt Status reverts to “To Be Issued” after saving the Batch

When gifts had been entered through Gift Batch with a receipt status of “Issued”, they would revert back to “To Be Issued” after the batch was saved. Batch now retains the correct status of “Issued” even after the batch is saved.

Allocations script applying incorrect amount when the recurring amount changes for future payments

When an allocation is missing, Causeview runs a script to write the missing allocation. However, if the recurring amount has changed, it had still been writing the allocation using the previous amount. This has now been resolved.

Default Fund specified for an Appeal failing to populate during Batch entry

When entering gifts in Gift Batch and an Appeal is selected during allocation, the default Fund for the appeal had not populated. This has been corrected.

Incorrect Schedule Day and Next Payment Date on recurring gifts

The Next Payment Date and Schedule Day was being populated incorrectly for months that have less than 30 or 31 days (i.e. when a recurring donation is entered and the first payment is processed on Jan 30th, the next Payment Date appears as Mar 2nd and the Schedule Day appears as “2” instead of taking the last day in February as the next payment date and setting the Schedule Day to “30”). This has been resolved.

Date of First Gift and Date of Last Gift not populating correctly

The Date of First Gift and Date of Last Gift were not populating correctly when the nightly contact rollup job was ran. This has now been resolved.

Next Payment Date populating incorrectly when the Recurring Frequency is changed

When updating the Frequency of a recurring gift after the first payment has been processed, Causeview was calculating the Next Payment Date from the Original Start date with the current Schedule Day, instead of the new Begin Date specified by the user. This has been corrected to populate accurately.

Organization Gifts failing to populate a contact on receipt record and send receipt by email

If a gift is created from an Organization, Causeview will now check to see if there is an organization email and will send the receipt to the organization email. If there is no email present, it will provide the user an error message.

Updated Rollup Field descriptions

Rollup Field Descriptions have been updated to provide users help text to better understand each rollup field