# Unifi Documentation ## 2.2 - [Unifi Documentation](https://docs.sharelogic.com/unifi/2.2/master.md): Welcome to the Unifi documentation space! Please take some time to read through the documentation as this will help you get the best out of the application. - [Release Notes](https://docs.sharelogic.com/unifi/2.2/release/release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, depracated features and general fixes. - [2.1 Release Notes](https://docs.sharelogic.com/unifi/2.2/release/release-notes/2.1-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, depracated features and general fixes. - [2.0 Release Notes](https://docs.sharelogic.com/unifi/2.2/release/release-notes/2.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, depracated features and general fixes. - [Hotfixes](https://docs.sharelogic.com/unifi/2.2/release/hotfixes.md): Unifi can be patched between releases by using a special Script Include called hotfix. This page contains any hotfixes that have been made for this version. Follow the instructions to apply them. - [Setup](https://docs.sharelogic.com/unifi/2.2/release/setup.md): The instructions on this page will show you to get up and running with Unifi as quickly and efficiently as possible. - [Quick Tour](https://docs.sharelogic.com/unifi/2.2/overview/quick-tour.md): A high-level overview of the Unifi application. - [Supported Features](https://docs.sharelogic.com/unifi/2.2/overview/supported-features.md): Details of the API models & integration features Unifi supports. - [Application Module Overview](https://docs.sharelogic.com/unifi/2.2/overview/application-module-overview.md): A quick overview of the Unifi Application and its modules. - [Outbound Incident Guide](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/2.2/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/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](https://docs.sharelogic.com/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](https://docs.sharelogic.com/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](https://docs.sharelogic.com/unifi/2.2/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](https://docs.sharelogic.com/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. - [Packager Feature Guide](https://docs.sharelogic.com/unifi/2.2/feature-guides/packager-feature-guide.md): This guide will demonstrate just how easy it is to package up all the elements of an integration so that it can be migrated between ServiceNow instances - 1-click easy! - [Instructions](https://docs.sharelogic.com/unifi/2.2/feature-guides/packager-feature-guide/instructions.md): Follow these instructions to Package your Integration, ready for migration between ServiceNow instances. - [Error Handling Tools Feature Guide](https://docs.sharelogic.com/unifi/2.2/feature-guides/error-handling-tools-feature-guide.md): Follow this guide to learn about the features built-in to Unifi which are designed specifically to help developers and administrators when debugging and error handling. - [Retry](https://docs.sharelogic.com/unifi/2.2/feature-guides/error-handling-tools-feature-guide/retry.md): Retry logic is configurable per Integration and controls how Unifi will automatically retry errored HTTP Requests. - [Replay](https://docs.sharelogic.com/unifi/2.2/feature-guides/error-handling-tools-feature-guide/replay.md): You can easily replay Requests and Transactions directly from the records themselves. This is an invaluable tool for debugging and error handling. - [Ignore](https://docs.sharelogic.com/unifi/2.2/feature-guides/error-handling-tools-feature-guide/ignore.md): Setting Transactions to Ignored stops the queue from processing. - [Repair](https://docs.sharelogic.com/unifi/2.2/feature-guides/error-handling-tools-feature-guide/repair.md): The Repair feature allows you to manually replay all Transactions on an Integration which are in either an Error or Timed Out state. - [Pause and Resume](https://docs.sharelogic.com/unifi/2.2/feature-guides/error-handling-tools-feature-guide/pause-and-resume.md): You can now Pause & Resume an Integration. This will cause Transactions to queue and then be processed in the order they were queued. - [Bonds](https://docs.sharelogic.com/unifi/2.2/bonding/bonds.md): Bonds store the data necessary to link your ServiceNow record to an external system. - [Bonded Attachments](https://docs.sharelogic.com/unifi/2.2/bonding/bonded-attachments.md): A Bonded Attachment is created for every synchronised attachment, storing relevant data. - [Transport Data Flow](https://docs.sharelogic.com/unifi/2.2/transport/transport-data-flow.md): An overview of the flow of data through Unifi's built in message bus. - [Transactions](https://docs.sharelogic.com/unifi/2.2/transport/transactions.md): A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests. - [Stages](https://docs.sharelogic.com/unifi/2.2/transport/stages.md): The Stage is the root staging table for all data mapping. Stages are created dynamically at the time of data being sent/received. The Staged Data fields will vary dependent on the data being sent. - [HTTP Requests](https://docs.sharelogic.com/unifi/2.2/transport/http-requests.md): Every request is handled and tracked by a HTTP Request record. - [Response Actions](https://docs.sharelogic.com/unifi/2.2/transport/response-actions.md): Response Actions are interceptors that allow you to customise the way responses are handled. - [Processes](https://docs.sharelogic.com/unifi/2.2/configuration/process.md): Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.). - [Integrations](https://docs.sharelogic.com/unifi/2.2/configuration/integrations.md): The Integration is where most configuration and settings are stored. - [Connections](https://docs.sharelogic.com/unifi/2.2/configuration/connections.md): Use Connections to manage all your environment details for each integration. - [Messages](https://docs.sharelogic.com/unifi/2.2/configuration/messages.md): A Message contains all the configuration required to send, receive, and process a request. - [Message Scripts](https://docs.sharelogic.com/unifi/2.2/configuration/message-scripts.md): Message Scripts are where the request processing and data mapping occurs. - [Fields](https://docs.sharelogic.com/unifi/2.2/configuration/fields.md): Field and Field Map configuration records are elements that simplify and bring additional functionality when configuring Messages & Message Scripts and facilitate the auto-generation of documentation. - [Field Maps](https://docs.sharelogic.com/unifi/2.2/configuration/field-maps.md): Field Maps define template code into which details from Field records are substituted. The resulting blocks of code are wrapped and compiled together into their nominated Message Scripts. - [Event Actions](https://docs.sharelogic.com/unifi/2.2/configuration/event-actions.md): Event Actions are a means of triggering an action from an event. - [Pollers](https://docs.sharelogic.com/unifi/2.2/polling/pollers.md): A Poller makes a scheduled request to a remote system. - [Poll Processors](https://docs.sharelogic.com/unifi/2.2/polling/poll-processors.md): Poll Processors are used to setup, execute and process Poll Requests. - [Poll Requests](https://docs.sharelogic.com/unifi/2.2/polling/poll-requests.md): Each Poll Request stores the details and outcomes of a scheduled poll. - [Large Response Payloads](https://docs.sharelogic.com/unifi/2.2/polling/large-response-payloads.md): If you're building a polling integration that has response payloads larger than 5MB then you'll need to save them as attachments and adapt your response processing. - [Activity Logs](https://docs.sharelogic.com/unifi/2.2/administration/activity-logs.md): The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day. - [Data Stores](https://docs.sharelogic.com/unifi/2.2/administration/data-stores.md): A Data Store is simply a key-value pair stored in the database that is available to all records in the system. - [Properties](https://docs.sharelogic.com/unifi/2.2/administration/properties.md): Global system settings for Unifi. - [Scheduled Scripts](https://docs.sharelogic.com/unifi/2.2/administration/scheduled-scripts.md): Scheduled Scripts are automatically created by the system to perform tasks. - [System Logs](https://docs.sharelogic.com/unifi/2.2/administration/system-logs.md): The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day. - [Self-test](https://docs.sharelogic.com/unifi/2.2/administration/self-test.md): A suite of internal tests that can be executed at any time. - [Variables](https://docs.sharelogic.com/unifi/2.2/scripting/variables.md): Here you will find a description of the variables that are available to you when scripting in Unifi. - [Snippets](https://docs.sharelogic.com/unifi/2.2/scripting/snippets.md): Useful snippets of code given as examples to help with various scripting needs. - [Attachment Handling](https://docs.sharelogic.com/unifi/2.2/attachments/attachment-handling.md): An overview of Attachment handling in Unifi. - [Multipart Form Data](https://docs.sharelogic.com/unifi/2.2/attachments/multipart-form-data.md): An overview of multipart/form-data generation in Unifi. ## 3.0 - [Unifi Documentation](https://docs.sharelogic.com/unifi/3.0/master.md): Welcome to the Unifi documentation space! Please take some time to read through the documentation as this will help you get the best out of the application. - [Unifi 3.0 Release Notes](https://docs.sharelogic.com/unifi/3.0/release/release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.2 Release Notes](https://docs.sharelogic.com/unifi/3.0/release/release-notes/2.2-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.1 Release Notes](https://docs.sharelogic.com/unifi/3.0/release/release-notes/2.1-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.0 Release Notes](https://docs.sharelogic.com/unifi/3.0/release/release-notes/2.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Hotfixes](https://docs.sharelogic.com/unifi/3.0/release/hotfixes.md): Unifi can be patched between releases by using a special Script Include called hotfix. This page contains any hotfixes that have been made for this version. Follow the instructions to apply them. - [Setup](https://docs.sharelogic.com/unifi/3.0/release/setup.md): The instructions on this page will enable you to get up and running with Unifi as quickly and efficiently as possible. - [Quick Tour](https://docs.sharelogic.com/unifi/3.0/overview/quick-tour.md): A high-level overview of the Unifi application. - [Supported Features](https://docs.sharelogic.com/unifi/3.0/overview/supported-features.md): Details of the API models & integration features Unifi supports. - [Application Modules](https://docs.sharelogic.com/unifi/3.0/overview/application-module-overview.md): A quick overview of the Unifi Application and its modules. - [Data Model](https://docs.sharelogic.com/unifi/3.0/overview/data-model.md): An overview of the table structure used by Unifi - [Outbound Incident Guide](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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. - [Create Scenario](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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. - [Trigger](https://docs.sharelogic.com/unifi/3.0/integration-guides/outbound-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/3.0/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/bidirectional-asynchronous-incident-guide/web-service.md): The entry point for a Process - there should be one endpoint per Process. Once connected, messages are guided to the Integration based on the unique combination of authentication user & endpoint. - [Integration](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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. - [Create Scenario](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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. - [Trigger](https://docs.sharelogic.com/unifi/3.0/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the Process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/3.0/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/test-resolveincident.md): Follow these steps to test the ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/3.0/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/incident-parent-and-child-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/3.0/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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 may also utilise all the previously configured Messages in testing our Integration. - [AddAttachmentInbound Message](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/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](https://docs.sharelogic.com/unifi/3.0/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md): Follow these instructions to test the outbound Message scenarios. - [Test CreateIncidentInbound](https://docs.sharelogic.com/unifi/3.0/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](https://docs.sharelogic.com/unifi/3.0/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/3.0/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](https://docs.sharelogic.com/unifi/3.0/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/3.0/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. - [Packager Feature Guide](https://docs.sharelogic.com/unifi/3.0/feature-guides/packager.md): This guide will demonstrate just how easy it is to package up all the elements of an integration so that it can be migrated between ServiceNow instances - 1-click easy! - [Instructions](https://docs.sharelogic.com/unifi/3.0/feature-guides/packager/instructions.md): Follow these instructions to Package your Integration, ready for migration between ServiceNow instances. - [Error Handling Tools Feature Guide](https://docs.sharelogic.com/unifi/3.0/feature-guides/error-handling-tools.md): Follow this guide to learn about the features built-in to Unifi which are designed specifically to help developers and administrators when debugging and error handling. - [Retry](https://docs.sharelogic.com/unifi/3.0/feature-guides/error-handling-tools/retry.md): Retry logic is configurable per Integration and controls how Unifi will automatically retry errored HTTP Requests. - [Replay](https://docs.sharelogic.com/unifi/3.0/feature-guides/error-handling-tools/replay.md): You can easily replay Requests and Transactions directly from the records themselves. This is an invaluable tool for debugging and error handling. - [Ignore](https://docs.sharelogic.com/unifi/3.0/feature-guides/error-handling-tools/ignore.md): Setting Transactions to Ignored stops the queue from processing. - [Repair](https://docs.sharelogic.com/unifi/3.0/feature-guides/error-handling-tools/repair.md): The Repair feature allows you to manually replay all Transactions on an Integration which are in either an Error or Timed Out state. - [Pause and Resume](https://docs.sharelogic.com/unifi/3.0/feature-guides/error-handling-tools/pause-and-resume.md): You can now Pause & Resume an Integration. This will cause Transactions to queue and then be processed in the order they were queued. - [Unifi Test Assistant Feature Guide](https://docs.sharelogic.com/unifi/3.0/feature-guides/unifi-test-assistant.md): Follow this guide to learn how to generate and run automated Integration Tests in Unifi. - [Generating Tests](https://docs.sharelogic.com/unifi/3.0/feature-guides/unifi-test-assistant/generating-tests.md): How to generate an automated Integration Test. - [Running Tests](https://docs.sharelogic.com/unifi/3.0/feature-guides/unifi-test-assistant/running-tests.md): How to run an automated Integration Test. - [Exploring Results](https://docs.sharelogic.com/unifi/3.0/feature-guides/unifi-test-assistant/exploring-results.md): How to navigate, view and interpret the results of an automated Integration Test. - [Bonds](https://docs.sharelogic.com/unifi/3.0/bonding/bonds.md): Bonds store the data necessary to link your ServiceNow record to an external system. - [Bonded Attachments](https://docs.sharelogic.com/unifi/3.0/bonding/bonded-attachments.md): A Bonded Attachment is created for every synchronised attachment, storing relevant data. - [Transport Data Flow](https://docs.sharelogic.com/unifi/3.0/transport/transport-data-flow.md): An overview of the flow of data through Unifi's built in message bus. - [Snapshots](https://docs.sharelogic.com/unifi/3.0/transport/snapshots.md): Whenever there is an update to a bonded record, Unifi will take a snapshot of it and capture it in a Snapshot record. The Snapshot is the key to facilitating automated Integration testing. - [Transactions](https://docs.sharelogic.com/unifi/3.0/transport/transactions.md): A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests. - [Stages](https://docs.sharelogic.com/unifi/3.0/transport/stages.md): The Stage is the root staging table for all data mapping. Stages are created dynamically at the time of data being sent/received. The Staged Data fields will vary dependent on the data being sent. - [HTTP Requests](https://docs.sharelogic.com/unifi/3.0/transport/http-requests.md): Every request is handled and tracked by a HTTP Request record. - [Processes](https://docs.sharelogic.com/unifi/3.0/configuration/process.md): Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.). - [Integrations](https://docs.sharelogic.com/unifi/3.0/configuration/integrations.md): The Integration is where most configuration and settings are stored. - [Connections](https://docs.sharelogic.com/unifi/3.0/configuration/connections.md): Use Connections to manage all your environment details for each integration. - [Messages](https://docs.sharelogic.com/unifi/3.0/configuration/messages.md): A Message contains all the configuration required to send, receive, and process a request. - [Message Scripts](https://docs.sharelogic.com/unifi/3.0/configuration/message-scripts.md): Message Scripts are where the request processing and data mapping occurs. - [Fields](https://docs.sharelogic.com/unifi/3.0/configuration/fields.md): Field and Field Map configuration records are elements that simplify and bring additional functionality when configuring Messages & Message Scripts and facilitate the auto-generation of documentation. - [Field Maps](https://docs.sharelogic.com/unifi/3.0/configuration/field-maps.md): Field Maps define template code into which details from Field records are substituted. The resulting blocks of code are wrapped and compiled together into their nominated Message Scripts. - [Response Actions](https://docs.sharelogic.com/unifi/3.0/configuration/response-actions.md): Response Actions are interceptors that allow you to customise the way responses are handled. - [Event Actions](https://docs.sharelogic.com/unifi/3.0/configuration/event-actions.md): Event Actions are a means of triggering an action from an event. - [Pollers](https://docs.sharelogic.com/unifi/3.0/polling/pollers.md): A Poller makes a scheduled request to a remote system. - [Poll Processors](https://docs.sharelogic.com/unifi/3.0/polling/poll-processors.md): Poll Processors are used to setup, execute and process Poll Requests. - [Poll Requests](https://docs.sharelogic.com/unifi/3.0/polling/poll-requests.md): Each Poll Request stores the details and outcomes of a scheduled poll. - [Large Response Payloads](https://docs.sharelogic.com/unifi/3.0/polling/large-response-payloads.md): If you're building a polling integration that has response payloads larger than 5MB then you'll need to save them as attachments and adapt your response processing. - [Integration Tests](https://docs.sharelogic.com/unifi/3.0/testing/integration-tests.md): Unifi can create an automated Integration Test which will capture and replay the Transaction scenarios from an existing Bond. - [Test Scenarios](https://docs.sharelogic.com/unifi/3.0/testing/test-scenarios.md): Integration Test Scenarios are the elements that make up an Integration Test. Each Scenario will correlate to the relevant Transaction on the Bond from which the test was created. - [Test Scenario Data](https://docs.sharelogic.com/unifi/3.0/testing/test-scenario-data.md): Test Scenario Data is a snapshot of all the relevant records created during the processing of a Transaction and is used to both generate the test and ascertain the results of each test run. - [Test Results](https://docs.sharelogic.com/unifi/3.0/testing/test-results.md): Whenever you run an Integration Test, the results are captured in an Integration Test Result record. - [Test Scenario Results](https://docs.sharelogic.com/unifi/3.0/testing/test-scenario-results.md): Whenever an Integration Test Scenario is run as part of an Integration Test, the results are captured in an Integration Test Scenario Result record. - [Activity Logs](https://docs.sharelogic.com/unifi/3.0/administration/activity-logs.md): The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day. - [Data Stores](https://docs.sharelogic.com/unifi/3.0/administration/data-stores.md): A Data Store is simply a key-value pair stored in the database that is available to all records in the system. - [Properties](https://docs.sharelogic.com/unifi/3.0/administration/properties.md): Global system settings for Unifi. - [Scheduled Scripts](https://docs.sharelogic.com/unifi/3.0/administration/scheduled-scripts.md): Scheduled Scripts are automatically created by the system to perform tasks. - [System Logs](https://docs.sharelogic.com/unifi/3.0/administration/system-logs.md): The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day. - [Self-test](https://docs.sharelogic.com/unifi/3.0/administration/self-test.md): A suite of internal tests that can be executed at any time. - [Variables](https://docs.sharelogic.com/unifi/3.0/scripting/variables.md): Here you will find a description of the variables that are available to you when scripting in Unifi. - [Snippets](https://docs.sharelogic.com/unifi/3.0/scripting/snippets.md): Useful snippets of code given as examples to help with various scripting needs. - [Attachment Handling](https://docs.sharelogic.com/unifi/3.0/attachments/attachment-handling.md): An overview of Attachment handling in Unifi. - [Multipart Form Data](https://docs.sharelogic.com/unifi/3.0/attachments/multipart-form-data.md): An overview of multipart/form-data generation in Unifi. ## 3.1 - [Unifi User Documentation](https://docs.sharelogic.com/unifi/3.1/master.md) - [Release Notes](https://docs.sharelogic.com/unifi/3.1/release/release-notes.md) - [Unifi 3.1 Release Notes](https://docs.sharelogic.com/unifi/3.1/release/release-notes/release-notes.md) - [Unifi 3.0 Release Notes](https://docs.sharelogic.com/unifi/3.1/release/release-notes/unifi-3.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.2 Release Notes](https://docs.sharelogic.com/unifi/3.1/release/release-notes/2.2-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.1 Release Notes](https://docs.sharelogic.com/unifi/3.1/release/release-notes/2.1-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.0 Release Notes](https://docs.sharelogic.com/unifi/3.1/release/release-notes/2.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Installation](https://docs.sharelogic.com/unifi/3.1/release/installation.md) - [Global Utility](https://docs.sharelogic.com/unifi/3.1/release/global-utility.md) - [Hotfix](https://docs.sharelogic.com/unifi/3.1/release/hotfixes.md) - [Quick Tour](https://docs.sharelogic.com/unifi/3.1/overview/quick-tour.md): A high-level overview of the Unifi application. - [Supported Features](https://docs.sharelogic.com/unifi/3.1/overview/supported-features.md): Details of the API models & integration features Unifi supports. - [Application Modules](https://docs.sharelogic.com/unifi/3.1/overview/application-module-overview.md): A quick overview of the Unifi Application and its modules. - [Data Model](https://docs.sharelogic.com/unifi/3.1/overview/data-model.md): An overview of the table structure used by Unifi - [Outbound Incident Guide](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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. - [Create Scenario](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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. - [Trigger](https://docs.sharelogic.com/unifi/3.1/integration-guides/outbound-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/3.1/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/bidirectional-asynchronous-incident-guide/web-service.md): The entry point for a Process - there should be one endpoint per Process. Once connected, messages are guided to the Integration based on the unique combination of authentication user & endpoint. - [Integration](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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. - [Create Scenario](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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. - [Trigger](https://docs.sharelogic.com/unifi/3.1/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the Process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/3.1/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/test-resolveincident.md): Follow these steps to test the ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-parent-and-child-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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 may also utilise all the previously configured Messages in testing our Integration. - [AddAttachmentInbound Message](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/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](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md): Follow these instructions to test the outbound Message scenarios. - [Test CreateIncidentInbound](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](https://docs.sharelogic.com/unifi/3.1/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/3.1/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. - [Packager Feature Guide](https://docs.sharelogic.com/unifi/3.1/feature-guides/packager.md): This guide will demonstrate just how easy it is to package up all the elements of an integration so that it can be migrated between ServiceNow instances - 1-click easy! - [Instructions](https://docs.sharelogic.com/unifi/3.1/feature-guides/packager/instructions.md): Follow these instructions to Package your Integration, ready for migration between ServiceNow instances. - [Error Handling Tools Feature Guide](https://docs.sharelogic.com/unifi/3.1/feature-guides/error-handling-tools.md): Follow this guide to learn about the features built-in to Unifi which are designed specifically to help developers and administrators when debugging and error handling. - [Retry](https://docs.sharelogic.com/unifi/3.1/feature-guides/error-handling-tools/retry.md): Retry logic is configurable per Integration and controls how Unifi will automatically retry errored HTTP Requests. - [Replay](https://docs.sharelogic.com/unifi/3.1/feature-guides/error-handling-tools/replay.md): You can easily replay Requests and Transactions directly from the records themselves. This is an invaluable tool for debugging and error handling. - [Ignore](https://docs.sharelogic.com/unifi/3.1/feature-guides/error-handling-tools/ignore.md): Setting Transactions to Ignored stops the queue from processing. - [Repair](https://docs.sharelogic.com/unifi/3.1/feature-guides/error-handling-tools/repair.md): The Repair feature allows you to manually replay all Transactions on an Integration which are in either an Error or Timed Out state. - [Pause and Resume](https://docs.sharelogic.com/unifi/3.1/feature-guides/error-handling-tools/pause-and-resume.md): You can now Pause & Resume an Integration. This will cause Transactions to queue and then be processed in the order they were queued. - [Unifi Test Assistant Feature Guide](https://docs.sharelogic.com/unifi/3.1/feature-guides/unifi-test-assistant.md): Follow this guide to learn how to generate and run automated Integration Tests in Unifi. - [Generating Tests](https://docs.sharelogic.com/unifi/3.1/feature-guides/unifi-test-assistant/generating-tests.md): How to generate an automated Integration Test. - [Running Tests](https://docs.sharelogic.com/unifi/3.1/feature-guides/unifi-test-assistant/running-tests.md): How to run an automated Integration Test. - [Exploring Results](https://docs.sharelogic.com/unifi/3.1/feature-guides/unifi-test-assistant/exploring-results.md): How to navigate, view and interpret the results of an automated Integration Test. - [How to Handle Attachments](https://docs.sharelogic.com/unifi/3.1/how-to-guides/how-to-handle-attachments.md): Follow this guide to learn how to configure a dedicated Message in Unifi to handle streamed attachments. - [Message](https://docs.sharelogic.com/unifi/3.1/how-to-guides/how-to-handle-attachments/message.md): The AddAttachment Message will be used to process inbound and outbound attachments. - [Scripted REST Resource](https://docs.sharelogic.com/unifi/3.1/how-to-guides/how-to-handle-attachments/scripted-rest-resource.md): Unifi will automatically generate the Scripted REST Resource to cater for inbound streaming. If using a Resource created on a release prior to v3.0 this will need to be updated manually. - [Test AddAttachment](https://docs.sharelogic.com/unifi/3.1/how-to-guides/how-to-handle-attachments/test-addattachment.md): Follow these steps to test the AddAttachment Message. - [How to Setup an OAuth Connection](https://docs.sharelogic.com/unifi/3.1/how-to-guides/how-to-setup-an-oauth-connection.md): Follow this guide to learn how to setup an OAuth Connection in Unifi. - [Identity Provider Instance](https://docs.sharelogic.com/unifi/3.1/how-to-guides/how-to-setup-an-oauth-connection/identity-provider-instance.md): These are the configuration changes to be made in the identity provider instance when setting up an OAuth Connection. - [Identity Consumer Instance](https://docs.sharelogic.com/unifi/3.1/how-to-guides/how-to-setup-an-oauth-connection/identity-consumer-instance.md): These are the configuration changes to be made in the identity consumer instance when setting up an OAuth Connection. - [Bonds](https://docs.sharelogic.com/unifi/3.1/bonding/bonds.md): Bonds store the data necessary to link your ServiceNow record to an external system. - [Bonded Attachments](https://docs.sharelogic.com/unifi/3.1/bonding/bonded-attachments.md): A Bonded Attachment is created for every synchronised attachment, storing relevant data. - [Transport Data Flow](https://docs.sharelogic.com/unifi/3.1/transport/transport-data-flow.md): An overview of the flow of data through Unifi's built in message bus. - [Snapshots](https://docs.sharelogic.com/unifi/3.1/transport/snapshots.md): Whenever there is an update to a bonded record, Unifi will take a snapshot of it and capture it in a Snapshot record. The Snapshot is the key to facilitating automated Integration testing. - [Transactions](https://docs.sharelogic.com/unifi/3.1/transport/transactions.md): A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests. - [Stages](https://docs.sharelogic.com/unifi/3.1/transport/stages.md): The Stage is the root staging table for all data mapping. Stages are created dynamically at the time of data being sent/received. The Staged Data fields will vary dependent on the data being sent. - [HTTP Requests](https://docs.sharelogic.com/unifi/3.1/transport/http-requests.md): Every request is handled and tracked by a HTTP Request record. - [Processes](https://docs.sharelogic.com/unifi/3.1/configuration/process.md): Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.). - [Integrations](https://docs.sharelogic.com/unifi/3.1/configuration/integrations.md): The Integration is where most configuration and settings are stored. - [Connections](https://docs.sharelogic.com/unifi/3.1/configuration/connections.md): Use Connections to manage all your environment details for each integration. - [Messages](https://docs.sharelogic.com/unifi/3.1/configuration/messages.md): A Message contains all the configuration required to send, receive, and process a request. - [Message Scripts](https://docs.sharelogic.com/unifi/3.1/configuration/message-scripts.md): Message Scripts are where the request processing and data mapping occurs. - [Fields](https://docs.sharelogic.com/unifi/3.1/configuration/fields.md): Field and Field Map configuration records are elements that simplify and bring additional functionality when configuring Messages & Message Scripts and facilitate the auto-generation of documentation. - [Field Maps](https://docs.sharelogic.com/unifi/3.1/configuration/field-maps.md): Field Maps define template code into which details from Field records are substituted. The resulting blocks of code are wrapped and compiled together into their nominated Message Scripts. - [Response Actions](https://docs.sharelogic.com/unifi/3.1/configuration/response-actions.md): Response Actions are interceptors that allow you to customise the way responses are handled. - [Event Actions](https://docs.sharelogic.com/unifi/3.1/configuration/event-actions.md): Event Actions are a means of triggering an action from an event. - [Pollers](https://docs.sharelogic.com/unifi/3.1/polling/pollers.md): A Poller makes a scheduled request to a remote system. - [Poll Processors](https://docs.sharelogic.com/unifi/3.1/polling/poll-processors.md): Poll Processors are used to setup, execute and process Poll Requests. - [Poll Requests](https://docs.sharelogic.com/unifi/3.1/polling/poll-requests.md): Each Poll Request stores the details and outcomes of a scheduled poll. - [Large Response Payloads](https://docs.sharelogic.com/unifi/3.1/polling/large-response-payloads.md): If you're building a polling integration that has response payloads larger than 5MB then you'll need to save them as attachments and adapt your response processing. - [Integration Tests](https://docs.sharelogic.com/unifi/3.1/testing/integration-tests.md): Unifi can create an automated Integration Test which will capture and replay the Transaction scenarios from an existing Bond. - [Test Scenarios](https://docs.sharelogic.com/unifi/3.1/testing/test-scenarios.md): Integration Test Scenarios are the elements that make up an Integration Test. Each Scenario will correlate to the relevant Transaction on the Bond from which the test was created. - [Test Scenario Data](https://docs.sharelogic.com/unifi/3.1/testing/test-scenario-data.md): Test Scenario Data is a snapshot of all the relevant records created during the processing of a Transaction and is used to both generate the test and ascertain the results of each test run. - [Test Results](https://docs.sharelogic.com/unifi/3.1/testing/test-results.md): Whenever you run an Integration Test, the results are captured in an Integration Test Result record. - [Test Scenario Results](https://docs.sharelogic.com/unifi/3.1/testing/test-scenario-results.md): Whenever an Integration Test Scenario is run as part of an Integration Test, the results are captured in an Integration Test Scenario Result record. - [Activity Logs](https://docs.sharelogic.com/unifi/3.1/administration/activity-logs.md): The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day. - [Data Stores](https://docs.sharelogic.com/unifi/3.1/administration/data-stores.md): A Data Store is simply a key-value pair stored in the database that is available to all records in the system. - [Properties](https://docs.sharelogic.com/unifi/3.1/administration/properties.md): Global system settings for Unifi. - [Scheduled Scripts](https://docs.sharelogic.com/unifi/3.1/administration/scheduled-scripts.md): Scheduled Scripts are automatically created by the system to perform tasks. - [System Logs](https://docs.sharelogic.com/unifi/3.1/administration/system-logs.md): The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day. - [Self-test](https://docs.sharelogic.com/unifi/3.1/administration/self-test.md): A suite of internal tests that can be executed at any time. - [Variables](https://docs.sharelogic.com/unifi/3.1/scripting/variables.md): Here you will find a description of the variables that are available to you when scripting in Unifi. - [Snippets](https://docs.sharelogic.com/unifi/3.1/scripting/snippets.md): Useful snippets of code given as examples to help with various scripting needs. - [Attachments](https://docs.sharelogic.com/unifi/3.1/troubleshooting/attachments.md) - [New record attachments are not sent from Portal](https://docs.sharelogic.com/unifi/3.1/troubleshooting/attachments/new-record-attachments-are-not-sent-from-portal.md) - [Embedded attachments not being sent](https://docs.sharelogic.com/unifi/3.1/troubleshooting/attachments/embedded-attachments-not-being-sent.md) - [Special characters in attachment file names](https://docs.sharelogic.com/unifi/3.1/troubleshooting/attachments/special-characters-in-attachment-file-names.md) - [Development](https://docs.sharelogic.com/unifi/3.1/troubleshooting/development.md) - [Bonding to existing records](https://docs.sharelogic.com/unifi/3.1/troubleshooting/development/bonding-to-existing-records.md) - [Copying an existing Unifi trigger rule doesn't work](https://docs.sharelogic.com/unifi/3.1/troubleshooting/development/copying-an-existing-unifi-trigger-rule-doesnt-work.md) - [Duplicate messages being sent](https://docs.sharelogic.com/unifi/3.1/troubleshooting/development/duplicate-messages-being-sent.md) - [Deleted records are not packaged](https://docs.sharelogic.com/unifi/3.1/troubleshooting/development/deleted-records-are-not-packaged.md) - [Multipart Form Data](https://docs.sharelogic.com/unifi/3.1/troubleshooting/development/multipart-form-data.md): An overview of multipart/form-data generation in Unifi. - [Undefined error when building an integration](https://docs.sharelogic.com/unifi/3.1/troubleshooting/development/undefined-error-when-building-an-integration.md) - [Installation](https://docs.sharelogic.com/unifi/3.1/troubleshooting/installation.md) - [Latest version of Unifi not accessible](https://docs.sharelogic.com/unifi/3.1/troubleshooting/installation/latest-version-of-unifi-not-accessible.md) - [Integration Responses](https://docs.sharelogic.com/unifi/3.1/troubleshooting/integration-responses.md) - [Transaction has been processed already](https://docs.sharelogic.com/unifi/3.1/troubleshooting/integration-responses/transaction-has-been-processed-already.md) - [Initiating transaction not found for inbound receipt](https://docs.sharelogic.com/unifi/3.1/troubleshooting/integration-responses/initiating-transaction-not-found-for-inbound-receipt.md) - [Message has already been processed](https://docs.sharelogic.com/unifi/3.1/troubleshooting/integration-responses/message-has-already-been-processed.md) - [Message ID not found](https://docs.sharelogic.com/unifi/3.1/troubleshooting/integration-responses/message-id-not-found.md) - [Message is not valid for this bond](https://docs.sharelogic.com/unifi/3.1/troubleshooting/integration-responses/message-is-not-valid-for-this-bond.md) - [Message name not recognised](https://docs.sharelogic.com/unifi/3.1/troubleshooting/integration-responses/message-name-not-recognised.md) - [Unable to identify message name from request](https://docs.sharelogic.com/unifi/3.1/troubleshooting/integration-responses/unable-to-identify-message-name-from-request.md) - [Other](https://docs.sharelogic.com/unifi/3.1/troubleshooting/other.md) - [Dynamic stage does not render](https://docs.sharelogic.com/unifi/3.1/troubleshooting/other/dynamic-stage-does-not-render.md) ## 4.0 - [Unifi User Documentation](https://docs.sharelogic.com/unifi/4.0/readme.md) - [Release Notes](https://docs.sharelogic.com/unifi/4.0/install/release-notes.md) - [Unifi 4.0 Release Notes](https://docs.sharelogic.com/unifi/4.0/install/release-notes/unifi-4.0-release-notes.md): Release date: 12 September, 2022 - [Unifi 3.1 Release Notes](https://docs.sharelogic.com/unifi/4.0/install/release-notes/unifi-3.1-release-notes.md) - [Unifi 3.0 Release Notes](https://docs.sharelogic.com/unifi/4.0/install/release-notes/unifi-3.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.2 Release Notes](https://docs.sharelogic.com/unifi/4.0/install/release-notes/2.2-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.1 Release Notes](https://docs.sharelogic.com/unifi/4.0/install/release-notes/2.1-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.0 Release Notes](https://docs.sharelogic.com/unifi/4.0/install/release-notes/2.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Install or Upgrade](https://docs.sharelogic.com/unifi/4.0/install/installation.md) - [Global Utility](https://docs.sharelogic.com/unifi/4.0/install/installation/global-utility.md) - [Hotfix](https://docs.sharelogic.com/unifi/4.0/install/installation/hotfixes.md) - [Integration Designer](https://docs.sharelogic.com/unifi/4.0/configure/integration-designer.md) - [Processes](https://docs.sharelogic.com/unifi/4.0/configure/process.md): Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.). - [Integrations](https://docs.sharelogic.com/unifi/4.0/configure/integrations.md): The Integration is where most configuration and settings are stored. - [Connections](https://docs.sharelogic.com/unifi/4.0/configure/connections.md): Use Connections to manage all your environment details for each integration. - [Messages](https://docs.sharelogic.com/unifi/4.0/configure/messages.md): A Message contains all the configuration required to send, receive, and process a request. - [Message Scripts](https://docs.sharelogic.com/unifi/4.0/configure/message-scripts.md): Message Scripts are where the request processing and data mapping occurs. - [Fields](https://docs.sharelogic.com/unifi/4.0/configure/fields.md): Field and Field Map configuration records are elements that simplify and bring additional functionality when configuring Messages & Message Scripts and facilitate the auto-generation of documentation. - [Field Maps](https://docs.sharelogic.com/unifi/4.0/configure/field-maps.md): Field Maps define template code into which details from Field records are substituted. The resulting blocks of code are wrapped and compiled together into their nominated Message Scripts. - [Response Actions](https://docs.sharelogic.com/unifi/4.0/configure/response-actions.md): Response Actions are interceptors that allow you to customise the way responses are handled. - [Event Actions](https://docs.sharelogic.com/unifi/4.0/configure/event-actions.md): Event Actions are a means of triggering an action from an event. - [Datasets](https://docs.sharelogic.com/unifi/4.0/configure/datasets.md) - [Create a New Dataset](https://docs.sharelogic.com/unifi/4.0/configure/datasets/create-a-new-dataset.md) - [Dataset Extras](https://docs.sharelogic.com/unifi/4.0/configure/datasets/dataset-extras.md) - [Polling](https://docs.sharelogic.com/unifi/4.0/configure/polling.md) - [Pollers](https://docs.sharelogic.com/unifi/4.0/configure/polling/pollers.md): A Poller makes a scheduled request to a remote system. - [Poll Processors](https://docs.sharelogic.com/unifi/4.0/configure/polling/poll-processors.md): Poll Processors are used to setup, execute and process Poll Requests. - [Administration](https://docs.sharelogic.com/unifi/4.0/configure/administration.md) - [Activity Logs](https://docs.sharelogic.com/unifi/4.0/configure/administration/activity-logs.md): The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day. - [Data Stores](https://docs.sharelogic.com/unifi/4.0/configure/administration/data-stores.md): A Data Store is simply a key-value pair stored in the database that is available to all records in the system. - [Properties](https://docs.sharelogic.com/unifi/4.0/configure/administration/properties.md): Global system settings for Unifi. - [Scheduled Scripts](https://docs.sharelogic.com/unifi/4.0/configure/administration/scheduled-scripts.md): Scheduled Scripts are automatically created by the system to perform tasks. - [System Logs](https://docs.sharelogic.com/unifi/4.0/configure/administration/system-logs.md): The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day. - [Attachments](https://docs.sharelogic.com/unifi/4.0/configure/attachments.md) - [Extracting Attachments](https://docs.sharelogic.com/unifi/4.0/configure/attachments/extracting-attachments.md) - [Fetching Attachments](https://docs.sharelogic.com/unifi/4.0/configure/attachments/fetching-attachments.md) - [Embedded Attachments](https://docs.sharelogic.com/unifi/4.0/configure/attachments/embedded-attachments.md) - [Scripting](https://docs.sharelogic.com/unifi/4.0/configure/scripting.md) - [Snippets](https://docs.sharelogic.com/unifi/4.0/configure/scripting/snippets.md): Useful snippets of code given as examples to help with various scripting needs. - [Variables](https://docs.sharelogic.com/unifi/4.0/configure/scripting/variables.md): Here you will find a description of the variables that are available to you when scripting in Unifi. - [Documentation](https://docs.sharelogic.com/unifi/4.0/configure/documentation.md) - [How to guides](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides.md) - [How to Handle Attachments](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/how-to-handle-attachments.md): Follow this guide to learn how to configure a dedicated Message in Unifi to handle streamed attachments. - [Message](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/how-to-handle-attachments/message.md): The AddAttachment Message will be used to process inbound and outbound attachments. - [Scripted REST Resource](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/how-to-handle-attachments/scripted-rest-resource.md): Unifi will automatically generate the Scripted REST Resource to cater for inbound streaming. If using a Resource created on a release prior to v3.0 this will need to be updated manually. - [Test AddAttachment](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/how-to-handle-attachments/test-addattachment.md): Follow these steps to test the AddAttachment Message. - [How to Manually Close a Bond](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/how-to-manually-close-a-bond.md) - [How to Poll for Large Response Payloads](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/large-response-payloads.md): If you're building a polling integration that has response payloads larger than 5MB then you'll need to save them as attachments and adapt your response processing. - [How to Setup an OAuth Connection](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/how-to-setup-an-oauth-connection.md): Follow this guide to learn how to setup an OAuth Connection in Unifi. - [Identity Provider Instance](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-provider-instance.md): These are the configuration changes to be made in the identity provider instance when setting up an OAuth Connection. - [Identity Consumer Instance](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-consumer-instance.md): These are the configuration changes to be made in the identity consumer instance when setting up an OAuth Connection. - [How to Setup Heartbeat Messages](https://docs.sharelogic.com/unifi/4.0/configure/how-to-guides/how-to-setup-heartbeat-messages.md) - [Package](https://docs.sharelogic.com/unifi/4.0/deploy/package.md): Follow these instructions to Package your Integration, ready for migration between ServiceNow instances. - [Instance Clone](https://docs.sharelogic.com/unifi/4.0/deploy/cloning.md) - [Bonding](https://docs.sharelogic.com/unifi/4.0/operate/bonding.md) - [Bonds](https://docs.sharelogic.com/unifi/4.0/operate/bonding/bonds.md): Bonds store the data necessary to link your ServiceNow record to an external system. - [Bonded Attachments](https://docs.sharelogic.com/unifi/4.0/operate/bonding/bonded-attachments.md): A Bonded Attachment is created for every synchronised attachment, storing relevant data. - [Transport](https://docs.sharelogic.com/unifi/4.0/operate/transport.md) - [Snapshots](https://docs.sharelogic.com/unifi/4.0/operate/transport/snapshots.md): Whenever there is an update to a bonded record, Unifi will take a snapshot of it and capture it in a Snapshot record. The Snapshot is the key to facilitating automated Integration testing. - [Transactions](https://docs.sharelogic.com/unifi/4.0/operate/transport/transactions.md): A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests. - [Stages](https://docs.sharelogic.com/unifi/4.0/operate/transport/stages.md): The Stage is the root staging table for all data mapping. Stages are created dynamically at the time of data being sent/received. The Staged Data fields will vary dependent on the data being sent. - [HTTP Requests](https://docs.sharelogic.com/unifi/4.0/operate/transport/http-requests.md): Every request is handled and tracked by a HTTP Request record. - [Dataset Requests](https://docs.sharelogic.com/unifi/4.0/operate/transport/dataset-requests.md): Each Dataset Request stores the details and outcomes of a dataset import or export. - [Poll Requests](https://docs.sharelogic.com/unifi/4.0/operate/transport/poll-requests.md): Each Poll Request stores the details and outcomes of a scheduled poll. - [Error Handling](https://docs.sharelogic.com/unifi/4.0/operate/error-handling.md) - [Integration Pause and Resume](https://docs.sharelogic.com/unifi/4.0/operate/error-handling/pause-and-resume.md): You can now Pause & Resume an Integration. This will cause Transactions to queue and then be processed in the order they were queued. - [Integration Repair](https://docs.sharelogic.com/unifi/4.0/operate/error-handling/repair.md): The Repair feature allows you to manually replay all Transactions on an Integration which are in either an Error or Timed Out state. - [Request Retry](https://docs.sharelogic.com/unifi/4.0/operate/error-handling/retry.md): Retry logic is configurable per Integration and controls how Unifi will automatically retry errored HTTP Requests. - [Transaction & Request Replay](https://docs.sharelogic.com/unifi/4.0/operate/error-handling/replay.md): You can easily replay Requests and Transactions directly from the records themselves. This is an invaluable tool for debugging and error handling. - [Transaction Ignore](https://docs.sharelogic.com/unifi/4.0/operate/error-handling/ignore.md): Setting Transactions to Ignored stops the queue from processing. - [Overview](https://docs.sharelogic.com/unifi/4.0/test/overview.md): Follow this guide to learn how to generate and run automated Integration Tests in Unifi. - [Integration Test](https://docs.sharelogic.com/unifi/4.0/test/integration-tests.md): Unifi can create an automated Integration Test which will capture and replay the Transaction scenarios from an existing Bond. - [Test Scenario](https://docs.sharelogic.com/unifi/4.0/test/test-scenarios.md): Integration Test Scenarios are the elements that make up an Integration Test. Each Scenario will correlate to the relevant Transaction on the Bond from which the test was created. - [Test Scenario Data](https://docs.sharelogic.com/unifi/4.0/test/test-scenario-data.md): Test Scenario Data is a snapshot of all the relevant records created during the processing of a Transaction and is used to both generate the test and ascertain the results of each test run. - [Test Result](https://docs.sharelogic.com/unifi/4.0/test/test-results.md): Whenever you run an Integration Test, the results are captured in an Integration Test Result record. - [Test Scenario Result](https://docs.sharelogic.com/unifi/4.0/test/test-scenario-results.md): Whenever an Integration Test Scenario is run as part of an Integration Test, the results are captured in an Integration Test Scenario Result record. - [Generating Tests](https://docs.sharelogic.com/unifi/4.0/test/generating-tests.md): How to generate an automated Integration Test. - [Running Tests](https://docs.sharelogic.com/unifi/4.0/test/running-tests.md): How to run an automated Integration Test. - [Exploring Results](https://docs.sharelogic.com/unifi/4.0/test/exploring-results.md): How to navigate, view and interpret the results of an automated Integration Test. - [Outbound Incident Guide](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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. - [Trigger](https://docs.sharelogic.com/unifi/4.0/integration-guides/outbound-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.0/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/bidirectional-asynchronous-incident-guide/web-service.md): The entry point for a Process - there should be one endpoint per Process. Once connected, messages are guided to the Integration based on the unique combination of authentication user & endpoint. - [Integration](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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. - [Trigger](https://docs.sharelogic.com/unifi/4.0/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the Process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.0/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/test-resolveincident.md): Follow these steps to test the ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.0/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/incident-parent-and-child-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.0/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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 may also utilise all the previously configured Messages in testing our Integration. - [AddAttachmentInbound Message](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/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](https://docs.sharelogic.com/unifi/4.0/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md): Follow these instructions to test the outbound Message scenarios. - [Test CreateIncidentInbound](https://docs.sharelogic.com/unifi/4.0/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](https://docs.sharelogic.com/unifi/4.0/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.0/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](https://docs.sharelogic.com/unifi/4.0/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.0/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. - [Attachments](https://docs.sharelogic.com/unifi/4.0/troubleshooting/attachments.md) - [Inbound SOAP/Base64 attachments stopped working](https://docs.sharelogic.com/unifi/4.0/troubleshooting/attachments/embedded-attachments-not-being-sent.md) - [New record attachments are not sent from Portal](https://docs.sharelogic.com/unifi/4.0/troubleshooting/attachments/new-record-attachments-are-not-sent-from-portal.md) - [Special characters in attachment file names](https://docs.sharelogic.com/unifi/4.0/troubleshooting/attachments/special-characters-in-attachment-file-names.md) - [Datasets](https://docs.sharelogic.com/unifi/4.0/troubleshooting/datasets.md) - [Development](https://docs.sharelogic.com/unifi/4.0/troubleshooting/development.md) - [Bonding to existing records](https://docs.sharelogic.com/unifi/4.0/troubleshooting/development/bonding-to-existing-records.md) - [Copying an existing Unifi trigger rule doesn't work](https://docs.sharelogic.com/unifi/4.0/troubleshooting/development/copying-an-existing-unifi-trigger-rule-doesnt-work.md) - [Duplicate messages being sent](https://docs.sharelogic.com/unifi/4.0/troubleshooting/development/duplicate-messages-being-sent.md) - [Deleted records are not packaged](https://docs.sharelogic.com/unifi/4.0/troubleshooting/development/deleted-records-are-not-packaged.md) - [Multipart Form Data](https://docs.sharelogic.com/unifi/4.0/troubleshooting/development/multipart-form-data.md): An overview of multipart/form-data generation in Unifi. - [Undefined error when building an integration](https://docs.sharelogic.com/unifi/4.0/troubleshooting/development/undefined-error-when-building-an-integration.md) - [Diagnostic](https://docs.sharelogic.com/unifi/4.0/troubleshooting/diagnostic.md) - [Installation](https://docs.sharelogic.com/unifi/4.0/troubleshooting/installation.md) - [Latest version of Unifi not accessible](https://docs.sharelogic.com/unifi/4.0/troubleshooting/installation/latest-version-of-unifi-not-accessible.md) - [Integration Responses](https://docs.sharelogic.com/unifi/4.0/troubleshooting/integration-responses.md) - [Transaction has been processed already](https://docs.sharelogic.com/unifi/4.0/troubleshooting/integration-responses/transaction-has-been-processed-already.md) - [Initiating transaction not found for inbound receipt](https://docs.sharelogic.com/unifi/4.0/troubleshooting/integration-responses/initiating-transaction-not-found-for-inbound-receipt.md) - [Message has already been processed](https://docs.sharelogic.com/unifi/4.0/troubleshooting/integration-responses/message-has-already-been-processed.md) - [Message ID not found](https://docs.sharelogic.com/unifi/4.0/troubleshooting/integration-responses/message-id-not-found.md) - [Message is not valid for this bond](https://docs.sharelogic.com/unifi/4.0/troubleshooting/integration-responses/message-is-not-valid-for-this-bond.md) - [Message name not recognised](https://docs.sharelogic.com/unifi/4.0/troubleshooting/integration-responses/message-name-not-recognised.md) - [No retry for requests with 401 response](https://docs.sharelogic.com/unifi/4.0/troubleshooting/integration-responses/no-retry-for-requests-with-401-response.md) - [Unable to identify message name from request](https://docs.sharelogic.com/unifi/4.0/troubleshooting/integration-responses/unable-to-identify-message-name-from-request.md) - [Other](https://docs.sharelogic.com/unifi/4.0/troubleshooting/other.md) - [Dynamic stage does not render](https://docs.sharelogic.com/unifi/4.0/troubleshooting/other/dynamic-stage-does-not-render.md) - [Duplicate bonds on Request integrations](https://docs.sharelogic.com/unifi/4.0/troubleshooting/other/duplicate-bonds-on-request-integrations.md) - [Self-test](https://docs.sharelogic.com/unifi/4.0/troubleshooting/self-test.md): A suite of internal tests that can be executed at any time. - [Quick Tour](https://docs.sharelogic.com/unifi/4.0/about/quick-tour.md): A high-level overview of the Unifi application. - [Supported Features](https://docs.sharelogic.com/unifi/4.0/about/supported-features.md): Details of the API models & integration features Unifi supports. - [Application Modules](https://docs.sharelogic.com/unifi/4.0/about/application-module-overview.md): A quick overview of the Unifi Application and its modules. - [Data Model](https://docs.sharelogic.com/unifi/4.0/about/data-model.md): An overview of the table structure used by Unifi - [Transport Data Flow](https://docs.sharelogic.com/unifi/4.0/about/transport-data-flow.md): An overview of the flow of data through Unifi's built in message bus. ## 4.1 - [Unifi User Documentation](https://docs.sharelogic.com/unifi/4.1/readme.md) - [Release Notes](https://docs.sharelogic.com/unifi/4.1/install/release-notes.md) - [Unifi 4.1 Release Notes](https://docs.sharelogic.com/unifi/4.1/install/release-notes/unifi-4.1-release-notes.md): Release date: 17 November, 2023 - [Unifi 4.0 Release Notes](https://docs.sharelogic.com/unifi/4.1/install/release-notes/unifi-4.0-release-notes.md): Release date: 12 September, 2022 - [Unifi 3.1 Release Notes](https://docs.sharelogic.com/unifi/4.1/install/release-notes/unifi-3.1-release-notes.md) - [Unifi 3.0 Release Notes](https://docs.sharelogic.com/unifi/4.1/install/release-notes/unifi-3.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.2 Release Notes](https://docs.sharelogic.com/unifi/4.1/install/release-notes/2.2-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.1 Release Notes](https://docs.sharelogic.com/unifi/4.1/install/release-notes/2.1-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.0 Release Notes](https://docs.sharelogic.com/unifi/4.1/install/release-notes/2.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Install or Upgrade](https://docs.sharelogic.com/unifi/4.1/install/installation.md) - [Global Utility](https://docs.sharelogic.com/unifi/4.1/install/installation/global-utility.md) - [Hotfix](https://docs.sharelogic.com/unifi/4.1/install/installation/hotfixes.md) - [Integration Designer](https://docs.sharelogic.com/unifi/4.1/configure/integration-designer.md) - [Processes](https://docs.sharelogic.com/unifi/4.1/configure/process.md): Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.). - [Integrations](https://docs.sharelogic.com/unifi/4.1/configure/integrations.md): The Integration is where most configuration and settings are stored. - [Connections](https://docs.sharelogic.com/unifi/4.1/configure/connections.md): Use Connections to manage all your environment details for each integration. - [Messages](https://docs.sharelogic.com/unifi/4.1/configure/messages.md): A Message contains all the configuration required to send, receive, and process a request. - [Message Scripts](https://docs.sharelogic.com/unifi/4.1/configure/message-scripts.md): Message Scripts are where the request processing and data mapping occurs. - [Fields](https://docs.sharelogic.com/unifi/4.1/configure/fields.md): Field and Field Map configuration records are elements that simplify and bring additional functionality when configuring Messages & Message Scripts and facilitate the auto-generation of documentation. - [Field Maps](https://docs.sharelogic.com/unifi/4.1/configure/field-maps.md): Field Maps define template code into which details from Field records are substituted. The resulting blocks of code are wrapped and compiled together into their nominated Message Scripts. - [Response Actions](https://docs.sharelogic.com/unifi/4.1/configure/response-actions.md): Response Actions are interceptors that allow you to customise the way responses are handled. - [Event Actions](https://docs.sharelogic.com/unifi/4.1/configure/event-actions.md): Event Actions are a means of triggering an action from an event. - [Datasets](https://docs.sharelogic.com/unifi/4.1/configure/datasets.md) - [Create a New Dataset](https://docs.sharelogic.com/unifi/4.1/configure/datasets/create-a-new-dataset.md) - [Dataset Extras](https://docs.sharelogic.com/unifi/4.1/configure/datasets/dataset-extras.md) - [Polling](https://docs.sharelogic.com/unifi/4.1/configure/polling.md) - [Pollers](https://docs.sharelogic.com/unifi/4.1/configure/polling/pollers.md): A Poller makes a scheduled request to a remote system. - [Poll Processors](https://docs.sharelogic.com/unifi/4.1/configure/polling/poll-processors.md): Poll Processors are used to setup, execute and process Poll Requests. - [Administration](https://docs.sharelogic.com/unifi/4.1/configure/administration.md) - [Activity Logs](https://docs.sharelogic.com/unifi/4.1/configure/administration/activity-logs.md): The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day. - [Data Stores](https://docs.sharelogic.com/unifi/4.1/configure/administration/data-stores.md): A Data Store is simply a key-value pair stored in the database that is available to all records in the system. - [Properties](https://docs.sharelogic.com/unifi/4.1/configure/administration/properties.md): Global system settings for Unifi. - [Scheduled Scripts](https://docs.sharelogic.com/unifi/4.1/configure/administration/scheduled-scripts.md): Scheduled Scripts are automatically created by the system to perform tasks. - [System Logs](https://docs.sharelogic.com/unifi/4.1/configure/administration/system-logs.md): The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day. - [Attachments](https://docs.sharelogic.com/unifi/4.1/configure/attachments.md) - [Extracting Attachments](https://docs.sharelogic.com/unifi/4.1/configure/attachments/extracting-attachments.md) - [Fetching Attachments](https://docs.sharelogic.com/unifi/4.1/configure/attachments/fetching-attachments.md) - [Embedded Attachments](https://docs.sharelogic.com/unifi/4.1/configure/attachments/embedded-attachments.md) - [Scripting](https://docs.sharelogic.com/unifi/4.1/configure/scripting.md) - [Snippets](https://docs.sharelogic.com/unifi/4.1/configure/scripting/snippets.md): Useful snippets of code given as examples to help with various scripting needs. - [Variables](https://docs.sharelogic.com/unifi/4.1/configure/scripting/variables.md): Here you will find a description of the variables that are available to you when scripting in Unifi. - [Documentation](https://docs.sharelogic.com/unifi/4.1/configure/documentation.md) - [How to guides](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides.md) - [How to Handle Attachments](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-handle-attachments.md): Follow this guide to learn how to configure a dedicated Message in Unifi to handle streamed attachments. - [Message](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-handle-attachments/message.md): The AddAttachment Message will be used to process inbound and outbound attachments. - [Scripted REST Resource](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-handle-attachments/scripted-rest-resource.md): Unifi will automatically generate the Scripted REST Resource to cater for inbound streaming. If using a Resource created on a release prior to v3.0 this will need to be updated manually. - [Test AddAttachment](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-handle-attachments/test-addattachment.md): Follow these steps to test the AddAttachment Message. - [How to Manually Close a Bond](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-manually-close-a-bond.md) - [How to Poll for Large Response Payloads](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/large-response-payloads.md): If you're building a polling integration that has response payloads larger than 5MB then you'll need to save them as attachments and adapt your response processing. - [How to Setup an OAuth Connection](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-setup-an-oauth-connection.md): Follow this guide to learn how to setup an OAuth Connection in Unifi. - [Identity Provider Instance](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-provider-instance.md): These are the configuration changes to be made in the identity provider instance when setting up an OAuth Connection. - [Identity Consumer Instance](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-consumer-instance.md): These are the configuration changes to be made in the identity consumer instance when setting up an OAuth Connection. - [OAuth Refresh Token Job](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-setup-an-oauth-connection/oauth-refresh-token-job.md): Setup a scheduled job to ensure refresh tokens do not expire. - [How to Setup Heartbeat Messages](https://docs.sharelogic.com/unifi/4.1/configure/how-to-guides/how-to-setup-heartbeat-messages.md) - [Package](https://docs.sharelogic.com/unifi/4.1/deploy/package.md): Follow these instructions to Package your Integration, ready for migration between ServiceNow instances. - [Instance Clone](https://docs.sharelogic.com/unifi/4.1/deploy/cloning.md) - [Bonding](https://docs.sharelogic.com/unifi/4.1/operate/bonding.md) - [Bonds](https://docs.sharelogic.com/unifi/4.1/operate/bonding/bonds.md): Bonds store the data necessary to link your ServiceNow record to an external system. - [Bonded Attachments](https://docs.sharelogic.com/unifi/4.1/operate/bonding/bonded-attachments.md): A Bonded Attachment is created for every synchronised attachment, storing relevant data. - [Transport](https://docs.sharelogic.com/unifi/4.1/operate/transport.md) - [Snapshots](https://docs.sharelogic.com/unifi/4.1/operate/transport/snapshots.md): Whenever there is an update to a bonded record, Unifi will take a snapshot of it and capture it in a Snapshot record. The Snapshot is the key to facilitating automated Integration testing. - [Transactions](https://docs.sharelogic.com/unifi/4.1/operate/transport/transactions.md): A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests. - [Stages](https://docs.sharelogic.com/unifi/4.1/operate/transport/stages.md): The Stage is the root staging table for all data mapping. Stages are created dynamically at the time of data being sent/received. The Staged Data fields will vary dependent on the data being sent. - [HTTP Requests](https://docs.sharelogic.com/unifi/4.1/operate/transport/http-requests.md): Every request is handled and tracked by a HTTP Request record. - [Dataset Requests](https://docs.sharelogic.com/unifi/4.1/operate/transport/dataset-requests.md): Each Dataset Request stores the details and outcomes of a dataset import or export. - [Poll Requests](https://docs.sharelogic.com/unifi/4.1/operate/transport/poll-requests.md): Each Poll Request stores the details and outcomes of a scheduled poll. - [Error Handling](https://docs.sharelogic.com/unifi/4.1/operate/error-handling.md) - [Integration Pause and Resume](https://docs.sharelogic.com/unifi/4.1/operate/error-handling/pause-and-resume.md): You can now Pause & Resume an Integration. This will cause Transactions to queue and then be processed in the order they were queued. - [Integration Repair](https://docs.sharelogic.com/unifi/4.1/operate/error-handling/repair.md): The Repair feature allows you to manually replay all Transactions on an Integration which are in either an Error or Timed Out state. - [Request Retry](https://docs.sharelogic.com/unifi/4.1/operate/error-handling/retry.md): Retry logic is configurable per Integration and controls how Unifi will automatically retry errored HTTP Requests. - [Transaction & Request Replay](https://docs.sharelogic.com/unifi/4.1/operate/error-handling/replay.md): You can easily replay Requests and Transactions directly from the records themselves. This is an invaluable tool for debugging and error handling. - [Transaction Ignore](https://docs.sharelogic.com/unifi/4.1/operate/error-handling/ignore.md): Setting Transactions to Ignored stops the queue from processing. - [Overview](https://docs.sharelogic.com/unifi/4.1/test/overview.md): Follow this guide to learn how to generate and run automated Integration Tests in Unifi. - [Integration Test](https://docs.sharelogic.com/unifi/4.1/test/integration-tests.md): Unifi can create an automated Integration Test which will capture and replay the Transaction scenarios from an existing Bond. - [Test Scenario](https://docs.sharelogic.com/unifi/4.1/test/test-scenarios.md): Integration Test Scenarios are the elements that make up an Integration Test. Each Scenario will correlate to the relevant Transaction on the Bond from which the test was created. - [Test Scenario Data](https://docs.sharelogic.com/unifi/4.1/test/test-scenario-data.md): Test Scenario Data is a snapshot of all the relevant records created during the processing of a Transaction and is used to both generate the test and ascertain the results of each test run. - [Test Result](https://docs.sharelogic.com/unifi/4.1/test/test-results.md): Whenever you run an Integration Test, the results are captured in an Integration Test Result record. - [Test Scenario Result](https://docs.sharelogic.com/unifi/4.1/test/test-scenario-results.md): Whenever an Integration Test Scenario is run as part of an Integration Test, the results are captured in an Integration Test Scenario Result record. - [Generating Tests](https://docs.sharelogic.com/unifi/4.1/test/generating-tests.md): How to generate an automated Integration Test. - [Running Tests](https://docs.sharelogic.com/unifi/4.1/test/running-tests.md): How to run an automated Integration Test. - [Exploring Results](https://docs.sharelogic.com/unifi/4.1/test/exploring-results.md): How to navigate, view and interpret the results of an automated Integration Test. - [Outbound Incident Guide](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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. - [Trigger](https://docs.sharelogic.com/unifi/4.1/integration-guides/outbound-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.1/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/bidirectional-asynchronous-incident-guide/web-service.md): The entry point for a Process - there should be one endpoint per Process. Once connected, messages are guided to the Integration based on the unique combination of authentication user & endpoint. - [Integration](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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. - [Trigger](https://docs.sharelogic.com/unifi/4.1/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the Process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.1/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/test-resolveincident.md): Follow these steps to test the ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.1/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/incident-parent-and-child-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.1/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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 may also utilise all the previously configured Messages in testing our Integration. - [AddAttachmentInbound Message](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/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](https://docs.sharelogic.com/unifi/4.1/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md): Follow these instructions to test the outbound Message scenarios. - [Test CreateIncidentInbound](https://docs.sharelogic.com/unifi/4.1/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](https://docs.sharelogic.com/unifi/4.1/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.1/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](https://docs.sharelogic.com/unifi/4.1/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.1/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. - [Attachments](https://docs.sharelogic.com/unifi/4.1/troubleshooting/attachments.md) - [Inbound SOAP/Base64 attachments stopped working](https://docs.sharelogic.com/unifi/4.1/troubleshooting/attachments/embedded-attachments-not-being-sent.md) - [New record attachments are not sent from Portal](https://docs.sharelogic.com/unifi/4.1/troubleshooting/attachments/new-record-attachments-are-not-sent-from-portal.md) - [Special characters in attachment file names](https://docs.sharelogic.com/unifi/4.1/troubleshooting/attachments/special-characters-in-attachment-file-names.md) - [Datasets](https://docs.sharelogic.com/unifi/4.1/troubleshooting/datasets.md) - [Development](https://docs.sharelogic.com/unifi/4.1/troubleshooting/development.md) - [Bonding to existing records](https://docs.sharelogic.com/unifi/4.1/troubleshooting/development/bonding-to-existing-records.md) - [Copying an existing Unifi trigger rule doesn't work](https://docs.sharelogic.com/unifi/4.1/troubleshooting/development/copying-an-existing-unifi-trigger-rule-doesnt-work.md) - [Duplicate messages being sent](https://docs.sharelogic.com/unifi/4.1/troubleshooting/development/duplicate-messages-being-sent.md) - [Deleted records are not packaged](https://docs.sharelogic.com/unifi/4.1/troubleshooting/development/deleted-records-are-not-packaged.md) - [Multipart Form Data](https://docs.sharelogic.com/unifi/4.1/troubleshooting/development/multipart-form-data.md): An overview of multipart/form-data generation in Unifi. - [Undefined error when building an integration](https://docs.sharelogic.com/unifi/4.1/troubleshooting/development/undefined-error-when-building-an-integration.md) - [Diagnostic](https://docs.sharelogic.com/unifi/4.1/troubleshooting/diagnostic.md) - [Installation](https://docs.sharelogic.com/unifi/4.1/troubleshooting/installation.md) - [Latest version of Unifi not accessible](https://docs.sharelogic.com/unifi/4.1/troubleshooting/installation/latest-version-of-unifi-not-accessible.md) - [Integration Responses](https://docs.sharelogic.com/unifi/4.1/troubleshooting/integration-responses.md) - [Transaction has been processed already](https://docs.sharelogic.com/unifi/4.1/troubleshooting/integration-responses/transaction-has-been-processed-already.md) - [Initiating transaction not found for inbound receipt](https://docs.sharelogic.com/unifi/4.1/troubleshooting/integration-responses/initiating-transaction-not-found-for-inbound-receipt.md) - [Message has already been processed](https://docs.sharelogic.com/unifi/4.1/troubleshooting/integration-responses/message-has-already-been-processed.md) - [Message ID not found](https://docs.sharelogic.com/unifi/4.1/troubleshooting/integration-responses/message-id-not-found.md) - [Message is not valid for this bond](https://docs.sharelogic.com/unifi/4.1/troubleshooting/integration-responses/message-is-not-valid-for-this-bond.md) - [Message name not recognised](https://docs.sharelogic.com/unifi/4.1/troubleshooting/integration-responses/message-name-not-recognised.md) - [No retry for requests with 401 response](https://docs.sharelogic.com/unifi/4.1/troubleshooting/integration-responses/no-retry-for-requests-with-401-response.md) - [Unable to identify message name from request](https://docs.sharelogic.com/unifi/4.1/troubleshooting/integration-responses/unable-to-identify-message-name-from-request.md) - [Other](https://docs.sharelogic.com/unifi/4.1/troubleshooting/other.md) - [Dynamic stage does not render](https://docs.sharelogic.com/unifi/4.1/troubleshooting/other/dynamic-stage-does-not-render.md) - [Duplicate bonds on Request integrations](https://docs.sharelogic.com/unifi/4.1/troubleshooting/other/duplicate-bonds-on-request-integrations.md) - [Self-test](https://docs.sharelogic.com/unifi/4.1/troubleshooting/self-test.md): A suite of internal tests that can be executed at any time. - [Quick Tour](https://docs.sharelogic.com/unifi/4.1/about/quick-tour.md): A high-level overview of the Unifi application. - [Supported Features](https://docs.sharelogic.com/unifi/4.1/about/supported-features.md): Details of the API models & integration features Unifi supports. - [Application Modules](https://docs.sharelogic.com/unifi/4.1/about/application-module-overview.md): A quick overview of the Unifi Application and its modules. - [Data Model](https://docs.sharelogic.com/unifi/4.1/about/data-model.md): An overview of the table structure used by Unifi - [Transport Data Flow](https://docs.sharelogic.com/unifi/4.1/about/transport-data-flow.md): An overview of the flow of data through Unifi's built in message bus. ## 4.2 - [Unifi User Documentation](https://docs.sharelogic.com/unifi/4.2/readme.md) - [Release Notes](https://docs.sharelogic.com/unifi/4.2/install/release-notes.md) - [Unifi 4.2 Release Notes](https://docs.sharelogic.com/unifi/4.2/install/release-notes/unifi-4.2-release-notes.md): Release date: 15 April, 2024 - [Unifi 4.1 Release Notes](https://docs.sharelogic.com/unifi/4.2/install/release-notes/unifi-4.1-release-notes.md): Release date: 17 November, 2023 - [Unifi 4.0 Release Notes](https://docs.sharelogic.com/unifi/4.2/install/release-notes/unifi-4.0-release-notes.md): Release date: 12 September, 2022 - [Unifi 3.1 Release Notes](https://docs.sharelogic.com/unifi/4.2/install/release-notes/unifi-3.1-release-notes.md) - [Unifi 3.0 Release Notes](https://docs.sharelogic.com/unifi/4.2/install/release-notes/unifi-3.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.2 Release Notes](https://docs.sharelogic.com/unifi/4.2/install/release-notes/2.2-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.1 Release Notes](https://docs.sharelogic.com/unifi/4.2/install/release-notes/2.1-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.0 Release Notes](https://docs.sharelogic.com/unifi/4.2/install/release-notes/2.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Install or Upgrade](https://docs.sharelogic.com/unifi/4.2/install/installation.md) - [Global Utility](https://docs.sharelogic.com/unifi/4.2/install/installation/global-utility.md) - [Hotfix](https://docs.sharelogic.com/unifi/4.2/install/installation/hotfixes.md) - [Integration Designer](https://docs.sharelogic.com/unifi/4.2/configure/integration-designer.md) - [Processes](https://docs.sharelogic.com/unifi/4.2/configure/process.md): Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.). - [Integrations](https://docs.sharelogic.com/unifi/4.2/configure/integrations.md): The Integration is where most configuration and settings are stored. - [Connections](https://docs.sharelogic.com/unifi/4.2/configure/connections.md): Use Connections to manage all your environment details for each integration. - [Messages](https://docs.sharelogic.com/unifi/4.2/configure/messages.md): A Message contains all the configuration required to send, receive, and process a request. - [Message Scripts](https://docs.sharelogic.com/unifi/4.2/configure/message-scripts.md): Message Scripts are where the request processing and data mapping occurs. - [Fields](https://docs.sharelogic.com/unifi/4.2/configure/fields.md): Field and Field Map configuration records are elements that simplify and bring additional functionality when configuring Messages & Message Scripts and facilitate the auto-generation of documentation. - [Field Maps](https://docs.sharelogic.com/unifi/4.2/configure/field-maps.md): Field Maps define template code into which details from Field records are substituted. The resulting blocks of code are wrapped and compiled together into their nominated Message Scripts. - [Response Actions](https://docs.sharelogic.com/unifi/4.2/configure/response-actions.md): Response Actions are interceptors that allow you to customise the way responses are handled. - [Event Actions](https://docs.sharelogic.com/unifi/4.2/configure/event-actions.md): Event Actions are a means of triggering an action from an event. - [Datasets](https://docs.sharelogic.com/unifi/4.2/configure/datasets.md) - [Create a New Dataset](https://docs.sharelogic.com/unifi/4.2/configure/datasets/create-a-new-dataset.md) - [Dataset Extras](https://docs.sharelogic.com/unifi/4.2/configure/datasets/dataset-extras.md) - [Polling](https://docs.sharelogic.com/unifi/4.2/configure/polling.md) - [Pollers](https://docs.sharelogic.com/unifi/4.2/configure/polling/pollers.md): A Poller makes a scheduled request to a remote system. - [Poll Processors](https://docs.sharelogic.com/unifi/4.2/configure/polling/poll-processors.md): Poll Processors are used to setup, execute and process Poll Requests. - [Administration](https://docs.sharelogic.com/unifi/4.2/configure/administration.md) - [Activity Logs](https://docs.sharelogic.com/unifi/4.2/configure/administration/activity-logs.md): The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day. - [Data Stores](https://docs.sharelogic.com/unifi/4.2/configure/administration/data-stores.md): A Data Store is simply a key-value pair stored in the database that is available to all records in the system. - [Properties](https://docs.sharelogic.com/unifi/4.2/configure/administration/properties.md): Global system settings for Unifi. - [Scheduled Scripts](https://docs.sharelogic.com/unifi/4.2/configure/administration/scheduled-scripts.md): Scheduled Scripts are automatically created by the system to perform tasks. - [System Logs](https://docs.sharelogic.com/unifi/4.2/configure/administration/system-logs.md): The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day. - [Attachments](https://docs.sharelogic.com/unifi/4.2/configure/attachments.md) - [Extracting Attachments](https://docs.sharelogic.com/unifi/4.2/configure/attachments/extracting-attachments.md) - [Fetching Attachments](https://docs.sharelogic.com/unifi/4.2/configure/attachments/fetching-attachments.md) - [Embedded Attachments](https://docs.sharelogic.com/unifi/4.2/configure/attachments/embedded-attachments.md) - [Scripting](https://docs.sharelogic.com/unifi/4.2/configure/scripting.md) - [Snippets](https://docs.sharelogic.com/unifi/4.2/configure/scripting/snippets.md): Useful snippets of code given as examples to help with various scripting needs. - [Variables](https://docs.sharelogic.com/unifi/4.2/configure/scripting/variables.md): Here you will find a description of the variables that are available to you when scripting in Unifi. - [Documentation](https://docs.sharelogic.com/unifi/4.2/configure/documentation.md) - [How to guides](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides.md) - [How to Handle Attachments](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-handle-attachments.md): Follow this guide to learn how to configure a dedicated Message in Unifi to handle streamed attachments. - [Message](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-handle-attachments/message.md): The AddAttachment Message will be used to process inbound and outbound attachments. - [Scripted REST Resource](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-handle-attachments/scripted-rest-resource.md): Unifi will automatically generate the Scripted REST Resource to cater for inbound streaming. If using a Resource created on a release prior to v3.0 this will need to be updated manually. - [Test AddAttachment](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-handle-attachments/test-addattachment.md): Follow these steps to test the AddAttachment Message. - [How to Manually Close a Bond](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-manually-close-a-bond.md) - [How to Poll for Large Response Payloads](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/large-response-payloads.md): If you're building a polling integration that has response payloads larger than 5MB then you'll need to save them as attachments and adapt your response processing. - [How to Setup an OAuth Connection](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-setup-an-oauth-connection.md): Follow this guide to learn how to setup an OAuth Connection in Unifi. - [Identity Provider Instance](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-provider-instance.md): These are the configuration changes to be made in the identity provider instance when setting up an OAuth Connection. - [Identity Consumer Instance](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-consumer-instance.md): These are the configuration changes to be made in the identity consumer instance when setting up an OAuth Connection. - [OAuth Refresh Token Job](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-setup-an-oauth-connection/oauth-refresh-token-job.md): Setup a scheduled job to ensure refresh tokens do not expire. - [How to Setup Heartbeat Messages](https://docs.sharelogic.com/unifi/4.2/configure/how-to-guides/how-to-setup-heartbeat-messages.md) - [Package](https://docs.sharelogic.com/unifi/4.2/deploy/package.md): Follow these instructions to Package your Integration, ready for migration between ServiceNow instances. - [Instance Clone](https://docs.sharelogic.com/unifi/4.2/deploy/cloning.md) - [Bonding](https://docs.sharelogic.com/unifi/4.2/operate/bonding.md) - [Bonds](https://docs.sharelogic.com/unifi/4.2/operate/bonding/bonds.md): Bonds store the data necessary to link your ServiceNow record to an external system. - [Bonded Attachments](https://docs.sharelogic.com/unifi/4.2/operate/bonding/bonded-attachments.md): A Bonded Attachment is created for every synchronised attachment, storing relevant data. - [Transport](https://docs.sharelogic.com/unifi/4.2/operate/transport.md) - [Snapshots](https://docs.sharelogic.com/unifi/4.2/operate/transport/snapshots.md): Whenever there is an update to a bonded record, Unifi will take a snapshot of it and capture it in a Snapshot record. The Snapshot is the key to facilitating automated Integration testing. - [Transactions](https://docs.sharelogic.com/unifi/4.2/operate/transport/transactions.md): A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests. - [Stages](https://docs.sharelogic.com/unifi/4.2/operate/transport/stages.md): The Stage is the root staging table for all data mapping. Stages are created dynamically at the time of data being sent/received. The Staged Data fields will vary dependent on the data being sent. - [HTTP Requests](https://docs.sharelogic.com/unifi/4.2/operate/transport/http-requests.md): Every request is handled and tracked by a HTTP Request record. - [Dataset Requests](https://docs.sharelogic.com/unifi/4.2/operate/transport/dataset-requests.md): Each Dataset Request stores the details and outcomes of a dataset import or export. - [Poll Requests](https://docs.sharelogic.com/unifi/4.2/operate/transport/poll-requests.md): Each Poll Request stores the details and outcomes of a scheduled poll. - [Error Handling](https://docs.sharelogic.com/unifi/4.2/operate/error-handling.md) - [Integration Pause and Resume](https://docs.sharelogic.com/unifi/4.2/operate/error-handling/pause-and-resume.md): You can now Pause & Resume an Integration. This will cause Transactions to queue and then be processed in the order they were queued. - [Integration Repair](https://docs.sharelogic.com/unifi/4.2/operate/error-handling/repair.md): The Repair feature allows you to manually replay all Transactions on an Integration which are in either an Error or Timed Out state. - [Request Retry](https://docs.sharelogic.com/unifi/4.2/operate/error-handling/retry.md): Retry logic is configurable per Integration and controls how Unifi will automatically retry errored HTTP Requests. - [Transaction & Request Replay](https://docs.sharelogic.com/unifi/4.2/operate/error-handling/replay.md): You can easily replay Requests and Transactions directly from the records themselves. This is an invaluable tool for debugging and error handling. - [Transaction Ignore](https://docs.sharelogic.com/unifi/4.2/operate/error-handling/ignore.md): Setting Transactions to Ignored stops the queue from processing. - [Overview](https://docs.sharelogic.com/unifi/4.2/test/overview.md): Follow this guide to learn how to generate and run automated Integration Tests in Unifi. - [Integration Test](https://docs.sharelogic.com/unifi/4.2/test/integration-tests.md): Unifi can create an automated Integration Test which will capture and replay the Transaction scenarios from an existing Bond. - [Test Scenario](https://docs.sharelogic.com/unifi/4.2/test/test-scenarios.md): Integration Test Scenarios are the elements that make up an Integration Test. Each Scenario will correlate to the relevant Transaction on the Bond from which the test was created. - [Test Scenario Data](https://docs.sharelogic.com/unifi/4.2/test/test-scenario-data.md): Test Scenario Data is a snapshot of all the relevant records created during the processing of a Transaction and is used to both generate the test and ascertain the results of each test run. - [Test Result](https://docs.sharelogic.com/unifi/4.2/test/test-results.md): Whenever you run an Integration Test, the results are captured in an Integration Test Result record. - [Test Scenario Result](https://docs.sharelogic.com/unifi/4.2/test/test-scenario-results.md): Whenever an Integration Test Scenario is run as part of an Integration Test, the results are captured in an Integration Test Scenario Result record. - [Generating Tests](https://docs.sharelogic.com/unifi/4.2/test/generating-tests.md): How to generate an automated Integration Test. - [Running Tests](https://docs.sharelogic.com/unifi/4.2/test/running-tests.md): How to run an automated Integration Test. - [Exploring Results](https://docs.sharelogic.com/unifi/4.2/test/exploring-results.md): How to navigate, view and interpret the results of an automated Integration Test. - [Outbound Incident Guide](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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. - [Trigger](https://docs.sharelogic.com/unifi/4.2/integration-guides/outbound-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.2/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/bidirectional-asynchronous-incident-guide/web-service.md): The entry point for a Process - there should be one endpoint per Process. Once connected, messages are guided to the Integration based on the unique combination of authentication user & endpoint. - [Integration](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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. - [Trigger](https://docs.sharelogic.com/unifi/4.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the Process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.2/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/test-resolveincident.md): Follow these steps to test the ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.2/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/incident-parent-and-child-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.2/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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 may also utilise all the previously configured Messages in testing our Integration. - [AddAttachmentInbound Message](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.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](https://docs.sharelogic.com/unifi/4.2/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md): Follow these instructions to test the outbound Message scenarios. - [Test CreateIncidentInbound](https://docs.sharelogic.com/unifi/4.2/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](https://docs.sharelogic.com/unifi/4.2/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.2/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](https://docs.sharelogic.com/unifi/4.2/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.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. - [Attachments](https://docs.sharelogic.com/unifi/4.2/troubleshooting/attachments.md) - [Inbound SOAP/Base64 attachments stopped working](https://docs.sharelogic.com/unifi/4.2/troubleshooting/attachments/embedded-attachments-not-being-sent.md) - [New record attachments are not sent from Portal](https://docs.sharelogic.com/unifi/4.2/troubleshooting/attachments/new-record-attachments-are-not-sent-from-portal.md) - [Special characters in attachment file names](https://docs.sharelogic.com/unifi/4.2/troubleshooting/attachments/special-characters-in-attachment-file-names.md) - [Datasets](https://docs.sharelogic.com/unifi/4.2/troubleshooting/datasets.md) - [Development](https://docs.sharelogic.com/unifi/4.2/troubleshooting/development.md) - [Bonding to existing records](https://docs.sharelogic.com/unifi/4.2/troubleshooting/development/bonding-to-existing-records.md) - [Copying an existing Unifi trigger rule doesn't work](https://docs.sharelogic.com/unifi/4.2/troubleshooting/development/copying-an-existing-unifi-trigger-rule-doesnt-work.md) - [Duplicate messages being sent](https://docs.sharelogic.com/unifi/4.2/troubleshooting/development/duplicate-messages-being-sent.md) - [Deleted records are not packaged](https://docs.sharelogic.com/unifi/4.2/troubleshooting/development/deleted-records-are-not-packaged.md) - [Multipart Form Data](https://docs.sharelogic.com/unifi/4.2/troubleshooting/development/multipart-form-data.md): An overview of multipart/form-data generation in Unifi. - [Undefined error when building an integration](https://docs.sharelogic.com/unifi/4.2/troubleshooting/development/undefined-error-when-building-an-integration.md) - [Diagnostic](https://docs.sharelogic.com/unifi/4.2/troubleshooting/diagnostic.md) - [Installation](https://docs.sharelogic.com/unifi/4.2/troubleshooting/installation.md) - [Latest version of Unifi not accessible](https://docs.sharelogic.com/unifi/4.2/troubleshooting/installation/latest-version-of-unifi-not-accessible.md) - [Integration Responses](https://docs.sharelogic.com/unifi/4.2/troubleshooting/integration-responses.md) - [Transaction has been processed already](https://docs.sharelogic.com/unifi/4.2/troubleshooting/integration-responses/transaction-has-been-processed-already.md) - [Initiating transaction not found for inbound receipt](https://docs.sharelogic.com/unifi/4.2/troubleshooting/integration-responses/initiating-transaction-not-found-for-inbound-receipt.md) - [Message has already been processed](https://docs.sharelogic.com/unifi/4.2/troubleshooting/integration-responses/message-has-already-been-processed.md) - [Message ID not found](https://docs.sharelogic.com/unifi/4.2/troubleshooting/integration-responses/message-id-not-found.md) - [Message is not valid for this bond](https://docs.sharelogic.com/unifi/4.2/troubleshooting/integration-responses/message-is-not-valid-for-this-bond.md) - [Message name not recognised](https://docs.sharelogic.com/unifi/4.2/troubleshooting/integration-responses/message-name-not-recognised.md) - [No retry for requests with 401 response](https://docs.sharelogic.com/unifi/4.2/troubleshooting/integration-responses/no-retry-for-requests-with-401-response.md) - [Unable to identify message name from request](https://docs.sharelogic.com/unifi/4.2/troubleshooting/integration-responses/unable-to-identify-message-name-from-request.md) - [Other](https://docs.sharelogic.com/unifi/4.2/troubleshooting/other.md) - [Dynamic stage does not render](https://docs.sharelogic.com/unifi/4.2/troubleshooting/other/dynamic-stage-does-not-render.md) - [Duplicate bonds on Request integrations](https://docs.sharelogic.com/unifi/4.2/troubleshooting/other/duplicate-bonds-on-request-integrations.md) - [Self-test](https://docs.sharelogic.com/unifi/4.2/troubleshooting/self-test.md): A suite of internal tests that can be executed at any time. - [Quick Tour](https://docs.sharelogic.com/unifi/4.2/about/quick-tour.md): A high-level overview of the Unifi application. - [Supported Features](https://docs.sharelogic.com/unifi/4.2/about/supported-features.md): Details of the API models & integration features Unifi supports. - [Application Modules](https://docs.sharelogic.com/unifi/4.2/about/application-module-overview.md): A quick overview of the Unifi Application and its modules. - [Data Model](https://docs.sharelogic.com/unifi/4.2/about/data-model.md): An overview of the table structure used by Unifi - [Transport Data Flow](https://docs.sharelogic.com/unifi/4.2/about/transport-data-flow.md): An overview of the flow of data through Unifi's built in message bus. ## 4.3 - [Unifi User Documentation](https://docs.sharelogic.com/unifi/4.3/readme.md) - [Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes.md) - [Unifi 4.3 Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes/unifi-4.3-release-notes.md): Release date: 5 September, 2024 - [Unifi 4.2 Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes/unifi-4.2-release-notes.md): Release date: 15 April, 2024 - [Unifi 4.1 Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes/unifi-4.1-release-notes.md): Release date: 17 November, 2023 - [Unifi 4.0 Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes/unifi-4.0-release-notes.md): Release date: 12 September, 2022 - [Unifi 3.1 Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes/unifi-3.1-release-notes.md) - [Unifi 3.0 Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes/unifi-3.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.2 Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes/2.2-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.1 Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes/2.1-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.0 Release Notes](https://docs.sharelogic.com/unifi/4.3/install/release-notes/2.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Install or Upgrade](https://docs.sharelogic.com/unifi/4.3/install/installation.md) - [Global Utility](https://docs.sharelogic.com/unifi/4.3/install/installation/global-utility.md) - [Hotfix](https://docs.sharelogic.com/unifi/4.3/install/installation/hotfixes.md) - [Integration Designer](https://docs.sharelogic.com/unifi/4.3/configure/integration-designer.md) - [Processes](https://docs.sharelogic.com/unifi/4.3/configure/process.md): Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.). - [Integrations](https://docs.sharelogic.com/unifi/4.3/configure/integrations.md): The Integration is where most configuration and settings are stored. - [Connections](https://docs.sharelogic.com/unifi/4.3/configure/connections.md): Use Connections to manage all your environment details for each integration. - [Messages](https://docs.sharelogic.com/unifi/4.3/configure/messages.md): A Message contains all the configuration required to send, receive, and process a request. - [Message Scripts](https://docs.sharelogic.com/unifi/4.3/configure/message-scripts.md): Message Scripts are where the request processing and data mapping occurs. - [Fields](https://docs.sharelogic.com/unifi/4.3/configure/fields.md): Field and Field Map configuration records are elements that simplify and bring additional functionality when configuring Messages & Message Scripts and facilitate the auto-generation of documentation. - [Field Maps](https://docs.sharelogic.com/unifi/4.3/configure/field-maps.md): Field Maps define template code into which details from Field records are substituted. The resulting blocks of code are wrapped and compiled together into their nominated Message Scripts. - [Response Actions](https://docs.sharelogic.com/unifi/4.3/configure/response-actions.md): Response Actions are interceptors that allow you to customise the way responses are handled. - [Event Actions](https://docs.sharelogic.com/unifi/4.3/configure/event-actions.md): Event Actions are a means of triggering an action from an event. - [Datasets](https://docs.sharelogic.com/unifi/4.3/configure/datasets.md) - [Create a New Dataset](https://docs.sharelogic.com/unifi/4.3/configure/datasets/create-a-new-dataset.md) - [Dataset Extras](https://docs.sharelogic.com/unifi/4.3/configure/datasets/dataset-extras.md) - [Polling](https://docs.sharelogic.com/unifi/4.3/configure/polling.md) - [Pollers](https://docs.sharelogic.com/unifi/4.3/configure/polling/pollers.md): A Poller makes a scheduled request to a remote system. - [Poll Processors](https://docs.sharelogic.com/unifi/4.3/configure/polling/poll-processors.md): Poll Processors are used to setup, execute and process Poll Requests. - [Administration](https://docs.sharelogic.com/unifi/4.3/configure/administration.md) - [Activity Logs](https://docs.sharelogic.com/unifi/4.3/configure/administration/activity-logs.md): The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day. - [Data Stores](https://docs.sharelogic.com/unifi/4.3/configure/administration/data-stores.md): A Data Store is simply a key-value pair stored in the database that is available to all records in the system. - [Properties](https://docs.sharelogic.com/unifi/4.3/configure/administration/properties.md): Global system settings for Unifi. - [Scheduled Scripts](https://docs.sharelogic.com/unifi/4.3/configure/administration/scheduled-scripts.md): Scheduled Scripts are automatically created by the system to perform tasks. - [System Logs](https://docs.sharelogic.com/unifi/4.3/configure/administration/system-logs.md): The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day. - [Attachments](https://docs.sharelogic.com/unifi/4.3/configure/attachments.md) - [Extracting Attachments](https://docs.sharelogic.com/unifi/4.3/configure/attachments/extracting-attachments.md) - [Fetching Attachments](https://docs.sharelogic.com/unifi/4.3/configure/attachments/fetching-attachments.md) - [Embedded Attachments](https://docs.sharelogic.com/unifi/4.3/configure/attachments/embedded-attachments.md) - [Scripting](https://docs.sharelogic.com/unifi/4.3/configure/scripting.md) - [Snippets](https://docs.sharelogic.com/unifi/4.3/configure/scripting/snippets.md): Useful snippets of code given as examples to help with various scripting needs. - [Variables](https://docs.sharelogic.com/unifi/4.3/configure/scripting/variables.md): Here you will find a description of the variables that are available to you when scripting in Unifi. - [Documentation](https://docs.sharelogic.com/unifi/4.3/configure/documentation.md) - [How to guides](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides.md) - [How to Handle Attachments](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-handle-attachments.md): Follow this guide to learn how to configure a dedicated Message in Unifi to handle streamed attachments. - [Message](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-handle-attachments/message.md): The AddAttachment Message will be used to process inbound and outbound attachments. - [Scripted REST Resource](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-handle-attachments/scripted-rest-resource.md): Unifi will automatically generate the Scripted REST Resource to cater for inbound streaming. If using a Resource created on a release prior to v3.0 this will need to be updated manually. - [Test AddAttachment](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-handle-attachments/test-addattachment.md): Follow these steps to test the AddAttachment Message. - [How to Manually Close a Bond](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-manually-close-a-bond.md) - [How to Poll for Large Response Payloads](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/large-response-payloads.md): If you're building a polling integration that has response payloads larger than 5MB then you'll need to save them as attachments and adapt your response processing. - [How to Setup an OAuth Connection](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-setup-an-oauth-connection.md): Follow this guide to learn how to setup an OAuth Connection in Unifi. - [Identity Provider Instance](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-provider-instance.md): These are the configuration changes to be made in the identity provider instance when setting up an OAuth Connection. - [Identity Consumer Instance](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-consumer-instance.md): These are the configuration changes to be made in the identity consumer instance when setting up an OAuth Connection. - [OAuth Refresh Token Job](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-setup-an-oauth-connection/oauth-refresh-token-job.md): Setup a scheduled job to ensure refresh tokens do not expire. - [How to Setup Heartbeat Messages](https://docs.sharelogic.com/unifi/4.3/configure/how-to-guides/how-to-setup-heartbeat-messages.md) - [Package](https://docs.sharelogic.com/unifi/4.3/deploy/package.md): Follow these instructions to Package your Integration, ready for migration between ServiceNow instances. - [Instance Clone](https://docs.sharelogic.com/unifi/4.3/deploy/cloning.md) - [Bonding](https://docs.sharelogic.com/unifi/4.3/operate/bonding.md) - [Bonds](https://docs.sharelogic.com/unifi/4.3/operate/bonding/bonds.md): Bonds store the data necessary to link your ServiceNow record to an external system. - [Bonded Attachments](https://docs.sharelogic.com/unifi/4.3/operate/bonding/bonded-attachments.md): A Bonded Attachment is created for every synchronised attachment, storing relevant data. - [Transport](https://docs.sharelogic.com/unifi/4.3/operate/transport.md) - [Snapshots](https://docs.sharelogic.com/unifi/4.3/operate/transport/snapshots.md): Whenever there is an update to a bonded record, Unifi will take a snapshot of it and capture it in a Snapshot record. The Snapshot is the key to facilitating automated Integration testing. - [Transactions](https://docs.sharelogic.com/unifi/4.3/operate/transport/transactions.md): A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests. - [Stages](https://docs.sharelogic.com/unifi/4.3/operate/transport/stages.md): The Stage is the root staging table for all data mapping. Stages are created dynamically at the time of data being sent/received. The Staged Data fields will vary dependent on the data being sent. - [HTTP Requests](https://docs.sharelogic.com/unifi/4.3/operate/transport/http-requests.md): Every request is handled and tracked by a HTTP Request record. - [Dataset Requests](https://docs.sharelogic.com/unifi/4.3/operate/transport/dataset-requests.md): Each Dataset Request stores the details and outcomes of a dataset import or export. - [Poll Requests](https://docs.sharelogic.com/unifi/4.3/operate/transport/poll-requests.md): Each Poll Request stores the details and outcomes of a scheduled poll. - [Error Handling](https://docs.sharelogic.com/unifi/4.3/operate/error-handling.md) - [Integration Pause and Resume](https://docs.sharelogic.com/unifi/4.3/operate/error-handling/pause-and-resume.md): You can now Pause & Resume an Integration. This will cause Transactions to queue and then be processed in the order they were queued. - [Integration Repair](https://docs.sharelogic.com/unifi/4.3/operate/error-handling/repair.md): The Repair feature allows you to manually replay all Transactions on an Integration which are in either an Error or Timed Out state. - [Request Retry](https://docs.sharelogic.com/unifi/4.3/operate/error-handling/retry.md): Retry logic is configurable per Integration and controls how Unifi will automatically retry errored HTTP Requests. - [Transaction & Request Replay](https://docs.sharelogic.com/unifi/4.3/operate/error-handling/replay.md): You can easily replay Requests and Transactions directly from the records themselves. This is an invaluable tool for debugging and error handling. - [Transaction Ignore](https://docs.sharelogic.com/unifi/4.3/operate/error-handling/ignore.md): Setting Transactions to Ignored stops the queue from processing. - [Overview](https://docs.sharelogic.com/unifi/4.3/test/overview.md): Follow this guide to learn how to generate and run automated Integration Tests in Unifi. - [Integration Test](https://docs.sharelogic.com/unifi/4.3/test/integration-tests.md): Unifi can create an automated Integration Test which will capture and replay the Transaction scenarios from an existing Bond. - [Test Scenario](https://docs.sharelogic.com/unifi/4.3/test/test-scenarios.md): Integration Test Scenarios are the elements that make up an Integration Test. Each Scenario will correlate to the relevant Transaction on the Bond from which the test was created. - [Test Scenario Data](https://docs.sharelogic.com/unifi/4.3/test/test-scenario-data.md): Test Scenario Data is a snapshot of all the relevant records created during the processing of a Transaction and is used to both generate the test and ascertain the results of each test run. - [Test Result](https://docs.sharelogic.com/unifi/4.3/test/test-results.md): Whenever you run an Integration Test, the results are captured in an Integration Test Result record. - [Test Scenario Result](https://docs.sharelogic.com/unifi/4.3/test/test-scenario-results.md): Whenever an Integration Test Scenario is run as part of an Integration Test, the results are captured in an Integration Test Scenario Result record. - [Generating Tests](https://docs.sharelogic.com/unifi/4.3/test/generating-tests.md): How to generate an automated Integration Test. - [Running Tests](https://docs.sharelogic.com/unifi/4.3/test/running-tests.md): How to run an automated Integration Test. - [Exploring Results](https://docs.sharelogic.com/unifi/4.3/test/exploring-results.md): How to navigate, view and interpret the results of an automated Integration Test. - [Outbound Incident Guide](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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. - [Trigger](https://docs.sharelogic.com/unifi/4.3/integration-guides/outbound-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.3/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/bidirectional-asynchronous-incident-guide/web-service.md): The entry point for a Process - there should be one endpoint per Process. Once connected, messages are guided to the Integration based on the unique combination of authentication user & endpoint. - [Integration](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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. - [Trigger](https://docs.sharelogic.com/unifi/4.3/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the Process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.3/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/test-resolveincident.md): Follow these steps to test the ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.3/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/incident-parent-and-child-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.3/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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 may also utilise all the previously configured Messages in testing our Integration. - [AddAttachmentInbound Message](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/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](https://docs.sharelogic.com/unifi/4.3/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md): Follow these instructions to test the outbound Message scenarios. - [Test CreateIncidentInbound](https://docs.sharelogic.com/unifi/4.3/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](https://docs.sharelogic.com/unifi/4.3/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.3/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](https://docs.sharelogic.com/unifi/4.3/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.3/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. - [Attachments](https://docs.sharelogic.com/unifi/4.3/troubleshooting/attachments.md) - [Inbound SOAP/Base64 attachments stopped working](https://docs.sharelogic.com/unifi/4.3/troubleshooting/attachments/inbound-soap-base64-attachments-stopped-working.md) - [New record attachments are not sent from Portal](https://docs.sharelogic.com/unifi/4.3/troubleshooting/attachments/new-record-attachments-are-not-sent-from-portal.md) - [Special characters in attachment file names](https://docs.sharelogic.com/unifi/4.3/troubleshooting/attachments/special-characters-in-attachment-file-names.md) - [Datasets](https://docs.sharelogic.com/unifi/4.3/troubleshooting/datasets.md) - [Development](https://docs.sharelogic.com/unifi/4.3/troubleshooting/development.md) - [Bonding to existing records](https://docs.sharelogic.com/unifi/4.3/troubleshooting/development/bonding-to-existing-records.md) - [Copying an existing Unifi trigger rule doesn't work](https://docs.sharelogic.com/unifi/4.3/troubleshooting/development/copying-an-existing-unifi-trigger-rule-doesnt-work.md) - [Duplicate messages being sent](https://docs.sharelogic.com/unifi/4.3/troubleshooting/development/duplicate-messages-being-sent.md) - [Deleted records are not packaged](https://docs.sharelogic.com/unifi/4.3/troubleshooting/development/deleted-records-are-not-packaged.md) - [Multipart Form Data](https://docs.sharelogic.com/unifi/4.3/troubleshooting/development/multipart-form-data.md): An overview of multipart/form-data generation in Unifi. - [Undefined error when building an integration](https://docs.sharelogic.com/unifi/4.3/troubleshooting/development/undefined-error-when-building-an-integration.md) - [Diagnostic](https://docs.sharelogic.com/unifi/4.3/troubleshooting/diagnostic.md) - [Installation](https://docs.sharelogic.com/unifi/4.3/troubleshooting/installation.md) - [Latest version of Unifi not accessible](https://docs.sharelogic.com/unifi/4.3/troubleshooting/installation/latest-version-of-unifi-not-accessible.md) - [Integration Responses](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses.md) - [Transaction has been processed already](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/transaction-has-been-processed-already.md) - [Initiating transaction not found for inbound receipt](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/initiating-transaction-not-found-for-inbound-receipt.md) - [Message has already been processed](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/message-has-already-been-processed.md) - [Message ID not found](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/message-id-not-found.md) - [Message is not valid for this bond](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/message-is-not-valid-for-this-bond.md) - [Message name not recognised](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/message-name-not-recognised.md) - [No retry for requests with 401 response](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/no-retry-for-requests-with-401-response.md) - [Unable to identify message name from request](https://docs.sharelogic.com/unifi/4.3/troubleshooting/integration-responses/unable-to-identify-message-name-from-request.md) - [Other](https://docs.sharelogic.com/unifi/4.3/troubleshooting/other.md) - [Dynamic stage does not render](https://docs.sharelogic.com/unifi/4.3/troubleshooting/other/dynamic-stage-does-not-render.md) - [Duplicate bonds on Request integrations](https://docs.sharelogic.com/unifi/4.3/troubleshooting/other/duplicate-bonds-on-request-integrations.md) - [Self-test](https://docs.sharelogic.com/unifi/4.3/troubleshooting/self-test.md): A suite of internal tests that can be executed at any time. - [Quick Tour](https://docs.sharelogic.com/unifi/4.3/about/quick-tour.md): A high-level overview of the Unifi application. - [Roles](https://docs.sharelogic.com/unifi/4.3/about/roles.md) - [Supported Features](https://docs.sharelogic.com/unifi/4.3/about/supported-features.md): Details of the API models & integration features Unifi supports. - [Application Modules](https://docs.sharelogic.com/unifi/4.3/about/application-module-overview.md): A quick overview of the Unifi Application and its modules. - [Data Model](https://docs.sharelogic.com/unifi/4.3/about/data-model.md): An overview of the table structure used by Unifi - [Transport Data Flow](https://docs.sharelogic.com/unifi/4.3/about/transport-data-flow.md): An overview of the flow of data through Unifi's built in message bus. ## 4.4 - [Unifi User Documentation](https://docs.sharelogic.com/unifi/4.4/readme.md) - [Installing Unifi](https://docs.sharelogic.com/unifi/4.4/install/installation.md) - [Upgrading Unifi](https://docs.sharelogic.com/unifi/4.4/install/upgrading.md) - [Hotfix](https://docs.sharelogic.com/unifi/4.4/install/hotfixes.md) - [Global Utility](https://docs.sharelogic.com/unifi/4.4/install/global-utility.md) - [Advanced Dataset Upgrade](https://docs.sharelogic.com/unifi/4.4/install/advanced-dataset-upgrade.md): Introduction of new Advanced flag on Datasets for Zurich compatibility - [Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes.md) - [Unifi 4.4 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/unifi-4.4-release-notes.md): Release date: 25 November, 2025 - [Unifi 4.3 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/unifi-4.3-release-notes.md): Release date: 5 September, 2024 - [Unifi 4.2 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/unifi-4.2-release-notes.md): Release date: 15 April, 2024 - [Unifi 4.1 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/unifi-4.1-release-notes.md): Release date: 17 November, 2023 - [Unifi 4.0 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/unifi-4.0-release-notes.md): Release date: 12 September, 2022 - [Unifi 3.1 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/unifi-3.1-release-notes.md) - [Unifi 3.0 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/unifi-3.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.2 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/2.2-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.1 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/2.1-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.0 Release Notes](https://docs.sharelogic.com/unifi/4.4/install/release-notes/2.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Integration Designer](https://docs.sharelogic.com/unifi/4.4/configure/integration-designer.md) - [Processes](https://docs.sharelogic.com/unifi/4.4/configure/process.md): Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.). - [Integrations](https://docs.sharelogic.com/unifi/4.4/configure/integrations.md): The Integration is where most configuration and settings are stored. - [Connections](https://docs.sharelogic.com/unifi/4.4/configure/connections.md): Use Connections to manage all your environment details for each integration. - [Messages](https://docs.sharelogic.com/unifi/4.4/configure/messages.md): A Message contains all the configuration required to send, receive, and process a request. - [Message Scripts](https://docs.sharelogic.com/unifi/4.4/configure/message-scripts.md): Message Scripts are where the request processing and data mapping occurs. - [Fields](https://docs.sharelogic.com/unifi/4.4/configure/fields.md): Field and Field Map configuration records are elements that simplify and bring additional functionality when configuring Messages & Message Scripts and facilitate the auto-generation of documentation. - [Field Maps](https://docs.sharelogic.com/unifi/4.4/configure/field-maps.md): Field Maps define template code into which details from Field records are substituted. The resulting blocks of code are wrapped and compiled together into their nominated Message Scripts. - [Response Actions](https://docs.sharelogic.com/unifi/4.4/configure/response-actions.md): Response Actions are interceptors that allow you to customise the way responses are handled. - [Event Actions](https://docs.sharelogic.com/unifi/4.4/configure/event-actions.md): Event Actions are a means of triggering an action from an event. - [Datasets](https://docs.sharelogic.com/unifi/4.4/configure/datasets.md) - [Create a New Dataset](https://docs.sharelogic.com/unifi/4.4/configure/datasets/create-a-new-dataset.md) - [Dataset Extras](https://docs.sharelogic.com/unifi/4.4/configure/datasets/dataset-extras.md) - [Sharing Extended Tables with Datasets](https://docs.sharelogic.com/unifi/4.4/configure/datasets/sharing-extended-tables-with-datasets.md) - [Polling](https://docs.sharelogic.com/unifi/4.4/configure/polling.md) - [Pollers](https://docs.sharelogic.com/unifi/4.4/configure/polling/pollers.md): A Poller makes a scheduled request to a remote system. - [Poll Processors](https://docs.sharelogic.com/unifi/4.4/configure/polling/poll-processors.md): Poll Processors are used to setup, execute and process Poll Requests. - [Administration](https://docs.sharelogic.com/unifi/4.4/configure/administration.md) - [Activity Logs](https://docs.sharelogic.com/unifi/4.4/configure/administration/activity-logs.md): The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day. - [Data Stores](https://docs.sharelogic.com/unifi/4.4/configure/administration/data-stores.md): A Data Store is simply a key-value pair stored in the database that is available to all records in the system. - [Properties](https://docs.sharelogic.com/unifi/4.4/configure/administration/properties.md): Global system settings for Unifi. - [Scheduled Scripts](https://docs.sharelogic.com/unifi/4.4/configure/administration/scheduled-scripts.md): Scheduled Scripts are automatically created by the system to perform tasks. - [System Logs](https://docs.sharelogic.com/unifi/4.4/configure/administration/system-logs.md): The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day. - [Attachments](https://docs.sharelogic.com/unifi/4.4/configure/attachments.md) - [Extracting Attachments](https://docs.sharelogic.com/unifi/4.4/configure/attachments/extracting-attachments.md) - [Fetching Attachments](https://docs.sharelogic.com/unifi/4.4/configure/attachments/fetching-attachments.md) - [Sending Attachments](https://docs.sharelogic.com/unifi/4.4/configure/attachments/sending-attachments.md) - [Sending Journal Embedded Attachments](https://docs.sharelogic.com/unifi/4.4/configure/attachments/sending-journal-embedded-attachments.md) - [Sending Multipart Attachments](https://docs.sharelogic.com/unifi/4.4/configure/attachments/sending-multipart-attachments.md) - [Deleting Attachments](https://docs.sharelogic.com/unifi/4.4/configure/attachments/deleting-attachments.md) - [Scripting](https://docs.sharelogic.com/unifi/4.4/configure/scripting.md) - [Snippets](https://docs.sharelogic.com/unifi/4.4/configure/scripting/snippets.md): Useful snippets of code given as examples to help with various scripting needs. - [Variables](https://docs.sharelogic.com/unifi/4.4/configure/scripting/variables.md): Here you will find a description of the variables that are available to you when scripting in Unifi. - [Documentation](https://docs.sharelogic.com/unifi/4.4/configure/documentation.md) - [How to guides](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides.md) - [How to Handle Attachments](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-handle-attachments.md): Follow this guide to learn how to configure a dedicated Message in Unifi to handle streamed attachments. - [Message](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-handle-attachments/message.md): The AddAttachment Message will be used to process inbound and outbound attachments. - [Scripted REST Resource](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-handle-attachments/scripted-rest-resource.md): Unifi will automatically generate the Scripted REST Resource to cater for inbound streaming. If using a Resource created on a release prior to v3.0 this will need to be updated manually. - [Test AddAttachment](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-handle-attachments/test-addattachment.md): Follow these steps to test the AddAttachment Message. - [How to Manually Close a Bond](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-manually-close-a-bond.md) - [How to Poll for Large Response Payloads](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/large-response-payloads.md): If you're building a polling integration that has response payloads larger than 5MB then you'll need to save them as attachments and adapt your response processing. - [How to Setup an OAuth Connection](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-setup-an-oauth-connection.md): Follow this guide to learn how to setup an OAuth Connection in Unifi. - [Identity Provider Instance](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-provider-instance.md): These are the configuration changes to be made in the identity provider instance when setting up an OAuth Connection. - [Identity Consumer Instance](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-consumer-instance.md): These are the configuration changes to be made in the identity consumer instance when setting up an OAuth Connection. - [OAuth Refresh Token Job](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-setup-an-oauth-connection/oauth-refresh-token-job.md): Setup a scheduled job to ensure refresh tokens do not expire. - [How to Setup Heartbeat Messages](https://docs.sharelogic.com/unifi/4.4/configure/how-to-guides/how-to-setup-heartbeat-messages.md) - [Package](https://docs.sharelogic.com/unifi/4.4/deploy/package.md): Follow these instructions to Package your Integration, ready for migration between ServiceNow instances. - [Instance Clone](https://docs.sharelogic.com/unifi/4.4/deploy/cloning.md) - [Bonding](https://docs.sharelogic.com/unifi/4.4/operate/bonding.md) - [Bonds](https://docs.sharelogic.com/unifi/4.4/operate/bonding/bonds.md): Bonds store the data necessary to link your ServiceNow record to an external system. - [Bonded Attachments](https://docs.sharelogic.com/unifi/4.4/operate/bonding/bonded-attachments.md): A Bonded Attachment is created for every synchronised attachment, storing relevant data. - [Transport](https://docs.sharelogic.com/unifi/4.4/operate/transport.md) - [Snapshots](https://docs.sharelogic.com/unifi/4.4/operate/transport/snapshots.md): Whenever there is an update to a bonded record, Unifi will take a snapshot of it and capture it in a Snapshot record. The Snapshot is the key to facilitating automated Integration testing. - [Transactions](https://docs.sharelogic.com/unifi/4.4/operate/transport/transactions.md): A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests. - [Stages](https://docs.sharelogic.com/unifi/4.4/operate/transport/stages.md): The Stage is the root staging table for all data mapping. Stages are created dynamically at the time of data being sent/received. The Staged Data fields will vary dependent on the data being sent. - [HTTP Requests](https://docs.sharelogic.com/unifi/4.4/operate/transport/http-requests.md): Every request is handled and tracked by a HTTP Request record. - [Dataset Requests](https://docs.sharelogic.com/unifi/4.4/operate/transport/dataset-requests.md): Each Dataset Request stores the details and outcomes of a dataset import or export. - [Poll Requests](https://docs.sharelogic.com/unifi/4.4/operate/transport/poll-requests.md): Each Poll Request stores the details and outcomes of a scheduled poll. - [Error Handling](https://docs.sharelogic.com/unifi/4.4/operate/error-handling.md) - [Integration Pause and Resume](https://docs.sharelogic.com/unifi/4.4/operate/error-handling/pause-and-resume.md): You can now Pause & Resume an Integration. This will cause Transactions to queue and then be processed in the order they were queued. - [Integration Repair](https://docs.sharelogic.com/unifi/4.4/operate/error-handling/repair.md): The Repair feature allows you to manually replay all Transactions on an Integration which are in either an Error or Timed Out state. - [Request Retry](https://docs.sharelogic.com/unifi/4.4/operate/error-handling/retry.md): Retry logic is configurable per Integration and controls how Unifi will automatically retry errored HTTP Requests. - [Transaction & Request Replay](https://docs.sharelogic.com/unifi/4.4/operate/error-handling/replay.md): You can easily replay Requests and Transactions directly from the records themselves. This is an invaluable tool for debugging and error handling. - [Transaction Ignore](https://docs.sharelogic.com/unifi/4.4/operate/error-handling/ignore.md): Setting Transactions to Ignored stops the queue from processing. - [Overview](https://docs.sharelogic.com/unifi/4.4/test/overview.md): Follow this guide to learn how to generate and run automated Integration Tests in Unifi. - [Integration Test](https://docs.sharelogic.com/unifi/4.4/test/integration-tests.md): Unifi can create an automated Integration Test which will capture and replay the Transaction scenarios from an existing Bond. - [Test Scenario](https://docs.sharelogic.com/unifi/4.4/test/test-scenarios.md): Integration Test Scenarios are the elements that make up an Integration Test. Each Scenario will correlate to the relevant Transaction on the Bond from which the test was created. - [Test Scenario Data](https://docs.sharelogic.com/unifi/4.4/test/test-scenario-data.md): Test Scenario Data is a snapshot of all the relevant records created during the processing of a Transaction and is used to both generate the test and ascertain the results of each test run. - [Test Result](https://docs.sharelogic.com/unifi/4.4/test/test-results.md): Whenever you run an Integration Test, the results are captured in an Integration Test Result record. - [Test Scenario Result](https://docs.sharelogic.com/unifi/4.4/test/test-scenario-results.md): Whenever an Integration Test Scenario is run as part of an Integration Test, the results are captured in an Integration Test Scenario Result record. - [Generating Tests](https://docs.sharelogic.com/unifi/4.4/test/generating-tests.md): How to generate an automated Integration Test. - [Running Tests](https://docs.sharelogic.com/unifi/4.4/test/running-tests.md): How to run an automated Integration Test. - [Exploring Results](https://docs.sharelogic.com/unifi/4.4/test/exploring-results.md): How to navigate, view and interpret the results of an automated Integration Test. - [Outbound Incident Guide](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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. - [Trigger](https://docs.sharelogic.com/unifi/4.4/integration-guides/outbound-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.4/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/bidirectional-asynchronous-incident-guide/web-service.md): The entry point for a Process - there should be one endpoint per Process. Once connected, messages are guided to the Integration based on the unique combination of authentication user & endpoint. - [Integration](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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. - [Create Scenario](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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. - [Trigger](https://docs.sharelogic.com/unifi/4.4/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the Process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/4.4/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/test-resolveincident.md): Follow these steps to test the ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.4/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/incident-parent-and-child-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.4/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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 may also utilise all the previously configured Messages in testing our Integration. - [AddAttachmentInbound Message](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/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](https://docs.sharelogic.com/unifi/4.4/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md): Follow these instructions to test the outbound Message scenarios. - [Test CreateIncidentInbound](https://docs.sharelogic.com/unifi/4.4/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](https://docs.sharelogic.com/unifi/4.4/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/4.4/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](https://docs.sharelogic.com/unifi/4.4/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/4.4/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. - [Attachments](https://docs.sharelogic.com/unifi/4.4/troubleshooting/attachments.md) - [Inbound SOAP/Base64 attachments stopped working](https://docs.sharelogic.com/unifi/4.4/troubleshooting/attachments/inbound-soap-base64-attachments-stopped-working.md) - [New record attachments are not sent from Portal](https://docs.sharelogic.com/unifi/4.4/troubleshooting/attachments/new-record-attachments-are-not-sent-from-portal.md) - [Special characters in attachment file names](https://docs.sharelogic.com/unifi/4.4/troubleshooting/attachments/special-characters-in-attachment-file-names.md) - [Datasets](https://docs.sharelogic.com/unifi/4.4/troubleshooting/datasets.md) - [Development](https://docs.sharelogic.com/unifi/4.4/troubleshooting/development.md) - [Bonding to existing records](https://docs.sharelogic.com/unifi/4.4/troubleshooting/development/bonding-to-existing-records.md) - [Copying an existing Unifi trigger rule doesn't work](https://docs.sharelogic.com/unifi/4.4/troubleshooting/development/copying-an-existing-unifi-trigger-rule-doesnt-work.md) - [Duplicate messages being sent](https://docs.sharelogic.com/unifi/4.4/troubleshooting/development/duplicate-messages-being-sent.md) - [Deleted records are not packaged](https://docs.sharelogic.com/unifi/4.4/troubleshooting/development/deleted-records-are-not-packaged.md) - [Multipart Form Data](https://docs.sharelogic.com/unifi/4.4/troubleshooting/development/multipart-form-data.md): An overview of multipart/form-data generation in Unifi. - [Undefined error when building an integration](https://docs.sharelogic.com/unifi/4.4/troubleshooting/development/undefined-error-when-building-an-integration.md) - [Diagnostic](https://docs.sharelogic.com/unifi/4.4/troubleshooting/diagnostic.md) - [Installation](https://docs.sharelogic.com/unifi/4.4/troubleshooting/installation.md) - [Latest version of Unifi not accessible](https://docs.sharelogic.com/unifi/4.4/troubleshooting/installation/latest-version-of-unifi-not-accessible.md) - [Integration Responses](https://docs.sharelogic.com/unifi/4.4/troubleshooting/integration-responses.md) - [Transaction has been processed already](https://docs.sharelogic.com/unifi/4.4/troubleshooting/integration-responses/transaction-has-been-processed-already.md) - [Initiating transaction not found for inbound receipt](https://docs.sharelogic.com/unifi/4.4/troubleshooting/integration-responses/initiating-transaction-not-found-for-inbound-receipt.md) - [Message has already been processed](https://docs.sharelogic.com/unifi/4.4/troubleshooting/integration-responses/message-has-already-been-processed.md) - [Message ID not found](https://docs.sharelogic.com/unifi/4.4/troubleshooting/integration-responses/message-id-not-found.md) - [Message is not valid for this bond](https://docs.sharelogic.com/unifi/4.4/troubleshooting/integration-responses/message-is-not-valid-for-this-bond.md) - [Message name not recognised](https://docs.sharelogic.com/unifi/4.4/troubleshooting/integration-responses/message-name-not-recognised.md) - [No retry for requests with 401 response](https://docs.sharelogic.com/unifi/4.4/troubleshooting/integration-responses/no-retry-for-requests-with-401-response.md) - [Unable to identify message name from request](https://docs.sharelogic.com/unifi/4.4/troubleshooting/integration-responses/unable-to-identify-message-name-from-request.md) - [Other](https://docs.sharelogic.com/unifi/4.4/troubleshooting/other.md) - [Dynamic stage does not render](https://docs.sharelogic.com/unifi/4.4/troubleshooting/other/dynamic-stage-does-not-render.md) - [Duplicate bonds on Request integrations](https://docs.sharelogic.com/unifi/4.4/troubleshooting/other/duplicate-bonds-on-request-integrations.md) - [Query Range ACL Errors](https://docs.sharelogic.com/unifi/4.4/troubleshooting/query-range-acl-errors.md): Troubleshooting: Query Range ACL Errors After May 2025 ServiceNow Patch - [Self-test](https://docs.sharelogic.com/unifi/4.4/troubleshooting/self-test.md): A suite of internal tests that can be executed at any time. - [Quick Tour](https://docs.sharelogic.com/unifi/4.4/about/quick-tour.md): A high-level overview of the Unifi application. - [Roles](https://docs.sharelogic.com/unifi/4.4/about/roles.md) - [Supported Features](https://docs.sharelogic.com/unifi/4.4/about/supported-features.md): Details of the API models & integration features Unifi supports. - [Application Modules](https://docs.sharelogic.com/unifi/4.4/about/application-module-overview.md): A quick overview of the Unifi Application and its modules. - [Data Model](https://docs.sharelogic.com/unifi/4.4/about/data-model.md): An overview of the table structure used by Unifi - [Transport Data Flow](https://docs.sharelogic.com/unifi/4.4/about/transport-data-flow.md): An overview of the flow of data through Unifi's built in message bus. ## 4.5 - [Unifi User Documentation](https://docs.sharelogic.com/unifi/readme.md) - [CRITICAL UPGRADE NOTICE](https://docs.sharelogic.com/unifi/install/critical-upgrade-notice.md) - [Installing Unifi](https://docs.sharelogic.com/unifi/install/installation.md) - [Upgrading Unifi](https://docs.sharelogic.com/unifi/install/upgrading.md) - [Hotfix](https://docs.sharelogic.com/unifi/install/hotfixes.md) - [Global Utility](https://docs.sharelogic.com/unifi/install/global-utility.md) - [Advanced Dataset Upgrade](https://docs.sharelogic.com/unifi/install/advanced-dataset-upgrade.md): Introduction of new Advanced flag on Datasets for Zurich compatibility - [Release Notes](https://docs.sharelogic.com/unifi/install/release-notes.md) - [Unifi 4.5 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/unifi-4.5-release-notes.md): Release date: 13 April, 2026 - [Unifi 4.4 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/unifi-4.4-release-notes.md): Release date: 25 November, 2025 - [Unifi 4.3 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/unifi-4.3-release-notes.md): Release date: 5 September, 2024 - [Unifi 4.2 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/unifi-4.2-release-notes.md): Release date: 15 April, 2024 - [Unifi 4.1 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/unifi-4.1-release-notes.md): Release date: 17 November, 2023 - [Unifi 4.0 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/unifi-4.0-release-notes.md): Release date: 12 September, 2022 - [Unifi 3.1 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/unifi-3.1-release-notes.md) - [Unifi 3.0 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/unifi-3.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.2 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/2.2-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.1 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/2.1-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Unifi 2.0 Release Notes](https://docs.sharelogic.com/unifi/install/release-notes/2.0-release-notes.md): Here you will find details of what's changed in this release, including new features & improvements, deprecated features and general fixes. - [Integration Designer](https://docs.sharelogic.com/unifi/configure/integration-designer.md) - [Processes](https://docs.sharelogic.com/unifi/configure/process.md): Process is the top level configuration element which contains all Integrations for the Process concerned (e.g. Incident, Problem, Change, Request etc.). - [Integrations](https://docs.sharelogic.com/unifi/configure/integrations.md): The Integration is where most configuration and settings are stored. - [Connections](https://docs.sharelogic.com/unifi/configure/connections.md): Use Connections to manage all your environment details for each integration. - [Messages](https://docs.sharelogic.com/unifi/configure/messages.md): A Message contains all the configuration required to send, receive, and process a request. - [Message Scripts](https://docs.sharelogic.com/unifi/configure/message-scripts.md): Message Scripts are where the request processing and data mapping occurs. - [Fields](https://docs.sharelogic.com/unifi/configure/fields.md): Field and Field Map configuration records are elements that simplify and bring additional functionality when configuring Messages & Message Scripts and facilitate the auto-generation of documentation. - [Field Maps](https://docs.sharelogic.com/unifi/configure/field-maps.md): Field Maps define template code into which details from Field records are substituted. The resulting blocks of code are wrapped and compiled together into their nominated Message Scripts. - [Response Actions](https://docs.sharelogic.com/unifi/configure/response-actions.md): Response Actions are interceptors that allow you to customise the way responses are handled. - [Event Actions](https://docs.sharelogic.com/unifi/configure/event-actions.md): Event Actions are a means of triggering an action from an event. - [Datasets](https://docs.sharelogic.com/unifi/configure/datasets.md) - [Create a New Dataset](https://docs.sharelogic.com/unifi/configure/datasets/create-a-new-dataset.md) - [Dataset Extras](https://docs.sharelogic.com/unifi/configure/datasets/dataset-extras.md) - [Sharing Extended Tables with Datasets](https://docs.sharelogic.com/unifi/configure/datasets/sharing-extended-tables-with-datasets.md) - [Polling](https://docs.sharelogic.com/unifi/configure/polling.md) - [Pollers](https://docs.sharelogic.com/unifi/configure/polling/pollers.md): A Poller makes a scheduled request to a remote system. - [Poll Processors](https://docs.sharelogic.com/unifi/configure/polling/poll-processors.md): Poll Processors are used to setup, execute and process Poll Requests. - [Administration](https://docs.sharelogic.com/unifi/configure/administration.md) - [Activity Logs](https://docs.sharelogic.com/unifi/configure/administration/activity-logs.md): The Activity Logs module is a quick link to the Unifi Activity Logs and shows all entries from the current day. - [Data Stores](https://docs.sharelogic.com/unifi/configure/administration/data-stores.md): A Data Store is simply a key-value pair stored in the database that is available to all records in the system. - [Properties](https://docs.sharelogic.com/unifi/configure/administration/properties.md): Global system settings for Unifi. - [Scheduled Scripts](https://docs.sharelogic.com/unifi/configure/administration/scheduled-scripts.md): Scheduled Scripts are automatically created by the system to perform tasks. - [System Logs](https://docs.sharelogic.com/unifi/configure/administration/system-logs.md): The System Logs module is a quick link to the ServiceNow system logs and shows errors and warnings from the current day. - [Attachments](https://docs.sharelogic.com/unifi/configure/attachments.md) - [Extracting Attachments](https://docs.sharelogic.com/unifi/configure/attachments/extracting-attachments.md) - [Fetching Attachments](https://docs.sharelogic.com/unifi/configure/attachments/fetching-attachments.md) - [Sending Attachments](https://docs.sharelogic.com/unifi/configure/attachments/sending-attachments.md) - [Sending Journal Embedded Attachments](https://docs.sharelogic.com/unifi/configure/attachments/sending-journal-embedded-attachments.md) - [Sending Multipart Attachments](https://docs.sharelogic.com/unifi/configure/attachments/sending-multipart-attachments.md) - [Deleting Attachments](https://docs.sharelogic.com/unifi/configure/attachments/deleting-attachments.md) - [Scripting](https://docs.sharelogic.com/unifi/configure/scripting.md) - [Snippets](https://docs.sharelogic.com/unifi/configure/scripting/snippets.md): Useful snippets of code given as examples to help with various scripting needs. - [Variables](https://docs.sharelogic.com/unifi/configure/scripting/variables.md): Here you will find a description of the variables that are available to you when scripting in Unifi. - [Documentation](https://docs.sharelogic.com/unifi/configure/documentation.md) - [How to guides](https://docs.sharelogic.com/unifi/configure/how-to-guides.md) - [How to Handle Attachments](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-handle-attachments.md): Follow this guide to learn how to configure a dedicated Message in Unifi to handle streamed attachments. - [Message](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-handle-attachments/message.md): The AddAttachment Message will be used to process inbound and outbound attachments. - [Scripted REST Resource](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-handle-attachments/scripted-rest-resource.md): Unifi will automatically generate the Scripted REST Resource to cater for inbound streaming. If using a Resource created on a release prior to v3.0 this will need to be updated manually. - [Test AddAttachment](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-handle-attachments/test-addattachment.md): Follow these steps to test the AddAttachment Message. - [How to Manually Close a Bond](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-manually-close-a-bond.md) - [How to Poll for Large Response Payloads](https://docs.sharelogic.com/unifi/configure/how-to-guides/large-response-payloads.md): If you're building a polling integration that has response payloads larger than 5MB then you'll need to save them as attachments and adapt your response processing. - [How to Setup an OAuth Connection](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-setup-an-oauth-connection.md): Follow this guide to learn how to setup an OAuth Connection in Unifi. - [Identity Provider Instance](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-provider-instance.md): These are the configuration changes to be made in the identity provider instance when setting up an OAuth Connection. - [Identity Consumer Instance](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-setup-an-oauth-connection/identity-consumer-instance.md): These are the configuration changes to be made in the identity consumer instance when setting up an OAuth Connection. - [OAuth Refresh Token Job](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-setup-an-oauth-connection/oauth-refresh-token-job.md): Setup a scheduled job to ensure refresh tokens do not expire. - [How to Setup Heartbeat Messages](https://docs.sharelogic.com/unifi/configure/how-to-guides/how-to-setup-heartbeat-messages.md) - [Package](https://docs.sharelogic.com/unifi/deploy/package.md): Follow these instructions to Package your Integration, ready for migration between ServiceNow instances. - [Instance Clone](https://docs.sharelogic.com/unifi/deploy/cloning.md) - [Bonding](https://docs.sharelogic.com/unifi/operate/bonding.md) - [Bonds](https://docs.sharelogic.com/unifi/operate/bonding/bonds.md): Bonds store the data necessary to link your ServiceNow record to an external system. - [Bonded Attachments](https://docs.sharelogic.com/unifi/operate/bonding/bonded-attachments.md): A Bonded Attachment is created for every synchronised attachment, storing relevant data. - [Transport](https://docs.sharelogic.com/unifi/operate/transport.md) - [Snapshots](https://docs.sharelogic.com/unifi/operate/transport/snapshots.md): Whenever there is an update to a bonded record, Unifi will take a snapshot of it and capture it in a Snapshot record. The Snapshot is the key to facilitating automated Integration testing. - [Transactions](https://docs.sharelogic.com/unifi/operate/transport/transactions.md): A Transaction is an instance of a Message occurence. It contains and tracks the processing of a Message using Stages and HTTP Requests. - [Stages](https://docs.sharelogic.com/unifi/operate/transport/stages.md): The Stage is the root staging table for all data mapping. Stages are created dynamically at the time of data being sent/received. The Staged Data fields will vary dependent on the data being sent. - [HTTP Requests](https://docs.sharelogic.com/unifi/operate/transport/http-requests.md): Every request is handled and tracked by a HTTP Request record. - [Dataset Requests](https://docs.sharelogic.com/unifi/operate/transport/dataset-requests.md): Each Dataset Request stores the details and outcomes of a dataset import or export. - [Poll Requests](https://docs.sharelogic.com/unifi/operate/transport/poll-requests.md): Each Poll Request stores the details and outcomes of a scheduled poll. - [Error Handling](https://docs.sharelogic.com/unifi/operate/error-handling.md) - [Integration Pause and Resume](https://docs.sharelogic.com/unifi/operate/error-handling/pause-and-resume.md): You can now Pause & Resume an Integration. This will cause Transactions to queue and then be processed in the order they were queued. - [Integration Repair](https://docs.sharelogic.com/unifi/operate/error-handling/repair.md): The Repair feature allows you to manually replay all Transactions on an Integration which are in either an Error or Timed Out state. - [Request Retry](https://docs.sharelogic.com/unifi/operate/error-handling/retry.md): Retry logic is configurable per Integration and controls how Unifi will automatically retry errored HTTP Requests. - [Transaction & Request Replay](https://docs.sharelogic.com/unifi/operate/error-handling/replay.md): You can easily replay Requests and Transactions directly from the records themselves. This is an invaluable tool for debugging and error handling. - [Transaction Ignore](https://docs.sharelogic.com/unifi/operate/error-handling/ignore.md): Setting Transactions to Ignored stops the queue from processing. - [Overview](https://docs.sharelogic.com/unifi/test/overview.md): Follow this guide to learn how to generate and run automated Integration Tests in Unifi. - [Integration Test](https://docs.sharelogic.com/unifi/test/integration-tests.md): Unifi can create an automated Integration Test which will capture and replay the Transaction scenarios from an existing Bond. - [Test Scenario](https://docs.sharelogic.com/unifi/test/test-scenarios.md): Integration Test Scenarios are the elements that make up an Integration Test. Each Scenario will correlate to the relevant Transaction on the Bond from which the test was created. - [Test Scenario Data](https://docs.sharelogic.com/unifi/test/test-scenario-data.md): Test Scenario Data is a snapshot of all the relevant records created during the processing of a Transaction and is used to both generate the test and ascertain the results of each test run. - [Test Result](https://docs.sharelogic.com/unifi/test/test-results.md): Whenever you run an Integration Test, the results are captured in an Integration Test Result record. - [Test Scenario Result](https://docs.sharelogic.com/unifi/test/test-scenario-results.md): Whenever an Integration Test Scenario is run as part of an Integration Test, the results are captured in an Integration Test Scenario Result record. - [Generating Tests](https://docs.sharelogic.com/unifi/test/generating-tests.md): How to generate an automated Integration Test. - [Running Tests](https://docs.sharelogic.com/unifi/test/running-tests.md): How to run an automated Integration Test. - [Exploring Results](https://docs.sharelogic.com/unifi/test/exploring-results.md): How to navigate, view and interpret the results of an automated Integration Test. - [Outbound Incident Guide](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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. - [Create Scenario](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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. - [Trigger](https://docs.sharelogic.com/unifi/integration-guides/outbound-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/integration-guides/outbound-incident-guide/create-scenario/test-createincident.md): We will test our CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/outbound-incident-guide/update-scenario/test-updateincident.md): We will test our UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/outbound-incident-guide/resolve-scenario/test-resolveincident.md): We will test our ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/outbound-incident-guide/conclusion.md): Congratulations on completing this Outbound Incident Integration Guide. - [Bidirectional Asynchronous Incident Guide](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/bidirectional-asynchronous-incident-guide/web-service.md): The entry point for a Process - there should be one endpoint per Process. Once connected, messages are guided to the Integration based on the unique combination of authentication user & endpoint. - [Integration](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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. - [Create Scenario](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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. - [Trigger](https://docs.sharelogic.com/unifi/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/trigger.md): The Trigger is a Business Rule which stipulates the conditions under which Messages will be sent for the Process concerned. - [Test CreateIncident](https://docs.sharelogic.com/unifi/integration-guides/bidirectional-asynchronous-incident-guide/create-scenario/test-createincident.md): Follow these steps to test the CreateIncident Message. - [Update Scenario](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/bidirectional-asynchronous-incident-guide/update-scenario/test-updateincident.md): Follow these steps to test the UpdateIncident Message. - [Resolve Scenario](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/bidirectional-asynchronous-incident-guide/resolve-scenario/test-resolveincident.md): Follow these steps to test the ResolveIncident Message. - [Build - Integration Level](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/bidirectional-asynchronous-incident-guide/conclusion.md): Congratulations on completing this bidirectional asynchronous Incident integration Guide. - [Incident Update Poller Guide](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/incident-multiple-message-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/integration-guides/incident-multiple-message-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/incident-parent-and-child-poller-guide/testing/test-updateincidentinbound.md): Follow these steps to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/integration-guides/incident-parent-and-child-poller-guide/testing/test-resolveincidentinbound.md): Follow these steps to test the ResolveIncidentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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 may also utilise all the previously configured Messages in testing our Integration. - [AddAttachmentInbound Message](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/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](https://docs.sharelogic.com/unifi/integration-guides/incident-attachment-poller-guide/testing/test-outbound-scenarios.md): Follow these instructions to test the outbound Message scenarios. - [Test CreateIncidentInbound](https://docs.sharelogic.com/unifi/integration-guides/incident-attachment-poller-guide/testing/test-createincidentinbound.md): Follow these instructions to test the CreateIncidentInbound Message. - [Test UpdateIncidentInbound](https://docs.sharelogic.com/unifi/integration-guides/incident-attachment-poller-guide/testing/test-updateincidentinbound.md): Follow these instructions to test the UpdateIncidentInbound Message. - [Test ResolveIncidentInbound](https://docs.sharelogic.com/unifi/integration-guides/incident-attachment-poller-guide/testing/test-resolveincidentinbound.md): Follow these instructions to test the ResolveIncidentInbound Message. - [Test AddAttachmentInbound](https://docs.sharelogic.com/unifi/integration-guides/incident-attachment-poller-guide/testing/test-addattachmentinbound.md): Follow these instructions to test the AddAttachmentInbound Message. - [Conclusion](https://docs.sharelogic.com/unifi/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. - [Attachments](https://docs.sharelogic.com/unifi/troubleshooting/attachments.md) - [Inbound SOAP/Base64 attachments stopped working](https://docs.sharelogic.com/unifi/troubleshooting/attachments/inbound-soap-base64-attachments-stopped-working.md) - [New record attachments are not sent from Portal](https://docs.sharelogic.com/unifi/troubleshooting/attachments/new-record-attachments-are-not-sent-from-portal.md) - [Special characters in attachment file names](https://docs.sharelogic.com/unifi/troubleshooting/attachments/special-characters-in-attachment-file-names.md) - [Datasets](https://docs.sharelogic.com/unifi/troubleshooting/datasets.md) - [Development](https://docs.sharelogic.com/unifi/troubleshooting/development.md) - [Bonding to existing records](https://docs.sharelogic.com/unifi/troubleshooting/development/bonding-to-existing-records.md) - [Copying an existing Unifi trigger rule doesn't work](https://docs.sharelogic.com/unifi/troubleshooting/development/copying-an-existing-unifi-trigger-rule-doesnt-work.md) - [Duplicate messages being sent](https://docs.sharelogic.com/unifi/troubleshooting/development/duplicate-messages-being-sent.md) - [Deleted records are not packaged](https://docs.sharelogic.com/unifi/troubleshooting/development/deleted-records-are-not-packaged.md) - [Multipart Form Data](https://docs.sharelogic.com/unifi/troubleshooting/development/multipart-form-data.md): An overview of multipart/form-data generation in Unifi. - [Undefined error when building an integration](https://docs.sharelogic.com/unifi/troubleshooting/development/undefined-error-when-building-an-integration.md) - [Diagnostic](https://docs.sharelogic.com/unifi/troubleshooting/diagnostic.md) - [Installation](https://docs.sharelogic.com/unifi/troubleshooting/installation.md) - [Latest version of Unifi not accessible](https://docs.sharelogic.com/unifi/troubleshooting/installation/latest-version-of-unifi-not-accessible.md) - [Integration Responses](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses.md) - [Transaction has been processed already](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/transaction-has-been-processed-already.md) - [Initiating transaction not found for inbound receipt](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/initiating-transaction-not-found-for-inbound-receipt.md) - [Message has already been processed](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/message-has-already-been-processed.md) - [Message ID not found](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/message-id-not-found.md) - [Message is not valid for this bond](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/message-is-not-valid-for-this-bond.md) - [Message name not recognised](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/message-name-not-recognised.md) - [No retry for requests with 401 response](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/no-retry-for-requests-with-401-response.md) - [Unable to identify message name from request](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/unable-to-identify-message-name-from-request.md) - [Other](https://docs.sharelogic.com/unifi/troubleshooting/other.md) - [Dynamic stage does not render](https://docs.sharelogic.com/unifi/troubleshooting/other/dynamic-stage-does-not-render.md) - [Duplicate bonds on Request integrations](https://docs.sharelogic.com/unifi/troubleshooting/other/duplicate-bonds-on-request-integrations.md) - [Query Range ACL Errors](https://docs.sharelogic.com/unifi/troubleshooting/query-range-acl-errors.md): Troubleshooting: Query Range ACL Errors After May 2025 ServiceNow Patch - [Self-test](https://docs.sharelogic.com/unifi/troubleshooting/self-test.md): A suite of internal tests that can be executed at any time. - [Quick Tour](https://docs.sharelogic.com/unifi/about/quick-tour.md): A high-level overview of the Unifi application. - [Roles](https://docs.sharelogic.com/unifi/about/roles.md) - [Supported Features](https://docs.sharelogic.com/unifi/about/supported-features.md): Details of the API models & integration features Unifi supports. - [Application Modules](https://docs.sharelogic.com/unifi/about/application-module-overview.md): A quick overview of the Unifi Application and its modules. - [Data Model](https://docs.sharelogic.com/unifi/about/data-model.md): An overview of the table structure used by Unifi - [Transport Data Flow](https://docs.sharelogic.com/unifi/about/transport-data-flow.md): An overview of the flow of data through Unifi's built in message bus.