Aggregate Monetized Usage

Overview

This configuration enables the operations user to decide how monetized transactions are synchronized back from Aria Allegro to Aria core for invoicing and/or statement generation.

Allegro uses bulk_record_usage_m API to synchronize monetized usage transaction back to core Aria.

View Existing Aggregate Monetized Usage Configuration

1. Click on the Usage switch (Usage/Account toggle switch) in the navigation pane.
2. Click on the Configurations menu option in the navigation panel. This will expand the submenu for Configurations in the Navigation Pane.
3. Click on the Aggregate Monetized Usage menu option in the navigation pane.
4. This will fetch the existing configuration for synchronizing the monetized usage.

This is shown in the following UI screenshot:

Please note that the payload for the bulk_record_usage_m API is fixed. Most of the fields are chosen and a default entry for each attribute is automatically added in the configuration as part of the deployment.

The configuration allows the mapping of the bulk_record_usage_m API attribute to the corresponding attribute from the Allegro usage container (later to be extended for other objects as well like account).

Some of the attributes are mandatory attributes and have a fixed mapping. These attributes are disabled, and the user will not be allowed to change the mapping for these attributes. For example, account-Id is a mandatory attribute and that attribute mapping will remain the same.

All Aria Allegro monetized usage record attributes map to the corresponding core Aria bulk_usage_map API attributes to send relevant data back to core Aria.

Modify Existing Aggregate Monetized Usage

1. Navigate using “To view existing Aggregate Monetized Usage”.
2. Manage Header level attributes:
   • Aggregate Usage—This sets the system property to indicate whether we want to aggregate usage before sending them to core Aria or not. Aggregation may be required where we expect to manage huge volume of transactions. Select the Boolean value from the dropdown list to set the default for the Client setup.
   • Aggregate Usage Unit—Set this attribute to indicate at what frequency to send the monetized usage from Aria Allegro to Aria Core. For example, sending monetized usage once daily, set the unit as DAYS. Select the value from the dropdown list.
   • Aggregate Usage Frequency—Set this attribute to indicate at what frequency to send the monetized usage from Aria Allegro to Aria Core. For example, sending monetized usage once daily, enter the frequency as 1 (for once a day).
3. For each attribute listed in the table:
   • If the attribute is not a mandatory attribute (enabled for mapping), select the field Attribute Name from the Allegro usage container dropdown list that would map to the bulk_record_usage_m API attribute identified by Billing Attribute.
   • If the Aggregate usage is enabled, then select whether the attribute should be part of the aggregation key or not. This is done for the field Aggregate by selecting the Boolean value from the dropdown list. 
   • Please note: 
     1. If one or more attributes are marked for aggregation, then the Amount, Unit Price and Quantity values will get aggregated.
     2. Other attributes that are not mandatory and are not part of the aggregation key, then the values for those attributes will be sent as NULL.
     3. If you want all non-mandatory and non-summation attributes (unit price, quantity, net amount) to be part of the aggregation, then that is simply achieved by turning off “Aggregate Usage”.
   • Repeat Step 3 for each attribute enabled for Edits.
4. Click on the SAVE button at the bottom right corner of the drawer. This will push the changes to save the configuration using the backend API.
5. Click on the CANCEL button at the bottom right corner of the drawer to cancel all the data entry and go back to the pre-edit state for the configuration.