This update includes information about new features aimed at supporting GDPR compliance. If you are a European organization or process the data of European residents, you may be affected by the GDPR. We highly recommend consulting legal advice to assess your liability and any necessary changes to your processes.
We're also hoping to schedule calls with every affected CSL customer. We've emailed staff at each organization, but you can also see our checklist here: https://docs.google.com/docume
Updates / Bug Fixes
- Infrastructure updates.
- Updated Spanish, French, Dutch, Arabic, Romanian, and German translations. Thank you to all of the organizations that keep our translations up to date.
- We've continued our work toward supporting organizational compliance with the EU's GDPR. We've already added support for tracking consent status and version information on admin member record pages (accessible by searching for the member's email address from /org/members). That information is also now included in webhooks and the authenticated rest API. In webhooks, consent status and version is included in the signature, attendee, local chapter member, and user webhooks. For the rest API, that information is included in the members API. This consent information will also be included in bulk data CSV exports. More information can be found in our developer docs: https://developers.controlshiftlabs.com.
- Also included in our GDPR compliance work, we've added support for tracking email opt-in consents (which is separate from the above data processing consent). This is an ongoing feature and more information will follow.
- We've exposed a new JSON endpoint for petitions in a partnership. This may be useful for partner organizations that wish to include a list of their partner petitions on their main website. More information can be found in our developer docs: https://developers.controlshiftlabs.com/#list-petitions-in-a-partnership.
- When viewing a member's record page (from /org/members) the page would crash if the user made a donation on a since-deleted petition. This is now fixed.
- For organizations using the Salsa CRM sync, we're now sending language information for signatures/members and mapping that information to the appropriate field in Salsa.
- The cookies banner that some organizations have enabled was not working on the admin pages that have our updated UI. This is now fixed.
- We're sunsetting the query page/feature which is currently located at /org/query/new. We recommend that users wishing to continue performing SQL queries on their CSL data use webhooks to send platform data to a more modern and robust SQL tool.
Updates / Bug Fixes
- In the All petitions list (/org/petitions), the Source filter's dropdown is now alphabetized.
- The bottom of the offline signatures collection form pdf referenced the previously-deprecated petition manage page. We've updated that sentence to directly reference the URL of the offline signatures page. †
- When a user updated a petition's thank you for signing email, clicking the save button in the after-signing section wouldn't save the updated email template if the user had also updated the after-signing daisy chain. This is now fixed.
- We've added support for a global after-signing redirect rule. Like our other global after-signing rules, this rule can be set from the org settings page (/org/settings > Post Action Flow). Using this global default post-signing rule will allow admins to set a default redirect to a new URL rule for all petitions. This new rule also supports including liquid variables in the resulting URL. For organizations redirecting to a donation page, including a liquid variable will allow admins to track which petitions are leading to donations. †
- We've removed support for including a redirect parameter in a petition's URL. Previously, this allowed admins to include an arbitrary URL in the petition signature page's URL that signers would be directed to after signature. Because of the possibility of this being used for nefarious purposes, including phishing, we no longer support this method of redirection. All redirects will need to be configured in the petition's admin settings > after signing section.
- Blast emails from partners now appropriately include the partner organization's name in the email's from field and use the partner's email address as the email's reply-to address. The from name and email address can be set from the partnership's settings page. Note that this only affects blast emails that are created from the partnership's manage page (e.g. /partnerships/[name of the partnership]/manage), not blast emails that are created from a partner petition's email supporters page even if the drafter is also an admin of the partnership. (More information on configuring from name and email settings: https://controlshiftlabs.zendesk.com/hc/en-us/articles/203073587-Tutorial-on-Partnerships#settings.)
Updates / Bug Fixes
- On the calendar hub page, we no longer show the location search box if all of the events in the calendar (including past events) are virtual events.
- We've moved the clone event button from the All events page (/org/events) to the event's admin page (/org/events/[event name]). †
- The All events page (/org/events) now uses the same UI as the All Petitions page (/org/petitions). This new UI allows for filtering and sorting the list of events. Current filter options include: moderation status, country, location, locale, upcoming vs. past, cancelled, and keyword searches. †
The subsequent list can also be sorted by created at date, event date, number of attendees, and (if the location filter is used) distance from the queried location. †
This UI work is a first iteration. If there are additional filter and/or sort conditions that you'd like to see, please let us know.
Nothing new in groups, TakeCharge or VisitThem.
† This feature required new text strings. If you're using the platform in a language other than English, you may need to provide updated translations.