### Configuration JSON Example Source: https://help.mpmx.com/platform/qlik/installation-setup-integration/mpmx-installation/install_or_update_the_import_wizard Example of the config.json file with tenant URI and web integration ID. ```json { "tenantUri": "", "webIntegrationId": "12345abcde" } ``` -------------------------------- ### Configuration File Example Source: https://help.mpmx.com/platform/qlik/installation-setup-integration/mpmx-installation/install_or_update_the_import_wizard Example of the config.json file, showing how to set the app-filter string to specify which apps are available. ```json { "app": { "appFilter": "mpmX\_ProcessMining\_Template", ... } } ``` -------------------------------- ### Installation Notebook Source: https://help.mpmx.com/platform/databricks/installation_and_update The installation notebook guides the user through the setup process. It includes cells for configuring installation parameters and checking prerequisites. ```python from mpmx_databricks.install import install install( app_name="mpmX - Process Mining for Databricks", install_source_catalog="mpmx_marketplace_catalog", admin_group="account users", sql_warehouse="marketplace-serverless-warehouse" ) ``` -------------------------------- ### Configuration Example for Cloud Deployment Source: https://help.mpmx.com/platform/qlik/installation-setup-integration/mpmx-installation/install_or_update_the_bpmn_wizard Example configuration snippet showing how to set the tenant URI and web integration ID for the BPMN Import Wizard in a Qlik Cloud environment. ```json "tenantUri": "" "webIntegrationId": "12345abcde" ``` -------------------------------- ### Example products.json entry Source: https://help.mpmx.com/platform/qlik/installation-setup-integration/mpmx-installation/install_the_mpmX_cockpit An example of a product entry within the products.json file, showing the structure and the 'url' field that needs to be updated. ```json { "name": "Product Name", "description": "Product description goes here.", "imageUrl": "product-image.png", "url": "https://example.com/product1" }, ``` -------------------------------- ### Transform Phase (02transform) Example Source: https://help.mpmx.com/platform/qlik/tags/setup Combine two tables into one data view using an SAP example. ```sql Combine two tables into one data view using an SAP example ``` -------------------------------- ### Simple KEYs Example Source: https://help.mpmx.com/platform/qlik/advanced-features-and-configurations/pre-mining-configurations/holiday-and-shift-time-handling This example shows the simplest setup where all three pillars (workday, holiday, shift) use the same KEY value. ```qlikview // Same KEY for all three pillars — simplest setup 'Office' as KEY_WORKDAY, 'Office' as KEY_HOLIDAY, 'Office' as KEY_SHIFT ``` -------------------------------- ### mvCalendarFM Example Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/template-app/variables-cheat-sheet Example of setting the fiscal year start month. ```qlik LET mvCalendarFM = 8; ``` -------------------------------- ### Example Resource Model Configuration Source: https://help.mpmx.com/release-notes/v3-0-0 Example configuration file for setting up resource model support with Snowflake. ```qlikview mpmX_scripts/V3.0.0/customizing/SF/custom_variables_resource.qvs ``` -------------------------------- ### Install the App from the shared private listing Source: https://help.mpmx.com/platform/snowflake/installation_and_update SQL commands to install the mpmX Snowflake app using the MPMX_ADMIN role. ```sql USE ROLE MPMX_ADMIN; CREATE APPLICATION MPMX_APP FROM LISTING GZSYZPF2MY BACKGROUND_INSTALL = TRUE; ``` -------------------------------- ### Example Directory Structure Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/create-an-event-log-with-mpmx/generate-events/create_event_sources_for_ccpm An example of the directory structure for generated QVD files, based on mvProcessDescription = 'P2P'. ```shell mpmX_data/etl/P2P/03_ProcessLogGeneration ├── DataSource_EventLogs │ └── eventLog_ds_CDHDR_CDPOS_EINKBELEG.qvd └── DataSource_Repositories └── eventLog_repo_CDHDR_CDPOS_EINKBELEG_activityScenarioFieldsTable.qvd ``` -------------------------------- ### Create MPMX_ADMIN role and grant permissions Source: https://help.mpmx.com/platform/snowflake/installation_and_update SQL commands to create the MPMX_ADMIN role and grant necessary global privileges for application installation. ```sql CREATE ROLE IF NOT EXISTS MPMX_ADMIN COMMENT = 'mpmX Admin'; GRANT CREATE APPLICATION ON ACCOUNT TO ROLE MPMX_ADMIN; GRANT IMPORT SHARE ON ACCOUNT TO ROLE MPMX_ADMIN; ``` -------------------------------- ### Example Case Object Configuration Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/how_to_configure_the_template_app_for_ocpm_fasttrack This snippet shows an example of how to configure case objects for deliveries and payments within the mpmX template app. ```qlikview if(mvProcessDescription = 'Delivery', 1,0-103-104-118-119-126-99999999,CaseObjectType = 'Delivery' CaseInformation_$(mvProcessDescription) y, 2, Happy Path for payment, 0-102-103-117-119-126-190-99999999, CaseObjectType = 'Payment', CaseInformation_$(mvProcessDescription) ]; end if ``` -------------------------------- ### Conformance Checking HappyPathTable configuration Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/how_to_configure_the_template_app_for_ocpm_fasttrack Example configuration for the HappyPathTable in OCPM conformance checking, relating happy paths to objects using CaseObjectType. ```Qlik (QVS) if mvIsOCPM = 0 then HappyPathTable: load * inline [Selected, HappyPathUniqueNo, HappyPathDescription, HappyPaths, RelatedDimensions, RelatedDimensionTable ]; else // OCPM-EXAMPLE: HappyPathTable: load * inline [Selected, HappyPathUniqueNo, HappyPathDescription, HappyPaths, RelatedDimensions, RelatedDimensionTable y, 0, Happy Path for purchase order, 0-103-101-118-119-126-99999999, CaseObjectType = 'Purchase Order', CaseInformation_$(mvProcessDescription) ]; ``` -------------------------------- ### Case Information table with Link field Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/how_to_configure_the_template_app_for_ocpm_fasttrack Example of a Case Information table load script including the obligatory OCPM field: Link. ```Qlik (QVS) Left Keep(EventLog) [CaseInformation_$(mvProcessDescription)]: LOAD distinct CaseID, //OCPM information obligatory Link, //context information CaseDimension1, CaseDimension2 FROM [lib://helpdesk/HelpdeskEventlog.qvd] (qvd); ``` -------------------------------- ### Event Log with OCPM fields Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/how_to_configure_the_template_app_for_ocpm_fasttrack Example of an EventLog table load script including the obligatory OCPM fields: ObjectType, PrincipalObjectType, and ActivityOriginID. ```Qlik (QVS) EventLog: //Log table name: "EventLog" LOAD //ProcessAnalyzer information CaseID, "ActivityName" as ActivityType, Timestamp(ActivityStartTimestamp) as ActivityStartTimestamp, Timestamp(ActivityEndTimestamp) as ActivityEndTimestamp, //OCPM information obligatory ObjectType, PrincipalObjectType, ActivityOriginID ``` -------------------------------- ### Event Log with ObjectFinished field Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/how_to_configure_the_template_app_for_ocpm_fasttrack Example of an EventLog table load script including the custom ObjectFinished field for defining process completion per object type. ```Qlik (QVS) EventLog: //Log table name: "EventLog" LOAD //ProcessAnalyzer information CaseID, "ActivityName" as ActivityType, Timestamp(ActivityStartTimestamp) as ActivityStartTimestamp, Timestamp(ActivityEndTimestamp) as ActivityEndTimestamp, //OCPM information obligatory ObjectType, PrincipalObjectType, ActivityOriginID, //OCPM information for further app configuration ObjectFinished //contains information for every CaseID if it is finished or not ``` -------------------------------- ### Helpdesk Example Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/use-an-event-log-created-with-mpmX/reuse_the_context_information_template This code snippet provides an example of how the Helpdesk data might be loaded, mapping specific fields to CaseID and other CaseDimension-like fields. ```qlik Left Join([CaseInformation_$(mvProcessDescription)]) LOAD distinct PurchaseOrderItem as CaseID, Supplier, Company, SpendArea, ProductClass, ProcessPathUniqueNo, City FROM [lib://helpdesk/HelpdeskEventlog.qvd] (qvd); ``` -------------------------------- ### Example 2: Inline Table Definition Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/use-an-event-log-NOT-created-with-mpmX/define_subprocesses_v2 This example shows an alternative inline table definition for subprocesses, featuring multiple activities for start and end points. ```qlik // Example 2: SubprocessDefinition_$(mvProcessDescription): Load * Inline [ Qualifier, StartActivity, IncludeStartActivity, MinMaxStartActivity, EndActivity, IncludeEndActivity, MinMaxEndActivity, TargetTime, TargetTimeOperator WIP, Take in charge ticket|Insert ticket, y, Max, Wait|Require upgrade, n, Min, 60, < WIP_old, Take in charge ticket, y, Min, Wait, n, Max, 45, > ]; ``` -------------------------------- ### Sample Configuration for P2P Process and 01qvdbuilder Scenario Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/create-an-event-log-with-mpmx/app_structure This snippet shows how to set the mvProcessDescription and mpmXvAppConfigAlias variables for a specific scenario. ```qlikview LET mvProcessDescription = 'P2P'; SET mpmXvAppConfigAlias = '01qvdbuilder'; ``` -------------------------------- ### Example 1: Inline Table Definition Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/use-an-event-log-NOT-created-with-mpmX/define_subprocesses_v2 This example demonstrates an inline table definition for subprocesses, including qualifiers, start and end activities, and target time constraints. ```qlik // Example 1: SubprocessDefinition_$(mvProcessDescription): Load * Inline [ Qualifier, StartActivity, IncludeStartActivity, MinMaxStartActivity, EndActivity, IncludeEndActivity, MinMaxEndActivity, TargetTime, TargetTimeOperator Payment Process, Record Service Entry|Record Goods Receipt, y, Max, Pay Invoice, n, Min, 60, < WIP, Take in charge ticket, y, Min, Wait, n, Max, 45, > ]; ``` -------------------------------- ### Helpdesk Example - Event Information Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/use-an-event-log-NOT-created-with-mpmX/reuse_the_context_information_template An example of event information for a Helpdesk scenario, demonstrating field renaming and dimension mapping. ```qlikview //Event information //Here you can add other event-related information (dimensions and values) User as ActivityUserName, if(WildMatch("User", '*Batch*','*1*'), 0, 1) as RealUser, if(Wildmatch(Activity,'*Delete*','*Change*','*Cancel*') > 0, 1, 0) as ReworkEvent, EventResource, //EventDimension1 CumNetWorth //EventDimension2 FROM [lib://helpdesk/HelpdeskEventlog.qvd] (qvd) where len(Activity) > 1; ``` -------------------------------- ### onlyFrontEnd - Step 1: Copy Template Source: https://help.mpmx.com/platform/qlik/advanced-features-and-configurations/pre-mining-configurations/mining-events/subsetloads Copy the template custom_logic_onlyFrontEnd.qvs into your ExampleProcess Folder. ```text custom_logic_onlyFrontEnd.qvs ``` -------------------------------- ### Count activities starting with 'Change' Source: https://help.mpmx.com/platform/qlik/troubleshooting Example of using a wildcard character in a set expression to count activities that begin with a specific string. ```qlik count({}distinct ActivityType) ``` -------------------------------- ### Required Account-Level Privileges Source: https://help.mpmx.com/platform/snowflake/security These are the account-level and reference privileges mpmX requires to function. The application will guide you through the initial setup, so manual SQL grants are not necessary. ```sql GRANT EXECUTE TASK GRANT USAGE ON WAREHOUSE GRANT SELECT ON TABLE GRANT SELECT ON VIEW ``` -------------------------------- ### Helpdesk Example - Case Information Source: https://help.mpmx.com/platform/qlik/use-apps-and-scripts/use-an-event-log/use-an-event-log-NOT-created-with-mpmX/reuse_the_context_information_template An example of case information for a Helpdesk scenario, showing distinct case IDs and mapping specific fields to case dimensions. ```qlikview Left Keep(EventLog) [CaseInformation_$(mvProcessDescription)]: LOAD distinct PurchaseOrderItem as CaseID, Supplier, Company, SpendArea, ProductClass, ProcessPathUniqueNo, City FROM [lib://helpdesk/HelpdeskEventlog.qvd] (qvd); ``` -------------------------------- ### Timestamp Format Example Source: https://help.mpmx.com/basics/Glossary An example of a timestamp format. ```text DD.MM.YYYY hh:mm:ss ``` -------------------------------- ### Example: Calling the mpmX-Algorithm Source: https://help.mpmx.com/platform/qlik/advanced-features-and-configurations/how_to_load_more_than_one_event_log This code snippet demonstrates how to call the mpmX-Algorithm, specifying parameters for scenario name, log table name, grouping table name, data connection, and QVD storage. ```qlik // :::::::::::::::::: CALLING THE mpmX-ALGORITHM ::::::::::::::::::::::: // // Here the mpmX-Algorithm is called. // Please insert four parameters as in the example below. // First parameter: scenario name // Second parameter: log table name // Third parameter: Grouping table name (leave empty '' if no grouping table is provided) // Fourth parameter: Data connection where you would like to save the (temporary) .qvd-files to // EXAMPLE: call mv_pa_initMining ('ScenarioName','EventLogTableName','GroupingTableName','FolderName', 'StoreQVDs'); //                                  1st parameter , 2nd parameter ,     3rd parameter,   4th parameter, 5th parameter call mw_pa_initMining('Users','EventLog','','$(DataConnection)','$(mvStorempmXModelQVD)',''); ```