{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":760,"path":"api-reference/server-api-reference/EventQueueProcessorOOBScopedAPI.md","title":"EventQueueProcessorOOB - Scoped","bundle":null,"doc_type":null,"release":"australia","body":"\n# EventQueueProcessorOOB- Scoped\n\nThe EventQueueProcessorOOB script include provides methods to manage event requests on the inbound event queue \\(located in the Inbound Queue \\[sn\\_tmt\\_core\\_inbound\\_queue\\] table\\).\n\nIf you want to change the default functionality of this script include, you need to override these methods in the `EventQueueProcessor` script include. You must have the admin role to modify this script include.\n\nThis script include runs in the `sn_api_notif_mgmt` namespace.\n\n**Parent Topic:**[Server API reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/server-api-reference/api-server.md)\n\n## EventQueueProcessorOOB - transformEventObject\\(Object eventSnapshot, Object eventJson, String queueType\\)\n\nAdds attributes to the passed event snapshot.\n\nThis method is not implemented in the base instance. If you need to add attributes to the event snapshot before processing the event and sending it out on the proper message-bus, you should override this method in the `EventQueueProcessor` script include.\n\n<table id=\"table_dlh_xrb_vzb\" class=\"parameters\"><thead><tr><th>\n\nName\n\n</th><th>\n\nType\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\neventSnapshot\n\n</td><td>\n\nObject\n\n</td><td>\n\nRaw event data in which to add attributes.This object is from the payload field of the Inbound Queue \\[sn\\_tmt\\_core\\_inbound\\_queue\\] table. Inbound queue records are created by business rules, such as Trouble Ticket Attribute Change Event, that are associated with the Incident \\[incident\\] table.\n\nThe format of the event snapshot is defined by the business rule that originally pushed the event into the inbound queue.\n\n</td></tr><tr><td>\n\neventJson\n\n</td><td>\n\nObject\n\n</td><td>\n\nJSON formatted glide record that caused the event to be triggered. This is the object that was stored in the Inbound Queue table. The format of this object is dependent on the table from which it was generated, such as incident or case.\n\n</td></tr><tr><td>\n\nqueueType\n\n</td><td>\n\nString\n\n</td><td>\n\nQueue in which the event was pushed. For the default implementation, this is always `sn_tmt_core_inbound_queue`. If you modify the event queuing implementation in your instance, pass the name of the queue that contains the event record.\n\n</td></tr></tbody>\n</table>|Type|Description|\n|----|-----------|\n|None| |\n\nThe following code example shows how to call this method.\n\n```\npushEventsToEventQueue: function(eventSnapshot, queueType) {\n  if (queueType == Constants.QUEUE_TYPE.INBOUND_QUEUE) {\n    var inboundQueueEventJson = this.generateInboundQueueObj(eventSnapshot);\n    this.transformEventObject(eventSnapshot, inboundQueueEventJson, queueType);\n    // Passing isSecure as false\n    new sn_tmt_core.InboundQueue(null, false).createInboundQueueRecord(inboundQueueEventJson);\n  }\n},\n```\n\n"}}