Fired when a user submits a contact-us form. Carries an attribute called "contactRequest" holding the ContactRequest record that was saved for the submission. Event ID: contact.
Implements: TriggerEvent
Properties
| Property | Returns | Description |
|---|---|---|
| attributes | Map<String,Object> | Extra properties for this event: "contactRequest" holding the saved ContactRequest record, when one was saved. |
| eventId | String | The constant event id used to register listeners for this event type. |
| sourceProfile | Profile | The profile who submitted the form, when the submitter was a logged-in user. |
| triggerItem1 | String | The id of the website the contact form was submitted on. |
| triggerItem2 | String | The name of the contact form that was submitted. |
| triggerItem3 | String | Not used, always null. |
| triggerItem4 | String | Not used, always null. |
| triggerItem5 | String | Not used, always null. |
| website | Website | The website the contact form was submitted on. |
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()
getWebsite()
Returns: Website
The website the contact form was submitted on.
getSourceProfile()
Returns: Profile
The profile who submitted the form, when the submitter was a logged-in user.
getEventId()
Returns: String
The constant event id used to register listeners for this event type.
getTriggerItem1()
Returns: String
The id of the website the contact form was submitted on.
getTriggerItem2()
Returns: String
The name of the contact form that was submitted.
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: "contactRequest" holding the saved ContactRequest record, when one was saved.