Retrieve Payload FeatureGeneral Information What is the Problem? There is no direct way to figure out the discovery payloads after the discovery completion (Horizontal Discovery). For the payload generated by Pattern execution, you must go to the relevant input ECC queue and then retrieve the payload. There is no way to figure out the input IRE payload. Similarly, there is no way to check the output IRE payload. In such scenario, debugging IRE payload processing error becomes tricky, challenging and time consuming. What are we doing? The solution for the mentioned problem will fetch/generate the various payloads (Payload from pattern execution, Input IRE payload, Output IRE payload) at one place in a flow, making it easy for the user to check the payload content for a completed horizontal discovery and check if there any payload errors in one go. How it is being solved? Fetching of all the relevant payloads is achieved by extending the Payload Generator feature present in the Pattern Designer. The current implementation and look and feel of the Payload Generator will be enhanced to behave differently when we want to fetch/generate the payloads of a completed discovery. Capabilities will be added to get redirected to the payload generator feature when we want to check the payloads for a certain discovery from the pattern log in a similar line where users are redirected from the pattern log to the pattern designer when they wish to debug the pattern. Requirements and Use Cases There is no direct way to check all the relevant payloads for a certain horizontal discovery, because of which it contributes to a considerable portion of the customer cases as users are unable to figure out the reason behind IRE failures. Debugging an IRE failure at present is complex because the IRE logs shown as part of Discovery pattern log is not clear and informative many times. Now to fetch the output IRE payload, we need to generate the input IRE payload, which is complex and requires considerable effort. Once we have the input IRE payload, we need to carefully follow a sequence of steps to get the output IRE payload. The feature will fetch/generate: Payload After Pattern Execution: This is the payload we see in the relevant Input ECC Queue records. The payload contains the full list of Cis, Relation and References.Input IRE Payload: This payload is achieved after running the configured pre sensors for the pattern to the payload (which is generated after pattern execution). This payload is the input payload for the IRE.Output IRE Payload: This payload is the result of the IRE Identification and contains information on each CI, whether it was created, updated or skipped because of any IRE errors. Feature Flow We have introduced two buttons in Payload Processing section of the Pattern log. Retrieve Payload: Click this will take you to the Pattern Designer where the feature sits, and you will be asked to enter the page number of the discovery result, this is to incorporate multi page discovery scenario. In case the discovery is not multi paged then we need to enter 1 as page number.IRE Error Documentation: IF the IRE error is quite visible in the pattern log, then we can click on the button to go to ServiceNow doc which tells us about different IRE error, what it means and how it can be resolved. This button will only be visible when there are IRE failures in horizontal discovery. HD is successful. HD experiences IRE failure. After we click the retrieve payload button, we will be redirected to PD. Here we are supposed to enter the page number for which we want to retrieve the payloads. Once you click on Retrieve Pattern Payload Button, you will get the payload which is the output of the Pattern Execution. This is Pattern Payload. Here all the Pre sensors configured to run for the pattern will already be auto selected. Now there are 4 buttons visible which are: Reset Payload: Resets the payload back to pattern payload.Run Pre-Sensors: Will run the selected pre sensors over the pattern payload.Format IRE Payload: This will format payload to either index based or internal id based formatting for the cis. This is a new feature too. Clicking this after running pre sensors will give you the Input IRE Payload.Test IRE: This will run your payload against IRE, to give Output IRE payload. Note: To simulate the HD processing scenario, you need to first run pre sensors, then format the payload and then do Test IRE. Now in case of IRE failure of HD , when you use this feature and click on TEST IRE button, then you will see a message informing that the payload has IRE errors. There will also be link provided for ServiceNow IRE failures documentation in the message, which will help you in understanding and resolving the IRE error. On clicking the link you will be redirected to the documentation. Document URL: https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/configuration-management/concept/identification-simulation.html?cshalt=yes