Add Answer to Change Log
Description
The Add Answer to Change Log part will post a customizable key, value, and other information to the changelog table during application runtime in preparation and for use with the Standard Reporting Package session log tables and any advanced or client-specific reporting.
Use this part to add your own logging information at any point in the execution of your business logic model. You can flag any event, such as an action, or an add, delete, or close process for any number of different "keys" and their corresponding "value" and meta data every time the logging part is traversed by the LogicNets runtime engine.
Use
This part is accessible from the Misc menu in a process node in all frameworks. You could use this part for the following:
- to supplement the application logging that is standard within the LogicNets platform. See Logging Events in LogicNets article for more information.
- to log business information like the type of transaction, summary numeric calculations, department, machine, or serial number to use for weekly, monthly, or yearly analysis.
Editor Fields
| Field Name | Description/Use | Type/Options | Optional/Mandatory |
| Action | Choose the type of action that you want to log. Action is a separate column in the changelog table and that you can use to sort or filter results. The system only logs update actions on a change in the value of the targeted variable, as specified in the value field within a session. |
Event | Update | Delete | Close |
Mandatory |
| Key | Enter the name of the key associated with this logging event. Keys are typically organized in a structured data string separated by a period (.). Existing structures that can be adopted by these custom events include the following. There is no theoretical limit to the number of levels, but keys should be kept short and succinct for ease of reading and downstream analysis.
|
Text | Optional |
| Value | Enter a value or reference in $(...) format to store against the key. | Text | Optional |
| Database | Include the name of the database from which the value is sourced, if required. The default action is to leave this field blank. | Text | Optional |
| Referenced Meta Data | Include any collection of meta data associated with the event here. This will be reported in the meta data column of the changelog. | Collection | Optional |
| Manual Meta Data | Add individual additional key/value pairs in this grid, as required. This will be incorporated into the meta data column of the changelog. | Text | Optional |
Testing Custom Logs
The system adds all logging events to the changelog.db, which you can view in real time in the Standard Reporting package.
Choose Logs from the dropdown list of reports to see all the automatic logging events, and verify the system added your custom logging at the right time and with the right information.
You can filter, sort, and tailor the Standard Reporting package view of logs to show you the most pertinent information.
