|This content applies solely to Process Mining, which must be purchased separately from the Appian base platform.
This page describes what event logs are and how to manage them.
An event log, commonly referred to as a log, is a table of events and their associated event attributes. For example, event logs contain a list of events and their case ID, time stamp(s), and additional event attributes. Additional event attributes may include the the employee that performed the action or the system that was used. The log represents the cases of a business process. Process Mining performs analysis on event logs to create a discovered model.
A formatted event log looks something like this:
Event logs also correspond with case attribute files. Case attributes can be thought of as fixed characteristics of an overall case that do not change from event to event. Case attributes are important part of analysis to create graphs and aggregate data. For example, case attributes could help you determine the number of cases per customer.
In addition to the categorical, impact, and numerical attributes you can define in Mining Prep, you can also define descriptive attributes when you upload a log. Descriptive attributes are similar to categorical attributes, but they are irrelevant for most calculations and analysis. For example, product descriptions or user notes are usually distinct for each row of data and therefore do not add value to your analysis.
You can create event logs and case attribute files in Mining Prep.
Before you do anything in Process Mining, you must first select an event log. This log contains the process data that Process Mining analyzes. If you haven't uploaded any event logs yet, see Upload a log and case attribute file.
To select a process to analyze via its event log:
You can also access event logs from the header bar by clicking the event log dropdown.
You can add, share, edit, and delete event logs from the management hub. The LOG tab displays all of the event logs that you've uploaded to Process Mining or that have been shared with you.
To quickly find a specific event log, use the Search field.
The active event log is the basis for much of what you see in Process Mining. Only one event log can be active at a time, but you can create process scorecards with multiple logs.
The active event log is displayed in the header bar as shown in the following image:
To change the active event log:
You can also click the name of the event log in the header bar and select another event log from the Switch to section. This is an easy way to change the active event log from anywhere in the system. If a target model is linked to an event log, the Link icon displays beside the name in the dropdown.
There are several ways to add an event log to Process Mining:
You can also optionally upload a case attribute file to Process Mining. If you transform and load your data from Mining Prep, this happens automatically.
If you upload a log file without a case attribute file, you cannot add the case attribute file later. While a case attribute file is optional, we recommend it so you can maximize the potential of your analysis.
You can upload a file up to 1 GB in size for Appian Cloud Process Mining installations depending on your local network speeds.
To upload only an event log file directly to Process Mining:
Select Upload new log.
To upload an event log and case attribute file directly to Process Mining:
After you upload the file(s), Process Mining displays the discovered model for the newly uploaded event log.
You can edit the name of event logs that you've uploaded to the system.
To edit an event log name:
You can add or edit the description of event logs that you've uploaded to the system.
Add descriptions to your event logs to provide context for you and other members of your organization. If an event log doesn't have a description, its row in the Description column displays Add description.
To add or edit an event log description:
Alternatively, you can click a description directly to edit it.
Connect a target model to your log when you want to analyze the conformance and deviations of your discovered process against the target process. If you want to connect a model to your log, you can either upload a target model, select an already uploaded target model, or create a new target model. See Models for instructions on how to upload or create a target model.
To connect an existing event log with a model:
Rather than select an existing model, you can also upload or create a new model during this process.
To disconnect an event log from a model:
The most common reason you'd update an event log's model is when you have a new target model. You may create a new target model as the result of changes to target processes, laws, regulations, internal guidelines, or service-level agreements (SLAs).
To change the connected model:
You can also upload or create a new model during this process.
You may wish to share an event log with your entire organization or with specific users. When you share an event log, the connected models, dashboards, and filters are also shared. However, you can also choose to share these items individually.
To share an event log:
To stop sharing an event log:
To delete an event log:
If you delete an event log, this action cannot be undone.