> 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.3-april-8-2020.md). # 3.1.3 - April 8, 2020 Release Notes 3.1.3 ## Features and Improvements 1. OAuth2 support added 2. Mail Templates updated for all sort of emails 3. Project/Group owner name added for all kind of invitations 4. Pricing moved to live. Need to provide Valid Card details after the trail period expired 5. Added Icons for selecting plans in registration page 6. MySQL handler added in flows - Supports to generate MySQL queries 7. Cron Job added to delete jobs from DB 8. Enable/Disable all pipes added integration grid page ## Bug Fixes 1. Unable to add Custom Index issue fixed 2. Fixed Token URL tab not getting displayed for Cookies Authentication 3. Page not working issue after Project Transfer fixed 4. Fixed Array To array mapping issue in Root Level of the JSON 5. While cloning new project, CLONED prefix will be added only in the project name. 6. AutoMode will be turned off of for the cloned integrations 7. Fixed Last Sync time not getting Displayed for Dynamic pipe --- # 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.3-april-8-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.