sf-update-icon

Classy for Salesforce Release Notes

In case you missed out, check out the latest features of each Salesforce release. Feel free to reach out with any questions, here.

 

Looking for more information about our Salesforce integration?  
View our technical documentation

Features Under Review:

  • New Registration with Fundraising: Support for offline registrations
  • New Registration with Fundraising: Support for Crediting Registrations to Fundraisers or Teams
  • New Registration with Fundraising: Support for Crediting Additional Donations to Fundraisers or Teams
  • New Registration with Fundraising & Events: Support for changes made on the Overview tab
  • New Classy Manager: Support for updates to Supporters
  • Fundraiser selected Designations
  • Campaign Duplication
  • Offline Dedications

Known Common Issues:

  • With the new Winter 20' release, your API Keys and Metrics tab may not display its intended data properly. This is currently an issue that is on the surface-level and is being investigated. As long as your Classy Manager displays the Salesforce extension as "Enabled", data will continue to sync without any issues!

Last Updated: June 26, 2019

C4NPSP 1.33: Brosiah

Released May 29, 2019

 

Summary

Classy for NPSP version 1.33 includes a fix for NPSP GAU Allocations.

 

Squashed Bugs

  • Fixed an issue causing extremely slow transaction processing time on rare occasions when a large number of GAU Allocations exist.

Q3 2019

6.5300

Released October 09, 2019

 

Summary

Classy for Salesforce version 6.5300 includes fixes for issues related to the Classy Control Panel, Contact address fields being overwritten, Campaign Member/Contact creation and inconsistent format for Campaign Types. We’ve also included a minor improvement to the way new API Requests are handled.

 

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

  • API Requests for Transactions will now be prioritized based on the event type. Transaction completed API Requests will take priority over transaction updated messages, and transaction updated API Requests will take priority over transaction created API Requests.

Squashed Bugs

  • Fixed an issue with the Classy Control Panel being unable to schedule new Apex jobs in the “Tools” section.
  • Fixed an issue with the integration overwriting addresses in certain situations even though the “Update Existing Contact Address” Setting is turned off.
  • Fixed some inconsistency with the “Type” field on Classy Campaigns where they would come in uncapitalized for Donation and Peer-to-Peer Campaigns.
  • Fixed an issue in which an incorrect State and/or Country value on the supporter would cause failure on Contact creation.

Q2 2019

6.522

Released June 26, 2019

 

Summary

Classy for Salesforce version 6.522 contains a fix to an issue where a Scheduled job could not be scheduled in the Developer Console.

 

Squashed Bugs

  • Fixed an issue where the Data Sync Scheduled Job could not be scheduled in the Developer Console

6.52

Released June 14, 2019

 

Summary

Classy for Salesforce version 6.52 includes a number of under the hood enhancements that make way for some future Classy functionality like internal Campaign names. We’ve also included a bug fix for the Processor ID field not filling in on recurring Opportunities that some Authorize.net clients were experiencing.

 

What’s New

  • Internal Campaign Name Setting [future functionality] will allow organizations to choose whether or not the Classy Internal Campaign Name or Classy External Campaign Name is used in the standard “Name” field on Campaigns

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

  • New field on Campaign object with API Name “stayclassy__Classy_Campaign_External_Name__c” and label “Classy Campaign External Name” which always populates with the public Campaign name [future functionality]
  • New field on Campaign object with API Name “stayclassy__Classy_Campaign_Internal_Name__c” and label “Classy Campaign Internal Name” which always populates with the internal Campaign name [future functionality]

Squashed Bugs

  • Fixed an issue where Processor ID field was not populating on Opportunities for some Authorize.net recurring transactions

6.51

Released May 29, 2019

 

Summary

Classy for Salesforce version 6.51 includes a number of fixes for issues with Event Contact Creation, Offline Donation Creation, and Source Codes.

 

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

  • New field on Classy Recurring History object with API Name “stayclassy__Classy_Transaction_ID__c” and label “Classy Transaction ID” which allows for Transaction ID associated with a Recurring History record to be captured if applicable
  • New field on Classy Source Code object with API Name "stayclassy__Referrer_long__c” and label “Referrer” which allows for full-length referrer text to be captured
  • Renamed the label on the field with API Name “stayclassy__Referrer__c” to “Referrer Short” in order to distinguish it from the full-length referrer text field

Squashed Bugs

  • Fixed an issue where Event data was not created in some situations when Salesforce State/Country Picklists feature is enabled. Now, Event data will be created as expected.
  • Fixed an issue blocking the creation of Opportunities for Offline Donations when no email address was provided. Now, Offline Donations without email addresses are created and related to a “Classy Bucket” Account without a Contact in order to prevent unreliable matching/duplicates.
  • Fixed an issue where Source Codes were not created if the Referrer was too long.

Q1 2019

6.501

Released January 31, 2019

 

Summary

Classy for Salesforce version 6.501 includes a revamped version of the Data Sync Tool with more flexibility in finding and creating data. From support for timezones to filtering results and searching by ID, give your organization the ability to identify which missing records you'd like to sync before you create standard and custom objects. As always, we've included bug fixes and other improvements.

 

What’s New

  • Data Sync Tool v2
    • The Classy Data Sync tool has been redesigned from the ground up to give you more control over missing Classy data. With this facelift, we thought it deserved its own section in the Control Panel sidebar named “Data Sync”.
    • Find by Type and Date Range
      • Now you can choose what kind of data you want to find. Look for just transaction data, campaign data, or both over a given date range. Created date for campaigns and purchased date for transactions are used to identify records within the given date range.
    • Timezone Aware
      • In order to be more precise, your Salesforce organization timezone is now displayed and used when looking for missing data.
      • Note: Classy timezone is viewable on reports and may differ.
    • View Results
      • The new “Results” section allows you to see missing data before it is created. View data by its type and unique Classy ID. For power users, you can even click on records to view their raw data.
    • Filter and Search by ID
      • The results view has several filtering options including filtering by type or Classy ID. This helps in identifying the correct records you’d like to create.
    • Create All or Individual Data
      • Select individual records that you’d like to create or click “Select All” which selects all records on all pages.
    • Nightly Data Correction
      • Improvements to the tool mean our nightly data sync job gets this same great functionality. It is now even more precise when finding missing records and automatically syncing them.
    • Email Results
      • We’ve improved the completion by adding a summary of results. Summary totals include a count of records found and a count of records missing.
    • New Logs
      • For those who like to debug on their own, we’ve added additional logs which display sync results. This is especially helpful if you’d like to see what the nightly data sync job attempted to sync the previous day.

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

  • New object named “Classy Temporary Data” which contains Data Sync Tool results
  • Removed “ClassyHealthCheck” scheduled job since results are now viewable in Classy Logs
  • Simplified configuration section of Control Panel by removing deprecated settings
  • Standardized naming convention for API Requests created by the Data Sync Tool
  • Various changes to keep in line with Salesforce security best practices

Squashed Bugs

  • Fixed an issue where the Data Sync Tool was syncing transactions with status “Canceled”
  • Fixed an issue where the Data Sync Tool could be manually started multiple times before completion which produced inaccurate results
  • Fixed an issue where “Donor Selected Classy Mode” field on Opportunities was intermittently incorrect for recurring donations
  • Fixed an issue where Data Sync Tool completion email was sent even if an API credential was inactive
  • Fixed an issue where transaction data was not syncing for Honoree name fields that exceeded max length
  • Fixed a typo on the Enhanced Contact Matching setting help text

Q4 2018

6.47

Released November 16, 2018

 

Summary

Classy for Salesforce version 6.47 contains a number of minor bug fixes for transaction and recurring profile linking as well as other improvements.

 

What’s New

  • Changed the "Campaign" field label on Opportunity to "Classy Campaign" to help distinguish it from other Campaign lookup fields
  • Created a "Classy Member Name" field on Opportunity which contains the full name captured by the "Your Information" fields on donation pages

What’s Fixed

  • Fixed an issue where some registration data failed to sync if similar names were used for Ticketed Event registrations
  • Fixed a rare issue where Classy Recurring Donors were not related to Opportunities during times of high transaction volume
  • Fixed a rare issue where Opportunities would associate with the wrong Classy Recurring Donor record if a "0" was stored for its Classy Recurring ID
  • Fixed an issue where transaction Classy API Requests with recurring donors contained an "Invalid decimal" error (NGO Connect organizations only)

6.461

Released November 5, 2018

 

What’s Fixed

  • Fixed an issue where data related to Opportunities for ticketed events was not created

Q3 2018

6.46

Released August 10, 2018

 

Summary

Classy for Salesforce version 6.46 contains a number of minor bug fixes and improvements. "Attendee" Opportunity Contact Roles will now be created for all attendees besides the donor which still receive a "Donor" Opportunity Contact Role. Additionally, in order to improve support for NPSP rollup fields based on Opportunity Contact Roles, we've added logic to ensure a "Donor" Opportunity Contact Role is created even if a donor donates to their own Fundraising Page and/or Team Page.

 

What’s New

  • Added an "Attendee" Opportunity Contact Role to ticket purchase transaction
  • "Donor" Opportunity Contact Role will now always populate for the donor if they donate to a Team they are captain of or Fundraising page they are the fundraiser for
  • Improved Classy Recurring Donor rollup to accommodate for Opportunities with a null "Amount" field
  • Removed requirement for "Recurring ID" field on Classy Recurring Donor records

What’s Fixed

  • Fixed an issue where "Host Total" field was not filling in on Opportunity records
  • Fixed an Issue where "Default Opportunity Contact Role" setting was also on Account & Contact section of Classy Control Panel
  • Removed deprecated "TEST Email" field from Contact

6.45

Released July 27, 2018

 

Summary

Classy for Salesforce version 6.45 contains support for the Opt-In checkbox on Classy transactions. This selection will be captured and stored in the field "Classy Opt-In" on Contacts and will update for any Contacts with Classy Member IDs that share the same email address. Additionally, this update includes several bug fixes for the Classy Recurring Donor object.

 

What’s New

  • Added support for the "Classy Opt-In" checkbox on Classy transactions
  • "Classy Opt-In" field will be updated whenever a new transaction is created
  • "Classy Opt-In" field will be updated whenever a Supporter is updated in Classy

What’s Fixed

  • Fixed an issue where Classy Recurring Donors that were missing a Contact were not updated if a new successful transactions was created
  • Fixed an issue where Classy Recurring Donor records with no successful transactions were being created
  • Fixed an issue where updates to non-ID and non-lookup fields could not be made to Classy Recurring Donor records
  • Fixed the spelling of "Event Type" field label from "Entity Type" on Classy Source Codes

6.44

Released July 11, 2018

 

Summary

Classy for Salesforce version 6.44 contains several bug fixes and the groundwork for Source Codes. Expect to see more details on this new functionality in future releases of Classy for Salesforce and the Classy Fundraising Suite.

 

What’s New

  • Added an object called “Classy Source Codes” in order to support future functionality
  • Prevented an email about Classy Recurring Donor rollups when run by scheduled job

What’s Fixed

  • Fixed an issue where the State field on Contacts is sometimes not filling in when State/Country picklists are enabled
  • Fixed an issue where the NPSP Extension menu was showing even if the NPSP Extension is not installed

Q2 2018

6.431

Released June 21, 2018

 

What’s Fixed

  • Fixed an issue where "Attendee" Campaign Member setting was not enabled by default

6.43

Released June 13, 2018

 

Summary

Classy for Salesforce version 6.43 provides a number of bug fixes related to registrations as well as a new nightly job to recalculate Classy Recurring Donor rollups. Additionally, we’ve added a Campaign Member status called “Attendee” so that it’s easier to determine who’s attending an event in Salesforce.

 

What’s New

  • Added fields on Campaign, Opportunity, and Classy Recurring Donor to support New Classy Mode
  • Added “Attendee” Campaign Member status on Campaign object
  • Added a nightly rollup job to improve reliability of rollups on Classy Recurring Donor object
  • Added a button in Classy Control Panel tools section to refresh Classy Recurring Donor rollups

What’s Fixed

  • Fixed an issue where the “Contact” and “Classy Registration” fields on Classy Custom Answer records were not always filled in
  • Fixed an issue where some registration data was not created for Campaigns with a custom Campaign Member status
  • Fixed an issue where the Data Sync tool would fail on a newly refreshed Sandbox

6.421

Released May 1, 2018

 

What’s Fixed

  • Fixed an issue where the Parent Campaign field was overwritten on Campaigns

6.42

Released April 9, 2018

 

Summary

Classy for Salesforce version 6.42 provides a number of bug fixes related to Registration with Fundraising, Events, and the Data Sync tool.

 

What’s Fixed

  • Fixed an issue where the Data Sync tool would stall if a recurring profile had text in its name
  • Fixed an issue where Campaign Members were not created and the Contact field was not filled on fundraising page and team Campaign records for Registration with Fundraising campaigns
  • Fixed an issue where Campaign Members were not created for a Registration with Fundraising campaign when same registrant info is used for multiple attendees
  • Fixed an issues where Contact Address fields would overwrite after registering for an event
  • Reduced the number of duplicate Contacts when registering as a Team Captain
  • Added logs to provide more registration details

Q1 2018

6.41

Released March 8, 2018

 

Summary

Classy for Salesforce version 6.41 provides a number of bug fixes related to Registration with Fundraising campaign types as well as improvements to the Data Sync tool.

 

What’s Fixed

  • Fixed an issue where the Data Sync tool was not including the full “Days to compare” of the Data Health tool
  • Fixed an issue where offline donations were syncing even if “Salesforce Sync” option was disabled
  • Fixed an issue where Campaign Members were not created for fundraising page contacts coming from a Registration with Fundraising campaign
  • Fixed an issue where the “Transaction Type” field on Opportunity filled in with “Donation” instead of “Registration” intermittently
  • Fixed an issue where the “Classy Opt-in” field on Contacts was being cleared on update

6.4

Released February 19, 2018

 

Summary

Classy for Salesforce 6.4 is a deeper integration than ever before, with a number of significant improvements based on providing valuable insight into how the integration is performing, tools to reconcile data, and a brand new interface for managing integration settings and configuration. This new version also fully supports the upcoming revamp of Classy Events. In addition, substantial improvements have been made to our data processing in order to drastically reduce the amount of duplicate contacts.

 

What’s New

  • Classy Control Panel
    • The Classy Control Panel is an entirely new aspect of our integration. Our intention is to make the Control Panel your home page for everything about the Classy for Salesforce integration. We’ll be making a lot of updates to the Control Panel going forward, so stay tuned! For this initial launch, we’ve added some links to useful articles about the integration. In the future, look forward to release notes, known issues updates, and more!
    • Data Reconciliation Tool
      • This was first released generally in August, but we’ve updated to a brand new UI to make this tool easier to use than ever!
    • Health Metrics
      • Looking for insight into the health of your integration? This is the place for you! Find details on how successfully your donations are syncing to Salesforce as well as additional information on other areas of the integration, including:
        • The status of the last five sync events
        • Scheduled jobs status, with a simple button to schedule any non-running jobs
        • Classy API credentials
        • Type of contact matching used by the integration
        • And more!
    • Custom Settings & Configuration UI
      • Previously settings were managed partly in Classy and partly through custom settings in Salesforce, which are buried in menus and have a difficult UI as well. We’ve built an entirely new UI to help you navigate and manage your settings from a single place within your integration.
  • Support for New Classy Events
    • Get ready for the new Classy Events suite, coming soon! This release of Classy for Salesforce fully supports Classy Events, so update now to ensure you’ll have full support for Events once it’s released. With this update, all event data, including transactions, tickets, and attendees will sync in real-time to Salesforce, just like our other new event types.
    • Additionally, the integration now supports creating Contacts for event attendees, a long time feature request! (Please note attendees must fill in first/last name & email in order for a Contact to be created).

What’s Fixed

  • Reduced the number of duplicates created for new donors
  • Reduced the number of duplicates created during registration & ticketed events
  • Resolved an issue where recurring plans with a status of “Failing” weren’t updating correctly in Salesforce
  • Designations created or updated through the API are now processing correctly in Salesforce
  • For NPSP users, event & registration attendees that are new Contacts are now correctly associated to a Household Account
  • Corrected an issue where the Designation lookup field was overwritten and set as blank for Campaigns when a Recurring Donor was updated

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

 

  • New tab for “Classy Control Panel” to let you experience the new suite of tools around data validation, reconciliation, health metrics, and configuration.

Q4 2017

6.33

Released December 13, 2017

 

Summary

Classy for Salesforce version 6.33 contains a number of improvements, but the key update involves some new functionality around matched donations and company offline donations. It’s been a highly requested feature to prevent matched donations from syncing to Salesforce, so our team has added a new custom setting to stop matched donations from creating Opportunities. However, if you still want to see those matched donations in Salesforce, we’ve updated our integration to add Account fields for both matched donations and offline donations made to companies. To ensure we don’t create duplicate Accounts, we recommend that the organizations you specify in Classy already have Accounts we can match to in Salesforce. See below for more details on these and more exciting features!

 

What’s New

  • Improvements to matched gifts and company offline donations
    • A new custom setting called “Prevent creation of matched gifts”. While disabled by default, when this setting is enabled matched gifts will NOT be created as Opportunities.
    • When Opportunities are created from either matched gifts or company offline donations, the integration will attempt to exactly match to an existing Account. The integration will not create Accounts, and will only look for exact matches, so we recommend ensuring that Accounts exist in Salesforce prior to applying those organizations to company offline donations matched donations.
  • In conjunction with the release of Classy Passport, added new currency specific fields on the Classy Recurring Donor object:
    • Raw Donation Amount: The amount selected by the donor on the donation form
    • Raw Currency Code: The currency selected by the donor on the donation form
    • Charged Currency Code: The type of currency sent by Classy to the payment processor
    • Charged Donation Amount: The amount of the donation sent by Classy to the payment processor
  • Added new fields to separate first/last names for dedications, including the dedication contact and honoree. This should make email template creation utilizing separate names substantially easier.
    • Dedication First Name: The value of Recipient’s First Name on the dedication form in Classy
    • Dedication Last Name: The value of Recipient’s Last Name on the dedication form in Classy
    • Honoree First Name: The value of Honoree’s First Name on the dedication form in Classy
    • Honoree Last Name: The value of Honoree’s First Name on the dedication form in Classy
  • Added a new field called “Campaign Path” on Campaign. This field is used to populate the Campaign URL field with the updated URL structure used by Classy’s new fundraising suite.

What’s Fixed

  • Fixed several inconsistent fields affecting offline donations to new campaigns. This includes ensuring that the “Offline Donation” field is checked, the “Payment Gateway” field is set to “Offline”, and the “Payment Method” is set correctly based on the value selected when creating the offline donation.
  • Resolved an issue where Custom Field Mapping was not working properly when mapping between fields on the same object (for instance, from one Opportunity field to another). NOTE: this bug did not affect mapping from a Custom Answer to a different object, such as a Contact.
  • Corrected an issue where the “Campaign URL” field for donation page campaigns pointed to the campaign landing page, which doesn’t exist for donation page-only campaigns.

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

 

  • The “Campaign URL” field now has a new URL structure for new fundraising page campaigns, including the parent campaign, fundraising pages, and fundraising teams. Previously this field always used the legacy URL structure for all campaigns; for new campaigns, legacy URLs would automatically redirect to new URLs.

Q3 2017

6.32

Released November 1, 2017

 

Summary

Classy for Salesforce version 6.32 focuses on improved capabilities for organizations with multiple Classy accounts connected to a single Salesforce instance and adding detailed history for recurring donation plans.

 

What’s New

  • Improved the system for automatically fetching missing data for organizations that have multiple Classy accounts connected to a single Salesforce instance.
  • Added a new field to indicate if a donor marked their donation as Gift Aid Eligible on the Classy donation form (see Important Changes below for additional details).
  • Recurring Donation History object is now populating for all recurring donations created in new fundraising suite campaigns and for all recurring donations processed by Classy Pay.

What’s Fixed

  • Fixed an issue affecting clients using NPSP where an update to a Classy transaction would overwrite the NPSP formatted Opportunity name with the default Classy formatted Opportunity name. All Opportunities for NPSP users should always adhere to NPSP Opportunity naming conventions. Requires NPSP Extension package.
  • Resolved an issue where registrations purchases with Classy mode/fee on top selected by the donor were not including the additional fee in the Amount field on Opportunities.
  • Corrected an issue in the Data Sync tool which was not resetting the retrieval dates for the nightly job properly. Now if the Data Sync tool is manually set to verify data for an arbitrary date in the past, when the daily reconciliation job runs it will ensure that the data is being retrieved for the previous day.

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

 

  • New custom field Is Gift Aid Eligible on Opportunity. This checkbox field will be set to true if a donor indicated that their donation is eligible for Gift Aid in the United Kingdom. NOTE: This features requires an organization to enable the Gift Aid setting in their Classy account.

6.31

Released October 4, 2017

 

Summary

Classy for Salesforce version 6.31 introduces a couple of new features as well as a number of critical bug fixes intended to keep your integration operating smooth as silk.

 

What’s New

  • Added a new custom field named Donor Selected Classy Mode on Opportunity to indicate if “Classy Mode” (the option on a donation form where the user elects to cover Classy's fees) was selected when donating.
  • New "Classy Passport Transactions" report listing all international donations as part of Classy Passport. This is located in the Classy Reports folder in the Reports tab.

What’s Fixed

  • Fixed an issue where updating attendee information via Classy Reports did not update the attendee in Salesforce.
  • Resolved an issue with the data reconciliation tool where campaign names using special characters could cause an error during processing which prevented the record from being created.
  • Corrected an issue where multiple attendees on a single registration have an incorrect Amount attributed to the purchase
  • Fixed an issue with invalid state names preventing Contact records from being created in organizations with the state/country picklist feature enabled.

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

 

  • New custom field Donor Selected Classy Mode on Opportunity

6.3

Released August 31, 2017

 

Summary

Classy for Salesforce version 6.3 introduces a highly requested feature, a tool that compares and resyncs missing records. This tool can support data verification for different object types, and is configured to run nightly to try and reprocess any missing data.

This release also supports data related to promo codes for new Classy Events (including Registration with Fundraising).

 

What’s New

  • New custom UI to manage the data reconciliation tool
  • Set start and end dates to import data for specific time periods
  • The tool is configured to run nightly after upgrading to 6.3. After installation the tool will verify and attempt to reprocess any missing data each night.
  • By default the tool will sync data related to the following resources/objects:
    • Transactions (non-offline)
    • Campaigns
    • Custom Questions
    • Fundraising Pages
    • Fundraising Teams
    • Custom Answers
    • Recurring Donations
    • Tickets/Registrations
    • Contacts (Supporters)
  • Supports the new promo code system for Classy Events, including Registration with Fundraising
    • Populates the promo code used and the adjustment amount representing the discount applied via the promo code on Opportunities
  • New SDK method to allow updating recurring donation attributes such as amount, the day of the month the charge occurs, and setting an end date. Note that this does not allow updating credit card or billing information.

What’s Fixed

  • Resolved an issue for orgs using NPSP where the Account on an Opportunity would not be populated
  • Fixed an issue where the following fields were not being populated on recurring donations: Contact, Designation, Installment Period, Billing Address Line 2, Payment Gateway Name, and Gateway Subscription ID
  • Fixed an issue where the "Payment Gateway Transaction ID" was not populated on Opportunities (this field has been re-labeled as "Processor ID"; see Important Changes below for more details).
  • Fixed an issue where the Account Name field was not always populated for classic Classy campaigns for organizations using NPSP
  • Fixed an issue where the billing address 2 field was not getting added to the address data for Contacts
  • Resolved an issue where custom questions did not sync when a Campaign was duplicated in Classy
  • Fixed an issue where the honoree and recipient fields were switched for dedications made through new fundraising suite campaigns
  • Fixed an issue where Team Captains were not being created as Campaign Members on the parent Campaign
  • Fixed an issue where field mapping was not always correctly applied for donation custom answers for recurring donations made to legacy campaigns

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

 

  • The "Payment Gateway Transaction ID" custom field on Opportunity has been re-labeled as "Processor ID" to reflect the name of this field in Classy Reporting.
  • On Opportunities, the “Discount Code” and “Discount Total” have been renamed as “Promo Code” and “Adjustment Amount”, respectively, in order to match the field names in Classy reporting. This will not impact existing or new data.

Q2 2017

6.23

Released July 12, 2017

 

Summary

This release had a heavy focus on resolving some lingering issues, in particular populating dedication fields for new campaign types and respecting certain custom settings, such as object Record Type defaults.

 

What’s New

  • New fields on Opportunity to support future payment options
    • Payment Account Type
    • Payment Account Number
    • Payment Institution

What’s Fixed

  • Dedication fields now populating on Opportunities.
  • Fixed an issue with custom field mapping settings not working properly for new campaign type data, including transactions.
  • Fixed an issue where default Record Type settings for Contact, Campaigns, and Opportunities were not being respected for transactions through new campaign types.
  • Billing Address 2 field now populating on Opportunities.
  • Payment Gateway Name now populating on Opportunities.
  • Fixed an issue where the "Always use Classy parent Campaign as the Primary Campaign on an Opportunity" custom setting was not being respected.

Important Changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

 

  • Field Name: Opportunity > Payment Gateway Name
    • Old Value: “Classy Pay”
    • New Value: Actual payment processor used (e.g., “Braintree”, “WePay”, “Authorize.net”)

6.204

Released May 17, 2017

 

Summary

Version 6.2 includes support for the new Registration with Fundraising campaign type. All data related to a registration will be sent to Salesforce in real time, including all registrations, donations made along with the registration purchase, contacts, fundraising pages, fundraising teams, and custom answers. In addition, this version supports multi-currency Salesforce orgs.

 

What’s New

  • Support for FRS Registration with Fundraising campaign data, including transactions, registrations, and custom questions
  • Support for multi-currency Salesforce orgs
  • Matching Sponsor gifts for FRS Campaigns now sync without creating or matching to a Contact or Account
  • New object:
    • Related Entity, to allow for easy reporting on attendees
  • New fields on Opportunity:
    • Opportunity: Classy Business ID
    • Opportunity: Parent Transaction ID
    • Opportunity: Is a Matched Gift?

What’s Fixed

  • Custom Answers for Classy Pay transactions will now sync
  • Transaction Type field on Transactions is now populated properly
  • Custom answers will now populate for transactions & fundraising pages
  • Deleted campaigns, fundraising pages, and teams will now properly update the Campaign Status & Active fields
  • Saving addresses with orgs that have state/country picklists enabled
  • Matching Sponsor gifts no longer relate to incorrect Contact and Account

Important Changes

  • Names are no longer automatically re-formatted to only uppercase the first letter of the first/last name for FRS campaign types. Names will now mirror the casing/formatting in Classy
  • Transaction Type field on Opportunity will now be set to “Registration” for registrations and "Donation" for donations on donation pages or additional donations for registrations
  • For registrations where a single email is used to create multiple registrations, individual Contacts will be created based on the First/Last/Email when Enhanced Contact Matching is enabled
  • Classy Lookup fields are no longer editable in order to reduce issues related to these fields containing differing values from Classy.

Q1 2017

6.125

Released April 13, 2017

 

  • Bug fixes related to default Custom Settings
  • Bug fixes related to default Salesforce Duplicate Management settings

6.0

Released February 23, 2017

 

  • Enhanced Contact Matching
  • Improved Logs for better troubleshooting
  • Real-time sync with new Fundraising Suite campaigns
  • Accounts are now created by NPSP instead of Classy for Salesforce
  • Contact Data Now Populates with Billing Info and not Member Info for FRS Transactions

Q1 2016

5.201

  • Completely revamped UI for Classy Custom Field Mapping
  • Better support for mapping to Date/DateTime and Currency fields
  • Bug fixes related to incorrect Amounts for ticket purchases that incorporate a portion of the event fee
  • New custom field: Classy Order Total on Opportunity

5.111

  • Fixed issue with incorrect Date of Last Donation on the Contact record
  • Updated enhanced contact matching to allow matching for non-string fields
  • Bug fixes related to matching on multiple email fields
  • Improved query to search for existing Classy jobs in Post Install script

5.1

  • Contacts were not being created in orgs with Enhanced Contact Matching enabled but no saved criteria
  • Moves Contact field updates from a third party integration (i.e., our NGOC integration) are now being applied AFTER Accounts are created; this was causing issues in NGOC, which expects an AccountId value on Contacts

5.0

  • Improved Account/Contact creation process
  • Improved Campaign Member Roles (if a fundraiser joins a team, their role will update to Team Member, and if they leave, will return to Fundraiser role)

Q4 2015

4.312

  • Adds a new custom field called Organization ID to Opportunity; this helps organizations that have multiple Classy accounts connected to a single Salesforce instance

4.3

  • Added additional fields to roll up reporting on the Contact record, including new fields for number & total amount of recurring donations, number of fundraising pages created, and new fields for number & amount of donations for the past X days, where X can be set within Classy custom settings.

Q3 2015

4.24

  • Adds the option to set custom Record Types for all Account, Contact, and Campaign records created by Classy

4.23

  • Updates Team and Fundraising Campaigns so that donors to a page are added as Campaign Members; previously donors were only add to the parent Campaign.
  • Added a setting to force the Primary Campaign on an Opportunity to always be the parent Campaign, instead of a team or fundraising Campaign.

4.22

  • Added new custom fields on Opportunity: Discount Code, Discount Total, and Browser Info

Q2 2015

4.2

  • Added custom fields for Billing First/Last Name on Opportunity
  • Removal of deprecated objects/fields

Q1 2015

4.193

  • Added support for Fundraiser Alias field on the Campaign object. This field is used for fundraising pages that want to display a name other than their contact name.

4.192

  • Contact Mailing Field Update

  • We enountered an issue where the Mailing Address field on Contact records was not getting added properly. This new packages provides a resolution for this issue.

4.19

  • New Transaction Type Field

  • In this version we've added a new field for Transaction Type which indicates whether a purchase is a donation, ticket, or registration. The API name of this field Stayclassy__Transaction_Type__c

4.16

  • NGO Connect Release

  • Our newest version of the NGO Connect package is now avialable.

  • Custom Layouts

  • Instead of changing your organization's record layouts when you install our package, you now have the option to use our record types at your leisure, when it makes sense for your organization. They will no longer appear as the default.

  • Custom Field Mapping

  • With our custom field mapping tool you can push your Classy data to a custom or standard field of your choice on the same object. Field mapping is available for Custom Answers, Opportunities, Campaigns and Contacts.

  • Custom PriceBook Attribution

  • If your organization uses a unique PriceBook, let us know and we can add that setting to our database.

3.5

  • Fixed bugs caused by field level security from previous version

3.33

  • Integration now allows a Classy top-level Campaign to be a child of an existing Campaign

3.3

  • Update the logo and app labeling to reflect our new name, Classy!
  • Added a new custom object, Recurring History, to capture detailed events related to a recurring donor profile, including payments, failures, and cancellations.

Q3 2014

3.26

  • Added Team Captain & Team Members (Fundraisers) as Campaign Members under the Team Campaign Record
  • New Attendees Report for Event & Registration Campaign Types
  • Added support for Birthdate field
  • Provided better logic for updating empty Contact fields (preventing updating existing fields when empty in StayClassy; allowing updating if org has update field setting disabled but the field is empty in Salesforce)

3.23

  • Added support for State/Country picklists for Contacts
  • Bug fixes for matching existing Contact records
  • Security fixes for App Exchange submission

3.2

  • Added Custom Objects for Classy Questions and Classy Answers. These objects are hold response to data from custom fields asked via StayClassy fundraiser, ticket, registration, and donation forms. Please add related lists for these objects to your Campaign, Contact, and Opportunity page layouts to show the data for your StayClassy custom fields.

Q2 2014

3.14

  • Added Tickets/Registrations as Products
  • Tickets/Registrations displayed as Opportunity Line Items
  • Added Fundraiser as an Opportunity Contact Role
  • Added settings to prevent overwriting existing Contact fields

Q2 2014

3.0

  • Fundraisers/Teams are now Campaigns; moved all code logic to Apex; better support for bulk uploads

Q4 2013

2.1

  • New Classy Dashboard with pre-defined reports for a high-level overview of StayClassy Activity

2.0

  • The StayClassy app now utilizes the standard Campaign and Opportunity objects in place of the Classy Campaign and Classy Transactions custom objects. This allows for deeper integration with SalesForce processes as well as third-party apps that utilize the standard objects.

Q1 2013

1.0

  • Initial release of the StayClassy package