> 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/design-considerations-and-frameworks/frameworks/web-services-framework/web-services-framework-advanced-topics.md).

# Web Services Framework - Advanced Topics

## 1. Onstart Logicnets

When you want your application to perform common initialization tasks when it starts, you can create and put those logicnets in the *onstart* folder of your project. You can put as many logicnets as you want in this folder, and the system will execute them in the order they appear in the folder.

The logicnets the system calls in the *onstart* folder have access to the same context as the end-point logicnets, so they can access the \_\_in and \_\_out data-objects to retrieve input data or to write data to the output data objects.

## 2. Custom Input and Output Data Conversion

You can specify custom input and output data convertors; for example, to support custom data formats or to perform data validation on the input data. You specify your data convertors in the Framework settings tab.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-50567d09bd388db2f654986d0d2ee91e379a0d05%2F79fcc0a5-0583-493b-9022-72853fddfa1b.png?alt=media)

Note: If you specify a data convertor, the system bypasses the standard framework data convertor. This means that you will have to perform data conversion for all the data formats that you want to support. You can use the information from the ‘**request\_info**’ to determine the data format of the input data.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f7b2e4d1350767f924cf56b123aad7582df4e6eb%2F234efd9f-d9cd-44d7-b0d2-06449f7c642a.png?alt=media)

Data convertors have access to the same context as the end-point logicnets, so they can access the \_\_in and \_\_out data-objects to retrieve input data or to write data to the output data objects.

## 3. Logging Inbound Calls

For troubleshooting, set *log\_inbound\_ws\_calls = 1* in the *\_session* section of the company *settings.cfg*. The framework then writes one log file per call to *dat\bnt\\\log\ (\_webservice\_\_\_.log)* with the request and the response.

The system writes passwords, secrets, API keys, and tokens in the request and response as \*\*\*\*\*\*\*\*, but the client still receives the real response. To mask such values yourself, for example before you write them to your own log or database, use the Mask sensitive data part.


---

# 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/design-considerations-and-frameworks/frameworks/web-services-framework/web-services-framework-advanced-topics.md?ask=<question>&goal=<user_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.