![]() Since this use case was simpler, we made use of the dynamic forms in Flows. This feature is also referred to as “Dynamic Forms” in Flows (see the screenshot below), and it allows the binding of the multiple fields of an object directly to a record variable. It uses a new Screen Flow feature that allows developers to place record fields directly on the flow screens. ![]() Let’s look at how the Create Account screen (the first element on the above screenshot) is built. Output variables from the flow can be captured from the Lightning web component. An Assignment element to assign the output variables.A Data element to insert a record into the Salesforce object.It consists of fields from the Account object. A Screen element that allows users to input the data.We have named this flow “Create_Account.” The diagram below shows an example flow for the Account object. To keep the design simple, we built one flow for every object that the quickRecordCreate component supports. The first step we took in designing the quickRecordCreate component is to build the screen flows. The diagram below shows how we compose the component using the Lightning web component and the flow. However, let’s use Screen Flows to build the form so that we can understand how to embed flows within the Lightning web component, as well as the advantages of using this approach. There are multiple ways to build the form component with the various base components, such as lightning-record-form (see docs) or lightning-record-edit form (see docs). ![]() The component shown in the diagram in the previous section can be completely built using Lightning Web Components.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |