Version 10.3

Release Date: March, 2025

Features

Task mining

Process mining enables us to identify operational improvements in end-to-end workflows. For instance, in a procure-to-pay process, we might identify the task “Analyze Requisition Request” as a bottleneck. To eradicate this bottleneck, we need to understand the specific details of the activity. It could be that the task involves steps performed across one or more software applications such as opening URLs, clicking buttons, filling forms, copying texts, and so on. To enable us to drill down into these steps done and from there, into the application windows and UI elements that are involved in these steps, we are excited to introduce Apromore Task Mining. To learn more, see Task Mining.

Lite Dashboards

Lite Dashboards enables us to create an overview of the performance of multiple processes, and to easily share these overviews with other users. A Lite Dashboard consists of widgets that display KPIs or metrics. Each widget may refer to a different event log. In this way, we can create a dashboard that presents relevant metrics across any number of event logs. To enable quick insights, we can also set a lite dashboard as our landing page after logging in to Apromore. To learn more about creating a lite dashboard, see Create a lite dashboard.

Process Views Inventory

A process view defines a process map that can be visualized in Process Discoverer, with customized settings such as:

• A log filter e.g. retains all cases with a case duration of 12 days or more

• An overlay, e.g. show the average duration overlay

• A layout option, e.g., showing the process map in the backbone visualization

To make it easier for users to see all the available process views in their workspace, we have introduced a dedicated page, called the Process Views Inventory. This page provides a list of all process views available to the user. This list can be filtered based on the name of the view, the event log from which the view is derived, and any keywords in the description of the view. To learn more, see Access process views inventory.

Filter Enhancement

Improved attribute event-level filter

Attribute event-level filters allow us to filter our process based on a single event attribute. For example, we can filter all “Verify Claim” events. However, there are situations where we need to define the filter on multiple conditions. For instance, we may want to retain all “Verify Claim” events performed by the Claims Officer that took more than 2 days. To accommodate these more complex scenarios, we’ve enhanced the attribute event-level filters to support secondary conditions. To learn more, see Event > Attribute filter.

Copilot Enhancements

Copilot suggests sample questions

To enable us to understand the capabilities of Apromore Copilot, the Copilot welcome message now displays sample process mining questions that it can answer. To see the questions, click the Copilot icon in Process Discoverer. To learn more, see Copilot for process discovery.

Copilot answers questions about activity automation

We have enhanced Copilot to accurately answer questions involving the full or partial automation of an activity. To learn more, see Copilot for simulation.

Copilot answers multiple what-if scenarios in one question

We have improved Copilot so that it is capable of addressing multiple what-if scenarios within one query. For instance, let us ask “What if demand increased by 20% and I added 2 FTEs to the “Purchasing Agent” role? Then what is the impact of this?”. To learn more, see Ask multiple what-if scenarios within one query.

Copilot highlights elements referenced in its answer

For easy discovery, when Copilot returns answers that involve elements in the process map, Copilot highlights the elements. To learn more, see Copilot for process discovery.

Copilot formats answers in rich text

To enable us to distill key information from the Copilot response, the Copilot formats its answer in rich text. The following formatting is performed:

• Answers are formatted in tables where applicable.

• Key information appears in bold.

• Bullet points are used to itemize a list of answers.

To learn more, see Copilot for process discovery.

Copilot returns concise and precise answers

To enable us to easily identify answers, Copilot responds directly and clearly.

To learn more, see Copilot for process discovery.

Copilot offers the ability to expand or contract its window

We can now expand or contract Copilot’s window. We can choose to expand it horizontally or vertically. To learn more, see Change Copilot window size.

Compliance Center Enhancements

Add and manage compliance items states

Tracking compliance items through their lifecycle is essential for ensuring operational integrity. For instance, a bank might initially mark its anti-money laundering control as “Draft” during initial evaluations. Once the control proves effective, it is updated to “Validated”. To enable us to tag compliance items at different stages of their lifecycle, we can now assign a state during creation. To learn more, see Manage compliance items states.

Create controls using filters

To create more flexibility when creating controls, we now have the option of creating controls with filters. When creating a control with a filter, cases that meet the filter criterion are considered the violating cases. For instance, if the filter retains cases that took more than 2 weeks, the filter result would be the cases violate the control rule. To learn more, see Create controls using filters.

Streamlined process for assigning a control to a log

Previously, controls created without a control template couldn’t be assigned to the log until the template was added. Now, we can assign a control to the log even if a control template has not been pre-defined. When assigning the control to the log, we are prompted to create a control template, which is then automatically saved with the control. To learn more, see Assign controls without a template to log.

Email notifications for compliance check outcome

To enable us to respond promptly to compliance check outcomes, we can now opt-in to receive email notifications once a check is complete. We can also specify whether or not to receive in-platform or email notifications on specific compliance items. For instance, we may want checks on the “Overdraft control” to send notifications while checks on the “Quick payment control” to not send notifications. To learn more, see Email notifications for compliance check outcome.

Link compliance items to models and their elements

To enable more robust modeling, we can now link compliance items to models in the BPMN Editor. In addition, we can link compliance items to specific elements of the BPMN Editor. To learn more, see Link compliance items to models elements from the BPMN Editor.

View violating cases from a compliance table

When reviewing a compliance table that lists violations by case, we may want to investigate the underlying reasons for each breach. To allow us to perform these investigations, we can drill down into a specific case directly from the compliance table. To learn more, see View violating cases from a compliance table.

Improvements and Bug Fixes

Classic dashboard

• Fix: Resolved an issue where users without “Create compliance dashboard” permissions could not see compliance widgets in a dashboard, irrespective of other dashboard permissions. Now, users who have permission to view a dashboard can view compliance widgets.

• Fix: Resolved an issue where, after renaming one log in a multi-log dashboard, reopening the multi-log dashboard would display one of the log’s details twice. Now, the dashboard correctly shows both logs, reflecting any new log names.

• Fix: Resolved an issue where a dashboard does not display the compliance result if the control rule involved a “Eventually followed by” template.

• Fix: Resolved an issue where loading a dashboard template containing compliance widgets on a log with no compliance items resulted in an error. The dashboard now correctly displays “No data to display”.

• Fix: Resolved an issue where a saved dashboard that contains a compliance table/chart, does not show the table/chart data when reopened. Now, the dashboard correctly displays the tables and charts with the compliance result.

• Fix: When a dashboard table is downloaded as a CSV, the timestamp and duration values are split into separate cells for date and time, causing misalignment in the exported CSV file. Now, all columns maintain alignment and match the displayed format in the dashboard.

• Fix: Resolved an issue where “Cases” tables downloaded from a dashboard as a CSV converts colon (:) in the values to underscore (_).

• Fix: Resolved an issue where the value displayed when hovering the mouse on the Role utilization chart was inconsistent with the value on the Y-axis.

• Fix: When a user applies a calendar in a log, a dashboard showing a heatmap does not update its values. Now, applying a calendar updates all dashboard widgets including heatmaps.

• Fix: Resolved an issue where the user could not change the page of compliance tables in a dashboard.

• Fix: Resolved an issue where creating an “Event attribute overview” table caused the default event attributes (activity, resource, and role) to disappear from the attribute list in a chart widget. Now, default event attributes always appear when selecting attributes in a chart.

• Fix: Resolved an issue in dashboard slicing that prevented retrieval of all event and case attribute values from the log. Now, every available attribute value is displayed for selection based on the chosen attribute.

• Fix: Resolved an issue where dashboard tiles incorrectly display 0 cases after a filter template is applied.

• Fix: Resolved an issue where, when creating a dashboard table with event attributes, a selected attribute would disappear from the available options after saving and reloading the table. Now, all attributes remain visible for selection.

Filters

• Improvement: For better readability, when creating a timeframe filter, the time range displayed has been changed from YYYY.MM.DD hh:mm:ss i.e., 2020-01-01 00:00:00 to DD MMM YY, HH:mm, i.e., 1 Jan 2020, 00:00.

• Fix: Resolved an issue where saving a filter from the dashboard and applying the filter again returns an invalid filter error. Now reapplying a filter saved from a dashboard works without errors.

• Fix: Resolved an issue where views created using filters with the reset counter are not correctly shown after closing the view and reopening.

• Fix: Resolved an issue where the process map displayed does not get updated after the user defines an event-level path filter.

• Fix: Resolved an issue where saving an event filter with no matching events returned an error. Users can now create and save filters even when no events meet the specified condition, with the filter returning the full log.

• Fix: Previously, when a created filter criterion is not valid, the filter simply returns an invalid filter which is not informative. Now, the filter criteria return the reason the criteria are invalid.

• Fix: Resolved an issue that caused the event level between filters to not display the full list of activities when one or more filter criteria have been removed or added.

• Fix: Resolved an issue in the “Load Filter” window so that when it’s reopened after being closed with the “Show all my filters” option selected, it now displays the correct set of filters that match the checkbox state.

• Fix: Resolved an issue where the secondary attribute list sometimes included values that didn’t match the selected primary attribute. Now, the list only shows secondary values that have one or more matching cases with the chosen primary attribute.

• Fix: Resolved an issue where downloading a filter with “>” in its name downloads an empty zip file. Now, a user can download a filter successfully irrespective of the characters in its name.

• Fix: Resolved an issue that caused block filters to be greyed out when created in dashboards. Now, users can create and apply block filters in dashboards alongside other filter types.

Compliance Center

• Improvement: When defining compliance rules, we have added the “Start” and “End” nodes to the attribute drop. This means that we can now create rules from the start and/or end nodes. For example, we can create a rule that checks the “Start” node is directly followed by an activity P.

• Improvement: When assigning a log to a control that does not yet have a control template configured, we can now define control templates directly from the “Assign control to process log” window.

• Fix: Resolved an issue where, when a user creates a population filter from a saved filter to create a control and the filter is subsequently deleted, running a compliance check would result in the error message: “An unexpected error has occurred.” Now, the user will receive a message indicating that the population filter used in the control has been deleted.

• Fix: Resolved an issue where importing a compliance register returned an unexpected error if the register contained the “State” column. Now, users can import a compliance register successfully with the “State” column.

• Fix: Resolved an issue where a compliance check fails after the log gets updated using a delta upload. Now, further compliance checks after a delta upload on a log run successfully.

• Fix: Resolved an issue that sometimes caused the creation of control to take a long time before failing.

• Fix: Resolved an issue where creating two compliance items in quick succession caused the second item to inherit details from the first. New compliance items are now open with empty fields as expected.

• Fix: Resolved an issue that caused the Case ID column to not appear when displaying a non-compliance table.

• Fix: When a user without the necessary compliance access rights updates a log that is attached to a control, the compliance check will not run. Now, regardless of the user’s access rights, any log update triggers a compliance check.

• Fix: Resolved an issue where a user, who owns a risk could not link the risk to a control shared as a viewer. Risk owners can now successfully link the risk to controls even with viewer permissions to the control.

• Fix: Resolved an issue where a compliance register with over 400 items failed to import. Now, a compliance register can be uploaded successfully irrespective of the number of items in it.

• Fix: Resolved an issue where controls, risks, or obligations are where the name column is missing in the register import file. Now, when the name, description, or type value is missing in the Register import file, the compliance item is not created.

• Fix: Resolved an issue where rows in the compliance report appear with random numbers rather than the name of the compliance item used in generating the report.

• Fix: Resolved an issue that sometimes caused cases that were violated on the last compliance check that did not appear in the compliance report.

BPMN Editor

• Improvement: When merging models with unsupported BPMN elements (e.g., pools, lanes, data objects, intermediate events), it returns an unclear error message. Now, the error message states: “Unable to merge these models. The models may only include start events and end events, simple activities, and parallel and decision gateways. Pools, lanes, data objects, and intermediate events are not supported.”

• Fix: Resolved an issue where attachments in the new BPMN Editor UI changed to “New Attachment” or “New Attachment 1” rather than the attachment’s original name. Now, attachments in the new BPMN Editor UI maintain their initial names.

• Fix: Resolved some UI bugs in the properties panel of the BPMN Editor.

• Fix: Resolved an issue that caused model labels to appear squashed upon import. Imported models now display clear, legible labels in the BPMN Editor.

• Fix: Resolved an issue in the BPMN editor where expanding attachments extended beyond screen bounds, interfered with other elements, and prevented users from contracting them. Now, attachments expand only to the allowable space, allowing users to easily reduce their size.

• Fix: Resolved an issue where opening a model only displayed the start event and duplicates didn’t reflect recent edits. Now, users see the complete model immediately and can save their changes without encountering access errors.

Access Management

• Improvement: When a model is opened in View mode, the “Attachments” and “Simulation” panels are not visible so the users cannot perform operations.

• Improvement: When deleting a user who owns one or more metrics, the delete user window previously displayed the assets without the corresponding metric icon. We have now added the metric icon for a more informative and consistent display.

• Fix: Resolved an issue where changing a user’s first name removed the user from any assigned group.

• Fix: Resolved an issue where the Edit icon was erroneously displayed on dashboards shared with viewers. Now, when a user with Viewer permission opens a dashboard, the Edit icon is no longer visible.

• Fix: Resolved an issue where deleting a user/group assigned as a property caused an error. Now, when a user/group is deleted, the corresponding property is set to null.

• Fix: Resolved an issue where, during the transfer of a KPI from user A to user B upon deletion of user A, user B encountered an error when editing and saving the KPI. User B can now successfully edit and save the KPI.

• Fix: Resolved an issue where draft models were generated for users with “Viewers” permissions. Now, if a user with “Viewers” permission opens a model, no draft model is created.

• Fix: Resolved an issue where the introduction of access rights in the compliance center caused an unexpected error when a compliance item is deleted. Now, users can delete a compliance item without issues.

• Fix: Resolved an issue where loading a saved view that displays a BPMN model disabled the “Save BPMN Model” option. Now, after retrieving the saved view, the “Save BPMN Model” option remains enabled, allowing the model to be saved directly.

• Fix: Resolved an issue that caused attachments in the BPMN Editor to be misaligned with the task. Now, the attachment is placed in alignment with the task it was attached to.

• Fix: Resolved an issue where transferred assets were not fully accessible—logs are hidden and errors occurred in accessing KPIs and metrics. Now, transferring asset ownership after deleting a user correctly allows the new user to seamlessly access all transferred assets and functionalities.

• Fix: Resolved an issue where a user with viewer-only rights on a folder—but with editor/owner rights on a model within that folder—could not save edits to the model. Now, such users can save changes to the model without encountering access errors.

• Fix: Resolved an issue where right clicking a log with “Restricted Viewer” rights resulted in all options being disabled. Now, only the privileges permitted by the “Restricted Viewer” role are enabled, while the others remain disabled.

• Fix: Enhanced the shared KPI/Metric behavior so that when the log isn’t shared along the KPI, the edit option next to the filter in KPI population, condition, and metric is disabled, preventing the user from editing KPI/Metric based on the log details.

• Fix: Resolved an issue where transferring ownership of a KPI returned an error. Now a user can successfully share a KPI with another user as the owner while removing themselves from the KPI.

Copilot

• Improvement: Previously, when a user asked a performance-related what-if question, Copilot compared the total cycle time (processing time plus waiting time) before a change with only the processing time afterward. Now, it compares processing time before and after the change, providing more accurate insights into performance variations.

• Improvement: The Copilot can now correctly answer what-if questions that involve multiple scenarios. For example, what is the impact of increasing demand by 20% and adding 2 FTEs to the “Purchasing Agent” role

• Improvement: We have now improved Copilot to automatically determine the kind of questions being asked. Users do not need to toggle on Simulation or Discovery when interfacing with Copilot.

• Improvement: We can now ask the Copilot questions about roles and resolves while being in the activities overlay.

• Improvement: For flexibility, we can now increase/decrease the size of the Copilot width and height.

• Fix: Resolved an issue where the Copilot returned answers about activities when asked about roles or resources.

ETL

• Retired: The MySQL and PostgreSQL extractors in ETL have been retired and are no longer supported.

• Fix: Resolved an issue where CSV files extracted from an S3 connector, causes a pipeline schedule to fail. Now, the pipeline runs successfully when a CSV file is extracted via the S3 connector.

• Fix: Resolved an issue that now allows a user to add the subtraction of two timestamp columns to another timestamp column in the ETL pipeline.

• Fix: Fixed an issue where rows with at least one empty column are not deduplicated during a delta upload.

• Fix: Resolved an issue where, after user A creates a pipeline and is deleted—transferring all assets to user B—the pipeline resulting logs become inaccessible, and a new pipeline run fails. Now, user B can fully access the assets and can perform all actions previously available to user A.

• Fix: Resolved an issue in the pipeline’s transform stage where deleting a newly created column did not remove its associated rule, causing the rule to affect other columns. Now, deleting a column automatically nullifies its rule across the dataset.

• Fix: Resolved an issue where there were some missing columns when joining tables in an ETL pipeline. Now, all columns from tables are correctly merged and accessible in the Transform step.

• Fix: Resolved an issue in the Extract step where changing a column’s datatype from Real to Integer converted values to NULL. Now, the values are rounded to the nearest integer as expected.

• Fix: Resolved an issue that caused the first run of a pipeline to fail.

Simulation

• Improvement: To prevent divergent simulation results, the deterministic mode is turned on by default when a user saves a model with simulation parameters. Max branching probability is now also set to 1% from 5%.

• Improvement: Changed the “Cases in the queue at the start of the simulation”, “Cases to exclude from the start of the simulation”, and “Cases to exclude from the end of the simulation” inputs from percentage dropdowns to integer textboxes (default 0), enabling precise numerical entry.

• Improvement: If the simulation fails to complete in the background, the Copilot may return wrong answers. We have improved the Copilot to mention it could not successfully run the simulation scenario required to answer the question. A different question should be asked.

• Fix: Resolved an issue where adding a role group to the simulation parameters without assigning any roles—despite it being linked to a task—resulted in an “Internal server error” during simulation. The simulation now returns a validation error specifying that a role group must have roles assigned.

• Fix: When defining a priority in the simulation parameter, the list of possible operators displayed was incomplete. Now, the correct list of operators for each of the attribute types is displayed.

• Fix: Resolved an issue in the simulation engine where overlapping case arrival timetables produced a “Case arrival timetables overlap” validation error rather than an “Inter arrival time slot overlap” validation error.

• Fix: Resolved an issue in which the “Cases in Queue at Start” value was not saved in Advanced settings. Now, all user-entered values—including those for cases in a queue and cases to exclude—are properly retained when simulating the model.

Properties Manager

• Improvement: When creating a property, we now select “Governance” by default rather than “Metadata” because governance properties are more frequently used.

• Improvement: When a user changes the type of a saved property, a warning message now appears to inform them that the existing value will be deleted.

• Fix: Resolved an issue where when a user creates a property with the Predefined option type, deleting the first item causes the item to move to the subsequent field. Now, once the first option is deleted, the other options remain as is.

• Fix: Resolved an issue where changing the “Allow user to add options” of a predefined options property without saving resulted in a warning that the property was changed. Now, the warning only appears when the user changes the option and saves the change.

• Fix: When a user adds or removes some properties in a model without saving and publishes the model, the properties appear empty in the published model. Now, when publishing a model without saving changes, a warning message appears that changes will be lost.

• Fix: When creating a property, the Create button appears enabled even though all mandatory fields have not been filled. Now, the Create button is only enabled after all mandatory fields are filled.

Others

• Improvement: We have enhanced readability by displaying variant node statistics in the Variant Comparison tool on separate lines.

• Improvement: Files and folders in the Portal are now sorted using alphanumeric ordering rather than just alphabetic, for a more intuitive arrangement.

• Improvement: Enhanced error messages in the Case Inspector and Case Variant Inspector. Now, when the activity limit is exceeded, the error message states, “The selected variant/case has more than X activity instances and cannot be visualized”.

• Improvement: We can now save KPIs even if no cases initially meet the KPI condition. If the log gets updated, the KPI value will be automatically recalculated and updated.

• Improvement: We have changed the position of the quick case filter in Process Discoverer so that the Copilot can be expanded fully on the right.

• Fix: Resolved an issue that caused the log animator to continue beyond the log timeframe.

• Fix: Resolved an issue where the user could not download multiple logs and/or a model when the language in Portal is not English.

• Fix: Resolved an issue where a user’s assigned groups were not selected. Now, when a user’s groups are displayed, the ones they belong to are indicated with a checkmark.

• Fix: Resolved an issue causing the “Add new” button in Portal to sometimes disappear. Now, the “Add new” button always remains visible.

• Fix: Resolved an issue where viewing predictions on a log displayed an error message. Now the user can apply a predictor to a log and view the predictions.

• Fix: Resolved an issue that caused the Variant comparison tool to throw an error when the user uploads a filter using a JSON file.

• Fix: Resolved an issue that caused the log download preparation to fail.

• Fix: Resolved an issue where usernames with apostrophes could not be deleted. Now, such users can be deleted successfully.

• Fix: Resolved an issue that sometimes caused the “Animate log” not to work when a model and a log are selected together.

• Fix: Optimized the process of assigning/unassigning access rights of users, leading to improved performance.

• Fix: Resolved an issue with event log imports where switching the timestamp type altered the date format. Now, Apromore preserves the original day/month/year format and allows manual adjustments without parsing errors.

• Fix: Resolved an issue where downloading the Case Variant Inspector table retrieved the wrong file (the Case Inspector table). Now, downloading the Case Variant Inspector table correctly downloads the table.

• Fix: Resolved an issue in Process Discoverer where using the filter shortcut for filtering arcs sometimes returned incorrect results. Now, the shortcut correctly applies the right filter.

• Fix: Resolved an issue in Process Discoverer where applying an event attribute filter—either via the shortcut (ALT+CTRL+Right click) or through the Filter icon—did not work correctly when a user-defined backbone layout was applied. Now, the filter properly retains only events matching the selected activity, regardless of the layout.

• Fix: Resolved inconsistent icon behavior in the “Recent” and “Favourites” sections. Now, logs and models with restricted permissions display the correct icons—matching their appearance in Portal.

• Fix: Resolved an issue that resulted in empty emails being sent. Now, the email contains a list of relevant updates for the user.

• Fix: Resolved an issue where reopening a saved “Relative Case frequency” view in Process Discoverer incorrectly displayed the “Case frequency” overlay. Now, the view correctly displays the Relative Case frequency” overlay.

• Fix: Resolved an issue where emails are sent even after the user has read the notification on the platform. Now, when a notification has been read on the platform, the user does not receive an email any longer.

• Fix: Resolved an issue where users’ sorting preferences were lost when navigating between folders in Portal. Now, the chosen sorting order in a folder persists if the user moves to another folder.

• Fix: Resolved an issue where Japanese characters appear jumbled after importing a log with Windows-31j encoding. Apromore now correctly supports Windows-31j encoding and its characters are displayed correctly in both Process Discoverer and dashboards.

• Fix: Resolved an issue that caused log exports to be in UTF-8 encoding even though Windows-31j. Apromore now supports Windows-31J for log exports.

Version 10.2

Release Date: November, 2024

Features

New properties manager for process models

Capturing precise information about BPMN process models and their elements is essential for effective management. Take a payment processing workflow in a bank as an example: the model can define properties such as the account manager’s name, the compliance status, and required audit types to ensure the process adheres to protocols. Additionally, specific elements such as tasks, decision gateways, and sequence flows can have properties for better clarity. For instance, an “Approve Funds” task might include properties such as an approval checklist or approval authority. To capture detailed information about models and their elements, Apromore 10.2 introduces the Properties Manager.

The Properties Manager allows us to define and manage properties for process models and their elements. Properties store metadata or governance information about the BPMN model or BPMN model element. In BPMN Editor, we can assign and view the properties assigned to the model and its elements. To learn more, see Manage properties.

Access to S3 bucket via Secure File Transfer Protocol (SFTP)

It is now possible to drop files in the S3 bucket of your tenancy via SFTP. The files dropped in this way may be used in a pipeline via the S3 Connector.

For details on how to access your tenancy’s S3 bucket via SFTP, please raise a ticket in the support desk.

User Management Enhancements

Permissions for deleting models and logs

To enhance control over user interactions with logs and models, we have added two new permissions specifying whether a role can delete a log or delete a model. The new permissions are:

• Delete logs: When disabled, the user cannot delete logs in their instance.

• Delete model: When disabled, the user cannot delete models in their instance.

To learn more see Create a new role.

Permission for creating folders

To provide granular control for folder creation, we have added a permission called “Create folders”. This permission determines whether a user can create new folders in the Workspace. To learn more see Create a new role.

ETL Enhancements

Find and Extract capability in the Transform Step of a data pipeline

We have added a new operation in the Transform Step of the data pipeline that allows us to extract a substring from a column based on a regular expression. For example, if a column contains timestamps, we can extract and populate a separate column with just the date component. Similarly, given a column that contains email addresses, we can create another column that contains the domain names of those email addresses. To learn more, see Transform data.

Custom behavior for merging rows with duplicate values

When scheduling a data pipeline, Apromore automatically removes duplicate rows. Duplicate rows are rows that have identical values across ALL attributes in the event log. However, there are scenarios where rows should be considered duplicates even if only their default attributes are identical. These default attributes are:

• Case ID.

• Activity.

• End timestamp.

• Start timestamp (if it exists).

• Resource (if it exists) and,

• Role (if it exists).

Other columns are non-default attributes. In Apromore 10.2, we can specify that rows with identical values on the default attributes should be treated as duplicates and therefore merged, even if these rows differ on some of the non-default attributes. To learn more, see Merge rows with duplicate values.

Compliance Center Enhancements

Share compliance items

To enable seamless collaboration, we can now share compliance items with other users of our instance. To learn more, see Share compliance items.

Link compliance items to models from the Portal

We can now link compliance items to process models and view these associations directly in Portal. To learn more, see Link compliance items to models from the Portal.

Link compliance items to models from the Compliance Center

We can link compliance items with process models in the Compliance Center. To learn more, see Link compliance items to models from the Compliance Center.

Generate compliance report

After linking models or logs to compliance items, we can generate a compliance report that displays information about the linked model or log for a given period of time. The report shows:

• Logs or models that are actively linked to compliance items at the time the report was generated.

• Linkages that were established between the logs/models and compliance items during the chosen reporting period.

To learn more, see Generate compliance report.

Display compliance results for a specified timeframe in a table/chart

When running multiple compliance checks, we may wish to display a compliance table/chart that focuses on results found within a specific period. For instance, imagine a scenario where an event log was updated today and a compliance check was run. We can display only the compliance events that were discovered today rather than those earlier discovered. This can be done by specifying a timeframe in the compliance table/chart. To learn more, see View result as a table.

Filters Enhancements

Improved timeframe event-level filters

Earlier, Apromore allowed only a simple event-level filtering within a specific timeframe. There however are complex situations where we need to specify other nuances. For instance, we may want to retain only activity instances/events that were active within a timeframe, or filter based on well-known periods (e.g., Q4 2020). Additionally, we often need to define relative time periods such as “the last quarter” without constantly updating filters as time progresses. Also, there are situations where after applying the initial filter, we need an additional secondary filter. In Apromore 10.2, we can now perform all these in the timeframe event filter. To learn more, see Event > Timeframe filter.

New Frequency event-level filters

We now have a new frequency event-level filter. This allows us to dice an event log based on how often activities or other attributes in the log occur. The frequency event-level filter can particularly help us identify hidden patterns such as rework and bottlenecks. For instance, we can retain only activities that were repeated within a case, giving us a clear picture of how often and where rework occurs in the process. To learn more, see Event > Frequency filter.

New performance event-level filters

During waste analysis, it may be useful to find the activity-processing bottlenecks or high-cost activities. We have now extended the event filters to include a Performance filter, enabling us to filter events based on their duration or cost. To learn more, see Event > Performance filter.

New path event-level filter

In some situations, understanding what happens immediately before or after a particular event can reveal critical insights about the process. For example, we may want to display all the events that directly follow “Close Assessment” in the process. This will reveal what possible activities that happen after closing a claim assessment. On the other hand, we may be interested in events that lead to a specific event. For instance, we may want to see the roles that are handed over to the Product Manager. To create such filters, we can use the new path event-level filter in Apromore 10.2. To learn more, see Event > Path filter.

Improvements and Bug Fixes

ETL

• Fix: Resolved an issue where the first scheduled run of an hourly pipeline did not execute in some cases.

• Fix: When a pipeline component is edited, data pipelines using that pipeline component crash. Now, editing a pipeline component does not crash a dependent data pipeline.

• Fix: When a referenced column was removed in the Transform step, the header was removed, but the data from the deleted column was still displayed, causing incorrect data display under the remaining headers. Now, both the removed column and any referencing columns are fully removed.

• Fix: When a user deletes pipeline components linked to a data pipeline, the pipeline component still appeared in the manage data pipelines window and cannot be deleted in some cases. Now, the user sees an empty dataset when they view the pipeline component, they see a reason message on refresh, and they can delete the pipeline component without issues.

• Fix: When a user shared a data pipeline with a linked component, the user could not save changes to the data pipeline. Now, both the owner and shared users can refresh, extract components, and save the data pipeline successfully.

• Fix: When a user creates a pipeline component from an S3 connector, a data pipeline that utilizes this pipeline component fails to run. Now data pipelines built from pipeline components created with an S3 connector run successfully.

• Fix: When a user opens a pipeline that was created in a previous version and consists of a pipeline component, a vague error message appears. Now, the user gets a friendly message with the action steps to follow to recover from the scenarios.

• Fix: Resolved an issue where if a pipeline fails, the next run includes data from the previous run, resulting in duplicate events in the resultant process log. Now, rerunning a failed pipeline no longer generates duplicate events.

• Fix: Resolved an issue where after changing the loading strategy of a data pipeline, the pipeline appeared as failed even though the log was created. Now, adjusting a pipeline’s loading strategy no longer marks subsequent runs as failed.

• Fix: When a new column in the Data Pipeline Builder is created with rules that affect other columns, and the new column gets deleted, the rule from the deleted column is still applied to other columns. Now, deleting a column also removes any rules applied to it, ensuring no lingering effects.

KPI and Metrics

• Improvement: When a user performs root cause analysis on a log with no violated case, the user gets a technical error message. Now the user gets a simpler one, saying “The root cause analysis cannot be performed because of this error: The KPI population must contain both compliant cases and non-compliant cases”.

• Improvement: Root cause analysis cannot be performed on process-level KPIs. When a user clicked Investigate, the UI does not respond. Now, the user returns a clear message saying, “You cannot perform root-cause analysis on a process-level KPI”.

• Fix: Resolved an issue where the root cause analysis result returned findings based on only event attributes. Now findings are based on case attributes, activities, resources, roles, or timestamps.

• Fix: Resolved an issue where selecting the “click to move the selected block” icon in a dashboard did not disable the KPI functionality as expected. Now, all dashboard elements, including the KPI icon, are correctly disabled when the move block function is active.

• Fix: When a user creates a custom metric that uses the Case length (average) metric, the metric returns an error. Now, the metric value is calculated and displayed.

• Fix: When a user adds a new custom target while creating KPIs, the value of the new target would intermittently switch with the existing one. Now, the user can add additional targets, each retaining its assigned value correctly.

• Fix: When a user copies a log containing KPIs to another folder and attempts to edit the KPI, the user gets an unexpected error message. Now, when a log is copied, associated KPIs are not copied alongside.

• Fix: Resolved an issue where sharing a KPI with Editor access does not still allow the user to edit the KPI.

• Fix: Resolved an issue where editing KPIs in filtered logs caused errors and unintended behavior, with KPIs from the original log appearing in the filtered log. Now, filtered logs do not carry over KPIs from the main log.

BPMN Editor

• Fix: When a user signs out from the BPMN Editor and attempts to sign back in, the user encounters a “too many redirects” error. Now, the signing in again clearly indicates the current login status and/or redirects to the relevant interface.

• Fix: When a user unpublishes a model and publishes another version, the user could not access the published link. Now, the user can access the published link by clicking the globe icon.

• Fix: Resolved an issue where the attachments in the BPMN Editor were not properly aligned with the task.

• Fix: Fixed an inconsistency in the BPMN Editor where new tasks appeared with a smaller font size than existing tasks. Now, all tasks follow the standard font size uniformly unless manually adjusted.

• Fix: Resolved an issue where task names were not centered in the BPMN Editor.

• Fix: Resolved an issue in the BPMN Editor where labels of events, flows, and annotations appear squished. Now, the labels are properly displayed.

Dashboards

• Fix: Resolved an issue where opening a multi-log dashboard sometimes returned an internal server error.

• Fix: Resolved an issue where the logarithmic scale of a chart from a simulated log does not appear. Now when a simulated log is opened in the dashboard, the user can display the logarithmic scale.

• Fix: When a user creates a filter from the dashboard, and hovers over a filter criterion, a message, “Source log criterion is immutable for the content editor” is displayed. Now the user sees no message when they hover over a filter criterion.

• Fix: When a user creates a gauge without selecting a performance metric, the gauge title defaulted to “Average Performance Metric.” Now, the “average” stat type is selected by default, ensuring accuracy in the gauge title.

• Fix: Resolved an issue where double-clicking on textboxes in the Slicing window inadvertently added multiple slice lines. The double-click functionality has been removed from textboxes, ensuring slices are only added when double-clicking on the designated white area or clicking Add slice line.

• Fix: When a simulated log is opened in a dashboard, and a widget is resized vertically, the widget appeared empty. Now resizing a widget vertically does not affect the displayed data.

• Fix: Resolved an issue where dashboards for a log named “Log” could not be opened. Now, we can open saved dashboards irrespective of the dashboard name.

• Fix: Resolved an issue where, in the Overview, Activities, or Resources views of the dashboard, navigating to the next page of a table would skip pages (e.g., from pages 1 to 3 to 5). Users can now navigate to the next page of the table without issues.

• Fix: Resolved an issue where two tables in a saved Dashboard view incorrectly displayed cases from the same log. The tables now display cases from different logs as expected.

• Fix: When a user creates a compliance chart and the control gets updated, the compliance chart showed “No data to display”. Now the compliance chart is displayed based on the new control.

• Fix: Resolved an issue where specifying the source and target node when creating a handover (arc) tile in a dashboard returned an error: Target Unreachable, identifier ‘vm’ resolved to null.

• Fix: When a log has a saved dashboard, the user could not delete the log. Now the user can delete a log even if it has an associated saved dashboard.

• Fix: When launching a saved dashboard from Process Discoverer, the dashboard displayed filters saved with the dashboard instead of those applied in Process Discoverer. Dashboards now reflect only filters applied in Process Discoverer, ensuring consistency.

• Fix: Resolved an issue where a simulated log with a role name containing a comma cannot be opened in the dashboard.

• Fix: Resolved an issue where refreshing an already opened dashboard failed to retrieve data for the compliance tile and table. Dashboards now correctly retrieve and display data upon refresh.

Filters

• Fix: Resolved an issue where creating a secondary case attribute filter displayed an incorrect count of selectable attribute values. The counter now displays the accurate number of available attribute values.

• Fix: When a user searches for an attribute when creating an attribute filter, and the attribute is not contained in the log, the user gets a technical error message. Now, searching for attributes that do not match any attribute value returns an empty result.

• Fix: When creating a case ID filter and the user searches for a case ID that does not exist in the log, an error message appeared. Now, the filter correctly returns no search results.

• Fix: Resolved an issue where an applied quick case filter is getting updated in the filter window. Now, when a quick case filter is applied, that same filter criterion is displayed in the filter window.

• Fix: When a user creates a case-level timeframe filter and edits it, the user still sees the full-time range of the event log. Now, when editing an applied timeframe filter, the user sees the duration of the filtered timeframe.

• Fix: When a user opens the same log in two separate tabs and applied a filter in one, the filter would apply to both tabs. Now, filters are applied only to the specific tab where they are set, leaving the other tab unfiltered as expected.

• Fix: When a user changes a duration-based chart to a “Relative” scale, the percentage values are not divided by 100, making them incorrect. Now the percentage values are correct when the user hovers on a duration-based chart in the relative scale.

• Fix: When the user opens the Save filter window and sorts by last update, the sorting was not accurately done. Now, the Sort by last updated functionality works accurately.

• Fix: When a user creates a path filter and selects the “Require” checkbox, an error message is sometimes displayed. Now, the user can create a path filter and specify the “Require” checkbox without errors.

• Fix: When applying a case-level filter to retain cases where an activity occurs less than 1 time and another filter to retain cases where the activity occurs less than or equal to 0 times, inconsistent results were produced. These filters now produce consistent results as expected.

• Fix: When a user checks “Predefined timeframes” when creating a timeframe filter, and does not specify any interval, an error occurs. Now the timeframe filter does not display any value until an interval is selected.

• Fix: Resolved an issue where the reset counter button for creating relative filters did not perform computations as expected. Now creating relative filters returns the expected result.

Emails and Notifications

• Fix: Resolved an issue causing some users to not receive notifications of pipeline runs.

• Fix: Resolved an issue that caused KPI email notifications to fail due to missing information. Now, when information about a KPI is missing, the email will be sent, without the missing information.

• Fix: Resolved an issue where images in notification emails were not rendering.

• Fix: Resolved an issue where the notification dot remained visible even after the user opened the notification bell and interacted with the notifications. The dot now disappears as expected once notifications are viewed.

• Fix: Resolved an issue where clicking “X” to clear a notification did not work.

Portal

• Improvement: Made improvements to the owner rights system such that owners cannot strip other owners of a folder of their access rights unless they have a lower privilege in a higher-level folder in the hierarchy.

• Improvement: When multiple files are selected, the tick icon showing the number of items selected now has the same color irrespective of the file type selected.

• Improvement: For improvement readability, we changed the hover text color for the “Third-party open-source libraries” link in the “About Apromore” window blue.

• Fix: When a folder description is saved, the description is not visible when the folder is clicked through the “My Workspace” panel. Now, folder descriptions are visible when accessed via “My Workspace” in the left-side panel.

• Fix: Resolved an issue where long folder paths in the Portal would extend beyond one line, causing overlap. Long folder paths are now truncated to show only the beginning and key folder names for clarity.

• Fix: Resolved an issue where searching for a file in Portal returned duplicate results.

• Fix: Resolved an issue where lengthy folder names increase the width of the folder tree in Portal. Now, the folder name is truncated to fit the folder tree size.

• Fix: Resolved an issue where the download preparation window in Portal does not automatically close after a download is complete.

Access right management

• Fix: Resolved an issue in Access rights management where searching for files in subfolders returned no results. The search now correctly displays all relevant files within folders based on the provided keyword.

• Fix: Resolved an issue where deleting a user and transferring assets did not fully transfer logs, KPIs, and Metrics. Now, all assets are correctly transferred, and the new owner can access them without errors.

• Fix: Resolved an issue where, after transferring assets from a deleted user, the new owner could not access previously generated logs or successfully re-run a transferred data pipeline. Now, the new owner can view existing logs, trigger pipelines without errors, and perform all owner actions on transferred assets.

• Fix: When a shared model has changes, the user sees a message stating that ‘a user’ has edited the model and should the edited model be opened. Now, the message clearly mentions the username that made the changes.

• Fix: Resolved an issue where in some cases the user could not update the user/group that a log, model, or folder has been shared.

Compliance center

• Improvement: For better usability, we enhanced the Compliance Center UI with updated icons, refined tooltips, renamed menu items and window headers.

• Fix: Resolved an issue where users could not import a compliance register when the CSV is not UTF-8 encoded. Now the user is able to select the specific encoding of the CSV file and upload it successfully.

• Fix: When a compliance register has duplicated ID for risks, obligation, or control, and any of these are edited, the UI loads infinitely. Now, when a compliance register has duplicated IDs, the compliance item is ignored.

• Fix: Resolved an issue where updates to the Population Filter checkbox were not saved when editing a control with an empty description field. The Population Filter checkbox is now saved correctly and displayed as enabled in the “Assign Process Logs” window.

Others

• Improvement: For clarity, the variant comparison tool now labels common nodes simply as “Common” instead of “Common nodes.”

• Fix: Resolved an issue where a 24-hour duration was represented as 23.98 hours after a Mon to Fri 24-hour calendar was applied to the log.

• Fix: When the user opens Apromore Copilot during a log animation, the animation gets distorted. Now, opening Apromore Copilot during an animation does not affect the animation display.

• Fix: When the Frequency → Relative Case is selected during variant comparison and two variants have 100% as values in nodes, the text and background turn white making it not readable. Now, the values are displayed so it is readable.

• Fix: Resolved an issue where users could not upload an event log if the language was changed from English.

• Fix: When a user applies the cost center while a filter is applied in Process Discoverer, and then undo the filter, the cost statistics all become zero. Now, undoing a filter no longer impacts cost statistics.

• Fix: Resolved an issue in the log importer where the “Event Attribute → Ignore” and “Ignore → Event Attribute” buttons in Japanese appear garbled. Now, both buttons are correctly displayed in Japanese.

• Fix: Resolved an issue where importing a log with valid column names returned an “Invalid column names detected” error.

• Fix: Resolved an issue where logs could not be downloaded if the language was not in English.

• Fix: When performing a variant comparison with the relative frequency overlay, the darkness of nodes/arcs did not accurately reflect differences in the variant statistics. Nodes and arcs now use shading intensity to better represent statistical differences between variants.

• Fix: When a user hovers their mouse on the start event from the Case inspector, the start event information appeared cut off. Now the start event is fully displayed.

• Fix: When a user saves a view from the Role perspective and reopens the view, Process discoverer incorrectly displayed “Activities” statistics in the Case stats section. Now the Role statistics are correctly displayed.

Version 10.1

Release Date: June, 2024

Features

Compliance center

Compliance management allows organizations to monitor the fulfillment or violation of their service level agreements (SLAs) and regulatory requirements. In earlier versions of Apromore, we could create compliance rules for a process by creating filters on the event log. For instance, in an international payment process, we can have a compliance rule that rejects payments to blacklisted individuals. This is done by creating the filter condition on the log. However, operationalizing this workflow is a bottleneck.

When we have multiple compliance rules to check, we must create multiple filters. Also, if we want to create the same compliance rules on other logs, we must create the filters for each log and apply the filter each time. To streamline the process of operationalizing compliance management in Apromore, we introduced the compliance center. To learn more, see Navigating the compliance center.

Apromore Copilot

Navigating across process mining visualizations to extract insights for improvement is often very time-consuming. To enable a faster and more convenient approach to process discovery, Apromore 10.1 introduces an AI-powered Copilot.

Apromore Copilot is a chat interface that allows us to ask process discovery questions in Process Discoverer. The chat conversation is based on the process map displayed in Process Discoverer and can answer quick questions about the process performance. So, rather than navigating the barrage of information in Process Discoverer, we can simply ask Apromore. To learn more, see Copilot for process discovery.

Apromore Copilot can also answer simulation questions. Instead of manually discovering and adjusting simulation models to explore ‘what-if’ scenarios, we can now simply Ask Apromore to do so! To learn more, see Copilot for Simulation.

Variant comparator in Process discoverer

When multiple processes exist, comparing the performance of the processes can be daunting. Without a clear understanding of the differences in the variations, it is difficult to optimize the processes. For instance, during A/B tests with high-level changes, we may need to know the activity-level differences that have been made and the impact these differences have on the process performance. To enable us to compare multiple processes, the Process discoverer in Apromore 10.1 comes with a variant comparator.

The variant comparator allows us to compare multiple event logs in one Process discoverer view. It highlights differences in activities or transitions as well as the performance statistics of each variant. To learn more, see Compare variants.

Custom metrics

Apromore offers a wide range of metrics, such as average duration, case utilization, total rework, etc., for various performance mining tasks. However, there are situations where these metrics do not capture the specific insight we need. For instance, in a claims handling process, we may want to track the number of claims done per resource within a given period of time. This could help identify resource bottlenecks and balance workloads in the process. To enable us to create such a unique metric, we can now create a custom metric by combining attributes in our event log.

Custom metric allows us to define our own performance metric by combining values and attributes in the event log into formulas. To learn more, see Manage metrics.

Predictive Monitoring Enhancements

Predicted remaining time in filters and dashboards

To enable us to better understand the predicted results in Apromore, the predicted remaining time now appears with a time unit. Thus, if we wish to filter a log by the remaining time, we see the filter range in the most convenient time unit. To learn more, see Use predictions in dashboards and filters.

KPI Enhancements

Streamlined flow for creating KPIs

In Apromore 10.1, we have redesigned the KPI center for a more refreshing and intuitive user experience. In addition to that, we can now create process-level KPIs in addition to the existing case-level KPIs. To learn more, see Manage KPIs.

Process-level KPIs

In previous versions of Apromore, we could create case-level KPIs. These KPIs track the process performance based on the number of cases that fulfils a condition. However, these KPIs focuses on individual cases rather than the process as a whole. For instance, if we want to ensure the average processing time of the process is within a range, case-level KPIs fall short. To address these needs, we introduce Process-level KPIs in Apromore 10.1.

Process-level KPIs allows us create KPIs from performance metrics in the entire process. We can then identify when the process falls below the threshold of the given metric, ensuring we quickly detect any inefficiencies. To learn more, see Process-level KPIs.

BPMN Editor Enhancements

Download Salesforce Flow metadata

To enable us define Salesforce Flows from BPMN models, we can now download a BPMN model as a Salesforce Flow metadata. This downloads an XML file that stores the necessary information about the process to define a Salesforce Flow. To learn more, see Download model.

Notification Center Enhancements

Email subscription to notifications

To keep us up-to-speed with what is happening in our process, we can now subscribe to email notifications. In the notification center, we can toggle email notifications. This ensures that Apromore sends alerts to our email address. We can toggle on email alerts for KPI breaches, BPMN model publication and data pipeline updates. To learn more, see Notification settings.

KPI breach notifications

Receiving prompt notifications when a KPI is breached is essential for ensuring prompt responses to deviations. In Apromore 10.1, we can now subscribe to notifications whenever a KPI is breached. To learn more, see Get KPI breach notifications.

ETL failure notifications

To enable us to get real-time alerts to data pipelines, we now receive notifications on the status of pipeline runs. We get a notification when a pipeline run is successful or fails. In addition, when a pipeline is updated, and the schema changes, owners and editors will be notified. To learn more, see ETL failure notifications.

ETL Enhancements

Import and export pipelines

Creating a data pipeline from scratch can be time-consuming, especially when we need to perform the same merge or transformation step on a similar log. To streamline this process, we can now reuse the merge and transformation operations from previously created pipelines. To learn more, see Import and export pipelines.

Improvements and Bug Fixes

ETL

• Improvement: When a user extracts a dataset containing completely empty or null rows in the extract step of a data pipeline, the empty/null rows are eliminated.

• Improvement: When a user edits a pipeline component, and the pipeline component is extracted in a data pipeline, the user receives a warning pipeline when saving and exiting the pipeline. The warning message informs the user that the transform step of the pipeline has changed due to the changed pipeline component.

• Improvement: When managing the data pipeline, the user can now click ‘>’ next to a data pipeline to open pipeline components connected to the data pipeline. The user can also now edit the connected pipeline components.

• Improvement: We have improved the time to import multiple files in the extract stage of data pipelines.

• Improvement: If an existing pipeline is edited, such as the column positions are changed, but the names remain the same, the pipeline breaks. Now, a change in column position does not break a pipeline, given that the column names remain unchanged.

• Improvement: When a data pipeline is in a locked state, other users could delete it. Now, no shared users can delete the pipeline in a locked state. Only the user who has acquired the lock on the pipeline can delete it or until the lock from the pipeline gets released due to timeout.

• Improvement: When the schema of an existing pipeline component is changed, a refresh button appears in the Extract step of other pipelines utilizing the pipeline component. When the user clicks the refresh button, the pipeline adopts the changed pipeline component.

• Improvement: If uploading a log takes more than one minute, the user gets a message stating that the upload is being done in the background.

• Fix: When the user extracts a pipeline component that consists of an S3 connector in a main data pipeline and schedules it, the log import failed. Now, the user can extract a pipeline component with an S3 connector, schedule it, and successfully run the main pipeline.

• Fix: When a shared pipeline has a pipeline component, the shared pipeline cannot be updated and saved. Now, the shared pipeline can be saved by any of the shared users.

• Fix: Fixed an issue with specific type of pipelines failing when extracted from an S3 folder.

• Fix: When editing an existing pipeline component and changes are made in the Transform step, the save button turns black after clicking. Now, the button works as expected.

• Fix: If an existing data pipeline is edited, including auto-detecting the start timestamp because new files do not have a start timestamp, the pipeline will not fail as long as the column names remain unchanged.

• Fix: When a user creates an ETL pipeline from a filtered log, the column names get changed. Now, the column names in the ETL pipeline are the same as the column names in the ETL pipeline.

• Fix: When the first 300 rows of a data pipeline is empty, the pipeline failed to detect and convert the columns’ data as timestamps at the Extract and Load steps. Now, the pipeline allows the user to set the columns as timestamps without causing errors or pipeline failures.

• Fix: Fixed an issue where filtering by timestamp in the transform step of a data pipeline sometimes yielded inaccurate results.

• Fix: When a pipeline component gets deleted in the extract step of a data pipeline, it used to remain in the merge and transform steps of the data pipeline. Now, the pipeline component is correctly removed from all steps.

• Fix: When an empty log is imported, a message indicated the the log was empty was not properly rendered. Now, the message is displayed clearly.

• Fix: Fixed an issue with timestamp columns being displayed as NULL even when the columns were successfully parsed in the Extract step. Now the timestamp column is displayed correctly as a timestamp.

• Fix: When a user saved a new pipeline without first clicking on the transform tab, an error message would appear upon opening the transform tab. Now, the user can open the transform tab without errors.

• Fix: When a user appends three tables forming a cycle, an error stating something unexpected happens is displayed. Now the user gets a clearer message stating what rows form the cycle and needs to be resolved.

• Fix: When a pipeline component is created from the Workspace connected, and the pipeline component is used to created a data pipeline. The data pipeline fails to schedule. Now, the data pipeline can be successfully scheduled.

• Fix: When creating a data pipeline with a faulty merge operation and the pipeline gets saved, the faulty merge is saved alongside. Now, the faulty merge operation is not saved and the user can update the pipeline to correct it.

• Fix: Fixed an issue where some numeric rules applied on columns with integer data type were not producing accurate results.

• Fix: Fixed an issue where compressed file types could not be extracted from an S3 folder.

• Fix: When merging two similar large logs, the results were not displayed after clicking “Submit.” Now, the results of the table join are displayed correctly, with a warning message if the result exceeds the limit.

• Fix: Fixed an issue where removing a column from a pipeline did not update the dependent pipelines correctly. Now, when a column is removed, dependent pipelines are paused, marked as an error, and a warning message notifies users of the schema change.

• Fix: Fixed an issue where the full text on the “+Add field” button was not visible when the language was set to Japanese. Now, the button is highlighted correctly, and the full text is visible.

• Fix: Fixed an issue where closing the ETL tab during a log extraction with the S3 Connector caused subsequent extractions to take twice the time. Now, reopening ETL and extracting a second log will only upload the second log and is independent of the first log execution time.

• Fix: Implemented a fix that ensures that division involving integers in the transformation step of an ETL pipeline produces accurate results.

• Fix: Fixed an issue where a pipeline with the “Append to the same log” strategy failed when the start timestamp column in the new run was removed and changed. Now, if the start timestamp column is in the original log and the new log maintains the same column order, the pipeline does not and data is appended successfully.

• Fix: When the user adds 100 columns at once, using the “Add whole table” button, the user received an error. Now, all 100 columns are added without errors.

• Fix: When the user uploads a log with attribute case changes (e.g., upper to lower) compared to a previous log in their workspace and they allow schema mapping, an error occurred. Now, schema mapping is case-insensitive and the new log is imported without errors.

• Fix: Fixed an issue where the extraction step in ETL failed for datasets with certain timestamp formats, such as those with alphabetical symbols, single-digit days or months, and null columns. Now, these datasets are successfully extracted with timestamp fields.

• Fix: Fixed an issue in the transform step of ETL where adding or subtracting timestamp fields resulted in an “invalid rule” error. Now, users can add or subtract timestamps.

• Fix: Fixed an issue where running a scheduled pipeline changed the folder permission from owner to viewer. Now, if a user with owner or editor permissions creates a pipeline with that folder as the destination, the permissions remain unchanged after running the pipeline. If a user without access runs the pipeline, they will be granted viewer access to the folder.

• Fix: Fixed an issue where data pipelines beyond the first page of the data pipeline management window were not displayed.

• Fix: Fixed an issue where changes made in the transform step of a pipeline component were not reflected in the connected data pipelines. Now, any changes in the transform step are accurately shown in the connected data pipelines.

• Fix: When the user schedules a pipeline with “append” or “replace” loading strategies and runs it twice, the second run failed with a schema difference error due to an extra ID field. Now, the id field is correctly excluded from the schema difference logic and the schedule runs successfully.

• Fix: When the user selects a folder where the pipeline result will be saved, an error sometimes occurs. Now, users can select folders from the dropdown without encountering any errors.

Filters

• Improvement: We have improved the implementation of the percentile performance filter so that it returns consistent results.

• Improvement: When loading saved filters, a “Show all my filters” checkbox now appears. When the checkbox is deselected, the load filter window shows all the filters linked to the opened log. When the checkbox is selected, all the filters linked to the opened log and other saved filters linked to other logs are displayed.

• Improvement: When saving a filter, the user can now specify the folder where the filter will be saved.

• Improvement: For visibility, when the user hides the top bar of Process discoverer, the quick case filter icon is moved to the top right corner.

• Fix: When a timeframe filter is applied to a log and the log is animated in Process discoverer, the animation no longer goes beyond the specified timeframe in the filtered log

Log importer

• Improvement: The log importer is now robust enough to use more timestamp formats.

• Fix: Fixed an issue where a data pipeline still displayed data after all transform columns were removed from its pipeline component. Now, the pipeline component table is deleted when all transform columns are removed, and the data pipeline correctly shows no data.

• Improvement: When uploading a file containing a numeric value greater than the exponential of 48, the user gets an error message saying: “There was an undefined error loading the file: {file name}. A possible cause could be a column containing numeric values in scientific notation with an exponent greater than 48. Please verify that this is not the case and try again. Otherwise, contact our service desk.”

• Fix: Fixed an issue where the Log importer cannot auto-detect the data type of a column.

Others

• Improvement: The statistics panel in Process discoverer is now displayed as donut charts and not pie charts.

• Improvement: We rearchitected the predictive process monitoring module so that the training time on large event logs is reduced and generates predicted results in situations where it didn’t before now.

• Improvement: When a user predicts the remaining time of a process during predictive process monitoring, the remaining time is of the duration data type.

• Improvement: When a user searches for a file in their Workspace, the result now also displays its location. The user can click on the folder name to open the file location.

• Improvement: When a model containing a linked subprocess is published, other users cannot access the linked subprocess. Now, a second user can access the linked subprocess of a published model.

• Improvement: When saving a BPMN model from Process discoverer, the “Include simulation parameters” checkbox is now ticked by default.

• Improvement: When a Process discoverer view is saved, any calendar or cost center attached to the log is now saved with the view. If the cost center changes, when the user loads the view next, the user receives an info message stating what changed since the view was saved.

• Improvement: When a copy of a log file is made in the Apromore Workspace, Process discoverer views attached to the log are saved in the copied log. If the user edits or deletes the view in the original log, the view in the copied log is unaffected.

• Improvement: When a user clicks on a published link of a model version that is not the latest, a message is displayed stating that while the user tried to access the model version xx, they have been redirected to the latest published version, which is yy. If they need to review version xx, they can click on the information icon in the toolbar.

• Improvement: When a user attempts to save a BPMN model with changes that have not been manually saved, the user gets a warning message that they are trying to publish a model version with a work-in-progress draft. If they continue, the draft will be recoverable only as a new version of the model.

• Improvement: When a user adds a KPI as a gauge in a dashboard and uses the “Mean + Tolerance” KPI, the lower and upper bound labels are not shown in the gauge. Now, the user sees the lower and upper bound labels in the gauge based on their specified mean and tolerance values.

• Improvement: To enhance the user experience when creating a new user, group, or role, the newly created entries will now appear at the top of the list for easy identification.

• Fix: During predictive process monitoring, the predicted remaining time is of the duration data type and is in minutes.

• Fix: In some situations, blank charts are displayed when a polar chart is selected. This bug has been fixed.

• Fix: Fixed a UI text alignment issue in the data pipeline window.

• Fix: If user A transfers ownership of a folder to user B, and user A removes themselves from the folder access or becomes an editor of the folder access, the creator field will not appear empty.

• Fix: Fixed issue with a user getting “Error occured while initializing Process Discoverer”, when opening an event log.

• Fix: When deleting a folder, users were receiving both a confirmation and an error message, with the folder ID remaining in the URL and the “Add new” button missing. This also occurred when deleting a shared folder. Now, users receive the correct message, and the folder ID is properly removed from the URL.

• Fix: When a log is shared without artifacts, the recipient should see all related options disabled. However, the filter option remains enabled but does not work. Now, all options are correctly disabled if no artifacts are shared.

• Fix: When a log is shared with viewer-restricted permissions, the recipient should see the shared file in search results. However, the file name was not appearing in the search results. Now, shared files with viewer-restricted access are not displayed in search results.

• Fix: When a user shares a log with a “Restricted Viewer” and also shares an associated dashboard, the recipient was unable to see the shared dashboard. Now, the recipient can open the shared dashboard by right-clicking on the log or in the info panel.

• Fix: When a user shares a folder and the recipient moves that folder to a location where the original user does not have access, the original user encountered errors. Now, the original user can navigate to the “Folders” section to view the updated folder location within the workspace without errors.

• Fix: Fixed an issue where the Case Path Filter was converting time intervals during calculations causing inaccuracies. Now, the filter retains the original time unit input (e.g., hours) without converting it to other units, ensuring accurate and consistent filtered results.

• Fix: When a log has NULL in a numerical attribute, the case timeline view is not displayed. Now numerical attributes with NULL are ignored and the case timeline view is displayed.

• Fix: When selecting any case within the Case Inspector screen and hovering over an activity, event attribute text longer than 20 characters extended beyond the black UI box, making it unreadable. This issue has been fixed to ensure that the entire text is contained within the black UI box and is easily readable, regardless of length.

Version 10.0

Release Date: April, 2024

Features

Refreshed UI

We are excited to announces our new and refreshed UI. To improve our customer experience, Apromore 10.0 comes with a modern, reactive, and efficient user interface. This is aimed at an intuitive user experience, making our features easily accessible yet simpler to use. The new look introduces our new brand color, oceanic blue, to improve Apromore’s visual appeal. To learn more, see Navigating the Apromore Portal.

Complex data pipelines with pipeline composition

Building data pipelines often involves merging outputs from multiple data sources. The data from these sources may, however, require separate merging or transformation operations, necessitating their own data pipelines. To enable us to create complex data pipelines involving the combination of smaller data pipelines, we introduce the use of pipeline components. To learn more, see Create pipeline component.

Root Cause Analysis Enhancement

Event attribute conditions in root cause analysis

To give us a more accurate reason for KPI violation, root cause analysis in Apromore now incorporates event attributes as conditions. This helps us understand how event-specific attributes affect our KPI fulfillment. For instance, we can see that when the Purchasing Agent is involved in a case more than 8.5 times, the KPI will be violated in 65.4% of the cases. To learn more, see Perform root cause analysis.

Process Discoverer Enhancements

Process discoverer views

After creating a view in Process Discoverer, we may want to display the exact same view later. For instance, we may select a different perspective, change the abstraction setting, or arrange the layout of activities. Creating the same view from scratch at a later time can be time-consuming. In Apromore 10.0, we can now save our current view of Process Discoverer and display the same view later. To learn more, see Save Process Discoverer views.

Dynamic abstraction slider settings

In previous versions of Apromore, when the abstraction setting in Process discoverer is changed, the new abstraction setting is applied to all perspectives. For instance, if we set a 100% node abstraction in the activity perspective and change it to 40% node in the resource perspective, Apromore changes the 100% node in the activity perspective (and all other available perspectives) to 40% nodes. Invariably, only one perspective could be set at a given time.

However, it is convenient to have separate abstraction settings for different perspectives. In Apromore 10.0, we can adjust the abstraction settings for each perspective, and Apromore will remember these settings when we switch between perspectives. To learn more, see Dynamic abstraction sliders.

Filter Enhancements

Rework filters on event attributes

In Apromore 10.0, we can now create a rework filter based on not just activities but other event attributes such as roles, resources, etc. This way, we can use the rework filter to discover cases where a role, resource or any other event attribute is involved in multiple activities in a case.

For instance, in a Procure to Pay log, we may wish to filter cases where the “Purchasing Agent” is involved in more than 10 activity instances. If, by design, the Purchasing agent is not meant to be involved in a case more than 10 times, this filter returns cases where the purchasing agent was involved in a rework. To learn more, see Rework filters on event attributes.

ETL Enhancements

Automated discovery of start timestamps

If a data pipeline in the Load step does not have a start timestamp column, Apromore can now automatically discover the start timestamps.

Dashboard Enhancements

Simplified user flow for multi-process dashboard creation

If a business contains multiple processes with specific nuances, it is useful for business stakeholders to create a comparative dashboard that displays the performance statistics of the processes together. This helps in benchmarking and can also reveal inefficiencies in certain processes. In Apromore 10.0, we can now create a multi-process dashboard that displays the performance statistics of multiple processes in one view. To learn more, see Create multi-process dashboards.

Download PDF report from a dashboard view

For reporting purposes, we can now download the dashboard view as a PDF file. The PDF will render all charts, tables, tiles, or KPIs in the view. To learn more, see Download dashboard.

Custom attribute values in heatmaps and bubble charts

When creating a heatmap or bubble chart, we may be interested in displaying specific attribute values or the most frequent values. For instance, when we create a heatmap with “Resource” as X and Y axis attributes, this displays handoffs between the resources. If there are 50 resources, the heatmap displays the 20 top resources on the X and Y axis. However, we may be interested in display handoffs between specific resources. We may also be interested in displaying handoffs from the top 5 most frequent resources. In Apromore 10.0, we can specify the attribute values to retain or the most frequent values to retain when we create a heatmap or bubble chart. To learn more, see Attribute values in 3D charts.

Role utilization charts

To aid resource planning, it is important to visualize the role utilization in our processes. In Apromore 10.0, we can now add a role utilization chart in dashboards.

Role utilization indicates the percentage of time a role is involved in an activity with respect to their total working hours. For instance, a 100% role utilization indicates that the role has no idle time, which necessitates the need for more resource allocation. To learn more, see Performance histogram chart.

User Management Enhancements

When managing users in previous versions of Apromore, we can see the list of created users and sort by the date they were created. We, however, could not sort groups, group relations, and roles by creation date. Apromore 10.0 now allows us to sort groups, group relations, or roles by creation date in ascending or descending order. To sort by date created, go to the respective tab and click Created.

Improvements and Bug Fixes

Dashboard

• Improvement: We can now download the entire view of a dashboard in a PDF.

• Fix: When a log timeframe is less than 96 hours, the user should be able to create a WIP chart in a dashboard with Hourly X-Axis internals. This was not the case for some logs. Now, users can create WIP charts with an hourly X-axis option for all logs within a timeframe of less than 96 hours.

• Fix: Users could not download filter or dashboard templates with double-byte characters (e.g., Japanese characters). Now, the users can download templates saved with these characters.

• Fix: The user could not download a dashboard time if the name contained double-byte characters (e.g., Japanese characters). Now, the user can download a dashboard template with double characters in the dashboard name.

• Fix: When a handover statistic chart is selected, changed and selected again, the handover chart does not show a target node to select from. Now, when a handover chart is selected for the second time, the chart displays the source of the target node from which the user can choose.

• Fix: When downloading a process model as a PDF, all the text was lost in the exported PDF. Now, the downloaded PDF contains the same model with text as the BPMN Editor.

• Fix: When the user creates a chart with a timestamp event or case attribute as an X-axis, no data is displayed (e.g. when the Y-axis is case frequency), and data is displayed (for string values), but the X-axis is paginated and bucketed (for numerical values). Now, the Y works for any type of datatype on the X-axis, including timestamps. Also, timestamp event/case attributes are bucketed as if they were numbers and not paginated.

• Fix: After applying the specific template to the dashboards, some charts disappear. Now, when necessary, the chart appears with the “No data to display” label.

Process Discoverer

• Improvement: When the user downloads the process map from Process Discoverer with the cost/duration overlay, the name of the downloaded file in the format “[Name of the file] - [aggregator] [selected overlay], not “[Name of the file] - [aggregator] label.”

• Improvement: When the user hovers the mouse over any of the log statistics sections in the top panel in Process Discoverer, the statistics appear in the order: Average, Std dev, First quartile, Median, Third quartile, Min, Max, Total and Rework.

• Fix: In some cases, the user could not apply a user-defined backbone in Process Discoverer. Now, the user can define a backbone line when the start and end nodes are included in the path.

• Fix: When the user hovers over an arc involving the start or end event in Process Discoverer, a trailing and leading -%- symbol is present. Now, the -%- are no longer present.

• Fix: When the user attempts to adjust the chart timeline width setting in the case inspector, the value gets auto-updated to 184200. Now, the user can change the chart timeline width in the case inspector.

• Fix: When downloading the activity inspector, the end and start event has a leading and trailing -%- symbol. Now, this symbol does not appear in the downloaded file.

• Fix: In the activity inspector, the start and end activities had an unnecessary leading and trailing -%- symbol. Now, the symbol no longer appears.

• Fix: When the user launches the Dashboard via Process Discoverer, the dashboard inherits any previous filters saved from the dashboard. Now, all dashboard filters are ignored and overwritten by any filters in the current Process Discoverer.

ETL Pipeline

• Improvement: When extracting multiple logs in an ETL pipeline, the logs extraction time is now reduced

• Improvement: When performing the merge operation in the ETL pipeline, the time to compute the merge result has now been reduced.

• Fix: The ETL crashed when more than 10 files were extracted through the ‘Local file upload’ method. Now, the user receives an error message alerting that a maximum of 10 files can be uploaded at a time using local file upload.

• Fix: When the timestamp format during ETL extraction has alphabetical symbols or has single-digit days or months or null columns, the data is successfully extracted, and the timestamp is converted to its ISO8601 standard without failing.

• Fix: When a user attempts to merge CSV and Parquet files in the ETL pipeline, the user cannot perform this merge. Now, the bug has been fixed and the user can merge a CSV and parquet file.

• Fix: When a user whose username is up to 45 characters (the maximum allowable number of characters), the user cannot save or schedule an ETL pipeline. Now, the user with 45 characters can schedule or save an ETL pipeline.

• Fix: When a log has a timestamp earlier than 1 January 1900, importing the log in the ETL pipeline fails. Now, these timestamps are filled with NULL, and the row passes through.

KPIs

• Improvement: When a KPI is added as a pie chart, the chart shows the KPI value percentage below the KPI target.

• Improvement: When a KPI is added as a gauge, the chart shows the KPI value percentage up to 2 decimal places.

• Improvement: When a custom KPI target is selected, Apromore now pre-populates the thresholds with the following colours: 0 - 70% (red), 70% - 85% (amber), and 85% - 100% (green).

• Fix: When investigating KPIs, some of the causes had missing or incomplete conditions. Now, the KPIs causes display complete conditions.

• Fix: When performing root cause analysis, the same value appears in the activity attribute, and in an event attribute, the root cause analysis fails. Now, it returns the correct root causes.

• Fix: When column names include double-byte characters (e.g., Japanese characters), the investigate function in root cause analysis failed. Now, the user can investigate KPIs when the log has column names with double-byte characters.

• Fix: Root cause analysis returned an error when a string attribute contained numbers. Now, the root cause analysis is successfully returned irrespective of numbers in a string-designated attribute.

• Fix: Root cause analysis returned an error when there is a single quotation market in the activity labels. Now, the root cause analysis successfully runs irrespective of quotation marks in the activity labels.

Filters

• Improvement: When creating a case filter, the case IDs are all selected by default, necessitating the user to deselect unneeded ones. This can be time-consuming. Now, all case IDs are deselected by default. The user can quickly select the few things that are important to them.

• Improvement: When creating a rework filter, the user is now able to set the upper bound greater than the maximum number of reworks or a lower bound less than the minimum number of rework.

• Improvement: Previously, the value NULL appeared when creating an attribute filter blocking the user from using the slider. Now, NULL does not appear as a value when creating attribute filters.

• Improvement: In some situations, the percentile performance filter does not give consistent results. Now, the filter returns the same result when the same percentile filter criterion is created.

• Improvement: Improved the capabilities of the Blocks filter to return a valid result when a user creates a filter criterion with case and event numerical attributes.

• Fix: When creating filter criteria, the statistics on the left side of the filters overview were not updated after changing the order of filters. Now, the statistics on the filter overview are updated.

• Fix: When a filter containing block filter criterion is saved and loaded, the filter returns zero cases. Now, the loaded filter returns the same result when it is saved.

• Fix: Fixed an inconsistent error that pops up when a user applies a filter and double-clicks the filter icon in Process discoverer.

• Fix: When a filtered log is saved, the column names may be changed, e.g., from Application ID to Case ID. Now, the column names in the original log are maintained in the saved filtered log.

Others

• Improvement: When viewing the version history of BPMN models, there is now a “Published versions” header indicating the list displays only the published models.

• Improvement: When a user creates a new user, group, or role, the created user, group, or role is selected automatically so that the user can make quick changes to the created values.

• Improvement: When a new user is created, the user is added to the end of the user’s list. To confirm the user was successfully created, newly created users have been added to the top of the users’ list.

• Fix: When a simulation log is saved with more than 100 characters, the user is unable to rename the log. Now, a warning appears when the user saves a log with more than 100 characters.

• Fix: When a log file contains Japanese labels and the default column tags are changed in the log importer, the log is successfully updated, but the user cannot download the log afterward. Now, the user can download the log after uploading.

• Fix: There was a temporary issue where the user could not open or create a calendar. This bug has been fixed.

• Fix: During conformance checking, if more than 30 activity differences are identified, the user gets an error message saying the number of added activities is exceeded, rather than conformance checking not working.

• Fix: During conformance checking, if the model contains multiple nodes with the same activity label, the user receives the error message: “Conformance checking cannot be performed because the model has two nodes with the same name.” rather than conformance checking not working.

• Fix: During conformance checking, if the process model is complex, the user receives an error message: “Unable to check conformance. The process model is too complex”, rather than conformance checking not working.

• Fix: Fixed the bug causing some XLSX files not to get imported in Portal.

Version 9.5.2

Release Date: February, 2024

Improvements and Bug Fixes

ETL

• Fix: When a Parquet and CSV file are extracted using S3 connector and merged using the Append operation, an unclear error message is displayed. Now, the logs are appended without errors.

• Fix: When a user has a username of 45 characters (max character length), and the user schedules a pipeline, the pipeline either fails to save or cannot be scheduled. Now, the pipeline can be saved or scheduled when the username has 45 characters.

• Fix: When a user extracts a log via the workspace connector in the ETL pipeline, the extraction steps fail due to a possible mismatch in the timestamps. Now, the user can extract the log successfully.

Others

• Fix: There was an error when the user clicks the “Manage access right” icon in Portal. Now, the user can open the “Manage access right” without errors.

• Fix: When a dashboard template with sliced tiles is reapplied to the same log, the tiles appear without the slice setting. Now, when a dashboard template is applied on the same log, the tiles contain the initial configured slice setting.

• Fix: When viewing the case timeline, the last activity appears as a number when the activity name is long. Now, the case timeline displays the actual name of the activity.

• Fix: When a user shares a log containing a KPI and the shared user attempts to delete the KPI, the KPI is deleted for the shared user but remains available for the owner of the log.

• Fix: When the dashboard is configured to display a case attribute chart, the chart may display no data. Now the dashboard displays the case attribute chart accurately.

• Fix: When a directly-follow path filter is applied, the filter results may be inaccurate. Now, the filter displays the accurate result in the process.

• Fix: When performing root cause analysis, values of timestamp attributes appear in human readable format and no longer in UNIX format.

• Fix: The dates of the public holiday were slightly inaccurate due to timezone difference. Now, the dates are displayed accurately and the user can make edits to the dates of holiday(s).

• Fix: When a filter containing multiple filter types including a block filter is saved and loaded, the result of the loaded filter is incorrect. Now, the loaded filter displays the accurate result of the filter criteria.

• Fix: When a log that has an existing mapping schema is uploaded, the prompt asking the user to accept the schema or not is unresponsive if the log had invalid rows. Now, the user can select whether or not to accept the existing mapping schema and proceed with the log upload.

• Fix: The KPI result sometimes returned different results from when the same filter was applied through the Filter log window. Now, the result of the KPI result is the same with the filter result if the same filter was created.

• Fix: When the position of tiles and gauges are relocated in a dashboard, and the dashboard is saved and loaded, the tiles and gauges were not found in the new location. Now, the tiles and gauges appear in the locations they were moved to.

• Fix: When two BPMN models are compared and the difference involves the use of a different task type, the BPMN comparator displayed inaccurate result. Now, the BPMN comparator displays the exact changes that were made.

• Improvement: When creating a PAAR draft, all qualifiers and benefits were disabled by default and the sliders extremes’ labels were strings with keywords. Now, the qualifiers and benefits are enabled by default and the labels show the correct numerical value.

Version 9.5.1

Release Date: February, 2024

Features

S3 Connector Enhancements for Micro-Batch Ingestion

Micro-batch ingestion is a method where data is ingested in small, manageable batches, instead of being ingested in a single, large batch.

The Apromore S3 Connector now supports micro-batch ingestion. In the S3 Connector, a micro-batch is a file containing a (relatively) small number of rows. When adding a new table to a pipeline using the S3 connector, we can specify that this table must be ingested in micro-batches, instead of it being ingested in a single go, from one single file.

Improvements and Bug Fixes

Process Discoverer

• Improvement: The layout dropdown in Process Discoverer toolbar has been moved to its original place (before the zoom icons).

• Improvement: After selecting a layout option from the layout dropdown, the dropdown stays open as though a selection was not made. Now, the dropdown closes after a layout option is selected.

• Improvement: The share icon in Process Discoverer toolbar has been relocated after the KPI icon.

• Fix: Password management application sometimes autofill the search bar in Process Discoverer sometimes redirects the user to the documentation. Now, password management applications no longer populate the search bar in Process Discoverer.

• Fix: When a user changes the schema of a scheduled ETL pipeline, the next pipeline run now fails and informs the user that they cannot perform an operation on a log whose schema has changed.

Others

• Fix: When the user enters a KPI name that is more than 100 characters, an error message is no longer displayed. Rather, a warning message informs the user that a KPI name cannot exceed 100 characters.

• Fix: When an Approver shares a model with another user, the Approver may sometimes not view the model from their notification center. Now, the Approver can view the model from their notification center.

• Fix: When a user shares a process model that has a subprocess, the shared user could not access the subprocess in the model. Now, the shared user can access the subprocess in the model.

• Fix: When a user publishes a model and selects an approver, sometimes the approver does not see the model in their notification window. Now, the approver sees the sharing request and can approve or reject it.

• Fix: Sometimes, the “Filter by case cost” feature displays an infinite loading spinner when it does not have the required data for the operation. Now, the “Filter by case cost” button is disabled when it does not have the data to filter a log by case cost.

• Fix: When an ETL pipeline is created from three sources and the “Generate a new log every time the pipeline is executed” loading strategy is selected, the pipeline run fails. Now, the pipeline runs successfully in these conditions.

• Fix: When a dashboard template that is not fully compatible is loaded, the dashboard returns blank widgets. Now, the dashboard returns the widgets with a message “No data to display”.

• Fix: The rework filter fails to select any cases where the activity name had a single quotation mark. Now, single quotation marks in activity names do not affect the rework filter functionality.

• Fix: The swimlane descriptions were not aligned and was overlapping with the lane. Now, this alignment issue has been fixed.

Version 9.5

Release Date: January, 2024

Features

Blocks Filters

The Blocks Filter is a new type of filter that allows us to create filters consisting of multiple conditions, in an intuitive manner. We can create multiple filter conditions in one go by dragging and dropping filter blocks.

Multiple block rows are concatenated by an “AND” logical operator or an “OR” logical operator. If the “AND” logical operator is selected, then the Blocks filter criterion is fulfilled if every one of its conditions is true. If the “OR” operator is selected, the Blocks filter criterion is fulfilled if at least one of its conditions is true. To learn more, see Blocks filter.

Process Discoverer Enhancements

Process Map Layout in Process Discoverer

To better understand a process map, displaying the most frequent activities along a horizontal line may be useful. In Apromore 9.5, we can horizontally align and lock the most frequent activities in one specific Y-coordinates (called the backbone line) when displaying the process map.

There are three layout options when configuring the process map layout in Process Discoverer: legacy left-to-right, auto-discovered backbone and user-defined backbone. To learn more, see Process map layout.

Activity Inspector in Process Discoverer

In business process mining, it is useful for stakeholders to have a detailed understanding of each transition between consecutive activities in a process to enhance operational efficiency and decision making. To analyze the activity transitions in detail, we need to have a way to investigate each incoming and each outgoing arc of an activity.

In Apromore 9.5, when we double-click an activity in Process Discover, the Activity Inspector now displays the activities that directly follow and the activities that directly precede the selected activity, as well as relevant metrics: relative frequency, average frequency and average duration. To learn more, see Inspect activities.

Dashboard Enhancements

Work-in-Progress (Activity Queue) Chart

For business monitoring purposes, managers may be interested in knowing the number of cases where an activity is in Activity queue or the number of activity completion over a period of time. This may be useful for planning resource allocation or expected turnover rate.

In the dashboard, we can have the Work-in-Progress (Activity Queue) chart that displays the work-in-progress per activity or the activity throughput over a period of time. To learn more, see Work-in-Progress (Activity Queue).

Multiple Y-axis in Performance Trend Charts

When creating a performance trend chart, it is often necessary to display multiple performance metrics simultaneously over a period of time. This allows us to see how these metrics evolve together.

In Apromore 9.5, we can add multiple Y-axis in a performance trend chart. For instance, we can have a primary Y-axis that displays the average case duration over a period and, in the same chart, a secondary Y-axis that displays the waiting time over the time period. We can add up to two additional Y-axis (called secondary Y-axis). To learn more, see Performance trend chart.

User Management Enhancements

As admins or superusers, we can now see all the files (i.e., folders, logs, or models) that a specific user within our tenancy has access to and can edit those access rights. To learn more, see see Manage access rights.

KPI Enhancements

Root Cause Analysis

The root-cause analysis feature is now able to discover complex conditions, consisting of more than one predicate, such as: Country = “Germany” and InvoiceAmount > 5000 and ProductType = “Machinery”. This helps us understand specific contributing factors to the KPI violations. To learn more, see Perform root cause analysis.

Improvements and Bug Fixes

Process Discoverer

• Improvement: When the user removes the value from the text box in the abstraction slider and applies an empty text box (by clicking on any empty place in Process Discoverer, or pressing “Enter“), the value is auto filled as 0 and 0 is displayed in the textbox. The slider is also saved as 0 and is moved to the left corner.

• Improvement: When the user selects the “Total Rework“ dimension for the “Frequency“ or “Duration“ overlay, the rework metric is displayed for each transition.

• Improvement: The Case Inspector now contains the start and the end timestamp in addition to the Case ID, activity instances, duration, and cost as in previous versions.

• Improvement: The user is now able to download the data from the Case Inspector. For larger logs with more than 100000 cases, the user can download the first 100000 cases from the Case Inspector.

• Improvement: When a case is selected in the case inspector, and the user hover over an activity in Process Discoverer, the user can see the start and end timestamps in the format “dd MM yyyy HH:mm:ss“.

• Fix: The duplication of NULL value in the filter log window is now fixed.

• Fix: The toolbars in Process Discoverer window is disabled when user has another window opened.

• Fix: When a cost center has been applied to a log and a filtered log is saved, the filtered log also saves the cost values.

• Fix: When an uncommon currency is used in Process Discoverer, the user sometimes gets a “Filter response error” when applying a filter. This issue has been fixed.

BPMN Editor

• Improvement: The BPMN Editor now displays the description of the specific model.

• Improvement: There is now a “Publication history” icon that allows the user to view the history of all the published/unpublished versions of the model.

• Improvement: The labels entered on a task/event in the BPMN Editor is now center-aligned by default and not left-aligned.

• Improvement: When the user edits the texts in the following BPMN element: “Arc description”, “Gateway description”, “Start/End/Intermediate event name” and “Data objects description”, the font size does not change but remains the same during rendering.

• Improvement: When saving a BPMN model in the BPMN Editor, the “Autosave” label is now changed to “Auto backup (local draft)”.

• Fix: When a user changes the font size of a model, all the elements are resized to the specified font size. If the user adds a new element (e.g. a task), the font size of this new task is still the font size the user specified.

• Fix: Task names are aligned and appear within the frame when the BPMN model is downloaded as PNG, SVG or PDF.

• Fix: In some situations, the BPMN comparator says an activity was changed when no change was made. Now, the BPMN comparator shows the exact changes made when comparing two models.

• Fix: The BPMN Editor now successfully opens a model discovered from a log with simulation parameters when the log contains over 200 role values.

• Fix: When editing a task in the BPMN Editor, the font size while typing no longer appear small but maintain the same font size as other tasks in the model.

• Fix: When the user deselects “Show attachment labels”, the icons and labels no longer disappear as they are attachments and not the attachment labels.

• Fix: When saving a BPMN model from a log with “.” before the file extension, the BPMN model maintains the name of the log while only changing its extension.

Dashboard

• Improvement: When selecting 3D charts (eg, heatmap, tree map, or bubble charts), the data points column is replaced with a “Total frequency” column. The Total frequency column shows the total frequency of the attribute. The chart also shows the top 20 most frequent attributes by default.

• Fix: The dashboard now shows the updated charts after a filter is applied to a cloned chart.

• Fix: Consecutive-pairs heatmap now displays consistent values when only one X-axis value is selected.

• Fix: When a chart block is moved in a dashboard, no empty space is created. Only the moved block changes its position, and all other blocks remain in their original locations.

• Fix: The dashboard no longer has missing fields in the presentation section when a tile with case attribute is created, the selected attribute has real numbers, and the display type is “Sum (inter-cases)”.

• Fix: When a dashboard template is loaded, heatmap charts with same X and Y attributes are loaded successfully.

• Fix: When a dashboard template containing a table with an applied filter is loaded to another dashboard, the filter remains applied to the table.

• Fix: When a dashboard with incompatible log slicing rules or incompatible log filtering rule is imported, the dashboard does not show blank widgets but present empty results.

• Fix: After slicing a block (chart, tile, table) using the resource attribute, filters applied to the block are successfully reflected in the displayed data.

• Fix: When user opens attribute value window after changing an attribute (case or event), the user sees the updated values in the attribute value window.

• Fix: Fixed an issue in the dashboard where “Others” appears twice in a pie chart, depending on the log.

• Fix: When the user clicks the “Relative” scale of a duration chart, and hovers their mouse on a data point, the % symbol appears which was not present before.

• Fix: The X and Y-axis values of a timestamp-based attribute values are displayed in the dd.mm.yyyy hh:mm:ss format instead of the simple epoch millisecond values.

• Fix: When the user creates a predicted case attributes using the predictor, the user is now able to create charts based on the predictor case attributes.

• Fix: When the user creates a chart with numerical attributes on X-axis and a Resource as an Event attribute on Y-axis, the Y-axis now accurately displays the resource names. Prior to now, the resource names were not displayed correctly on the Y-axis.

• Fix: When creating a performance trend chart, the variability ratio now accurately displays the ratio between variants and cases.

• Fix: When a chart is created where the value of the X-axis attribute has long characters, the user sees an abridged X-axis attribute with ellipses (…) ensuring the X-axis attribute text do not overlap.

• Fix: The issue where scatterplots in a dashboard were not displayed when the user downloads the dashboard in DOCX or PPTX format has been fixed.

• Fix: The bug that replaced spaces in a log name with ‘n’ when uploading a filter template from the dashboard has been fixed.

• Fix: The bug that replaced spaces in a log name with ‘n’ when editing the name of a filter applied on a dashboard block has been fixed.

• Fix: When a user creates a heatmap chart and selects the X and Y-axis attribute, the user now sees the selected X and Y axis attribute values in the chart even if the combination (“X1”, “Y1”) and (“X1”, “Y2”) did not occur in the log.

• Fix: When a performance trend chart (custom) is created, the time unit on the Y-axis is now automatically set depending on the data rather than it being in milliseconds.

• Fix: When adding the reference line/KPI threshold of a performance trend chart, the values are no longer in milliseconds but rather are in the same unit as in the chart.

• Fix: Before now, the user could not add an X-Axis reference line after creating a performance trend chart. This bug is now fixed, and the user can add an X-axis reference lines to a performance trend chart.

• Fix: When a user adds a Y-axis reference line to a performance trend chart and then changes the Y-axis metric, the Y-axis reference line could not be modified. This issue has been fixed and the user can now change the Y-axis metric at any time.

• Fix: Fixed an issue where loading a saved filter template with both Filter and Slicing criteria did not apply these settings to tables or charts in dashboards. Now, tables and charts correctly reflect the slicing and filter criteria from saved templates.

• Fix: Prior to now, when creating a performance trend chart, empty buckets may be displayed at the start of the time frame (X-axis), making the chart less appealing. Now, the performance trend chart starts from the first non-empty bucket.

Log Importer

• Improvement: When importing a log in the workspace, cells in the Log importer are center aligned, the columns names for the timestamp column have tidy alignment and there is more spacing between rows.

• Fix: When an event log is exported, the columns tagged as event attribute perspective displays the original column names and not the base32 encoded names.

• Fix: Users can now import timestamps with extra digits in the micro-seconds section, i.e., with the format yyyy-MM-dd HH:mm:ss.SSSSSS.

• Fix: The user can now successfully import a log with up to 2000 role values.

ETL Pipeline

• Improvement: When selecting an S3 bucket to extract in an ETL pipeline, the “Browse” button has been changed to the folder icon.

• Improvement: When there are more than 100 runs of a schedules pipeline, then the latest 100 runs of the pipelines are displayed.

• Fix: Fixed issue with a scheduled ETL pipeline failing when the pipeline uses a workspace connector sourced from a delta log.

• Fix: Before now, when the user uploads a log extracted from the workspace connector, only 50 rows are uploaded each time. The user can now fully import the events when logs are extracted using the workspace log. This extracted log can also be uploaded in full using the Upload button and schedule pipeline in ETL.

• Fix: Fixed issue with importing logs where rows with integers greater than 4,294,967,296 fails.

• Fix: When a chained pipeline is built using S3 connector, the chained pipeline no longer appears empty when the preview icon is clicked.

• Fix: Fixed issue with the user sometimes getting the “Oops… something unexpected happened” error message after an ETL pipeline was successfully scheduled.

• Fix: In the transform step of an ETL pipeline, the user no longer gets NULL values when there are three timestamp columns.

• Fix: The ETL screen does not freeze when removing a log that’s being used in the merge step.

• Fix: The ETL screen does not freeze when attempting to upload more than 10 files at once including zip files but rather warn the user that a maximum of 10 files can be uploaded at a time using local file upload.

• Fix: Log import no longer fails with usernames having characters dot “.” or underscore “_” or file names that have “.”

• Fix: The user can now perform undo/redo in the ETL pipeline without errors.

• Fix: When an extracted log is deleted in the workspace, the user now sees a clear error message stating that one or more extracted workspace logs have been deleted and that a new log should be extracted.

Filters

• Fix: The two NULL values that show up when performing an attribute filter has been fixed. Now only one NULL value can appear.

• Fix: When creating an event-based timeframe filter, and the log-scale is selected, the data points in the chart do not appear as blank out anymore.

• Fix: Fixed issue with the case variant filter occasionally returning inconsistent values.

• Fix: The “Filter by case cost” button is disabled if the log does not have the necessary data to support this operation.

• Fix: Before now, when accessing the “Load filter templates” window via Portal or Process Discoverer, the action icons (rename and delete) appeared cropped. Now, they appear fully.

• Fix: When saving a filtered log, a 100-character limit has been introduced. The label is updated to “Enter a log name (no more than 100 chars)”.

• Fix: When a user undoes multiple quick filters in the dashboard, each “Undo“ clicks represent each filter that was applied.

• Fix: The user can now perform range selection on an attribute filter with negative numerical values.

• Fix: When a calendar that has been added to a log is removed, the result of any previously applied filter is now updated if the filter is dependent on the calendar values.

• Fix: Fixed issue with users occasionally not being able enter spaces in filter descriptions.

• Fix: Fixed issue with the user no longer able to use the filter sliders to select a timeframe after toggling the “Relative timeframes” on and off in the Timeframe filter.

• Fix: Fixed an inconsistency in Process Discoverer where removing a previously applied calendar caused mismatched filter results between the log statistics section and the filter window. Now, filter results are consistent, regardless of calendar changes.

KPIs

• Improvement: When the KPI name is up to 200 characters, the user gets a warning stating that the KPI name should not be longer.

• Improvement: When there are no violations found during root cause analysis, the KPI center displays information stating no root cause was found rather than displaying an error message.

• Improvement: The KPI title displays the KPI stats without any imperfections regardless of the size of log.

• Fix: When the KPI window is opened, the user is no longer able to interact with other content in the background.

• Fix: When the user updates the cost center information or calendar information of a log, KPIs attached to the log reflects the updated values.

• Fix: The KPI center now reflects the updated currency when the currency in the cost center is changed.

• Fix: Fixed issue with the KPI returning NullPointerException for some logs when the KPI target was set to <= a value.

• Fix: Fixed issue with the user getting an empty zip file when downloading a KPI due to the presence of special characters (/, \, |, :, *, ?, “, <, >) in the KPI name.

Others

• Improvement: Users can use special characters when entering an artifact description.

• Improvement: When the user creates a new user in the “User Management” window, the new “Role” dropdown is added that allows the user to assign the needed role at the point of creating the new user.

• Fix: Empty user logins is not shown in Activity history if there is a redirection error during log in.

• Fix: Fixed issue with some model versions appearing to be already published (according to icon labels), however, when the user clicks on such icons, the publishing window open - yet they cannot proceed with the publication process.

• Fix: When a log with an applied calendar is shared to another user, the applied calendar is visible to the shared user from the Cost center window.

• Fix: When a calendar that is applied to a role is deleted, the user was not able to make any further in the cost center. This has been fixed.

• Fix: When the user changes the interarrival time in the simulation parameters to the same value changes, the values (although unchanged) is changed in the backend. This issue has been fixed.

• Fix: Fixed issue with the red (removed) elements appearing smaller than the green (added) elements during conformance checking of a BPMN model.

• Fix: During conformance checking, the arcs are now displayed to begin and end on the edge of the task, event or gateway frame.

Version 9.4

Release Date: October, 2023

Features

Performance Trend Charts

When analyzing a business process, it is useful to understand how certain process performance metrics change over time. This helps in detecting performance improvements or degradations.

You can now create a performance trend chart which displays how a performance metric evolves. An example of a performance trend chart is a chart that displays the “average case duration over time” or the “active cases over time”.

For more information, see Performance trend chart.

Simulation Enhancements

Resource Performance Handicap

Sometimes, a resource may take longer to complete an activity than the assigned activity duration. For instance, assume we have two roles, “Junior Financial Manager” and “Financial Manager”. Both roles can perform the same tasks (e.g., “Pay invoice”, “Release supplier’s invoice”, etc.). However, the resources with the “Junior” role are 10% slower due to their lack of experience. To capture this difference, you can add a 10% “performance handicap” to the Junior Financial Manager role.

For more information, see Resource performance handicap.

Resource Maximum Allowed Overtime

When we simulate a process model, a resource may sometimes begin an activity instance just before their work shift completes, in such a way that the resource is unable to complete the activity instance within their current shift.

For instance, consider the following example. Mark (a Purchasing Agent) starts the “Analyze Request for Quotation” activity, which takes 30 minutes at 4:40 pm. But his shift ends at 5:00 pm, so he does not complete the activity in the current shift. The following day, Mark continues the activity execution and completes it in 10 minutes (at 9:10 am). In other words, the default behavior of the simulator is to interrupt an activity instance at the end of a shift, and to resume it at the beginning of the next shift (e.g., the next work-day).

When faced with such situations in reality, a resource may opt to do a 10-minute overtime to complete the task instead of postponing its completion to the next working day.

In Apromore 9.4, you can now capture this behavior by assigning a “maximum allowed overtime” to a role. In the above example, if the Purchase Agent role has a maximum allowed overtime of 10 minutes or more, the simulator will consider that Mark will use the overtime to complete the above activity instance within the same work shift where it started.

For more information, see Resource maximum allowed overtime.

Event attributes in simulation parameters

In previous versions of Apromore, only case attributes were supported by the simulator. In Apromore 9.4, you can attach attributes to a simulation scenario. These attributes may behave as case attributes or as event attributes, depending on whether they are modified by one or more tasks (event attributes), or they are never modified (case attributes).

For more information, see Attributes.

BPMN Editor Enhancements

Show or hide comments, attachments and attachment labels

You can now show or hide comments, attachments, and attachment labels in the BPMN Editor.

Resize attachments with associated tasks

When an attachment is added to a task, you can now resize the attachment in the BPMN Editor.

Process Modeling Enhancements

Compare two versions of a process model

You can now compare two versions of the same BPMN model to highlight the differences between these versions.

Dashboards Enhancements

Handover statistics in the Dashboard

During performance monitoring, managers may need to understand how efficiently tasks are transferred from one resource, role, or team to the other. You can now visualize the handover statistics in a dashboard tile.

Improvements and Bug Fixes

ETL

• Improvement: An error message is produced if an ETL pipeline generates an excessive number of records (more than five times the maximum number of records allowed in one import). This typically happens when a join operation uses an incorrect key.

• Improvement: A warning message is displayed when a connected pipeline changes.

• Improvement: In the “Data pipeline management“ window, when a pipeline run has “failed“, the reason for the failure is displayed when you hover over the “Failed” status tag.

• Improvement: Error messages when a pipeline fails now include hints on how to fix the error.

• Improvement: When an event log is extracted via the Workspace connector, the timestamp columns are displayed in standardized ISO-8601 format with a timezone indicator, e.g., 2020-05-31T23:10:01.000+10:00. These standardized timestamps make it simpler to perform date operations (e.g., extract the year and month of a timestamp column).

• Improvement: When configuring a pipeline with a loading strategy of “always append data to the same log” or “Overwrite the log every time the pipeline is executed,” there is now an option to choose whether or not a new log should be generated when the schema of the pipeline is altered, to prevent schema incompatibility issues.

• Improvement: When uploading a log via a data pipeline, an error message is displayed if two columns have identical names or if one column is named “Activity” and a different column is tagged as the “Activity” column (or same for “Resource” or “Role”).

• Improvement: A warning message is displayed when a chained pipeline changes its output.

• Improvement: In the “Data pipeline management“ window, when a pipeline run has “failed“, the reason for the failure is displayed when hovering over the “Failed” status tag. The message includes hints on how to fix the error.

• Improvement: When configuring a pipeline with a loading strategy of “always append data to the same log” or “Overwrite the log every time the pipeline is executed,” there is now an option to choose whether or not a new log should be generated when the schema of the pipeline is altered, toprevent schema incompatibility issues.

• Improvement: An error message is produced if an ETL pipeline generates an excessive number of records when importing a log. This typically happens when a join operation uses an incorrect key.

• Improvement: Added a confirmation message before deleting a pipeline.

• Fix: In the ETL module, it is now possible to import CSV files that contain fields wrapped between “double quotation marks.”

• Fix: Replace log from the local file upload option in the Extract step has been fixed and improved.

• Fix: ETL no longer crashes when deleting logs from existing pipelines or rescheduling.

• Fix: Column rules are more fault tolerant when creating rules with incompatible data types.

• Fix: Resolved issues with shared users editing and viewing pipeline destination folders

• Fix: Pipelines can now be shared with empty groups.

• Fix: Column labels in the load tab are now reloaded when editing pipelines.

• Fix: Deleted columns are now immediately removed from the Transform table.

Log and Model Importer

• Fix: Error message “Multi part upload End of File” failure when uploading large uncompressed CSV files.

• Improvement: It is now possible to import CSV files in the ETL Load step that contain fields that are wrapped within double quotation marks.

• Improvement: When importing a log via the Portal, it is now possible to rename the columns, for example, to avoid a name clash. Note that you cannot rename case ID, start time, activity, resource, and role.

• Fix: When there are duplicate column names, the column name can be changed in the Log importer.

• Fix: Apromore now enforces a maximum number of rows per role, which depends on your tenancy. If there are more roles than the maximum, a warning is displayed, and the Importer only imports up to the maximum allowed rows.

• Fix: BPMN models and logs in the Apromore Workspace are properly sorted. You can also sort the files in either ascending or descending order.

Dashboard

• Improvement: Performance improvements in dashboards with multiple filters.

• Fix: When viewing a dashboard from the Portal, the Portal correctly displays a list of saved Dashboard to choose from.

Simulation

• Improvement: When you save a BPMN with simulation parameters, the information about the roles in the event in the log, if available, is also included in the simulation parameters.

• Improvement: When specifying the maximum branching probability error, an info icon informs you that in the simulation results, the gateway branching probabilities will not deviate more than the specified value.

• Improvement: The “download simulation scenario” icon/button is now relocated to the “Download” dropdown menu.

Process Discoverer

• Improvement: When you hover the mouse over any log statistics sections in the top panel in Process Discoverer, you will see the 1st and 3rd quartiles for the duration and cost statistics.

• Improvement: The case inspector now displays the cost, and the case variant inspector now displays the average cost.

• Improvement: When you select a specific case in the case variant inspector and hovers their mouse on the start event, you can see the three most frequent values of every case attribute.

Others

• Improvement: When saving or editing filters, filter templates, and dashboards, you can now add or edit a description.

• Fix: When you enter a comment or the name of an activity with multiple lines in the BPMN Editor, each line wraps with a complete word if the word is less than the maximum box width.

• Improvement: When an event that can be linked to a subprocess is selected, if you hover with the pointer over it, the pointer turns into the “selection hand”. If you do a second left-click (not a double-click), the window to link a process model appears, allowing you to link an event to a subprocess

• Fix: The log name on the Activity History page matches the correct log name.

Version 9.3

Release Date: June, 2023

Features

Root Cause Analysis

As a process manager or analyst, when a KPI target is not met, we need to understand which cases are more likely to violate the KPI. This information can help us to identify KPI violation causes and corrective actions.

In Apromore 9.4 you can now perform a root cause analysis to help in such investigations. The Root Cause Analyzer in the KPI Center displays a list of conditions under which the risk of KPI violation is considerably higher when this condition holds compared to when the condition does not hold. For more information, see Perform root cause analysis.

Automation Assessment

You can now generate a Process Automation Assessment Report (PAAR) which provides a summary of the benefits of automating one or more activities in a process. This helps you assess the time and cost improvements of automating one or more activities in a process. For example, the PAAR can indicate how the resource cost will change when a resource or group of resource is replaced by a bot. The auto generated PAAR contains the following:

• Changes to the resource cost.

• Changes to the average task duration.

• Changes to the average task cost.

• Changes to the average frequency per month.

After generating a Process Automation Assessment Report (PAAR), it is now possible to send the data in the report to a MuleSoft RPA Manager for technical assessment. The URL and credentials of a MuleSoft tenancy need to be provided to do so.

For more information, see Generate PAAR Draft.

Rework Metrics

Apromore 9.3 supports the use of rework metrics in the Process Discoverer, and in the Dashboard. The rework metrics helps to identify the effect of rework in a business process. The following rework metrics are supported:

• Total rework: Total number of times an activity has been repeated after having been executed once in a case.

• Rework duration: Total duration of the reworked activity instances.

• Rework cost: Total cost of the reworked activity instances.

In Process Discoverer, you can now display the total rework for each task, the total rework cost for each task and the total duration a resource spends on the rework.

In Dashboard, you can now display a chart in showing the rework metrics on the Y-axis against any activity attribute on the X-axis. For example, you can now create a column chart showing the average rework cost for every activity in the business process.

For more information, see Event attribute chart.

First Touch Metrics

In a customer-facing process, touchpoint activities affect the customer experience, as well as several business process metrics, such as the case duration. Apromore 9.3 now supports first touch metrics which is used to analyze the performance of the resources that perform the first touchpoint activity in each case (the first-touch activity). For example, in a complaints handling process, it is useful to analyze the durations of cases depending on which resource performed the first-touch activity in a case (the first-touch resource).

You can now display several performance statistics for each first-touch resource and first-touch activity in Apromore 9.3. This is achieved by adding a first-touch statistics table in a custom dashboard.

For more information, see First touch (FT) statistics table.

Custom Predictive Dashboards

You can now create custom predictive dashboards in Apromore. Predictive dashboards enables business stakeholders to visualize the predicted performance of a process in the near term (e.g., in the next 3-5 days).

For example, you can configure a chart in a custom dashboard to display the number of cases that will end up with a negative outcome, per country or per type of customer. Next to this chart, you can add other custom charts to display the same information for the recent past (e.g., last week) to allow managers to compare the recent performance with the predicted performance.

You can use predictive attributes in a dashboard or in filters. When used in a dashboard, you can create a chart that displays the predicted attribute against any other case attributes. For example, a heat map showing the predicted accepted cases for each channel. When used in Filter, you can filter the log based on the values in the predicted attribute. For example, you can filter cases where the predicted attribute is “Yes” or “No”.

For more information, see Use predictions in dashboards and filters.

Start Times Estimation

When importing an event log that contains end times but not start times, Apromore now provides the option of estimating the start times of every activity in an event log, given the end times. The start time is calculated from the end time attribute and the resource attribute when importing an event log.

For more information, see Start Times Estimation.

Model Publication Approval

You can now add requester and approval groups in Apromore. This is useful when publishing a model in Apromore. When a user in a Requester group requests to publish a model, the request must first be approved by a member of a corresponding Approvers group.

The approver can either approve or decline the publication of the model. Apromore also allows for two levels of Approvers (Level 1 and Level 2). A model is only published when Level 1 and Level 2 Approvers approve the publication request. If Level 2 Approver was not created, the model is published when the Level 1 Approval approves the request.

However, when a user is not assigned to a group of Requesters or is assigned to a group of Requesters that is not related to the user’s group of Approvers, the user is able to publish process model versions without approval.

For more information, see Publish Process Model.

Process Discoverer Enhancements

Discovery of Probability Distributions in Simulation Models

In the Process Discoverer, when a BPMN model is saved with simulation parameters, each activity in the model is assigned a probability distribution (normal, exponential, fixed, or uniform) depending on the distribution of activity durations in the event log. (Previously, all activities were assigned the default exponential distribution).

Discovery of Case Attributes and Their Probability Distributions

In the Process Discoverer, when a BPMN model is saved with simulation parameters, the case attributes of the event log are also saved in the simulation scenario. For each case attribute, the simulation scenario will contain its data type (String, Integer, Real, Timestamp) and its probability distribution (normal, exponential, uniform, fixed).

Log Filter Enhancements

Percentile Performance Filter

You can now filter based on a percentile over a performance metric in the performance filter. For example, you can retrieve all cases in the top-10th percentile of case duration. In other words, the top 10% fastest cases.

ETL Enhancements

Pipeline sharing

Apromore 9.3 now allows you to share an ETL pipeline with other users or groups, such that these users or groups can view, edit or own the shared ETL pipeline.

Other Improvements and Bug Fixes

• Improvement: If an ETL pipeline takes one single CSV file as input, and two events in the imported file have identical case ID, start time, and end time, the tie-break is resolved by preserving the original order of these rows in the imported CSV file. This behavior is consistent with the behavior of the log importer in the Portal.

• Improvement: In the transform step of an ETL pipeline, a user is able to undo/redo operations that create, rename, or delete a column, as well as operations to add or edit rules.

• Improvement: In the Transform view of an ETL pipeline, there is a delete button next to each column. When a column that has an associated rules is deleted, a warning message is given to prevent the user from inadvertendly losing these rule(s).

• Improvement: Compressed event logs can be imported via the S3 connector (in zip or gz formats).

• Improvement: A warning pop-up window is displayed when a user moves a folder or file to a new location and this movement would cause a change in the access rights of the folder or file.

• Improvement: A warning pop-up window is displayed when a session is about to expire, and the user is given the option to extend the session. A session timeout counter is displayed in the pop-up window.

• Improvement: When a filtered log is saved in Process Discoverer or Dashboard, a short textual description can be added. This description can be viewed in the Details section in the Portal. Users with editor or owner right can edit the description associated to a log.

• Improvement: When a new process model (version) is saved, a short description can be added. This description can be viewed in the Details section in the Portal. Users with editor or owner right can edit the description associated to a log.

• Improvement: When saving a BPMN model in Process Discoverer, the pop-up window now includes a Folder section. It is possible to select the folder where the model will be saved using the Browse button. By default, the process model is saved in the same folder as the event log.

• Improvement: Costs with a decimal component are supported in the Cost Center.

• Improvement: Performance improvements have been made to reduce the time required to apply log filters consisting of many filter criteria.

• Improvement: The Creator of each process model is now displayed in the Portal.

• Fix: The button “Download simulation configuration” is disabled for users with a Viewer role.

• Fix: Filters applied in Process Discoverer do not use the calendar (when a calendar is associated with the log).

• Fix: Incorrect access control propagation: when one access right is changed in a folder, all existing access rights are propagated to the subfolders instead of only propagating the modified access right.

• Fix: After a calendar is applied to a log, the restore button in the Calendar Management window does not restore the default (24/7) calendar

• Fix: The search box is not working in the “Case ID” filter window.

• Fix: Cannot delete a published process model

• Fix: The download button does not work for simulated logs.

• Fix: The simulation editor continues displaying the error message “the sum of the probabilities should be one” after the user has fixed the issue.

• Fix: The conformance checker is unable to match the activity labels in the model and the log when they contain double-byte (Japanese/Chinese) characters.

• Fix: When a user extracts a log from the Workspace connector and reimports it, the log cannot be used in the Dashboard nor Filters.

• Fix: SSO Users having special characters in their email address are not able to access process models.

• Fix: In published model versions, the version auto-increase feature produces an incorrect number.

Version 9.2

Release Date: April, 2023

Enhancements to Dashboards

Quick range filters in dashboards

You can apply a filter to any chart by selecting a range of values. The filter is applied to all charts in the dashboard. For example, by selecting the corresponding range in the chart of case durations and then clicking on the filter (funnel) icon in that chart, you retain all cases that have a duration of up to 60 days. The filter can be removed with the remove icon found in each chart.

Drill-throughs from dashboard

From a dashboard, you can now navigate to the Process Discoverer to visualize the event log with the currently active filter. For example, after applying a filter to retain all cases that take less 60 days, you can navigate to Process Discoverer to visualize the process map of those cases.

Enhancements to ETL Pipelines

User Interface (UI) Enhancements

The former Extract view in the ETL data pipelines module has been split into two views:

An Extract view, where you upload and designate the tables to be processed by the ETL data pipeline. The Extract view consists of one tile per data source. The available data sources are:

• File upload: Upload a file manually

• Workspace: Retrieve a file from an existing folder in the Apromore workspace

• Amazon S3: Retrieve a file from the Amazon S3 bucket of your tenancy. This option is only available to users with data engineering privileges.

• Relational database: This option requires access to a supported relational database.

A Merge view, where you specify how these tables are merged, for example via join or append operations. In the Merge view, you can switch between:

• A list view, where each operation is specified as a row.

• A graph view, consisting of tiles and arrows. A tile represents a table and an arrow indicates a merge operation.

Pipeline chaining

Once you have defined a pipeline, in the Load phase, you can chain the current pipeline to another pipeline. This means that the output of the first pipeline will be given as one of the inputs to the second pipeline. In this way, you can define your pipelines modularly. For example, a data pipeline that extracts data from a CRM system can be chained with a second pipeline that enhances the CRM data with data from a legacy system.

Eviction periods in delta uploads

When a delta upload is performed, you can specify that only the data of the past X days (e.g. 90 days) is kept in the event log. Data older than this limit is evicted.

Enhancements to Business Process Simulation

External delays in arcs

After selecting an sequence flow (arc) in the business process editor, you can set an external delay in the Simulation tab. For example, you can set the external delay to 10 minutes. Each time this arc is traversed during a simulation, the specified delay (e.g. 10 minutes) is added to the current case duration. This delay is equivalent to inserting an intermediate timer event between the source and the target of the arc.

Multiple inter-arrival timetables

You can specify different inter-case arrival times for different periods of the day or week. For example, you can specify that the arrival time from Monday to Friday 8:00 to 18:00 is one case every two minutes (30 cases per hour), while the interarrival time on Monday to Friday between 00:00 and 08:00 and between 18:00 and 24:00 is one case every 12 minutes (5 cases per hour), and the same for the weekend times.

To specify multiple inter-arrival timetables, add an inter-arrival timetable and specify the inter-case arrival time for that timetable. To specify the previous example, you need to add four timetables: Monday-Friday 00:00 to 08:00, Monday-Friday 08:00 to 18:00, Monday-Friday 18:00 to 23:59:59, and Saturday-Sunday 00:00 to 23:59:59, and you then need to assign the corresponding inter-arrival times to each timetable in the General tab of the simulation editor. The timetables should first be specified and named in the Timetables tab of the simulation editor.

Duration-based conditions in the conditional flows

You can use the case duration as an attribute when you specify conditions in a sequence flow coming out of a decision gatway (a conditional flow). The case duration is interpeted as the time since the creation of the currently simulated case. For example, you may specify that a flow of a decision gateway should be taken when the time since the start of the case is more than 8 days. In this case, if the currently simulated case has been ongoing for more than 8 days, this pathway will be taken. You can combine duration-based conditions such as this one, with conditions based on other case attributes.

Fixed cost per activity execution

You can specify that each time an activity is executed, we incur a fixed cost, such as a material cost or a pay-per-use fee for an external service. For example, you can specify that there is a fee of 2 dollars each time we perform a credit history check. This fixed cost is added to the labor cost of performing the credit history check.

Assignment of activities to roles

You can now assign an activity to a role in the simulation editor. A role is defined as one or multiple resource pools. For example, a role “Claims Handler” can consists of two resource pools: “Senior Claims Handler” and “Junior Claims Handler”. Assigning an activity to a role means that any resource belonging to one of these resource pools may be assigned to this activity.

Enhancements to Predictive Process Monitoring

Prediction refresh after delta upload

• Predictions are re-computed after every delta-upload to an event log.

• Each remaining time prediction is now accompanied by a confidence interval.

Enhancements to User Administration

User activity history

• Each user can see the history of their recent operations, by using the User menu (in the top-right corner). This allows users to retrace the steps they took to achieve a result. The history can be exported as a spreadsheet. The history only contains the steps performed without details about the data.

• Users with administration privilege can view the history of activity of all users in their tenancy.

License management

• Users with administration privileges can view license parameters (e.g. number of available user licenses).

• When a new role is created, a license type must be assigned to it.

• When a role is assigned to a user, the available licenses are updated.

Minor Improvements and Bug Fixes

• Improvement: Whenever a log download completes, notifications are shown in a dedicated icon (top-right corner of any window).

• Improvement: In the ETL data pipelines, the log schema defined in the Load phase is saved and reloaded every time a pipeline is edited.

• Improvement: In Process Discoverer, in the Cost Center window, you can assign a calendar to each role separately. If a calendar is assigned to a role, this role-level calendar overrides the calendar assigned to the whole log (if there is one). This feature allows you to define different timetables for different roles (e.g. one timetable for Claims Analyst and another one for Claims Officer).

• Improvement: In the quick filter window in Process Discoverer, when a case attribute is selected, the values of the selected case attributes are immediately displayed (no click required).

• Improvement: In the BPMN editor, you can now copy a map or part of a map from one BPMN model to another.

• Improvement: In the BPMN model editor, you can copy-paste an element or a selected set of elements from one model editor window to another.

• Improvement: In the simulation editor, you can specify a time-zone for the simulation. All times during the simulation are interpreted in this time zone.

• Improvement: In the simulation editor, you can download the simulation parameters in CSV format (spreadsheet).

• Improvement: In the simulation editor, in the Task tab, two new options are available in the type of probability distribution: histogram distribution and skewed uniform distribution.

• Improvement: In the simulator, after running a simulation, the simulated event log now contains columns corresponding to each case attribute specified in the simulation scenario, a role column, and cost information. The inclusion of roles and cost information allows the simulated log to be analyzed using cost overlays in Process Discoverer and cost metrics in the Log Filtering module.

• Improvement: All functionality is now available in the contextual menus (right-click menus). Accordingly, the top menu bar has been removed from the Portal.

• Improvement: Faster loading times when importing event logs of smaller sizes (less than 10MB).

• Improvement: Performance improvements in the log animator.

• Fix: When a user with a special character in the email id logs in via SSO and opens BPMN Editor, the model does not load.

• Fix: When an administrator tries to change a role of a user with a special character in the email id, the page refreshes.

• Fix: When a user uses the workspace connector to extract logs, the column names are not readable names.

• Fix: In the Attribute filters, when an attribute is of type timestamps, the values are displayed as numbers instead of formatted dates and times.

• Fix: Version numbers starting with zeroes in the minor and micro value positions are incorrectly displayed in the portal (e.g. 1.01 displayed as 1.1 and 1.1.01 displayed as 1.1.1).

• Fix: The event log importer does not return an error message when the start time of an activity instance is greater than its completion time.

• Fix: A empty (blank) window is displayed instead of the case timeline when the user has ignored some attributes during log import.

• Fix: When one of the case attribute is a numerical and contains Null (empty) values, the dropdown of case attributes in the Attribute Filter lists some event attributes in addition to the case attributes.

Version 9.1

Release Date: March, 2023

Feature/Enhancement

KPI Center

Apromore now provides the ability to define Key Performance Indictors (KPIs) to measure process-level conformance and performance. A process KPI is either an absolute number or a percentage of cases (across an entire process or a subset of the process) that fulfill a condition. Examples of KPIs include:

• Percentage of cases in the entire log that have completed in more than 5 days

• Number of cases where the invoice was approved by the same perform who approved the invoice payment

You can display a list of KPIs and their associated values in the “KPI popup” in the Portal, Process Discoverer, or Dashboard. You can create additional KPI tiles in the Dashboard. These tiles are synchronized with the KPIs, and they change as the KPIs are edited.

Enhancements to Business Process Simulator

The Business Process Simulator now includes the following enhancements:

• We can specify that certain cases should be prioritized over others based on case attributes. For example, we can specify that cases where the CustomerType = “Premium” should have higher priority than those where CustomerType = “Regular”. Resources are first allocated to activity instances within cases with higher priority.

• We can define “Teams” in a simulation model. A team is a set of roles. For example a “Claims Handlers” team may consist of three roles: “Junior Claims Handlers”, “Senior Claims Handlers” and “Lead Claims Handlers”. If an activity is assigned to a team, an instance of this activity may be assigned to any resource whose role is part of the team.

• We can assign multiple roles or multiple teams to the same task. If a task is assigned to multiple roles, the task may be performed by any resource who has this role.

• We can set the maximum deviation in the branching probabilities. If the probability of a conditional flow is 50%, and the maximum deviation is 5%, then in any simulation, this conditional flow will be chosen between 45% and 55% of times (counting the cases where the source node of the conditional flow is reached).

• We can limit the number of times a conditional flow is taken. If the limit of a conditional flow is set to 5, then this conditional flow will not be taken more than 5 times in any given case. This feature allows users to prevent infinite loops, or to prevent situations where a loop is executed for unreasonable number of times.

Enhancements to Process Discoverer

• Quick Filters: We can now apply a case attribute filter with one click in the Process Discoverer, for example to view the process map for “Premium” customers only or for “Regular” processes in one click

• Case Timeline View in Process Discoverer: We can open the case timeline view in the Process Discoverer by double-clicking on a case in the “Case Inspector”.

Enhancements to Dashboards

• Resource handoff heatmaps: We can now create a heatmap to display how many times a resource hands over work to another resource.

• Consecutive activities heatmaps: We can now create a heatmap to display how many times an activity is followed by another activity to find the most frequent transitions

Enhancements to Process Model Editor

• Apromore now provides the ability to hide text annotations in a process model.

• We can now attach multiple images or multiple documents to an activity.

• Published models are now frozen. They can only be edited when unpublished.

• We can now publish multiple versions of the same model.

Improvements and Bug Fixes

• Improvement: A user can now select scenario timezone in the Business Process Simulator.

• Improvement: Additional options like average cost, average frequency, relative case frequency, median duration and max duration are added to the abstraction settings.

• Fix: When a task type is changed to a subprocess, the BPMN editor becomes unresponsive.

• Fix: When a user sets incorrect timestamp in ETL, the ETL window becomes unresponsive.

• Fix: When nodes slider is set to less than 100 in Process Discoverer, the BPMN model could not be saved.

• Fix: When user made any changes in the BPMN Editor, the auto save feature did not work and the changes were not saved.

• Fix: When user imports a log, the columns were not automatically detected due to presence of all uppercase letters.

Version 9.0

Release Date: December, 2022

Feature/Enhancement

New process mining engine based on Big Data technology

• Apromore now provides you with the ability to handle event logs of up to hundreds of millions of events. The new data layer of Apromore leverages Amazon’s elastic map-reduce technology, which enables you to start with a smaller capacity and seamlessly scale up to larger datasets sizes based on your needs.

Delta Upload

• You can now append additional events to an existing event log. For example, you can add data from April 2022 to an event log containing data for the period January-March 2022. Delta uploads can be triggered via ETL or APIs. The associated metadata like filters and dashboards are updated automatically.

S3 and Workspace Connector

• Apromore now allows you to pick files from Apromore’s S3 data volume or a user’s workspace using ETL. A user should have a Superuser or Data Engineer role to use the S3 connector.

Recent and Favorites

• A user can now see the list of recent files they have been working on, and can also mark files and folders as favorites in the Apromore workspace.

Relative Filters

• You can define tiles and gages that display the percentage of cases within a population that fulfill a set of criteria. For example, you can define a tile that displays the percentage of cases in Australia (the population) that have a case duration greater than five days (the relative filter). This can be achieved by means of the “reset counter” button in the Filter window. The reset counter button divides a list of filter criteria into two groups separated by a line. The criteria above the dividing line define the population (e.g. country = “Australia”), while the criteria below the line define the relative filter (e.g. case duration > 5 days).

Additional ETL Operators

• In the Transform section of the ETL data pipelines environment, you can now use the following operators:

1. Remove a row from the dataset

2. Check if a cells “contains” a pattern (string matching). For example, you can check if a cell starts with a prefix “US-”.

3. Check if a cell is of a given type (“Is of type”), for example, check if a column is numeric. This allows you, for example, to define a rule that removes all rows such that the value of column “Amount” is not numeric.

Improvements and Bug Fixes

• Improvement: A user can now auto align elements in the BPMN Editor.

• Improvement: A user can now choose to whether or not enable autosave option in BPMN Editor.

• Improvement: A column of type Numeric or Timestamp (except for columns tagged as the Start Timestamp or the Completion Timestamp) may contain empty values. These empty values will show up as NULL values in the dashboard and in the filters.

• Fix: When an event log with a Japanese special character is opened in process discoverer, the process map not visible.

• Fix: When a user Is viewing a change in the model comparator, the positioning of models is lost.

• Fix: When charts are exported from dashboards, the Japanese labels appeared as garbled text.

Version 8.5

Release Date: August, 2022

Feature/Enhancement

Activity and Case Cost Metrics in Dashboards and Filters

• Apromore now allows you to use cost metrics in the widgets of the dashboard and also provides the ability to specify cost-based filters at the case and node level (activity, resource, role, etc).

Simulating a Model with Categorical and Numerical Attributes

• You can now simulate a model by defining different categorical and numerical attributes and use them as conditions from outgoing arcs of (X)OR-splits.

Improvements and Bug Fixes

• Improvement: Log animation can now be performed on a BPMN model with pools, lanes, and data objects/stores.

• Improvement: A subprocess can now be connected to a specific version of an existing process model.

• Improvement: A user can now traverse between different subprocesses when published.

• Improvement: A user can now choose the desired location to save a model.

• Improvement: The size of different tasks can now be changed in the BPMN editor.

• Fix: When exporting a BPMN model as a PDF/PNG, the model name was a generic name.

• Fix: When saving a simulated log, the resultant log was saved in a wrong location.

• Fix: When opening an event log containing Japanese characters, the process map was not visible due to the presence of the katakana middle dot character.

• Fix: When exporting a BPMN model containing Japanese characters as PDF, the characters were not visible.

Version 8.4

Release Date: June, 2022

Feature/Enhancement

Predictive Process Monitoring

• Apromore now allows you to train one or more predictive machine learning models from an event log. Given an event log, you can train a machine learning model to predict:

1. The remaining time of an ongoing case until its completion

2. Whether an ongoing case will reach a given outcome or not, for example, will a case in a price quotation process reach a state where the customer places an order or will an order-to-cash process reach a state where the customer returns the product.

You can also view the quality metrics of a trained machine learning model, such as its accuracy metrics, as well as different charts to explain how the predictor works, such as the most important features that the model uses to make predictions. Given an event log containing data about ongoing cases of a process, you can use the predictive models you have previously trained to generate a table with predictions for each of the cases in the event log.

Mulesoft Anypoint Connector for Apromore

• The Mulesoft Anypoint Connector for Apromore allows you to ingest data from external systems into Apromore. For example, you can use the Apromore connector to ingest incident management data from Service Cloud to perform analysis to uncover different friction points like bottlenecks and identify improvement opportunities in the process.

Compatibility:

Application/Service	Version
Mule Runtime	4.3.x and later
Anypoint Studio	7.11.x and later

ETL Vertical Union

• Apromore now allows you to perform a union of two event logs. For example, if you have an event log of an order-to-cash process for the period January-March, and another event log of the same process for the period April-June, you can create an event log for the period January-June by doing a Union of these two event logs in a data pipeline in the ETL module. The two event logs in a Union do not necessarily need to have the same columns. For example, you can join an event log of a purchase order handling process with an event log of a product delivery process (child process). The union operator will return a log with the union of the attributes in one log and in the other (but the shared columns are only represented once), and the union of the rows in the two logs.

ETL Parent-Child Union

• Apromore allows you to perform a parent-child union between an event log of a parent process and an event log of a child process. This union operator is specifically designed for the scenario where an instance of one process (the parent process) spawns one or more instances of another process (the child process). For example, you can join an insurance policy management process (the parent process) with an insurance claim process (the child process). The Parent-Child union operator implements a best-effort approach to fill in any missing case identifiers of the parent process. In the above example, the parent-child union tries to ensure that every row in the resulting log has an insurance policy ID, so that you can use the insurance policy ID as a case identifier when loading the resulting log into the Apromore workspace.

Resize font size in BPMN Editor

• Apromore now allows you to change the font size of BPMN elements in the BPMN editor.

Improvements and Bug Fixes

• Improvement: The conformance checker layout algorithm has been improved to relay the new elements in the canvas.

• Improvement: A parameter can be configured to assign viewer as a default role for newly created users.

• Improvement: Existing APIs have been migrated to make use of Spring Rest.

• Improvement: An operator that can be used to round of the number of decimals of a column has been added in ETL

• Fix: When exporting a BPMN model as a PDF with attachments, the PDF did not include the attachments

• Fix: When checking the last activity details in the access management window, the date field was empty.

• Fix: When exporting a PDF from a BPMN model containing Japanese characters, the activity names were not visible.

Version 8.3

Release Date: April, 2022

Feature/Enhancement

Data-driven Simulation

• Apromore now allows you to automatically discover a BPMN model with simulation parameters from an event log. When saving the BPMN model in Process Discoverer, select the option “include simulation parameters” to obtain a model that is ready for simulation.

Cost Overlay

• Apromore now allows you to display cost metrics on top of a process map or a BPMN model in the Process Discoverer. This option is available in the “overlay” section of the Process Discover menu. In order to display a cost overlay, you should associate a cost per time unit to each role present in the event log.

Import and Export of Dashboard and Filter Templates

• Apromore now gives you the option of exporting and importing dashboard and filter templates. To export/import a dashboard or filter template, select the option “Load template” in the Dashboard/Filter window.

Auto save a BPMN Model

• Apromore now automatically saves your work in the BPMN Editor so that you can revisit your changes in case of accidental closing of the BPMN Editor.

Link subprocess to other processes

• Apromore now allows you to link a subprocess to other processes. You can choose to link your subprocess with a new or an existing process. To link a subprocess to a process, click on the “+” button of a subprocess activity and link it to the desired process.

Comments in BPMN Editor

• Apromore now allows you to create and edit comments in the BPMN editor. Comments can be attached to any flow object in BPMN (activity, event, or gateway).

Property Drawer in BPMN Editor

• Apromore now allows you to create different custom attributes for different BPMN elements. For example, you can use the properties drawer in the BPMN editor to attach custom attributes such as “cost”, “priority”, or “risk” to a given activity.

Anonymization in ETL

• The “anonymize” toggle button is now also available in the ETL data pipelines module. If you turn on the button for a given column, all values in that column will be replaced by hash codes when the data is imported.

Custom Roles

• You can now create custom roles (e.g. Auditor, Financial Manager) and by assigning visibility options to a user based on your organizational requirements (e.g. an Auditor can open an event log in read-only mode in Process Discoverer and Dashboard but cannot apply filters nor run simulations).

LDAP Support

• Apromore can now be connected with your corporate LDAP directory for authentication (in addition to the existing SAML-based single sign-on option).

Improvements and Bug Fixes

• Improvement: You can choose to view the case variants by percentage, duration, and alignment ratio in the conformance checker.

• Improvement: You can now export multiple logs or models at a time.

• Improvement: You can now sort the artifacts in the portal by type, name, creation date, last version, last update, or owner.

• Improvement: A message is shown when there are invalid rows discovered during log import due to the consideration of daylight savings time.

• Fix: The ordering of the folder structure in the left panel was not following a sequence.

• Fix: When importing a parquet file via the log importer, the error report only contained the first error.

• Fix: When copying and pasting the style formatting on a dashboard tile/chart, an error message is displayed.

• Fix: When the language was switched to Japanese, the conformance checking option was disabled.

Version 8.2

Release Date: January, 2022

Feature/Enhancement

Publish Models

• Apromore now allows you to publish a BPMN model and share the URL with other users.

Additional charts in dashboard

• Apromore now allows you to use different charts like heatmaps, treemaps, and solid gauge in the dashboard.

Improvements and Bug Fixes

• Improvement: You can now change the color of elements from a palette in the BPMN Editor.

• Improvement: You can now add images, icons, hyperlinks as attachments to your BPMN model in the BPMN Editor.

• Improvement: You can now see the compute variability ratio between the case variants and cases in the process discoverer.

• Fix: A parquet file could not be exported for a dashboard view having more than one table of same type and attribute.

• Fix: An error message popped up when trying to export a CSV in dashboard with a view consisting of two different tables.

Version 8.1

Release Date: December, 2021

Feature/Enhancement

Conformance Checker

• Apromore now allows you to compare a log and a BPMN model to perform delta analysis. For example, When you compare a process model and an event log using delta analysis, the tool displays the differences and allows you to overlay the differences on top of the process models.

Improvements and Bug Fixes

• Improvement: You can now move artifacts in the Apromore workspace by drag and drop method.

• Improvement: Functions like launching dashboards/filters can now be accessed by right clicking on a log/model.

• Improvement: Functions such as cut/copy/paste can now be performed via keyboard shortcuts.

• Improvement: Custom calendars can now be accessed via process discoverer and dashboard.

• Fix: The dashboard was not loading when it was associated to a custom calendar.

• Fix: Duplicate parquet files were generated from different case variant table in the dashboard.

• Fix: The search similarity results view was mixed up in the Apromore portal.

Version 8.0

Release Date: November, 2021

Feature/Enhancement

Custom Calendars

• Apromore now provides the ability to create and edit custom calendars and to associate a custom calendar with an event log. When creating a calendar, you can include public holidays based on your location and add custom holidays to the calendar.

Delta Analysis between process models

• Apromore now allows you to compare two BPMN process models to perform delta analysis. For example, you can use delta analysis to compare a process model discovered from an event log (capturing the as-is process) with a reference process model (capturing a to-be process). When you compare two process models using delta analysis, the tool displays the differences and allows you to overlay the differences on top of the process models.

Filter and Dashboard Templates

• Apromore now provides the ability to save a filter or a dashboard template that you have defined on an event log, and to apply the saved template to another log. For example, you can create a dashboard template on an event log containing all the cases of an order-to-cash process that completed in October, and then copy it to an event log containing all the cases of the same order-to-cash process for the month of November.

Internationalization

• Apromore now provides the option to switch between different languages. Currently, we support English and Japanese, with German coming soon. New languages can easily be added.

Support for Group Authorization

• Apromore now supports group-based authorization using groups extracted from an external identity provider (SAML or LDAP).

Anonymization

• You can now choose to anonymize one or more columns during log import by selecting the “anonymization” icon on the columns you wish to anonymize. For example, you may anonymize sensitive information such as case IDs and resource names.

Automatic data ingestion via the S3 connector

• You can now ingest data into Apromore via our AWS S3 Connector. The logs can be pushed into S3 buckets via data ingestion pipelines, and picked up automatically by Apromore to be registered in Apromore’s repository. The S3 bucket can be hosted by Apromore or the customer, in their private AWS cloud. Encryption can be managed by AWS with customer-provided master key, or directly by the customer.

Case and Event attribute on X and Y-axis

• We have added more customization options to Apromore’s Dashboard. You can now display numerical or categorical case/event attributes on the X and Y-axis of any chart in a dashboard. For example, you can create a chart to display the number of resources (Y-axis) who perform each activity in the log (X-axis). If you select a numeric attribute in the Y-axis, you can also select an aggregation function such as average, total, median, etc. For example, you can create a chart that displays the countries on the X-axis and for each country, the total revenue on the Y-axis.

KPI Thresholds and Reference lines

• In the Dashboard, you can now set KPI thresholds and add reference lines for average and median, as well as custom reference lines, along both X and Y-axis. For example, you can choose to add a KPI threshold to separate the cases with a higher waiting time from those with a lower waiting time, or show the average number of active cases over time in the Work-in-Progress area chart.

Exporting Dashboard Analytics to S3 buckets

• Apromore now provides the capability to export dashboard analytics as CSV or Parquet files and save these locally or on an AWS S3 bucket.

Between Filter

• With a couple of clicks, you can now define a new filter criterion to retain or remove events between the first or last occurrence of a source and target node in the process map. For example, you can retain all events between the first occurrence of the “Send invoice” activity and the last occurrence of the “Receive payment” activity.

Save and edit ETL data pipelines

• Apromore now supports the ability to save and edit data ingestion pipelines. For example, you can now edit an existing pipeline by replacing the existing logs with an event log with the latest data.

Performance Improvement in Dashboard

• The performance of the operations performed on large logs in the dashboard has been improved.

Case Variant Inspector

• You can now inspect each case variant individually using the case variant inspector in the Process Discoverer plugin, and check out the value of attributes for each node in the variant.

Improvements and Bug Fixes

• Improvement: The start and end timestamps were exported in a single column when exporting an event log in CSV format. Now, both timestamps are placed in separate columns within the same row.

• Improvement: You can now choose to tag a column as a Perspective in the Log Importer. Once done, you can switch between these perspectives in Process Discoverer.

• Improvement: The Log Importer now supports ISO-8859-1 (Latin-1) encoding type.

• Improvement: An event log with a standard ISO-8601 format timestamp can now be imported into Apromore.

• Improvement: The ETL plugin now supports the ability to subtract two timestamps and trim a column value.

• Improvement: You can now upload zipped BPMN models

• Improvement: You can now set the name of the log when importing it into Apromore

• Improvement: A BPMN model shared with a viewer cannot be exported/modified.

• Fix: A log containing a case ID greater than 15 digits could not be uploaded.

• Fix: The labels on gateways in a BPMN model were not getting updated when changing them.

• Fix: Uploading files in Apromore using the ETL plugin used to throw an error when connecting to an S3 bucket with a name greater than 30 characters.

Version 7.20

Release Date: June, 2021

Feature/Enhancement

Extract-Transform-Load (ETL) Console

• Apromore now comes with a graphical ETL console that allows you to compose event logs from one or more tables or data sources. The ETL console allows you to define data pipelines to extract tables from relational databases, transform these tables to compose an event log, and load the resulting event log table into Apromore. In addition to different join operations, you can remove columns and create columns in the event log by composing existing columns using arithmetic, concatenation, and find-and-replace operations. For example, you can add a “Cost” column to an event log and compute this cost based on the hourly rate of your resources and the duration of tasks. You can also schedule a data pipeline to run hourly, daily, weekly, or monthly jobs to extract, transform, and load event logs into Apromore.

Single Sign-on Support

• Apromore can now be connected with your corporate identity system for single sign-on (SAML or OpenID).

Storage in Amazon S3 buckets

• Apromore now comes with an option to store your event logs in a dedicated Amazon S3 bucket for high reliability and security (available for enterprise licenses only). Your IT security team can be given rights to audit your tenancy’s S3 bucket. The data in your tenancy’s S3 bucket is protected at all times using either an Amazon S3-managed encryption key or an encryption key provided by your IT team. This enables your IT team to have full control over access to your event logs.

Transfer Ownership

• Before deleting a user, you can transfer ownership of all the assets (models, logs, analytics artifacts) to better manage business continuity.

Fine-Grained Sharing

• You can choose to share individual dashboards and filters associated with a log by giving a user restricted viewer rights. For example, when sharing an event log, you can choose which specific dashboards or filters you wish to share, as an alternative to sharing all the associated dashboards and filters.

Case Length Filter

• You can now filter out cases based on case length (number of activity instances in the case). For example, you can retain or remove all cases whose length is between 3 to 15 activity instances.

Undo/Redo Filter

• You can remove/reinstate a filter criterion using the undo/redo filter buttons in Process Discover.

Performance Improvements in Filter

• The performance of the filter operations on large logs has been improved.

Look-and-feel improvements in Log Animator

• The ability to hide/unhide tokens of a log in a multi-log animation has been introduced. You can also customize the color of the tokens.

Report Issue

• A Report Issue button has been introduced to allow users to report bugs.

Recursive Folder Sharing

• You can now share a folder in such a way that all sub-folders and files inside that folder are shared along, recursively.

Improvements and Bug Fixes

• Improvement: When trying to animate a syntactically incorrect process model, the log importer now shows user-friendly error messages.

• Improvement: You can now animate both process maps and BPMN models directly inside Process Discoverer.

• Improvement: File names can now contain commas and periods

• Improvement: A new “Generate report” function in the dashboard allows you to choose which tiles, charts, and tables you wish to include in the Word, PDF or Powerpoint report (or you can select “all” to include everything).

• Fix: The BPMN editor gives an error message when you change the version number to a different format.

• Fix: The shortcut for opening the arc duration filter is not working.

• Fix: In the slice log window, the number of cases is incorrect.

• Fix: Column names with accented letters are not displayed in the log importer.

• Fix: When a logs contains empty column names, no data is shown in the log importer.

• Fix: Access rights management window gives an error when the group name matches the user name.

• Fix: The fields in the user creation window are not validated

• Fix: Incorrect error message is given when a file name contains more than 60 characters.

Version 7.19

Release Date: January, 2021

Feature/Enhancement

Process Simulator

• You can now attach a simulation scenario to a BPMN model and simulate a model with an attached simulation scenario. The output of a simulation is a simulated log. You can analyze a simulated log using all the functionality available in Apromore (Process Discoverer, Dashboard, etc.). In the Dashboard, you can view a range of statistics for simulated logs, including case duration, case duration within timetable, case waiting time, cycle time, waiting time, and cost.

Node duration performance filter

• You can filter out cases based on the node’s duration.

Arc duration performance filter

• You can filter out cases based on the arc’s duration.

Secondary attribute filter

• You can filter out cases based on two attributes simultaneously, for example, retain or remove all cases where there is an event with Activity = “Create order” (primary attribute) and Resource = “John Smith” (secondary attribute).

Share filters and dashboards

• Multiple users can edit filters and dashboards concurrently.

Dashboard auto-saving

• You can now choose whether or not to auto-save changes to your dashboards.

Export dashboards

• You can now export your dashboards in a variety of formats incl. Word and PowerPoint to create professionally looking reports.

Timestamp format detection in CSV Importer

• A wider range of timestamp formats are now supported.

Timezone detection in CSV Importer

• When you import a CSV/XLSX/Parquet file, the timezone is automatically detected.

Import Parquet and XLSX files

• You can upload a parquet or XLSX file.

Performance and look-and-feel improvements in Log Animator

• The responsiveness of the log animator has been improved. When a large number of tokens are stuck in the same arc, a bubble is shown instead of showing individual tokens.

Version 7.18

Release Date: October, 2020

Feature/Enhancement

Portal grid view

• You can browse through the folders and files in Apromore’s Portal in grid format (default mode) in addition to the old list format.

Import log from URL

• You can import a file from Dropbox, Google Drive, Microsoft OneDrive or from any URL.

• See: Upload a file from URL

Save and share filters

• You can save filters associated with a log and share these filters alongside the event log.

• Note: Only the owner of an event log can save, edit, or remove the filters associated with that log. Other users can define temporary filters but not save them.

Customize, save & share performance dashboards

• You can add, remove, or customize any performance indicator, chart or table in the default views of the performance dashboard.

• You can add one or more custom views to the performance dashboard of a log. Custom views can be created from existing views or from scratch.

• You can save and share dashboards. All changes you make to a performance dashboard are saved together with the event log and are visible to all users who have access to the log.

• See: Video demonstration of the new Performance Dashboard.

• Note: Only the owner of a log can edit the performance dashboard of the log. Other users can make a copy of a log and customize the dashboard on a copy of the log

Reusing CSV import schemas

• When you import a CSV file, the mapping of the columns (schema mapping) is automatically saved. When you later import a CSV file with the same column headers, the CSV importer prompts a dialog box to let you choose whether to apply the saved mapping or not.

Clear applied filters

• You can clear all the filters on the current log in Process Discoverer with a single click.

Search box in Process Discoverer

• A new search box in Process Discover allows you to search for a node (e.g. activity) by its name or a prefix of the name. All nodes that match the search string are highlighted.

Enhanced users and groups management

• You can grant access rights to any folder and file you own either to an individual user or to a group.

• Administrators can create groups and assign users to groups.

• See: Users and groups management

Download process performance stats from dashboard

• You can download the data behind any chart or table in the performance dashboard in CSV format, or you can download all CSV files with the data in the performance dashboard in a single zip file

Copying and moving logs or process models

• You can copy or move files across the folders in the Portal via the copy, cut, and paste icons.

Improved session management

• We have made improvements to session management to improve performance and reduce session timeouts.

LDAP Authentication

• System administrators can more easily configure Apromore to connect to a corporate LDAP directory for authentication.

New shortcuts for filtering

• You can open the case filter, case variant filter, event filter, activity filter, performance and timeframe filters in one click from the Process Discoverer by clicking on the respective icons in the Log Statistics and Temporal statistics sections of the Process Discoverer.

Relative case frequency overlay

• You can now display the relative case frequency on each node/arc in the Process Discoverer. The relative case frequency is the percentage of cases in which a given node or directly-follows relation occurs.

Bug Fix

Folder and file renaming

• The portal gives an error message when you enter forbidden characters in file name.

Handling of long labels

• Fixed a bug that made long activity or node labels to go across the corresponding node in the process map/model.

Version 7.16

Release Date: June, 2020

• New Features:

  • Tiles of performance measures can now be created in custom dashboards. These can be useful to display a set of standard and user-defined KPIs, in addition to the custom charts

  • Aggregated log stats can now be exported from the Dashboard into CSV files

  • Reimplemented median calculations for frequencies and durations in Process Discoverer

  • Introduced “breadcrumbs” for easier Portal navigation

  • Process models and logs can now be searched for from the Search bar of the Portal

• Improvements:

  • Improved memory management across various plugins

  • Process models created by the Merge plugin are now automatically laid out

  • Improved automatic detection of various timestamp formats in CSV Importer

  • Automatic detection of case attributes and event attributes in CSV Importer

  • Removed unused fields in the Portal

  • Simplified import of process models

  • Multiple visual and performance improvements in custom dashboards

• Bug Fix:

  • Fixed issue with not being able to animate some logs

  • Fixed issue with misaligned timelines in the log animation

  • Fixed issue with CSV importer failing due to missing case identifiers or activity names

  • Fixed issue with the results of Similarity Search not being displayed until the Portal is refreshed

  • Fixed some issues with the Rework & repetition filter

Version 7.15

Release Date: May, 2020

• Process Discoverer: New ribbon interface makes it easier to tune and switch between visualization and abstraction settings

• Dashboard: Ability to create customized charts with user-defined KPIs

• Portal:

  • Enhanced user registration screen

  • Ability to choose file format when downloading event logs (XES or CSV, and encoding for CSV files)

• Log Animation: Visual improvements in the Log Animation

• CSV Importer: UI and performance improvements

• Various bug fixes and performance improvements

Version 7.14

Release Date: March, 2020

• Process Discoverer:

  • Re-engineered plugin with new internal, high-performing data structure

  • Re-designed user interface with new abstraction functionality and statistics visualization

• Filter:

  • Cosmetic improvements

  • Performance improvements

• Dashboard:

  • Log cloning feature

  • Cosmetic improvements

  • Performance improvements

• Various bug fixes and performance improvements

Version 7.13

Release Date: February, 2020

• New modern UI featuring consistent branding and look & feel

• CSV Importer:

  • Support for non UTF-8 encodings

  • Fault tolerance (e.g. missing attribute value)

• Filter:

  • New Rework & Repetition filter makes it easier to track cases with repeated tasks (e.g. rework due to amendments)

  • Ability to search for specific cases and event attributes when setting filters

  • New Case variant and Case ID Inspector view

• Process Discoverer:

  • Pie charts to show the percentage of cases, variants and events left after applying a filter

  • Performance improvements

• Dashboard:

  • Distinction between Case attributes and Event attributes

  • Relative frequency in Activities and Resources views

  • Performance improvements

• Single Editor for process modeling based on BPMN.io (legacy editor deprecated)

• Various bug fixes

Version 7.10

Release Date: December, 2019

• Filter:

  • Advanced case variant filter to show the distribution of case variants

  • Advanced options for the Eventually-follows filter

  • Filtering by processing time, waiting time and case utilization when events have start timestamps

  • Advanced options for Time window filters (case contained in the time window, active in, starts in, ends in)

  • Ability to download and upload filter criteria for reuse

  • Pie charts to show the percentage of cases, variants and events left after applying a filter

  • Minor cosmetic fixes

• Dashboard:

  • Support for case-level attributes

  • Minor cosmetic fixes

• CSV Importer:

  • Improved data type detection

  • Ability to import zipped and gzipped CSV files

• Process Discoverer: Various bug fixes and improvements

• Caching mechanism to improve system performance

Version 7.8

Release Date: October, 2019

• Filter: Advanced filtering options

• CSV Importer: More robust CSV Importer

• Improved handling of security permissions for event logs

• Process Discoverer:

  • Performance and visual improvements

  • Various bug fixes

Version 7.6

Release Date: August, 2019

• Filter: New Filter plugin

• Process Discoverer: Various bug fixes and performance and visual improvements

• CSV Importer: More robust CSV Importer

• Improved handling of security permissions for event logs (Security button)

• Migrated to the current version of ZK libraries 8.6.0.1

• Dynamic switching of UI themes (Account -> Change theme)

Version 7.5

Release Date: August, 2019

• Dashboard: New Dashboard plugin

• Process Discoverer:

  • Automatic centering and fit to screen when changing layout

  • Various bug fixes and performance improvements

• CSV Importer:

  • Improved tolerance for errors while importing CSVs

  • More robust mechanism to recognize timestamp format

  • Multiple UI improvements

• Added password recovery feature