SimpleEvent resources are used to define an object that represents an activity, such as sending an invoice, debiting an account, and so on.
You can modify and enrich events before they are asserted into working memory. Rule evaluation depends on event values at time of assertion, so they can be changed only before assertion.
Global Var? The name to appear as the label for the resource. Names follow Java variable naming restrictions. Do not use any reserved words. Names must be unique within a folder. See Identifiers (Names) in TIBCO BusinessEvents Language Reference. Specify a numerical value and a time unit. Time units available are milliseconds, seconds, minutes, hours, and days.The timer starts after the first rule evaluation. After the time to live (TTL) period, the event expires and is deleted from working memory.With Persistence object management, the expired event is also marked for deletion. See Delete Retracted Objects from Database for more details.
● One or higher (>0): the event expires after the specified number of units elapse.
● Zero (0): the event expires after the completion of the first RTC cycle. Do not set to 0 if you want to correlate the event with a future event or other future occurrences of this event.
● A negative integer (<0): the event does not expire, and must be explicitly consumed. This event inherits from the event you select here. Leave blank if you don’t want to use inheritance. Default Destination Unless you specify a destination explicitly, events of this type are sent to the destination you select here. For example you can send an event to the default destination of its event type using the Event.sendEvent() function. You can specify one or more actions to perform when the event expires. Click the rule function button to display the rule function editor.Note: If an event is explicitly consumed in a rule, BusinessEvents does not execute the expiry action.
Global Var? The name to appear as the label for the property. Names follow Java variable naming restrictions. Do not use any reserved words. See Identifiers (Names) in TIBCO BusinessEvents Language Reference.Note: In addition to standard naming restrictions, do not begin a property name with _ns_ or _nm_. These have a special use. See XREF.For events used in JMS channels Names beginning with _jms or jms (case insensitive) are used only for JMS header properties. See Table 7, JMS Header Field Names for the list of properties. See Using JMS Header Properties in Incoming and Outgoing Messages. Consult the JMS specification for more details. Note: For properties of type Double, all NaN (Not a Number) values are converted to 0.00.An event can have a payload. The payload corresponds to a message body. Payloads are defined using XML. The table below describes the payload parameters. The following parameters appear in the drop-down list in the Payload tab:
An element that contains other elements. This is like a structure in a programming language. The complex element can contain zero or more elements of other types, including other complex elements. An element with a specified data type. You can specify a scalar data type (string, integer, and so on), you can reference an XML type, or you can specify the TIBCO ActiveEnterprise Any data type. The specific data type. For example, float or month. Refer to the TIBCO BusinessWorks Palette Reference for a complete list. A reference to an element in a stored XML schema. See TIBCO Designer documentation for more information about XML schemas. An attribute with a specified data type. You can specify a scalar data type (string, integer, and so on), you can reference an XML type, or specify the TIBCO ActiveEnterprise Any data type. The specific data type. For example, float or month. Refer to the TIBCO BusinessWorks Palette Reference for a complete list. A sequence of elements. Each item in the sequence is a structure of the sub-elements of this element. A choice of elements. The data type of this element can be one of the sub-elements defined. The data type of this element can be all of the data types of the sub-elements defined. A reference to an XML group in a stored XML schema. See TIBCO Designer documentation for more information about XML schema. Model Group A reference to any XML Element. You can use the Coercions button to supply a reference to the XML Element for this item when it appears in the input or process data.
Copyright © TIBCO Software Inc. All Rights Reserved.