A few months ago as our organization was just starting to use CiviCRM, Dave Greenberg recommended that we look at CiviCase as a solution for our admissions team to keep track of prospective students. As a collection of activities associated with a client, CiviCase looked like a great way to record our interactions with potential students as we made initial contact, followed up, received communication from them, sent more info, and then accepted their applications. From a DB point of view, yes, it is a nearly perfect way to store that information. But from a UI point of view, we had a long way to go before our admissions team would be able to painlessly get the data in, work with and update it once it was there, and then be able to get it back out in the form of reports. Here's what we did to make that happen (and more!):
Blogues
Restez à l'affut des dernières nouvelles de CiviCRM avec les billets de blogue de développeurs et d'utilisateurs de partout dans le monde.
This past Monday, the 18th of October 2010, a group of about 10 people gathered for Toronto's fifth ever CiviCRM Users' Group Meetup. The turnout was up significantly from last month, and we look forward to growing the local community even more. In future, we'll make sure to post clear and detailed directions to the location to ensure everyone who wants to come can find us!
Great news for CivICRM users in the UK. CiviCRM now comes with 'out of the box' support for Gift Aid. The code is freely available for download, installation (instructions here) and use on your site.
It's 3.3.alpha1 time! After a couple months of work, it's finally time to push out all those new cool features out! Before jumping directly on downloads (yeah, we know you can't wait!), we strongly recommend going through 3.3 highlights post, where you will find out what's new and hot in this release.
If you want to experience 3.3.alpha1, it is now available for download. You can also try it out on our sandbox site. Please remember this is an ALPHA release and it should NOT be used on production sites.
As we are getting ready to roll out the first alpha for CiviCRM v3.3, I figured a status update on some of the cool new features of 3.3 was in order. So without further ado, here are some of the cool new features that are part of 3.3
As a part of 3.3 release we will be deprecating all v1 api's and if you are still use them, it's a good time to migrate to v2 api's before upgrading to CiviCRM v3.3 release.
CiviCRM api v2 were introduced in v2.0. For every v1 api there is equivalent v2 api.
Reason for removing v1 api's:
A quick look the book CiviCRM a comprehensive guide: how we got here, and our plans for the future
Just a quick update to say that the 'de-dupe exception table' initiative is now funded for release 3.3. This will allow those poor souls struggling through a big de-dupe to mark some contacts as 'non-matches' and not have to wade through them every time.
This initiative was sponsored by
Creative Commons
Community Builders Australia Pty Ltd
Australian Greens
NES Alumni and Friends Nonprofit Partnership
Today is the last day of the Bristol code sprint, which was a great experience! Lots done, climbed the Cheddar Gorge and tasted Kurundś famous lamb.... I will also always remember it for finding out I was part of the API team :-)
On a serious level, it is a good idea to have a team of people that take care of the API's. And taking care I think involves:
One of the goals of the (ongoing) Bristol code sprint was taking a stab at making the API calls properly permissioned, and I’m happy to report that after two days of very fruitful hacking with Erik and Xavier we’ve landed the crux of it on trunk (to be released as CiviCRM 3.3 later this autumn).
