A flexible assembly case trial implementation method and system

Abstract

A flexible case handling implementation method and system is disclosed, belonging to the field of data processing technology. It solves the problems associated with secondary development in traditional case handling process design and development models. The method includes the following steps: case handling item configuration, case handling item arrangement, case handling stage configuration, case handling phase configuration, case handling execution, and case handling item slots. By breaking down complex cases into a series of specific and operable minimum item units, the key points, points of contention, and potential risks of the case can be more clearly identified, thus providing strong support for subsequent handling work. Different case handling items form different case handling stages, which in turn form different case handling phases. This allows for flexible assembly of processes corresponding to different cases, adapting to the needs of different case handling, without the need for secondary development.

Description

Technical Field

[0001] This invention belongs to the field of data processing technology, specifically relating to a flexible assembly method and system for case adjudication. Background Technology

[0002] In legal practice and the operation of related case management systems, the design and implementation of case hearing procedures have always been crucial for ensuring fairness and improving efficiency. Traditional case hearing procedure design models typically involve a step-by-step approach, following the hearing procedures proposed by the requesting party.

[0003] From a process design perspective, the development team engages in in-depth and detailed communication with the stakeholders to understand their specific requirements, the order of events, and the logical relationships between different stages of the case hearing. For example, in case hearings, the specific operational procedures and timelines for each step, from case filing and acceptance, evidence exchange, pre-trial mediation, court hearings to the final judgment, must be clearly defined. Based on this detailed requirement information, the developers utilize professional software development technologies and tools to construct a complete case hearing process framework. This framework acts as a precise blueprint, providing clear guidance for subsequent development work and ensuring that the developed system operates accurately and flawlessly according to the established hearing process, thereby guaranteeing the standardization and accuracy of case hearings.

[0004] During the development and implementation phase, developers, based on the designed process framework, use various programming languages ​​and development frameworks to translate the trial process into code that computers can recognize and execute. This process requires a high degree of professionalism and rigor, because even a small error can cause deviations in the entire trial process, affecting the normal handling of cases. For example, if there are errors in the code when handling case flow logic, it may cause the case to stall at a certain stage or be incorrectly transferred to the next stage, causing serious disruption to the trial work.

[0005] However, this traditional case handling process design and development model has many drawbacks. When new requirements arise during the case handling process, or when adjustments to existing nodes are needed, significant challenges arise. Because traditional systems are often designed based on a fixed process framework, adding or adjusting new nodes often means re-examining and modifying the entire system architecture. This necessitates secondary development work.

[0006] Secondary development not only consumes a significant amount of development time, as developers need to re-analyze requirements, modify code, and conduct testing—a series of tedious tasks—but also requires extensive debugging and optimization to ensure compatibility between new features and the original system, further extending the development cycle. A lengthy development process can cause the case adjudication system to be unable to respond promptly to changes in actual work, impacting the user experience. For example, when new laws and regulations are introduced, requiring the addition of corresponding review nodes to the case adjudication process, if the secondary development cycle is too long, the case adjudication work may not be able to proceed according to the new requirements during this period, thus affecting efficiency.

[0007] Furthermore, frequent secondary development can easily lead to redundant and messy code. As new nodes are added and nodes are repeatedly adjusted, the code in the system becomes increasingly complex. Differences in coding styles and logic among different developers can significantly reduce code readability and maintainability. In the long run, the system becomes difficult to manage and upgrade, posing immense challenges to subsequent maintenance and potentially even affecting the stability and security of the entire case handling system. Summary of the Invention

[0008] To address the issues arising from the need for secondary development and the problems associated with traditional case trial process design and development models, this invention provides a flexible and modular method and system for implementing case trials.

[0009] The method includes the following steps: S1. Case hearing item configuration: Based on the functional points and details provided by the client, the case hearing items are defined by breaking them down into the smallest granular units; then, the case hearing items are created and added. S2. Arrangement of Case Hearing Items: Confirm the prerequisites for activating case hearing items; confirm the case hearing items that need to be completed in the case hearing stage; confirm the new case hearing items triggered after the case hearing stage is completed; S3. Case hearing process configuration: Confirm whether the case hearing process can be omitted; confirm the prerequisite case hearing matters for initiating the case hearing process; confirm the necessary case hearing matters for completing the case hearing process. S4. Case Trial Stage Configuration: Confirm the prerequisite case trial matters for initiating the case trial stage, and confirm the mandatory case trial matters for completion during the case trial stage; S5. Case Adjudication and Execution: The adjudication and execution process is as follows: execute the case adjudication matters and report them; load the case adjudication stage, case adjudication link, and case adjudication matters into the task server memory; monitor the case adjudication task; S6. Case Adjudication Item Slot: If new case adjudication items need to be added during the execution of different case adjudication processes, they can be added through the case adjudication item slot function.

[0010] Furthermore, when configuring case handling matters, they are categorized and configured according to document drafting type, process handling type, and content inspection type.

[0011] Furthermore, the prerequisite for activating a case hearing matter is the completion status of other case hearing matters and reaching a specific case hearing stage; a case hearing stage consists of several case hearing matters.

[0012] Furthermore, based on the characteristics and actual needs of different cases, it is determined whether any part of the case hearing process can be omitted; after confirming the prerequisite case hearing matters for initiating the case hearing process, the case hearing process can only proceed after all the prerequisite case hearing matters for initiating the case hearing process have been completed; the case hearing process is deemed complete when all the necessary case hearing matters for completion have been completed.

[0013] Furthermore, once all the preliminary case-handling matters that would have initiated the case-handling stage have been completed, the case-handling stage begins; once all the necessary case-handling matters that must have been completed in the case-handling stage have been completed, the case-handling stage ends, and the next case-handling stage begins; the necessary matters completed in each case-handling stage are recorded, and a stage report is formed.

[0014] Furthermore, when executing and reporting case hearing matters, the reporting parameters include: case ID, case hearing matter type, case hearing matter ID, case hearing matter progress, case hearing matter completion time, and case hearing matter handler; Load the case hearing stage, case hearing process, and case hearing matters into the task server memory, specifically as follows: Step 1: Query all configuration case hearing matters; Step 2: Load the tree structure of case hearing matters; that is, case hearing matter 1 is the parent node of the tree; the child nodes are the list of case hearing matters affected by the completion progress of case hearing matter 1, which are cached in the server memory; Step 3: Load the case hearing process and complete the necessary case hearing items; Step 4: Load the case hearing stage and complete the necessary case hearing matters; Case trial task monitoring, specifically: Step 1: Complete the loading of the case hearing stage, case hearing process, and case hearing matters; Step 2: Receive the report of completion of case hearing matters; Step 3: Match the case hearing matter tree and obtain the sub-case hearing matter list; Step 4: Loop through the list of sub-case hearing matters and determine whether the sub-case hearing matters have met the triggering and completion conditions; if the triggering conditions are met, mark the status of the case hearing matter as pending completion; if it is found that the sub-case hearing matter has been completed, do not process it. Step 5: Check completed case hearing matters; Step 6: Based on the loaded case hearing process configuration, determine the completion status of the case hearing process and record it; Step 7: Based on the loaded case hearing stage configuration, determine the completion status of the case hearing stage and record it.

[0015] Furthermore, the implementation of the case hearing matter slot function is as follows: Step 61: Reserve interfaces for implementing case hearing matters Step 62: When it is necessary to add new case hearing matters, configure the new case hearing matters by implementing the interface; Step 63: Manually upload the JAR package and configure the fully qualified package name and class name of the implementation class corresponding to the newly added case hearing matters; Step 64: Call the custom loading class to load the implementation class; Step 65: In the constructor of the implementation class, load the implementation method of the implementation class and the name of the newly added case hearing matter into the matter factory management class; Step 66: When the front-end calls the unified interface for handling new case hearing matters, it passes the corresponding name and parameters of the new case hearing matter to the back-end interface. Step 67: The backend factory management class routes to the specified implementation class by adding a case hearing matter name; Step 68: Complete the calling of the implementation class for adding new case hearing matters to realize the function of adding new case hearing matters without service interruption.

[0016] The system includes the following units: Case hearing item configuration unit: Based on the functional points and details provided by the customer, the case hearing items are defined by breaking them down into the smallest granular units; then, the case hearing items are created and added. Case hearing item arrangement unit: confirms the prerequisites for activating case hearing items; confirms the case hearing items that need to be completed in the case hearing stage; confirms the new case hearing items triggered after the case hearing stage is completed; Case hearing process configuration unit: confirms whether the case hearing process can be omitted; confirms the prerequisite case hearing matters for initiating the case hearing process; confirms the necessary case hearing matters for completion of the case hearing process; Case trial stage configuration unit: confirms the prerequisite case trial matters for initiating the case trial stage, and confirms the necessary case trial matters for completion during the case trial stage; Case Adjudication and Execution Unit: The adjudication and execution process is as follows: execute the case adjudication matters and report them; load the case adjudication stage, case adjudication link, and case adjudication matters into the task server memory; monitor the case adjudication tasks; Case hearing item slot unit: When encountering new case hearing items during the execution of different case hearings, these items can be added through the case hearing item slot function.

[0017] The beneficial effects of the method described in this invention are as follows: In the traditional case trial development process, a complete case trial process framework is constructed based on the client's specific requirements for each stage of the case trial, the order of events, and the logical relationships between different stages. Then, a case trial system is developed based on this case trial process framework to assist judges in conducting trials. However, because the process framework is fixed, the case trial system obtained in this way cannot adapt to new node requirements that arise during the case trial process.

[0018] The method described in this invention does not arrange the case handling process according to a fixed process framework. Instead, it arranges the case handling process by dividing it into the smallest case adjudication matters and constructing it layer by layer through case adjudication matters - case adjudication stages - case adjudication phases. This arrangement of the case handling process has the following technical advantages: (1) In the process of case hearing and management, the matters are broken down into the smallest granularities. This breakdown not only helps to deeply understand and grasp every minute detail of the case, but also significantly improves the accuracy and efficiency of case hearing. By breaking down complex cases into a series of specific and operable smallest matter units, the key points, points of contention and potential risks of the case can be more clearly identified, thereby providing strong support for subsequent hearing work.

[0019] (2) Different case hearing matters can be combined to form different case hearing stages, which in turn can form different case hearing phases. This allows for flexible assembly of the processes corresponding to different cases to meet the needs of different case handling without the need for secondary development. This saves development resources and case handling time costs.

[0020] The method described in this invention also includes a case handling item slot function. During the execution of different case hearings, if new case handling items need to be added, they can be added through this slot function. This further improves the flexibility and efficiency of case handling. Attached Figure Description

[0021] Figure 1 This is a flowchart of the method described in an embodiment of the present invention. Detailed Implementation

[0022] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of the present invention.

[0023] Example 1 This embodiment provides a flexible and modular method for implementing case hearings, such as... Figure 1 As shown, the method includes the following steps: S1. Case hearing item configuration: Based on the functional points and details provided by the client, the case hearing items are defined by breaking them down into the smallest granular units; then, the case hearing items are created and added. S2. Arrangement of Case Hearing Items: Confirm the prerequisites for activating case hearing items; confirm the case hearing items that need to be completed in the case hearing stage; confirm the new case hearing items triggered after the case hearing stage is completed; S3. Case hearing process configuration: Confirm whether the case hearing process can be omitted; confirm the prerequisite case hearing matters for initiating the case hearing process; confirm the necessary case hearing matters for completing the case hearing process. S4. Case Trial Stage Configuration: Confirm the prerequisite case trial matters for initiating the case trial stage, and confirm the mandatory case trial matters for completion during the case trial stage; S5. Case Adjudication and Execution: The adjudication and execution process is as follows: execute the case adjudication matters and report them; load the case adjudication stage, case adjudication link, and case adjudication matters into the task server memory; monitor the case adjudication task; S6. Case Adjudication Item Slot: If new case adjudication items need to be added during the execution of different case adjudication processes, they can be added through the case adjudication item slot function.

[0024] Example 2 This embodiment is a further description of Embodiment 1. It provides further explanation of the configuration of case hearing matters.

[0025] In the case handling process, the proper arrangement of matters is crucial to ensuring smooth progress. By clearly defining the sequence and dependencies between matters, the efficiency and accuracy of the case handling can be guaranteed. Matters are defined by breaking them down into their smallest granular units based on the functional points and details provided by the client.

[0026] The system centrally manages matters related to case hearings, including documents to be prepared and operational procedures to be submitted during the hearing process. The configuration of a case mainly includes the case type, case name, redirect page, and additional parameters. This allows for the creation and addition of case cases to the system, meeting the needs of continuously added cases in business operations and ensuring the integrity and timeliness of system data.

[0027] After configuring all aspects of the case hearing process, the case hearing workflow configuration function can be used to systematically connect the flow rules and logical relationships between various aspects of the case hearing process. This allows the case hearing workflow to flexibly adapt to different scenarios, such as the hearing workflow for adjudicated cases or administrative penalty cases.

[0028] For example, the case review stage requires four steps: preparing case review notes, returning the case for further investigation, conducting hearing interviews, and submitting a hearing report. Based on the above content, we can break it down as follows, and the results are shown in Table 1.

[0029] Table 1 Breakdown of Case Review Stages:

[0030] When configuring case handling matters, they are categorized and configured according to document drafting type, process handling type, and content inspection type.

[0031] Example 3 This embodiment is a further introduction to Embodiment 1. It provides further explanation of the arrangement of matters for case hearing.

[0032] 1. Confirm the prerequisites for activation. The system outlines the conditions that must be met before each item can be initiated. These prerequisites include the completion status of other items and reaching specific time points. For example, in case hearings, the prerequisite for issuing a "decision to accept the case" might be the approval of the "formal review of the case." By setting these prerequisites, the system can precisely assess them, ensuring that the item is activated and becomes operational only when all prerequisites are met.

[0033] For complex preconditions, logical expressions can be used to define them, such as "(item A is completed and the result of item B is passed) or (item C is completed before the specified date)", to meet diverse business needs.

[0034] 2. Items to be completed during the confirmation process Clearly define the specific tasks involved in each stage of the process, ensuring these tasks have clearly defined operational steps and deliverables. Taking the "disciplinary decision" stage in an administrative penalty case as an example, the tasks might include "collecting evidence of illegality," "interrogating relevant parties," and "preparing a review report." Establish detailed operational guidelines for each task; for instance, for "collecting evidence of illegality," specify the types of evidence, collection methods, and evidence preservation requirements to ensure that personnel can complete the tasks accurately.

[0035] At the same time, assign a responsible person to each task and clarify their duties and authority in the task completion process to avoid situations where the designated person in charge cannot be found.

[0036] 3. New events triggered after the completion of the process. Once a process step is successfully completed, subsequent new items are automatically triggered according to preset rules, achieving automated process flow. For example, after the "submission of trial report" step in a adjudicated case is completed, the "Standing Committee Special Meeting" item is automatically triggered.

[0037] Trigger rules can be set based on various factors, such as the outcome of a task, time conditions, and specific data values. By flexibly configuring trigger rules, the system can adapt to the trial processes of different types of cases, improving the intelligence level and automation of the process.

[0038] Example 4 This embodiment is a further description of Embodiment 1. It provides further explanation of the configuration for the case hearing process.

[0039] The trial stage is a core component of the case trial process. By carefully configuring the trial stage, it can be ensured that each stage proceeds in an orderly manner according to established rules, thus guaranteeing the quality and efficiency of the case trial.

[0040] 1. Can the configuration process be omitted? Based on the characteristics and actual needs of different types of cases, options are set for whether each stage of the trial can be omitted. For some non-critical stages, such as "exclusion of illegally obtained evidence" in certain cases, if the case does not involve illegally obtained evidence, this stage can be set as optional, allowing the case to proceed directly to the next stage of the trial process, thus improving trial efficiency. The system interface provides "Yes" and "No" options via drop-down menus for configuration personnel to choose from, facilitating quick and easy setup.

[0041] 2. Prerequisites for initiating the confirmation process Clearly define the prerequisites that must be completed before each stage of the review process can begin. For example, before "formal acceptance" can begin, prerequisites such as "transfer for review and processing," "assignment of review members," and "formal review" must be completed. Only when all these prerequisites are completed will the system allow "formal acceptance" to officially begin.

[0042] The system monitors and provides feedback on the completion status of prerequisites in real time. If a prerequisite is not completed, the system will prompt the operator to handle it and prevent the start of subsequent review stages, thus ensuring the rigor of the review process.

[0043] 3. Required items for completion of the confirmation process Each stage of the review process has clearly defined completion criteria and mandatory requirements. A stage is considered complete once all mandatory requirements are met. The system records and reviews the completion status of each mandatory requirement to ensure the standardization and completeness of the review process. For the completion status of mandatory requirements, relevant supporting documents can be uploaded for subsequent review and verification.

[0044] Example 5 This embodiment is a further description of Embodiment 1. It provides further explanation of the configuration for the case hearing stage.

[0045] The trial stage is a division of the case trial process. By rationally allocating the trial stages, the case trial process can be made clearer, more organized, and easier to manage and monitor.

[0046] 1. Prerequisites for initiating the confirmation phase Each stage of the trial requires certain prerequisites to be met, reflecting the state a case should reach before entering that stage. For example, before the "case review" stage begins, the prerequisite of a "formal acceptance decision" must be met. Only when all prerequisites are met can a case smoothly enter the review stage.

[0047] The system will automatically verify the prerequisites. If the prerequisites are not met, the system will prevent the case from proceeding to the next stage and prompt for supplementation and improvement of the relevant matters to ensure the correct flow of the case trial stage.

[0048] 2. Required items to be completed during the confirmation phase Clearly define the tasks that must be completed at the end of each hearing stage. These tasks signify the successful conclusion of that stage and prepare the case for the next stage. For example, in the "case review" stage, mandatory tasks might include "issuing a review report." Only after all mandatory tasks are completed can the case move from the case review stage to the next.

[0049] Detailed records should be kept of all necessary items to be completed at each stage of the trial, and a stage report should be prepared to review and summarize the trial process, and to provide a basis for subsequent case quality evaluation.

[0050] Example 6 This embodiment is a further description of Embodiment 1. It provides further explanation of the case trial and execution.

[0051] 1. Execute the tasks and report them. Reporting parameter definition { "case_id": "case id", "item_type": "item type", "item_id": "item ID", "item_progress": "Item progress", "completion_time": "completion time", "handler": the person who will handle the process. } Note: Reporting supports message queues, memory queues, database queues, etc.

[0052] 2. Load stages, processes, and tasks into the task server's memory. Step 1: Query all configuration items; Step 2: Load the item tree structure; that is, item 1 is the parent node of the tree; the child nodes are the list of items affected by the completion progress of item 1; cached in the server memory (when the virtual machine retrieves data, retrieving data from memory is the most efficient). Step 3: Loading process and necessary steps to complete the process; Step 4: Loading phase and necessary tasks for phase completion; Note: In a multi-node high-availability deployment, each node is notified via TCP / UDP. Upon receiving the notification, the loading process is re-executed.

[0053] 3. Task monitoring (handling reported matters) Step 1: Load the stages, steps, and tasks; Step 2: Receive the task completion report event; Step 3: Match the item tree and obtain the list of sub-items; Step 4: Loop through the list of sub-items and determine whether each sub-item has met the trigger and completion conditions. If the trigger condition is met, mark the sub-item as pending completion. If the sub-item is found to be completed, do not process it. Step 5: Check completed items; Step Six: Based on the loaded process configuration, determine the completion status of the process and record it; Step 7: Based on the loaded stage configuration, determine the stage completion status and record it.

[0054] Example 7 This embodiment is a further description of Embodiment 1. It provides further explanation of the case hearing matter slot.

[0055] The function of continuously adding new items has been reserved, that is, adding new item X requires case review.

[0056] The implementation of the case hearing matter slot function is as follows: Step 1: Reserve interfaces for implementing case hearing matters Step 2: When it is necessary to add new case hearing items, configure the new case hearing items through the interface; Step 3: Manually upload the JAR package and configure the fully qualified package name and class name of the implementation class corresponding to the newly added case hearing matters; Step 4: Call the custom loading class to load the implementation class; Step 5: In the constructor of the implementation class, load the implementation method of the implementation class and the name of the newly added case to be heard into the matter factory management class; Step 6: When the front-end calls the unified interface for handling new case hearing matters, it passes the corresponding name of the new case hearing matter and parameters to the back-end interface; Step 7: The backend factory management class routes the new case handling item name to the specified implementation class; Step 8: This enables the invocation of the class for adding new case hearing matters, thus achieving the function of adding new case hearing matters without service interruption.

[0057] Example 7 This embodiment is a further description of embodiments 1-6. The methods involved are further described and expanded.

[0058] The methods in Examples 1-6 can achieve flexible assembly of items: Dynamic template adaptation: For different case types such as adjudicated cases and administrative penalties, templates can be configured and extracted to achieve precise matching of "one template per case".

[0059] Dynamic access control: Based on the RBAC model (role-based access control), it automatically matches processing permissions according to the type of matter, meeting the needs of cross-departmental collaboration.

[0060] The methods in Examples 1-6 can be further extended to include: Real-time reporting of task completion status: Intelligent progress calculation automatically calculates the remaining time for each step based on preset time limits in the process, and uses red, yellow, and green to indicate the warning level, simultaneously pushing reminders. Abnormal behavior analysis: Monitors abnormal situations in the handling of tasks (such as "overdue" or "overdue for return for investigation and replacement of certificates"), automatically marks potential risk points, and issues task warnings.

[0061] Listening to distributed events: Message queue middleware: Builds an asynchronous communication mechanism to ensure that messages such as changes in the status of items and reminders are delivered in real time, avoiding system congestion or data loss.

[0062] The methods in Examples 1-6 can achieve the following technical effects: Value of Technological Integration: A Governance Leap from "Experience-Driven" to "Data-Driven," with Four Technological Modules Forming a Closed Loop: Formatted extraction provides a high-quality data foundation for subsequent processing; flexible assembly ensures process adaptability and permission compliance; real-time reporting enables transparency of progress and controllability of risks; and distributed monitoring ensures system stability and scalability.

[0063] Final result: Efficiency improvement: The average trial period for a single case has been shortened from 45 days to 25 days; Quality optimization: Problem clue detection rate increased by 60%, and false alarm rate reduced to below 5%; Management upgrade: Shifting from "manual monitoring" to "system-driven", leaders can keep abreast of the dynamics of the entire case handling process in real time and accurately allocate resources.

[0064] This method provides quantifiable, traceable, and optimizable digital support for monitoring work, and promotes the monitoring and governance model towards a smart stage of proactive prevention, precise policy implementation, and dynamic optimization.

Claims

1. A flexible assembly method for implementing case hearings, characterized in that, The method includes the following steps: S1. Case hearing item configuration: Based on the functional points and details provided by the client, the case hearing items are defined by breaking them down into the smallest granular units; then, the case hearing items are created and added. S2. Arrangement of Case Hearing Items: Confirm the prerequisites for activating case hearing items; confirm the case hearing items that need to be completed in the case hearing stage; confirm the new case hearing items triggered after the case hearing stage is completed; S3. Case hearing process configuration: Confirm whether the case hearing process can be omitted; confirm the prerequisite case hearing matters for initiating the case hearing process; confirm the necessary case hearing matters for completing the case hearing process. S4. Case Trial Stage Configuration: Confirm the prerequisite case trial matters for initiating the case trial stage, and confirm the mandatory case trial matters to be completed during the case trial stage; S5. Case Adjudication and Execution: The adjudication and execution process is as follows: execute the case adjudication matters and report them; load the case adjudication stage, case adjudication link, and case adjudication matters into the task server memory; monitor the case adjudication task; S6. Case Adjudication Item Slot: If new case adjudication items need to be added during the execution of different case adjudication processes, they can be added through the case adjudication item slot function.

2. The method for flexibly assembling case hearing procedures according to claim 1, characterized in that, When configuring case handling matters, they are classified and configured according to document writing type, process handling type, and content inspection type.

3. The method for implementing flexible case hearing according to claim 2, characterized in that, The prerequisites for activating a case's adjudication are the completion status of other case adjudication matters and reaching a specific case adjudication stage; The case hearing process consists of several case hearing matters.

4. The method for implementing flexible case hearing according to claim 3, characterized in that, Based on the characteristics and actual needs of different cases, determine whether any part of the case hearing process can be omitted; after confirming the prerequisite case hearing matters for the start of the case hearing process, the case hearing process can only proceed after all the prerequisite case hearing matters for the start of the case hearing process have been completed; the case hearing process is deemed complete when all the necessary case hearing matters for the start of the case hearing process have been completed.

5. The method for flexibly assembling case hearing procedures according to claim 4, characterized in that, Once all the preliminary case-handling matters that would have initiated the case-handling stage have been completed, the case-handling stage begins; once all the necessary case-handling matters that must be completed in the case-handling stage have been completed, the case-handling stage ends, and the next case-handling stage begins; all necessary matters completed in each case-handling stage are recorded, and a stage report is formed.

6. The method for flexibly assembling case hearings according to claim 5, characterized in that, When executing and reporting case hearing matters, the reporting parameters include: case ID, case hearing matter type, case hearing matter ID, case hearing matter progress, case hearing matter completion time, and case hearing matter handler; Load the case hearing stage, case hearing process, and case hearing matters into the task server memory, specifically as follows: Step 1: Query all configuration case hearing matters; Step 2: Load the tree structure of case hearing matters; that is, case hearing matter 1 is the parent node of the tree; the child nodes are the list of case hearing matters affected by the completion progress of case hearing matter 1, which are cached in the server memory; Step 3: Load the case hearing process and complete the necessary case hearing items; Step 4: Load the case hearing stage and complete the necessary case hearing matters; Case trial task monitoring, specifically: Step 1: Complete the loading of the case hearing stage, case hearing process, and case hearing matters; Step 2: Receive the report of completion of case hearing matters; Step 3: Match the case hearing matter tree and obtain the sub-case hearing matter list; Step 4: Loop through the list of sub-case hearing matters and determine whether the sub-case hearing matters have met the triggering and completion conditions; if the triggering conditions are met, mark the status of the case hearing matter as pending completion; if it is found that the sub-case hearing matter has been completed, do not process it. Step 5: Check completed case hearing matters; Step 6: Based on the loaded case hearing process configuration, determine the completion status of the case hearing process and record it; Step 7: Based on the loaded case hearing stage configuration, determine the completion status of the case hearing stage and record it.

7. The method for flexibly assembling case hearings according to claim 6, characterized in that, The implementation of the case hearing matter slot function is as follows: Step 61: Reserve interfaces for implementing case hearing matters; Step 62: When it is necessary to add new case hearing matters, configure the new case hearing matters by implementing the interface; Step 63: Manually upload the JAR package and configure the fully qualified package name and class name of the implementation class corresponding to the newly added case hearing matters; Step 64: Call the custom loading class to load the implementation class; Step 65: In the constructor of the implementation class, load the implementation method of the implementation class and the name of the newly added case hearing matter into the matter factory management class; Step 66: When the front-end calls the unified interface for handling new case hearing matters, it passes the corresponding name and parameters of the new case hearing matter to the back-end interface. Step 67: The backend factory management class routes to the specified implementation class by adding a case hearing matter name; Step 68: Complete the calling of the implementation class for adding new case hearing matters to realize the function of adding new case hearing matters without service interruption.

8. A flexible, modular case hearing system, characterized in that, The system includes the following units: Case hearing item configuration unit: Based on the functional points and details provided by the customer, the case hearing items are defined by breaking them down into the smallest granular units; then, the case hearing items are created and added. Case hearing item arrangement unit: confirms the prerequisites for activating case hearing items; confirms the case hearing items that need to be completed in the case hearing stage; confirms the new case hearing items triggered after the case hearing stage is completed; Case hearing process configuration unit: confirms whether the case hearing process can be omitted; confirms the prerequisite case hearing matters for initiating the case hearing process; confirms the necessary case hearing matters for completion of the case hearing process; Case trial stage configuration unit: confirms the prerequisite case trial matters for initiating the case trial stage, and confirms the necessary case trial matters for completion during the case trial stage; Case Adjudication and Execution Unit: The adjudication and execution process is as follows: execute the case adjudication matters and report them; load the case adjudication stage, case adjudication link, and case adjudication matters into the task server memory; monitor the case adjudication tasks; Case hearing item slot unit: When encountering new case hearing items during the execution of different case hearings, these items can be added through the case hearing item slot function.

9. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1-7.

10. A computer-readable storage medium for storing computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the steps of the method according to any one of claims 1-7.

Images