SHARE YOUR IDEAS

At the moment, the Namespace name must be changed for every source table separately. Source tables with the same Namespace are shown in a group. Change of the Namespace name for a group saves a lot of clicks and time.

For some reasons and governance rules an absence management must be possible. Therefore I suggest that the Process Mining Admin can add the functional right to a second user. I also suggest to add this as a self service option to minimize/reduce m...

if a table has an empty description, an description in another language should be extracted and provided in the ARIS Process Mining UI.

Description: Scheduling and triggering the execution of an externally implemented data extraction should be defined in APM much like with the built-in connectors Solution: Provide scheduling and last export information persistence for API connecti...

For any process mining analysis, a process flow component is a basic need. The fundamental requirement is to select the activities (start & end) directly in the FE (dashboard), being able to change them, having in-memory recalculations. We see...

E.g. DD/MM/YY instead of MM/DD/YY Current fixed setup is confusing for the users.

Not having has a negative impact on the UX

Next to cases deletion, event deletion would be useful.

At the moment a user needs the functional privilege of "User admin" to add system integration or ARIS integration. This right allows also the administration of users. I suggest to separate that into two functional privileges. This gives better co...

re-use of existing (already loaded) data tables can overcome some of the limitations we currently encounter: a. the fact that we can only load 1 reference model per data set. creating a 2nd data set based on the same loaded data tables will reduce...