Task release method and device, computer equipment and readable storage medium

Abstract

The invention relates to the technical field of transaction processing process optimization, and provides a task issuing method and device, computer equipment and a readable storage medium, and the method comprises the steps: receiving a template editing instruction through a template library, and generating or modifying a task template based on the template editing instruction; in response to the task release request, calling a target task template from a template library, obtaining task basic information and approval chain information, and configuring task trigger rules including a trigger mode, a complex date rule and a precondition; according to the task triggering rule and the target task template, a task instance containing a form is automatically generated, and a task notification is generated and sent to a preset filling terminal; and when the filling terminal fills in the task form, calling a preset verification rule in the target task template in real time to verify input data corresponding to the task form so as to complete release of a task corresponding to the task form. According to the invention, a universal solution is provided for complex scenes such as financial compliance management and medical data submission.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of transaction process optimization, and in particular to a task publishing method and device, a computer device and a readable storage medium. BACKGROUND

[0002] In the business management of the financial field and the medical and health care field, task publishing and data reporting are core process links, but the existing technology has significant defects and cannot meet the needs of complex scenarios.

[0003] In finance, the compliance report reporting and transaction data checking tasks of financial institutions have the characteristics of high frequency, strong timeliness and multiple rules. For example, transaction checking tasks need to be triggered according to the data state of the clearing system every day, and regulatory reports need to be generated on the last working day of the natural month every month. Different business lines of report templates (such as anti-money laundering reports and balance sheets) need to be configured with different field verification rules (such as numerical balance verification and date format verification). However, the existing task publishing system only supports fixed time interval triggering (such as 9 o'clock every day), cannot dynamically adjust the task publishing time according to real-time data state (such as a clearing completion signal), and template configuration relies on technical personnel to modify the code or complex configuration files, so business personnel cannot define field verification rules independently, resulting in low efficiency of compliance task execution, high cost of manual checking, and even regulatory risks caused by rule configuration errors.

[0004] In the medical and health care field, old-age care institutions need to collect old-age health data (blood pressure, medication records) regularly and report them to the regulatory platform, and hospitals need to generate research data reports quarterly. The release frequency of such tasks needs to adapt to the business characteristics: for example, old-age care institutions need to trigger health data collection tasks on the third Friday of each month (the old-age care day), and hospitals need to automatically start data reporting after the clinical trial data meets the requirements. However, the existing system only supports simple period configuration such as "every day / week", cannot parse complex date rules such as "the last day of each quarter", and the approval process needs to be forwarded manually, and there is a lack of real-time logical verification (such as the correlation verification of medication dosage and body weight) when filling in data, resulting in frequent data omission and error reporting, which seriously affects service quality and regulatory compliance.

[0005] The existing task publishing method has three major problems: insufficient configuration flexibility: template fields and verification rules are fixed and cannot be quickly adapted to the diverse reporting needs of the financial and medical fields; single trigger rule: relies on fixed time intervals and cannot dynamically schedule tasks based on business data state (such as financial clearing completion, medical data meeting requirements) or complex date logic (such as working days, natural month characteristics); low automation: manual intervention is required from task publishing to approval, and data verification is delayed, resulting in low process efficiency and inability to meet high-frequency, high-compliance business scenarios.

[0006] Therefore, there is an urgent need for a method to solve at least one of the above problems. SUMMARY

[0007] The present application provides a task publishing method and device, computer equipment and readable storage medium, aiming at solving the problem that in the business management of the financial field and the medical health and pension field, task publishing and data reporting are core process links, but the existing technology has significant defects and is difficult to meet the needs of complex scenarios.

[0008] In a first aspect, the present application provides a task publishing method, comprising: receiving a template editing instruction through a template library, and generating or modifying a task template based on the template editing instruction; the task template includes a self-definable configurable form structure, field type, verification rule and mandatory attribute, to adapt to the task reporting needs of different business scenarios; in response to a task publishing request, calling a target task template from the template library, obtaining task basic information and approval chain information, and configuring a task trigger rule, the trigger rule including trigger mode, complex date rule and prerequisite condition; According to the task trigger rule and the target task template, a task instance containing a form is automatically generated, and a task notification is generated and sent to a preset reporting terminal; When filling in the task form on the reporting terminal, the preset verification rule in the target task template is called in real time to verify the input data corresponding to the task form, and the verification result is fed back in real time and prompted to correct until the input data passes the verification, completing the publication of the task corresponding to the task form.

[0009] In some embodiments, the generating or modifying a task template based on the template editing instruction comprises: receiving field type selection instructions, verification rule editing instructions and mandatory attribute setting instructions input by an administrator through a graphical interface, the field type including at least one of text, numerical value and date, the verification rule including format verification rule, logic verification rule or association verification rule, and the mandatory attribute being used to mark the fields that must be filled in by the user in the task form; and associating and storing the field type, verification rule and mandatory attribute with the form structure to form a reusable task template.

[0010] In some embodiments, the calling a target task template from the template library in response to a task publishing request comprises: displaying preset task template classification labels on a template library interface, the classification labels including business type labels, template use labels or historical use frequency labels; and retrieving and calling corresponding target task templates from the template library according to user inputted filtering conditions.

[0011] In some embodiments, the task basic information and the approval chain information are acquired, and a task triggering rule is configured, including that the task basic information includes a task name, a task description, and a task deadline, and the approval chain information includes a reporter identifier, an approval person level, and an approval node sequence; the triggering mode includes on-demand triggering, natural day cycle triggering, workday cycle triggering, or single triggering based on a specific time point; the complex date rule is generated by code logic to analyze a date rule described in natural language; and the precondition includes judging whether system data has been updated or whether target data meets a preset threshold through an integrated data verification service or a custom script.

[0012] In some embodiments, a task instance containing a form is automatically generated according to the task triggering rule and a target task template, including that a task form with input controls is generated based on a form structure and a field definition of the target task template, and a type of the input controls corresponds to a type of a preset field in the template one by one; a unique identifier is assigned to the task instance, and notification information containing a task link and a deadline is sent to the reporting terminal according to a notification mode in the task triggering rule.

[0013] In some embodiments, when the task form is filled in the reporting terminal, a preset verification rule in the target task template is called in real time to verify input data corresponding to the task form, including that when it is detected that a user completes single field input or submits a form operation, the verification rule of the corresponding field is triggered in real time; if the input data does not meet a format verification rule, error prompt information of the corresponding field is displayed on the reporting terminal interface; if the input data does not meet a logic verification rule or an association verification rule, a global error prompt and a correction guide are displayed on the reporting terminal interface until the input data passes all preset verification rules.

[0014] In some embodiments, before the publication of the task corresponding to the task form is completed, the task form is further transferred to a corresponding approval terminal according to preset approval chain information, and after approval information of the approval terminal is acquired, an approval record is formed and is associated to the task instance.

[0015] In a second aspect, the present application provides a task publishing device, including: An instruction receiving unit is configured to receive a template editing instruction through a template library, and generate or modify a task template based on the template editing instruction; the task template contains a self-definable configurable form structure, a field type, a verification rule, and a required attribute, so as to adapt to task reporting needs of different business scenarios; The template calling unit is configured to, in response to a task publishing request, call a target task template from the template library, acquire task basic information and approval chain information, and configure a task triggering rule, the triggering rule including a triggering mode, a complex date rule, and a precondition. The instance generating unit is configured to automatically generate a task instance including a form according to the task triggering rule and the target task template, and generate a task notification and send the task notification to a preset filing terminal. The publishing completion unit is configured to, when the task form is filled in the filing terminal, call a preset verification rule in the target task template to verify input data corresponding to the task form in real time, feed back a verification result and prompt correction in real time, until the input data passes the verification, and complete publishing of a task corresponding to the task form.

[0016] In a third aspect, the present application further provides a computer device, comprising: a memory and a processor; the memory is configured to store a computer program; the processor is configured to execute the computer program and implement the steps of the task publishing method according to the first aspect.

[0017] In a fourth aspect, the present application further provides a computer readable storage medium, which stores a computer program, and the computer program, when executed by a processor, causes the processor to implement the steps of the task publishing method according to the first aspect.

[0018] The present application provides a task publishing method, which significantly improves the efficiency and accuracy of task execution in complex business scenarios through customizable template configuration, multi-dimensional triggering rules, and full-process automation mechanism.

[0019] Through template library customization of form structure, field type (text / numerical value / date), verification rule (format / logic / association verification), and mandatory attribute, business personnel can independently configure financial report templates (such as anti-money laundering field association verification) and pension data collection templates (such as physical examination date format verification); configure triggering modes (on demand / natural day / workday / specific time point), parse complex date rules such as "the third Friday of each month" through code logic, support using system data status (such as financial clearing completion, medical data compliance) as a precondition for task publishing; automatically generate a task form according to the template and the triggering rule, verify the filing data in real time (such as financial numerical value balance verification, pension drug dosage logic verification), and automatically transfer the approval chain (such as financial multi-level compliance approval, medical data grading review), forming a closed-loop management.

[0020] Through visual template editing, financial institutions can quickly customize different regulatory report templates, and pension institutions can flexibly configure physical examination data collection rules without technical intervention, and the response speed is improved by more than 80%; support for "data state + complex date" dual trigger conditions solves the needs of the financial field "reporting immediately after clearing" and the medical field "automatic reporting of data meeting standards", and the task triggering accuracy is improved by 95%; real-time data verification avoids manual checking errors (such as financial report value imbalance and pension data format error), and the automatic transfer of the approval process reduces manual intervention, the process efficiency is improved by 70%, and the compliance cost and management risk are significantly reduced.

[0021] The application provides a universal solution for complex scenarios such as financial compliance management and medical data reporting through modular and intelligent design, and fundamentally solves the core defects of the prior art in flexibility, accuracy and automation.

[0022] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF DRAWINGS

[0023] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0024] Figure 1 is a step schematic flow chart of a task publishing method provided by an embodiment of the present application; Figure 2 is a structural schematic diagram of a task publishing device provided by an embodiment of the present application; Figure 3 is a structural schematic block diagram of a computer device provided by an embodiment of the present application.

[0025] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. DETAILED DESCRIPTION

[0026] The technical solutions in the embodiments of the present application will be described clearly and completely in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0027] The flowcharts shown in the drawings are merely illustrative and do not necessarily include all contents and operations / steps, nor are they necessarily executed in the order described. For example, some operations / steps can also be decomposed, combined or partially merged, so the actual execution order can be changed according to actual conditions.

[0028] It should be understood that, in order to facilitate clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the terms "first", "second", etc. are used to distinguish the same or similar items with basically the same functions and effects. Those skilled in the art can understand that the terms "first", "second", etc. do not limit the quantity and execution order, and the terms "first", "second", etc. also do not necessarily mean different.

[0029] It should be understood that the terms used in this application specification are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in the application specification and the appended claims, the singular forms "a", "an" and "the" are intended to include plural forms unless the context clearly indicates otherwise.

[0030] It should also be understood that the term "and / or" used in the application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes these combinations.

[0031] Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The following embodiments and features in the embodiments can be combined with each other without conflict.

[0032] In finance, the compliance report submission of financial institutions and transaction data checking tasks have the characteristics of high frequency, strong timeliness and multiple rules. For example, daily transaction checking tasks need to be triggered according to the data state of the clearing system, monthly regulatory reports need to be generated on the last working day of the natural month, and different business line report templates (such as anti-money laundering reports and balance sheets) need to be configured with differentiated field verification rules (such as numerical balance verification and date format verification). However, the existing task publishing system only supports fixed time interval triggering (such as 9 o'clock every day), cannot dynamically adjust the task publishing time according to the real-time data state (such as the clearing completion signal), and the template configuration relies on technical personnel to modify the code or complex configuration files, and business personnel cannot define field verification rules independently, resulting in low efficiency of compliance task execution, high cost of manual checking, and even regulatory risks caused by rule configuration errors.

[0033] In the medical and health care for the elderly scene, the old-age institution needs to collect the health data of the elderly (blood pressure, medication record) regularly and report to the regulatory platform, and the hospital needs to generate research data report quarterly. The release frequency of such tasks needs to adapt to the business characteristics: such as the old-age institution needs to trigger the health data collection task on the third Friday of each month (the elderly physical examination day), and the hospital needs to automatically start data reporting after the clinical trial data meets the standard. However, the existing system only supports simple period configuration such as "every day / week", cannot parse complex date rules such as "the last day of each quarter", and the approval process needs to be forwarded manually, and there is a lack of real-time logical verification (such as the association verification of medication dose and body weight) when filling in data, which leads to frequent data omission and error reporting, seriously affecting service quality and regulatory compliance.

[0034] The existing task release method has three major problems: insufficient configuration flexibility: template fields and verification rules are fixed, making it difficult to quickly adapt to the diverse reporting needs of financial and medical fields; single trigger rule: relying on fixed time intervals, unable to combine business data status (such as financial clearing completion, medical data meeting the standard) or complex date logic (such as working days, natural month characteristics) to dynamically schedule tasks; low automation: manual intervention is required from task release to approval, data verification is delayed, resulting in low process efficiency and inability to meet high-frequency, high-compliance business scenarios.

[0035] Therefore, there is an urgent need for a method to solve at least one of the above problems.

[0036] To solve the above problems, please refer to Figure 1 , Figure 1 is a schematic flowchart of the task release method provided by an embodiment of the present application. The task release method can be implemented by a computer device, which can be deployed on a single server or a server cluster. It can also be deployed on a handheld terminal, a notebook computer, a wearable device, or a robot, etc.

[0037] It should be noted that the acquisition of any information mentioned in the provided method is in accordance with relevant regulations and with the consent of the user, and does not infringe on the user's privacy or violate relevant laws and regulations.

[0038] To solve the above problems, please refer to Figure 1 . Specifically, as shown in Figure 1 , the provided task release method includes steps S101 to S104. The details are as follows: Step S101. Receive template editing instructions through a template library, and generate or modify a task template based on the template editing instructions; the task template includes self-definable configuration of form structure, field type, verification rule and mandatory attribute, to adapt to the task filling needs of different business scenarios.

[0039] Specifically, the administrator's visual editing instructions are received through the template library interface, supporting the core elements of customizing the task template: form structure: drag-and-drop generation of form field layout (such as single-line text, multi-line text, drop-down menu); field type: supporting basic types such as text, numerical value, date, file upload, and business-specific types (such as financial account number, medical record number); verification rules: including format checking (such as email format, identity card number regular matching), logical checking (such as numerical value range limitation, non-negative constraint), and association checking (such as field A value needs to be greater than field B value); mandatory attributes: marking key business fields (such as "transaction amount" in financial report, "patient name" in medical form), and prohibiting submission if not filled in.

[0040] In the financial scenario, the application scenario can configure the "anti-money laundering transaction report template" field: add "transaction account" (text type, need to meet the bank account format regular verification), "transaction amount" (numerical value type, mandatory and need to be ≥0), "counterparty" (association verification: need to match with the enterprise name in the customer information library); visual editing: through the template management interface of the financial business platform, compliance officers can drag and drop to generate fields without code capability, and configure logical verification rules for "transaction amount + counterparty risk level" (such as single transaction exceeding 500,000 yuan needs to trigger high-risk marking).

[0041] In the medical and health care scenario, the application scenario: configure the "nursing home monthly health data collection template" field configuration: add "old man's name" (mandatory text), "blood pressure value" (numerical value type, need to meet the logical verification of systolic pressure 90-140mmHg), "medication date" (date type, need to be later than the last medication date 72 hours association verification); visual editing: the nursing home administrator can preset the "blood pressure value and age association verification rule" (such as the systolic pressure upper limit for people over 80 years old is relaxed to 150mmHg) in the template through the nursing management system, forming differentiated verification logic.

[0042] Financial compliance officers and nursing home administrators can independently complete template configuration without relying on IT departments, and the template iteration cycle is shortened from traditional "weekly" to "minutes"; supporting differentiated configuration of financial field multi-regulatory reports (anti-money laundering, credit investigation, balance sheet) and individualized collection of medical and nursing field health data, medication records, and nursing logs, avoiding the problem of field redundancy or missing verification caused by "one template for all"; common templates (such as quarterly regulatory reports, monthly health records) can be saved to the template library for repeated calling, reducing repetitive configuration work and reducing human error rate.

[0043] Step S102. In response to the task publishing request, a target task template is called from the template library, task basic information and approval chain information are obtained, and a task triggering rule is configured, the triggering rule including a triggering mode, a complex date rule, and a precondition.

[0044] Specifically, in response to a task publishing request, three elements are configured: template calling: retrieving and loading a target template (such as a “quarterly regulatory report template” in a financial scenario or a “clinical trial data reporting template” in a medical scenario) from the template library; basic information input: filling in the task name, deadline, and reporter / approver roles (such as “2024 Q2 anti-money laundering report” in a financial scenario or “diabetes patient medication data collection task” in a medical scenario); triggering rule configuration: triggering mode: on-demand triggering (manual immediate publishing), periodic triggering (natural day / working day cycle), and single-time triggering (specific time point such as “2024-12-31 17:00”); complex date rule: natural language dates are parsed through code (such as “every third Friday of the quarter” and “10 working days before the Spring Festival each year”), and accurate scheduling times are generated; precondition: relying on system data state (such as a “clearing completion” flag in a financial clearing system or a “sample size meets the standard” signal in a medical data platform) as a pre-triggering condition.

[0045] In a financial scenario, application scenario: configuring a “cross-border transaction daily report task” triggering rule: triggering mode: periodic triggering by working day (excluding weekends and statutory holidays); complex date rule: analyzing “every last working day of the month” to generate a monthly summary task; precondition: obtaining the “daily transaction reconciliation completion” status of the clearing system through an API, and if it is not completed, rechecking after 1 hour, until the status is “completed” to trigger the task.

[0046] In a medical and health care scenario, application scenario: configuring a “chronic disease patient medication reminder task” triggering rule: triggering mode: periodic triggering by natural day (8:00 and 18:00 every day); complex date rule: analyzing “the 10th of every month (patient follow-up day)” to trigger an additional medication adherence survey task; precondition: interfacing with an electronic health record system, and if the patient has not uploaded medication records in the past 30 days, a supplementary task is automatically triggered.

[0047] Solve the problem of "relying on manual judgment of clearing state" in the financial field and "fixed time triggering ignoring data integrity" in the medical field. The task triggering accuracy is improved from 70% in the traditional scheme to more than 95%. Support embedding financial compliance rules (such as workday scheduling) and medical business processes (such as re-examination day association) into the triggering condition to avoid resource waste or task omission caused by "one-size-fits-all" fixed time scheduling. Through the configuration of the precondition, the data state linkage between task publishing and core business systems (financial clearing system, medical electronic archives) is realized, forming a closed loop of "data ready → task automatic triggering".

[0048] Step S103. According to the task triggering rule and the target task template, a task instance containing a form is automatically generated, and a task notification is sent to the preset reporting terminal.

[0049] Specifically, based on the configured triggering rule and template, an interactive task instance is automatically generated and the reporter is reached: form instance generation: render input controls according to template field types (such as numerical value fields corresponding to numerical input boxes, date fields corresponding to calendar selectors), associate with preset validation rules; task unique identifier: generate UUID or task number according to "business type + timestamp" rule (such as financial scenario "FX20240627001", medical scenario "HL20240627001"); multi-channel notification: send task notification through SMS, email, APP push, system intranet letter, etc., including task link, deadline, reporting requirements (such as financial report needs to attach transaction voucher scans, medical form needs to upload examination report).

[0050] In the financial scenario, application scenario: generate "monthly balance sheet reporting task" form instance: automatically generate a form containing "asset subject", "liability subject", and "owner's equity" fields according to the template, and automatically associate the numerical value fields with the logical validation rule "asset = liability + owner's equity"; notification method: send an email notification to the financial personnel, with the title "

Emergency

[0051] In the medical and health care scenario, application scenario: generate "old people's quarterly physical examination data entry task" form instance: generate a form containing "height", "weight", and "electrocardiogram result" fields according to the template, and associate the "weight" field with the automatic calculation function "BMI = weight / (height ^ 2)" and health level prompt (such as BMI ≥ 28 marked red warning); notification method: push task reminders to nursing staff through the exclusive APP of the nursing home, with voice broadcast function ("Please complete the physical examination data entry of Mr. Zhang in room 302 within 3 days"), and pop up a to-do list window on the PC.

[0052] Avoid the inefficient process of "manually creating forms -> notifying fillers one by one" in traditional solutions, task generation efficiency is improved by more than 90%, and human error is eliminated. Business information integrity: Form fields are strictly aligned with templates, and notification content automatically includes business scenario-specific requirements (such as financial report attachments and medical form report formats), reducing the cost of fillers' information acquisition. Support for PC, mobile (APP / H5) to receive tasks simultaneously, meet the needs of financial institutions headquarters-branch collaborative reporting, and mobile real-time input for nursing staff in nursing homes.

[0053] Step S104. When filling in the task form at the reporting terminal, real-time call the preset verification rules in the target task template to check the input data corresponding to the task form, real-time feedback the verification result and prompt for correction, until the input data passes the verification, complete the release of the task corresponding to the task form.

[0054] Specifically, when the filler fills in the form, real-time three-layer verification and dynamic feedback are performed: format verification: instant verification of field input format (such as financial account length, medical date format), real-time red prompt if not compliant; logic verification: single field value verification based on business rules (such as financial transaction amount cannot be negative, medical drug dosage cannot exceed the maximum dosage specified in the instructions); correlation verification: cross-field linkage verification (such as financial scenario "cumulative transaction amount = sum of single transaction amounts", medical scenario "patient age ≥ 65 years old, blood pressure upper limit automatically relaxed by 10 mmHg"); interactive feedback: guide correction through prompts below the input box, global error list, field flashing, etc. Submission is prohibited if the verification fails.

[0055] In the financial scenario, application scenario: fill in the "cross-border remittance application form"; real-time verification: format verification: when the "remitter account number" field is input, real-time comparison with the bank account regular expression, error prompt "account number must be 19 digits, starting with 62"; logic verification: after inputting the "remittance amount" field, automatically verify whether it is ≤ the daily foreign exchange limit (such as 50,000 USD per year for individuals), and if it exceeds the limit, it will be highlighted in red; correlation verification: "recipient country" and "exchange rate type" fields are linked, if "USA" is selected, the USD exchange rate will be automatically loaded, and the "remittance amount x exchange rate" will be verified to be consistent with the "RMB equivalent amount" field.

[0056] In the medical and health care for the elderly scene, the application scenario is filling in the "diabetes patient blood glucose monitoring table"; real-time verification: format verification: the "blood glucose value" field only allows input of 0-800 numerical values, and when non-numeric input, it is emptied immediately and prompts "please enter a valid value"; logic verification: if the "detection time" is "empty stomach", the "blood glucose value" automatically triggers the normal range verification of 3.9-6.1 mmol / L, and when the range is exceeded, it prompts "contact the doctor for confirmation"; association verification: the "insulin dose" field is associated with the "average blood glucose value of the last three times", and if the average blood glucose is > 10 mmol / L, the dose suggestion value automatically increases by 10%, and prompts "suggest filling in after confirmation by the doctor".

[0057] By intercepting the numerical balance error of financial statements and the logic conflict of medical data in the reporting stage, the inefficient cycle of "submitting and then discovering errors by manual review" in the traditional scheme is avoided, and the one-time data pass rate is improved from 50% to more than 90%; business rule visualization: by real-time verification prompts, financial compliance requirements (such as foreign exchange quota restrictions) and medical diagnosis and treatment specifications (such as medication dosage guidelines) are embedded into the reporting process, forming an intelligent guide of "reporting compliance", reducing manual training costs; user experience optimization: immediate feedback of error causes and correction methods, reducing the trial and error time of the reporter, the average reporting time of complex reports in the financial scene is shortened from 40 minutes to 15 minutes, and the data entry efficiency of nursing staff in the medical scene is improved by 60%.

[0058] Through the above four core steps, the application constructs a task publishing system of "flexible configuration → intelligent triggering → automatic execution → real-time verification", and for high-frequency and high-compliance task scenarios in the fields of finance, medical and health care for the elderly, it realizes the paradigm shift from "manual driving" to "rule driving", significantly improves business efficiency, reduces operational risk, and provides core support for the digital transformation of complex business processes.

[0059] In some embodiments, the method further comprises: receiving, through a graphical interface, field type selection instructions, verification rule editing instructions, and mandatory attribute setting instructions input by an administrator, wherein the field type includes at least one of text, numerical value, and date, the verification rule includes a format verification rule, a logic verification rule, or an association verification rule, and the mandatory attribute is used to mark a field that must be filled in by a user; and storing the field type, the verification rule, and the mandatory attribute in association with a form structure to form a reusable task template.

[0060] The administrator can visualize the configuration of the task template core elements through the graphical interface, including: interaction mode: providing a drag-and-drop form designer, supporting field type selection (text / numeric / date), verification rule editing (format / logic / association verification), and mandatory attribute marking; data association: binding the configured field type, verification rule, and mandatory attribute with the form structure, and storing in the template library to form a reusable template.

[0061] In the financial scenario, the application scenario is to configure a "cross-border remittance application template", and the operation process is that the compliance administrator drags and adds "remittance account" (text type, configured with bank account regular format verification, and marked as mandatory), "remittance amount" (numeric type, configured with "≥ 0 and ≤ 50,000 US dollars" logical verification), and "recipient country" (text type, associated with "exchange rate conversion rule" verification) through the graphical interface of the financial middle platform; the storage form is that the template is stored in JSON format, and the field information includes {"field name": "remittance account", "type": "text", "verification rule": "^62\d{17}$", "mandatory": true}.

[0062] In the medical health scenario, the application scenario is to configure a "chronic disease medication record template", and the operation process is that the nurse station administrator drags and adds "patient ID" (text type, configured with 18-digit regular verification, mandatory), "dose" (numeric type, configured with "≤ maximum dose of drug instruction" logical verification), and "time" (date type, associated with "need to be later than the last medication time by 6 hours" verification) through the medical management system interface; the storage form is that the template field association relationship is stored in a database table, including field type, verification logic expression (such as dose <= drug library.max dose), and mandatory identifier. Business personnel (non-technical personnel) can independently complete template design, solve the pain point of "template modification dependent on IT development" in the traditional scheme, and improve the template iteration efficiency by 90%; customized verification rules are provided for scene-specific fields such as financial account and medical ID to avoid verification loopholes caused by "one-size-fits-all" of general templates; common templates can be directly copied and reused, such as sharing anti-money laundering templates among different branches of financial institutions and reusing medication templates among different departments of medical institutions, reducing repetitive configuration work.

[0063] In some embodiments, the target task template is called from the template library in response to a task publishing request, including: displaying preset task template classification labels on the template library interface, the classification labels including business type labels, template purpose labels, or historical use frequency labels; retrieving and calling the corresponding target task template from the template library according to the user input filtering conditions.

[0064] A classification retrieval mechanism is established in the template library, including: classification labels: preset business types (finance / medical), template purposes (reporting / collection), historical usage frequencies (high / low) and the like; and retrieval logic: supporting retrieval of target templates according to label combinations (such as "finance + report + high frequency") or keywords (template name, applicable scenario).

[0065] In the financial scenario, a "money laundering transaction report template" is quickly retrieved; the interface display: the classification tree is displayed on the left side of the template library interface, and the hierarchy is "business type -> finance" -> "template purpose -> regulatory report" -> "usage frequency -> high frequency"; the retrieval operation: the user inputs the screening condition "money laundering + 2024 version", the system matches the labels "business type = finance", "purpose = compliance report" and the template name keyword, and the target template is located in seconds.

[0066] In the medical health scenario, a "senior health record collection template" is found, and the labels "business type -> medical health and old age care", "purpose -> data collection" and "applicable object -> old age care institution" are marked; the nursing supervisor selects "medical health and old age care + data collection" in the screening bar, and inputs the keyword "senior", and the system preferentially displays the top 3 templates in terms of historical usage frequency.

[0067] Blind searching in a large number of templates is avoided, and the template retrieval time of compliance personnel of a financial institution is shortened from "10 minutes / each time" to "30 seconds / each time"; hierarchical classification is performed according to business characteristics (such as financial regulatory level and medical data sensitivity), to meet the compliance requirements of the financial industry "strict isolation of different regulatory reports" and the medical industry "division management of medical / old age care templates"; high-frequency templates are preferentially displayed, to reduce repetitive work and meet the business characteristics of "fixed template high-frequency reuse" in the financial and medical scenarios.

[0068] In some embodiments, the task basic information and the approval chain information are acquired, and a task triggering rule is configured, including: the task basic information includes a task name, a task description and a task deadline, and the approval chain information includes a reporter identifier, an approval person level and an approval node sequence; the triggering mode includes on-demand triggering, natural day cycle triggering, working day cycle triggering or single triggering based on a specific time point; the complex date rule is generated by code logic to analyze the date rule described in natural language to generate a task scheduling time; and the precondition includes judging whether system data has been updated or whether target data meets a preset threshold through an integrated data verification service or a custom script.

[0069] Elements of task publishing configuration are refined, including: basic information: task name, description, deadline, and approval chain information (reporter role, approval level, node sequence); and triggering rule: supporting "triggering mode (periodic / single / on-demand) + complex date analysis (natural language to time) + precondition (data state verification)" combination configuration.

[0070] In the financial scenario, by configuring "monthly clearing report task"; approval chain: the reporter is fixed as "clearing group officer", the approval chain is "department supervisor preliminary review → compliance department review → financial director final review", the node order strictly follows the hierarchical flow trigger rule: trigger mode: triggered every month on the last day at 18:00; complex date: analyze "the last working day of each month" (automatically exclude holidays); precondition: obtain the "monthly transaction reconciliation completion" status of the clearing system through API, and if it is not completed, it will be re-verified in 2 hours.

[0071] In the medical health scenario, by configuring "postoperative patient follow-up task"; approval chain: the reporter is "responsible nurse", the approval chain is "nurse supervisor review → attending physician final review", and the node supports parallel approval (nurse supervisor and attending physician can audit at the same time); trigger rule: trigger mode: triggered as needed (manually started after surgery); complex date: none (single trigger); precondition: interface with HIS system, and when the patient "postoperative hospitalization days ≥ 7 days and vital signs are stable", automatically publish the follow-up task to the nurse station.

[0072] Financial multi-level compliance approval and medical hierarchical quality control are automatically executed through pre-set approval chain, avoiding process confusion caused by manual flow, and improving approval efficiency by 40%; solving the complex needs of financial "holiday skipping" and medical "triggering when condition meets", the task triggering accuracy rate is improved from 70% of the traditional scheme to 95%; through the integration of core business system data (such as financial clearing status, medical electronic medical record), the intelligent scheduling of "data ready → task automatically started" is realized.

[0073] In some embodiments, the task instance containing the form is automatically generated according to the task trigger rule and the target task template, including: based on the form structure and field definition of the target task template, generating a task form with input controls, the input control type corresponds to the field type in the template one by one; assign a unique identifier to the task instance, and according to the notification mode in the task trigger rule, send notification information containing task link and deadline to the reporting terminal.

[0074] Based on the template and the trigger rule to generate the task instance, including: form rendering: generate corresponding input controls (text box / number input box / calendar component) according to template field type, bind verification rules; task identification: generate a unique task ID (such as "FIN-20240627-001" "HL-20240627-001"); notification mechanism: support message push, email, system pop-up window, with task link and deadline.

[0075] In the financial scenario, a "quarterly asset balance sheet reporting task" is generated; the form rendering: the "total assets" field generates a numerical input box, associated with the "must be > 0" logical verification; the "preparation date" field generates a calendar component, limiting the selection to the last day of the quarter; notification sending: send an email to the financial personnel with the title "

Important

[0076] In the medical health scenario, a "vaccine inoculation record supplement task" is generated; form rendering: the "vaccine batch number" field generates a text input box, configured with "8-digit + letter combination" format verification; the "inoculation date" field is associated with the "must be within the valid period" logical verification; notification sending: push a pop-up window notification to the community health service station personnel through the medical APP, with a voice reminder "Please supplement the child's vaccine inoculation record within 3 days", and click the pop-up window to directly jump to the filling interface.

[0077] Instead of the traditional "manually create forms → notify one by one" inefficient process, the task generation time is reduced from "30 minutes / time" to "seconds", and the problem of missing and wrong sending is eliminated; The input control strictly matches the field type (such as date field prohibited text input), reducing the operation error of the filler, and the financial report filling error rate is reduced from 20% to less than 5%; support for PC and mobile terminal to receive tasks synchronously, meet the multi-scenario needs of financial institutions headquarters-branch collaboration and medical community-general hospital data interconnection.

[0078] In some embodiments, when filling in the task form at the filling terminal, the pre-set verification rules in the target task template are called in real time to verify the input data corresponding to the task form, including: when detecting that the user has completed single field input or submitted the form operation, triggering the verification rule of the corresponding field in real time; if the input data does not meet the format verification rule, displaying the error prompt information of the corresponding field on the filling terminal interface; if the input data does not meet the logical verification rule or the association verification rule, displaying the global error prompt and correction guide on the filling terminal interface until the input data passes all pre-set verification rules.

[0079] Real-time three-level verification and feedback during filling: verification timing: trigger format / logical verification when single field input is completed, trigger association verification when form is submitted; feedback mechanism: format error field level prompt (such as red border + error information), global prompt for logical / association errors (such as top error list + correction guide).

[0080] In the financial scenario, the "customer risk level assessment form" is filled out; real-time verification: format verification: after the "customer ID number" is input, it is immediately compared with 18 regular numbers, and when an error occurs, the "please enter the correct 18-digit ID number" is prompted; logical verification: after the "annual income" field is input, it is verified whether it is greater than or equal to 0, and when it is negative, the "income cannot be negative" is prompted in red; correlation verification: when submitted, it is checked whether the "risk tolerance level" matches the "investment experience years" (for example, if the experience is less than 1 year, the level cannot be "high risk"), and when it does not match, the "risk level needs to be consistent with the investment experience" is prompted globally.

[0081] In the medical health scenario, the "pregnant woman's prenatal examination record form" is filled out. Real-time verification is performed through format verification: the "gestational age" field is only allowed to input integers from 1 to 42, and when non-numeric input is input, it is automatically emptied and the "please enter the valid gestational age" is prompted; logical verification: after the "blood pressure value" is input, it is verified whether the systolic pressure is within 90-140 mmHg, and when it is out of range, the "abnormal blood pressure, please review" is prompted; correlation verification: when submitted, it is checked whether the "weight gain" is consistent with the standard curve (for example, the weight gain should be less than or equal to 5 kg when the gestational age is 20 weeks), and when it deviates, the "abnormal weight gain, please contact the doctor" is prompted globally.

[0082] By intercepting financial compliance errors (such as ID number format) and medical logic conflicts (such as gestational age weight abnormalities) in the filling stage, the traditional "submit and then manually review and return" inefficient cycle is avoided, and the one-time data pass rate is increased from 60% to 92%; by real-time prompting, the financial regulatory requirements (such as ID verification) and medical diagnosis and treatment standards (such as blood pressure standards) are embedded into the interaction process, forming an "filling is compliant" intelligent guide, reducing the cost of manual training; the error position and reason are fed back immediately, the financial complex report filling time is shortened from 30 minutes to 10 minutes, and the medical form entry efficiency is improved by more than 50%.

[0083] In some embodiments, before the task form corresponding to the task is completed, the method further comprises: according to the pre-set approval chain information, the task form is transferred to the corresponding approval terminal, and after the approval information of the approval terminal is obtained, an approval record is formed and is associated with the task instance.

[0084] Please refer to Figure 2 , as shown in the figure, Figure 2 is a structural schematic diagram of a task publishing device 200 provided by the embodiments of the present application. The task publishing device 200 is used to execute the steps of the task publishing method shown in the above embodiments. The task publishing device 200 can be a single server or a server cluster, or the task publishing device 200 can be a terminal, which can be a handheld terminal, a notebook computer, a wearable device, or a robot, etc.

[0085] As shown in Figure 2 , the task publishing device 200 comprises: The instruction receiving unit 201 is configured to receive a template editing instruction through a template library, and generate or modify a task template based on the template editing instruction; the task template includes a self-definable configurable form structure, a field type, a verification rule, and a required attribute, so as to adapt to the task reporting needs of different business scenarios; The template calling unit 202 is configured to call a target task template from the template library in response to a task publishing request, obtain task basic information and approval chain information, and configure a task triggering rule, the triggering rule including a triggering mode, a complex date rule, and a prerequisite condition. The instance generating unit 203 is configured to automatically generate a task instance including a form according to the task triggering rule and the target task template, and generate a task notification and send it to a preset reporting terminal. The publishing completion unit 204 is configured to call a preset verification rule in the target task template to check input data corresponding to a task form in real time when the task form is filled in the reporting terminal, and real-time feedback the checking result and prompt for correction until the input data passes the checking, and the publishing of the task corresponding to the task form is completed.

[0086] In some embodiments, the generating or modifying a task template based on the template editing instruction includes: receiving a field type selection instruction, a verification rule editing instruction, and a required attribute setting instruction input by an administrator through a graphical interface, the field type including at least one of text, numerical value, and date, the verification rule including a format verification rule, a logic verification rule, or an association verification rule, and the required attribute is used to mark a field in the task form that must be filled in by a user; and associating and storing the field type, the verification rule, and the required attribute with the form structure to form a reusable task template.

[0087] In some embodiments, the calling a target task template from the template library in response to a task publishing request includes: displaying a preset task template classification label on a template library interface, the classification label including a business type label, a template use label, or a historical use frequency label; and retrieving and calling a corresponding target task template from the template library according to a user inputted filtering condition.

[0088] In some embodiments, the task basic information and the approval chain information are acquired, and a task triggering rule is configured, including that the task basic information includes a task name, a task description, and a task deadline, and the approval chain information includes a reporter identifier, an approval person level, and an approval node sequence; the triggering mode includes on-demand triggering, natural day cycle triggering, workday cycle triggering, or single triggering based on a specific time point; the complex date rule is generated by code logic to analyze a date rule described in natural language; and the precondition includes judging whether system data has been updated or whether target data meets a preset threshold through an integrated data verification service or a custom script.

[0089] In some embodiments, a task instance containing a form is automatically generated according to the task triggering rule and a target task template, including that a task form with input controls is generated based on a form structure and a field definition of the target task template, and a type of the input control corresponds to a type of a preset field in the template one by one; a unique identifier is assigned to the task instance, and notification information containing a task link and a deadline is sent to the reporting terminal according to a notification mode in the task triggering rule.

[0090] In some embodiments, when the task form is filled in the reporting terminal, a preset verification rule in the target task template is called in real time to verify input data corresponding to the task form, including that when it is detected that a user completes single field input or submits a form operation, the verification rule of the corresponding field is triggered in real time; if the input data does not meet a format verification rule, error prompt information of the corresponding field is displayed on the reporting terminal interface; if the input data does not meet a logic verification rule or an association verification rule, a global error prompt and a correction guide are displayed on the reporting terminal interface until the input data passes all preset verification rules.

[0091] In some embodiments, before the task corresponding to the task form is completed, the task form is further transferred to a corresponding approval terminal according to preset approval chain information, and after approval information of the approval terminal is acquired, an approval record is formed and is associated to the task instance.

[0092] It should be noted that, for the convenience and brevity of description, the specific working process of the task publishing device and each module described above can refer to the corresponding process in the task publishing method embodiments described above, which will not be described herein.

[0093] The task publishing method described above can be implemented in the form of a computer program, which can run on the device as shown in Figure 2 .

[0094] Please refer toFigure 3 , Figure 3 is a structural schematic block diagram of a computer device provided by an embodiment of the present application. The computer device comprises a processor, a memory and a network interface connected through a device bus, wherein the memory can comprise a storage medium and an internal memory.

[0095] The storage medium can store an operating device and a computer program. The computer program comprises program instructions which, when executed, can cause the processor to perform any one of the task publishing methods.

[0096] The processor is configured to provide computing and control capabilities to support the operation of the entire computer device.

[0097] The internal memory provides an environment for the operation of the computer program in the non-volatile storage medium, which, when executed by the processor, can cause the processor to perform any one of the task publishing methods.

[0098] The network interface is configured to perform network communication, such as sending assigned tasks, etc. Those skilled in the art can understand that the structure shown in the above embodiment is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the terminal to which the scheme of the present application is applied. A specific computer device can comprise more or fewer components than those shown in the figure, or some components can be combined, or have a different arrangement of components. Figure 3

[0099] It should be understood that the processor can be a central processing unit (CPU), and the processor can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0100] In one embodiment, the processor is configured to run a computer program stored in the memory to implement the following steps: receive a template editing instruction through the template library, and generate or modify a task template based on the template editing instruction; the task template comprises a self-definable configuration of a form structure, a field type, a verification rule and a required attribute, so as to adapt to the task reporting needs of different business scenarios; ​In response to a task publishing request, a target task template is called from the template library, task basic information and approval chain information are obtained, and a task triggering rule is configured, the triggering rule including a triggering mode, a complex date rule, and a precondition; According to the task triggering rule and the target task template, a task instance containing a form is automatically generated, and a task notification is generated and sent to a preset reporting terminal; When the task form is filled in at the reporting terminal, the preset verification rule in the target task template is called in real time to verify the input data corresponding to the task form, the verification result is fed back in real time and a correction is prompted until the input data passes the verification, and the publishing of the task corresponding to the task form is completed.

[0101] In some embodiments, the task template is generated or modified based on the template editing instruction, including: receiving field type selection instructions, verification rule editing instructions, and mandatory attribute setting instructions input by an administrator through a graphical interface, the field type including at least one of text, numerical value, and date, the verification rule including format verification rule, logic verification rule, or association verification rule, and the mandatory attribute is used to mark a field in the task form that must be filled in by a user; the field type, the verification rule, and the mandatory attribute are associated with the form structure and stored to form a reusable task template.

[0102] In some embodiments, the target task template is called from the template library in response to the task publishing request, including: preset task template classification labels are displayed on a template library interface, the classification labels including a business type label, a template use label, or a historical use frequency label; according to a user input filter condition, a corresponding target task template is retrieved and called from the template library.

[0103] In some embodiments, the task basic information and the approval chain information are obtained, and the task triggering rule is configured, including: the task basic information includes a task name, a task description, and a task deadline, the approval chain information includes a reporter identifier, an approval person level, and an approval node sequence; the triggering mode includes on-demand triggering, natural day cycle triggering, workday cycle triggering, or single triggering based on a specific time point; the complex date rule generates a task scheduling time by code logic to analyze a date rule described in natural language; the precondition includes judging whether system data has been updated or whether target data meets a preset threshold through an integrated data verification service or a custom script.

[0104] In some embodiments, automatically generating a task instance containing a form based on the task triggering rules and the target task template includes: generating a task form with input controls based on the form structure and field definitions of the target task template, wherein the input control types correspond one-to-one with the preset field types in the template; assigning a unique identifier to the task instance; and sending notification information containing a task link and a deadline to the filling terminal according to the notification method in the task triggering rules.

[0105] In some embodiments, when filling out a task form on the form-filling terminal, the step of real-time invoking of preset verification rules in the target task template to verify the input data corresponding to the task form includes: when a user completes a single field input or submits a form, the corresponding field's verification rule is triggered in real time; if the input data does not conform to the format verification rule, an error message for the corresponding field is displayed on the form-filling terminal interface; if the input data does not conform to the logical verification rule or the association verification rule, a global error message and correction guidance are displayed on the form-filling terminal interface until the input data passes all preset verification rules.

[0106] In some embodiments, before the task corresponding to the task form is published, the method further includes: transferring the task form to the corresponding approval terminal according to preset approval chain information, and after obtaining the approval information of the approval terminal, forming an approval record and associating it with the task instance.

[0107] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to perform the steps of the task publishing method described in the first aspect above.

[0108] The computer-readable storage medium may be an internal storage unit of the computer device described in the foregoing embodiments, such as the hard disk or memory of the computer device. The computer-readable storage medium may also be an external storage device of the computer device, such as a plug-in hard disk, SmartMedia Card (SMC), Secure Digital (SD) card, or Flash Card equipped on the computer device.

[0109] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A task publishing method, characterized in that, include: Receive template editing instructions from the template library, and generate or modify task templates based on the template editing instructions; The task template includes a customizable form structure, field types, validation rules, and required attributes to adapt to the task reporting needs of different business scenarios. In response to a task release request, the target task template is retrieved from the template library, basic task information and approval chain information are obtained, and task triggering rules are configured. The triggering rules include triggering method, complex date rules and preconditions. Based on the task triggering rules and target task template, a task instance containing a form is automatically generated, and a task notification is generated and sent to the preset filling terminal. When the task form is filled out on the reporting terminal, the preset verification rules in the target task template are called in real time to verify the input data corresponding to the task form, and the verification results are fed back in real time and corrections are prompted until the input data passes the verification and the task corresponding to the task form is published.

2. The method according to claim 1, characterized in that, The process of generating or modifying a task template based on the template editing instructions includes: The system receives field type selection instructions, validation rule editing instructions, and required attribute setting instructions from the administrator through a graphical interface. The field types include at least one of text, numeric, and date. The validation rules include format validation rules, logical validation rules, or association validation rules. The required attributes are used to mark fields that users must fill in in the task form. The field types, validation rules, and required attributes are associated with the form structure and stored to form a reusable task template.

3. The method according to claim 1, characterized in that, The step of responding to a task release request by retrieving the target task template from the template library includes: The template library interface displays preset task template category tags, which include business type tags, template purpose tags, or historical usage frequency tags. Based on the filtering criteria input by the user, the corresponding target task template is retrieved from the template library and called.

4. The method according to claim 1, characterized in that, The process of obtaining basic task information and approval chain information, and configuring task triggering rules, includes: The basic information of the task includes the task name, task description and task deadline, and the approval chain information includes the submitter's identifier, approver level and approval node sequence. The triggering methods include on-demand triggering, triggering based on a natural day cycle, triggering based on a workday cycle, or single triggering based on a specific time point; The complex date rules are generated by parsing date rules described in natural language through code logic to produce task scheduling times; The prerequisites include determining whether the system data has been updated and whether the target data meets the preset threshold through an integrated data verification service or a custom script.

5. The method according to claim 1, characterized in that, The step of automatically generating a task instance containing a form based on the task triggering rules and the target task template includes: Based on the form structure and field definition of the target task template, a task form with input controls is generated, wherein the input control types correspond one-to-one with the preset field types in the template; Assign a unique identifier to the task instance, and send a notification message containing the task link and deadline to the reporting terminal according to the notification method in the task triggering rules.

6. The method according to claim 1, characterized in that, When filling out the task form on the data entry terminal, the system calls the preset verification rules in the target task template in real time to verify the input data corresponding to the task form, including: When a user completes input in a single field or submits a form, the corresponding field's validation rules are triggered in real time. If the input data does not conform to the format validation rules, the corresponding error message will be displayed on the form filling terminal interface; If the input data does not conform to the logical verification rules or the association verification rules, a global error message and correction instructions will be displayed on the data entry terminal interface until the input data passes all preset verification rules.

7. The method according to claim 1, characterized in that, Before publishing the task corresponding to the completed task form, the following steps are also included: The task form is transferred to the corresponding approval terminal according to the preset approval chain information. After obtaining the approval information from the approval terminal, an approval record is formed and associated with the task instance.

8. A task issuing device, characterized in that, include: The instruction receiving unit is used to receive template editing instructions through the template library, and generate or modify task templates based on the template editing instructions. The task template includes a customizable form structure, field types, validation rules, and required attributes to adapt to the task reporting needs of different business scenarios. The template calling unit is used to respond to the task release request, call the target task template from the template library, obtain the basic task information and approval chain information, and configure the task triggering rules, which include triggering method, complex date rules and preconditions; The instance generation unit is used to automatically generate a task instance containing a form according to the task triggering rules and the target task template, and generate a task notification to send to the preset filling terminal. The release completion unit is used to call the preset verification rules in the target task template in real time to verify the input data corresponding to the task form when the task form is filled in on the filling terminal, provide real-time feedback on the verification results and prompt for correction, until the input data passes the verification and the release of the task corresponding to the task form is completed.

9. A computer device, characterized in that, The computer device includes a memory and a processor; The memory is used to store computer programs; The processor is configured to execute the computer program and, in executing the computer program, implement the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, causes the processor to implement the method as described in any one of claims 1 to 7.

Images