Custom / Configurable Actions
Throughout Seven20, there are areas where actions can be performed on records in context, such as within Search or Hotlists. These actions include standard Seven20 actions, but they can be extended to include custom actions that are specific to your organisation's needs.
Action metadata
All actions, whether they are standard or custom, are configured through the use of metadata records. These records are of the type seven20__Custom_Action__mdt and are used to control everything from the action's label, to its ordering within the UI. The following fields are available on the metadata records:
| Field Label | Field Api Name | Description | Editable |
|---|---|---|---|
| Developer Name | DeveloperName | The unique name of the record | No |
| Label | Label | A user friendly version of the Developer Name | No |
| Active | seven20__Active__c | Indicates whether this action is active or not | Yes |
| Button Icon | seven20__Button_Icon__c | The fully qualified API Name of a SLDS Utility Icon | Yes |
| Button Label | seven20__Button_Label__c | The fully qualified API Name of a Salesforce custom Label | No |
| Component Name | seven20__Component_Name__c | The fully qualified API Name of the Flow. | No |
| Implementation Type | seven20__Implementation_Type__c | Must be set to flow. Standard actions use Seven20 | No |
| Order | seven20__Order__c | If multiple records are defined for the same process what order should they appear in. 0 is leftmost and 99 rightmost | Yes |
| Process | seven20__Process__c | Picklist, select the relevant location in Seven20 where the action will appear | No |
seven20__Button_Icon__c will be ignored for mass actions embedded in a tab
The editable column only applies to packaged records, e.g. those with an implementation type of seven20
Action ordering
Custom and standard actions are ordered collectively with no differentiation between Seven20 actions and custom ones for this purpose.