> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/local-governance/v2.8/platform/configure-digit/services-overview/business-services/dashboard-analytics-backend/dss-features-enhancements.md). # DSS Features Enhancements V2 Technical Document for UI ## Overview This release for DSS focuses on improving user experience and the ability given to the user to get deeper insights using drill-through and comparison indicators in tables. The release includes the following features: * Breadcrumbs for better navigation * Drill through options in tables and charts * Comparison indicators in Table ### **Breadcrumbs For Navigation** In addition to the left navigation panel, the addition of breadcrumbs is also useful to provide a better sense of the current page insight. It is also very much helpful for mobile navigation. The user can navigate using the breadcrumbs by clicking on the required parent menu. *Technical Implementation Details* It Works based on the Current Route URL and previous Route URL File Details - ### **Drill through options in tables and charts** The ability provided in DSS to configure the drill through for required options in tables as well as charts. The drill through options is useful in configuring the required hierarchy of data set. This helps users to go up to 'N' levels to get deeper insights **Technical Implementation Details:** Drill down/drill through in tables, is based on the drillDownChartId and filter. Here chart id is used for the subsequent call to fetch the next table along with the applied/selected filters. File Details - Drill throughs in piecharts: It is similar to the drill-down in tables. Here drill through in piecharts are based on the drillDownChartId field in the parent piechart. File Details - ### **Comparison Indicators in Tables** Providing better insights about the metric performances of different dimensions, a comparison indicator is required inside data tables comparing usually with a different time range (last year/last month) and what is percentage change with time. **Technical Implementation Details:** Comparison with the previous year's data in every table data uses the same request object by changing the time range to the previous year/month/week. File Details - The following method along with parameters is used to fetch the previous year's data. ``` getLastYearRequest(calledFrom, visualcode, active, filterList) ``` After receiving last year's data it is compared with the current year's data. The comparison is shown as insight data. The comparison logic is present in uiTable.js - **TimeFilter** The current time component is not very intuitive and user-friendly. So a new library react-date range is used to enhance the time filter. File Details - **Event Duration Graphs** Ability to generate graphs showcasing time spent between multiple events like average turnaround time, complaint assigning time, etc. A DSS\_EVENT\_DURATION\_GRAPH is added in the PGR config ``` { "id": 412, "name": "DSS_EVENT_DURATION_GRAPH", "dimensions": { "height": 350, "width": 7 }, "vizType": "chart", "isCollapsible": false, "label": "", "charts": [ { "id": "eventDurationGraph", "name": "Monthly", "code": "", "chartType": "line", "filter": "", "headers": [] } ] } ``` ## **API Call Role Action Mapping** | API | Action ID | Roles | | -------------------------------------------------------------- | --------- | ---------------------------------------------------------------------- | | /localization/messages/v1/\_search | 1531 | SUPERUSER,EMPLOYEE,CITIZEN,GRO,DGRO, | | /egov-mdms-service/v1/\_search | 954 | LOA\_CREATOR,SUPERUSER,WO\_CREATOR,AE\_CREATOR,WORKS\_MASTER\_CREATOR, | | /dashboard-analytics/dashboard/getDashboardConfig/propertytax | 1892 | STADMIN | | /dashboard-analytics/dashboard/getDashboardConfig/home | 1889 | STADMIN | | /dashboard-analytics/dashboard/getDashboardConfig/tradelicense | 1893 | STADMIN | | /dashboard-analytics/dashboard/getDashboardConfig/pgr | 1894 | STADMIN | | /dashboard-analytics/dashboard/getDashboardConfig/ws | 2010 | STADMIN | | /dashboard-analytics/dashboard/getChartV2 | 1890 | STADMIN, EMPLOYEE | > [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)\_\_](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation* ](https://egov.org.in/)*is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.* --- # 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.digit.org/local-governance/v2.8/platform/configure-digit/services-overview/business-services/dashboard-analytics-backend/dss-features-enhancements.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.