Data extension ExtEvent - configuration window

Description:

Data extension configuration ExtEvent - Data extension for generating events

Configurators:

Data extension identifier	System text (without spaces and diacritics - i.e. national dependent characters). It is used for unambiguous identification of data extension in data item (e.g. in the Extension method). The default value is "ev".
Target object (PmaEventGroup)	Path to the target object of appropriate type, in which the data variable must be registered. The object can be selected also by the button on the right. Macro expression can be used for input, the result must be a NON-LOCALIZED path to Pma object (it is evaluated after the application is launched).
Event template	The unique text identifier of the alarm of Template type (see the "Template for dynamically created items" configurator), whose configuration is used.
Automatically generated event identifier	If checked, then the alarm identifier will be created automatically by the system (_autoN).
Event identifier	Manually entered alarm identifier. This configurator sets the initial value of the PmAlarmItem.Id property. Macro expression can be used for input (it is evaluated after the application is launched). Caution: Macro expression $vb cannot be used for input.
Event source (source)	The text specifies the logical placement of the alarm in the technology. It has the same meaning as the "Source" configurator for standalone configured alarms/events. Macro expression can be used for input (it is evaluated after the application is launched). Caution: Macro expression $vb cannot be used for input.
Event description defined here (otherwise from template)	If checked, then the event description can be specified in the following configurator. Otherwise the template event description is used.
Event description (desc)	Macro expression can be used for input ($.text ..) (it is evaluated when calling a method). Caution: Macro expression $vb cannot be used for input.
Value type	Method for obtaining value for evaluation (testing): 0 - whole value - The whole value is used. Non-zero value means true and zero value means false. 1 - defined bit - Value of specified bit is used. Non-zero value means true and zero value means false. 3 - JavaScript expression - Value defined by JavaScript expression is used. Non-zero value means true and zero value means false.
Specifies the bit number to test	If set "3 - JavaScript expression", then serves for specifying the particular bit index. The particular bit is identified by the order, so the lowest bit is numbered 0.
JavaScript expression	If set "3 - JavaScript expression", then it serves for specifying of the JavaScript expression itself. The JavaScript expression can have two parameters: pVal: The value of the PmVar.Value property for simple usage in the expression. pDE: Reference to data extension object (for obtaining other values from data extension or from variable). pVar: Reference to the PmVar object of data extension.
Activate the event if	Specifies when is the event activated. On each writing - The event will be activated with each writing into the variable (whole value or defined bit). On each modification - The event will be activated if writing into into the variable (whole value or defined bit) changes it. On each change to true - The event will be activated if after writing into the variable (whole value or defined bit) the value is changed to true (non-zero value). On each change to false - The event will be activated if after writing into the variable (whole value or defined bit) the value is changed to false (zero value).

Note:

This configuration window can be opened from the "Data extensions" configurator in the variable of the PmaData object.

Caution! In order to create user defined event description (desc) can be used Macro expression, that is evaluated with EVERY activation of such event. Macro expression $.expr allows to access the script interface of data extension via the pDE variable. The pVar property returns the PmVar object. This allows to create an event description that may be different with each activation and may even contain a name, current value of the variable, etc. (pVar.Name, pVar.Value). See examples.

Example1:

Generating the event from the PmVar variable of the String type on each writing, so the string written into the variable will appear in the description of the event. The Macro expression will be shown for the "Event description (desc)" configurator.

$.expr(pVar.Value)

Example2:

Generating the event from the PmVar variable of the String type on each writing, so the localized text, separator and current value written into the variable will appear in the description of event. The Macro expression will be shown for the "Event description (desc)" configurator.

$.join($.text("sys","description"), ": ", $.expr("pVar.Value"))

or to ExtSubVar

$.join($.text("sys","description"), ": ", $.expr("pVar.Extension('sv').Value"))