The Native App is designed to streamline the configuration of process mining within your Snowflake environment. We call this configuration a Process Scenario.
Object-centric fields on the event log (such as EL_LINK) are optional at scenario creation; validation depends on which columns your event log contains. See Input Data Model.
Scenario name requirements
The scenario name becomes a database schema name, so it must be 1–20 characters, start with a letter, and contain only letters, digits, spaces, hyphens, and underscores (German äöüÄÖÜß are allowed). It must also not resolve to a reserved SQL keyword — for example Order, Select, User, Table, Session, or Current Date. Combined names are fine (User Order becomes the schema USER_ORDER).
Otherwise you'll see: "The name of the process scenario would result in a reserved SQL keyword (like ORDER or SELECT) and cannot be used." Scenarios can't be renamed later, so pick another name (for example Order → Orders). See the full list of reserved keywords in Snowflake.
Create a Process Scenario
Continue by clicking "Create".
Once the scenario has been created, you will be taken to the Data Sources screen of the scenario.
Select a table or view as the Event Log.
The application will initialize the scenario. This step may take a few moments.
You can also add additional information using the Case and Event Dimensions.
Example Scenarios - Select an Event Log
You can also add additional information using the Case and Event Dimensions.
Example Scenarios - Select an Event LogThe app asks for access to a table in your account
You can also add additional information using the Case and Event Dimensions.
Example Scenarios - Select an Event LogThe app asks for access to a table in your accountChoose your Data
You can also add additional information using the Case and Event Dimensions.
Example Scenarios - Select an Event LogThe app asks for access to a table in your accountChoose your Data
You can also add additional information using the Case and Event Dimensions.
Example Scenarios - Select an Event LogThe app asks for access to a table in your account
You can also add additional information using the Case and Event Dimensions.
Example Scenarios - Select an Event LogThe app asks for access to a table in your account
You can also add additional information using the Case and Event Dimensions.
Example Scenarios - Select an Event LogThe app asks for access to a table in your accountChoose your DataThe app asks for access to a table in your accountChoose your Data
You can also add additional information using the Case and Event Dimensions.
Example Scenarios - Select an Event LogThe app asks for access to a table in your account
Click "Next →" to continue
Fill in the process mining configuration—including optional Conformance Checking and Impact Analysis (Core mode)—until you've reached the Task Execution History screen. Each change will be saved automatically. See Impact Analysis Page.
Autosave Notification
Here you can configure regular process mining runs.
To start the process mining manually, click on the "Start Mining Task" button, right beneath the Ad-hoc Task Execution Section.
Start Process Mining
The Task Execution History section, which you can also see on the screenshot above, displays the current status of the process mining run.
Once the process mining has been completed for the first time, you can analyze the mining model using the mpmX Analytics tool.
The ouput of the mining process can be found in the schema named after the process scenario.