Calculated Attributes in QPR ProcessAnalyzer - Revision history

Ollvihe: /* Functioning principle and use cases */

2023-04-18T22:20:03Z

Functioning principle and use cases

← Older revision		Revision as of 22:20, 18 April 2023
Line 11:		Line 11:

	Calculated attributes work as follows:		Calculated attributes work as follows:
	* After the model is loaded, the calculated and imported attributes work similarly, e.g. both are available in the profiling and ~~influence~~ analyses.		* After the model is loaded, the calculated and imported attributes work similarly, e.g. both are available in the profiling and root causes analyses.
	* Calculated attributes are calculated when the model is loaded, and thus calculated attribute values don't change after the model loading during the time the model is in the memory. If attributes need to be calculated again, the model needs to be reloaded.		* Calculated attributes are calculated when the model is loaded, and thus calculated attribute values don't change after the model loading during the time the model is in the memory. If attributes need to be calculated again, the model needs to be reloaded.
	* Calculated attribute values are stored into the memory like the imported attributes, meaning the model requires more memory, the more there are calculated attributes.		* Calculated attribute values are stored into the memory like the imported attributes, meaning the model requires more memory, the more there are calculated attributes.

Ollvihe at 17:22, 10 March 2021

2021-03-10T17:22:30Z

← Older revision		Revision as of 17:22, 10 March 2021
Line 1:		Line 1:
	Calculated attributes enable to create case and event attributes using a expressions (calculation formula) based on data in the QPR ProcessAnalyzer model. Calculated attributes can be modified and Model attributes dialog that can be opened in the models list in the header. Note that when calculated attributes are changed, the model is dropped from the memory, so that the changed attributes can be recalculated (reloading large models might take time).		Calculated attributes enable to create case and event attributes using a expressions (calculation formula) based on data in the QPR ProcessAnalyzer model. Calculated attributes can be modified and Model attributes dialog that can be opened in the models list in the header. Note that when calculated attributes are changed, the model is dropped from the memory, so that the changed attributes can be recalculated (reloading large models might take time).

	~~Data to '''case attributes''' and '''event attributes''' can be originated as follows:~~
	* '''Import''' them into QPR ProcessAnalyzer from a source system, csv file etc.
	* '''Calculate''' attribute values when the model is loaded using an [[QPR ProcessAnalyzer Expressions\|expression]].

	== Setting calculated attributes ==		== Setting calculated attributes ==
Line 9:		Line 5:

	== Functioning principle and use cases ==		== Functioning principle and use cases ==

			Data to case attributes and event attributes can be originated as follows:
			* '''Import''' them into QPR ProcessAnalyzer from a source system, csv file etc.
			* '''Calculate''' attribute values when the model is loaded using an [[QPR ProcessAnalyzer Expressions\|expression]].

	Calculated attributes work as follows:		Calculated attributes work as follows:
	* After the model is loaded, the calculated and imported attributes work similarly, e.g. both are available in the profiling and influence analyses.		* After the model is loaded, the calculated and imported attributes work similarly, e.g. both are available in the profiling and influence analyses.

Ollvihe at 17:21, 10 March 2021

2021-03-10T17:21:49Z

← Older revision		Revision as of 17:21, 10 March 2021
Line 1:		Line 1:
	Calculated attributes enable to create case and event attributes using a expressions (calculation formula) based on data in the QPR ProcessAnalyzer model. Calculated attributes can be modified and Model ~~properties~~ dialog.		Calculated attributes enable to create case and event attributes using a expressions (calculation formula) based on data in the QPR ProcessAnalyzer model. Calculated attributes can be modified and Model attributes dialog that can be opened in the models list in the header. Note that when calculated attributes are changed, the model is dropped from the memory, so that the changed attributes can be recalculated (reloading large models might take time).

	~~== Configuration ==~~
	Calculated case and event attributes are set for each model separately in the '''Model attributes''' dialog that can be opened in the models list in the header. The dialog has '''Case attributes''' and '''Event attributes''' tabs, where each contain an ordered list of case/event attributes. Each attribute has a name, and in addition it should be defined how the attribute value is calculated. There is a list of ready made selections (same as the dimensions list in the [[QPR_ProcessAnalyzer_Chart#Measures.2C_Dimensions_and_Columns\|chart settings]], and additionally a custom expression can be written for the calculated attribute. It's possible to convert a ready-made selection into a custom expression by selecting '''Custom expression''' from the list, e.g. to modify the ready-made selection.

	~~== Introduction and Use Cases==~~
	Data to '''case attributes''' and '''event attributes''' can be originated as follows:		Data to '''case attributes''' and '''event attributes''' can be originated as follows:
	* '''Import''' them into QPR ProcessAnalyzer from a source system, csv file etc.		* '''Import''' them into QPR ProcessAnalyzer from a source system, csv file etc.
	* '''Calculate''' attribute values when the model is loaded using an [[QPR ProcessAnalyzer Expressions\|expression]].		* '''Calculate''' attribute values when the model is loaded using an [[QPR ProcessAnalyzer Expressions\|expression]].

	Calculated attributes ~~have following use cases:~~		== Setting calculated attributes ==
	* Conversions: If an ~~imported~~ attribute ~~data is not in~~ a ~~suitable format~~, the ~~data can be overridden by defining~~ a ~~calculated attribute with~~ the ~~same name~~. ~~The calculated attribute~~ expression ~~performs conversions~~ for the ~~data~~.		Calculated case and event attributes are set for each model separately in the '''Model attributes''' dialog that can be opened in the models list in the header. The dialog has '''Case attributes''' and '''Event attributes''' tabs, where each contain an ordered list of case/event attributes. Each attribute has a name, and in addition it should be defined how the attribute value is calculated. There is a list of ready made selections (same as the dimensions list in the [[QPR_ProcessAnalyzer_Chart#Measures.2C_Dimensions_and_Columns\|chart settings]], and additionally a custom expression can be written for the calculated attribute. It's possible to convert a ready-made selection into a custom expression by selecting '''Custom expression''' from the list, e.g. to modify the ready-made selection.
	* Aggregations: It's possible to ~~aggregate~~ e.g. ~~event level information to case level using a calculated case attribute.~~
	* Performance: If there is an expression to aggregate event level information to ~~a case level, the aggregation can be done already in~~ the ~~model loading using a calculated case attribute for better performance~~.

	== Functioning ~~Principle~~ ==		== Functioning principle and use cases ==
	Calculated attributes work as follows:		Calculated attributes work as follows:
	* After the model is loaded, the calculated and imported attributes work similarly, e.g. both are available in the profiling and influence analyses.		* After the model is loaded, the calculated and imported attributes work similarly, e.g. both are available in the profiling and influence analyses.
Line 25:		Line 19:

	Calculated case and event attributes are configured in the Model properties in the '''Calculated case attributes''' and '''Calculated event attributes''' tabs. The new attributes can be created, existing modified, reordered and deleted. Each attribute has '''Name''' and '''Calculation expression'''. The expression is calculated in the case's or event's context.		Calculated case and event attributes are configured in the Model properties in the '''Calculated case attributes''' and '''Calculated event attributes''' tabs. The new attributes can be created, existing modified, reordered and deleted. Each attribute has '''Name''' and '''Calculation expression'''. The expression is calculated in the case's or event's context.

			Calculated attributes have following use cases:
			* Conversions: If an imported attribute data is not in a suitable format, the data can be overridden by defining a calculated attribute with the same name. The calculated attribute expression performs conversions for the data.
			* Aggregations: It's possible to aggregate e.g. event level information to case level using a calculated case attribute.
			* Performance: If there is an expression to aggregate event level information to a case level, the aggregation can be done already in the model loading using a calculated case attribute for better performance.

	== Examples of calculated case attributes ==		== Examples of calculated case attributes ==

Ollvihe at 23:14, 26 January 2021

2021-01-26T23:14:50Z

← Older revision		Revision as of 23:14, 26 January 2021
Line 2:		Line 2:

	== Configuration ==		== Configuration ==
	Calculated case and event attributes are set for each model separately in the '''Model attributes''' dialog that can be opened in the models list in the header. The dialog has '''Case attributes''' and '''Event attributes''' tabs, where each contain an ordered list of case/event attributes. Each attribute has a name, and in addition it should be defined how the attribute value is calculated. There is a list of ready made selections (same as the dimensions list in the [[QPR_ProcessAnalyzer_Chart#Measures.2C_Dimensions_and_Columns\|chart settings]], and additionally a custom expression can be written for the calculated attribute. It's possible to convert a ready-made selection into a custom expression by selecting '''Custom expression''' from the list, e.g. ~~for modifying~~ the ready-made selection.		Calculated case and event attributes are set for each model separately in the '''Model attributes''' dialog that can be opened in the models list in the header. The dialog has '''Case attributes''' and '''Event attributes''' tabs, where each contain an ordered list of case/event attributes. Each attribute has a name, and in addition it should be defined how the attribute value is calculated. There is a list of ready made selections (same as the dimensions list in the [[QPR_ProcessAnalyzer_Chart#Measures.2C_Dimensions_and_Columns\|chart settings]], and additionally a custom expression can be written for the calculated attribute. It's possible to convert a ready-made selection into a custom expression by selecting '''Custom expression''' from the list, e.g. to modify the ready-made selection.

	== Introduction and Use Cases==		== Introduction and Use Cases==

Ollvihe at 23:14, 26 January 2021

2021-01-26T23:14:30Z

← Older revision		Revision as of 23:14, 26 January 2021
Line 2:		Line 2:

	== Configuration ==		== Configuration ==
	Calculated case and event attributes are set in the '''Model attributes'' dialog that can be opened in the models list. The dialog has '''Case attributes''' and '''Event attributes''' tabs, where each contain an ordered list of case/event attributes. Each attribute ~~needs to have~~ a name and in addition it should be defined how the attribute value is calculated. There is a list of ready made selections (same as the dimensions list in the [[QPR_ProcessAnalyzer_Chart#Measures.2C_Dimensions_and_Columns\|chart settings]], and additionally a custom expression can be written for the calculated attribute.		Calculated case and event attributes are set for each model separately in the '''Model attributes''' dialog that can be opened in the models list in the header. The dialog has '''Case attributes''' and '''Event attributes''' tabs, where each contain an ordered list of case/event attributes. Each attribute has a name, and in addition it should be defined how the attribute value is calculated. There is a list of ready made selections (same as the dimensions list in the [[QPR_ProcessAnalyzer_Chart#Measures.2C_Dimensions_and_Columns\|chart settings]], and additionally a custom expression can be written for the calculated attribute. It's possible to convert a ready-made selection into a custom expression by selecting '''Custom expression''' from the list, e.g. for modifying the ready-made selection.

	== Introduction and Use Cases==		== Introduction and Use Cases==

Ollvihe at 23:11, 26 January 2021

2021-01-26T23:11:55Z

← Older revision		Revision as of 23:11, 26 January 2021
Line 1:		Line 1:
	Calculated attributes enable to create case and event attributes using ~~an expression~~ (calculation formula) based on data in the QPR ProcessAnalyzer model. Calculated attributes can be modified and Model properties dialog.		Calculated attributes enable to create case and event attributes using a expressions (calculation formula) based on data in the QPR ProcessAnalyzer model. Calculated attributes can be modified and Model properties dialog.

	== Introduction and ~~Usecases~~==		== Configuration ==
			Calculated case and event attributes are set in the '''Model attributes'' dialog that can be opened in the models list. The dialog has '''Case attributes''' and '''Event attributes''' tabs, where each contain an ordered list of case/event attributes. Each attribute needs to have a name and in addition it should be defined how the attribute value is calculated. There is a list of ready made selections (same as the dimensions list in the [[QPR_ProcessAnalyzer_Chart#Measures.2C_Dimensions_and_Columns\|chart settings]], and additionally a custom expression can be written for the calculated attribute.

			== Introduction and Use Cases==
	Data to '''case attributes''' and '''event attributes''' can be originated as follows:		Data to '''case attributes''' and '''event attributes''' can be originated as follows:
	* '''Import''' them into QPR ProcessAnalyzer from a source system, csv file etc.		* '''Import''' them into QPR ProcessAnalyzer from a source system, csv file etc.

Ollvihe: /* Functioning Principle */

2020-10-01T17:21:34Z

Functioning Principle

← Older revision		Revision as of 17:21, 1 October 2020
Line 21:		Line 21:
	* If there is an error in the calculated attribute expression, the model loading fails, and the error needs to be corrected before the model can be used.		* If there is an error in the calculated attribute expression, the model loading fails, and the error needs to be corrected before the model can be used.

	Calculated case and event attributes are configured in the Model properties in the '''Calculated case attributes and '''Calculated event attributes''' tabs. The new attributes can be created, existing modified, reordered and deleted. Each attribute has '''Name''' and '''Calculation expression'''. The expression is calculated in the case's or event's context.		Calculated case and event attributes are configured in the Model properties in the '''Calculated case attributes''' and '''Calculated event attributes''' tabs. The new attributes can be created, existing modified, reordered and deleted. Each attribute has '''Name''' and '''Calculation expression'''. The expression is calculated in the case's or event's context.

	== Examples of calculated case attributes ==		== Examples of calculated case attributes ==

Ollvihe at 17:21, 1 October 2020

2020-10-01T17:21:17Z

← Older revision		Revision as of 17:21, 1 October 2020
Line 21:		Line 21:
	* If there is an error in the calculated attribute expression, the model loading fails, and the error needs to be corrected before the model can be used.		* If there is an error in the calculated attribute expression, the model loading fails, and the error needs to be corrected before the model can be used.

	Calculated case and event attributes are configured to the ~~model JSON settings are follows:~~		Calculated case and event attributes are configured in the Model properties in the '''Calculated case attributes and '''Calculated event attributes''' tabs. The new attributes can be created, existing modified, reordered and deleted. Each attribute has '''Name''' and '''Calculation expression'''. The expression is calculated in the case's or event's context.
	~~{\| class="wikitable"~~
	!'''~~Property~~'''
	! '''~~Description'''~~
	\|-
	\|\|
	~~CaseAttributes~~
	\|\|
	~~Array of calculated case~~ attributes ~~with the following properties:~~
	* '''~~name~~'''~~: Calculated attribute name. There are no restrictions for the attribute names, but avoid names starting or ending with spaces to avoid confusion.~~
	*'''expression'''~~: Expression to calculate the calculated attribute~~. The expression is calculated in the case's or event's context. ~~Only when an expression has been defined, the attribute is a calculated attribute.~~
	\|-
	\|\|
	~~EventAttributes~~
	\|\|
	~~Calculated event attributes are defined using the same structure as calculated case attributes.~~
	\|}

	== Examples ==		== Examples of calculated case attributes ==
	~~Example~~ of calculated case attributes:

	Cost:		Cost:
Line 76:		Line 59:
	</pre>		</pre>

	Example of calculated event attributes:		== Example of calculated event attributes ==

	Event Month:		Event Month:

Ollvihe: /* Examples */

2020-10-01T17:18:48Z

Examples

← Older revision		Revision as of 17:18, 1 October 2020
Line 41:		Line 41:
	== Examples ==		== Examples ==
	Example of calculated case attributes:		Example of calculated case attributes:
	* Cost: <pre>Cost * 1.5</pre>
	* myBooleanAttribute1: <pre>CURRENCYCODE == "RUB"</pre>		Cost:
	* Combined status: <pre>PurchaseStatus + " " + PurchaseType</pre>		<pre>Cost * 1.5</pre>
	* Repeated Events Count: <pre>Count(_.Events) - Count(Distinct(_.Events.Type))</pre>
	* Automation of first Shipment Sent: <pre>If(Count(_.EventsByType("Shipment Sent"))==0, null, (_.EventsByType("Shipment Sent").Attribute("Automation"))[0])</pre>		myBooleanAttribute1:
	* Duration between "Invoice Sent" and "Payment Received":		<pre>CURRENCYCODE == "RUB"</pre>

			Combined status:
			<pre>PurchaseStatus + " " + PurchaseType</pre>

			Repeated Events Count:
			<pre>Count(_.Events) - Count(Distinct(_.Events.Type))</pre>

			Automation of first Shipment Sent:
			<pre>If(Count(_.EventsByType("Shipment Sent"))==0, null, (_.EventsByType("Shipment Sent").Attribute("Automation"))[0])</pre>

			Duration between "Invoice Sent" and "Payment Received":
	<pre>		<pre>
	If(Count(_.EventsByType("Invoice Sent")) == 0 \|\| Count(_.EventsByType("Purchase Order Line Created")) == 0,		If(Count(_.EventsByType("Invoice Sent")) == 0 \|\| Count(_.EventsByType("Purchase Order Line Created")) == 0,
Line 53:		Line 64:
	)		)
	</pre>		</pre>
	* KPI_SegregationOfDuties:
			KPI_SegregationOfDuties:
	<pre>		<pre>
	Count(		Count(
Line 65:		Line 77:

	Example of calculated event attributes:		Example of calculated event attributes:
	* Event Month: <pre>Timestamp.Truncate("month")</pre>
	* Duration to Next Event: <pre>If(IsNull(_.NextInCase), null, (_.NextInCase.Timestamp-_.Timestamp))</pre>		Event Month:
	* Event type occurrence number: <pre>let eventTypeName = _.Typename;Count(_.Recurse(_.PreviousInCase).Where(_.Typename==eventTypeName))</pre>		<pre>Timestamp.Truncate("month")</pre>

			Duration to Next Event:
			<pre>If(IsNull(_.NextInCase), null, (_.NextInCase.Timestamp-_.Timestamp))</pre>

			Event type occurrence number:
			<pre>let eventTypeName = _.Typename;Count(_.Recurse(_.PreviousInCase).Where(_.Typename==eventTypeName))</pre>

	[[Category: QPR ProcessAnalyzer]]		[[Category: QPR ProcessAnalyzer]]

Ollvihe: /* Examples */

2020-10-01T17:17:48Z

Examples

← Older revision		Revision as of 17:17, 1 October 2020
Line 46:		Line 46:
	* Repeated Events Count: <pre>Count(_.Events) - Count(Distinct(_.Events.Type))</pre>		* Repeated Events Count: <pre>Count(_.Events) - Count(Distinct(_.Events.Type))</pre>
	* Automation of first Shipment Sent: <pre>If(Count(_.EventsByType("Shipment Sent"))==0, null, (_.EventsByType("Shipment Sent").Attribute("Automation"))[0])</pre>		* Automation of first Shipment Sent: <pre>If(Count(_.EventsByType("Shipment Sent"))==0, null, (_.EventsByType("Shipment Sent").Attribute("Automation"))[0])</pre>
	* Duration between "Invoice Sent" and "Payment Received": <pre>If(Count(_.EventsByType("Invoice Sent")) == 0 \|\| Count(_.EventsByType("Purchase Order Line Created")) == 0, null, (GetAtReverse(0,_.EventsByType(["Invoice Sent", "Payment Received"])).Timestamp-GetAt(0,_.EventsByType(["Invoice Sent", "Payment Received"])).Timestamp))</pre>		* Duration between "Invoice Sent" and "Payment Received":
			<pre>
			If(Count(_.EventsByType("Invoice Sent")) == 0 \|\| Count(_.EventsByType("Purchase Order Line Created")) == 0,
			null,
			GetAtReverse(0, _.EventsByType(["Invoice Sent", "Payment Received"])).Timestamp - GetAt(0, _.EventsByType(["Invoice Sent", "Payment Received"])).Timestamp
			)
			</pre>
	* KPI_SegregationOfDuties:		* KPI_SegregationOfDuties:
	<pre>		<pre>