> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/others/release-notes/3.3.6-july-20-2022.md).

# 3.3.6 July 20, 2022

Release Notes 3.3.6

## Features/Improvements

1. Console log viewer in logs page. Console logs files with size less than 2 Mb can be now viewed directly in browser. 
2. Improved the layout and design of Credential page and all grids. 
3. Provided capability to add dependency between fields in flow handlers 
4. Bower components has been removed and all the images are moved to CDN for better performance. 
5. Added systems filter in API Manager grid page. 
6. Option to provide page number in grids.

## Bug Fixes

1. Occasional mapping errors when created from templates - fixed. 
2. Configuration values become empty when created from templates - fixed. 
3. System / API is not mapped in Snippets when created from templates - fixed. 
4. Issue while re-entering TOTP in login page - fixed. 
5. Logs page Duration display issue when ran in milliseconds - fixed. 
6. Adding user group to project issue in rare cases - fixed.

{% hint style="success" %}
Lightning Services are updated to v3.3.6
{% endhint %}


---

# 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://docs.dckapintegrator.com/others/release-notes/3.3.6-july-20-2022.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.