Unable to Access Response Body from Outbound AS2 Connection for Use in Downstream Flow Steps

Integrator.io
, ,
1

Hi Celigo Community,

I'm working on an outbound AS2 integration in Celigo (integrator.io) where we send AS2 messages to a trading partner. After the message is sent, I need to capture the response body returned by the partner's AS2 endpoint and use that data in the subsequent steps of our flow — but the response body is coming back empty or missing entirely.

I'd love some guidance on how to correctly retrieve and pass this response data downstream.

2

You've about come at the perfect time. We have a release going out next week where you'd be able to do exactly this. Adding in @sreeneshc as he is the product manager for it and can confirm if I'm incorrect.

3

Hi @Shrehith_K1 If you are looking for the MDN response from the trading partner, please wait until May 7th.

Post release we will be capturing and mapping MDNs to their respective EDI records. You can seamlessly retrieve this data via API for your downstream processing.

Shall be able to help you out with the API information soon.

4

@Shrehith_K1 This will be a two step process to fetch the MDN for the downstream processing.

  1. Post sending the message to the destination, you need to add a new import step in the flow to hit the API /ediTransactions/query with the documentNumber as a input (ex: Purchase order number, Invoice number etc.) which is populated on the EDI activity dashboard.
  2. From the generated response of the above step you'd need to fetch the 'Id' and pass onto a new step by initiating a request to the API /ediTransactions/:_transactionId/mdn (replace the fetched ID with _transactionId in the API call).

This functionality shall be available from May 7th.

5

Hey,
Is this functionality Available Now ? Please can you guide me on fetch the MDN Details in my Downstream Flow using an example ?

6

6a046e8687d2ad85712c66ef (1).zip (17.0 KB)

Please refer to the Steps 3&4 from this zip.

  • While the Step3 is fetching the record information of the transaction.

  • Please make changes to the result mapping in Step2 as per your document type. In the sample it is hardcoded to 'Invoice number'

  • Step4 fetches the MDN information for that specefic Invoice in this usecase.