When I was just learning Salesforce and starting my career, the company I worked for at the time often tasked me with the exciting and highly sought after role of writing test scripts and performing Quality Assurance testing. It turned out I had a knack for it. First and foremost, because as I was new to Salesforce, I excelled at blundering my way through the system breaking everything imaginable as I went. Picture me as a hurricane of user errors, wreaking havoc on even the simplest of test scenarios. The second more important reason I excelled at QA, was because when I wasn’t breaking things on accident, I tried to break them on purpose.
For many years, Bellingham Food Bank used a legacy Access database called “The Food Bank Intake Database” to track client intake information for the 300-600 households who use their services each day they’re open. This software allowed them to collect data for analysis of the services they provided to their clients, and to produce the monthly statistical reports required by various funders.
As time passed, and as the organization upgraded their various systems, the Access database did not upgrade along with it. The staff at Bellingham Food Bank recognized the mission critical nature of the database, and began to make plans to replace the aging system once it started to crash regularly. In order to process a household every 30-60 seconds, the team needed a system they could depend on.
The Bellingham Food Bank engaged DaizyLogik to design and develop a client intake application that leverages the features of Salesforce…
View original post 20 more words