Best Way to Debug a W
-
I have a workflow that after being run from the viewer yields a "GenericNull error". I have not yet figured out what's causing this. Yet, when I run the workflow in the workflow simulator, the workflow DOES NOT yield an error??? When during a simulation of my workflow, I've tried several levels of logging debug access/system log levels to the bottom console, with NO identifiable results or NO indication that the work has a generic null error....!!!
This new field requires the user input a date with the format of 'mm/dd/yyyy' But when I explore the input scope of the textbox in the design form environment, I only see one type called 'date' but it's format is unknown.
One final observation...during a workflow simulation, I can see that during the creation of my dictionary that textfield6 (my new field) does carry the value of what I keyed in.
What debugging capabilities can anyone offer on how to further isolate this persistent error?
Walter
0 -
The easiest way is still to use Log activities. When all else fails, I insert a Log after each activity, so I can see which activity causes problems. But since you say that the error is raised after the workflow is run, this may not give you much information. Unless it's the last activity in the WF that fails. BTW log messages are not sent to a console, but rather to the Essentials logfile(s), e.g. "Geocortex Essentials\Default\REST Elements\REST\App_Data\Logs". The loglevel can be set in the Essentials Manager.
If the problematic activity deals with ArcGIS Server, (http://www.telerik.com/fiddler) Fiddler can also be usefull, it can show you whatever http requests are sent to AGS, for instance. You may have to run it on the server where Essentials is installed, and modify web.config so that http traffic is actually using Fiddler as a proxy.
0
Please sign in to leave a comment.
Comments
2 comments