{"id":4733,"date":"2026-07-01T12:32:33","date_gmt":"2026-07-01T07:02:33","guid":{"rendered":"https:\/\/blog.jupitice.com\/?p=4733"},"modified":"2026-07-01T16:24:37","modified_gmt":"2026-07-01T10:54:37","slug":"june-2026-v26-6","status":"publish","type":"post","link":"https:\/\/blog.jupitice.com\/?p=4733","title":{"rendered":"June 2026 (v26.6)"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">Key Highlights<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"has-small-font-size\"><strong><a href=\"#1\">Enhancing Authentication, User Management, and Marketplace Deployment<\/a><\/strong>: We have implemented secure authentication enhancements, improved user validation and profile accessibility, and successfully deployed the platform on a new marketplace domain for a seamless, secure, and scalable user experience.<\/li>\n\n\n\n<li class=\"has-small-font-size\"><strong><a href=\"#2\">Case Log- Hearing Room<\/a><\/strong>: We have implemented the Case Log feature in the Hearing Room as an immutable, chronological ledger with list and calendar views plus advanced filtering to ensure complete, transparent, and auditable tracking of all case lifecycle activities.<\/li>\n\n\n\n<li class=\"has-small-font-size\"><strong><a href=\"#3\">Enhancing User Experience with Key UI Improvements<\/a><\/strong>: We have implemented UI enhancements to improve user experience, including video call confirmation popups, enhanced signup validation, streamlined marketplace navigation, and seamless profile picture management.<\/li>\n\n\n\n<li class=\"has-small-font-size\"><strong><a href=\"#4\">Case Listing- Hearing Room<\/a><\/strong>:We have implemented and validated the \u201cListing Clerk Confirms Date\u201d workflow in the Hearing Room to enable seamless hearing date selection, automatic case status transition, and accurate scheduling within the Listing phase.<\/li>\n\n\n\n<li class=\"has-small-font-size\"><strong><a href=\"#5\">Rabbit MQ Integration<\/a><\/strong>: We have implemented a production-grade RabbitMQ system with multi-tenant support, centralized queue management, parallel processing, robust error handling, and an interactive sandbox UI to ensure scalable, reliable, and fully observable asynchronous message processing across the platform.<\/li>\n\n\n\n<li class=\"has-small-font-size\"><strong><a href=\"#6\">Cause List Assignment &amp; Hearing (Hearing Room)<\/a><\/strong>: We have implemented the Cause List Assignment &amp; Hearing workflow in the Hearing Room to enable seamless case scheduling, automatic hearing creation, bench association, and status transition from \u201cawaiting cause list\u201d to \u201cpending.\u201d<\/li>\n\n\n\n<li class=\"has-small-font-size\"><strong><a href=\"#7\">Ecourt CIS integration<\/a><\/strong>: We have implemented the eCourt CIS Integration to provide secure, real-time access to High Court case information through official eCourt APIs, enabling CNR search, party name search, and cause list retrieval directly within the platform.<\/li>\n<\/ul>\n\n\n\n<h3 id=\"1\" class=\"wp-block-heading\"><strong>Enhancing Authentication, User Management, and Marketplace Deployment<\/strong><\/h3>\n\n\n\n<p class=\"has-small-font-size wp-block-paragraph\">We have implemented key enhancements to strengthen platform security, improve user management, and ensure seamless deployment. A secure Forgot Password feature has been added, with OTP\/email verification, validation, and expiry handling to ensure safe credential recovery. The registration workflow now includes a pre-validation check to prevent duplicate accounts before OTP authentication. We also introduced controlled profile viewing for non-legal professionals with role-based access permissions and a distinct UI to differentiate them from legal professional profiles. Additionally, the application has been successfully deployed on a new marketplace domain with complete environment configuration, DNS setup, SSL integration, and post-deployment validation, ensuring secure access, reliable performance, and a smooth user experience.<\/p>\n\n\n\n<h3 id=\"2\" class=\"wp-block-heading\"><strong>Case Log- Hearing Room<\/strong><\/h3>\n\n\n\n<p class=\"has-small-font-size wp-block-paragraph\">We have implemented the Case Log feature in the Hearing Room as an immutable, chronological ledger that records every significant event in a case&#8217;s lifecycle, enabling users to reconstruct a complete procedural timeline with ease. The system tracks key activities, including case creation and status changes, member assignments and removals, team allocations, hearing lifecycle updates (such as scheduled, adjourned, passed over, or marked heard), and urgent mentioning requests with full lifecycle tracking. We have also introduced structured views to improve usability, including a List View for detailed reverse-chronological tracking with categorized icons, timestamps, and actor information, and a Calendar View for month-wise visualisation of case activity density. Additionally, we implemented Advanced Filters to enable users to refine logs by activity type and custom date ranges, making it easier to analyse complex case histories efficiently. This enhancement improves transparency, auditability, and overall case tracking within the platform.<\/p>\n\n\n\n<h3 id=\"3\" class=\"wp-block-heading\">Enhancing User Experience with Key UI Improvements<\/h3>\n\n\n\n<p class=\"has-small-font-size wp-block-paragraph\">We have implemented key UI enhancements to improve usability, simplify user interactions, and deliver a more seamless experience across the platform. A success pop-up has been added to acknowledge video call requests, providing users with instant confirmation that their request has been successfully submitted and will be processed by the team. On the Signup page, &#8220;Join Community&#8221; has been replaced with &#8220;Explore Jupitice Marketplace&#8221; to better align with the platform&#8217;s user journey and encourage marketplace exploration. We also introduced email format validation to ensure only valid email addresses are accepted during registration, reducing input errors and improving data accuracy. Additionally, Citizen Profile users can now upload or update their profile pictures directly from their profile page, making profile management more convenient and personalized. Together, these enhancements improve user engagement, navigation, accessibility, and the overall platform experience.<\/p>\n\n\n\n<h3 id=\"4\" class=\"wp-block-heading\"><strong>Rabbit MQ Integration<\/strong><\/h3>\n\n\n\n<p class=\"has-small-font-size wp-block-paragraph\">We have implemented a production-grade RabbitMQ integration designed to enhance scalability, reliability, and asynchronous processing across the platform. The system supports multi-tenant architecture with centralized queue management, ensuring that each tenant\u2019s messaging workflow is isolated, configurable, and efficiently managed. It enables parallel message processing to improve throughput and system performance, while robust error handling mechanisms ensure message integrity and prevent data loss during failures or retries. To make the system highly configurable and maintainable, we introduced database-driven queue configurations that are loaded at server startup, allowing dynamic control over queue behaviour without code changes. Detailed logging has been integrated throughout the message lifecycle to support monitoring, debugging, and operational transparency. In addition, an interactive sandbox UI has been developed to visualise real-time message flow and validate end-to-end processing, helping developers and stakeholders better understand system behaviour. The system also supports essential queue operations such as purging and management controls, making it easier to maintain and operate in production environments. Built on a modular, extensible architecture comparable to existing MySQL and Redis integrations, the solution ensures consistency across the platform\u2019s core infrastructure.<\/p>\n\n\n\n<h3 id=\"5\" class=\"wp-block-heading\">Case Listing- Hearing Room<\/h3>\n\n\n\n<p class=\"has-small-font-size wp-block-paragraph\">We have implemented and validated the \u201cListing Clerk Confirms Date\u201d workflow<strong> <\/strong>in the Hearing Room under the Listing phase to streamline hearing scheduling and case progression. In this process, the Listing Clerk accesses My Queue and opens the Listing tab, where all cases with the status \u201clisting\u201d are displayed. After selecting a case, the clerk initiates the \u201cList Case\u201d action, which opens a date-selection modal to select an appropriate hearing date. Upon submission, the system automatically updates the next_hearing_date field and transitions the case status from \u201clisting\u201d to \u201cawaiting_cause_list\u201d, ensuring accurate and consistent state management. The workflow has been tested for the happy path and is functioning as expected, supporting smooth scheduling and reliable case movement within the Listing phase.<\/p>\n\n\n\n<h3 id=\"6\" class=\"wp-block-heading\"><strong>Cause List Assignment &amp; Hearing (Hearing Room)<\/strong><\/h3>\n\n\n\n<p class=\"has-small-font-size wp-block-paragraph\">We have implemented the Cause List Assignment &amp; Hearing workflow in the Hearing Room to streamline case scheduling under the \u201cAwaiting Cause List\u201d stage. In this process, the Cause List Clerk navigates to My Queue and opens the Awaiting Cause List tab, where all pending cases are displayed. After selecting a case, the clerk initiates the assignment action, which opens a date picker defaulted to the case\u2019s next_hearing_date. The system then fetches all available unpublished cause lists for the selected date, including details such as bench, time slot, and list type (Daily or Supplementary). The clerk selects the appropriate cause list and confirms the assignment. Upon successful execution, the system automatically creates a hearing record with status \u201clisted\u201d, generates a video conferencing link via Jitsi, associates the relevant bench through case_teams, and updates the case status from \u201cawaiting_cause_list\u201d to \u201cpending\u201d. This workflow ensures accurate scheduling, proper bench allocation, and readiness for upcoming hearings.<\/p>\n\n\n\n<h3 id=\"7\" class=\"wp-block-heading\"><strong>Ecourt CIS integration<\/strong><\/h3>\n\n\n\n<p class=\"has-small-font-size wp-block-paragraph\">We have implemented the eCourt CIS Integration to seamlessly connect the High Court platform with India&#8217;s national eCourt judicial database, enabling secure, real-time access to High Court case information through official eCourt APIs. The integration provides a unified interface that allows judicial officers and court staff to perform CNR-based case searches<strong>,<\/strong> party-name searches with registration-year and case-status filters, and cause-list retrieval for scheduled hearings, eliminating the need to navigate multiple systems. Users can efficiently access comprehensive case information, including party details, case status, hearing history, court orders, filing dates, next-hearing schedules, and daily cause lists, all within the platform. The eCourt API Explorer is available at \/dashboard\/ecourt-api and is accessible exclusively to users with Super Admin and<strong> <\/strong>Registrar Judicial<strong> <\/strong>roles. The Cause List functionality is available upon activation of the required API subscription.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Key Highlights Enhancing Authentication, User Management, and Marketplace Deployment We have implemented key enhancements to strengthen platform security, improve user management, and ensure seamless deployment. A secure Forgot Password feature has been added, with OTP\/email verification, validation, and expiry handling to ensure safe credential recovery. The registration workflow now includes a pre-validation check to prevent [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":4786,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,3],"tags":[],"class_list":["post-4733","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-releases","category-tech"],"_links":{"self":[{"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=\/wp\/v2\/posts\/4733","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4733"}],"version-history":[{"count":56,"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=\/wp\/v2\/posts\/4733\/revisions"}],"predecessor-version":[{"id":4791,"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=\/wp\/v2\/posts\/4733\/revisions\/4791"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=\/wp\/v2\/media\/4786"}],"wp:attachment":[{"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4733"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4733"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jupitice.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4733"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}