DRISTI
  • 👋Welcome to DRISTI
    • Why DRISTI?
  • ⚖️About DRISTI
    • Overview
    • Design Principles
    • Value Proposition
    • Architecture Overview
    • System Users
    • Key Modules
      • Async Applications & Submissions
        • Key Features
        • Process & Workflows
        • Specifications
      • Case Management
        • Key Features
        • Process & Workflows
        • Specifications
      • E-Filling, Scrutiny and Admission
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Evidence
        • Key Features
        • Process & Workflows
        • Specifications
      • Listing & Scheduling
        • Key Features
        • Process & Workflows
        • Specifications
      • Hearings
        • Key Features
        • Process & Workflows
        • Specifications
      • Orders & Tasks
        • Key Features
        • Process & Workflows
        • Specifications
      • Summons, Bails, Warrants
        • Key Features
        • Process & Workflows
        • Specifications
      • User Benefits
      • User Registration
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Roles per Module
    • API Specifications
    • Security
    • Privacy
  • 🧰DRISTI Platform
    • Architecture
      • Overview
      • Principles
      • High Level Design
        • Technology Stack
        • Access Control & Roles
        • Data & Analytics
        • Non Functional Requirements
          • Performance
          • Security
          • Data Retention
        • Logging Guidelines
      • Low Level Design
        • Advocate
          • Advocate - API Specifications
          • Sequence Diagram
        • Application
          • Application - API Specifications
          • Sequence Diagram
        • Case
          • Case - API Specifications
          • Sequence Diagram
        • Case Management
          • Case Management - API Specifications
          • Sequence Diagram
        • Evidence
          • Evidence - API Specifications
          • Sequence Diagram
        • Hearing
          • Hearing - API Specifications
          • Sequence Diagram
        • Order
          • Order - API Specifications
          • Sequence Diagram
        • Task
          • Task - API Specifications
          • Sequence Diagram
          • Summons
          • Warrant
      • Architectural and Design Decisions
        • Data Visibility
        • Detailed Case Access
        • Case Numbering
          • Filing Number
          • Court Case Number
          • CNR Number
          • Case Stages, Numbers & Dates
    • Interoperability
    • Release Notes
      • Release 1.1.0
      • Release 1.2.0
      • Release 1.3.0
      • Release 1.4.0
      • Release 1.5.0
      • Release 1.6.0
    • Hotfixes
      • Hotfix Release 17.3
      • Hotfix Release 18.1
      • Hotfix Release 18.2
      • Hotfix Release 18.3
      • Hotfix Release 18.4
      • Hotfix Release 19.1
  • 🪝Setup
    • Planning DRISTI Implementation
    • Establish Project & Team
    • Gather Requirements
    • Installation
      • Infrastructure Setup
        • Azure Setup
        • SDC - OpenShift Setup
      • Code Deployment
      • Configuration
        • Functional Configuration
        • Service Configuration
          • Court
            • Court UI
          • Case
            • Case UI
          • Advocate
            • Advocate UI
          • Application
            • Application UI
          • Task
            • Task UI
          • Order
            • Order UI
          • Hearing
            • Hearing UI
          • Evidence
            • Evidence UI
    • Quality Assurance Testing
    • Go Live
    • Operational Support
    • Monitoring
  • 🛣️Roadmap & Updates
    • Roadmap
  • 🌾Resources
    • Source Code
    • Technology Stack
    • Licensing
    • Legal Taxonomy
  • 🌐COMMUNITY
    • Interested in Contributing?
    • Github Discussion
    • Code of Conduct
  • 🪝Setup
    • Coming soon...
    • 🟢ABOUT US
Powered by GitBook
On this page
  • Overview
  • API Details
  • Kafka Topics
  • DB Schema
  • Workflows
  1. DRISTI Platform
  2. Architecture
  3. Low Level Design

Application

PreviousSequence DiagramNextApplication - API Specifications

Last updated 3 months ago

Overview

The Application Registry and Service allow for the create, update and search of the various applications and affidavits as part of a dispute or independently in judicial operations. The registry serves as a central database where applications and affidavits within the platform are stored and managed. This registry serves as a single source of truth, maintaining detailed records of each application, including its metadata, configuration, and status.

All applications and services are registered with unique identifiers, which ensures that they are accurately referenced across the entire ecosystem. This prevents conflicts and errors that might arise from duplicate or inconsistent records. The Applications APIs allow for seamless integration across tech systems deployed in the judicial ecosystem

Potential uses of this service include:

  1. Direct Submission of Drafted Legal Documents: A third-party drafting service provider is tasked with preparing legal documents such as petitions, affidavits, or agreements for court cases. The drafting service provider integrates with the DRISTI platform using the Application API. Once the document is prepared, the service provider’s application can directly submit the document to the appropriate case management system within the platform without requiring a user to manually download the document and then upload it into the system.

  2. Automated Status Updates for Applications upon Filing: After submitting an application or legal document, the drafting service provider wants to track the status of the submission to ensure it has been received, reviewed, and filed correctly. The service provider’s system uses the API to query the status of the submitted application in real-time. The API allows the provider to automatically receive updates on the application's progress through the judicial process, such as whether it has been accepted, is under review, or if additional information is required.

  3. Legal Research Service Integration: A legal research service provider offers a tool that enables legal professionals to search for relevant case law, statutes, and legal precedents. The service provider integrates their research tool Application APIs to track all applications and their statuses against a case.

API Details

  • Create (/application/v1/create): Creates a new application, requiring details like application ID, tenant ID, case ID, and application type.

  • Update (/application/v1/update): Updates an existing application with data similar to the create operation.

  • Search (/application/v1/search): Allows searching for applications based on various criteria, such as tenant ID, application ID, case ID, application type, and status.

  • Exists (/application/v1/exists): Checks whether a specific application exists using the application ID.

  • Add Comment (/application/v1/addComment): Adds a comment to an existing application, requiring the application ID, comment text, and the user ID of the commenter.

Kafka Topics

Topic Name
Description
Payload

save-application

When a new application is created, data is pushed to this topic.

Application create payload. Refer to the API spec.

update-application

When an application is updated, data is pushed to this topic.

Application update payload. Refer to the API spec.

update-application-status-application

When workflow status changes happen, data is pushed to this topic.

update-application-comments-application

When additional comments are added to an application, data is pushed to this topic.

DB Schema

Workflows

Business Name
Business Service Name
Description

application

application-order-submission-default

application-order-submission-feedback

application-voluntary-submission

delay-condonation-submission

Workflow configuration JSON is .

🧰
Application - API Specifications
checked in here