*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.Options are great, but how do you determine which one (or which combination) is the right option? That’s where this doc comes in. And representing pro-code is the LWC framework and its ever-growing library of base components. Hanging out in the middle of the continuum is the ability to extend screen flows with LWCs. Representing low-code, Dynamic Forms in Lightning App Builder and screen flows in Flow Builder. Looking to build forms on the Salesforce Platform? You’ve got multiple options, spanning the entire low-code to pro-code continuum. Our forward-looking statement applies to roadmap projections. Roadmap corresponds to October 2022 (Winter ‘23) projections.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |