WELCOME TO THE COMMUNITY
find what you are looking for or ask a new question
Home > Forum > Latest posts

latest posts

MVP

Hi AndreeLi
I don't have an answer how you could deal with this error other than writing an SDK, but i've an explanation why it happens.

Webcon API is created using Swagger (OpenAPI) specification, so i would assume, that they are also using some kind of library to execute REST API actions.
Based on HTTP specification RFC 7231*
> A payload within a GET request message has no defined semantics;
sending a payload body on a GET request might cause some existing
implementations to reject the request.

GET requests shouldn't have a Body - data should be contained within the path or query part of the url, so properly implemented library shouldn't allow sending body when the verb is GET, and that is exactly what happens.

* https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.1
* https://stackoverflow.com/questions/73443585/why-http-get-with-request-body-in-swagger-node-js-not-working
* https://stackoverflow.com/questions/978061/http-get-with-request-body/38625554#38625554

Hello,

I have an external API: GET https://domain.com/api/employee/GetAll
I have created a process using REST API that get token, then get Employee. (START - FINISH)
GetAll - Retrieve the employees list. The HTTP verb for this method is GET.

When i run the process manually, it works. I have created a global cyclical action that starts my workflow (every day run), but it doesn't work:

Response Code:

Exceptions:
Error occurred : Cannot send a content-body with this verb-type.
System.Exception: Error occurred : Cannot send a content-body with this verb-type.
at WebCon.WorkFlow.BusinessLogic.Actions.Logic.Webservices.REST.ActionRunner.GetNotSerializedResponse(RestLogger log, Boolean expectContinue)
at WebCon.WorkFlow.BusinessLogic.Actions.Logic.Webservices.REST.InvokeRESTWebServiceAction.<FireActionAsync>d__5.MoveNext()



Do you have any ideas why it is happening?
Version 2023.1.2.68


Thanks.

Hi community!


I have to remove all privileges (except the author of the element) on current workflow element for security reasons.

I tried putting the action 'On exit' of the current step, before executing all other actions (assigning tasks, adding certain privileges, ...) on path to next step.

According to an old documentation 'On exit' actions should be executed first and should not be dependent on the path, that was taken.

Unfortunately the action 'Remove privileges' is always postponed and removes all the privileges / tasks which were set on path, which is not the expected behaviour.

Is there any way to execute this certain action before any other actions?


Thanks a lot in advance, Nik

In reply to: Jacek

Hi Nikolaus,
I don't know if I understood the problem correctly but maybe instead of the "declare" section (1) you should just use the attribute value from the "Form fields" section (3) in place of (2).

Regards,

Hi Daniel & Jacek!

Thanks a lot for the answers.

I initially tried with Form field, but it did not work in the first step (New Form) for no obvious reason. I also was unable to identify, which exact SQL statement was executed here. I think this could be a Webcon bug.

Step Id is not a problem at all, this is working in the new form.

The working solution is a common datasource, which has an additional filter set in designer studio.

Best regards, Nik