Custom Actions

Tables have the ability to configure custom actions and use them with different views. First, we have to define the feature and then relate it to view(s) in which we want to use custom actions using the view feature. Depend on the custom action type we have to configure JSON. For now, the tables support the below type of custom actions:

• Custom Action - Aura / LWC Component

• Custom Action - Flow

Here are detailed steps:

Create “Feature” Record

Create “View Feature” Record

1. View = Select View

2. Object Feature = Select Action

3. View Name / Object Feature Name = View Developer Name

4. Object = Object API Name

5. Configuration = Config JSON (Refer below sections to configure different types of custom actions)

   1. Custom Action - Aura / LWC Component

   2. https://avnio.atlassian.net/wiki/spaces/Tables/pages/edit-v2/451379201?draftShareId=483bd301-da2b-4b66-97ad-38473db79d3e

Supported Configuration JSON Attributes

• icon - Any utility icon from https://www.lightningdesignsystem.com/icons/

• recordLevel - Available options: <blank>, single, multiple, single+multiple

• refreshOnClose - Whether to refresh Tables on action close

• showInToolBar - Whether to display in toolbar actions or not (by default available in context menu)

• targetConfiguration - JSON object configuration for target component or flow

• targetType - Available options: Aura/LWC Component, Flow

Supported Target Configuration Attributes

• title - Title of modal

• componentName - Fully qualified API name of component or flow

• componentParams - Parameters to be passed on to target component

• componentParamsList - Parameters to be passed on to target of type list (i.e. for Flow type)

• bodyCss - Custom CSS

• height - Height of modal

• width - Width of modal

• footerActions - Available actions on footer

Supported Target Configuration > Footer Actions Attributes

• name - Unique name of the footer action (used for events)

• label - Label shown to users

• theme - Displayed button variant of the footer action. Available options: base, neutral, brand, brand-outline, destructive, destructive-text, inverse, success

Supported Dynamic Target Configuration > Component/Flow Params Attributes

** Most of these (newer) attributes require minimum Tables Package version 1.130.

• selectedRecordId - First selected record’s ID

• selectedRecord - First selected record

• selectedRecordIds - Selected record ID's list

• selectedRecords - Selected records list

• objectApiName - Object Api Name of current Tables View

• viewDeveloperName - Developer Name of current Tables View

• tablesView - Current Tables View record

• relatedFieldApiName - Related Field Api Name for loading only related records

• relatedRecordId - Related Record ID for loading only related records

• userId - Currently logged in Salesforce user ID

• locale - Currently logged in Salesforce user’s locale code

• language - Currently logged in Salesforce user's language code

• timeZone - Currently logged in Salesforce user's time-zone code

• userCurrencyCode - Currently logged in Salesforce user’s currency code

• orgCurrencyCode - Default currency code for org

• isUserTablesAdmin - If currently logged in Salesforce user has Tables Admin permission set assigned

• isMultiCurrencyEnabled - If multi-currency is enabled for org