I'm not entirely sure if you are consuming or publishing a rest service. As you are using httpmethod put I would say consume, but on the other hand you mention you want to receive data. Plus your stacktrace implies publishing.
From the stacktrace:
Cannot publish microflow MyFirstModule.PutIssue, it should exist and have exactly zero or one argument
Did you try to only have the issue entity as microflow parameter?
Hi Henry,
It is perfectly possible to use multiple values as input for an argument, however, you should wrap those values in one single transient object. So if you create a domain model transient entity:
MyArgs
------
issueid : integer
issue : string
reason : string
Your microflow should then have one argument of the type MyArgs. After that you are free to mix and match stuff from the url and the document body.
You could for example use an url like /submitissue/{id} and send json body { issue : string, reason : string }, but you could also use a template /submitissue/{id}/{issue} with { body : reason } or no body at all.
I tried doing this, however, this is the only way I could get it to work.
As you can see I have to specify the IssueViewIdWrapped_IssueView relationship in the body payload. Is there a way I can get this to work when I only supply the "Issue"-entity in the body?