Add Actions to a Flexcard (Managed Package)

For the managed package runtime, add up to six actions to a Flexcard to launch or update an Omniscript, navigate to a web page or application, display a flyout, fire an event, or update data field values. For example, add an action on an account Flexcard that when clicked, displays the contact information for the account.

1. In the Flexcard Designer, drag the Action element from the Build panel into a state on the canvas.
2. (Optional) From the Properties panel, update the element name in the Element Name field.
3. Beginning Spring '22, execute multiple sequential actions from one element:

   1. (Optional) To block users from interacting with the Flexcard until actions that require waiting for a response, such as a Data action, are resolved, enter true in Show Spinner. Or enter a merge field whose value is true, such as {requireResponse}. The user sees a spinner image and a dimmed page while waiting. Default is false.

   2. Select the right arrow under Actions next to the default Action label to reveal properties to configure.

   3. (Optional) To distinguish this action from other actions on this element, update Action Label. This label is only visible within the designer in Design view.

   4. Select the type of action to execute from the Action Type dropdown. See Flexcards Actions Reference (Managed Package).

   5. Before Spring '22, configure one action to execute:

   6. (Optional) To create another action that executes after the previous one completes, select + Add New, and repeat steps a through e.

   Before Spring '22, configure one action to execute:

   1. Select the type of action from the Action Type dropdown. See Flexcards Actions Reference (Managed Package).

   2. Before Spring '22, configure one action to execute:

4. (Optional) To update the visible label for the action, enter a new label in the Label field.
   

   Note

   Beginning Summer '21, Label supports concatenated strings. Combine plain text and supported merge fields. For example, Update {AccountName}.

5. (Optional) To update the default icon, from the Icon field, perform one of these tasks:

   • Enter the name of the icon, such as utility:arrowdown. See Salesforce Lightning Design System.

   • Click the search icon in the input field, and perform one of the following tasks:

     • Click to select an icon from the list available, and click Save.

     • Search for an icon in the search field, click an icon to select it, and click Save.

6. (Optional) To show an icon without text, check Show Only Icon.
7. (Optional) To show a label without an icon, check Hide Icon.
8. (Optional) To display the action link as a button:

   1. Check Display As Button.

   2. Select a style option from the Variant dropdown. For a description of each variant, see Variations.

9. (Optional) To add conditions that must be met for the element to display, see Add Conditions to a Flexcard Element (Managed Package).

• Add a Click Event to a Flexcard Element (Managed Package)
  For the managed package runtime, enable an element on a Flexcard to perform an action when clicked. Supported elements include Image, Block, Icon, and Toggle.
• Flexcards Actions Reference (Managed Package)
  For the managed package runtime, select from multiple ways to execute an action from a Flexcard. Create an action to launch an Omniscript, navigate to a web page or application, display a flyout, fire an event, and more.
• Flexcards Action Properties (Managed Package)
  For the managed package runtime, Action element properties are configurable from the Properties panel in the Flexcard Designer when you select an Action element. With the Action element, create an action to launch an Omniscript, navigate to a web page or application, display a flyout, fire an event, and more.
• Flexcards Sequential Actions (Managed Package)
  For the managed package runtime, enable an element or an event listener to execute sequential actions on a Flexcard. When there are multiple actions, the first action fires, completes, and then triggers the next action. You can use the response from the previous action to perform subsequent actions.
• Flexcard Card Actions (Managed Package)
  For the managed package runtime, the Flexcard Card action type enables you to trigger actions specific to a record item on a Flexcard or the Flexcard itself.
• Navigate from a Flexcard with the Navigate Action (Managed Package)
  For the managed package runtime, navigate to an external web address, or within Lightning Experience, Lightning communities, or the Salesforce mobile app from a Navigate Action element on a Flexcard. For example, allow a user to navigate to a Policy record page by clicking an action element on a Flexcard that lists Account Policies.
• Add a Vlocity Action to a Flexcard (Managed Package)
  For the managed package runtime, add a reusable action to a Flexcard with a Vlocity Action element. Vlocity Actions launch Omniscripts, components, web pages, or external applications.
• Launch a Flyout from an Action on a Flexcard (Managed Package)
  For the managed package runtime, create a flyout to display additional information when a user clicks an action on a Flexcard. For example, a Flexcard that displays Account information can display the Primary Contact's name and email address in a flyout.
• Launch an Omniscript from a Flexcard (Managed Package)
  For the managed package runtime, launch an Angular or LWC Omniscript from an Omniscript Action element on a Flexcard. For example, launch a form that updates Account information based on the account Id passed from the Flexcard to the Omniscript.
• Update an Omniscript from a Flexcard (Managed Package)
  For the managed package runtime, create an action that updates an Omniscript's data JSON from the Flexcard embedded in the Omniscript. You can embed a Flexcard inside an Omniscript as a Custom LWC.
• Call a Data Source from an Action on a Flexcard (Managed Package)
  For the managed package runtime, trigger a data source from an action to get data from a server or post data to a server. When data is fetched from the server, the incoming data is appended to the data JSON in the card's record object or to a data node you name. If you choose to send the request without getting a response from the server, the data JSON does not update. To confirm your request is sent successfully, in Preview, view the requested data in the Action Debugger's response.
• Trigger a Custom Event from an Action on a Flexcard (Managed Package)
  For the managed package runtime, notify a Flexcard of an event occurring from an action on an element. Then execute an action based on the event. Custom Events are used to communicate between a child to its parent, whether it's between a child Flexcard and its parent, or between an element and the Flexcard it's on.
• Trigger a Pubsub Event from an Action on a Flexcard (Managed Package)
  For the managed package runtime, enable an action on a Flexcard to notify another component, such as another Flexcard on a page or application, of an event occurring. For example, update a list of products on one Flexcard from a filter on another Flexcard on the same page or application.
• Register Dynamic Custom and Pubsub Events (Managed Package)
  For the managed package runtime, register events based on dynamic event and channel names. Use a parent attribute, a recordId, or a session variable within the Channel Name and Event Name of a pubsub event, or the Event Name of a custom event.
• Flexcards Reserved Event and Channel Names (Managed Package)
  For the managed package runtime, when configuring pubsub and custom events, there are some event names and channel names that are reserved for specific purposes. These reserved names are listed here.