Testing Inbound Integration Handlers
Choose "Import and Process Message". The following applies:
- An integration event entry gets created and you will be prompted to select a file
- The integration is then triggered as if the file had been received externally
Processing Integration Messages in the Background
You can configure inbound integrations messages to be processed in the background. This is useful for large payloads to prevent timeouts. When an inbound integration message is set to process in the background, the message creates an entry in the Integration Job Queue Entry and the integration message gets completed.
The message will only get validated in the background process. If you want to check the status after processing, you need to make a separate call.
Integration Job Queue Entry
When access is granted to Business Central using AAD Applications, the users are not considered licensed users and therefore cannot create scheduled tasks. This impacts integrations that need to do some background processing - primarily those that are set to run as a job queue.
To overcome this limitation, a new queue has been created to allow these messages to be queued. When a message is received and the configuration is to process through a job queue, the following applies:
- A record is created in the Integration Job Queue Entry table. This table has similar fields to the Job Queue Entry.
- A job queue entry configured to run
Codeunit 58312 - ProcessIntJQEntries_IF_TSLthen reads the new queue table and creates a Job Queue Entry to handle the background process.
This approach ensures that the actual Job Queue Entry only every gets created from a licensed user. Additional cues have been added to the integration activities page to report on the status of these records.