> 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.1.5-may-15-2020.md). # 3.1.5 - May 15, 2020 Release Notes 3.1.5 ## Features and Improvements 1.Registration Page Design Updated 2\. Handlers Added/Updated: * ‌JSON to CSV Conversion added in "Formatter" Handler * Pagination Handler added * While loop Handler added * Break Handler added 3\. Admin Analytics feature added to track the usage of the Integrator Users 4\. Force Login added in DCKAP Integrator Admin side. Global password will not work anymore. Admin has to request the user to enable "Force Login" in their Account settings. 5\. Plan Description added in "Plans and Pricing" page. 6\. Auto complete disabled in all forms. 7\. Copy URL message Updated for Dynamic Pipes. ## Bug Fixes 1.Freeze account after the expiry of the trail fixed. 2\. AutoPilot issue fixed. 3\. Trial/plan expired users will not be able to create projects. --- # 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.1.5-may-15-2020.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.