Geez, what a nasty thing. I implemented Omni-Channel lately to allow for a very limited number of staff skim through a huge heap of records. Omni Channel is a huge feature for this task: You can define queues for different objects, assign queues to channel, define how many items each agent can handle at a time, distribute work among agents that have capacity and so on.
Now, if something stops working abruptly on the Salesforce platform, anyone should know what happened, but I was looking for the less obvious reasons anyway. So, here’s the note to myself, and all others who have been failed by Omni-Channel all of a sudden:
- Omni-Channel has an own set of limits, and these strictly enforced limits. 10,000 items can be simultaneously pending, and 5,000 items can be routed per hour. Numbers vary by edition, but not really: Professional, Enterprise, Unlimited and Performance have these limits, and the feature is not available for Personal, Group, and Contact Manager editions. That’s it. Therefore: First point to check for all Omni-Channel Mishaps is the limit consumption.
With a certain routine in Salesforce certification (I hold 12 currently, including all four consultant certs), I have to admit that my latest addition, Certified Marketing Cloud Consultant, was indeed one that I seriously struggled with. So – first time ever – I decided to have a blog post on that one. Maybe someone will find it helpful.
Continue reading “Getting the Marketing Cloud Consultant exam in the books…”
Quite regularly I happen to meet the challenge of building something on the Force.com platform that is not exactly a CRM application. Exposing a public site as a storefront and integrating payment into it is quite that kind of app. We decided to use Stripe as a payment provider – its handling fees are moderate and it’s an API-first platform, using RESTful webservices and JSON objects for all communication. It’s doesn’t take a lot of knowledge about platforms to realize that anything that speaks JSON via HTTPS is a good choice to build things that seamlessly integrate.
And it gets even better: Cirruspath open-sourced an Apex-Library named “stripeforce” on github, so there’s even as foundation to build upon. Continue reading “Getting started with Stripe payments”