877.703.4488 info@cloudmybiz.com
Tip of the Week – Use monitoring to troubleshoot Workflows in Salesforce

Tip of the Week – Use monitoring to troubleshoot Workflows in Salesforce

Frustration at its finest

If you’ve been using Salesforce for a while now, you probably have built dozens of Workflow rules to streamline your processes and help your team accomplish more every day thanks to powerful and easy to build automations. Occasionally, you’ve probably come across that pesky rule that just won’t work the way you intended, and you may have been able to problem solve thanks to the video we shared with you a couple years ago. But if you’ve got time-based workflow rules, sometimes you need another tool in your arsenal to resolve issues, and I’d like to point you to one you may not know about.

Because time-based workflow rules don’t act immediately, they can be difficult to troubleshoot. You’d normally have to wait until the scheduled time before you see them acting as intended. Well, Salesforce offers a tool out of the box to help you monitor when time-based workflows have been triggered and are scheduled. This will let you see important information, assisting you in confirming everything is in order. All you have to do is go to Setup -> Monitor -> Time-Based Workflow, or type Time-Based Workflow into the Quickfind. Click Search to see all pending actions, or add filters to drill down to exactly what you’re looking for. For more information, check out Salesforce’s help doc, and good luck with your latest automations!

-Jared and the Salesforce Guys

Tip of the Week – A bit.ly integration for Salesforce all from one tweet

Tip of the Week – A bit.ly integration for Salesforce all from one tweet

I know I rave about the Salesforce community. A lot. And for very good reason. A few weeks ago, I was asked if you could send shortened URLs from Salesforce. Sending them wasn’t the problem – there’s dozens of approaches there. But I didn’t quite have a solution for generating those links. I knew my team could figure it out quickly, but it was after-hours when the question came in and I wanted an answer fast. I turned to Twitter, and within a few minutes, I had several approaches lined up and could definitively say it was possible. The next morning, I awoke to an incredible blog post by Doug Ayers, who took my question as a challenge and stayed up late writing the code.

In short, his solution is brilliantly simple. First, you sign up for a free bit.ly account. In Salesforce, create a “Named Credential” (a tool designed for storing login credentials and endpoint URLs for integrations; Setup -> Security Controls -> Named Credential), then a Custom Field to hold your shortened URL. Next, copy and paste his Apex code – yeah, it’s ready to fly and very well-commented. Finally, use the Process Builder to create a Process, activate it, and test it out. Due to some known limitations with the Process Builder (if you need to do this in bulk, you could hit some problems), my team needed to swap that out for a Trigger, and a few other modifications were needed to make it fit into the process flow, but the hardest part was solved with just one tweet and the incredible #askforce community! Check out Doug’s post here, and enjoy this awesome solution!

-Jared and the Salesforce Guys
Cover image by Joelle Diane

Dreamforce Sock Update:

Dreamforce Socks

The socks are done! They look awesome, and feel even more incredible! I think I’ll be knitting another pair of Dreamforce socks next year, and I definitely plan on strolling around the convention in these!

App of the Week – Salesforce connects to the world with the Salesforce IFTTT Channel

App of the Week – Salesforce connects to the world with the Salesforce IFTTT Channel

Salesforce IFTTT

You may have read our post a while back about the Salesforce Chatter Channel for IFTTT (“if this then that), a free IoT (that’s “Internet of Things”) integration tool that lets you automatically trigger actions across internet-connected services and devices based on events – in example, I love that whenever I update my Facebook profile picture, Twitter is updated automatically too! Well, back in April 2014, the Salesforce Channel was pretty limited. All you could do was create triggers to post to Chatter. Well, it’s a whole lot more powerful than that now!

With the Salesforce IFTTT channel you can easily create integrations between Salesforce and your favorite apps. Turn on a Hue light when an opportunity is won. Post on Chatter when someone tweets a specific hashtag.

Check out the AppExchange listing for Salesforce IFTTT, or dive right in and check out some of the awesome Salesforce recipes like posting escalated Cases to Slack or tracking your FitBit data in Salesforce today!

Tip of the Week – Don’t pass over the Process Builder in Salesforce

Tip of the Week – Don’t pass over the Process Builder in Salesforce

Over the last few months, I’ve been putting off an update I wanted to make in my developer org which required updating all child records when a specific change was made on the parent – think changing Account Status to “Closed” and wanting all Cases to be closed. Normally, I’d be plotting out the logic, writing a trigger, test class, test scenarios, testing it out, reworking, and it would take hours of painstaking work.  And if they wanted to make any small changes, its back to the drawing board with more Apex, more testing, more rework, etc. But now that the Process Builder is generally available, I decided to take a different route.

Using the Process Builder, I created a new process called “Close Cases when Account is Closed” and added a description to quickly highlight the logic. I set the main object to the parent, or the Account. The logic was: every time the record was created or edited, if the Account Status was “Closed”, and only when this field was actively changed. Next, I added an immediate action to update records, selected Cases__r from the list of fields/objects available, selected the Status field, and chose the value of Closed. After I reviewed and confirmed the logic, I activated the Process and tested it. Worked like a dream, and took less than half the time a trigger would have taken to develop and test. And the best part is that if anything needs to be changed in this process going forward, it can be updated quickly with clicks, not code!

-Jared and the Salesforce Guys