Tab 1 - App set-up & File Upload tab

When you first go to the mpmX Import Wizard link, you have a choice to create a new app or edit an existing app. Click on the "Create new app" button to get started.

The v2.5 Import Wizard has some changes from previous versions.

• Some of the fields and parameters are now on different tabs.
• Naming restrictions have been tightened.
• There are more data upload options.

1. Select the Template App

First, you need to select which mpmX Template App to use with the Import Wizard.

1. Notice that above the selection field is an App-Filter box. Only apps whose names have words that match the options listed in the App-Filter box will show in the dropdown.
2. A standard TemplateApp comes with the installation - called "mpmX TemplateApp Wizard". This could be copied, modified, and/or renamed to suit specific needs.

warning

Make sure that you chose an actual Template App for use in this field.

The apps that show up in this list will simply match the search patterns you configure, shown in the App Filter line above. This does not mean that every app will be compatible for use with the Import Wizard. So it is very important that on first setup you create and use a naming convention that identifies proper Template Apps to avoid any confusion.

Select a Template and App Filter bar

2. Define the name for your application

A good convention is to not use spaces in the name.

warning

These characters are no longer allowed to be used in the application name:

\ / : * ? " < > |

This avoids problems and makes the system more stable.

Name your app

3. Give your app a description

This does not have to be long, but should clearly identify the process type or any other important information.

Only after the description has been entered will you see the three options from where to upload your data.

Process description and upload options

4. Select the option from where to upload the event log

There are three new options to choose from. Depending on which one you choose different selections will be required to define which event log should be loaded and how it is accessed and what is displayed on the next tab (Event log configuration).

Regardless of which option you choose, the final two tabs (the Advanced Functionalities tab and the Generate App and Load Data tab) will operate the same.

Below are three tabs representing the three options you have to upload your data. Click on the preferred tab to see the correct instructions for that upload option.

In each example we use a Case-Centric Process Mining example. Here is a link where you learn more about how to create an Object-Centric Process Mining process with the Import Wizard.

Upload from Client

How to Upload from a Client

1. Select your folder connector

   • Click in the field to get a dropdown with the connection choices.
   • Choose the connection where your csv file is stored.
   • Click "Upload local file"

     

     Select your folder connector

2. Find your data file

   • Navigate to the folder where your csv file is stored, select the event log, and click "Open".
   • In our example it is stored in the mpmX_data/event_logs folder.

     

     Select your event log

3. Adjust your parameter settings under "Upload local file".

   Here you can set some parameters that were in previous versions on the Event Log Configuration tab.

   • Which delimiter sign is used in the csv: Comma, Semicolon, or Blank (space)
   • Whether the field names are included in the csv file or the header: Yes or No
   • Which line break control is used (like under Linux or Windows for example): CR (Carriage Return), LF (Line Feed), or both
   • Which quote option is used when content is in columns: Auto-Detect, Single Quotes, or Double Quotes
   • The name of the Eventlog file that you selected is automatically shown.

The wizard will try to automatically detect the correct settings, but you can adjust them if required as they may not always be detected automatically. All of these settings ensure that the file gets read in the correct way.

Upload from Client - Select Local file

4. Click "Continue" to preview the selected event log.

Now you will be taken to the Event Log Configuration page (for Upload from Client).

Load from Server

How to Load from a Server

1. Select the source connection

   • Select the source connection in the dropdown.
   • Click "Import via data connection"

     

     Load from Server

2. Select the data file

   • Navigate to the folder on the server where your event logs are stored
   • From the Select file type dropdown select the file type (qvd, csv, or Parquet)
   • Select the event log
   • Click "Apply Selection"

     

     Select data file and Apply Selection

3. Click "Continue" to preview the selected event log.

   

   Click Continue to confirm your choice

Now you will be taken to the Event Log Configuration page (for Load from Server)

Load from Database

How to Load from a Database

We will start off with some preliminary information. If this is not of interest, scroll down to the next section - How to Load from a Database. We currently support Snowflake and Postgres and will be expanding the database types in the future.

Correct Database Setup and Configurations

The standard installation of QlikSense offers about 40 database connections to different data sources. The Import Wizard only works with databases which support SQL, so mpmX filters on the Qlik ODBC connector package to define the subset of connections which are ODBC compliant and to relational databases or data warehouses which support SQL. We currently support Snowflake and Postgres.

Depending on how the connection is defined by the QlikSense administrator and the technical possibilities of the backend, we can sometimes preassign the correct values, otherwise you need to select them manually.

Here is some technical background information.

• In addition to a Database/Datawarehouse connection, we need the fully qualified name of a table which must always consist of the three parameters and the notation database.schema.tablename. Optionally, a warehouse, role, user, password, etc may be used.
• Some backends (like Snowflake) with the specific Qlik connector can establish a connection without predefined database and schema values. In that case the correct one must be selected from the list, because depending on the permissions of the current user, there may be more than one option to select from.
• Other backends (like Postgres) do not allow Qlik connections without defined database and schema values in the connection. If a user needs access to multiple databases or schemas, then the Qlik admin must provide more connections.
• The Import Wizard first checks the content of the connection definition on the Qlik server.
  • If it finds values for the database (the names for this information differ depending on the type of connection) and schema, we use these values as a preselection in the dialog. With Postgres these are the only working values and in other scenarios the most likely values are presented.
  • If it finds no value, the fields stay empty and the user must select the database. Then mpmX's Qlik backend logic tries to determine the available schemas based on the selected connection and database. These are then presented for selection. After the selection we proceed with the table selection like in the scenario when both values are preselected.
  • If all three parameters (Database Connection, Database Name, and Schema) are defined, then mpmX's Qlik Backend Logic determines the available tables, which are then automatically chosen for selection.

How to Load from a Database

1. Select your Database connector

• Once you select "Load from Database" a dropdown window will appear
  • Select the database connector

    

    Select Database Connector

2. Select the Database & Schema

• The Database & Schema needs to be selected. It will load automatically if there is only one option.
• As mentioned above in the preliminary information, sometimes you have to manually select the database and schema and in other circumstances it may automatically be filled in.

  

  Select Database and Schema

3. Select the Table or View

• Select the event log table from the dropdown menu

  

  Select the Event Log Table or View

4. Click "Continue"

Now you will be taken to the Event Log Configuration page (for Load from Database)