It is my first time using ACTION with an IFS REST Connector for Cloud in Boomi. I am specifically using the Invoke action “PromoteToObsolete” on a document. This is the Post request:
I am currently receiving a Bad Request so there must be something wrong with the way that I am passing the parameters.
Before my Connector, I set up a “Set Property” shape of a Dynamic Process Property that contains he value that I will be using for the Bound Entity Set Parameters:
After that, I connected it to my Connector. In the Dynamic Operation Properties tab, I call on the DPP that I set earlier as the Bound Entity Set Parameters. (in additional, I added the E-Tag because I saw that it was required in the API doc)
For the Bound Entity Set Name, I just added it into the Operation since it will never change:
Is there something that I am missing or do I have to adjust the way I set up the multiple parameters?
Best answer by jamie.malangyaon
The issue has been resolved. I forgot to mention that this API call worked in Postman but did not in Boomi. This is a bug with Boom and REST Connectors as per a Boomi Support:
The issue you are encountering is a known problem when using the Boomi Rest Client Connector.
The Rest Client Connector can send a body with GET requests, which is not standard and can lead to errors if the API does not expect a body.
This behavior differs from tools like Postman, which typically do not send a body with GET requests unless explicitly configured to do so.
These were the steps that were taken to fix it:
1) Clear the Document Path by placing a blank message step before the Rest Client Connector in your process. This will clear any document content that might be inadvertently sent as a body with the GET request.
2) Use a Branch Step by introducing a branch step before the Rest Client Connector. Ensure that the connector is on a path that does not carry any document content that could be sent as a body.
The issue has been resolved. I forgot to mention that this API call worked in Postman but did not in Boomi. This is a bug with Boom and REST Connectors as per a Boomi Support:
The issue you are encountering is a known problem when using the Boomi Rest Client Connector.
The Rest Client Connector can send a body with GET requests, which is not standard and can lead to errors if the API does not expect a body.
This behavior differs from tools like Postman, which typically do not send a body with GET requests unless explicitly configured to do so.
These were the steps that were taken to fix it:
1) Clear the Document Path by placing a blank message step before the Rest Client Connector in your process. This will clear any document content that might be inadvertently sent as a body with the GET request.
2) Use a Branch Step by introducing a branch step before the Rest Client Connector. Ensure that the connector is on a path that does not carry any document content that could be sent as a body.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
