You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When testing a form, or even with a deployed form, we should provide the form author with visibility on the service, without having to looks at logs. This should include showing:
the request, including URL, headers, and body
the response, including headers, and body
This must also work for SQL services, and show the actual SQL query and parameters used, as well as the resulting XML.
Showing what caused the service to run (action) would be good too.
The text was updated successfully, but these errors were encountered:
+1 from me today, including some context from the actions, for example: action such and such is running because of this event and condition, then calling this service with such and such parameters, then handling the response in such and such way, etc.
This would be useful for deployed forms, maybe in some "dev" mode.
When testing a form, or even with a deployed form, we should provide the form author with visibility on the service, without having to looks at logs. This should include showing:
This must also work for SQL services, and show the actual SQL query and parameters used, as well as the resulting XML.
Showing what caused the service to run (action) would be good too.
The text was updated successfully, but these errors were encountered: