Jump to: navigation, search

Difference between revisions of "Activity:DebugMessage (Activity)"


 
(7 intermediate revisions by 2 users not shown)
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]].
 +
= Description =
 
{{ActivityInfoBox
 
{{ActivityInfoBox
 
| title = Debug Message
 
| title = Debug Message
Line 9: Line 11:
 
| version = 2.1+
 
| version = 2.1+
 
}}
 
}}
The DebugMessage Activity writes a string to the {{UBIK}} debugging service, which is i.e. displayed in the [[Debugger|Code- and Workflow Debugger]].
+
===Arguments===
 
+
 
+
 
+
 
+
==Arguments==
+
  
 
{| class="wikitable sortable" | width = "50%"
 
{| class="wikitable sortable" | width = "50%"
Line 20: Line 17:
 
! Argument!! Type !! Direction !! Purpose  
 
! Argument!! Type !! Direction !! Purpose  
 
|- align="left"
 
|- align="left"
| UBIKObject|| BaseClass || In || A UBIK object
+
| UBIKObject|| [[BaseClass]] || In || A UBIK object
 
|- align="left"
 
|- align="left"
| Text || String || In || The string to be written to the debugging service
+
| Text || {{String_MSDN}} || In || The string to be written to the debugging service
 
|- align="left"
 
|- align="left"
| Result|| Boolean || Out || Returns True on success, false on error
+
| Result|| {{Boolean_MSDN}} || Out || Returns True on success, false on error
 
|}
 
|}
  
==Usage==
+
===Usage===
  
 
This activity is typically used to output debug information like variable values, object properties etc. during the execution of a workflow.
 
This activity is typically used to output debug information like variable values, object properties etc. during the execution of a workflow.
Line 33: Line 30:
 
{{Hint|Once your workflow runs smoothly, consider removing the DebugActivities you used during design. They are lean but they still consume resources!}}
 
{{Hint|Once your workflow runs smoothly, consider removing the DebugActivities you used during design. They are lean but they still consume resources!}}
  
==Example==
+
=Example=
 
+
 
Output the number of MetaClasses that derive (direct and indirect) from the MetaClass of a given object:
 
Output the number of MetaClasses that derive (direct and indirect) from the MetaClass of a given object:
 
  
 
{| class="wikitable" | width = "50%"
 
{| class="wikitable" | width = "50%"
Line 46: Line 41:
 
| Text || <source lang = "vbnet">UBIKObject.MetaClass.AllDerivates.Count.ToString()</source>
 
| Text || <source lang = "vbnet">UBIKObject.MetaClass.AllDerivates.Count.ToString()</source>
 
|}
 
|}
 +
 +
{{Activity/End}}
  
 
==See also==
 
==See also==
 
* [[Workflow Designer]]
 
* [[Workflow Designer]]
  
[[Category:Workflows]] [[Category:Activities]]
+
[[Category:Activities]]

Latest revision as of 10:23, 19 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.

IC Hint square.pngOnce 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()


See also