Process Flowchart - Revision history

TeeHiet: TK-61458

2026-02-03T09:30:50Z

TK-61458

← Older revision		Revision as of 09:30, 3 February 2026
Line 4:		Line 4:

	There are two kinds of flowcharts available: ''Snowflake flowchart'' and ''In-memory flowchart''. The latter performs processing using the in-memory calculation engine (requiring to load models into memory). Both flowcharts have similar functionality, except available event type and flow measures are different, as the Snowflake flowchart has same measures available as the [[Snowflake_Chart\|Snowflake chart]]. Also in Snowflake flowchart, a filter can be set for each individual event and flow measure.		There are two kinds of flowcharts available: ''Snowflake flowchart'' and ''In-memory flowchart''. The latter performs processing using the in-memory calculation engine (requiring to load models into memory). Both flowcharts have similar functionality, except available event type and flow measures are different, as the Snowflake flowchart has same measures available as the [[Snowflake_Chart\|Snowflake chart]]. Also in Snowflake flowchart, a filter can be set for each individual event and flow measure.

			== Presets ==
			The Process flowchart provides presets that deliver immediate, high-quality visualization the process. The presets configure the flowchart to show the most relevant event types and flows, making it an ideal starting point for case-centric models. When analyzing an object-centric model, you need to select the base object type for the preset to work.

	== Visibility settings ==		== Visibility settings ==

TeeHiet: TK-57056

2026-01-13T08:44:18Z

TK-57056

← Older revision		Revision as of 08:44, 13 January 2026
Line 18:		Line 18:
	There are two resets of the zoom and position available, '''Window width''' and '''100% zoom''', which can be toggled by clicking the '''Reset zoom''' button in the bottom right. When zoom is 100%, Window width mode is activated, and when zoom is other than 100%, 100% zoom is activated.		There are two resets of the zoom and position available, '''Window width''' and '''100% zoom''', which can be toggled by clicking the '''Reset zoom''' button in the bottom right. When zoom is 100%, Window width mode is activated, and when zoom is other than 100%, 100% zoom is activated.

	[[Process_Mining_Concepts#Filter_and_Filter_Rule\|Filter rules]] can be created from the flowchart by selecting the event types and flows. When selecting only event types, you can create a filter which includes and excludes cases containing any the selected event types. In addition, you can include and exclude the selected event types (i.e. filter the events based on event types). When selecting only flows (or both event types and flows), you can create a filter to include only cases containing the selected flows and event types.		[[Process_Mining_Concepts#Filter_and_Filter_Rule\|Filter rules]] can be created from the flowchart by selecting the event types and flows. When selecting only event types, you can create a filter which includes and excludes cases or objects containing any of the selected event types. In addition, you can include and exclude the selected event types or objects (i.e. filter the events based on event types or objects). When selecting only flows (or both event types and flows), you can create a filter to include or exclude only cases or objects containing the selected flows and event types.

	== Event type and flow KPI's ==		== Event type and flow KPI's ==

TeeHiet: TK-57056

2026-01-13T08:40:55Z

TK-57056

← Older revision		Revision as of 08:40, 13 January 2026
Line 18:		Line 18:
	There are two resets of the zoom and position available, '''Window width''' and '''100% zoom''', which can be toggled by clicking the '''Reset zoom''' button in the bottom right. When zoom is 100%, Window width mode is activated, and when zoom is other than 100%, 100% zoom is activated.		There are two resets of the zoom and position available, '''Window width''' and '''100% zoom''', which can be toggled by clicking the '''Reset zoom''' button in the bottom right. When zoom is 100%, Window width mode is activated, and when zoom is other than 100%, 100% zoom is activated.

	~~Event type and flow based~~ [[Process_Mining_Concepts#Filter_and_Filter_Rule\|~~filter~~ rules]] can be created from the flowchart by selecting the event types and flows. When selecting only event types, you can create a filter which includes and excludes cases containing any the selected event types. In addition, you can include and exclude the selected event types (i.e. filter the events based on event types). When selecting only flows (or both event types and flows), you can create a filter to include only cases containing the selected flows and event types.		[[Process_Mining_Concepts#Filter_and_Filter_Rule\|Filter rules]] can be created from the flowchart by selecting the event types and flows. When selecting only event types, you can create a filter which includes and excludes cases containing any the selected event types. In addition, you can include and exclude the selected event types (i.e. filter the events based on event types). When selecting only flows (or both event types and flows), you can create a filter to include only cases containing the selected flows and event types.

	== Event type and flow KPI's ==		== Event type and flow KPI's ==

TeeHiet: TK-57100

2025-05-14T06:59:22Z

TK-57100

← Older revision		Revision as of 06:59, 14 May 2025
Line 66:		Line 66:
	'''Advanced''' tab has following settings:		'''Advanced''' tab has following settings:
	* '''Model''': Select [[QPR ProcessAnalyzer Project Workspace#Models\|model]] that is shown by the flowchart. This model selection overrides the model selection in the main header, allowing to create dashboards showing flowcharts from several models.		* '''Model''': Select [[QPR ProcessAnalyzer Project Workspace#Models\|model]] that is shown by the flowchart. This model selection overrides the model selection in the main header, allowing to create dashboards showing flowcharts from several models.
	* '''Cases Sample Size''' (Snowflake): Defines how many cases are randomly selected when determining variations. When not defined, sampling is not applied. Sampling is ~~only~~ applied for the variation ~~calculation, and it's never applied for the event type and flow~~ calculation. Purpose of sampling is to improve performance because instead of entire dataset only a subset is used in the variation calculation.		* '''Cases Sample Size''' (Snowflake): Defines how many cases are randomly selected when determining variations. When not defined, sampling is not applied. Sampling is always applied for the variation calculation. Purpose of sampling is to improve performance because instead of entire dataset only a subset is used in the variation calculation.
			* '''Sampling Affects Measures''' (Snowflake): Defines whether the Cases Sample Size setting is applied for the event type and flow measure calculation (i.e., measures are calculated from a sampled set of cases).
	* '''Visible Case Attributes''': Case attributes that are shown in the case attribute selector lists. This setting can be used to hide unneeded attributes for simplicity.		* '''Visible Case Attributes''': Case attributes that are shown in the case attribute selector lists. This setting can be used to hide unneeded attributes for simplicity.
	* '''Visible Event Attributes''': Similar setting as the previous, except for the event attribute selector lists.		* '''Visible Event Attributes''': Similar setting as the previous, except for the event attribute selector lists.

Ollvihe at 21:33, 2 November 2024

2024-11-02T21:33:36Z

← Older revision		Revision as of 21:33, 2 November 2024
Line 3:		Line 3:
	Event type name is by default shown as the first text line in the event type box, but it can also be hidden to show customized text. Event type measures can be mapped to Label, 2nd label and 3rd label, which are shown in the next lines in the box. Flows are shown as arrows connecting the event types, and the arrow is also indicating the process flow direction. Flow measures can be mapped to Label, 2nd label and 3rd label, which are shown in separate lines in the middle of the flow. The starting and ending flows are shown as dashed lines. When an event type is hovered, its incoming (light blue) and outgoing (dark blue) flows are highlighted.		Event type name is by default shown as the first text line in the event type box, but it can also be hidden to show customized text. Event type measures can be mapped to Label, 2nd label and 3rd label, which are shown in the next lines in the box. Flows are shown as arrows connecting the event types, and the arrow is also indicating the process flow direction. Flow measures can be mapped to Label, 2nd label and 3rd label, which are shown in separate lines in the middle of the flow. The starting and ending flows are shown as dashed lines. When an event type is hovered, its incoming (light blue) and outgoing (dark blue) flows are highlighted.

	There are two kinds of flowcharts available: ''Snowflake flowchart'' and ''In-memory flowchart''. The latter performs processing using the in-memory calculation engine (requiring to load models into memory). Both flowcharts have similar functionality, except available event type and flow measures are different, as the Snowflake flowchart has same measures available as the [[~~Big_Data_Chart~~\|Snowflake chart]]. Also in Snowflake flowchart, a filter can be set for each individual event and flow measure.		There are two kinds of flowcharts available: ''Snowflake flowchart'' and ''In-memory flowchart''. The latter performs processing using the in-memory calculation engine (requiring to load models into memory). Both flowcharts have similar functionality, except available event type and flow measures are different, as the Snowflake flowchart has same measures available as the [[Snowflake_Chart\|Snowflake chart]]. Also in Snowflake flowchart, a filter can be set for each individual event and flow measure.

	== Visibility settings ==		== Visibility settings ==

Ollvihe: /* Flowchart advanced settings */

2024-10-02T08:53:28Z

Flowchart advanced settings

← Older revision		Revision as of 08:53, 2 October 2024
Line 66:		Line 66:
	'''Advanced''' tab has following settings:		'''Advanced''' tab has following settings:
	* '''Model''': Select [[QPR ProcessAnalyzer Project Workspace#Models\|model]] that is shown by the flowchart. This model selection overrides the model selection in the main header, allowing to create dashboards showing flowcharts from several models.		* '''Model''': Select [[QPR ProcessAnalyzer Project Workspace#Models\|model]] that is shown by the flowchart. This model selection overrides the model selection in the main header, allowing to create dashboards showing flowcharts from several models.
	* '''Cases Sample Size''' (Snowflake): Defines how many cases are randomly selected when determining variations. When not defined, sampling is not applied. Sampling is only applied for the variation calculation and it's ~~not~~ applied for the event type and flow calculation.		* '''Cases Sample Size''' (Snowflake): Defines how many cases are randomly selected when determining variations. When not defined, sampling is not applied. Sampling is only applied for the variation calculation, and it's never applied for the event type and flow calculation. Purpose of sampling is to improve performance because instead of entire dataset only a subset is used in the variation calculation.
	* '''Visible Case Attributes''': Case attributes that are shown in the case attribute selector lists. This setting can be used to hide unneeded attributes for simplicity.		* '''Visible Case Attributes''': Case attributes that are shown in the case attribute selector lists. This setting can be used to hide unneeded attributes for simplicity.
	* '''Visible Event Attributes''': Similar setting as the previous, except for the event attribute selector lists.		* '''Visible Event Attributes''': Similar setting as the previous, except for the event attribute selector lists.

Ollvihe: /* Flowchart advanced settings */

2024-10-02T08:51:50Z

Flowchart advanced settings

← Older revision		Revision as of 08:51, 2 October 2024
Line 66:		Line 66:
	'''Advanced''' tab has following settings:		'''Advanced''' tab has following settings:
	* '''Model''': Select [[QPR ProcessAnalyzer Project Workspace#Models\|model]] that is shown by the flowchart. This model selection overrides the model selection in the main header, allowing to create dashboards showing flowcharts from several models.		* '''Model''': Select [[QPR ProcessAnalyzer Project Workspace#Models\|model]] that is shown by the flowchart. This model selection overrides the model selection in the main header, allowing to create dashboards showing flowcharts from several models.
			* '''Cases Sample Size''' (Snowflake): Defines how many cases are randomly selected when determining variations. When not defined, sampling is not applied. Sampling is only applied for the variation calculation and it's not applied for the event type and flow calculation.
	* '''Visible Case Attributes''': Case attributes that are shown in the case attribute selector lists. This setting can be used to hide unneeded attributes for simplicity.		* '''Visible Case Attributes''': Case attributes that are shown in the case attribute selector lists. This setting can be used to hide unneeded attributes for simplicity.
	* '''Visible Event Attributes''': Similar setting as the previous, except for the event attribute selector lists.		* '''Visible Event Attributes''': Similar setting as the previous, except for the event attribute selector lists.

Ollvihe at 17:37, 13 June 2024

2024-06-13T17:37:55Z

← Older revision		Revision as of 17:37, 13 June 2024
Line 3:		Line 3:
	Event type name is by default shown as the first text line in the event type box, but it can also be hidden to show customized text. Event type measures can be mapped to Label, 2nd label and 3rd label, which are shown in the next lines in the box. Flows are shown as arrows connecting the event types, and the arrow is also indicating the process flow direction. Flow measures can be mapped to Label, 2nd label and 3rd label, which are shown in separate lines in the middle of the flow. The starting and ending flows are shown as dashed lines. When an event type is hovered, its incoming (light blue) and outgoing (dark blue) flows are highlighted.		Event type name is by default shown as the first text line in the event type box, but it can also be hidden to show customized text. Event type measures can be mapped to Label, 2nd label and 3rd label, which are shown in the next lines in the box. Flows are shown as arrows connecting the event types, and the arrow is also indicating the process flow direction. Flow measures can be mapped to Label, 2nd label and 3rd label, which are shown in separate lines in the middle of the flow. The starting and ending flows are shown as dashed lines. When an event type is hovered, its incoming (light blue) and outgoing (dark blue) flows are highlighted.

	There are two kinds of flowcharts available: ''~~In-memory~~ flowchart'' and ''~~Big data~~ flowchart''. The ~~former~~ performs processing using the in-memory calculation engine (requiring to load models into memory) ~~and the latter uses Snowflake~~. Both flowcharts have similar functionality, except available event type and flow measures are different, as the ~~Big data~~ flowchart has same measures available as the [[Big_Data_Chart\|~~Big data~~ chart]]. Also in ~~Big data~~ flowchart, a filter can be set for each individual event and flow measure.		There are two kinds of flowcharts available: ''Snowflake flowchart'' and ''In-memory flowchart''. The latter performs processing using the in-memory calculation engine (requiring to load models into memory). Both flowcharts have similar functionality, except available event type and flow measures are different, as the Snowflake flowchart has same measures available as the [[Big_Data_Chart\|Snowflake chart]]. Also in Snowflake flowchart, a filter can be set for each individual event and flow measure.

	== Visibility settings ==		== Visibility settings ==
Line 53:		Line 53:
	* '''On-screen settings''': Event type and flow measure parameters can be defined as on-screen settings, similar to in [[QPR_ProcessAnalyzer_Chart#On-screen_Settings\|charts]].		* '''On-screen settings''': Event type and flow measure parameters can be defined as on-screen settings, similar to in [[QPR_ProcessAnalyzer_Chart#On-screen_Settings\|charts]].
	* '''Export''': The flowchart can be exported as png or svg image file.		* '''Export''': The flowchart can be exported as png or svg image file.
	* '''Event type mapping''': Defines the event attribute used as the event type for this flowchart, to visualize the process flow from different angles (e.g., the social mining usecase). For more information about the event type mapping, see [[QPR_ProcessAnalyzer_Chart#Analyzed_Data\|chart settings]]. This setting is available only for the ~~Big data~~ flowchart. When the mapping is used, ''Cases by Event Attribute'' and ''Events by Attribute'' type of filter rules are created when event types are selected (instead of event type filter rules), to avoid the mismatch if charts have different event type selections.		* '''Event type mapping''': Defines the event attribute used as the event type for this flowchart, to visualize the process flow from different angles (e.g., the social mining usecase). For more information about the event type mapping, see [[QPR_ProcessAnalyzer_Chart#Analyzed_Data\|chart settings]]. This setting is available only for the Snowflake flowchart. When the mapping is used, ''Cases by Event Attribute'' and ''Events by Attribute'' type of filter rules are created when event types are selected (instead of event type filter rules), to avoid the mismatch if charts have different event type selections.

	== Flowchart layout settings ==		== Flowchart layout settings ==

Ollvihe: /* Visibility setting */

2024-05-27T09:54:21Z

Visibility setting

← Older revision		Revision as of 09:54, 27 May 2024
Line 5:		Line 5:
	There are two kinds of flowcharts available: ''In-memory flowchart'' and ''Big data flowchart''. The former performs processing using the in-memory calculation engine (requiring to load models into memory) and the latter uses Snowflake. Both flowcharts have similar functionality, except available event type and flow measures are different, as the Big data flowchart has same measures available as the [[Big_Data_Chart\|Big data chart]]. Also in Big data flowchart, a filter can be set for each individual event and flow measure.		There are two kinds of flowcharts available: ''In-memory flowchart'' and ''Big data flowchart''. The former performs processing using the in-memory calculation engine (requiring to load models into memory) and the latter uses Snowflake. Both flowcharts have similar functionality, except available event type and flow measures are different, as the Big data flowchart has same measures available as the [[Big_Data_Chart\|Big data chart]]. Also in Big data flowchart, a filter can be set for each individual event and flow measure.

	== Visibility ~~setting~~ ==		== Visibility settings ==
	[[File:FlowchartAnalysis.png\|right\|550px]]		[[File:FlowchartAnalysis.png\|right\|550px]]
	Often the real-life processes are very complex, and trying to show all realized event types and flows don't provide a very illustrative presentation. This is why the flowchart shows only the most important event types and flows, which is based on the variations as follows: You will choose the number of most common variations, and only the event types and flows that appear in those most common variations are shown. Variations are a natural way to draw the flowchart, because variations represent a continuous flow of cases from start to end.		Often the real-life processes are very complex, and trying to show all realized event types and flows don't provide a very illustrative presentation. This is why the flowchart shows only the most important event types and flows, which is based on the variations as follows: You will choose the number of most common variations, and only the event types and flows that appear in those most common variations are shown. Variations are a natural way to draw the flowchart, because variations represent a continuous flow of cases from start to end.

Ollvihe: /* Visibility settings */

2024-05-27T09:53:54Z

Visibility settings

← Older revision		Revision as of 09:53, 27 May 2024
Line 5:		Line 5:
	There are two kinds of flowcharts available: ''In-memory flowchart'' and ''Big data flowchart''. The former performs processing using the in-memory calculation engine (requiring to load models into memory) and the latter uses Snowflake. Both flowcharts have similar functionality, except available event type and flow measures are different, as the Big data flowchart has same measures available as the [[Big_Data_Chart\|Big data chart]]. Also in Big data flowchart, a filter can be set for each individual event and flow measure.		There are two kinds of flowcharts available: ''In-memory flowchart'' and ''Big data flowchart''. The former performs processing using the in-memory calculation engine (requiring to load models into memory) and the latter uses Snowflake. Both flowcharts have similar functionality, except available event type and flow measures are different, as the Big data flowchart has same measures available as the [[Big_Data_Chart\|Big data chart]]. Also in Big data flowchart, a filter can be set for each individual event and flow measure.

	== Visibility ~~settings~~ ==		== Visibility setting ==
	[[File:FlowchartAnalysis.png\|right\|550px]]		[[File:FlowchartAnalysis.png\|right\|550px]]
	Often the real-life processes are very complex, and trying to show all realized event types and flows don't provide a very illustrative presentation. This is why the flowchart shows only the most important event types and flows, which is based on the variations as follows: You will choose the number of most common variations, and only the event types and flows that appear in those most common variations are shown. Variations are a natural way to draw the flowchart, because variations represent a continuous flow of cases from start to end.		Often the real-life processes are very complex, and trying to show all realized event types and flows don't provide a very illustrative presentation. This is why the flowchart shows only the most important event types and flows, which is based on the variations as follows: You will choose the number of most common variations, and only the event types and flows that appear in those most common variations are shown. Variations are a natural way to draw the flowchart, because variations represent a continuous flow of cases from start to end.