MPM eXecution |
Scroll Previous Topic Top Next Topic More |
MPM eXecution uses a write-back-Extension to enable interactive working with the MPM apps.
1.Once the user edits data and saves it, it is sent to a writeback service.
2.The writeback service saves the data to the project specific database (MSSQL, Oracle, MariaDB, PostgreSQL or CSV File).
3.Once the data is successfully saved, the writeback service will send a reload trigger to Qlik Sense. This reloads the particular app in which the data was edited and the new data is made available to all users in that app.
A general documentation about the write-back solution is delivered with the purchase of the product.
MPM eXecution currently consists of five modules that can be used together or individually. The most interesting module is probably the integrated workflow management. MPM eXecution provides an integrated interface that allows you to distribute actions directly from the process mining platform to employees - rule-based, automatically from root cause analysis or directly from the user's front-end. In addition, you can interactively record process steps that are manual and not IT or system-based, and integrate them into the process and its further monitoring.
In this chapter...
Install mpm execution
Learn how to set up an infrastructure for MPM eXecution.
|
|
understand the general script structure
Learn how the MPM eXecution Template App' script is structured.
|
understand the general front-end structure
Learn how to sheets of the MPM eXecution Template App are configured.
|
deploy the mpm execution modules
Learn how to set-up and integrate the MPM eXecution modules in the MPM ProcessMining Template App..
|
build custom solution with mpm execution
Learn how to build your own solutions with MPM eXecution.
|