Difference between revisions of "Activity:DebugMessage (Activity)"
(→Example) |
|||
Line 16: | Line 16: | ||
− | == | + | ==Arguments== |
{| class="wikitable sortable" | width = "50%" | {| class="wikitable sortable" | width = "50%" | ||
|- | |- | ||
− | ! | + | ! Argument!! Type !! Direction !! Purpose |
|- align="left" | |- align="left" | ||
| UBIKObject|| BaseClass || In || A UBIK object | | UBIKObject|| BaseClass || In || A UBIK object |
Revision as of 08:01, 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
Arguments
Argument | 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() |