This year I had the honor of presenting at Forcelandia again. Forcelandia is one of my favorite user led conferences, both because of it’s wealth of technical content and because, living in Seattle, it’s our closest PNW Conference. Big Shout out to Slalom for being a Platinum Sponsor this year! And of course to all the amazing folks that managed to put this great event together.
This year I spoke about One Process To Rule Them All… One process to rule them all, one process to find them, one process to bring them all and in the invocation bind them. As a best practice Salesforce now recommends restricting your org to one record-change process per object, and if need be invoking flows or sub-processes. This is great because it allows us to see all the criteria that are evaluated each time records are updated, consolidate actions to avoid hitting limits, and determine the order of operations. Truly a tool of great power. But what if you want to deactivate just one criteria node? Invokable processes/flows could be used elsewhere, you may only have actions associated with your process criteria node that you do not want to delete, or you may want to deactivate certain processes just for a subset of users. In this session you’ll learn tricks to manage process criteria nodes using Custom Metadata Types, Custom Settings, and Custom Permissions. No harrowing trip to Mount Doom required.
Enjoy the slides here or use the link below to download:
Please feel free to post comments/questions here for the benefit of other readers, or reach out to me on Twitter or LinkedIn. #KeepCodeWeird
