- Language support for “de”, “hi”, “ja”, “mk”, “th”, and “tl”
- Import Phone Contacts
- Link support for Maps and Social Media
- Lots of bug fixes!
Release Date Planned: 27th of January 2021.
Previously, certain roles such as the Admin were able to see all system contact records. This presented security, trust and management/workflow issues that needed to be navigated, especially as Disciple.Tools instances grew and added hundreds of users and thousands of contacts. For clarity we attempt to show each user only what they need to focus on. By implementing contact types, users have far more control over access to private information.
To start, with personal contacts, users can create contacts that are only visible to them. The user is able to share the contact for collaboration, but is private by default. This lets multipliers track their oikos ( friends, family and acquaintances ) without worrying about who can see the details.
This contact type should be used for contacts that come from an access strategy like a web page, Facebook page, sports camp, English club, etc. By default, collaborative follow-up of these contacts is expected. Certain roles like the Digital Responder or the Dispatcher have permission and responsibility for fielding these leads and driving towards next steps that would lead to handing the contact off to a Multiplier. This contact type most resembles former standard contacts.
The Connection contact type can be used to accommodate for movement growth. As users progress toward a movement more contacts will be created in connection to that progress.
This can contact type can be thought of as a placeholder or soft contact. Often the details for these contacts will be extremely limited and the user’s relationship to the contact will be more distant.
Example: If a Multiplier is responsible for Contact A and Contact A baptizes their friend, Contact B, then the Multiplier will want to record this progress. When a user needs to add a contact simply to represent something like a group member or baptism, a connection contact can be created.
The Multiplier is able to view and update this contact, but does not have an implied responsibility that compares to the responsibility of access contacts. This lets the Multiplier record progress and activity without overwhelming their working list, reminders and notifications.
While Disciple.Tools has developed as a solid tool for collaborative access initiatives, the vision continues that it will be an extraordinary movement tool that will aid users in every phase of Disciple Making Movements (DMM). Connection contacts is a push in this direction.
See roles documentation (for developers)
Modules extend the functionality of types of records like Contacts or Groups. A module resembles what can be done through a plugin. The big difference is that modules can be added to a Disciple.Tools system while allowing each instance Admin to enable/disable the modules they want or need. The core theme and plugins can now package multiple modules. A developer is still needed to create a module, but once created, control of its use can be distributed to the Admin of each site.
A module can be used to add/modify:
With the v1.0 release, the Disciple.Tools theme has added 2 main modules by default.
The DMM module adds fields, filters and workflows that pertain to: coaching, faith milestones, baptism date, baptisms etc. These are fields needed for anyone pursuing a DMM.
The Access module focuses more on collaborative contact followup and come with fields like the seeker path, assigned_to and subassigned fields and update needed functionality. It also adds a follow-up tab to the filters on the contact list page.
See modules documentation (for developers)
See list of code changes: here
Celebrating new Languages:
-Fix languages direction issue.
-Fix baptism date being in the wrong timezone @micahmills
-New endpoint for contact transfers
See 0.32.1…0.33.0 for full list of changes