QPR ProcessAnalyzer Expressions - Revision history

Ollvihe: /* Full and limited modes */

2026-03-19T09:53:43Z

Full and limited modes

← Older revision		Revision as of 09:53, 19 March 2026
Line 844:		Line 844:
	* ImportOdbc()		* ImportOdbc()
	* ImportOdbcSecure()		* ImportOdbcSecure()
			* Model.CreateDiagram()
			* Model.CreateFilter()
	* Model.DeletePermanently()		* Model.DeletePermanently()
			* Model.ResetModelCache()
			* Model.ResetPreprocessings()
			* Model.Modify()
	* Model.Restore()		* Model.Restore()
	* Model.TriggerNotifications()		* Model.TriggerNotifications()
			* Project.CreateDashboard()
			* Project.CreateDatatable()
			* Project.CreateModel()
			* Project.CreateProject()
	* Project.DeletePermanently()		* Project.DeletePermanently()
			* Project.Import()
			* Project.Modify()
	* Project.Restore()		* Project.Restore()
	* Project.~~CreateDatatable~~()		* Project.SetSecret()
	* Datatable.AddColumn()		* Datatable.AddColumn()
			* Datatable.AddColumns()
	* Datatable.DeletePermanently()		* Datatable.DeletePermanently()
			* Datatable.DeleteRows()
	* Datatable.Import()		* Datatable.Import()
	* Datatable.Merge()		* Datatable.Merge()
			* Datatable.Modify()
	* Datatable.RemoveColumns()		* Datatable.RemoveColumns()
	* Datatable.RenameColumns()		* Datatable.RenameColumns()
			* Datatable.SetForeignKeys()
			* Datatable.SetPrimaryKey()
			* Datatable.Synchronize()
	* Datatable.Truncate()		* Datatable.Truncate()
			* Datatable.UpdateRows()
	* RecycleBin.DeletePermanently()		* RecycleBin.DeletePermanently()
	* Call SQL script		* Call SQL script

Ollvihe: /* Full and limited modes */

2026-03-19T09:47:49Z

Full and limited modes

← Older revision		Revision as of 09:47, 19 March 2026
Line 832:		Line 832:

	== Full and limited modes ==		== Full and limited modes ==
	~~The~~ expression language can run in two modes: the ''full'' and ''limited'' mode. In the full mode, all functionality is available, while in the limited mode, operations that modify data or connect to external datasources are prevented.		To improve security, the expression language can run in two modes: the ''full'' and ''limited'' mode. In the full mode, all functionality is available, while in the limited mode, operations that modify data or connect to external datasources are prevented.

	Different modes are used as follows:		Different modes are used as follows:

Ollvihe: /* Full and limited modes */

2026-03-19T09:47:15Z

Full and limited modes

← Older revision		Revision as of 09:47, 19 March 2026
Line 832:		Line 832:

	== Full and limited modes ==		== Full and limited modes ==
	The expression language can run in two modes: the ''full'' and ''limited'' mode. In the full mode, all functionality is available, while in the limited mode, operations that modify data or connect to external datasources are prevented. In ~~dashboards~~, the limited mode is in use ~~for security reasons~~, ~~and in~~ scripts the full mode is ~~available~~. The following operations are prevented in the limited mode:		The expression language can run in two modes: the ''full'' and ''limited'' mode. In the full mode, all functionality is available, while in the limited mode, operations that modify data or connect to external datasources are prevented.

			Different modes are used as follows:
			* In dashboard custom expressions, the limited mode is in use (to prevent opening dashboards from modifying data).
			* In scripts, the full mode is used.
			* When scripts are called from [[QPR_ProcessAnalyzer_Table#Table_actions\|table actions]] or [[Label_and_Link#Run_script_action\|label actions]], the full mode is used.

			The following operations are prevented in the limited mode:
	* SendEmail()		* SendEmail()
	* CallWebService()		* CallWebService()
Line 853:		Line 860:
	* Call SQL script		* Call SQL script

	~~Calling expression scripts~~ is allowed, but in the ~~script all previously mentioned operations are prevented~~.		When a script is called in the limited mode, the calling is allowed, but the script will run in the limited mode.

	== In-memory expression blocks in SQL expressions ==		== In-memory expression blocks in SQL expressions ==

Ollvihe: /* Operators */

2025-12-04T09:32:05Z

Operators

← Older revision		Revision as of 09:32, 4 December 2025
Line 121:		Line 121:
	Following arithmetic and logical operations are available:		Following arithmetic and logical operations are available:
	* '''Addition (+)''' can be performed on numeric types, strings (concatenate two strings) and [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#TimeSpan\|Timespans]] (addition of two TimeSpans).		* '''Addition (+)''' can be performed on numeric types, strings (concatenate two strings) and [[QPR_ProcessAnalyzer_Objects_in_Expression_Language#TimeSpan\|Timespans]] (addition of two TimeSpans).
	* '''Subtraction (-)''' can be performed on numeric types, [[~~QPR_ProcessAnalyzer_Objects_in_Expression_Language~~#DateTime\|DateTimes]] (calculating TimeSpan between two DateTimes) and TimeSpans (difference between two TimeSpans).		* '''Subtraction (-)''' can be performed on numeric types, [[Generic_Objects_in_Expression_Language#DateTime\|DateTimes]] (calculating TimeSpan between two DateTimes) and TimeSpans (difference between two TimeSpans).
	* '''Multiplication (*)''' can be performed on numeric types, and between a TimeSpan and a numeric type (multiplying TimeSpan by number which results in TimeSpan),		* '''Multiplication (*)''' can be performed on numeric types, and between a TimeSpan and a numeric type (multiplying TimeSpan by number which results in TimeSpan),
	* '''Division (/)''' can be performed on numeric types, between a TimeSpan and a numeric type (dividing a TimeSpan where TimeSpan must be the left hand side operand).		* '''Division (/)''' can be performed on numeric types, between a TimeSpan and a numeric type (dividing a TimeSpan where TimeSpan must be the left hand side operand).

Ollvihe: /* Introduction to Expressions */

2024-07-07T17:35:09Z

Introduction to Expressions

← Older revision		Revision as of 17:35, 7 July 2024
Line 31:		Line 31:
	* Each object has an own context in which object's '''functions''' and '''properties''' can be used.		* Each object has an own context in which object's '''functions''' and '''properties''' can be used.
	* There is also the [[Generic_Objects_in_Expression_Language#Generic_Context\|generic context]] which is used when the function or property is not found in the object specific context.		* There is also the [[Generic_Objects_in_Expression_Language#Generic_Context\|generic context]] which is used when the function or property is not found in the object specific context.
			* If there is both a variable and a property with the same name in the same scope, the variable has the precedence, i.e., an identifier refers to the variable, not the property.

	== Chaining Expressions ==		== Chaining Expressions ==

Ollvihe: /* Expression Language Overview */

2024-06-13T17:48:31Z

Expression Language Overview

← Older revision		Revision as of 17:48, 13 June 2024
Line 18:		Line 18:
	In the dashboards, there are two chart types available:		In the dashboards, there are two chart types available:
	* '''Snowflake chart''' creates a '''Snowflake query''' to fetch the data. The in-memory query uses the ''SqlDataFrame'' to perform calculations.		* '''Snowflake chart''' creates a '''Snowflake query''' to fetch the data. The in-memory query uses the ''SqlDataFrame'' to perform calculations.
	* '''In-memory chart''' creates a '''in-memory ~~queries~~''' to fetch the data. The in-memory query uses the ''In-memory model API'' to perform calculations. Thus, all the features and limitation of the In-memory model API affect the in-memory chart.		* '''In-memory chart''' creates an '''in-memory query''' to fetch the data. The in-memory query uses the ''In-memory model API'' to perform calculations. Thus, all the features and limitation of the In-memory model API affect the in-memory chart.

	Expression language is run by QPR ProcessAnalyzer Server, and the expressions are used by dashboards and scripts.		Expression language is run by QPR ProcessAnalyzer Server, and the expressions are used by dashboards and scripts.

Ollvihe: /* Expression Language Overview */

2024-06-13T17:48:06Z

Expression Language Overview

← Older revision		Revision as of 17:48, 13 June 2024
Line 17:		Line 17:

	In the dashboards, there are two chart types available:		In the dashboards, there are two chart types available:
			* '''Snowflake chart''' creates a '''Snowflake query''' to fetch the data. The in-memory query uses the ''SqlDataFrame'' to perform calculations.
	* '''In-memory chart''' creates a '''in-memory queries''' to fetch the data. The in-memory query uses the ''In-memory model API'' to perform calculations. Thus, all the features and limitation of the In-memory model API affect the in-memory chart.		* '''In-memory chart''' creates a '''in-memory queries''' to fetch the data. The in-memory query uses the ''In-memory model API'' to perform calculations. Thus, all the features and limitation of the In-memory model API affect the in-memory chart.
	* '''Big data chart''' creates a '''Snowflake query''' to fetch the data. The in-memory query uses the ''SqlDataFrame'' to perform calculations.

	Expression language is run by QPR ProcessAnalyzer Server, and the expressions are used by dashboards and scripts.		Expression language is run by QPR ProcessAnalyzer Server, and the expressions are used by dashboards and scripts.

Ollvihe: /* Throwing objects */

2023-08-16T20:38:42Z

Throwing objects

← Older revision		Revision as of 20:38, 16 August 2023
Line 646:		Line 646:

	== Throwing objects ==		== Throwing objects ==
	Objects can be "thrown" using the '''throw''' statement. For example, strings can be thrown, but the thrown object can also be a more complex dictionary containing additional data. Note that there is no separate exception entity that can be thrown.		Objects can be thrown using the '''throw''' statement. For example, strings can be thrown, but the thrown object can also be a more complex dictionary containing additional data. Note that there is no separate exception entity that can be thrown.

	Following example throws a string that can contain a message why the processing was stopped:		Following example throws a string that can contain a message why the processing was stopped:
Line 653:		Line 653:
	</pre>		</pre>

	The thrown object can be caught using the '''try-catch''' statement. The caught entity is an exception object that has the thrown object as parameter '''thrownObject'''.		The thrown object can be caught using the '''try-catch''' statement. The caught entity is an exception object that has the thrown object in parameter '''thrownObject'''.

	Example:		Example:

Ollvihe: /* Throwing objects */

2023-08-16T20:36:13Z

Throwing objects

← Older revision		Revision as of 20:36, 16 August 2023
Line 646:		Line 646:

	== Throwing objects ==		== Throwing objects ==
	~~Any objects~~ can be "thrown" using the '''throw''' statement. ~~Simply~~ strings can be thrown, but the thrown object can also be a more complex dictionary ~~delivering~~ additional data. Note that there is no separate exception entity that can be thrown.		Objects can be "thrown" using the '''throw''' statement. For example, strings can be thrown, but the thrown object can also be a more complex dictionary containing additional data. Note that there is no separate exception entity that can be thrown.

	Following example throws a string (that can ~~be used to deliver~~ a message why the processing was stopped):		Following example throws a string that can contain a message why the processing was stopped:
	<pre>		<pre>
	throw "Error occurred etc.";		throw "Error occurred etc.";
	</pre>		</pre>

	The thrown object can be caught using the '''try-catch''' statement. Example:		The thrown object can be caught using the '''try-catch''' statement. The caught entity is an exception object that has the thrown object as parameter '''thrownObject'''.

			Example:
	<pre>		<pre>
	try {		try {
	throw "Error occurred etc.";		throw "Error occurred etc.";
	} catch (~~error~~) {		} catch (exception) {
	WriteLog(~~error~~);		WriteLog(exception.thrownObject);
	}		}
	</pre>		</pre>

Ollvihe: /* Throwing exceptions */

2023-07-25T22:16:08Z

Throwing exceptions

← Older revision		Revision as of 22:16, 25 July 2023
Line 645:		Line 645:
	</pre>		</pre>

	== Throwing ~~exceptions~~ ==		== Throwing objects ==
	Any objects can be thrown using the throw statement. ~~Example~~:		Any objects can be "thrown" using the '''throw''' statement. Simply strings can be thrown, but the thrown object can also be a more complex dictionary delivering additional data. Note that there is no separate exception entity that can be thrown.

			Following example throws a string (that can be used to deliver a message why the processing was stopped):
	<pre>		<pre>
	throw "Error occurred etc.";		throw "Error occurred etc.";
	</pre>		</pre>

	The thrown object can be caught using the '''try-catch''' statement.		The thrown object can be caught using the '''try-catch''' statement. Example:
			<pre>
			try {
			throw "Error occurred etc.";
			} catch (error) {
			WriteLog(error);
			}
			</pre>

	== Defining functions ==		== Defining functions ==