Overview

The EventType provide the metadata for a class of events. It specifies the name and type of properties that should be present in the events of that type. The event subscribers write the filtering conditions on event types. If the condition is true the event handlers get executed.

Members

Show inherited members

Projections
Name Type Required Description

attachedMarkers

marker[]
Set of marker elements associated with the entity.

attachedReminders

reminder[]
List of reminders attached to the entity

attachedSubscriptions

subscription[]
List of subscriptions attached to the entity

attributes

attributeDescriptor[]
The attribute types of a particular EventType is returned by getAttributes(). Used the GUI teams to show list of attributes that can be used in building the RuleCondition

collabId

beeId
CollabId of the snapshot

createdOn

dateTime
Entity's creation date

creator

actor
The actor that created this entity

deleted

boolean
Deletion flag. If this property is set to true the entity is deleted.

description

string
returns the description of the event type

displayName

string

javaClassName

string

modifiedBy

actor
The actor that last modified the entity

modifiedOn

dateTime
The date when entity was last modified

name

string
Name of the entity.

parent

entity
The parent for this entity.

payloadType

string
returns the payload type. In the current implementation this is PLSQL ADT Type.

snapshotId

string
Contains the snapshot identifier for this snapshot. Snapshot identifiers are used to implement optimistic locking on the server.

synchronous

boolean
returns boolean whether the event is synchronous or not. If the event type is synchronous, the event handlers get executed before the call is returned to the event publisher. The event handlers in synchronous events are only PL/SQL calls. If the event type is Asynchronous event types, the event is put into event queue and the events are processed by event handlers Asynchronusly.

Hierarchy

Inherits From

Inherited By

Examples

Below are examples in XML formats. All examples are shown with all inherited members. Quoting when required is part of the examples, but you must obviously populate with your own data.

XML Example

(show inherited members)

<obh:eventDefinition xsi:type="obh:eventDefinition" xmlns:obh="http://www.oracle.com/beehive" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <attachedMarkers>your_marker_0</attachedMarkers>
        <attachedMarkers>your_marker_1</attachedMarkers>
        <attachedMarkers>your_marker_2</attachedMarkers>
         <attachedReminders>your_reminder_0</attachedReminders>
        <attachedReminders>your_reminder_1</attachedReminders>
        <attachedReminders>your_reminder_2</attachedReminders>
         <attachedSubscriptions>your_subscription_0</attachedSubscriptions>
        <attachedSubscriptions>your_subscription_1</attachedSubscriptions>
        <attachedSubscriptions>your_subscription_2</attachedSubscriptions>
         <attributes>your_attributeDescriptor_0</attributes>
        <attributes>your_attributeDescriptor_1</attributes>
        <attributes>your_attributeDescriptor_2</attributes>
         <collabId>your_beeId_0</collabId>
         <createdOn>your_dateTime_0</createdOn>
         <creator>your_actor_0</creator>
         <deleted>your_boolean_0</deleted>
         <description>your_string_0</description>
         <displayName>your_string_0</displayName>
         <javaClassName>your_string_0</javaClassName>
         <modifiedBy>your_actor_0</modifiedBy>
         <modifiedOn>your_dateTime_0</modifiedOn>
         <name>your_string_0</name>
         <parent>your_entity_0</parent>
         <payloadType>your_string_0</payloadType>
         <snapshotId>your_string_0</snapshotId>
         <synchronous>your_boolean_0</synchronous>
 </obh:eventDefinition>

Referenced By Representaions