mpmX Help Documentation

 

Policy update:

 

Update first on test server, after a certain time period, without detecting major issues, update the production server.

To reduce problems during the upgrade, we recommend:

1.Notify all relevant users to test their apps after the update and adapt their script data connection to the new script-version and provide them the release notes so they can adapt their app accordingly.

2.Define a certain test period after which the production server is also updated, regardless if all users tested their app or not.

3.After the update on the production server the apps from the test server have to be migrated to the production server to replace (update) the apps there.

 

mpmX extension update:

 

1.Export the old extensions to have them as backup.

2.Delete the old extension versions via QMC

3.Import the extension bundle as described in Install mpmX

 

 

 

mpmX script update:

 

1.Create a new folder within the “mpmX_scripts” and name it as the actual release version (i.e. “V2.3.0”).

2.Save the new unzipped .qvs files in this folder.

3.The data connection in the App should point to this “mpmX_scripts” folder that includes folders for each script version.

 

mpmX Template App update:

 

1.Replace or upgrade the Template App.

2.If you are using the the Template App from the v2.3.0 release and the latest scripts, then you need to add these two lines:

oSET mpmXvVersion = 'V2.3.0';

oSET mpmXvScripts = 'lib://mpmX_scripts/$(mpmXvVersion)/';

 

Master Items repository update:

 

1.Create a subfolder with your mvProcessDescription in mpmX_repository

2.Save the repository (mpmX_masteritems.csv) and translations (mpmX_masteritem_translations.csv) under mpmX ProcessMining/mpmX_repository/[mvProcessDescription]/

3.Copy the remaining files from mpmX_repository/_templates/

 

Translations installation:

 

1.Save Translations.csv under mpmX ProcessMining/V2.3.0/mpmX_repository/.

 

How to merge custom development with a new development:

There are multiple scenarios when you want to update mpmX. Updating the scripts is straight forward as you do not overwrite the previous release versions. Updating the extensions (which means overwriting former versions) is normally no issue, they can be used in previously released mpmX Template Apps as long as the Release Notes do not indicate otherwise. Updating the mpmX Template Apps can thus be more demanding as this is where most customization takes place.

 

To get the new template app functionality, you have to decide if you want to update your process mining app with the new template app functions or if you want to migrate your customizations to the new template app. To decide which way is best consider the following:

 

1.Custom changes in the process mining app compared to the new template app are mainly in the script or on separate sheets.

a)The best way to update to the new template app is to copy the relevant script parts and sheets (copy sheet function) from your existing app to the new template.

 

2.Custom changes are mainly in the base sheets in the template app.

b)Adapt your process mining app's data editor script following the instructions in the Release Notes.

c)Use the new mpmX scripts to load your process mining app.

d)Import the new master items and copy the new sheets or new charts from  new template app to your process mining app - refer to the Release Notes.

e)You may also have to create some new variables if they are used in the measures - refer to the Release Notes.