It would be good if that would be possible. Especially in relation to to Xtensions. You could group a set variables to an object in WF designer or form designer. Also, you could create arrays of complex types then.
If an API requires an array of objects or other arrays as property its not possible to integrate it through a Xtension.
For us thats a annoying limitation, cause trivial request are not possible by custom connectors.
If the API requires OAuth2, you also can not use call a webservice.
I had multiple cases where I would have needed that.3 votes
If a workflow contains a custom action from another environment, and then the workflow is imported into another environment, without that custom action. The import will fail.
Please implement a mechanism to cope with missing actions, so that the workflow can be imported in and give the end user the option to remove the incompatible action.10 votes
I was working with Google Sheets API and found that I am not to get some actions to work such as append values.
After further investigation, it appears that I need the format to be a collection inside a collection.
I tested different ways but ultimately could not get that format.21 votes
This functionality was release in R120: https://help.nintex.com/en-US/platform/ReleaseNotes/NintexWorkflowCloud.htm
Currently if a xtension responds with a code other than 2xx the call is considered to be a failure.
However many APIs legitimately return a status-code other than 2xx. For example if you query a service and no results are found, many APIs return 404 - "Not Found". This is a valid response and I would like to react on this response within the workflow. Many times this would result in either creating a new record (if a query returns 404) or updating an existing record (if a query returns 200).11 votes
Thanks for your suggestion! It’s a great idea, I’ve added it to our backlog for Xtensions. I’ll keep this ticket updated as the request progresses through.
- Don't see your idea?