|This content applies solely to Process Mining, which must be purchased separately from the Appian base platform.|
You can mine data directly from your Appian applications using Records as a data source. There are several benefits to using a Records data source instead of extracting and loading a CSV file directly from a database.
For example, using the Records as a data source:
There are a few characteristics of record types that make them easier to mine. For example, your record types should include IDs to identify business processes, activities that make up your process, and time stamps for when activities took place.
See What makes a good data set? for more information.
The easiest way to mine data from your Appian applications is to use a record type as the data source. Once you add a Records data source in Mining Prep, you can import record data into data sets in a transformation project. You'll execute the transformation project to transform your record data into an event log and load it into Process Mining.
Add a Records data source to import record data into Mining Prep.
Before you begin these steps, make sure you have a service account API key.
To add a Records data source:
Once you've added the Records data source, you can import the record data as data sets. You can only import data from record types that your Process Mining service account can access.
To import data from a record type:
You can import data from multiple record types into the data source. Each record type will import into a unique data set.
Record types that contain close to 2 million rows or more than 50 columns may take over an hour to import.
Once you've imported the record data into different data sets, you can create a transformation project directly from the data set.
To create a transformation project:
You're done! You can now apply transformation actions to your data and execute the transformation project. Once you execute the transformation project, Mining Prep transforms your data into an event log and loads it into Mining Prep for further analysis.
Because Records data sources require record types that have data sync enabled, it's easy to keep your data fresh. Whenever you execute or schedule updates to a transformation project with a Records data source, your data will update automatically.
You can manually reload your data for in-progress transformation projects. Since you typically won't set up a transform and load schedule until your project is complete, manually reloading your data keeps it fresh during this stage.
To manually update your data set:
Mine Appian Applications Using Records