How can you debug Workflow 5 Objects to inspect them?

Permanently deleted user

January 12, 2018 09:59

Hi,

I am starting out with workflow 5 and I need a way to see objects and their properties. I tried chrome debugger but cant see how to find he WF5 form object when using the sand pit. Also I tried to use JSON.stringify within an alert serialise an object but it errors with JSON as undefined.

0

• 

  Stefan Schweigert

  January 12, 2018 16:12

  Hello Marco,

   

  There's a few different ways to inspect your workflow. If you run the workflow in the Sandbox, you can view the inputs and outputs of your workflow in the Chrome Console by setting the logging level to display all levels of errors (Verbose, Info, Warnings, Errors). You can view these same inputs/outputs in GVH by adding the &debug=true to the end of your URL and viewing the console during the execution of the workflow. Another option is to use the Log activity with an entire object or a property within the object, which will then be written out to the browser console (e.g. for Display Form, the input for Log could be =$form1.state.checkBox1.value or =$form1).

   

  Thanks, Stefan

  0
• 

  Permanently deleted user

  January 12, 2018 20:09

  Hi Stefan,

  thank you for the prompt reply. I got what I needed by adding a log and specifying =$form1.state.geometryPicker1.value to display it in the console.

   

  What I did not understand in your reply is how to go about the other options?,

  How do I go about "setting the logging level to display all levels of errors", is that a parameter in my work flow or is it a Chrome setting?

  What is GVH?

   

  Regards

  Marco

  0
• 

  Stefan Schweigert

  January 12, 2018 20:16

  Hi Marco,

   

  No problem.

   

  In the Google Chrome Developer Tools, just below the main toolbar, is a bar which has a Filter and a dropdown where you can configure the log levels.

   

  GVH is an acronym for the Geocortex Viewer for HTML5, which is one of the client applications where you can execute workflows within, the other being the Web AppBuilder.

   

  Thanks, Stefan

  0
• 

  Permanently deleted user

  February 14, 2019 15:53

  Good news, everyone! I discovered dev mode for GVH today, and need to spread the word.

   

  Do you want to watch your workflow work without all those pesky 'ViewDeactived', 'LayerUpdate', 'TraceEvent' etc messages clogging your log? LatGeo is right there with you, and one step ahead of you (or at least, of me).

   

  Instead of using "&debug=true", use "&dev=true". You, and your browser, will be happier for it.

  0

Please sign in to leave a comment.