Last week, I showed you how to create a Queue overdue list of persons report.
This week, we’re going to work with the same tutorial, yet extend upon the base functionality you developed thus far.
As with any tutorial we extend upon, I’m not going to cover the nitty-gritty details of the previous tutorial. You’ll have a bit of reading and review for areas you find to be challenging.
That said, today’s tutorial focuses on having a Queue overdue persons report emailed to you using Church Community Builder’s API service.
You would right to think that you can already do such reporting by using the existing web front-end interface as provided by CCB.
But what if you wanted to access the data programmatically using a 3rd-party system?
Well, this is where last week’s and today’s tutorials come quite in handy. Let’s get started.Read This Tutorial
I’m back with a doozy of a tutorial today based upon using Church Community Builder’s (CCB) API to create an overdue persons report.
In short, CCB innately provides notifications when individuals are placed in a queue and their due date expires without the queue manager taking action.
For example, our church has a number of ministry service teams:
- Coffee Bar
- mKids (Children’s Ministry)
- mYouth (Youth Ministry)
- Elevate (High School)
- Chi Street (Homeless Ministry)
- Worship Team
These various ministry areas rely on our Connection Card, Member Class, and Foundation Class processes to supply their ministry with volunteers to serve.
One of the things that can happen often is that queue managers, often volunteer ministry leads, forget to check their queues even with reminders auto emailed by CCB natively.
After all, it’s not a volunteer’s full time job or responsibility.
However, this type of inactivity causes communication challenges and breakdowns when ministry leads are not communicating in a timely manner to volunteers who have a desire to serve.
So today, I’ll show you how to create a report for a specific queue to determine how many days an individual is passed their due date.Read This Tutorial
I happened to check my email folder containing The Village’s emails, and found an email where someone was in need of a mass addition to process queues using the CCB API.
Of course, you know this made me perk up a bit. I opened the email to find the need addressed as follows:
In our organization we want to be able to track people who have completed a certain curriculum.
We have about 10 inactive groups of people who have this curriculum in the last two years.
Is there a way to add all of these people to a process queue?
I know I could reactivate all the groups and then search by group name to do a mass add via an Advanced Search.
However, I already have a spreadsheet of these people with their individual IDs from CCB.
It would be much easier to add the people by their individual IDs.
Geez, just re-reading the title makes me (and probably you too!) cringe at the thought of using the Church Community Builder API to automate processes, queues and attendance reporting into a repeatable dynamic action.
That’s a thought and mouthful to repeat.
Well, it’s been a fast moving week for me, and I’ve been a bit slow delivering today’s tutorial.
In fact, I wish I had finished and posted it earlier than now, and let me explain why.
As most of you know, I’m a member of and volunteer at Mosaic Church in Austin, Texas. My primary responsibility outside of discipling, ministering and leading is being the point of contact for our Foundation and Membership Classes, and the Membership Process in its entirety.
We recently had our latest Foundations Class end this past Sunday. As I was attempting to MANUALLY figure out who attended 4 or more classes and completed Membership Class, I was reminded how much I needed today’s tutorial.
It is possible to manually create reports using the CCB front-end interface and achieve the task.
However, I rarely have time to lose, and I like being able to setup the use of repeatable and dynamic automation using cron jobs. Read This Tutorial
Yes, another week has passed as fast as the speed of light.
It’s time for another tutorial.
This week I’ll lead you in creating a city, state dashboard much like we did with last week’s tutorial: Your Church’s Zip Code Dashboard.
It’s important, in my humble opinion, for a church to understand the dynamics and demographics of their church to be able to serve and reach their church and, more importantly, the surrounding cities and communities.
And if you church’s pulse is community group like ours is, then these dashboard reports are going to help you identify and anticipate where groups need to be launched.
Yes, preventative action and forecasting the growth of your church based on your current data.
Second to God providing your church wisdom and discernment for where to cast nets, if data is coupled with your city and surrounding areas’ population growth (by zip code or city), then you really can see where your church is reaching and should reach.
I think you get the point. Enough talk, and let’s get started with today’s tutorial.Read This Tutorial