> 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.2.2-dec-24-2020.md).

# 3.2.2 Dec 24, 2020

Release Notes 3.2.2

## Features 

1. Added the ability to print request parameters in console logs. 
2. GET\_FROM\_USER has been replaced with GET\_FROM\_CREDENTIALS in API Manager and Systems Page. 

   **Note**: We have provided backward compatibility to support GET\_FROM\_USER as well. We suggest using GET\_FROM\_CREDENTIALS in all API Managers and Systems page. 
3. Regex Modifier has been added. 
4. URL Validation added in Credentials Hostname field. 
5. Added Comment option in Mapping Fields.

## Bug Fixes 

1. Issue with nested array in Mapping is fixed. 
2. Fixed displaying the queue status even while the sync is running. 
3. Issue with Truncate Modifier is Fixed. 
4. Displaying other projects API manager data in API Handler is fixed. 
5. Fixed Detailed logs pop up misalignment. 
6. Change password 15 characters limitations added. 
7. Confirmation pop-up added to Reprocess Button. 
8. Fixed Mapping not populated issue if added in snippets.

{% hint style="info" %}
We are running a few background services to clean up old logs. So users will be able to see only the last two months' logs(Logs Summary, Detailed Logs, Console Logs). We will not retain any logs beyond two months.
{% 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.2.2-dec-24-2020.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.