Difference between revisions of "Activity:DebugMessage (Activity)"
(→Usage) |
(→Arguments) |
||
| Line 26: | Line 26: | ||
|- align="left" | |- align="left" | ||
| Text || String || In || The text to be written | | Text || String || In || The text to be written | ||
| + | |- align="left" | ||
| + | | Result|| Boolean || Out || Returns True on success, false on error | ||
|} | |} | ||
Revision as of 11:33, 19 July 2013
The DebugMessage Activity writes a string to the UBIK® debugging service, which is i.e. displayed in the Code- and Workflow Debugger.
| Debug Message | |
|---|---|
| Name | DebugMessage |
| Purpose | Output a string to the debug window |
| Category | Debugging |
| Returns | True if successful |
| Version | 2.1+ |
Arguments
| Arguments | Type | Direction | Purpose |
|---|---|---|---|
| UBIKObject | BaseClass | In | A UBIK object |
| Text | String | In | The text to be written |
| Result | Boolean | Out | Returns True on success, false on error |
Usage
This activity is typically used to output debug information like variable values, object properties etc. during the execution of a workflow.
 | Once your workflow runs smoothly, consider removing the DebugActivities you used during design. They are lean but they still consume resources! |
