Introducing: Universal Fields
For many organizations, entities may appear in multiple campaigns, and organizers often need access to information about those entities that goes beyond the standard ‘core’ fields on entity profiles. This could include persistent data such as demographics, interests, certifications, or other key attributes that aren't specific to any one campaign.
A potential use case for universal fields is tracking information about entities who are part of both a broader network and individual campaigns. For example, you might use universal fields to track issues someone cares about or their volunteer shift availability. This ensures that organizers at different levels can view and update the same shared information across campaigns.
Notes:
- Universal fields are created within universal sections (Administration > Info).
- Fields can only be created in either a universal or a regular section — they cannot be moved between the two.
- When a universal field is added to a campaign, all responses to that field are enabled and visible across any other campaign where the field is used. If you want to keep the field unlocked, remember that any data entered will be shared across campaigns using that field.
Updated SQL Mirror Documentation
Exciting news for developers using the SQL Mirror — we now have public documentation available! Check it out on our website here. If you would like to set up SQL Mirror access for your organization, have an administrator email us at support@actionbuilder.org.
Preferred for Single-Name Entities
The preferred name field is now available for “single name” entity types. Some examples of how you might use this include:
- Acronyms: You might want to find professors at Michigan State University and searching for “MSU” would be a convenient way to find them if that was stored in addition to the full name of the institution
- Colloquial names: Amazon Warehouse #12345 may be called "Fifth Street Warehouse" by the organizers, etc.
Turf Routing Limit Warning
Google Maps has a limit of 21 addresses when creating driving routes. If you create a turf with more than 21 (route-able) addresses, we’ll now show you a warning that the turf size is too big so you can adjust them accordingly before folks go in and try to create the route.
Note: if householding is turned on for a task, that will be accounted for in the total address count. So multiple entities at one address will only count as one address on the route.
See Who Created a Task
You can now see the Task creator’s name next to each Task in the Task Lists and on an individual Task manage page.
Regional Support Expanded to UK
We are excited to announce that, thanks to a partnership with [Small Axe], we are expanding Action Builder’s regional support to include UK-based data. In this release, we have implemented support for UK addresses (including making the United Kingdom the default country at the organization- or campaign-level) and phone numbers. Geolocation is still in progress, so mapping on UK addresses is not yet possible. Stay tuned!
Our privacy policy and Terms of Service have been updated. To set up a data protection agreement reach out to join@actionbuilder.org.
Bug Fixes / Minor Improvements
- In Chart View, you can now see a connection’s assessment level and easily click through to their profile.
- Shared contact info will now only show the icon if it’s not ‘marked as bad’.
- DOB/Age and Language now have separate profile sections (and an option for multiple spoken languages is in the works!)
- You can now have start and end times for shifts at any time, not just :00 and :30.
Comments
0 comments
Article is closed for comments.