|This content applies solely to Process Mining, which must be purchased separately from the Appian base platform.|
An event log is a table of events and their associated event attributes. For example, event logs contain a list of events and their case ID, timestamp(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.
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.
You can create event logs and case attributes in Mining Prep.
Before you do anything in Process Mining, you must first select an event log because this contains the data that Process Mining analyzes. When you first sign in, you can either choose to Analyze a process or Score processes.
To analyze a single process via its log:
If you haven't uploaded any event logs yet, see Upload a log and case attribute file.
To score multiple processes via their logs:
See Process Scorecards for more information.
The Log Management page displays all of the event logs that you've uploaded to Process Mining or that have been shared with you.
To access the Log Management page:
Alternatively, you can click Log Management from the side menu bar.
The Log Management page is split into two sections:
Rows in Your event logs display the Context Menu icon. Click the Context Menu icon to select from the following options:
To quickly find a specific event log, use the Search field in either section.
The active event log is the basis for much of what you see in Process Mining.
On the Log Management page, the Is Active? column indicates the active event log with a filled in radio button. Only one event log can be active at a time.
To switch to another event log, select the radio button in the Is Active? column. 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.
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.
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 import 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.
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 shown in the Your event log section.
To edit an event log name:
You can add or edit the description of event logs shown in the Your event log section.
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:
Connect a model to your log when you want to analyze the conformance and deviations of your discovered process against the target. If you want to connect a model to your log, you can either upload a model, select an already uploaded model, or create a new 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 why you would want to connect a new model to an event log 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.
On This Page