Updates / Bug Fixes
- Updates to the BSD integration: we now allow organizations to sync petition custom fields. If your organization is using BSD, we should have emailed your tech contact directly about a few updates we need them to make before the new code is made live. If you're the tech contact at your organization and you don't know what we're talking about, we're sorry! Send us a support email, and we'll attempt to make it up to you by giving you a few minutes of extra work.
Regardless of who you are – assuming you have full admin privileges on a BSD instance – you can make the necessary updates by following these instructions. If you're an admin at a BSD-using organization and don't want to change the configuration, that's fine too – we'll be in touch once the code is live to explain how it will work. (If you're not on our mailing list, you should be!)
- Updates to our new ActionKit events sync. Before, if a host did not include a venue name with the event location, the event would not sync with AK. We've fixed that issue and now the sync should work as expected. If you work for an organization using ActionKit and didn't know that we're now syncing events, we either didn't email you (in which case you, too, should join our our mailing list), or you didn't read the email we sent (in which case, you can see the email or peruse the help doc.)
Updates / Bug Fixes
- We've included a new JSON API endpoint that allows you to recreate the 'search-for-nearest-petition-in–an-effort' search box, as well as see all of the petitions in an effort. More info on our JSON endpoints.
- We've also updated our petition signature webhook to include partner and effort petition slugs. More info on webhooks.
Nothing new in events, groups, or TakeCharge.
(For those of you not particularly interested in the technical minutiae of CRM integrations, JSON API endpoints, or webhooks – our apologies. We're thinking of this week as a love letter to tech directors and we'll try to make next week's release notes a bit more exciting.)