Actions are configured to support your sales process and Salesforce usage. They provide utility directly in the Pipeline Review app for users to review and manage their deals and update other information. The actions appear in action menus throughout the app, including in List View rows, Kanban Cards, and Opportunity Popovers.
In the Akoonu Setup app you can change the labels, reorder, add, edit, and activate/deactivate Actions. They are similar to QuickActions in native Salesforce, and can be one of five types: Lightning Flow, Lightning Component, View record, Edit Record, and Navigate to a URL.
Set the Action Set to "Opportunity Rows and Cards" for the action to be in the Action Menu in user interface. Leave the Action Set to "None" for actions you wish to access programtically from custom components, but not to expose in the menu.
Actions can act on the Opportunity object, or any related objects, and illustrated in the examples below.
This action will open the Action Record either in a modal or in a new browser tab. The Action Record can be set to the Opportunity itself, or any related Object (i.e. Account). You can choose to open in the standard Salesforce modal, or open a new tab to the standard full page for the object.
This action will initiate the creation of a new record of the specified type. For objects with Record Types, you may optionally pass the Record Type Developer Name. Default Values can be defined in the Advanced Configuration as a JSON attribute named 'defaultValues'. Values may be static values, or Action Record data by refering to field names in braces.
Here is an example action configuration to create a new Task of type "Sales Action" with two fields preset:
"Description":"New Sales Action"
This action will launch a Lightning component in a modal window. You may choose any Lightning Component so this is a great way to add more information and utility directly into the interface.
The component must defined as access="global" to allow for instantiation within the Pipeline Review app.
The ID of the Action Record will be passed to the component as an attribute named recordId. The Action Record can be set to the Opportunity itself, or any related Object (i.e. Account).
Flow actions will launch the specified Flow. Input Variables can be defined in the Advanced Configuration as a JSON attribute named 'inputVariables'. Values may be static values, or Action Record data by referring to field names in braces.
The Action Record's ID will automatically be passed as a recordId Input Variable to the Flow.
For example, this action might launch a Flow to add a comment to an Opportunity.
Navigate to URL
This action will open a new browser tab to the configured URL. The URL can be tokenized so that data from the Origin Record can be populated into the URL parameters.
The tokens are defined in the Advanced Configuration as a JSON attribute named urlTokens that is a map of token and fields. The field names are enclosed in braces.
For example, here is how to open Google news for the Opportunity's account name. Note that AccountName__c is a formula field on the Opportunity object that references the Account.Name field.