> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/add-answer-to-change-log.md).
# 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](/release-9/design-considerations-and-frameworks/frameworks/reporting-framework/standard-reporting.md) 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](/release-9/platform-documentation/system-administration/system-settings/logging-events-in-logicnets.md) 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.
- session.\[key\_name]
- authentication.\[key\_name]
- application.\[key\_name]
- runtime.\[key\_name]
| 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.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/add-answer-to-change-log.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.