Difference between revisions of "Activity:DebugMessage (Activity)"
| Line 1: | Line 1: | ||
The DebugMessage Activity writes a string to the {{UBIK}} debugging service, which is i.e. displayed in the [[Debugger|Code- and Workflow Debugger]]. | The DebugMessage Activity writes a string to the {{UBIK}} debugging service, which is i.e. displayed in the [[Debugger|Code- and Workflow Debugger]]. | ||
| + | = Description = | ||
{{ActivityInfoBox | {{ActivityInfoBox | ||
| title = Debug Message | | title = Debug Message | ||
| Line 10: | Line 11: | ||
| version = 2.1+ | | version = 2.1+ | ||
}} | }} | ||
| − | |||
| − | |||
===Arguments=== | ===Arguments=== | ||
Revision as of 10:01, 10 March 2015
The DebugMessage Activity writes a string to the UBIK® debugging service, which is i.e. displayed in the Code- and Workflow Debugger.
[edit]
Description
| Debug Message | |
|---|---|
| Name | DebugMessage |
| Purpose | Output a string to the debug window |
| Category | Debugging |
| Returns | True if successful |
| Version | 2.1+ |
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() |
