Salesforce regex for number type in flow

#SALESFORCE REGEX FOR NUMBER TYPE IN FLOW CODE#

Harness the power of invoked actionsД¬lean up inefficient flows with invoked actions - donвЂ™t be scared of using some reusable code to make nice, clean, presentable flows. This is especially critical when youвЂ™re using a workaround to address a Flow limitation, performing a more advanced function, or calling an Apex invocable. This will ensure any member of the team can pick up the work if needed. Make sure you write short blurbs in each step and talk through what each Flow element is and its purpose. Check out this nifty Wiki article from the Salesforce Exchange Discord Server on suggestions for flow naming. One popular naming convention is called Camel Case. ThereвЂ™s no right or wrong way to do this just keep it consistent within the flow.

A little bit of work up front will go a long way for future вЂyouвЂ™ or somebody else that inherits the flow. Include in the variable description what youвЂ™re capturing. Stick to naming conventions when creating variables and elements in Flow. Have a JIRA or Story ID to link it to a Story? Stick it in the description! Ensure consistent naming across elements and variables Even better, if you can talk about or mention where this flow hooks into the business process and which groups it touches so the next person can go to them with questions. Outline the flowвЂ™s purposeДЇill in that description field! Which problem is your flow solving? Be sure to include what your flow does, the objects your flow touches, and where itвЂ™s invoked from (such as which page layout to use if itвЂ™s a screen flow, which Process Builder process to use if itвЂ™s an Autolaunched flow, etc.). Flow designers donвЂ™t create solutions out of thin air - we need a business case to solve hard problems, and having those breadcrumbs is critical for maintaining the automation long term. Document your flows!Дocumenting your flow allows the next person, or the forgetful future version of yourself, to understand the overall flowвЂ™s objective. In this blog, weвЂ™ll discuss best practices, вЂgotchas,вЂ™ and design tips to make sure your flows scale with your organization. WeвЂ™re starting to see a unique collaboration between admins and developers, with both sides learning a little something about Development and Administration. Flow is not just an вЂadmin toolвЂ™ - itвЂ™s the holy grail of declarative development that unites developers AND admins by allowing the use of Lightning Web Components (LWC) and Apex, and letting the admin orchestrate all of it in one place. ThereвЂ™s no way around it: Salesforce Flow is the automation tool of the future.

Salesforce regex for number type in flow