sections in the article
This article explains what a connect message is and how it is used.
About connect messages
A connect message contains information related to one event in inriver, before and after the event has been processed by an extension that is currently listening for events.
Structure of a connect message
The connect message structure fits an XML format, a format that is both human-readable and machine-readable.
The content of a message differs depending on the event. However, a connect message will always contain the following attributes:
Note that the attribute EntityId will change name in the above example, but it will always represent the Sys_id of an entity. The number 000 is just an example of a value, as is EventName.
Connect message attributes
|Message||String - The container for a connect message|
|Action||String - The name of the action in inriver that prompted the event to trigger.|
To view connect messages
- You can view the content of a connect message in Control Center > [Your environment] > Connect > Extensions.
- Click the name of an extension that has the ability to process events.
- Under Queued Events and Processed Events, each value in the Message column is a Connect message. Below is an example of what the messages might look like.
Benefits of evaluating connect messages
Connect messages provide you with a screenshot of past events. This provides valuable information about previously made changes, for example:
- Which entities have been deleted?
- Which entities have been updated?
- Also, what data was changed within the entities?
- Which entities have been created?
- Which channels have been affected?
- This includes channel entities, among others
Keep in mind
If you are processing a lot of entities through an extension, it is better to add additional logging to your extension. That will make it easier for you to handle a lot of data.
Please sign in to leave a comment.