Migrating Legacy widgets to IBM Process Mining NextGen

Widgets that are still supported in IBM Process Mining NextGen:

  • Preconfigured widgets

    • Process model
    • Filter summary
    • Case variants
    • Lead time distribution
    • Case KPI summary
  • Configurable filters

    • Elastic
    • Matrix
    • Table

    Use the Elastic widget instead of the Table widget to use all IBM Process Mining NextGen's capabilities.

    • Annotation
    • Card

Widgets that were created in IBM Process Mining Legacy projects and migrated to IBM Process Mining NextGen are visible but not supported. They can be recreated with the Elastic widget:

  • Configurable legacy widgets

    • Line
    • Area
    • Bar
    • Row
    • Stacked
    • Bubble

    Re-create the Bubble chart by using the Scatter chart type of the elastic widgets.

    • Scatter
    • Pie
    • Custom

Widgets that were created in IBM Process Mining Legacy projects and migrated to IBM Process Mining NextGen are still supported.

Custom widgets

Legacy Custom widgets are supported in IBM Process Mining NextGen only if they do not have any legacy backend logic.

Use the Elastic widget and the custom chart type to create custom widgets in IBM Process Mining NextGen.

Using the Elastic widget as a replacement for legacy widgets

To re-create the functions of the IBM Process Mining Legacy widgets in IBM Process Mining NextGen, use the following configurations of the Elastic widget.

Activity monitor

Activity monitor example

  • Configuration

    Dimensions
    DATE(End-Time)
    Measures
    # Activities count(*) Number
    Sum ServiceTime sum(servicetime) Lead time
  • Style

    Style for Activity Monitor

    Style for Activity Monitor

    Style for Activity Monitor

To re-create the Resource filter functions, you can use the widget filter, or use resource as a second dimension and select stacked bar chart as chart type.

Case list

Case list example

Predictive Analytics is unavailable for IBM Process Mining NextGen.

  • Configuration

    Dimensions
    Case ID
    Measures
    Is Running IS_RUNNING Text
    LeadTime leadtime Lead time
    Cost casecost() Amount
    Time % overall leadtime/overall_leadtime Percentage
    Cost % overall casecost() / overall_casecost Percentage
    Reworks count(activity)-count(distinct(activity)) Number

To use overall_leadtime and overall_casecost, create the two following project-level custom metrics. They can also be used for any other comparison.

Case list custom metrics

Case list custom metrics

Case status

Case status example

  • Configuration

    Dimensions
    IS_RUNNING
    Measures
    # Cases count(distinct(caseid)) Number
  • Style

    Style case status 1

Influencers

You can use the Prescriptive Process Mining to understand which attributes or activities have the highest negative impact on LeadTime. For more information, see Prescriptive Process Mining

Path time histogram

Numeric distributions are unavailable in IBM Process Mining NextGen.

To use Pathtime as a dimension, create a case-level custom metric and specify the activity interval you want to consider:

Path time custom metric

Use the following Elastic widget configuration to have the same functions:

  • Configuration

    Dimensions
    OPEN_RESOLUTION_PATHTIME
    Measures
    # Cases count(distinct(caseid)) Number
    Filters
    OPEN_RESOLUTION_PATHTIME > 0
  • Style

Style path time 1

Style path time 2

To use Pathtime as a dimension, create a case-level custom metric and specify the activity interval you want to consider:

Path time custom metric

Activity rework

Activity rework example

  • Configuration

    Dimensions
    Activity
    Measures
    Rework ratio count(activity)/count(distinct(caseid)) Number
    # Reworks count(activity) - count(distinct(caseid)) Number
    Rework cost sum(eventcost)*(count(activity) - count(distinct(case))) Amount

Activity trend

Activity trend example

  • Configuration

    Dimensions
    DATE(End-Time)
    Measures
    # Completed Case count(distinct(caseid)) Number
    Filters
    IS_RUNNING = 0
  • Style

Activity trend style 1

Activity trend style 2

Activity trend style 3

Automation trend

Automation trend example

  • Configuration

    Dimensions
    DATE(End-Time)
    "m/a"

    The "m/a" value refers to the column that you inserted as an automation attribute in the Editing automation attributes section.

    Measures
    Activities count(*) Number
    Resources count(distinct(resource)) Number

You can use either Activities or Resources as a measure according to your preferences. To see both measures at once, use the custom chart type.

You can implement more advanced configurations by using the custom chart style.

  • Style

Automation trend style 1

Automation trend style 2

Automation trend style 3

Behavior influencers

You can use the Prescriptive Process Mining to understand which attributes or activities have the highest negative impact on custom KPIs. For more information, see Prescriptive Process Mining.

Block stats

To re-create the functions of the Block stats widget, use the Card widget. Custom statistics can be created by using Custom metrics. For more information, see the Custom metrics in NextGen Engine section.

Changes and automation stats

To re-create the function of the Changes and automation stats widget, use the Card widget. Custom statistics can be created by using Custom metrics. For more information, see Custom metrics in NextGen Engine.

Path trend

Path trend example

  • Configuration

    Dimensions
    DATE(End-Time)
    Measures
    PathTime avg(pathtime) Lead time
    Occurrences (cases) count(distinct(caseid)) Number

Path trend filters 1

  • Style

Path trend style 1

Path trend style 2

Path trend style 3

Path trend style 4