Difference between revisions of "Activity:DebugMessage (Activity)"
m (moved Activity DebugMessage to DebugMessage (Activity)) |
(→Example) |
||
| Line 46: | Line 46: | ||
| UBIKObject|| Connect this argument with a variable | | UBIKObject|| Connect this argument with a variable | ||
|- align="left" | |- align="left" | ||
| − | | Text || <source lang = "vbnet"> | + | | Text || <source lang = "vbnet">UBIKObject.MetaClass.AllDerivates.Count.ToString()</source> |
|} | |} | ||
Revision as of 07:33, 23 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+ |
Contents
Argument
| Arguments | Type | Direction | Purpose |
|---|---|---|---|
| UBIKObject | BaseClass | In | A UBIK object |
| Text | String | In | The string to be written to the debugging service |
| 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! |
Example
Output the number of MetaClasses that derive (direct and indirect) from the MetaClass of a given object:
| Argument | Value |
|---|---|
| UBIKObject | Connect this argument with a variable |
| Text | UBIKObject.MetaClass.AllDerivates.Count.ToString() |
