It finally happened: Winter 23 is here. You cannot create new workflow rules (WFRs) anymore.
Migrate to flow functionality is GA (Generally Available).🔥 Before I get into the details of this topic, let me tell you that all my courses are on a huge sale. Check below. 🔥What do you do now? Use this, and a couple of clicks later, your Org will be all on flow? Not so fast.
Let’s review the facts here.
Workflow rules support:
- 🔁 Field Updates
- 📧 Email Alerts
- ☑️ Task Creation
- 🕊 Outbound Messages
You can do all these things with flow.
First, review all the WFRs you have in our Org. Main parameters to look at (make a table out of this): 💡
- Object (Opportunity)
- Trigger (On Create)
- Criteria (When Close Date <= Today + 30)
- Action (Email Alert)
Why can’t you just use migrate-to-flow and migrate everything? The limitations are: 😰
- Does not support tasks
- Does not support long text fields in the criteria
- Does not support cross-object reference in the criteria
- Migrates one WFR to one Flow
- Does not facilitate renaming/relabeling the flow (same name – renaming manual)
There are several approach alternatives you need to consider:
1️⃣ Custom Development: Analyze and design & build everything
2️⃣ Use migrate to flow when it works: One-to-one migration
3️⃣ Try to create one flow for most WFRs: Major work & Maintenance nightmare
4️⃣ Hybrid: Design your own strategy combining the methods above
I looked at all these factors and come up with a set of recommendations. I reviewed the recommendations in a Salesforce Saturday meeting with the awesome Salesforce ecosystem friends this past weekend. Here is a few of them:
- Use migrate to flow for Email Alerts. Rename flows to follow a convention. One-to-one migration. Exception: Long text field reference in criteria (LongText is not blank)
- Fast field updates should be combined in before-save flows. If you have too many variations of workflow criteria, do not force everything into one flow. Come up with logical divisions and split them into multiple naming the flows accordingly.
- Tasks should be combined in after-save flows. On objects where there is an after-save flow already, the field updates can be included in one after-save flow.
- When combining many WFRs with various different criteria into one flow, decisions get overly complicated. No access to a formula builder. Split if needed.
Please check the presentation pdf at this link for more information.🔥 All my courses are on a huge sale: 🔥
- My bestseller Udemy course is on sale for $9.99, the lowest price of the year. Buy it now and get lifetime access to the course and the reshoot that will be published by the end of 2023. I will publish a new code here every week until the end of October. Click here to buy or use the code: OCTOBER1
- My bootcamp-style six-week long Advanced Flow course is on a 50% sale. Buy it now and start the course on the 8th of January. Start the year strong: Click here to register.
This post was originally made to LinkedIn on October 17, 2022.
Read the previous post: AND(NextStep = “GoWithTheFlow”, OR(Type “WFR”, Type “PB”))