# Integration Guides - [Outbound Incident Guide](/unifi/2.2/integration-guides/outbound-incident-guide.md): Follow this guide to configure a simple outbound integration to the table API of your Personal Developer Instance. It is given as an aid for those new to Unifi, or to play as part of a trial. - [Getting Started](/unifi/2.2/integration-guides/outbound-incident-guide/getting-started.md): This Guide utilises the Unifi Integration Designer portal interface which allows you to configure and manage integrations much more intuitively and with greater efficiency. - [Process](/unifi/2.2/integration-guides/outbound-incident-guide/process.md): The first element to configure is the Process, which is the top level configuration element where all Integrations are contained. - [Integration](/unifi/2.2/integration-guides/outbound-incident-guide/integration.md): This is what defines the connection between a Process and the single system it's connecting with. It is also where most of the configuration and settings are stored. - [Connection](/unifi/2.2/integration-guides/outbound-incident-guide/connection.md): The Connection allows messages to be sent and received and stores all the authentication details of the Integration specific to a single environment. - [Trigger](/unifi/2.2/integration-guides/outbound-incident-guide/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the process concerned. - [Create Scenario](/unifi/2.2/integration-guides/outbound-incident-guide/create-scenario.md): For each of our Scenarios we will need to configure the relevant Messages & Fields. This scenario will need to be tested before moving on to the next. - [CreateIncidentResponse Message](/unifi/2.2/integration-guides/outbound-incident-guide/create-scenario/createincidentresponse-message.md): The CreateIncidentResponse Message is the immediate, synchronous response that is sent after processing the Createincident Message. - [CreateIncidentResponse Fields](/unifi/2.2/integration-guides/outbound-incident-guide/create-scenario/createincidentresponse-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the CreateIncidentResponse Message. - [CreateIncident Message](/unifi/2.2/integration-guides/outbound-incident-guide/create-scenario/createincident-message.md): The CreateIncident Message will create a ticket on the target table of the integrated system. - [CreateIncident Fields](/unifi/2.2/integration-guides/outbound-incident-guide/create-scenario/createincident-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the CreateIncident Message. - [Test CreateIncident](/unifi/2.2/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](/unifi/2.2/integration-guides/outbound-incident-guide/update-scenario.md): For each of our Scenarios we will need to configure the relevant Messages & Fields. This scenario will need to be tested before moving on to the next. - [Response Message](/unifi/2.2/integration-guides/outbound-incident-guide/update-scenario/response-message.md): The Response Message is the immediate synchronous response that is sent to acknowledge the successful transport of another Message. - [UpdateIncident Message](/unifi/2.2/integration-guides/outbound-incident-guide/update-scenario/updateincident-message.md): The UpdateIncident Message is an update type message that sends updates to the bonded record. - [UpdateIncident Fields](/unifi/2.2/integration-guides/outbound-incident-guide/update-scenario/updateincident-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the UpdateIncident Message. - [Test UpdateIncident](/unifi/2.2/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](/unifi/2.2/integration-guides/outbound-incident-guide/resolve-scenario.md): For each of our Scenarios we will need to configure the relevant Messages & Fields. This scenario will need to be tested before moving on to the next. - [ResolveIncident Message](/unifi/2.2/integration-guides/outbound-incident-guide/resolve-scenario/resolveincident-message.md): The ResolveIncident Message is an update type message that we will configure to deal specifically with our resolve scenario (resolve the bonded records). - [ResolveIncident Fields](/unifi/2.2/integration-guides/outbound-incident-guide/resolve-scenario/resolveincident-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the ResolveIncident Message. - [Test ResolveIncident](/unifi/2.2/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](/unifi/2.2/integration-guides/outbound-incident-guide/build-integration-level.md): It is possible to run the Build process from the Integration. This will cause the process to cycle through each of the Messages on the Integration in turn. - [Conclusion](/unifi/2.2/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide.md): Follow this guide to configure a bidirectional asynchronous integration to the Incident table. This push-push integration will use Unifi both ends. - [Getting Started](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/getting-started.md): This Guide utilises the Unifi Integration Designer portal interface which allows you to configure and manage integrations much more intuitively and with greater efficiency. - [Process](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/process.md): The first element to configure is the Process, which is the top level configuration element where all Integrations are contained. - [Web Service](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/web-service.md): The entry point for a Process - you would build one endpoint per process. Once connected, messages are guided to the integration based on the unique combination of authentication user & endpoint. - [Integration](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/integration.md): This is what defines the connection between a Process and the single system it's connecting with. It is also where most of the configuration and settings are stored. - [Connection](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/connection.md): The Connection allows messages to be sent and received and stores all the authentication details of the Integration specific to a single environment. - [Trigger](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the Process concerned. - [Create Scenario](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario.md): For each of our Scenarios we will need to configure the relevant Messages & Fields. This scenario will need to be tested before moving on to the next. - [Response Message](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/response-message.md): The Response Message is the immediate synchronous response that is sent to acknowledge the successful transport of another Message. - [CreateIncidentReceipt Message](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/createincidentreceipt-message.md): The CreateIncidentReceipt Message is the asynchronous receipt that is sent after processing the Createincident Message. - [CreateIncidentReceipt Fields](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/createincidentreceipt-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the CreateIncidentReceipt Message. - [CreateIncident Message](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/createincident-message.md): The CreateIncident Message will create a ticket on the target table of the integrated system. - [CreateIncident Fields](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/createincident-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the CreateIncident Message. - [Test CreateIncident](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario.md): For each of our Scenarios we will need to configure the relevant Messages & Fields. This scenario will need to be tested before moving on to the next. - [Receipt Message](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/receipt-message.md): The Receipt Message is the asynchronous receipt that is sent after processing update type messages. - [UpdateIncident Message](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/updateincident-message.md): The UpdateIncident Message is an update type message that sends updates to the bonded record. - [UpdateIncident Fields](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/updateincident-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the UpdateIncident Message. - [Test UpdateIncident](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario.md): For each of our Scenarios we will need to configure the relevant Messages & Fields. This scenario will need to be tested before moving on to the next. - [ResolveIncident Message](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/resolveincident-message.md): The ResolveIncident Message is an update type message that we will configure to deal specifically with our resolve scenario (resolve the bonded records). - [ResolveIncident Fields](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/resolveincident-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the ResolveIncident Message. - [Test ResolveIncident](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/test-resolveincident.md): Follow these steps to test the ResolveIncident Message. - [Build - Integration Level](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/build-integration-level.md): It is possible to run the Build process from the Integration. This will cause the process to cycle through each of the Messages on the Integration in turn. - [Build the Other Half](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/build-the-other-half.md): Building the other half of our integration is much easier than you think. - [Move the Integration](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/build-the-other-half/move-the-integration.md): The first step to building the other half of the Integration is to export it from one instance and import it to the other. - [Reconfigure the Connections](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/build-the-other-half/reconfigure-the-connections.md): The next step in building the other half of the Integration is to reconfigure the connections. - [Conclusion](/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](/unifi/2.2/integration-guides/incident-update-poller-guide.md): Follow this guide to configure a poller integration - polling the table API of your Personal Developer Instance (PDI) for updates only. This is the first of five Poller Guides. See 'Scope' for more. - [Polling](/unifi/2.2/integration-guides/incident-update-poller-guide/polling.md): We will configure a scheduled poll to query the remote system at regular intervals and pull back data that has changed which it will pass to Unifi to process. - [Poll Processor](/unifi/2.2/integration-guides/incident-update-poller-guide/polling/poll-processor.md): The Poll Processor contains the logic that will be applied when polling a remote system for data. - [Poller](/unifi/2.2/integration-guides/incident-update-poller-guide/polling/poller.md): A Poller is a configuration record which defines the frequency of polling and which logic to use. - [Inbound Message](/unifi/2.2/integration-guides/incident-update-poller-guide/inbound-message.md): We will need to configure an inbound message to process the data returned from the poll. - [UpdateIncidentInbound Message](/unifi/2.2/integration-guides/incident-update-poller-guide/inbound-message/updateincidentinbound-message.md): We will configure an inbound update message to process the data returned from the poll and update our target record. - [UpdateIncidentInbound Fields](/unifi/2.2/integration-guides/incident-update-poller-guide/inbound-message/updateincidentinbound-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the UpdateIncidentInbound Message. - [Message Identification](/unifi/2.2/integration-guides/incident-update-poller-guide/message-identification.md): Unifi needs to identify the name of the inbound message in order to know how to process the inbound data. - [Bond Identification](/unifi/2.2/integration-guides/incident-update-poller-guide/bond-identification.md): In order for both systems to identify & understand which records are bonded and to facilitate only returning data from bonded records, we need to make a few configuration changes. - [Edit Incident Form](/unifi/2.2/integration-guides/incident-update-poller-guide/bond-identification/edit-incident-form.md): The first configuration change we need to make to facilitate Bond identification is to add the Correlation ID field to the Incident form in our PDI. - [Edit CreateIncident Message](/unifi/2.2/integration-guides/incident-update-poller-guide/bond-identification/edit-createincident-message.md): Here we will deal with the configuration changes that need to be made to our CreateIncident Message to facilitate identifying and returning data from bonded records. - [Test Update Poll](/unifi/2.2/integration-guides/incident-update-poller-guide/test-update-poll.md): You should have successfully configured a Poll Processor, Poller and an inbound update message. You should also have made further changes to allow for message & bond identification. Now to test. - [Conclusion](/unifi/2.2/integration-guides/incident-update-poller-guide/conclusion.md): Congratulations on successfully polling your PDI for updates using this Update Poller Guide. - [Incident Multiple Message Poller Guide](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide.md): Follow this second of five Poller Guides to configure an integration - polling the table API of your Personal Developer Instance (PDI) for updates & deciding between multiple messages to process. - [Polling](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/polling.md): We will configure a scheduled poll to query the remote system at regular intervals and pull back data that has changed which it will pass to Unifi to process. - [Poll Processor](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/polling/poll-processor.md): The Poll Processor contains the logic that will be applied when polling a remote system for data. - [Poller](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/polling/poller.md): A Poller is a configuration record which defines the frequency of polling and which logic to use. - [Inbound Messages](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/inbound-messages.md): We will need to configure inbound Messages to process the data returned from the poll. - [ResolveIncidentInbound Message](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/inbound-messages/resolveincidentinbound-message.md): We will configure another inbound update type message to process the data returned from the poll and update our target record. - [ResolveIncidentInbound Fields](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/inbound-messages/resolveincidentinbound-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the ResolveIncidentInbound Message. - [Testing](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/testing.md): You should have successfully configured a Poll Processor and Poller. You should also have configured the ResolveIncidentInbound message. The next thing to do is to test. - [Test UpdateIncidentInbound](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/conclusion.md): Congratulations on using this Multiple Message Poller Guide to successfully poll your PDI for updates - deciding between multiple messages in Unifi to process the returned data. - [Incident Create Poller Guide](/unifi/2.2/integration-guides/incident-create-poller-guide.md): Follow this guide to configure a poller integration - polling the table API of your Personal Developer Instance (PDI) for creates only. This is the third of five Poller Guides. See 'Scope' for more. - [Polling](/unifi/2.2/integration-guides/incident-create-poller-guide/polling.md): We will configure a scheduled poll to query the remote system at regular intervals and pull back data from the relevant, newly created, unbonded records which it will pass to Unifi to process. - [Connection Variables](/unifi/2.2/integration-guides/incident-create-poller-guide/polling/connection-variables.md): Connection Variables can be especially useful if you have multiple connection environments - e.g. Dev, Test, Prod - each containing different data. - [Poll Processor](/unifi/2.2/integration-guides/incident-create-poller-guide/polling/poll-processor.md): The Poll Processor contains the logic that will be applied when polling a remote system for data. - [Poller](/unifi/2.2/integration-guides/incident-create-poller-guide/polling/poller.md): A Poller is a configuration record which defines the frequency of polling and which logic to use. - [Messages](/unifi/2.2/integration-guides/incident-create-poller-guide/messages.md): We will need to configure messages to process and respond to the data returned from the poll. - [CreateIncidentInboundReceipt Message](/unifi/2.2/integration-guides/incident-create-poller-guide/messages/createincidentinboundreceipt-message.md): We will configure an outbound receipt message to respond to the data returned from the poll and update the originating record in the remote instance with the correlation id. - [CreateIncidentInboundReceipt Fields](/unifi/2.2/integration-guides/incident-create-poller-guide/messages/createincidentinboundreceipt-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the CreateIncidentInboundReceipt Message. - [CreateIncidentInbound Message](/unifi/2.2/integration-guides/incident-create-poller-guide/messages/createincidentinbound-message.md): We will configure an inbound create message to process the data returned from the poll and create a new target record. - [CreateIncidentInbound Fields](/unifi/2.2/integration-guides/incident-create-poller-guide/messages/createincidentinbound-fields.md): We will utilise the Field & Field Map records to configure the Message Scripts for the CreateIncidentInbound Message. - [Build - Integration Level](/unifi/2.2/integration-guides/incident-create-poller-guide/build-integration-level.md): It is possible to run the Build process at the Integration level. This will cause the process to cycle through each of the Messages on the Integration in turn. - [Test Create Poll](/unifi/2.2/integration-guides/incident-create-poller-guide/test-create-poll.md): You should have successfully configured a Poll Processor and Poller. You should also have configured an inbound create type Message and its outbound receipt. Follow these steps to test. - [Conclusion](/unifi/2.2/integration-guides/incident-create-poller-guide/conclusion.md): Congratulations on successfully polling your PDI for non-bonded Incidents using this Create Poller Guide. - [Incident Parent and Child Poller Guide](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide.md): Follow this fourth of five Poller Guides to configure an integration, polling the table API of your PDI for updates in two stages - an initial light poll which passess data to a more detailed poll. - [Polling](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/polling.md): We will configure a scheduled poll to query the remote system and pull back a list of records that have changed. Data from which will be passed to an on-demand poll to pull back more detailed data. - [Connection Variables](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/polling/connection-variables.md): Connection Variables can be especially useful if you have multiple connection environments - e.g. Dev, Test, Prod - each containing different data. - [Child Poll Processor](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/polling/child-poll-processor.md): The Poll Processor contains the logic that will be applied when polling a remote system for data. - [Child Poller](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/polling/child-poller.md): A Poller is a configuration record which defines the frequency of polling and which logic to use. - [Parent Poll Processor](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/polling/parent-poll-processor.md): The Poll Processor contains the logic that will be applied when polling a remote system for data. - [Parent Poller](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/polling/parent-poller.md): A Poller is a configuration record which defines the frequency of polling and which logic to use. - [Inbound Messages](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/inbound-messages.md): We will utilise already configured inbound Messages to process the data returned from the poll. - [Testing](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/testing.md): You should have successfully configured two Poll Processors and two Pollers - to enable polling data from your PDI & passing the relevant data between them and then passing it to Unifi. Now to test. - [Test UpdateIncidentInbound](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/conclusion.md): Congratulations on using this Parent and Child Poller Guide to successfully poll your PDI for updates - passing relevant data between Pollers, deciding which Messages to use to process that data. - [Incident Attachment Poller Guide](/unifi/2.2/integration-guides/incident-attachment-poller-guide.md): Follow this fifth Poller Guide to configure an integration, polling the attachment API of your PDI for attachments in two stages - an initial light poll which passess data to a more detailed poll. - [Polling](/unifi/2.2/integration-guides/incident-attachment-poller-guide/polling.md): We will configure an on-demand poll to query the remote system and pull back a list of attachments added to bonded records that have changed. Each will then be retrieved by another on-demand poll. - [Connection Variables](/unifi/2.2/integration-guides/incident-attachment-poller-guide/polling/connection-variables.md): Connection Variables can be especially useful if you have multiple connection environments - e.g. Dev, Test, Prod - each containing different data. - [Edit Endpoint URLs](/unifi/2.2/integration-guides/incident-attachment-poller-guide/polling/edit-endpoint-urls.md): We have previously been polling the Table API of our PDI. We now want to poll the Attachment API. To facilitate this, we will need to make changes to the Endpoint URLs in multiple places. - [Get Attachment Poll Processor](/unifi/2.2/integration-guides/incident-attachment-poller-guide/polling/get-attachment-poll-processor.md): The Poll Processor contains the logic that will be applied when polling a remote system for data. - [Get Attachment Poller](/unifi/2.2/integration-guides/incident-attachment-poller-guide/polling/get-attachment-poller.md): A Poller is a configuration record which defines the frequency of polling and which logic to use. - [Select Attachments Poll Processor](/unifi/2.2/integration-guides/incident-attachment-poller-guide/polling/select-attachments-poll-processor.md): The Poll Processor contains the logic that will be applied when polling a remote system for data. - [Select Attachments Poller](/unifi/2.2/integration-guides/incident-attachment-poller-guide/polling/select-attachments-poller.md): A Poller is a configuration record which defines the frequency of polling and which logic to use. - [Edit Child Poll Processor](/unifi/2.2/integration-guides/incident-attachment-poller-guide/polling/edit-child-poll-processor.md): Our previously configured Child Poll Processor only polled for updates against records passed to it from its Parent. We will now edit it so that it will also kick off the Select Attachments Poller. - [Edit Child Update Poller](/unifi/2.2/integration-guides/incident-attachment-poller-guide/polling/edit-child-update-poller.md): A Poller is a configuration record which defines the frequency of polling and which logic to use. - [Messages](/unifi/2.2/integration-guides/incident-attachment-poller-guide/messages.md): We will need to configure a new inbound Message to process the attachments returned from the poll. We will also utilise all the previously configured Messages in testing our Integration. - [AddAttachmentInbound Message](/unifi/2.2/integration-guides/incident-attachment-poller-guide/messages/addattachmentinbound-message.md): We will configure another inbound update type Message to process the attachment data returned from the poll and update our target record. - [Testing](/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing.md): You should have successfully configured two Poll Processors and two Pollers (plus edited the previously configured Child Poller & Poll Processor and edited the Endpoint URLs. Now to test. - [Test Outbound Scenarios](/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md): Follow these instructions to test the outbound Message scenarios. - [Test CreateIncidentInbound](/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](/unifi/2.2/integration-guides/incident-attachment-poller-guide/conclusion.md): Congratulations on using this Attachment Poller Guide to successfully poll your PDI for updates & attachments - passing relevant data between Parent & Child Pollers, deciding which Messages to use.