> For the complete documentation index, see [llms.txt](https://cqube.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cqube.sunbird.org/release-notes/cqube-release-v1.3.md).
# cQube - Release Notes V 1.3
**1.** **Objectives of the cQube release 1.3**
cQube release version 1.3, as an upgrade to the cQube release 1.2 and 1.2.1 has been updated with a new reporting feature using UDISE data.
**2.** **Scope**
cQube product release features and issues are described in this version 1.3. This document describes the map based reports created using UDISE metrics and indices. The map based reports contain school rankings based on the UDISE data.
**3.** **Summary of the Product Features**
This document contains information on the following new features and enhancements to the existing features of the cQube product:
1. UDISE data map based visualization
2. Issues from the previous release have been resolved:
1. Continuous refresh issue
2. RAM size issue
3. Manifest file removal
3. Upgradation from 1.2.1 to 1.3
**Description of the Product Features**
**1. UDISE Visualization**
[CQB-531](https://project-sunbird.atlassian.net/browse/CQB-531), [CQB-539](https://project-sunbird.atlassian.net/browse/CQB-539), [CQB-136](https://project-sunbird.atlassian.net/browse/CQB-136), [CQB-134](https://project-sunbird.atlassian.net/browse/CQB-134), [CQB-133](https://project-sunbird.atlassian.net/browse/CQB-133), [CQB-137](https://project-sunbird.atlassian.net/browse/CQB-137), [CQB-131](https://project-sunbird.atlassian.net/browse/CQB-131), [CQB-135](https://project-sunbird.atlassian.net/browse/CQB-135), [CQB-128](https://project-sunbird.atlassian.net/browse/CQB-128), [CQB-130](https://project-sunbird.atlassian.net/browse/CQB-130), [CQB-132](https://project-sunbird.atlassian.net/browse/CQB-132)
| Sl No. | Feature | Description | Roles Impacted |
| ------ | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| 1 | Map based report | Map based reports have been created for the following metrics:
1. administration
2. arts lab index
3. community participation
4. enrollment
5. grant expenditure
6. ict lab index
7. medical index
8. nsqf
9. policy implementation
10. safety
11. school infrastructure
12. school inspection
13. school performance
14. science lab index
15. teacher profile
Each of these metrics have indices in them which have been described in a document attached to the JIRA ticket CQB-133
| Admin, Report viewers |
**2 Issues from the previous release**
[CQB-480](https://project-sunbird.atlassian.net/browse/CQB-480), [CQB-527](https://project-sunbird.atlassian.net/browse/CQB-527), [CQB-525](https://project-sunbird.atlassian.net/browse/CQB-525)
| Sl No. | Feature | Description | Roles Impacted |
| ------ | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- |
| 1 | Continuous refresh issue | Continuous refresh in incognito window for admin screens [CQB-480](https://project-sunbird.atlassian.net/browse/CQB-480). | |
| 2 | RAM Size issue | During installation, the RAM size validation is allowing upto 100% of the system RAM size. It should ideally allow only 70% of the RAM to be used. [CQB-527](https://project-sunbird.atlassian.net/browse/CQB-527) | Admin, Report viewers |
| 3 | Manifest file removal | Removed manifest file validation in Static data ,Diksha, semester and infra nifi processor groups, Student attendance and CRC and validations in all the processor groups. [CQB-525](https://project-sunbird.atlassian.net/browse/CQB-525) | |
**4.** **Known Issues:**
This is a section that describes all the known issues/ bugs that are present in the cQube product and they have been reported as being a part of this release.
| Sl No | Issues |
| ----- | ------------------------------------------------------------------------------------------------------------------------ |
| 1 | Infrastructure column validation issue - [CQB-561](https://project-sunbird.atlassian.net/browse/CQB-561) |
| 2 | Nifi restart issue while semester data file processing - [CQB-562](https://project-sunbird.atlassian.net/browse/CQB-562) |
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cqube.sunbird.org/release-notes/cqube-release-v1.3.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.