CivicActions is offering a full day CiviCRM User Training in Seattle and in Berkeley.
Blogs
Keep up-to-date with blogs from the core team, working groups, developers, users and champions worldwide. Subscribe to our newsletter to receive regular updates by email. We also have an RSS feed.
After what seems to be an incredibly long time, we released CiviCRM v3.2 a few weeks ago to good reviews and not too many critical bug reports :). Now that is out of the way, we are starting to plan the feature set for v3.3
We've been fortunate to get a grant from Open Society Institute to help add some features important for Human Right Organizations, specifically for Front Line. We've been working with Front Line for a few years and this grant allows us to target their needs more effectively. Some of the features that are included in this grant are:
Extending Address inheritance from Organization to an Individual (or from any contact to any other contact - TBD).
Building Advanced Reports and Dashlets for Human Rights Organizations
First version of Logging
I'm very thrilled and excited to announce that, we will introduce CiviCampaign as a Core CiviCRM component for Campaign functionality in CiviCRM v3.3
With the help of CiviCampaign we could effectively use CiviCRM for Voter Canvassing.
It allows you to define a group of contacts for canvassing who are voters for a survey. We are storing report of each voter interview with lots of flexibility.
I have developed very basic iphone app for CiviCRM using Titanium framework.
Tokens are used in CiviCRM to create mail merges in much the same way as, for example, Microsoft Office. They are currently implemented in (at least) four places in CIviCRM: 'CiviMail', 'Send Mail to Contacts', 'Create PDF Letter' and 'Create Mailing Labels'. Out of the box Civi comes with a decent set of tokens, including tokens for all the address fields. One thing it doesn't do is provide a token that correctly formats an address block taking account of when fields aren't present. For example, if i used the following address tokens for my address:
Hi all,
We probably all have the same problem: the same contact is present several times in our CRM.
We just released CiviCRM 3.2.1 - it is now available for download. You can also try it out on our demo site.
Being able to efficiently identify and merge duplicate contacts and related data is be an important -- and often time-consuming -- task for organizations getting data from multiple sources. The current CiviCRM dedupe and merge process does not scale well beyond a moderate number of contacts and consequently there has been dicussion on the forums and IRC about optimizing the dedupe and merge code in CiviCRM.
I've been working through case configuration with a few clients over the last several months and have run into a few areas where I think the functionality could be improved. The core team asked that I outline it for the community to see if other groups experience similar workflows and would benefit from these changes.
Finally, the time has come. Ladies and gentlemen, without further ado, here is CiviCRM version 3.2.0, stable - it is now available for download. You can also try it out on our demo site.
This release includes several major new features/highlights: Usability improvements - Better looking and more intuitive Contact Summary Page. The new "Actions" button provides 1-click access to most contact-related forms. New clean and consistent icons have been implemented to provide helpful visual cues. You can now get a configurable contact summary pop-up from search results by mousing over the contact icon on any row. We'll be blogging with more details on these usability features during the release cycle. Support for PHP 5.3 -This release supports PHP 5.3. CiviCase Phase 3 - Thanks to the Physicians Health Program folks for pushing CiviCase to the next level! You can check out the phase 3 enhancements here. CiviEvent workflow improvements - Streamlining the workflow for events, providing 1-click access to event related screens from the configuration panel, and generating event name badges. For more details check CRM-6230 and CRM-6294. Free-tagging, and Tags for Cases and Activities - You can add one or more free-tagging "taxonomies" - called Tagsets - for use with contacts, cases and / or activities. You can also specify which tags can be used for which types of records. Standalone version dropped - Please note that we are dropping support for the Standalone version in 3.2. We recommend that current standalone users convert their installations to run under a basic Drupal install during this release cycle. ... and lots of other improvements. Check out the complete listing of new features, improvements and bug fixes on the issue tracker.
