| Table of Contents |
|---|
...
Automated workflows are licensed by tenant or customer. Each execution of a workflow is considered as one transaction. These automated workflow transactions are in addition to conversation transactions. If a Luma skill is fulfilled by an Automated Workflow, two transactions are involved , - a conversation transaction and an automated workflow transaction.
...
What will not be considered as an automated workflow transaction:
- Automation workflows executed on a Staging (non-production) Luma environment.
| Info | ||
|---|---|---|
| ||
If automated workflows are enabled for a tenant, then the total purchased, used and available transactions are displayed in the Subscription Information tab. For more details, refer . |
Luma Usage Alerts
When Auto-refill is Enabled:
...
On the Settings page, click the Subscription Information tab to view the tenant subscription details as shown below.
Entitlement Details
Entitlement details displays the following information:
| Field | Description |
|---|---|
| Purchased TransactionsTotal Purchased | Displays the number of transactions the tenant purchased. |
| Used TransactionsUsed | Displays the number of transactions the tenant used to date. |
| Available TransactionsAvailable | Displays the remaining transactions which can be used by the tenant. |
| Contract Start Date | Displays the contract start date of the subscription. |
| Contract End Date | Displays the contract end date of the subscription. |
| Technical Contact Email | Email addresses of the technical contacts who manages the tenant. You can edit the information if required. Note: You can add multiple email addresses. |
| Billing Contact Email | Email addresses of the billing contacts who manages the tenant subscriptions. You can edit the information if required. |
...
You can download the transaction history data for your tenant environment. You can specify the duration of the transaction history by selecting a date range. For an overview of how transactions are defined see the Luma Transactions section below.
To download the transaction history log:
- Select the From date. By default, a period of 30 days is displayed in the calendar. A maximum of three months (90 days) can be specified to download the transaction history.
- Select the To date.
- Click Download
The file will be downloaded in .csv format as shown below:
The following columns are displayed.:
Transaction ID: The unique identifier of the transaction.
Transaction Date & Time: The date and time when the transaction occurred.
Bot Name: The name of the Bot where the transaction occurred.
Associated Skill Name: The skill associated to the transaction such as FAQ, View Ticket, and Add Worklog.
Transaction Type : Indicates the type of transaction that occurred either a Automated Workflow transaction or a Conversation transaction. This relates to the transaction licenses.
Fulfillment Type: The type of fulfillment that was used on the Skill associated with the transaction. This could be Automation Workflow, Web Services, Text, Email, Pre-Conversation Action, or FAQ.
Fulfillment Details: Fulfillment details includes the Automation workflow name, Web services connector and operation, Text ( and No need of Text response with actual output), Email-Template Name ( and for custom templates have "Email" only), or Pre-conversation action.
User Name: The username of the user chatting with the Luma bot that initiated this transaction.
Role: Role of the user who initiated the transaction.
Channel: The chat channel used to initiate this transaction. For example, MS Teams, Skype for Business, Web Widget, Slack and so on.
...