gokubi.com » CRM

Advocacy in the Cloud slides and recording

Steve — Fri, 16 Sep 2011 14:54:38 +0000

I recently had the pleasure of facilitating a Dreamforce session where two amazing people talked about how their organizations have gone all-in with engagement. The DC Project and Idaho Conservation League are each betting their futures on engagement, and in very different ways. Sara Arkle talked about how Idaho Conservation League is turning the organizational ship to find a new generation of supporters. Matthew Dunn told the compelling story of how the DC Project was birthed with technology and engagement at it’s heart. Very different stories, well told and I think helpful for folks looking to engage supporters more deeply than they are today. Below is the recorded presentation, as well as the slide deck we presented.

Advocacy in the Cloud

Chrome Extension: Salesforce.com Id Clipper

Steve — Mon, 06 Jun 2011 13:51:25 +0000

I had a great idea for a Chrome Extension that was pretty complicated, so I decided to come up with a simpler project to learn the ropes. This weekend I built the Salesforce.com Id Clipper, a Chrome Extension that helps you get Salesforce.com Ids from records more easily than copying. It’s a small problem I’m attempting to solve, but I think this extension does it pretty well. Here’s a rundown:

Go get it in the Chrome Web Store and please rate it if you try it out! The source is also out on Github free to use.

Nonprofit Starter Pack and Money

Steve — Mon, 09 May 2011 16:43:47 +0000

At a recent gathering of nonprofit-focused Salesforce developers, we got into a deep discussion about how to best track money in Salesforce. Everyone agreed that the Opportunity object was key, but there were differing opinions about what else needed to be done and how. I realized that this group of people, who had years and years of consulting experience with nonprofits, did not have a shared understanding of the best practices of how nonprofits should track money. I include myself in this group–I’ve had nonprofit accounting explained to me countless times, and it’s been a little different each time.

This article is meant to lay out what I’ve learned about this subject from all the great finance people I’ve worked with over my career. But more importantly it will examine how it all relates to Salesforce.com and some changes Kevin Bromer is making to the Nonprofit Starter Pack.

First I’ll talk a bit about how the Nonprofit Starter Pack works today. Next I’ll get into the accounting of it all, with the full disclaimer that I am not an accountant. And then I’ll get into the new way we’re going to do things, and talk about why that’s better, all with the goal of us better understanding the business processes we support.

Salesforce.com isn’t an accounting system, but thousands of organizations use it to track money. Many organizations directly integrate with their accounting systems. Modeling money well in Salesforce.com makes that kind of integration easier. And even if you don’t integrate, the changes we’re making provide much better support for key nonprofit work like pledged gifts, and gifts with multiple payments.

I got a lot of help in writing this article from Debbi Lewang, Shalinee Thakur, Nick Bailey, Sam Dorman and of course Kevin Bromer–any insights should be attributed to them, any errors in logic or accounting are most definitely mine.

How the nonprofit starter pack works today

The Nonprofit Starter Pack is used by thousands of organizations on Salesforce.com to manage their organizations and their missions. These organizations are incredibly diverse, engaging in everything from class-room education to lobbying congress to providing health care to the homeless. But no matter what they do, they must track their organizational revenue stream, and many do in the form of gifts, grants, ticket sales, etc.

Salesforce.com has a database object called Opportunity that represents revenue and potential future revenue. It was created by the company to handle sales deals when Salesforce.com was limited to Sales and Marketing. Now that the platform is so much more flexible, the Opportunity object serves well as any kind of revenue–gifts, grants, memberships, ticket sales, etc.

The Nonprofit Starter Pack uses Opportunity to track revenue, and it works pretty well. We also have a Recurring Donations package that can be used to track gifts that are paid with more than one payment. It has a simple object and wizard for creating a schedule of Opportunities spaced out at intervals you select. It is a simple way to create multiple Opportunities that are related.

There are some limitations with the way the Nonprofit Starter Pack supports money today. The main problems have to do with a lack of support for cash in addition to revenue. In the next section I’ll talk about the accounting realities that we are planning to support.

Revenue and Cash: Nonprofit accounting

Revenue tracking and forecasting is critical to all nonprofits. Annual revenue must be reported to the IRS, and any business that doesn’t know its revenue picture can’t effectively plan for the future. This is easily done by reporting on Opportunities, and most nonprofits using Salesforce.com have already figured that out.

Nonprofit accounting (and accounting in general) is more complex than simply recording revenue, though. We need to support cash tracking in addition to revenue. This is because nonprofits can report revenue without receiving any money. When that happens from a donor or a grant maker, we often call it a pledge. The donor commits to giving to the organization, and may identify a payment schedule at that time. Let’s look at an example case to get into the specifics.

The nonprofit Friends of Tiny Creek (FOTC) wins a $1 million grant from a foundation. At the time of the award, they are promised a check for $250,000 and are told to expect 3 additional payments of $250,000 over the next 3 years. How should this be recorded on the financial statements?

FOTC records $1 million in revenue from the foundation. This is revenue in the fiscal year in which the grant was received. Because the cash isn’t received at the time the revenue is recorded, it can’t be spent yet. While the funder can put other restrictions on the gift, we will assume that this one hasn’t, and the money will be available when the cash payments are received.

So this $1 million commitment is recorded as a credit (increase) to revenue on the income statement and a debit to assets on the balance sheet.

One week later the $250,000 check comes in as promised. $250,000 is now cash that can be spent. On the balance sheet, cash is debited by $250,000 and assets receivable is credited by the same amount. The effect of this seemingly backwards transaction (there is a reason I’m not an accountant) is that $250,000 of the grant funds are now available for use and $750,000 is still to be received. [1]

The initial pledge and the resulting cash are related, but come in at very different times. And in this case you can see how the date the revenue is recorded is very different from when FOTC can actually spend the money to support it’s mission efforts. If FOTC isn’t paying attention to it’s cash picture, they’re going to have a hard time planning and delivering.

As the yearly payments come in, they are recorded and revenue is released accordingly. When all payments are made, the receivable goes to zero and the funds are available.

In this case, though, the foundation in question rescinded the last payment of $250,000. In this case, FOTC must record that amount as a write off against the receivable. That balances the sheet, and the change in revenue can be reported in their annual numbers.

The case of monthly giving

On the face of it monthly giving looks a lot like a pledge of multiple payments similar to our grant example above. A monthly giver commits to $20/month and then makes payments on a schedule. However, the monthly giver’s commitment isn’t an official pledge unless they tell you the end point of their giving. In many cases the monthly gift is started with no set end date. If you don’t know the end date, you don’t know the total revenue, so you can’t record it as pledged revenue on your income statement.

Because of this, each monthly gift should be considered a separate revenue entry, with it’s own matching cash entry when it is paid.

Better modeling cash in the Nonprofit Starter Pack

As stated earlier, the Opportunity object is great for tracking revenue. But what about cash related to that revenue? There isn’t a good way to model cash in the Nonprofit Starter Pack, but lots of Salesforce.com users have already solved this for themselves–that’s the beauty of a flexible platform. We’ve looked at those solutions can come up with something that we think works pretty well. When we release this functionality, you’ll be able to turn it on, or continue to use the Nonprofit Starter Pack as you are today.

The Nonprofit Starter Pack will get a new child object to Opportunity called Payments. Payments will be where cash is recorded. The Payment object will represent all the cash received by an organization. It will be helpful in a number of ways:

Payments will allow you to record received cash payments against promised revenue
Payments will allow you to record a payment schedule and make sure you don’t forget to collect them when they come due
Payments will allow you to write off rescinded payments
Tracking cash in Salesforce.com allows for much better analytics than most accounting systems

The Payment object will have rollup summary fields to the Opportunity that show you the number of payments per Opportunity, the amount of payments that have been made, and the remaining balance. Having this information on Opportunity makes it very easy to see which Opportunities aren’t fully paid yet.

Ok, back to our scenario for some illumination.

FOTC is a very stable organization. If we look at a dashboard of their revenue (Opportunities), we see that it’s uniform. They get about the same amount of revenue each month.

Most of those Opportunities were one-time payments–the cash came in the same time the revenue did. But about a third of them were paid in multiple payments. If we take a look at a chart of the cash, you’ll see that it’s much more irregular than the revenue chart. Note that the scale is different in these charts.

The same is true with forecasting–revenue in the future is expected to be pretty stable.

If we look at a cash forecast, it’s very lumpy, with peaks and valleys.

FOTC needs to see its revenue picture and also it’s cash picture, and it’s not clear from one what the other will look like.

Revenue where the cash is received immediately

At most nonprofits, most gifts aren’t pledged, they are just given. A typical scenario is a $100 check coming in the mail. Recording that check requires recording the revenue and the cash at the same time. Data entry is a time consuming task as it is. Having to do double entry–revenue and cash–for all gifts is an unacceptable burden, so we built automatic cash recording right in.

In the case of a gift where revenue and cash are simultaneous, the new payments functionality creates one payment for every Opportunity. It keeps this payment in sync with the Opportunity, unless you choose to set up a payment schedule. This solves the case of multi-payment gifts without causing extra work for all those gifts that don’t have multiple payments.

By creating automatic cash payments for each opp, the cash picture isn’t limited just to pledges with payment schedules, but includes all cash for all revenue. This allows for better reporting, like the charts shown above.

The case of monthly giving

For monthly giving, each gift should be considered it’s own revenue event because they aren’t connected to a known pledged amount. Therefore each gift should be an Opportunity, rather than Payments under one Opportunity. Each gift will, of course, have a payment, because all revenue does when you’re tracking revenue and cash.

The Recurring Donations functionality in the Nonprofit Starter Pack will handle this case better with the next release. You will be able to create a Recurring Donation Profile, detailing the recurring gift. The wizard will then create Opportunities according to your schedule. At present moment we’re thinking that the Recurring Donation functionality doesn’t need to know about payments at all–it will just interact with Opportunities. This may change, but it’s what we’re thinking now.

Currently Recurring Donations has the word “Pledges” in the object name. If you’ve read this far, you understand now that this is incorrect. Kevin is planning major upgrades to Recurring donations, and we will likely be renaming things to make more sense. He’s also planning on supporting the automatic creation of Opportunities for open-ended giving, and keeping the Recurring Donation Profile in sync with the Opportunities. We’ll likely give you the ability to keep a rolling year of potential gifts in the system. If you don’t want all those open gifts out there, we’ll likely give you a way to keep just one open gift for each recurring donation.

Conclusion

While Salesforce.com isn’t an accounting system, better modeling of nonprofit accounting practices is great functionality and we expect it to be popular. The coming upgrades to the Nonprofit Starter Pack will allow for cash reporting, write-offs of revenue, and facilitate collections of promised payments. Upcoming improvements to Recurring Donations will make it easier to handle recurring donations that are open ended.

If you have questions or comments on our implementation, or have feature requests, please comment on this post.

————-

1. Technically, multi-year grants are received as restricted assets. Each year the revenue is released from restricted net assets to operating net assets as it is needed (credit on the restricted side, debit on the unrestricted side). Another interesting point – multi-year pledges are worth less than cash received today.You have to discount to present value and adjust based on the outstanding amount of the pledge each year. Again, this is something you’ll likely want to handle in your accounting system.

Join our team

Steve — Thu, 14 Apr 2011 15:11:06 +0000

The Salesforce.com Foundation technology team received a compliment the other day when a co-worker said, “Wow, your technology team is atypical.” I’ve been on great teams before in my career, and our team right now is up there as one of the best. I’m looking for a Force.com Developer to join us in our work driving the vision of the Salesforce.com Foundation and helping thousands of nonprofits do the same for their visions. We are small, motivated, we do great work, and we value each other.

If you want to make a difference working with the best tools and the best customers, on a great team, this may be the job for you.

Segmenting Campaigns

Steve — Fri, 15 Oct 2010 13:32:36 +0000

In the run up to the amazing Web of Change conference this year, I was asked to write a think-piece. I ended up writing about being scientific in the design, implementation, and analysis of our work. I called it We Must Be Scientists for Change, and it seemed to resonate with a number of the attendees.

In that article I talked about doing some simple A/B testing. A/B testing is best described as doing some effort while changing one variable in the hopes of learning something about how to affect the outcome of effort. It’s been perfected by the direct mail industry–mailings are run as experiments and each mailing adds to the base of knowledge of how to increase response rats.

As I was writing the article I became dismayed that what I was proposing wasn’t actually very easy to do in Salesforce.com, the system I champion on a daily basis. We use Campaigns for outreach efforts, and while Campaigns are incredibly powerful and easy to work with, randomly breaking them into segments for A/B testing wasn’t easy.

I say “wasn’t” because I have released a tool for A/B testing that is free to users of Salesforce.com, which is listed on the Appexchange under the name Campaign Segmentation Wizard.

Build your list of people to whom you want to reach out, then use the wizard to randomly break them into segments of the exact size you desire. Those segments are Campaigns of their own, and can be used in any way you see fit–mass email, phone banking, etc.

Here’s a short video showing how it works.

If you install it and use it, please rate the app on the Appexchange so others will get a sense if it’s helpful or not.

Textexpander snippets for Apex

Steve — Sat, 14 Aug 2010 14:19:35 +0000

I just upgraded my work computer to Snow Leopard and one of the benefits I was most excited about was being able to update Textexpander, the incredibly handy snippet tool. You create short codes and when you type them they are replaced with pre-recorded text. They’re much better at describing what it does. It’s really handy for email signatures, canned content for technical support–really anything you ever type more than once.

With the new features Textexpander got really interesting for use in coding on the Force.com platform. The Force.com IDE doesn’t have code completion like the in-line code editor does, and it’s something I look forward to Salesforce.com providing. But in the meantime Textexpander is a great solution for helping you with code you write over and over again.

Textexpander now allows you to put variables in your snippets and allows you to fill those variables as you are expanding the snippet. So, for example, when you’re declaring a List of Accounts, you don’t have to type List twice, and Account twice. It’s really slick.

I’ve created a Snippet Group for common Apex syntax. To use the file, install Textexpander. Right click on the link to the Snippet Group and save to your computer. It’s an XML file, but you need to maintain the .textexpander extension on it. Then open up Textexpander and ‘Add Group from File.’ The group will show up in Textexpander.

Right now this Snippet Group includes:

declaration of lists, sets, and maps
declaration of an sObject
for loops, both kinds
if statements
select statements
test methods
try catch block
system.assert statements
describe result for an sObject
describe result for a field

It’s just a start, but if you take it and like it, add to it. Let me know and we’ll expand this Snippet Group to be comprehensive. Clearly there should be a VisualForce Sinppet Group as well. If you create one, please let me know!

Salesforce.com as free, bolt-on analytics engine for any database app

Steve — Wed, 02 Jun 2010 21:47:26 +0000

Over my career I’ve noticed that most applications have very limited reporting and charting features. I’ve tried to write some of my own and realized quickly why this is–analytics is hard! Visual query builders, dynamic charting, aggregation of data, it’s all really tough to do right. I also think most application teams start out with the feature list of business processes that need supporting–recording transactions, editing information, etc. I think they often punt on the analytics engine for these reasons–it’s hard and the value is limited if the app doesn’t even do what it needs to do yet. Because of this, most apps come later, if at all to the analytics game.

And because most of the apps we use have lousy analytics, we often don’t know what we’re missing. In my CRM consulting it was very common for people to under-value the analytics compared to the process streamlining aspects. Getting things done more quickly is important, but analytics can help tell you if you’re doing the right things.

Salesforce.com has a great analytics engine. It’s an amazing blend of efficiency and power. Easy things are in the reach of most users, and hard things are possible without coding. Why are the analytics so good? Salesforce.com is a billion dollar company. They’ve spent amazing amounts of money building their platform, and as part of that, the killer analytics engine. They’ve made it a strategic priority, invested in it, and iterated over 10 years. It really shows.

Great, so Salesforce.com has good analytics. You might think that if you want to use those analytics tools, you need to ditch your app and rewrite the whole thing on Salesforce.com, right? Porting a functioning application is a big project, and while sometimes it might makes sense to do that, a lot of times it doesn’t. You may not have the money to do it. You may be on an open source platform and not want to go to a proprietary one.

But it turns out you don’t need to ditch your app to get Salesforce.com analytics for your data. Using free and open source tools you can bolt the Force.com Free Edition onto your application and very quickly get the power of Salesforce.com analytics for 100 users. For free. I did it myself last weekend. Here’s how it works:

Get your app up and running
Get Force.com Free Edition, or use your existing Salesforce.com organization
Create tables in Salesforce matching the key tables in your app
Create some simple triggers to get all your data relationships right
Set up an extract-transform-load (ETL) server like Jitterbit to pull data from your app and push it to Salesforce.com.
Set up reports and dashboards on that data
Let your data inform the strategic direction of your organization

If you do all this, you can pull data from your application directly into Salesforce.com, automatically updating it as changes are made in your app. Then your end users can get the analytics they can’t get in the app. And your key decision makers, who probably don’t use the app in the first place, can get the top level numbers and trends that help them manage the impact of your organization.

I’ll now go into detail on each of the steps above to show you how it can be done.

Step 1: Get your app up and running

I chose to work with Mifos, an open source application that helps microfinance institutions track their loans and borrowers. Microfinance is a global effort to get working capital in the hands of the poorest people. It’s amazing work being done by organizations all over the world. Mifos happens to be built on Tomcat with a MySQL database. But which app I use really isn’t important. All that matters is that is has extensive functionality for specific business cases, and it has a database we can directly access. If it does these things, it’s a candidate for Salesforce analytics.

I installed Mifos on an Amazon.com EC2 server, which saved me the trouble of trying to get it to run on my Mac. I love EC2!

Step 2: Get Salesforce

I got a free Developer account for this test case, but you could get Salesforce.com donated to your nonprofit, go with the Force.com Free Edition, or purchase Salesforce.com.

Step 3: Create your schema

Creating analogous tables to all the tables in your app is one of the more time-consuming parts of this process. I sped things up by using Model Metrics’s great Cloud Converter tool. I got the field names and one row of values for each table I cared about–you don’t need to get every table, just the ones that figure into your analytics. I created an Excel tab for each table, and pasted the header names and values into each. I then let the Cloud Converter loose on it, and the tables were created in just a few minutes! There might be some cleanup necessary with field types–Cloud Converter guesses what type the field should be, but sometimes it guesses incorrectly. You can do this by hand, or use the metadata API with Eclipse for the fastest action.

All the tables in your app probably have primary keys–some unique Id field that marks each row. In your Salesforce schema, you want to mark the analagous fields are External Ids. This will allow you to use Salesofrce’s Upsert web service method. Without External Ids, you need to know the Salesforce.com record Id in order to Update it. Upsert is incredibly amazing for this use case–it makes it all so easy. Just pass it the primary key from the app and it will find the right record in Salesforce.

The app you’re coming from has relationships between tables (using the primary key fields I just talked about), so you need to recreate those relationships in Salesforce. Cloud Converter might be able to do this for you, but I didn’t try that out. Create your lookup relationships between the objects and you’re good to go.

Step 4: Create your triggers

The ETL server will create your Salesforce records just fine, but it won’t make sure they’re related to the correct parent records for you. To do this you need simple triggers on each object to look at the foreign key from your app find the right Salesforce object, and relate the two. Here’s an example where the Account Payment object looks for the parent Account when it’s inserted or updated. If it finds it, the relationship gets recorded and the Account Payments show up under the Account:

trigger accountPaymentParentfinder on account_payment__c (before insert, before update) {

	Set accountIds = new Set();

	Map accountIdMap = new Map();

	//loop through the trigger set and build a set of all the Account Ids
	for(account_payment__c myAccountPayment : Trigger.new){
		if(myAccountPayment.account_ID__c!=null){
			accountIds.add(myAccountPayment.account_ID__c.intValue());
		}

	}

	//go query for those Account Ids and create a map connecting them with the Salesforce Ids
	for(account__c thisaccount : [select id,account_Id__c from account__c where account_Id__c IN :accountIds]){
		accountIdMap.put(thisaccount.account_Id__c.intValue(),thisaccount.id);
	}

	//put the right Salesforce Id in the lookup relationship
	for(account_payment__c myAccountPayment : Trigger.new){
		if(myAccountPayment.account_ID__c!=null){
			myAccountPayment.account__c = accountIdMap.get(myAccountPayment.account_ID__c.intValue());
		}
	}
}

You need to do this for each object. If an object has more than one lookup relationship, you’ll need to create the Set and Map structure for each. They all follow the same pattern. Easy peasy.

Step 5: Set up your ETL server and transformations

I chose Jitterbit for my ETL server. They have a free Community edition but I used a 30 day trial of their Enterprise edition, only because there was a machine image on Amazon.com EC2 for the enterprise version. Installation was a 10 minute affair.

The Jitterbit client is where you create the operations that pull data from the source and get it where you want it to go. I created an operation to log in to Salesforce.com and store my session Id. Then you pretty much create one operation for each table in your app, grabbing the data and passing it to Salesforce.com’s Upsert web service method. This will try to update a record that exists with that External Id. If it can’t find the record, it will create one. Brilliant.

It’s a ton of drag-and-drop mapping–this app field maps to this field on the Salesforce object. But once you get the hang of it, you’ll crank through all your tables.

When your operations are set up you run them, starting with the login, until all your data comes over. These operations can be scheduled to run as often as makes sense to you. You can pull over only data modified since you last pulled. I created a very simple data flow–one way from my app to Salesforce.com. But you can really do just about anything. You can send data back to your app. You could pull from 25 different apps all to Salesforce. It’s up to you.

Step 6: Set up your reports and dashboards

Once your data is in Salesforce.com and related correctly, start creating your reports and dashboards. What I find is that when I create a dashboard the next one immediately comes to mind. Loan default rate over time. But does marital status have an impact on that? What about number of children the borrow has? And what are the patterns for defaults? Do loans tend to default more frequently during the dry season? In the months before harvest? Do non-agriculture loans behave differently? People who work at microfinance institutions ask themselves these questions. They see patterns and want the data to confirm or challenge their assumptions. Because Salesforce.com makes analytics easy, users can ask these questions and get immediate answers. Dashboards can even be sent to them via email every week.

Then step back and take a look at your analytics. Here are some I created with a sample data set in my app:

I was very pleased with the story I am just starting to tell about the loan programs at this pretend microfinance institution. I think the take away is this: Salesforce.com can add value by helping you be creative in telling the story of your data. It’s a story that might be hard for you to tell right now. But with very little cost other than time and technical ability, you can add flexible, user-driven analytics to any database application by following this recipe.

You can add this power to your app. But the really amazing part is how easy it is to share this kind of setup. Once you create a schema that matches Mifos or OpenMRS or CiviCRM you can package that up in Salesforce and share it with anyone. Just a couple clicks and they can install all the objects, triggers, and dashboards for that app. Jitterbit operations can be shared as well. You export them as a “jitterpak” and anyone can use them with their setup. Just change the login information, point to your Salesforce.com web services and it should work without changes.

And perhaps the most important thing is that you’re not embedding Salesforce.com into your app. You’re not requiring that everyone using the app use Salesforce.com. I hop this example shows that Salesforce.com can be “bolted-on”, adding value along side your mission-critical application. The cost can be very low, the impact can be high, and you can do it without making big decisions about app architecture direction.

Salesforce sending SMS through FrontlineSMS

Steve — Thu, 27 May 2010 14:13:07 +0000

FrontlineSMS is an open source application used primarily in the developing world for communicating with large numbers of cell phone users. It’s a locally installed application that pushes SMS messages out through your tethered cell phone. It’s a really cool app with all sorts of great real-world usage. My friend Dale Zak just built an awesome reminders module for it, and that got me looking at it again.

The newest version of FrontlineSMS (1.6) has a very simple API for sending SMS messages. I have been successful in getting Salesforce.com to use this API to send SMS messages to single Contacts and to Leads and Contacts who are members of a Campaign. Here’s a short video of it in action:

Here’s what’s going on in the one-off send:

I’m using Visualforce to create UI that is called by the Send SMS buttons
The Visualforce page accepts the SMS text input
Clicking send shows an iFrame that calls the FrontlineSMS API correctly: http://localhost:/sms_number/sms_message
A Task is related to the Contact with the data and content of the SMS message

Why use the iFrame? Since FrontlineSMS is locally installed, we have to communicate with it from the browser. A more robust option would be to create Javascript that makes the localhost calls and listens for the success or failure and proceeds accordingly.

To all the members of a Campaign, we do the following:

The Visualforce page accepts the SMS text input
Clicking Send exposes an Action Poller, which calls code every 5 seconds
When the Action Poller calls code, 10 Campaign Members of the correct Status are queried
10 iFrames are populated with the FrontlineSMS API URLs for the messages
The Campaign Member records have their Status changed so they won’t be queried again
Tasks are related to the Campaign and the Contact or Lead

Here are the Salesforce code bits.

Visualforce page for one-off sends:


	
		
			
				Send an SMS using FrontlineSMS:
				
					Install FrontlineSMS on your computer
					Make sure FrontlineSMS is running
					Make sure your phone is connected to FrontlineSMS
				

			

		
		
		
			
				
				
			
			
				 

			
		
		
		
		
	


Apex controller for one-off sends:
public with sharing class extSendSMS {
	public Task task {get;set;}
	public String endpoint {get;set;}
	public Boolean showFrontlineSMSiframe {get;set;}
	private Contact contact;
	private Lead lead;
	public extSendSMS(ApexPages.StandardController stdController) {
		this.contact = (Contact)stdController.getRecord();
		this.contact = [select id, MobilePhone from Contact where Id=:contact.id];
		this.task = new Task();
		this.task.WhoId = contact.Id;
		this.task.type = 'SMS';
		this.task.ActivityDate = Date.Today();

		this.task.status = 'Completed';
		showFrontlineSMSiframe = false;
    }
    public PageReference sendSMS(){
    	this.task.subject = 'SMS: ' + this.task.Description;
    	insert task;
    	String strippedMobilePhone = '';
    	strippedMobilePhone = this.contact.mobilePhone;
    	strippedMobilePhone = strippedMobilePhone.replaceAll('[^0-9]', '');

    	endpoint = 'http://localhost:8565/'+ strippedMobilePhone +'/'+ this.task.Description;
    	showFrontlineSMSiframe = true;
    	return null;
    }
}

Visualforce page for Campaign sends:


		
			
				Send an SMS using FrontlineSMS:
				
					Install FrontlineSMS on your computer
					Make sure FrontlineSMS is running
					Make sure your phone is connected to FrontlineSMS
				

			

		
		
		
			
				Member Count
				Number Sent
				

			
			
				SMS 1 (debug)
				SMS 2 (debug)
				SMS 3 (debug)
				SMS 4 (debug)
				SMS 5 (debug)
				SMS 6 (debug)
				SMS 7 (debug)
				SMS 8 (debug)
				SMS 9 (debug)
				SMS 10 (debug)
			
			
				
			
		
		
			
		
		
			
				SMS 1 (debug)
				
				SMS 2 (debug)
				
				SMS 3 (debug)
				
				SMS 4 (debug)
				
				SMS 5 (debug)
				
				SMS 6 (debug)
				
				SMS 7 (debug)
				
				SMS 8 (debug)
				
				SMS 9 (debug)
				
				SMS 10 (debug)
				
			
		
	


Apex controller for campaign sends:
public with sharing class extSendSMSCampaign {
	public Campaign campaign {get;set;}
	public Task dummyTask {get;set;}
	public String SMSmessage {get;set;}
	public String endpoint1 {get;set;}
	public String endpoint2 {get;set;}
	public String endpoint3 {get;set;}
	public String endpoint4 {get;set;}
	public String endpoint5 {get;set;}
	public String endpoint6 {get;set;}
	public String endpoint7 {get;set;}
	public String endpoint8 {get;set;}
	public String endpoint9 {get;set;}
	public String endpoint10 {get;set;}
	public Integer memberCount {get;set;}
	public Integer numberSent {get;set;}
	private List endpoints = new List();
	private List SMSTasks = new List();
	private Id whoId;
	public Boolean showActionBlock {get;set;}
	public Boolean showFrontlineSMSiframe {get;set;}
	private Contact contact;
	private Lead lead;
	private CampaignMember campaignMember;

	public extSendSMSCampaign(ApexPages.StandardController stdController) {
		this.campaign = (campaign)stdController.getRecord();
		memberCount = [select count() from CampaignMember where CampaignId=:this.campaign.id AND status='sent' and (Contact.MobilePhone <> null OR Lead.MobilePhone <> null)];
		showFrontlineSMSiframe = false;
		showActionBlock=false;
		SMSmessage = 'test message';
		numberSent =0;
		dummyTask = new Task();
    }

    public PageReference sendSMS(){
    	showActionBlock = true;
    	showFrontlineSMSiframe = true;
    	return null;
    }

     public PageReference sendSMSToMembers(){
     	endpoints = new List();
     	endpoint1 = '';
		endpoint2 = '';
		endpoint3 = '';
		endpoint4 = '';
		endpoint5 = '';
		endpoint6 = '';
		endpoint7 = '';
		endpoint8 = '';
		endpoint9 = '';
		endpoint10 = '';
		SMSTasks = new List();
    	List myCampaignMembers = new List();
    	myCampaignMembers = [select id, Contact.MobilePhone,Contact.Id,Lead.Id, Lead.MobilePhone, status from CampaignMember where CampaignId=:this.campaign.id AND status='sent' and (Contact.MobilePhone <> null OR Lead.MobilePhone <> null) limit 10];
		if(myCampaignMembers.size()>0){
	    	for(Integer i=0;i0){
	    		While(endpoints.size()<10){
	    			endpoints.add('');
	    		}

		    	endpoint1 = endpoints[0];
				endpoint2 = endpoints[1];
				endpoint3 = endpoints[2];
				endpoint4 = endpoints[3];
				endpoint5 = endpoints[4];
				endpoint6 = endpoints[5];
				endpoint7 = endpoints[6];
				endpoint8 = endpoints[7];
				endpoint9 = endpoints[8];
				endpoint10 = endpoints[9];
	    	}
	    	for(CampaignMember myMember : myCampaignMembers){
	    		myMember.status='Responded';
	    	}
	    	update myCampaignMembers;
	    	insert SMSTasks;
		} else {
			showActionBlock = false;
		}
		return null;
    }

}

Strategic impact and making multi-level relationships look nice

Steve — Wed, 05 May 2010 21:03:22 +0000

I’ve been doing a little prototyping in Salesforce.com as a volunteer project for a nonprofit in town. They’ve got an interesting need to track their strategic plans in Salesforce. I’ve seen this kind of thing built many times and have built it myself for another org or two. For this org they’ve got 3 levels of custom objects to hold their data. Driver is their high-level strategic focus. Goal is the next level down–there can be many goals for each Driver. And Metrics our measurable things related to each Goal.

Salesforce lets you create these objects and relationships between them very easily. I created the schema in just a few minutes. I created three objects and related them together–in this case I made them master-detail relationships. You can see in the diagram what my schema ended up looking like.

Now tracking your strategic goals is great, and most nonprofits do that. But where I think it gets more interesting is when we can tie the actual work we do directly to the metrics we’re trying to deliver on. So you’ll see in the diagram that there is a 4th object called project. Project is used to track all the work efforts of the org that are worth recording. I created a lookup relationship from Project to Metric so every project this groups takes on can be explicitly related to a Metric we need to deliver on. Which is in turn related to a Goal, which is related to a Driver. So, why are you updating that website for the 100th time this year? Because the website Project is meant to deliver on the Metric of increasing engagement of our supporters 25%, which is part of a Goal to grow the direct impact our supporters have in the world, which in turn feeds our Driver which calls for us to lead the world with a model of catalytic impact.

Those strategic objectives are made up for this example, but you get the idea how daily work can roll up to why your organization exists. Seeing that direct relationship can be very powerful. So when you look at the Project record in Salesforce, what do you see? Because there is only a relationship to the Metric object, you only see the Metric on the page layout.

Because the Project isn’t directly related to Goal or Driver, we can’t have lookup fields to those objects. Lookups are only for direct relationships, from child to parent, not up to grandparent and beyond. So we need another solution, and it turns out to be formula fields. On the Project I can create a Goal field and a Driver field that are formula fields of type Text. Here’s the formula for each of them:

for Goal: HYPERLINK("/" + Metric__r.Goal__r.Id , Metric__r.Goal__r.Name,"_self" )
for Driver: HYPERLINK( "/" + Metric__r.Goal__r.Driver__r.Id , Metric__r.Goal__r.Driver__r.Name,"_self" )

We’re creating a hyperlink to fake a real lookup. The URL of the hyperlink is relative, so it starts with / rather than http://. It then has the Id of the object, which we get by traversing up the relationships in Salesforce. From project we follow the Metric__r relationship to the Metric object, then up the Goal__r relationship to the Goal where we can grab any fields we want. With Driver we do the same thing, just go up one more level. If you think this looks hard, don’t worry, the formula field editor is really easy to use and does all the hard work for you–you just click the relationship you want to traverse.

The text of the link is the Name of the object in question. And then we target the hyperlink to “_self” so that it will load the record in question into the current window–just like a regular lookup would.

After adding these formula fields to the page layout, the end result is this:

Now we’re telling the full story about this project with a little help from simple formula fields.

Medical Records for Gitwe

Steve — Thu, 18 Mar 2010 20:37:30 +0000

My trip to Rwanda was amazing. This first post is going to be about the volunteer project I was a part of. I’ll write more later about Rwanda and the people. There is so much to say…

First of all, our project team fully delivered on all we set out to do. While success was in doubt up until the last minute (why do I work in technology?) we pulled it out at the 11th hour. Literally–11pm the night before we left. I look at what we did and we really nailed every aspect. The hardware we brought is high-quality and well configured. We got all the server software running in the configuration required. The electrical infrastructure is sound and protects the hardware. And we documented the systems very well.

It was really interesting going to Rwanda, such an amazingly different place from where I live, and then spending a lot of time working with technology. Every day felt like two days. There was the experiential part–meeting people, taking in the bustle and beauty, and eating amazing food. And then there was the volunteer work. Every day we were focused on moving toward project success. It made for a trip that went by quickly, but at the same time seemed to be a month long.

And I wouldn’t do it differently. I highly recommend going to Rwanda and Kenya. And I really recommend going there with good work to do. Volunteer. Help out. Contribute to the country while you experience it. You’ll get more out of your time there. You will spend more time with Rwandans and Kenyans. You will connect deeper with the place and the people then you would as a tourist. When I go back to Rwanda, I will be going with some good work to do. Maybe technology related, maybe not. But this kind of travel really resonated with me.

Here’s a quick recap of the project and why I was there:

Medical Missions for Children sends doctors to the hospital in a town called Gitwe a couple times a year. These doctors volunteer their time and perform surgeries on kids and adults. Things like repairing cleft pallets and resectioning goiters. Surgeries that are common and easy in more wealthy countries, but just don’t happen in poorer places. These cosmetic surgeries can be absolutely life changing–much like the impact of homeless people getting free dentures in San Francisco. It turns out that these kinds of procedures can change people’s lives–giving them confidence they’ve lacked for years because of their limitations. The freedom to smile, and not feel self-conscious, re-connects people with society and their families in profound ways. These cosmetic procedures can be truly life-changing.

Lucky Gunasekara was the project lead and he assembled the team–me, Jordan Smock, and the incomparable Canadian, Dale Zak. I didn’t know any of these guys going into the trip, and I came away with real friends I know I’ll stay in touch with.

Our task on this trip was to install a computerized medical records system that could be used by Medical Missions for Children to record the patients they worked with. When you’re performing surgery, it’s really important to know the patient’s medical history so that you don’t inadvertently harm them with drugs they are alergic to, for example. Phase one of this project was to get the system in place and have MMFC use it after we left. Phase two is for Gitwe Hospital to use the medical records system more broadly–allowing for better care for the 300,000 people who turn to the hospital.

Gitwe Hospital is owned and operated by the wonderful Urayeneza Gerard. He was our gracious host during our time there. Everything we requested to get the project done–server room with a padlock, upgrade to the electrical system, curtains for the windows–was gotten on short order.

Because of limited prep time for the trip, we purchased the hardware in the US and carried it on the plane with us. 2 Netbooks, 2 small desktops, a server, a backup power supply (UPS) and a million cables, surge protectors and other miscellany. Surprisingly, everything made it to our destination safely, and worked when we unpacked it. We did the unpacking in Kigali, where we were more confident we would have reliable power and Internet access. One of our hotel rooms turned into a makeshift server room as we built up the hardware, the network, and the software.

The biggest issue we ran into while unpacking things was power. Rwandan power turned out to be reliable and clean, but it comes out of the wall at ~250V. The power supplies in all of our devices were rated to 240V, save the most important one, the UPS. Luckily that required an awesome day of walking around the commercial district searching for a solution. We found one with the amazing folks at Bricotech. They sold us a voltage regulator which would serve the dual purpose of stepping the voltage down to 110V and protecting our equipment against power fluctuations. They also put a British plug end on our UPS, solving our other issue.

We were now ready to leave the big city for the rural outpost of Gitwe. We packed all our gear and made the 2+ hour drive south to the hospital, stopping along the way for a Mutzig in the van.

Gitwe is an amazing little spot. It’s not really a town, more of a collection of shops and homes. The main centers of activity are the Hospital and Esapac, a technical school with about 1000 students. So while it was a tiny little place, it bustled with activity of people coming and going.

Over the course of five days we took an empty room at the hospital and transformed it into the Gitwe Hospital server room. Here are the before and after pics:

We worked side by side with the IT staff at the hospital–Innocent and Charles, setting up furniture, hardware and software. The technology we brought in is somewhat new to these folks. They haven’t used the medical records system before, and they need to come up to speed on Linux systems. We’re hoping to get them involved in an intensive nine-month training course offered by the Rwandan government to train folks to work with medical records systems. It’s a plumb placement, and a great opportunity if it comes through.

OpenMRS was our steepest learning curve in this project. We ended up running up against a problem with a bad install file posted to their website. Things just weren’t working for the first 3 days of our stay. We tried every angle we could think of, and then used our cellphone modem Internet access to throw a hail mary out to Dave Thomas, who works at the other end of Rwanda for Partners in Health. He saved our bacon. Completely. With his help, we were able to get the system functioning on our last day, and then spent the rest of the day and night configuring it for the special needs of MMFC. At midnight we headed back to our rooms for a beer, a bit of whiskey and Coke, with a palpable sense of relief and accomplishment.

The next morning we had breakfast with Gerard and his wife Justine, like we did each day in Gitwe. After breakfast Gerard said a prayer for our travels and really got us choked up as we realized how important this contribution is to him. He’s doing amazing things for Gitwe with the school and the hospital. He is by far the largest employer in the area, with the hospital alone having 1,500 employees. And he has no plans to slow down–Gitwe will likely be the home of the second medical school in Rwanda. I can’t wait for that to happen!

Now that our work was done, we could enjoy a little tourism. But, Lucky, Dale and I aren’t your average tourists. What we like to see are real people, and amazing good work. So, naturally, we headed up to Rwinkwavu to get a tour of the Partners in Health operation. It was the most amazing download of information I’ve had in a while. Hearing about the innovative things they are doing to ensure the health of the poor in northeastern Rwanda was nothing short of amazing and inspiring. PIH is my favorite nonprofit, and I highly recommend reading Mountains Beyond Mountains if you want to learn more about how comprehensive healthcare can be provided to people with no money. Thanks to our hosts Cheryl and Dave, we had plenty to think about on the long drive to Kigali.

I can’t say enough about the experience of working side-by-side with great folks in an amazing setting. It’s a great feeling to visit a place and leave behind something of value that can be built on. I hope to go back and contribute some of that building. I’d love to have more time to focus on knowledge transfer and skill building with Charles and Innocent and whomever is interested. This trip felt like a first step into a longer relationship. I hope that’s the case and that Gitwe moves forward as fast as we all want. There are governmental plans to bring fiber optic Internet to all the district hospitals in the next year or so. Gitwe could be transformed in short order if that’s the case. I’d love to witness it first hand!

An Introduction to Exception Handling in Apex

Steve — Tue, 12 Jan 2010 17:48:41 +0000

I was privileged to get to write an article for DeveloperForce.com on exception handling in Apex. I wrote this article not from the perspective of an expert on the subject, but as someone who really wanted to learn more about my options for using exception handling in my Apex code.

I’ve always had a nagging feeling that I wasn’t following best practices in my exception handling in Apex. In most cases I wasn’t doing any exception handling at all. I decided to write up what I have learned about error handling on the Force.com platform so that others could jump into it full-bore, and make their programs more robust and fault tolerant.

I hope it’s helpful to Apex programmers out there. Let me know what you think!

I’m going to Rwanda

Steve — Wed, 30 Dec 2009 04:50:56 +0000

Today I got confirmation of some great news–in February I’ll be going to Rwanda for a week to help install an open source medical records system at a rural health clinic! I’ll be going with Lucky Gunasekara and meeting with Partners in Health.

I’m really excited to work with Lucky! This project will be amazing, and Lucky has a longer-term vision. He wants to answer the question: does cloud computing have a role in health systems in rural Africa? He’s planning some really interesting efforts in Kenya later this year. In time, I think Salesforce.com can be a boon in rural Africa, and I’m really interested to start the work to figure out if that time is now, soon, or farther down the road. I see this trip as a great first step on that path.

When I started working with Salesforce.com five years ago, I felt part of my role was to go down the path of trying to deeply customize the platform for nonprofits, and then to report on that experience, warts and all. I really enjoyed that work, and I hope to do similar work and storytelling around Salesforce.com in parts of the world where people assume the cloud can’t work.

But most of all, I’m really excited to have all my assumptions and expectations blown out of the water! I can’t wait to walk the roads, meet folks, and most of all listen and learn. I will be arriving with no answers, and I don’t expect to leave with any. For me, it’s all about getting to the right questions. There will be so much to take in, to start orienting myself to this new set of challenges.

Only just a week ago a friend pointed me to this piece by David Brancaccio on Partners In Health’s work in Rwanda. I was floored by the outcomes they are getting, and the thoughtful design of the community health program. I recommend watching it–it’s amazing.

So many times people look to technology as a savior. That never works in my estimation–human systems are how problems are solved. Technology can augment and transform those solutions, but it isn’t the answer. I’m incredibly excited by what’s already working in Rwanda, and am fired up to start thinking about how technology can help extend that impact.

I watched this video and emailed the link to a friend of mine with the message, “this is the work I want to do with my life–helping people build community-based systems that really work.” Four days later I got an email from Lucky inviting me to Rwanda, to the very region where that video was filmed. Serendipity is a fabulous thing!

Ahh! I’m going to Rwanda! I still can’t really believe it. It all feels so fast and so amazingly exciting. Of course I’ll be writing about the experience, as well as taking tons of pictures and videos. So much to do to prepare!

A great job opportunity

Steve — Fri, 11 Dec 2009 15:37:56 +0000

Groundwire is an organization near and dear to my heart. I spent many wonderful years there back when it went by the name ONE/Northwest. My Salesforce-related career got it’s start there. Some of my most cherished relationships began there. And I was given the space and encouragement to grow exponentially as a person, technologist, and agent of change. I look back on those years very fondly–the work, the nonprofits we worked with, but most importantly the people.

Groundwire is looking for a top-notch CRM Consultant. Opportunities to join this amazing team are rare. If you are at all interested in using your Salesforce.com skills to make a difference in this world, you should follow up with Groundwire and make sure you don’t miss this chance.

Add a Donor Status Funnel to the Nonprofit Starter Pack

Steve — Wed, 09 Dec 2009 16:18:42 +0000

The vision of the Nonprofit Starter Pack has always been that it would be a starting place for nonprofits. It’s not a “application” so much as it’s a “platform.” We’ve tried to architect it in a way that gives some immediate benefit, while not precluding the change and extension that I feel is necessary for successful use. In that spirit, I want to show how to add some donor segmentation you might find interesting if you’re using the One-to-one Account model.

The image on the right is from a Dashboard showing all Contacts in an instance with the Nonprofit Starter Pack installed. All Contacts have been categorized by something called “Donor Status.” We’re looking at their giving and putting them in one of four categories–never a donor, a donor previous to last year, a donor last year, or a donor this year. Here’s how I created it.

First, we need to have 2 rollup summary fields on Account that calculate the Opportunity values over this year and last year. You could also add a third rollup to get the value from two years back:

Total Giving Year To Date – (Won EQUALS true) AND (Close Date GREATER THAN 12/31/2008) AND (Close Date LESS THAN 1/1/2010)
Total Giving Last Year – (Won EQUALS true) AND (Close Date GREATER THAN 12/31/2007) AND (Close Date LESS THAN 1/1/2009)
Total Giving 2 Years Previous – (Won EQUALS true) AND (Close Date GREATER THAN 12/31/2006) AND (Close Date LESS THAN 1/1/2008)

These dates need to be hard-coded for the rollup summaries to work. On Jan 1, you’ll need to add a year to all the dates. Don’t worry, all the rollups will then recalculate for you.

Now you want to show these Account fields on the Contact. Create three formulas that just show the Account field value:

YTD Giving Total – Account.Total_Giving_Year_To_Date__c
Last Year Giving Total – Account.Total_Giving_Last_Year__c
2 Years Previous Giving Total – Account.Total_Giving_2_Years_Previous__c

Once you have these summary values, you can use them in another Formula, our Donor Status formula:

IF( npe01__Lifetime_Giving_History_Amount__c >0, IF( YTD_Giving_Total__c =0, IF( Previous_Year_Giving_Total__c =0, "2. SYBUNT" , "3. LYBUNT") , "4. Current Donor") , "1. Not Donor")

Note that the npe01__Lifetime_Giving_History_Amount__c field is included in the Nonprofit Starter Pack. The others are fields you just created, so make sure the names match.

Now that you’ve got the formula field built, create a Contact and Organizations report that takes all Contacts and groups by Donor Status. Variations on this report can easily be used to send a letter to everyone who gave in the past but not this year. Once you save this report, you can build a funnel dashboard based on it and you’re done! You’ve now segmented your donors based on when they last gave.

My Nonprofit Starter Pack Session from Dreamforce 2009

Steve — Sun, 29 Nov 2009 01:10:27 +0000

Getting the Most of of the Nonprofit Starter Pack. We cover 3 main things:

Configuring the Starter Pack
Importing Contacts via the wizard
Upgrading a package

Feel free to fast forward through the first 4 minutes, where we’re getting 110 people logged into their orgs…