CiviCase Status Update Extension

CIVICRM - CIVICASE STATUS UPDATE EXTENSION

Are you worrying with the existing CiviCase component? because it does't allow you to update case status. No need to worry any more. Top-notch Extension is here.

The aim of this extension is to extend the CiviCase component functionality to update the case status any time.

MEMBERSHIP PERIODS

Are you struggling with the existing CiviCRM membership component? because it does not maintain membership periods. No need to worry any more. Top-notch Extension is here.

The aim of this extension is to extend the CiviCRM membership component so that when a membership is created or renewed a record for the membership “period” is recorded.

MANAGE :

Membership Churn Reports

Many organizations using CiviCRM wish to measure the CHURN rate of their members.

CHURN is closely related to the concept of average customer life time. For example, an annual churn rate of 25 percent implies an average customer life of four years. An annual churn rate of 33 percent implies an average customer life of three years.

Fast Action Links

Get your work done in fewer clicks!  Speed up your most tedious CiviCRM workflows by adding custom action links to your search results.

With a single click, you can execute one or more actions on a contact.  This is ideal for speeding up application review processes, one-click check-in to events, or any other situation where you want to take action on a set of contacts one by one.

Map Pins

CiviCRM natively supports one of three different map markers based on the contact type (Individual, Household, Organization). The Map Pins Extension allows you to replace those markers with custom markers of your own, based on configurable sets of rules depending on contact sub-type, group, tag, or other criteria.

 

Civi-RIP

Sets opt out flag when people are marked as deceased. On install deceased existing contacts will be opted out.

Note that most CiviCRM processes take the is_deceased flag into account so this is likely to be of use only if you have specific data processes that benefit from it

cards.iwwa.belgium

Extension with Belgian magic.

With this extension enabled, if you create or update a Belgian address, the province is determined based on the postal code. If the address belongs to a contact that doesn't have a preferred language, a preferred language is set based on the province. (This mainly applies when a contact was created using the API, otherwise CiviCRM will use the default language from the settings, I presume.)

This determination is not 100% correct, but I accept pull requests, as always.

randomness