Very basic workflow question about variables
I am hoping for a quick answer here. Not sure I have ever had a reply to a question yet, but here goes. We have a workflow that just stopped working and we have no idea what changed. We think we have found a variable linked to the issue. How do we view the value of variables as we are debugging a workflow and trying to identify the problem. This was covered in the class we took 3 years ago, but can not remember.
0
-
You can add an Alert activity to the workflow and put the name of the variable in the Text property.
If the data type of the variable is not String, add .ToString to the name of the variable.0 -
Thanks! We will do that. When I passed that info along, that wasn't what they were looking for, but we can do it this way. 0 -
How about writing to a log file? Any idea how to do this? 0 -
Hi Michael,
You can use the log activity (to write to the system.log file in the following directory: C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\REST\App_Data\Logs), or you can use the Log External activity to write to the viewer log. Note the viewer log will only log from the client side, and the information is lost when the user refreshes, so if you are looking for long term logs, using the Log activity is better.
Make sure you set the log level in the activity to the corresponding log level you've set in manager (under "Application Settings"). The log activity will do you no good if you have it set to log at the info level, but Essentials is only set to log Warnings and higher.
When I'm debugging something, I usually use the External log activity, if it's a quick one off check (for example checking to see the contents of a variable). It's like using an alert box as Nico described, but you can leave it in the workflow without impacting the users.
I hope that helps!
Thanks,
Danny0 -
Thanks Danny! 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
5 Kommentare