A new version of the Avonni Dynamic Components is now available!
Read the Release Notes
YouTube ChannelBook A DemoContact SupportSubscribe for Updates

Open Quick Action

Overview

The "Open Quick Action" interaction lets you launch Salesforce Quick Actions directly from within an Avonni Dynamic Component. This provides a seamless way to trigger standard or custom Quick Actions without requiring users to navigate to record detail pages, enabling streamlined workflows and faster data entry.

Configuration

The "Open Quick Action" interaction connects a user action (such as clicking a button) to a Salesforce Quick Action. When configured, it opens the Quick Action modal, optionally pre-fills form fields, and passes context like record IDs.

Add this interaction to any supported Avonni component through the component's properties panel under "Interactions." Select "Open Quick Action" as the interaction type.

Target Name

This is where you select which action on your component will trigger the Quick Action. When you add actions to components (like header actions on a data table or row actions), they become available in this dropdown.

How it works

  • First, you create an action on your component (e.g., a "Send Email" as a row action on a data table)

  • That action name then appears as an option in the Target Name dropdown

  • Select the action you want to connect to this Quick Action interaction

Example: If you added a row action called "Send Email" to your data table, you would select "Send Email" from the Target Name dropdown to link that action to the Quick Action.

Source Entity

This specifies the object context for your Quick Action:

  • For object-specific Quick Actions: Enter the API name of the standard or custom object (e.g., Contact, Account, Opportunity, Custom_Object__c)

  • For global Quick Actions: Leave this field empty

Why this matters: Object-specific Quick Actions are tied to a particular object and appear in that object's action menu. Global Quick Actions work across the entire org and aren't tied to any specific object.

Quick Action API Name

This is the API name of the Quick Action you want to launch. The format depends on whether it's object-specific or global:

For object-specific Quick Actions: Include the object's API name followed by a dot (.) before the Quick Action's API name.

Format: ObjectAPIName.QuickActionAPIName

Examples:

  • Contact.SendEmail - Send Email action on Contact object

  • Account.LogACall - Log a Call action on Account object

  • Opportunity.NewTask - Create Task action on Opportunity object

  • Custom_Object__c.Custom_Action__c - Custom action on custom object

For global Quick Actions: Use only the Quick Action's API name (no object prefix).

Examples:

  • NewContact - Global action to create a contact

  • NewTask - Global action to create a task

  • LogACall - Global action to log a call

  • SendEmail - Global action to send email

How to find the API Name:

  • Go to Setup → Object Manager → [Your Object] → Buttons, Links, and Actions

  • Or Setup → Global Actions (for global actions)

  • Find your action and note its API Name

Record ID (Optional)

This specifies which record the Quick Action should be associated with or use for context. Enter a reference to a field or variable that contains the record ID.

Common uses:

  • record:Id - The current record being viewed (if on a record page)

  • {!Datatable1.selectedRowsKeyValue} - The selected record from a data table

  • {!variableName} - A variable storing a record ID

When to use Record ID:

  • When the Quick Action needs to know which record it's acting on

  • For actions like "Send Email" that need a related record

  • For creating related records (e.g., creating a Task related to an Account)

Prefilled Values (Optional)

This lets you automatically populate fields in the Quick Action form before it opens, saving users time and ensuring data consistency.

For each prefilled value:

  • Field API Name: The API name of the field in the Quick Action you want to pre-fill (e.g., Subject, Status, Priority)

  • Value: What you want to populate - this can be:

    • A static value (e.g., "Follow-up Call")

    • A dynamic value from your component (e.g., {!accountName.value})

    • A resource variable (e.g., {!selectedStatus})

Example use cases:

  • Pre-fill the Subject field of a Task with "Follow-up: " + account name

  • Set the Status of a new Case to "New"

  • Populate the Related To field with the current account ID

  • Default the Priority to "High" for urgent actions

Troubleshooting

The Quick Action doesn't open

  • Verify the Quick Action API Name is correct (case-sensitive)

  • Check that the Quick Action exists and is active in your org

  • Ensure you're using the correct format (Object.Action for object-specific, just Action for global)

  • Verify the user has permissions to access the Quick Action

"Quick Action not found" error

  • Double-check the API Name in Setup

  • Ensure you included the object name for object-specific actions (e.g., Contact.SendEmail)

  • For global actions, ensure you didn't include an object prefix

Record ID not passing correctly

  • Verify your data table's API Name matches what you used in the formula

  • Check that a row is actually selected in the table

  • Use the correct attribute (.selectedRowsKeyValue for single selection)

Prefilled values don't appear

  • Verify the field API names exactly match the Quick Action's field names

  • Check that the fields are actually included in the Quick Action layout

  • Ensure your value expressions are valid and return the correct data type

User sees an error when submitting the Quick Action

  • This is typically a Salesforce validation error, not a configuration issue

  • Check Salesforce validation rules and required fields

  • Ensure pre-filled values meet field requirements

Need More Help?

If you have questions about implementing Quick Action interactions for your specific use case, or if you encounter issues with Quick Action configuration, don't hesitate to reach out. We're here to help you create streamlined workflows with Avonni components

Last updated

Was this helpful?