Table of Contents |
---|
Overview
...
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.
...
Field | Description |
---|---|
Refill Type | Displays the refill type, whether the transaction is refilled manually or automatically. |
Refill Date | Displays the date when the transaction is refilled. |
Added Transactions | Displays the number of transactions refilled. |
Luma Transactions
Anchor | ||||
---|---|---|---|---|
|
Luma transactions include conversation transactions and automated workflow transactions. As a tenant administrator in skills builder, you can view the number of transactions that are processed through Luma since the contract start date. As a result, you can ensure compliance with license agreements and purchase more transactions if necessary.
...
What will not be considered as an automated workflow transaction:
- Automation workflows executed on a Staging (non-production) Luma environment.