Message Monitoring is used to check the integration result after processing the Inbound or Outbound interface. The integration result includes Pending, Failed, Completed, Cancelled status and the reason why it failed. Additionally, we can know the real sObject is integrated successfully with completed status.
Message Monitoring divided into three sections which are:- Storage, Filters, and Message.
By using Message Board, we can check the amount of space we have used and how much is available for your
(1) Data Storage.
(2) File Storage Big.
We can check it anytime.
|Data Storage||It contains all the messages stored in the table.|
|File Storage||It contains all the attachments.|
|Big Object Storage||It contains all the massive amounts of data on the Salesforce.|
This screenshot display the storage usage section on Message Monitoring.
With the message monitor, you can search over different criteria. For example, you can search message by date e.g. the creation or modified date. You can select any of the mode from the picklist like Message, API or Event message monitoring. You can sort the view and search message over its content. Likewise, you can search for messages and see if it gets posted or failed. You can see the different statuses of messages e.g. green, red, yellow and grey.
Following are the search criteria you can use
|Mode||It Contains option All, Message, API and Event monitoring.|
|Integration Name||The name of the integration|
|Interface Name||The name of the interface|
|Message Name||The key to the message|
|Message Status||The status of the message|
|Message Content(Data)||The content of the message|
|Maximum Of Records||Use this filter to limit the result in the Message Monitoring to prevent the time out due to many messages.|
|Transaction Id||You can use this field to define a unique transaction id for all messages belonging to a logical object.|
|Basket Name||Use to filter the specific basket.|
|System External Id||You can filter and reference the message Id of an external system. It also can save the system Id.|
|Date||You can specify Creation or Modified date|
|From||The from date|
|To||The to date|
|Sort By||You can specify Creation date, Modified date or Message Name|
|Order By||Use to filter the message in order by Ascending or Descending.|
|Message Direction||You can specify to see Inbound and Outbound Message separately.|
|Business External Id||This is the id of the business object.So we can enter Id here in this field.|
|Transfer Id||This field is a unique id to identify the transfer package.|
|Comment Content||You can filter both comment short and long for the full error text.|
We provide two more modes to search API and Event message monitoring. It simplifies our work, and now we can easily search and differentiate. We can see in the picture given below.
- We can select any of the modes.
Field: Interface Name
You can see the different fields and their content. You can change the field content and do a reprocessing with the changed value.
SKYVVA provides an option for the user to exclude and include the particular interface to search the messages on the Message Monitoring Board. You can either search the specific interface by excluding the one you do not want to search for the message. Overall, you can select multiple interfaces to include or exclude.
Field: Message Status
You can select the message over the message status:
The following are the description of message status:
- None: Select all the status.
- New: This status corresponds to the color blue. This status occurs when users use CDD/CDT (Change Data Detection/ Change Data Transfer) Scheduler to run as a job regularly. CDD collect changes and create the message with status “New”
- Completed: This status corresponds to the color green. A message with this status could be posted successfully.
- Failed: This status corresponds to the color red. A message with this status could not be posted successfully due to some error situations. You have to look at the error description and fix the error. A message with this status can be reprocessed.
- Pending: This status corresponds to the color yellow. A message with this status is in the waiting state because it has to the dependent relationship to other messages which could not be posted successfully. Such a message can be reprocessed as well.
- Canceled: This status corresponds to the color grey. This status corresponds to the color grey. The user is not able to delete messages with status pending so he had to cancel them at the first. As a result, we will get messages with status Cancelled and the user will be able now to delete them.
Field: Maximum of Records
In case there are too many messages then we will run into time out, use this filter to limit the result in the Message Monitor.
Field: Message Direction
The screenshot of Message Direction is given below
The description of Message Direction:
|Inbound||Use this value when you want to search for Inbound messages.|
|Outbound||Use this value when you want to search for Outbound messages.|
|–None–||Use this value when you want to search for Inbound and Outbound messages.|
The following action is applied to the search screen:
Here the description’s function of the button in filter:
|After specifying all the search criteria push on this button to start the search.|
|With this button, you reset e.g. clear the search criteria you have entered before.|
This section will be displayed all types of messages as Failed, Pending, Cancelled, Completed, and New.
The following action for the result screen can be applied:
You can jump into the detail of a message. Click on the message name to jump into the detail. Here is an example of a message detail.
The user can also select (1) all the entry only per page and then he can apply an action (2) for the result screen.
- 19.1 Change the Message Name
- 19.2 Reprocessing of Messages
- 19.3 Jump to Interface from message Monitor
- 19.4 Jump from Task to SKYVVA message
- 19.5 Message summarization report
- 19.6 How to check entries in the message table
- 19.7 Create hypertext link to jump to Failed Message
- 19.8 The new v3 message monitoring with hierarchical view
- 19.9 Message,API and Event message monitoring
- 19.10 Detail view of message monitoring
- 19.11 Integrate3Batch to handle tree message