Fired when a profile accepts an invitation to a calendar event, raised from CalendarManager.accept once the attendee's participation status has been updated and, if they have their own calendar, a copy of the event has been added to it. Event ID: calendar-event.
Implements: TriggerEvent
Properties
| Property | Returns | Description |
|---|---|---|
| attendeeRequest | AttendeeRequest | The attendee request that was accepted, giving access to the calendar event, the organiser and the guest list. |
| attributes | Map<String,Object> | Extra properties for this event. Always empty for this event. |
| eventId | String | The constant event id used to register listeners for this event type. |
| sourceProfile | Profile | The profile who accepted the invitation. |
| triggerItem1 | String | The id of the website the accepted event's calendar belongs to. |
| triggerItem2 | String | The id of the calendar the accepted event belongs to. |
| triggerItem3 | String | Not used, always null. |
| triggerItem4 | String | Not used, always null. |
| triggerItem5 | String | Not used, always null. |
| website | Website | The website the accepted event's calendar belongs to. |
Inherited from TriggerEvent
Properties
| Property | Returns | Description |
|---|---|---|
| serialisable | boolean | Whether this event's attributes were built to survive being persisted, ie every value is a plain serialisable value rather than a persistent entity or some other object that only makes sense inside the firing transaction. Only the firing app can know this, so it declares it - see EventBuilder. An agent that subscribes to an event does not run when it fires. The event is written to storage as JSON, buffered with others, and read back minutes later in a different session, so a value that cannot be written and read back is not merely awkward, it breaks the whole delivery. The agent framework therefore ignores any event which does not say yes here. |
Methods
isSerialisable()
Returns: boolean
Whether this event's attributes were built to survive being persisted, ie every value is a plain serialisable value rather than a persistent entity or some other object that only makes sense inside the firing transaction. Only the firing app can know this, so it declares it - see EventBuilder. An agent that subscribes to an event does not run when it fires. The event is written to storage as JSON, buffered with others, and read back minutes later in a different session, so a value that cannot be written and read back is not merely awkward, it breaks the whole delivery. The agent framework therefore ignores any event which does not say yes here.
Methods
getWebsite() · getSourceProfile() · getEventId() · getTriggerItem1() · getTriggerItem2() · getTriggerItem3() · getTriggerItem4() · getTriggerItem5() · getAttributes() · getAttendeeRequest()
getWebsite()
Returns: Website
The website the accepted event's calendar belongs to.
getSourceProfile()
Returns: Profile
The profile who accepted the invitation.
getEventId()
Returns: String
The constant event id used to register listeners for this event type.
getTriggerItem1()
Returns: String
The id of the website the accepted event's calendar belongs to.
getTriggerItem2()
Returns: String
The id of the calendar the accepted event belongs to.
getTriggerItem3()
Returns: String
Not used, always null.
getTriggerItem4()
Returns: String
Not used, always null.
getTriggerItem5()
Returns: String
Not used, always null.
getAttributes()
Returns: Map<String,Object>
Extra properties for this event. Always empty for this event.
getAttendeeRequest()
Returns: AttendeeRequest
The attendee request that was accepted, giving access to the calendar event, the organiser and the guest list.