Improve debugging options for server workflows
It's hard to debug a server workflow because there is no console windows like we have for client workflow. Some things that don't help either are:
- I can get the workflow ‘ticket’ from the developer console, but to see the logging, I have to manually append it to https://example.com/geocortex/workflow/service/job/logs?ticket= . Only if the server workflow actually throws an error, a direct link can be found in the console. Sometimes I add a Throw activity at the end on purpose, so that I can get to the output more easily
- Debug logging is only written if I explicitly use Set Log Level with debug in the workflow itself. I always need to remember to change that back in a production environment
- There seems to be no logging of the activities that are executed, nor of their inputs and outputs.
Things that would make our life easier:
- Be able to set a system wide log level, like how it used to work in Geocortex Essentials
- Include more logging by default (if log level is set to debug), so I don't need to log all steps manually
- Always show a link to the workflow's output, or maybe only if log level is set to debug
3
Please sign in to leave a comment.
Comments
0 comments