I have just finished the development of a new extension for PUM (http://www.pum.nl - thank you!!) to be able to add a coordinator (with start and end date) to a tag. I have added the extension to the extension directory (https://civicrm.org/extensions/enhanced-tags). The extension is also availalbe on GitHub where you can find a little more documentation: https://github.com/CiviCooP/org.civicoop.enhancedtags.git
Last week I have been working for MAF Norge to connect CiviCRM to their SMS Gateway (PsWinCom) so that they can send and receive SMS from within CiviCRM. In addition PsWinCom offered a the possibility to send SMS which will charge the receiver an amount of money. This way MAF Norge used to receive SMS donations. Now they can do that from within CiviCRM.
SMS Autoreply extension
The SMS Autoreply extension does sends auto replies to incoming sms-es. It is triggered by a keyword...Read more
I think I saw the first demo of the CiviCRM extension dataviz after the post-CiviCon London sprint. Xavier Dutoit had been working real hard on this, and Hannelore and me were very impressed! The possibilities are great, and data visualization is IMO so much better than numbers on a report! Data becomes so much more alive.
I immediately thought it would be a great topic for a webinar. Last month I spent a co-working day with Xavier and we installed dataviz on the development server of MAF Norway and they were suitably impressed too! On top of that, the data visualization will be part of the Google Summer of Code (see https://civicrm.org/blogs/kreynen/gsoc-meet-the-students).
As we want everyone to be able to see what CiviCRM dataviz can do for them, we scheduled a webinar! On 27 May 2014 at 17.00 CET (check...Read more
One of the requirements in a project I am working at the moment was that the client wanted to enter when an adress becomes active. E.g. a member says he is moving by the 1st July 2015 (which is in the future). From that moment the member should be contacted by that address and till that moment the old address is the active address.
I have created an extension which achieve this. This extension is in beta and can be found on (https://github.com/CiviCooP/org.civicoop.futureaddress).
I will put this extension into the extension directory later on, when my client has finished testing this extension.
How does this extension work?
As a user you enter a future address by adding a new address on a contact and you set two things:
- You enter a location type which is a future one
- You enter a change date (the date when this address is changed)
A final blog about our Donor Journey sprint with Steinar and Helen from MAF Norge. Or I should really say our sprint on CiviCRM Trigger Action. We set out to at least create the first basic version of the engine to automatically do stuff based on stuff in CiviCRM :-) Some kind of mechanism that would allow MAF Norge to automatically move donors into specific groups once they have contributed for the first time or set up a recurring payment for example. I feel we have made a good really start on the engine, for more technical details read the previous blogposts by Jaap Jansma (jaapjansma in Civispeak). The first test was quite successfull, and going through the list of triggers with Steinar worked pretty well. As we expected we did make one of the most unsexy things ever, which is a nightmare to configure. So even though Helen and Steinar can work with it, it is not something I would hesitate to hand out to everyone...but it is...Read more
Today a new blog post about the progress of the implementation of Donor Journeys into CiviCRM. The route we are taking is that we want to create a trigger/action extension for civicrm because most the donor journey automation is based on a trigger/action. e.g. payment coming in resulting in a thank you SMS a day later.
Yesterday and today we have been working on refactoring the extension to meet the requirement of combining multuple triggers and having the possibility to have condition on custom fields as well. So we have decided to let go the trigger action table/structure and have decided that we have a rule_schedule table...Read more
Yesterday I wrote a blog about the first day in the sprint for the donor journeys. I have discussed that we are focussing on a trigger/action extension to automate most of the donor journeys. I wrote a bit about the internal working and the data structure of this extension.
Today we have finsished the internal working of the system. It is now possible to define triggers and actions. Right know you can enter those only in the database. We have made a start with the user interface and we continue to developer the user interface tomorrow. So that a user can enter a set of triggers and actions. In this blog post I want to show you how you can enter the trigger and actions in the database. The reason is that this will show in more depth how the extension works.
To explain how the extension work let me first explain which trigger/action I will use in this example.
Example: add every...Read more
The planning of this is an outcome of the unconference we had in Januari in London, with LLR, Amnesty Flanders, MAF Norway, Decaid Consulting and CiviCooP. The aim for this sprint, which last for only one week, is to create a trigger/action functionality for civicrm. E.g. we want a trigger that a donor becomes a member of a group of its total contributions are more than 25.000 euro's. Or when a contribution is completed we want to sent out a thank you message based on the communication preferences (e.g. e-mail, sms, postal mail).
What we have done today is to brainstorm on how we want to setup the extension for the trigger and actions. We have created a data structure and started working on the first draft of the user interface. In this blog I want to introduce and explain the data structure and the working of the triggers.
The internal working of the trigger action extension is based on three components:
- A trigger (e.g....
Once upon a time there was a charity who was a visitor to both the lands of Xero and CiviCRM. This charity liked Xero and wanted contributions created in CiviCRM to be sent to the land of Xero. In the land of Xero these contributions would be called invoices and they would be matched with payments. Upon their return to CiviCRM all would know about their paid status and events would be confirmed and emails would go out and all would be be well. They spake with a mighty sorceress from the far-away do-ocracy of Fuzion and verily this came to pass.
At this time the wizard of Xero was little known and although others came seeking the path they found it tortuous, hard-coded and drupal 6 specific. But, as the prowess of Xero grew, more came seeking. Enter the Circle - a brave gladiator called Andy from Circle Interactive set out on the quest of building a bridge for users of Drupal 7 to the growing kingdom of Xero. Like many brave adventures this...Read more
Have you ever needed to send an email from CiviCRM that includes a list of upcoming events? Then you know how much fun the copy/paste effort this entails, especially if you want to use a checksum in the links to register. Plus you know you get to repeat the whole exciting process for the next newsletter the following week or month. Or if you have someone else you need to train on this task, try explaining to a non-technical person how to hand-edit the URL query string to include the checksum paramaters. (is the contact ID query string param name "cid=x" or "id=x", well that depends....) And even if you do not deal with events, you can have the same fun teaching someone else to properly use checksums when you need to include a hyperlink to a contribution page or a stand-alone profile.
If you want a much easier process for listing upcoming events with links to register, including links to contribution pages and stand-alone profiles, then try out the new extension...Read more