Learn the Basics
Last updated
Was this helpful?
Last updated
Was this helpful?
Welcome! This page is your guide to starting with the Avonni Components, a powerful way to build professional, interactive, customized screen flows in Salesforce – no coding is required! You'll learn how to:
to create dynamic, data-driven Flows. Accessing user selections: Getting values from components such as Combobox, Visual Picker.
with the Interactions Panel.
to match your brand and create a great user experience.
Mapped Values are a powerful way to connect your Avonni Components directly to data within your Salesforce Flow. This connection allows your components to:
Display Dynamic Data: Show information that changes based on Flow variables.
Respond to User Input: Update Flow variables based on user actions (like typing in a text box or selecting an option).
Think of Mapped Values as a two-way bridge between your Flow's data and the components on your screen.
Mapped Values let you create Flows that respond to data and user actions in real-time. Instead of static screens, your Flows become interactive and personalized
Let's say you're building a customer service Flow using Avonni Components:
Create a Flow Variable: You create a variable in your Flow called CustomerType (e.g., "Standard," "Premium," "VIP").
Add an Avonni Text Component: You add an Avonni Text component to your screen. This component will display a welcome message.
Map the Value: In the Avonni Component Builder for the Text component, you map the "Text" property of the component to the CustomerType variable.
Dynamic Display: Now, the Text component will automatically display different text based on the value of CustomerType:
If CustomerType is "Premium," the Text component might show: "Welcome, Premium Customer!"
If CustomerType is "Standard," it might show: "Welcome! How can we help you?"
If CustomerType is "VIP," it might show: "Welcome to our VIP service!"
The message changes without you needing to create separate Text components for each customer type. The Flow, through the Mapped Value, handles the dynamic update.
Here's how to connect your Avonni Components to Flow variables:
Add Component: Drag and drop the desired Avonni Component (e.g., Text, Button, Input Date) onto your Screen element in the Flow Builder.
Open Component Builder: Click the component to select it. The Component Builder (properties panel) will appear on the right.
Find the Property: In the Component Builder, locate the property you want to map (e.g., "Text," "Value," "Checked," "Disabled").
Map to Variable: Next to the property, click the connector icon that allow to map the value.
Choose Variable: Select the appropriate Flow variable from the list. Make sure the variable's data type (Text, Number, Boolean, etc.) is compatible with the component property.
Save: Click "Done" on the screen element and save your Flow.
Many Avonni Components allow users to make selections (e.g., choosing an item from a list, picking a date, entering text). You can access these user selections within your Flow to drive further actions, make decisions, or update data.
value AttributeSeveral components, including Visual Picker, Vertical Visual Picker, and Combobox, store the user's selection(s) in a value attribute. The format of this value depends on whether the component allows single or multiple selections.
Single Selection: The value attribute will contain a simple text string representing the selected item.
Example: If a user selects "Banking" from a Combobox, the value might be "Banking".
Multiple Selections: If the component allows multiple selections, the value attribute will contain a semicolon-separated string of the selected values.
Example: If a user selects "Banking," "Biotechnology," and "Chemicals," the value might be "Banking;Biotechnology;Chemicals".
For components that allow multiple selections, you often have additional options to access the selected values in a more structured way:
valueCollection: This attribute provides a collection (a list or array) of the selected values. This is the most useful format for working with individual selections within your Flow.
Example: [Banking, Biotechnology, Chemicals] (This is how it would appear within your Flow logic).
valueCollectionSerialized: This attribute provides a serialized text representation of the collection. This format is less commonly used directly within Flow logic but might be useful for specific data storage or integration scenarios.
Example: ["Banking","Biotechnology","Chemicals"]
Add the Component: Add the relevant Avonni Component (e.g., Visual Picker, Combobox) to your screen.
Configure as Needed: Set up the component's options (e.g., the list of choices for a Combobox).
Access the Value: In a later element in your Flow (e.g., a Decision, Assignment, or another component), you can reference the component's value, valueCollection, or valueCollectionSerialized attribute. You'll do this using the Flow Builder's expression builder (the formula editor).
Example: To check if the user selected "Banking" in a Combobox named "IndustrySelector," you might use a Decision element with a condition like this: {!IndustrySelector.value} CONTAINS "Banking"
Example: to iterate (loop) over selections from a multiple selection in a visual picker, loop over {!VisualPicker.valueCollection}
The Avonni Components offers a wide variety of interactive elements. For components other than Visual Picker, Vertical Visual Picker, and Combobox, always refer to the component's documentation. The documentation will explain accessing user input and data from that specific component. There will be a consistent and named attribute to access the value.
The Interactions Panel lets you create Flows that feel more like interactive applications than static forms. Use it to define what happens when a user interacts with an Avonni Component – for example, what happens when a button is clicked or a selection is made.
The Avonni Components lets you fully customize the look of your components. Change colors, fonts, spacing, and more to match your company's branding and create a professional, polished Flow.
