Trigger - Revision history

Frank@tygron.nl: /* TQL example: Geometry counter */

2026-04-24T08:03:37Z

TQL example: Geometry counter

← Older revision		Revision as of 08:03, 24 April 2026
Line 121:		Line 121:
	\| notes= * Because a JSON object is expected, the keys must be unique, in principle not allowing a single Trigger to call the same Event multiple times. However, adding a nonce parameter to the name of the event will work around this. For example: {"editorarea/add/nonce1":[1],"editorarea/add/nonce2":[2]} will be valid and result in the creation of a total of 3 [[Areas]].		\| notes= * Because a JSON object is expected, the keys must be unique, in principle not allowing a single Trigger to call the same Event multiple times. However, adding a nonce parameter to the name of the event will work around this. For example: {"editorarea/add/nonce1":[1],"editorarea/add/nonce2":[2]} will be valid and result in the creation of a total of 3 [[Areas]].

			}}

			{{article end
			\|api=*[[Api session items triggers]]
	}}		}}

	{{Editor tools nav}}		{{Editor tools nav}}

Maxim@tygron.com at 14:01, 10 October 2025

2025-10-10T14:01:38Z

← Older revision		Revision as of 14:01, 10 October 2025
Line 1:		Line 1:
	[[File:Api_tools_geo.png\|thumb\|right\|400px\|[[Trigger]]s in relation to [[Geo Plugin]]s]]		[[File:Api_tools_geo.png\|thumb\|right\|400px\|[[Trigger]]s in relation to [[Geo Plugin]]s]]
	~~{{stub}}~~

	Triggers can be used to execute external scripts and applications when a recalculation of grids and indicators is requested.		Triggers can be used to execute external scripts and applications when a recalculation of grids and indicators is requested.

Rudolf@tygron.nl at 07:32, 15 November 2024

2024-11-15T07:32:46Z

← Older revision		Revision as of 07:32, 15 November 2024
Line 58:		Line 58:

	==Timing==		==Timing==
	Triggers can be executed either before the grid and indicator calculations, or after in the [[Simulation Core]]. They ~~currently~~ cannot be executed between the grid and indicator calculations.		Triggers can be executed either before the grid and indicator calculations, or after in the [[Simulation Core]]. They cannot be executed between the grid and indicator calculations.

	When triggers are executed, the trigger responders are required to respond within the configured timeout time, making sure there is always an upper limit on the waiting time. By default this trigger timeout is set on 10 seconds.		When triggers are executed, the trigger responders are required to respond within the configured timeout time, making sure there is always an upper limit on the waiting time. By default this trigger timeout is set on 10 seconds.

Maxim@tygron.com: /* Timing */

2024-11-14T11:07:02Z

Timing

← Older revision		Revision as of 11:07, 14 November 2024
Line 58:		Line 58:

	==Timing==		==Timing==
	Triggers can be executed either before the grid and indicator calculations, or after. They currently cannot be executed between the grid and indicator calculations.		Triggers can be executed either before the grid and indicator calculations, or after in the [[Simulation Core]]. They currently cannot be executed between the grid and indicator calculations.

	When triggers are executed, the trigger responders are required to respond within the configured timeout time, making sure there is always an upper limit on the waiting time. By default this trigger timeout is set on 10 seconds.		When triggers are executed, the trigger responders are required to respond within the configured timeout time, making sure there is always an upper limit on the waiting time. By default this trigger timeout is set on 10 seconds.

Rudolf@tygron.nl at 10:48, 19 December 2023

2023-12-19T10:48:08Z

← Older revision		Revision as of 10:48, 19 December 2023
Line 34:		Line 34:
	==Response==		==Response==
	The web server is expected to send a response which is a parseable JSON object.		The web server is expected to send a response which is a parseable JSON object.

	~~==Timing==~~
	~~Triggers can be executed either before the grid and indicator calculations, or after. They currently cannot be executed between the grid and indicator calculations.~~
	When triggers are executed, the trigger responders are required to respond within the configured timeout time, making sure there is always an upper limit on the waiting time. By default this trigger timeout is set on 10 seconds. Grid and indicator calculations are only executed once all ''before'' triggers have either responded or timed out.

	===TQL response===		===TQL response===
Line 60:		Line 56:
	}		}
	}}		}}

			==Timing==
			Triggers can be executed either before the grid and indicator calculations, or after. They currently cannot be executed between the grid and indicator calculations.

			When triggers are executed, the trigger responders are required to respond within the configured timeout time, making sure there is always an upper limit on the waiting time. By default this trigger timeout is set on 10 seconds.

			Grid and indicator calculations are only executed once all ''before'' triggers have either responded or timed out.

	==Examples==		==Examples==

Rudolf@tygron.nl at 10:15, 4 July 2023

2023-07-04T10:15:54Z

← Older revision		Revision as of 10:15, 4 July 2023
Line 5:		Line 5:

	When a Trigger executes, it sends a web request to a specified url. The web request includes query parameters which the receiving server can use to interact with the requesting session.		When a Trigger executes, it sends a web request to a specified url. The web request includes query parameters which the receiving server can use to interact with the requesting session.
			{{clear}}

	==Request==		==Request==

Frank@tygron.nl at 14:06, 21 February 2023

2023-02-21T14:06:39Z

← Older revision		Revision as of 14:06, 21 February 2023
Line 1:		Line 1:
			[[File:Api_tools_geo.png\|thumb\|right\|400px\|[[Trigger]]s in relation to [[Geo Plugin]]s]]
	{{stub}}		{{stub}}

Rudolf@tygron.nl: Typo

2022-08-10T08:38:06Z

Typo

← Older revision		Revision as of 08:38, 10 August 2022
Line 97:		Line 97:
	$globalName = strtoupper($key).'_COUNTED';		$globalName = strtoupper($key).'_COUNTED';
	//...and use that to create the TQL update statement.		//...and use that to create the TQL update statement.
	$queries[ 'UPDATE_GLOBAL_VALUE_WHERE_NAME_IS_' . $globalName ] = $amountOfFeatures . '.0' ;//The Tygron Platform expects results with a ~~decial~~ notation.		$queries[ 'UPDATE_GLOBAL_VALUE_WHERE_NAME_IS_' . $globalName ] = $amountOfFeatures . '.0' ;//The Tygron Platform expects results with a decimal notation.
	}		}

Rudolf@tygron.nl at 13:11, 1 August 2022

2022-08-01T13:11:03Z

← Older revision		Revision as of 13:11, 1 August 2022
Line 115:		Line 115:

	{{article end		{{article end
	\| notes= * Because a JSON object is expected, the keys must be unique, in principle not allowing a single Trigger to call the same Event multiple times. However, adding a ~~query~~ parameter to the name of the event will work around this. For example: {"editorarea/add/nonce1":[1],"editorarea/add/nonce2":[2]} will be valid and result in the creation of a total of 3 [[Areas]].		\| notes= * Because a JSON object is expected, the keys must be unique, in principle not allowing a single Trigger to call the same Event multiple times. However, adding a nonce parameter to the name of the event will work around this. For example: {"editorarea/add/nonce1":[1],"editorarea/add/nonce2":[2]} will be valid and result in the creation of a total of 3 [[Areas]].

	}}		}}

	{{Editor tools nav}}		{{Editor tools nav}}

Rudolf@tygron.nl: /* Examples */

2022-07-29T08:29:50Z

Examples

← Older revision		Revision as of 08:29, 29 July 2022
Line 115:		Line 115:

	{{article end		{{article end
	\| notes= * Because a JSON object is expected, the keys must be unique, in principle not allowing a single Trigger to call the same Event multiple times. However, adding a query parameter to the name of the event will work around this. For example: {"editorarea/add~~?nonce=1~~":[1],"editorarea/add~~?nonce=2~~":[2]} will be valid and result in the creation of a total of 3 [[Areas]].		\| notes= * Because a JSON object is expected, the keys must be unique, in principle not allowing a single Trigger to call the same Event multiple times. However, adding a query parameter to the name of the event will work around this. For example: {"editorarea/add/nonce1":[1],"editorarea/add/nonce2":[2]} will be valid and result in the creation of a total of 3 [[Areas]].

	}}		}}

	{{Editor tools nav}}		{{Editor tools nav}}