In the previous post , we set the objective of cleaning up open tasks either when (1) the opportunity to which they are related is closed or (2) another task with many of the same attributes is created. We created an auto-launched flow which determined which of those two flavors was in play, captured the appropriate tasks and, if there were any, deleted those tasks. What we didn't do last time was launch that flow. That's the exercise now. We'll create two Process Builder flows which invoke the flow, setting the appropriate input variables. Recall there are two instances in which we're going to launch our flow. The first, and more complex, is when a task is created. If a task is created, it relates to an opportunity and its status is Not Started, I'm going to launch the flow. Let's get started... From Setup, search on Process Builder, then click on it and then New. Give the process a name, and have it start when a record changes. Next, Add Object and sele...

It seems fairly standard practice to create reminder tasks to nudge reps about neglected opportunities. We do that for open opps that haven't been modified for 30 days, and for renewal opps when they get within 90 days of the renewal date. Do your reps always take action? Yeah, mine don't either. My concern is that these reminders become noise. The few new alerts get crowded out (attention-wise) by all the alerts that have been sitting around neglected. The net is that reps learn to ignore these alerts, and they become pointless. What to do? One step I've taken is to automate cleanup of certain old tasks. This post and the next will walk through the steps I've taken. My aim is to (1) delete any 'Not Started' tasks associated with opportunities when the opportunities get closed, and (2) delete any duplicate reminder tasks on a given opportunity when creating a new such task. To do this, I'm going to create a flow which, given an opportunity id, will de...

Our Salesforce org doesn't allow reps to enter a unit sales price directly. Rather, reps can only apply a discount to the list price. There are some solid reasons for this, most notably that we want to know what discounts are being applied, and greater discounts may require different approvals (higher discounts might go all the way to the CFO and CEO for approval). But a couple of problems result from this restriction: 1) Sometimes a rep may want to sell (or at least quote) above list price, and Salesforce doesn't allow a negative discount. 2) The discount percent allows just two decimal places, so we can't always get to exactly the price we want (try discounting from $350 to $200 !). 3) Even when it is possible to discount to the exact price, the calculation isn't always easy for my reps. So we often had prices in the CRM that didn't match what the rep had expressed to the prospect. Or maybe I would get a call to adjust the pricing. My workaround: A flow!...