See the IAppEventMgr interface for details on IAppEventObj.

public int addAction(
	IValList action)

action. The input IValList object that defines the action to add. When an event is triggered, actions are executed in the same order in which they were added. The entries in this IValList object vary from one action type to another.

public int deleteActions()

public IEnumObject enumActions()

public IValList getAttributes()

public String getName()

pName. A pointer to an input buffer.

nName. The size of the input buffer.

public int setAttributes(
	IValList attrList)

attrList. The input IValList object that specifies the attributes. The keys and values you can specify are as follows. Note that string constants are available in the class com.kivasoft.types.GXConstants.

• GXConstants.GX_AE2_RE_KEY_STATE
• A variable that specifies the initial state of the event. This key is optional and has the following possible values:

• GXConstants.GX_AE2_RE_EVENT_DISABLED
• GXConstants.GX_AE2_RE_EVENT_ENABLED (the default)
• GXConstants.GX_AE2_RE_KEY_TIME
• An optional key that specifies the time at which the event will be triggered. Use the following format:

• hh:mm:ss W/DD/MM
• hh: 0 -23
• mm: 0 - 59
• ss: 0 - 59
• W (day of the week): 0 - 6 with 0 = Sunday.
• DD (day of the month): 1 - 31
• MM (month): 1 - 12
• Each of these fields may be either an asterisk (meaning all legal values) or a list of elements separated by commas. An element is either a number or two numbers separated by a minus sign indicating an inclusive range. For example, 2, 5 - 7:0:0 5/*/* means the event is triggered at 2 AM, 5AM, 6 AM and 7 AM every Friday.
• The specification of days can be made by two fields: day of the month (DD) and day of the week (W). If both are specified, both take effect. For example, 1:0:0 1/15/* means the event is triggered at 1 AM every Monday, as well as on the fifteenth of each month. To specify days by only one field, set the other field to *.
• GXConstants.GX_AE2_RE_KEY_ACTION_MODE
• An optional key that specifies whether actions are to be executed concurrently (at the same time) or in series (one after another). In serial execution, each action finishes executing before the next one starts, and execution occurs in the same order in which the actions were added.
• This key has the following possible values:

• GXConstants.GX_AE2_RE_ACTION_SERIAL
• GXConstants.GX_AE2_RE_ACTION_CONCURRENT (the default)