Flow provides a linear navigation framework for orchestrating multiple forms together.
If you’re building a multi-page form or a wizard, start with Flow. That “more” might be more advanced logic, such as branching or iteration, and it might be more actions like integrating with external systems, sending emails, or pushing notifications to a user’s mobile app. 
Both tools offer ways for your solution to do more than create or edit a single record.
If you need additional logic or actions behind the form, use Flow or LWC. If your requirements aren’t met by those constraints, keep reading. That means you need a create or edit form for exactly one object on desktop, and you need to control field visibility. If Lightning Pages and Dynamic Forms meet your requirements, use them. Quickly, let’s elaborate on the takeaways and table above. Not Available: No plans to support this capability within the next twelve months. Our forward-looking statement applies to roadmap projections. Roadmap: Estimated for support by Winter ’23 Release (October 2022). Not Ideal: Possible but consider an alternative tool. Available: Works fine with basic considerations. Lightning Pages are declaratively configured with the Lightning App Builder. *Dynamic Forms is a feature of Lightning Pages. You’ll see a similar assessment, focused on orchestrating automation logic within Salesforce in the Architect’s Guide to Building Record-Triggered Automation on Salesforce.Ī bit later, we’ll go into depth on these use cases and more, including how to choose between click-based tools and code-based tools (and when to combine them), but here are the major considerations to start with when choosing between these three options. This doc focuses on form-building options for working with records in Salesforce. You can write unit tests for any LWC, regardless of where you plan to embed it. Takeaway #3: If you need test automation, start with LWC. If you need to also meet precise UX requirements, layer in LWCs. Takeaway #2: Use Flow to build multi-screen forms. Takeaway #1: When building basic create/edit forms for custom objects on desktop Lightning Pages, use Dynamic Forms.
0 kommentar(er)
