You are using a PUT, that is to modify an existing entry. If you are wanting to create a work log entry, you'll need to use the POST to the proper URL
Can you give me an example because POST method is not allowed for the Modify URL in REST.
I use this URL, because in SOAP the work info note is part of the Modify action of the HPD_IncidentInterface_WS.
Also from SOAP, it always creates a new entry from the "modify" method, it does not change existing entries.
I found the rule that is responsible for the action:
I am not sure why it is working from SOAP modify, but it doesn't work from REST.
Also I think that REST PUT acts as overwrite on the Incident fields and it doesn't check if there was a previous value or not for the chosen field.
1 of 1 people found this helpful
I was thinking purely about creating a Work Log entry (ya know, manually, not through workflow)....so...I've looked at the workflow in question.
So, looking at your example above, yes, if you want to replicate what you have in SOAP, you are correct to use a modify of the Interface form...but, you need to ensure that you provide the same inputs....because of the resolution of your screen shot from soap, and from the fact that it doesn't show all of the input elements, it's hard to tell what you have the 'z1D Action' value set to...but it goes to reason that you would have it set to 'MODIFY', but in your REST example, you aren't setting it at all....so you might want to add that to your JSON, and ensure that you have everything else populated that you have in the SOAP as well. That appears to be the only missing piece though.
To expand on that you might want to log on the server side (API/FIlter/SQL to a single file is my favorite combo) a SOAP transaction and a REST transaction and see where the workflow starts to deviate in the REST transaction.