The test failure is from the remote endpoint returning a 404 "not found" response. this is indicated in the error response (http code : 404, errorCode: "action.remote_endpoint". This means the data action successfully reached the remote endpoint, and that the remote endpoint was unable to locate the resource requested.
If this had been an issue with a misconfigured request body, I would have expected the remote endpoint to respond with a 400 bad request.
I would recommend retrying your test with a known good set of inputs.
------------------------------
Richard Schott
Genesys - Employees
------------------------------
Original Message:
Sent: 12-13-2021 01:24
From: Vinayak Vagal
Subject: Data Integration
Hello Paul,
thanks for your suggestion.
As per the your1st point i have removed the root object and it works to get publish. however I do not understand about attributes implementation. where i can create the attributes. as the API developed by client side. need some help to get this done.
Note: i am less friendly with API part and configuration
Please find the screen short : now its falling the Test
------------------------------
Vinayak Vagal
SmartConnect Technologies Pvt. Ltd
------------------------------
Original Message:
Sent: 12-10-2021 11:26
From: Paul Simpson
Subject: Data Integration
It's a little difficult to see from the screenshots, but it looks like the second one is your Input contract?
Anyway, try removing the name for the root objects in the schemas.
Also, for the other two, make sure you have put the attribute name in, currently the two booleans appear to be unnamed.
------------------------------
Paul Simpson
Senior Technical Instructor