Difference between revisions of "Activity:WriteLogEntry (Activity)"
m (Text replacement - "Workflows" to "") |
|||
| Line 49: | Line 49: | ||
* [[Workflow Designer]] | * [[Workflow Designer]] | ||
| − | + | [[Category:Activities]] | |
Revision as of 12:49, 3 February 2015
| Write Log Entry | |
|---|---|
| Name | WriteLogEntry |
| Purpose | Write a log entry via the UBIK® logging mechanism |
| Category | Logging |
| Returns | True if successful |
| Version | 2.3+ |
The WriteLogEntry Activity writes a log message to the UBIK® logging mechanism.
Contents
Arguments
| Argument | Type | Direction | Purpose |
|---|---|---|---|
| UBIKObject | BaseClass | In | An UBIK® object |
| LogId | Integer | In | A user defined id to use for this log entry |
| Text | String | In | The message text to be written in the log entry |
| Title | String | In | The title of the log entry |
| Result | Boolean | Out | Returns True on success, false on error |
Usage
This activity is typically used to write information into a log file to document certain events like failures together with object properties etc. during the execution of a workflow. The location for this logfile can be configured by the user by editing the Web Service Configuration in section loggingConfiguration. For configuring the logging in UBIK.Studio, the section loggingConfiguration also exists in the Application Config file.
 | Once your workflow runs smoothly, consider removing frequently appearing log entries you needed during the design phase. Please be aware that the intense use of log output needs system resources and can generate confusing amounts of information! |
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() |
