AdvoLogix allows you to extract data from the billing preview lightning interface and consume any custom lightning component or background flows. Two kinds of actions are supported within the billing preview, and they allow your developer or administrator to extract all the billing record IDs or selected record IDs based on the filter applied. These record IDs can be used to query or process the data within your own customizations, such as a custom lightning component on the same page or within a background flow.
What custom action types are supported?
- Get All Billing Record IDs - When this action is activated from the billing preview, it fetches and returns record IDs for all of the billings shown on the user interface based on the filter applied.
- Get Selected Billing Record IDs - When this action is activated from the billing preview, it fetches and returns record IDs for all of the selected billings shown on the user interface based on the filter applied.
How do I add custom actions?
The system administrator can add custom actions in the AdvoLogix Setup tab. For more information, please follow this link.
How do I read the data from the custom actions execution?
The billing preview will present the custom actions added by your administrator within the action menu. These actions do not require any user interface interaction to activate; instead, the data provided as a result of the activation can be listed within your own custom lightning component or within a flow.
š§ Did you know? You can control the order of the custom actions from the AdvoLogix Setup tab. Follow this link for more information.
There are multiple ways you can get the data from the custom actions activation:
This approach is suggested for Lightning Web Components (LWC).
AdvoLogix issues Dynamic Interactions for LWCs that can be subscribed to within a lightning page in the Lightning app builder. Follow this link to configure interactions for the billing preview.
This approach is suggested for Aura Components.
AdvoLogix issues an Aura Application Event, named advologixBillingPreviewEvent. The event includes an attribute named data, which returns the billing preview JSON data based on the custom action issued.
This approach is suggested for any background operation like Flows or APEX Triggers.
AdvoLogix issues a Platform Event named advpm__Data_Event__c. The platform event includes the billing preview JSON data based on the custom action issued within the advpm__Payload__c field and the custom action name within the advpm__Type__c field.
Use the sample project provided with an example component to understand the usage of the Dynamic Interaction method for the billing preview data consumption.