Platform
New
- We've implemented an initial Upland MobileCommons integration, which allows organizations to sync signature or attendee information from ControlShift to Upland MobileCommons. Upland MobileCommons is a messaging tool and this integration will allow organizations to send automatic text messages after supporters take action. To get started, go to the Settings page > Integrations and click Add. †
Updates / Bug Fixes
- For organizations with reCAPTCHA enabled, signing a petition or submitting a contact message on Safari required the user to click the sign/submit button twice. We've released an update so users will only need to click once.
- We've updated our developer documentation to remove outdated bulk API instructions and references to requestb.in.
- We've updated the code that's used to select all notification methods on the user account notification page.
- We've fixed an issue that was preventing users from flagging inappropriate comments.
- We've fixed an issue where the download your data button was running off the screen on mobile.
- We've fixed a grammar issue with the phone number help text on the user creation form. †
- We've loosened our email validator to check for A and AAAA records, not just MX records. The previous validation excluded some university and older self-hosted mail servers.
- We've continued our work on a project to rewrite large portions of the javascript that powers the application to make it more modern, efficient, and reliable. This portion of project included updates to the categories selector during petition launch, the just launched banners for events and petitions, the image upload and crop process during petition launch, the profile picture upload and crop process, and modernizations to the Embedly integration.
- We've added HMAC signing support to webhooks. This allows signing webhooks with a shared secret so that the receiving application can determine if they've been tampered with in flight.
Petitions
Updates / Bug Fixes
- When people like a reason for signing on a petition page, we update the heart icon to be a light red. Previously, the color of the icon was only updated after the user reloaded the petition page, but we've updated the code so that the confirmation of the like happens automatically.
- We've updated our authenticated API so that the signature creation API endpoint doesn't fail when the organization has EU data processing consent enabled.
- We've updated the code used for setting a petition's moderation status from the petition signature page. If the petition is edited, ended, or reactivated, admins will see a link that directs them to the moderation queue.
- We're now allowing organizations to add a definition for dormant petitions. By default, a petition is dormant if no blast emails are sent and the petition is not edited within 12 months. However, admins can change the petition dormancy threshold from the Settings > Options > Petitions page. A petition's "Active" or "Dormant" status will be displayed on the petition's Admin > Details page. Eventually it will be possible to filter the All petitions page by whether petitions are Active or Dormant. †
- We now support including signature responses to custom fields as variables in URLs or emails. This may be useful for organizations who want to include responses to custom fields in the thank you for signing email or to send custom field responses through to an after-action page. To use the custom field response, use
{{signature.foo}}
wherefoo
is the custom field's short_name. For example, if you have anis_customer
custom field, you can include that variable in a redirect URL by redirecting signers to:https://www.example.com?customer={{signature.is_customer}}
Events
Updates / Bug Fixes
- We've updated the code used for setting an event's moderation status from the event RSVP page.
- We've updated the code for the date and time picker to more modern code.
Groups
Updates / Bug Fixes
- We've removed the profile picture upload process from the group creation flow.
VisitThem
Updates / Bug Fixes
- We've fixed an issue that was preventing users from signing up for new accounts.
† 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.
Comments
0 comments
Please sign in to leave a comment.