WO2018201774A1 - 数据审批方法、装置、设备和计算机可读存储介质 - Google Patents

数据审批方法、装置、设备和计算机可读存储介质 Download PDF

Info

Publication number
WO2018201774A1
WO2018201774A1 PCT/CN2018/076156 CN2018076156W WO2018201774A1 WO 2018201774 A1 WO2018201774 A1 WO 2018201774A1 CN 2018076156 W CN2018076156 W CN 2018076156W WO 2018201774 A1 WO2018201774 A1 WO 2018201774A1
Authority
WO
WIPO (PCT)
Prior art keywords
approval
data
rule
chain
approver
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2018/076156
Other languages
English (en)
French (fr)
Inventor
蒋增源
刘金萍
黄建虎
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2018201774A1 publication Critical patent/WO2018201774A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the present application relates to the field of data processing technologies, and in particular, to a data approval method, apparatus, device, and computer readable storage medium. .
  • the traditional approval chain rules are configured to be closely coupled with the workflow in the workflow.
  • the workflow reaches a certain node, the corresponding approval chain rules are obtained, and the obtained approval chain rules approve the data. Since the approval chain rules are closely coupled with the workflow, the acquisition of the approval chain rules needs to be obtained through the workflow, which leads to the cumbersome process of data approval.
  • the approval chain rules are to be changed, Rewriting the code to republish the workflow version and republishing the workflow version not only affects the stability of the system, but also adds a lot of work.
  • the main purpose of the present application is to provide a data approval method, apparatus, device and computer readable storage medium, aiming at solving the existing The method of data approval, the convenience and stability are poor, and it is also easy to cause technical problems with increased workload.
  • the present application provides a data approval method, and the data approval method includes:
  • the system interface of the approval chain is set in the background of the system, so that the URL is subsequently called in the system interface to obtain the approval chain rule for data approval.
  • the present application further provides a data approval device, the data approval device comprising:
  • the import module is configured to import the approval chain rule in the approval chain setting interface to store the approval chain rule to the system background;
  • a generating module configured to generate a uniform resource locator URL corresponding to the approval chain rule according to the stored approval chain rule in the system background;
  • the setting module is configured to set a system interface of the approval chain in the system background, so as to subsequently invoke the URL in the system interface to obtain an approval chain rule for data approval.
  • the present application further provides a data approval device, where the data approval device includes a memory, a processor, and a data approval program stored on the memory and operable on the processor, the data approval program being executed by the processor to implement the steps of the data approval method as described above .
  • the present application further provides a computer readable storage medium having data approval stored thereon.
  • a program that, when executed by the processor, implements the steps of the data approval method as described above.
  • This application first imports the approval chain rule in the approval chain setting interface to store the approval chain rule to the system background, and then generates a uniform resource locator URL corresponding to the approval chain rule according to the stored approval chain rule in the system background. Finally, the system interface of the approval chain is set in the background of the system, so that the URL is subsequently called in the system interface to obtain the approval chain rule for data approval.
  • the application is configured with the approval chain at the beginning, the approval chain and the workflow are separated, and the approval chain can be run through the system background. Since the approval chain rules are no longer coupled with the workflow, the approval chain rules need not be obtained through the workflow. The operation process of data approval is more convenient.
  • FIG. 1 is a schematic structural diagram of a device in a hardware operating environment involved in an embodiment of the present application
  • FIG. 2 is a schematic flow chart of the first embodiment of the data approval method of the present application.
  • FIG. 3 is a schematic flow chart of the second embodiment of the data approval method of the present application.
  • step S50 in FIG. 3 is a schematic diagram of the refinement process of step S50 in FIG. 3;
  • FIG. 5 is a schematic diagram of the refinement process of step S60 in FIG. 3;
  • FIG. 6 is a schematic flow chart of the fourth embodiment of the data approval method of the present application.
  • FIG. 7 is a schematic flow chart of the sixth embodiment of the data approval method of the present application.
  • the solution of the embodiment of the present application is mainly : Import the approval chain rule in the approval chain setting interface to store the approval chain rule to the system background, and then generate the uniform resource locator URL corresponding to the approval chain rule according to the stored approval chain rule in the system background, and finally in the system.
  • the system interface of the approval chain is set in the background, so that the URL is subsequently called in the system interface to obtain the approval chain rule for data approval.
  • stability and convenience are poor, and it is easy to increase the workload.
  • FIG. 1 is a schematic structural diagram of a data approval device of a hardware operating environment involved in an embodiment of the present application.
  • the device in the embodiment of the present application may be a PC, or may be a mobile terminal device having a display function, such as a smart phone, a tablet computer, an e-book reader, and a portable computer.
  • the device may include: A processor 1001, such as a CPU, a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005.
  • the communication bus 1002 is used to implement connection communication between these components.
  • User interface 1003 can include a display screen ( Display The input unit such as a keyboard, the optional user interface 1003 may also include a standard wired interface (for example, for connecting a wired keyboard, a wired mouse, etc.), a wireless interface (for example, for connecting a wireless keyboard, a wireless mouse).
  • the network interface 1004 can optionally include a standard wired interface (for connecting to a wired network), a wireless interface (such as a WI-FI interface, a Bluetooth interface, an infrared interface, a probe interface, a 3G/4G/5G network communication interface, etc.) Connect to a wireless network).
  • the memory 1005 may be a high speed RAM memory or a stable memory (non-volatile) Memory), such as disk storage.
  • the memory 1005 can also optionally be a storage device independent of the aforementioned processor 1001.
  • the device may further include a camera, an RF (Radio Frequency) circuit , sensors, audio circuits, WiFi modules, and more.
  • RF Radio Frequency
  • the device structure shown in FIG. 1 does not constitute a limitation on the device, and may include a ratio More or fewer parts, or some parts, or different parts.
  • an operating system As shown in FIG. 1, an operating system, a network communication module, a user interface module, and the like may be included in the memory 1005 as a computer readable storage medium.
  • Data approval process The operating system is a program for managing and controlling data approval devices and software resources, and supports network communication modules, user interface modules, and data approval procedures. And the operation of other programs or software; the network communication module is used to manage and control the network interface 1002; the user interface module is used to manage and control the user interface 1003.
  • the network interface 1004 is mainly used to connect the system background, and the system background Data communication is performed;
  • the user interface 1003 is mainly used for connecting a client (user end) to perform data communication with the client; and the data approval device calls the data stored in the memory 1005 through the processor 1001. Approve the procedures and perform the various steps of the data approval method.
  • FIG. 2 is a schematic flowchart of a first embodiment of a data approval method according to the present application.
  • the data approval method includes:
  • the data approval method is applied to a data approval device, and the data approval device is as shown in FIG.
  • Step S10 Import an approval chain rule in the approval chain setting interface to store the approval chain rule to the system background;
  • the approval chain setting interface is first opened in the data approval device.
  • the method of opening the approval chain setting interface is preferably opened in the approval chain setting application, and after the approval chain setting interface is opened, the approval chain rule is further imported in the approval chain setting interface.
  • an import button is displayed in the approval chain setting interface, and a pressing operation is received in the import button, and the data approval device pops up a selection window of the approval chain rule, so that the user selects the to be imported based on the selection window.
  • the approval chain rule, the selection window is preferably an Excel table, wherein the Excel table stores a large number of approval chain rules, and the approval chain rules are stored according to the organization or department. Therefore, when the approval chain rules are imported, according to the organization identification or department identification , select the appropriate approval chain rules to import.
  • the import approval chain rule may be a single import or a batch import.
  • the import lead chain rule is preferably imported in batches to improve the efficiency of the approval chain rule import.
  • the data approval device can store the approval chain rule to the system background. It can be understood that when the approval chain rule is selected from the above selection window, the approval chain rule corresponds to The organization ID or department ID. Therefore, when the approval chain rule is imported in the approval chain setting interface and stored in the background of the system, it can continue to be stored according to the organization ID or department ID of the approval chain rule.
  • Step S20 Generate a uniform resource locator URL corresponding to the approval chain rule according to the stored approval chain rule in the system background;
  • the uniform resource locator corresponding to the approval chain rule is generated according to the stored approval chain rule ( Uniform Resource Locator, URL), subsequently, through the URL, the approval chain rule corresponding to the organization identifier or the department identifier can be uniquely located.
  • URL Uniform Resource Locator
  • Step S30 setting a system interface of the approval chain in the background of the system, so as to subsequently invoke the URL in the system interface to obtain an approval chain rule for data approval.
  • the system interface of the approval chain is set in the system background, and subsequently, the data approval device can invoke the URL through the system interface to locate Approve the chain rules and approve the data according to the approved approval chain rules.
  • the approval chain rule can be imported from the Excel table, and no new workflow is needed, which reduces the workload and makes the configuration of the approval chain more convenient.
  • the data approval method there is no need to obtain approval chain rules through workflow, which makes the data approval method more convenient.
  • the approval chain rule is first introduced in the approval chain setting interface to store the approval chain rule to the system background, and then the unified resource positioning corresponding to the approval chain rule is generated according to the stored approval chain rule in the system background.
  • the URL is finally set in the system background to set the system interface of the approval chain, so that the URL is subsequently called in the system interface to obtain the approval chain rule for data approval.
  • the second embodiment of the data approval method is different from the first embodiment of the data approval method.
  • the data approval method further includes:
  • Step S40 when receiving the data approval instruction, calling the URL in the system interface of the approval chain to read the approval chain rule stored in the background of the system;
  • Step S50 starting a service in the background of the system, to load a rule factor corresponding to the approval chain rule by using the activated service;
  • step S60 the current approver is determined based on the loaded rule factor, and the approval process is transferred to the node where the determined approver is located for data approval.
  • the URL when receiving the data approval instruction, the URL is first invoked in the system interface of the approval chain to read the approval chain rule stored in the system background, since the URL can be uniquely mentioned in the first embodiment.
  • the approval chain rule is located, so the corresponding approval chain rule can be read by calling the URL.
  • the service is started in the system background, and the rule factor corresponding to the approval chain rule is loaded by the started service.
  • the step S50 includes:
  • step S51 when the service is started in the background of the system, the dimension information included in the data approval instruction is obtained, where the dimension information includes the insurance, the channel, and the organization;
  • step S52 the rule factor corresponding to the dimension information is loaded in the approval chain rule by the activated service.
  • the dimension information included in the data approval instruction is first acquired, and the dimension information includes, but is not limited to, insurance, channel, organization, product line, task type, etc., after determining the dimension information, by starting
  • the service loads the rule factor corresponding to the dimension information in the approval chain rule.
  • the service is used to load a rule factor.
  • the rule factors include: alarm, monitoring, financial materials, and the like. For example, if the dimension information included in the data approval instruction is 'institution', and the rule factor corresponding to the dimension information is 'alarm', then after obtaining the dimension information 'institution', the service can be launched through the approval chain. In the rule, the rule factor 'alarm' corresponding to the institution is loaded.
  • the current approver can be determined based on the obtained rule factor. If the approver corresponding to the rule factor of the alarm is A, the approval process can be transferred to the node where the approver A is located for data approval.
  • the step S60 includes:
  • Step S61 When the loaded rule factor includes multiple rule factors, obtain a rule factor with the highest matching rate with the dimension information.
  • step S62 the current approver is determined based on the rule factor with the highest matching rate, and the approval process is transferred to the node where the determined approver is located to perform data approval.
  • the rule factor with the highest matching rate with the dimension information is obtained first, and then the current approver is determined according to the rule factor with the highest matching rate.
  • the currently loaded rule factor includes Alarm and monitoring
  • the ruler corresponding to the rule factor of the alarm is A
  • the approver corresponding to the rule factor of the monitoring is B. If the rule factor with the highest matching rate of the dimension information in the current two rule factors is monitoring, then According to the rule factor 'Monitoring', it is determined that the approver is B, then the approval process can be transferred to the node where the approver B is located for data approval.
  • the URL when receiving the data approval instruction, the URL is invoked in the system interface of the approval chain to read the approval chain rule stored in the system background, and then the service is started in the system background to load and approve the service through the startup.
  • the rule factor corresponding to the chain rule and then determine the current approver based on the loaded rule factor, and transfer the approval process to the node where the determined approver is located for data approval, so that when the data is approved, the approval chain can be directly run in the system background.
  • the approver information is determined from the approver rules, and finally the approval process is transferred to the node where the approver is located for data approval, without the need for workflow, which improves the convenience of data approval.
  • the third embodiment of the data approval method is different from the second embodiment of the data approval method.
  • the data approval method further includes:
  • Step A determining whether the current flow continues according to the flow condition in the approval chain rule
  • step B if there is no need to perform the flow again, the approval process is ended.
  • the data approval device After the approval process is transferred to the node where the determined approver is located for data approval, according to the flow condition in the approval chain rule, it is determined whether the flow is still to be continued, if there is no next node in the flow condition If the data approval device ends the approval process, the data approval device directly ends the approval process. In this embodiment, the data approval device outputs a prompt when the data approval device ends the approval process. Information such as 'End of Approval Process' or 'Ended' prompts the user to get approval details of the approval chain process.
  • the data approval method further includes:
  • step C if the flow needs to be performed again, the message of continuing to flow is returned to the workflow, and the workflow is transferred from the workflow to the next node, and the service started in the next node is again in the approval chain rule. Load the rule factor to determine the new approver.
  • the flow needs to be performed again, the message of continuing to flow is returned to the workflow, and the approval process flows to the next node by the workflow, and then the approval is performed in the next node by the service.
  • the rule factor is loaded again in the chain rule to determine the new approver.
  • the rule factor is loaded again, and the processing mode of the new approver is determined to be consistent with the above, and will not be described here. It should be noted that the data approval device loads different rule factors in different nodes.
  • the approval chain rule is no longer obtained through the workflow, but the corresponding approval chain rule is obtained by calling the URL in the system interface, and the workflow is only the approval conclusion for receiving the approval chain, and When the approval conclusion is to continue the approval process, the approval process is transferred to the next node.
  • whether the process of continuing the approval process or the process of ending the approval process is determined by the flow condition in the approval chain, and when the approval process is continued, the message of continuing to flow is returned to the workflow, and the approval process is transferred to the next process by the workflow.
  • the node in the next node, loads the rule factor in the approval chain rule by the started service to determine the new approver, thereby ensuring the continued flow of the approval process.
  • the fourth embodiment of the data approval method is different from the second embodiment of the data approval method.
  • the data approval method further includes:
  • Step S70 when receiving the modification instruction of the rule factor, exporting the data table storing the rule factor in the database;
  • Step S80 modifying a rule factor based on a modification operation in the data table, where the modifying operation includes adding, deleting, updating, and replacing a rule factor;
  • step S90 the data table with the modified rule factor is updated into the database.
  • step S70 to step S90 may be performed before step S10.
  • the above operations may be performed after the step S60, and the operations may be performed in other steps according to actual needs, which are not limited.
  • the data table storing the rule factor is exported from the database, and then the exported data table is displayed in the interface, and if the modification operation is received in the data table, according to the The modification operation modifies the rule factor, and finally updates the original data table in the data table by using the data table with the rule factor modified.
  • the rule factor can be modified according to actual needs during the data approval process, thereby improving the flexibility of data approval.
  • the foregoing operations may be performed before the step S10, and the operations may be performed after the step S60, and the operations may be performed in other steps according to actual needs, which are not limited.
  • the modification may be performed in the account column where the approver account to be modified is located, specifically, the replacement account entered by the user in the account column is received, in order to ensure the account corresponding The approver exists, and after receiving the replacement account, the replacement account is verified.
  • the specific verification method is to compare the replacement account with each pre-stored account pre-stored in the system, and the replacement account and the system are detected. When any of the pre-stored accounts match, the replacement account exists. At this time, the replacement account that was to be replaced is replaced by the replacement account.
  • the approver can modify the data according to actual needs during the data approval process, thereby improving the flexibility of data approval.
  • the data approval method is different from the data approval method in the first to fifth embodiments. Referring to FIG. 7, the data approval method further includes:
  • Step S100 when receiving an export instruction of the approval chain, determining an approval chain to be exported
  • Step S110 Export an approval form corresponding to the approval chain in a database, so as to perform statistics, batch modification, and update of the approval chain rule based on the approval table.
  • the foregoing operations may be performed after the step S10, and the operations may be performed after the step S60, and the operations may be performed in other steps according to actual needs, which are not limited.
  • the approval chain to be exported is first determined, and if the approval chain of the 'security organization' is to be exported, at this time, the corresponding approval is derived according to the determined approval chain.
  • the table is used for subsequent statistics, batch modification and update of the approval chain rules based on the approval form, thereby improving the flexibility of data approval.
  • the present invention further provides a data approval device.
  • the first embodiment of the data approval apparatus of the present invention is proposed.
  • the embodiment provides a data approval device, and the data approval device includes:
  • the import module is configured to import the approval chain rule in the approval chain setting interface to store the approval chain rule to the system background;
  • a generating module configured to generate a uniform resource locator URL corresponding to the approval chain rule according to the stored approval chain rule in the system background;
  • the setting module is configured to set a system interface of the approval chain in the system background, so as to subsequently invoke the URL in the system interface to obtain an approval chain rule for data approval.
  • the data approval device is as shown in FIG.
  • the method includes an opening module, and the opening module is configured to open an approval chain setting interface in the data approval device.
  • the method of opening the approval chain setting interface is preferably opened in the approval chain setting application, and after the approval chain setting interface is opened, the approval chain rule is further imported in the approval chain setting interface.
  • an import button is displayed in the approval chain setting interface, and a pressing operation is received in the import button, and the data approval device pops up a selection window of the approval chain rule, so that the user selects the to be imported based on the selection window.
  • the approval chain rule, the selection window is preferably an Excel table, wherein the Excel table stores a large number of approval chain rules, and the approval chain rules are stored according to the organization or department. Therefore, when the approval chain rules are imported, according to the organization identification or department identification , select the appropriate approval chain rules to import.
  • the import approval chain rule may be a single import or a batch import.
  • the import lead chain rule is preferably imported in batches to improve the efficiency of the approval chain rule import.
  • the data approval device can store the approval chain rule to the system background. It can be understood that when the approval chain rule is selected from the above selection window, the approval chain rule corresponds to The organization ID or department ID. Therefore, when the approval chain rule is imported in the approval chain setting interface and stored in the background of the system, it can continue to be stored according to the organization ID or department ID of the approval chain rule.
  • the uniform resource locator corresponding to the approval chain rule is generated according to the stored approval chain rule ( Uniform Resource Locator, URL), subsequently, through the URL, uniquely locates the approval chain rule corresponding to the organization identifier or department identifier.
  • the system interface of the approval chain is set in the system background, and subsequently, the data approval device can invoke the URL through the system interface to locate Approve the chain rules and approve the data according to the approved approval chain rules.
  • the approval chain rule can be imported from the Excel table, and no new workflow is needed, which reduces the workload and makes the configuration of the approval chain more convenient.
  • the data approval method there is no need to obtain approval chain rules through workflow, which makes the data approval method more convenient.
  • the approval chain rule is first introduced in the approval chain setting interface to store the approval chain rule to the system background, and then the unified resource positioning corresponding to the approval chain rule is generated according to the stored approval chain rule in the system background.
  • the URL is finally set in the system background to set the system interface of the approval chain, so that the URL is subsequently called in the system interface to obtain the approval chain rule for data approval.
  • a loading module configured to start a service in the background of the system, to load a rule factor corresponding to the approval chain rule by using the started service;
  • the transfer module is configured to determine the current approver based on the loaded rule factor, and transfer the approval process to the node where the determined approver is located for data approval.
  • the URL when receiving the data approval instruction, the URL is first invoked in the system interface of the approval chain to read the approval chain rule stored in the system background, since the URL can be uniquely mentioned in the first embodiment.
  • the approval chain rule is located, so the corresponding approval chain rule can be read by calling the URL.
  • the service is started in the system background, and the rule factor corresponding to the approval chain rule is loaded by the started service.
  • the loading module includes:
  • a first obtaining unit configured to acquire dimension information included in a data approval instruction when the service is started in the system background, where the dimension information includes a insurance, a channel, and an organization;
  • a loading unit configured to load, by the activated service, a rule factor corresponding to the dimension information in an approval chain rule.
  • the dimension information included in the data approval instruction is first acquired, and the dimension information includes, but is not limited to, insurance, channel, organization, product line, task type, etc., after determining the dimension information, by starting
  • the service loads the rule factor corresponding to the dimension information in the approval chain rule.
  • the service is used to load a rule factor.
  • the rule factors include: alarm, monitoring, financial materials, and the like. For example, if the dimension information included in the data approval instruction is 'institution', and the rule factor corresponding to the dimension information is 'alarm', then after obtaining the dimension information 'institution', the service can be launched through the approval chain. In the rule, the rule factor 'alarm' corresponding to the institution is loaded.
  • the current approver can be determined based on the obtained rule factor. If the approver corresponding to the rule factor of the alarm is A, the approval process can be transferred to the node where the approver A is located for data approval.
  • the switching module includes:
  • a second acquiring unit configured to acquire a rule factor with the highest matching rate of the dimension information when the loaded rule factor includes multiple rule factors
  • the transfer unit is configured to determine the current approver based on the rule factor with the highest matching rate, and transfer the approval process to the node where the determined approver is located for data approval.
  • the rule factor with the highest matching rate with the dimension information is obtained first, and then the current approver is determined according to the rule factor with the highest matching rate.
  • the currently loaded rule factor includes Alarm and monitoring
  • the ruler corresponding to the rule factor of the alarm is A
  • the approver corresponding to the rule factor of the monitoring is B. If the rule factor with the highest matching rate of the dimension information in the current two rule factors is monitoring, then According to the rule factor 'Monitoring', it is determined that the approver is B, then the approval process can be transferred to the node where the approver B is located for data approval.
  • the URL when receiving the data approval instruction, the URL is invoked in the system interface of the approval chain to read the approval chain rule stored in the system background, and then the service is started in the system background to load and approve the service through the startup.
  • the rule factor corresponding to the chain rule and then determine the current approver based on the loaded rule factor, and transfer the approval process to the node where the determined approver is located for data approval, so that when the data is approved, the approval chain can be directly run in the system background.
  • the approver information is determined from the approver rules, and finally the approval process is transferred to the node where the approver is located for data approval, without the need for workflow, which improves the convenience of data approval.
  • a determining module configured to determine whether to continue to flow according to a flow condition in the approval chain rule
  • the end module is used to end the approval process if there is no need to flow again at present.
  • the data approval device After the approval process is transferred to the node where the determined approver is located for data approval, according to the flow condition in the approval chain rule, it is determined whether the flow is still to be continued, if there is no next node in the flow condition If the data approval device ends the approval process, the data approval device directly ends the approval process. In this embodiment, the data approval device outputs a prompt when the data approval device ends the approval process. Information such as 'End of Approval Process' or 'Ended' prompts the user to get approval details of the approval chain process.
  • the data approval device further includes:
  • a processing module configured to return a message of continuing to flow to the workflow if the flow needs to be performed again, the flow of the approval process is transferred to the next node by the workflow, and the approval chain is passed in the next node by the service in the approval chain rule Load the rule factor again to determine the new approver.
  • the flow needs to be performed again, the message of continuing to flow is returned to the workflow, and the approval process flows to the next node by the workflow, and then the approval is performed in the next node by the service.
  • the rule factor is loaded again in the chain rule to determine the new approver.
  • the rule factor is loaded again, and the processing mode of the new approver is determined to be consistent with the above, and will not be described here. It should be noted that the data approval device loads different rule factors in different nodes.
  • the approval chain rule is no longer obtained through the workflow, but the corresponding approval chain rule is obtained by calling the URL in the system interface, and the workflow is only the approval conclusion for receiving the approval chain, and When the approval conclusion is to continue the approval process, the approval process is transferred to the next node.
  • whether the process of continuing the approval process or the process of ending the approval process is determined by the flow condition in the approval chain, and when the approval process is continued, the message of continuing to flow is returned to the workflow, and the approval process is transferred to the next process by the workflow.
  • the node in the next node, loads the rule factor in the approval chain rule by the started service to determine the new approver, thereby ensuring the continued flow of the approval process.
  • the exporting module is configured to: when receiving the modification instruction of the rule factor, export the data table storing the rule factor in the database;
  • a modifying module configured to modify a rule factor based on a modification operation in the data table, where the modifying operation includes adding, deleting, updating, and replacing a rule factor;
  • An update module for updating a data table with a modified rule factor to the database.
  • the data table storing the rule factor is exported from the database, and then the exported data table is displayed in the interface, and if the modification operation is received in the data table, according to the The modification operation modifies the rule factor, and finally updates the original data table in the data table by using the data table with the rule factor modified.
  • the rule factor can be modified according to actual needs during the data approval process, thereby improving the flexibility of data approval.
  • the fifth embodiment of the data approval device is different from the second embodiment of the data approval device in that the determining module is further configured to determine an approver account to be modified when receiving the modification instruction of the approver account;
  • the data approval device further includes:
  • a verification module configured to perform verification on the replacement account when receiving the replacement account in the account column where the approver account to be modified is located;
  • the execution module is configured to perform an replacement operation of the approver account after the verification is successful.
  • the modification may be performed in the account column where the approver account to be modified is located, specifically, the replacement account entered by the user in the account column is received, in order to ensure the account corresponding The approver exists, and after receiving the replacement account, the replacement account is verified.
  • the specific verification method is to compare the replacement account with each pre-stored account pre-stored in the system, and the replacement account and the system are detected. When any of the pre-stored accounts match, the replacement account exists. At this time, the replacement account that was to be replaced is replaced by the replacement account.
  • the approver can modify the data according to actual needs during the data approval process, thereby improving the flexibility of data approval.
  • the difference between the sixth embodiment of the data approval device and the first to fifth embodiments of the data approval device is that the determination module is further configured to determine an approval chain to be exported when receiving the export instruction of the approval chain;
  • the exporting module is further configured to export an approval form corresponding to the approval chain in a database, so as to perform statistics, batch modification, and update of the approval chain rule based on the approval table.
  • the approval chain to be exported is first determined, and if the approval chain of the 'security organization' is to be exported, at this time, the corresponding approval is derived according to the determined approval chain.
  • the table is used for subsequent statistics, batch modification and update of the approval chain rules based on the approval form, thereby improving the flexibility of data approval.
  • the embodiment of the present application further provides a computer readable storage medium, where the computer readable storage medium stores a data approval program,
  • the data approval process is implemented by the processor to implement the steps of the data approval method as described above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • General Physics & Mathematics (AREA)
  • Operations Research (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种数据审批方法、装置、设备和计算机可读存储介质，所述方法包括：在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台(S10)；在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL (S20)；在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批(S30)。该方案提高了数据审批的便捷性和稳定性，还降低了数据审批的工作量。

Description

数据 审批方法、装置、设备和计算机可读存储介质
本申请要求于2017年05月05日提交中国专利局、申请号为201710315384.X、发明名称为' 数据 审批方法、设备 和计算机可读存储介质 '的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及 数据处理技术 领域，尤其涉及 一种 数据 审批方法、装置、设备 和计算机可读存储介质 。
背景技术
传统的审批链规则，是配置在工作流中与工作流紧密耦合，当工作流到达某一个节点时，才获取对应的审批链规则，由获取的审批链规则对数据进行审批处理。由于审批链规则与工作流紧密耦合，因此审批链规则的获取，需要通过工作流进行获取，导致数据审批的过程较为繁琐，并且在后续的数据审批过程中，若是要变更审批链规则，也需要重新编写代码以重新发布工作流版本，而重新发布工作流版本，不仅影响了系统的稳定性，还增加了许多工作量。
发明内容
本申请的 主要 目的在于 提供一种 数据 审批方法、装置、设备 和计算机可读存储介质 ，旨在解决现有的 数据 审批方式，便捷性和稳定性都较差，并且还容易导致工作量增多的技术问题。
为实现上述目的，本申请提供一种 数据 审批方法，所述 数据 审批方法 包括：
在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台；
在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL；
在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。
此外，为实现上述目的，本申请还提供一种 数据 审批装置，所述 数据 审批装置包括：
导入模块，用于在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台；
生成模块，用于在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL；
设置模块，用于在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。
此外，为实现上述目的，本申请还提供一种数据审批设备，所述数据审批设备包括 存储器、处理器及存储在所述存储器上并可在所述处理器上运行的 数据审批 程序，所述 数据审批 程序被所述处理器执行时实现如 上文 所述的 数据审批方法 的步骤 。
此外，为实现上述目的，本申请还提供一种 计算机可读存储介质，所述计算机可读存储介质上存储有 数据审批 程序，所述 数据审批 程序被处理器执行时实现如 上文 所述的 数据审批 方法的步骤。
本申请 提出的技术方案，先在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台，然后在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL，最终在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。本申请在一开始配置审批链时，就将审批链和工作流分开来，后续通过系统后台跑审批链即可，由于审批链规则不再与工作流耦合，审批链规则无须通过工作流获取，对数据审批的操作过程较为便捷，后续即使要更改审批链中的规则，直接更改后在设置界面中导入即可，对工作流也没有影响，无须编写代码，无须重新发布工作流版本，保证了系统的稳定性，也降低了工作量。
附图说明
图1 是本申请实施例方案涉及的硬件运行环境的 设备 结构示意图 ；
图 2 为 本申请 数据 审批方法 第一 实施例 的 流程示意图 ；
图 3 为 本申请 数据 审批方法 第二 实施例 的 流程示意图 ；
图 4 为 图3中步骤S50的细化 流程示意图 ；
图 5 为 图3中步骤S60的细化 流程示意图 ；
图 6 为 本申请 数据 审批方法 第四 实施例 的 流程示意图 ；
图 7 为 本申请 数据 审批方法 第六 实施例 的 流程示意图 。
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
本申请实施例 的 解决方案主要是 ：先在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台，然后在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL，最终在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。以解决现有的数据审批方式，稳定性和便捷性较差，并且还容易增多工作量的问题。
如图1所示，图1是本申请实施例方案涉及的硬件运行环境的 数据 审批设备的结构示意图。
本申请实施例设备可以是PC，也可以是智能手机、平板电脑、电子书阅读器、便携计算机等具有显示功能的可移动式终端设备。
如图1所示，该设备可以包括： 处理器1001，例如CPU，通信总线1002、用户接口1003，网络接口1004，存储器1005。其中，通信总线1002用于实现这些组件之间的连接通信。用户接口1003可以包括显示屏（ Display ）、输入单元比如键盘（Keyboard），可选用户接口1003还可以包括标准的有线接口（例如用于连接有线键盘、有线鼠标等）、无线接口（例如用于连接无线键盘、无线鼠标）。网络接口1004可选的可以包括标准的有线接口（用于连接有线网络）、无线接口（如WI-FI接口、蓝牙接口、红外线接口、探针接口、3G/4G/5G联网通信接口等，用于连接无线网络）。存储器1005可以是高速RAM存储器，也可以是稳定的存储器（non-volatile memory），例如磁盘存储器。存储器1005可选的还可以是独立于前述处理器1001的存储装置。
可选地， 设备 还可以包括摄像头、 RF（Radio Frequency，射频）电路 ，传感器、音频电路、 WiFi模块 等等。
本领域技术人员可以理解，图 1 中示出的 设备 结构并不构成对 设备 的限定，可以包括比图示 更多或更少的部件，或者组合某些部件，或者不同的部件布置。
如图1所示，作为一种计算机可读存储介质的存储器1005中可以包括操作系统、网络通信模块、用户接口模块以及 数据 审批 程序。其中，操作系统是管理和控制 数据 审批设备 与 软件 资源的程序，支持网络通信模块、 用户接口模块 、 数据 审批 程序 以及其他程序或软件的运行；网络通信模块用于管理和控制网络接口 1002 ； 用户接口模块 用于管理和控制 用户接口1003 。
在图1所示的 设备中 ，网络接口1004主要用于连接 系统后台 ，与 系统后台 进行数据通信；用户接口1003主要用于连接客户端（用户端），与客户端进行数据通信；所述 数据 审批设备 通过处理器1001调用存储器1005中存储的 数据 审批 程序，并执行 数据 审批方法的各个步骤 。
基于上述设备硬件结构，提出本申请 数据 审批方法的各个 实施例。
参照图2， 图 2 为本申请 数据 审批方法 第一 实施例 的 流程示意图 。
在本实施例中，所述 数据 审批方法包括：
在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台；在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL；在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。
本实施例中，所述数据审批方法应用于数据审批设备中，所述数据审批设备如图1所述的设备。
以下是本实施例中实现 数据 审批的具体步骤：
步骤S10，在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台；
在本实施例中，在所述步骤S10之前，先在数据审批设备中开启审批链设置界面。开启审批链设置界面的方式，优选是在审批链设置应用中开启，在开启审批链设置界面之后，进一步在审批链设置界面中导入审批链规则。
本实施例中，所述审批链设置界面中显示有导入按钮，在该导入按钮中接收到按压操作，数据审批设备弹出审批链规则的选择窗口，以供用户基于所述选择窗口选择待导入的审批链规则，所述选择窗口优选是Excel表格，该Excel表格中存储有大量的审批链规则，审批链规则是按照机构或部门存储的，因此，导入审批链规则时，按照机构标识或部门标识，选择相应的审批链规则导入即可。本实施例中，导入审批链规则可以是单个导入，也可以是批量导入，本实施例中优选导入审批链规则采用批量导入的方式，以提高审批链规则导入的效率。
在审批链设置界面中导入审批链规则之后，数据审批设备即可将审批链规则存储至系统后台，可以理解的是，从上述的选择窗口中选择审批链规则导入时，审批链规则都对应有机构标识或部门标识，因此，在审批链设置界面中导入审批链规则，并在系统后台进行存储时，可继续按照审批链规则的机构标识或部门标识进行存储。
步骤S20，在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL；
在本实施例中，在系统后台中存储审批链规则时，根据存储的审批链规生成该审批链规则对应的统一资源定位符（ Uniform Resource Locator，URL ），后续，通过所述URL可唯一定位到该机构标识或部门标识对应的审批链规则。
步骤S30，在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。
在本实施例中，在系统后台中根据存储的审批链规则生成URL之后，在系统后台中设置审批链的系统接口，后续，该数据审批设备可通过该系统接口调用所述URL，以定位到审批链规则，并根据定位到的审批链规则进行数据的审批。
需要说明的是，现有的审批链配置方式，不仅在审批链规则变更时，要经常更新工作流导致稳定性和便捷性较差，而且在有新增审批链规则时，由于要开发新的工作流，导致开发工作量也增多。
而本实施例中，即使要新增审批链规则，也只要从Excel表格中导入审批链规则即可，无须开发新的工作流，降低了许多工作量，使得审批链的配置也较为便捷，后续进行数据审批时，也无须通过工作流获取审批链规则，使得数据审批的方式也较为便捷。
本 实施例提出的技术方案，先在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台，然后在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL，最终在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。本申请在一开始配置审批链时，就将审批链和工作流分开来，后续通过系统后台跑审批链即可，由于审批链规则不再与工作流耦合，审批链规则无须通过工作流获取，对数据审批的操作过程较为便捷，后续即使要更改审批链中的规则，直接更改后在设置界面中导入即可，对工作流也没有影响，无须编写代码，无须重新发布工作流版本，保证了系统的稳定性，也降低了工作量。
进一步地，基于第一实施例提出本申请 数据 审批方法的第二实施例。
数据审批方法第二实施例与数据审批方法第一实施例的区别在于，参照图3，所述步骤S30之后，所述数据审批方法还包括：
步骤S40，在接收到数据审批指令时，在审批链的系统接口调用所述URL，以读取系统后台存储的审批链规则；
步骤S50，在系统后台启动服务，以通过启动的服务加载审批链规则对应的规则因子；
步骤S60，基于加载的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批。
在本实施例中，在接收到数据审批指令时，先在审批链的系统接口调用所述URL，以读取系统后台中存储的审批链规则，由于第一实施例中已经提到URL能唯一定位到审批链规则，因此调用所述URL即可读取到对应的审批链规则。在读取到审批链规则之后，在系统后台中启动服务，通过启动的服务加载审批链规则对应的规则因子。其中，参照图4，所述步骤S50包括：
步骤S51，在系统后台启动服务时，获取数据审批指令中包含的维度信息，其中，所述维度信息包括险种、通道、机构；
步骤S52，通过启动的服务在审批链规则中加载所述维度信息对应的规则因子。
即，在系统后台启动服务时，先获取数据审批指令中包含的维度信息，所述维度信息包括但不限于险种、通道、机构、产品线、任务类型等等，在确定维度信息之后，通过启动的服务在审批链规则中加载所述维度信息对应的规则因子。其中，所述服务用于加载规则因子。本实施例中，所述规则因子包括：报警、监控、财务材料等等。例如，所述数据审批指令中包含的维度信息为'机构'、该维度信息对应的规则因子为'报警'，那么，在获取到维度信息'机构'之后，即可通过启动的服务在审批链规则中，加载所述机构对应的规则因子'报警'。
在获取到规则因子之后，即可基于获取的规则因子确定当前的审批人，如报警的规则因子对应的审批人是A、那么即可将审批流程转到审批人A所在节点进行数据的审批。
进一步地，参照图5，所述步骤S60包括：
步骤S61，在加载的规则因子包括多个规则因子时，获取与所述维度信息匹配率最高的规则因子；
步骤S62，基于匹配率最高的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批。
即，在加载的规则因子包括多个规则因子时，先获取与该维度信息的匹配率最高的规则因子，然后根据匹配率最高的规则因子确定当前的审批人，例如，当前加载的规则因子包括报警和监控，报警的规则因子对应的审批人是A，监控的规则因子对应的审批人是B，若当前两个规则因子中，与维度信息的匹配率最高的规则因子是监控，那么，即可根据规则因子'监控'确定审批人是B，那么即可将审批流程转至审批人B所在节点中进行数据的审批。
在本实施例中，在接收到数据审批指令时，在审批链的系统接口调用所述URL，以读取系统后台存储的审批链规则，然后在系统后台启动服务，以通过启动的服务加载审批链规则对应的规则因子，再基于加载的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批，使得数据审批时，可直接在系统后台中跑审批链即可，以从审批人规则中确定审批人信息，最终将审批流程流转至该审批人所在节点进行数据的审批，无须经过工作流，提高了数据审批的便捷性。
进一步地，基于第二实施例提出本申请 数据 审批方法的第三实施例。
数据审批方法第三实施例与数据审批方法第二实施例的区别在于，所述步骤S60之后，所述数据审批方法还包括：
步骤A，根据审批链规则中的流转条件确定当前是否继续流转；
步骤B，若当前无须再次进行流转，则结束审批流程。
在本实施例中，在将审批流程转到确定的审批人所在节点进行数据的审批之后，根据审批链规则中的流转条件，确定当前是否还要继续进行流转，若流转条件中没有下一个节点，说明该审批链流程到当前节点就可以结束了，无须再次进行流转，此时，数据审批设备直接结束审批流程即可，本实施例中，优选在数据审批设备在结束审批流程时，输出提示信息如'审批流程结束'或者'已结束'等提示信息，以便于用户得到审批链流程的审批详情。
此外，所述步骤A之后，所述数据审批方法还包括：
步骤C，若当前需要再次进行流转，则返回继续流转的消息至工作流中，由工作流将审批流程流转至下一个节点，并在下一个节点中通过启动的服务在所述审批链规则中再次加载规则因子，以确定新的审批人。
在本实施例中，若当前需要再次进行流转，则返回继续流转的消息至工作流中，由工作流将审批流程流转至下一个节点，然后，在下一个节点中通过启动的服务在所述审批链规则中再次加载规则因子，以确定新的审批人。后续再次加载规则因子，并确定新的审批人的处理方式与上述一致，此处不再赘述。需要说明的是，在不同的节点中，数据审批设备加载的规则因子不同。
也就是说，在本实施例中，审批链规则不再通过工作流获取，而是在系统接口中通过调用URL获取相应的审批链规则，工作流仅仅是用于接收审批链的审批结论，并在该审批结论为继续进行审批流程时，将审批流程流转至下一个节点中。
在本实施例中，通过审批链中的流转条件决定是否继续审批流程还是结束审批流程，并在继续审批流程时，返回继续流转的消息至工作流中，由工作流将审批流程转至下一个节点，在下一个节点中通过启动的服务在所述审批链规则中再次加载规则因子，以确定新的审批人，从而保证了审批流程的继续流转。
进一步地，基于第二实施例提出本申请 数据 审批方法的第四实施例。
数据审批方法第四实施例与数据审批方法第二实施例的区别在于，参照图6，所述数据审批方法还包括：
步骤S70，在接收到规则因子的修改指令时，在数据库导出存储有规则因子的数据表；
步骤S80，在所述数据表中基于修改操作修改规则因子，其中，所述修改操作包括增加、删除、更新和替换规则因子；
步骤S90，将修改了规则因子的数据表更新到数据库中。
在本实施例中，可以是在步骤S10之前，执行步骤S70至步骤S90。也可以是步骤S60之后执行上述操作，还可以根据实际需要在其它步骤执行上述操作，具体不做限定。
在本实施例中，在接收到规则因子的修改指令时，从数据库中导出存储有规则因子的数据表，然后在界面中显示导出的数据表，若在数据表中接收到修改操作，根据该修改操作修改规则因子，最终采用修改了规则因子的数据表更新数据表中原本的数据表。
本实施例中，通过对规则因子的修改，实现了数据审批过程中，规则因子可根据实际需要进行修改，从而提高了数据审批的灵活性。
进一步地，基于第二实施例提出本申请 数据 审批方法的第五实施例。
数据审批方法第五实施例与数据审批方法第二实施例的区别在于，所述数据审批方法还包括：
在接收到审批人账号的修改指令时，确定待修改的审批人账号；
在待修改的审批人账号所在的账户栏中接收到替换账号时，对所述替换账号进行校验；
在校验成功后，执行审批人账号的替换操作。
在本实施例中，可以是在步骤S10之前执行上述操作，也可以是步骤S60之后执行上述操作，还可以根据实际需要在其它步骤执行上述操作，具体不做限定。
即，在接收到审批人账号的修改指令时，可在待修改的审批人账号所在的账户栏中进行修改，具体地，接收用户在所述账户栏中输入的替换账号，为了保证账号对应的审批人存在，在接到到替换账号之后，对替换账号进行校验，具体的校验方式是将该替换账号与系统中预存的各个预存账号进行比对，在检测到该替换账号与系统中的任一个预存账号匹配时，说明该替换账号存在，此时，采用该替换账号替换掉原来待替换的审批人账号。
本实施例中，通过对审批人账号的修改，实现了数据审批过程中，审批人可根据实际需要进行修改，从而提高了数据审批的灵活性。
进一步地，基于第一至第五实施例提出本申请 数据 审批方法的第六实施例。
数据审批方法第六实施例与数据审批方法第一至第五实施例的区别在于，参照图7，所述数据审批方法还包括：
步骤S100，在接收到审批链的导出指令时，确定待导出的审批链；
步骤S110，在数据库中导出所述审批链对应的审批表，以便后续基于所述审批表进行审批链规则的统计、批量修改和更新。
在本实施例中，可以是在步骤S10之后执行上述操作，也可以是步骤S60之后执行上述操作，还可以根据实际需要在其它步骤执行上述操作，具体不做限定。
在本实施例中，若接收到审批链的导出指令，先确定待导出的审批链，如待导出的是'平安机构'的审批链，此时，根据该确定的审批链，导出相应的审批表，以便后续基于所述审批表进行审批链规则的统计、批量修改和更新，从而提高数据审批的灵活性。
本发明进一步提供一种 数据审批 装置。
提出 本发明 数据审批 装置 第一实施例。
本实施例提出一种 数据审批 装置 ，所 述 数据审批 装置包括：
导入模块，用于在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台；
生成模块，用于在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL；
设置模块，用于在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。
本实施例中，所述数据审批装置如图1所述的设备。
在本实施例中，包括开启模块，开启模块用于在数据审批设备中开启审批链设置界面。开启审批链设置界面的方式，优选是在审批链设置应用中开启，在开启审批链设置界面后，进一步在审批链设置界面中导入审批链规则。
本实施例中，所述审批链设置界面中显示有导入按钮，在该导入按钮中接收到按压操作，数据审批设备弹出审批链规则的选择窗口，以供用户基于所述选择窗口选择待导入的审批链规则，所述选择窗口优选是Excel表格，该Excel表格中存储有大量的审批链规则，审批链规则是按照机构或部门存储的，因此，导入审批链规则时，按照机构标识或部门标识，选择相应的审批链规则导入即可。本实施例中，导入审批链规则可以是单个导入，也可以是批量导入，本实施例中优选导入审批链规则采用批量导入的方式，以提高审批链规则导入的效率。
在审批链设置界面中导入审批链规则之后，数据审批设备即可将审批链规则存储至系统后台，可以理解的是，从上述的选择窗口中选择审批链规则导入时，审批链规则都对应有机构标识或部门标识，因此，在审批链设置界面中导入审批链规则，并在系统后台进行存储时，可继续按照审批链规则的机构标识或部门标识进行存储。
在本实施例中，在系统后台中存储审批链规则时，根据存储的审批链规生成该审批链规则对应的统一资源定位符（ Uniform Resource Locator，URL ），后续，通过所述URL唯一定位到该机构标识或部门标识对应的审批链规则。
在本实施例中，在系统后台中根据存储的审批链规则生成URL之后，在系统后台中设置审批链的系统接口，后续，该数据审批设备可通过该系统接口调用所述URL，以定位到审批链规则，并根据定位到的审批链规则进行数据的审批。
需要说明的是，现有的审批链配置方式，不仅在审批链规则变更时，要经常更新工作流导致稳定性和便捷性较差，而且在有新增审批链规则时，由于要开发新的工作流，导致开发工作量也增多。
而本实施例中，即使要新增审批链规则，也只要从Excel表格中导入审批链规则即可，无须开发新的工作流，降低了许多工作量，使得审批链的配置也较为便捷，后续进行数据审批时，也无须通过工作流获取审批链规则，使得数据审批的方式也较为便捷。
本 实施例提出的技术方案，先在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台，然后在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL，最终在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。本申请在一开始配置审批链时，就将审批链和工作流分开来，后续通过系统后台跑审批链即可，由于审批链规则不再与工作流耦合，审批链规则无须通过工作流获取，对数据审批的操作过程较为便捷，后续即使要更改审批链中的规则，直接更改后在设置界面中导入即可，对工作流也没有影响，无须编写代码，无须重新发布工作流版本，保证了系统的稳定性，也降低了工作量。
进一步地，基于第一实施例提出本申请 数据 审批装置的第二实施例。
数据审批装置第二实施例与数据审批装置第一实施例的区别在于，所述数据审批装置还包括：
调用模块，用于在接收到数据审批指令时，在审批链的系统接口调用所述URL，以读取系统后台存储的审批链规则；
加载模块，用于在系统后台启动服务，以通过启动的服务加载审批链规则对应的规则因子；
转接模块，用于基于加载的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批。
在本实施例中，在接收到数据审批指令时，先在审批链的系统接口调用所述URL，以读取系统后台中存储的审批链规则，由于第一实施例中已经提到URL能唯一定位到审批链规则，因此调用所述URL即可读取到对应的审批链规则。在读取到审批链规则之后，在系统后台中启动服务，通过启动的服务加载审批链规则对应的规则因子。其中，所述加载模块包括：
第一获取单元，用于在系统后台启动服务时，获取数据审批指令中包含的维度信息，其中，所述维度信息包括险种、通道、机构；
加载单元，用于通过启动的服务在审批链规则中加载所述维度信息对应的规则因子。
即，在系统后台启动服务时，先获取数据审批指令中包含的维度信息，所述维度信息包括但不限于险种、通道、机构、产品线、任务类型等等，在确定维度信息之后，通过启动的服务在审批链规则中加载所述维度信息对应的规则因子。其中，所述服务用于加载规则因子。本实施例中，所述规则因子包括：报警、监控、财务材料等等。例如，所述数据审批指令中包含的维度信息为'机构'、该维度信息对应的规则因子为'报警'，那么，在获取到维度信息'机构'之后，即可通过启动的服务在审批链规则中，加载所述机构对应的规则因子'报警'。
在获取到规则因子之后，即可基于获取的规则因子确定当前的审批人，如报警的规则因子对应的审批人是A、那么即可将审批流程转到审批人A所在节点进行数据的审批。
进一步地，所述转接模块包括：
第二获取单元，用于在加载的规则因子包括多个规则因子时，获取与所述维度信息匹配率最高的规则因子；
转接单元，用于基于匹配率最高的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批。
即，在加载的规则因子包括多个规则因子时，先获取与该维度信息的匹配率最高的规则因子，然后根据匹配率最高的规则因子确定当前的审批人，例如，当前加载的规则因子包括报警和监控，报警的规则因子对应的审批人是A，监控的规则因子对应的审批人是B，若当前两个规则因子中，与维度信息的匹配率最高的规则因子是监控，那么，即可根据规则因子'监控'确定审批人是B，那么即可将审批流程转至审批人B所在节点中进行数据的审批。
在本实施例中，在接收到数据审批指令时，在审批链的系统接口调用所述URL，以读取系统后台存储的审批链规则，然后在系统后台启动服务，以通过启动的服务加载审批链规则对应的规则因子，再基于加载的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批，使得数据审批时，可直接在系统后台中跑审批链即可，以从审批人规则中确定审批人信息，最终将审批流程流转至该审批人所在节点进行数据的审批，无须经过工作流，提高了数据审批的便捷性。
进一步地，基于第二实施例提出本申请 数据 审批装置的第三实施例。
数据审批装置第三实施例与数据审批装置第二实施例的区别在于，所述数据审批装置还包括：
确定模块，用于根据审批链规则中的流转条件确定当前是否继续流转；
结束模块，用于若当前无须再次进行流转，则结束审批流程。
在本实施例中，在将审批流程转到确定的审批人所在节点进行数据的审批之后，根据审批链规则中的流转条件，确定当前是否还要继续进行流转，若流转条件中没有下一个节点，说明该审批链流程到当前节点就可以结束了，无须再次进行流转，此时，数据审批设备直接结束审批流程即可，本实施例中，优选在数据审批设备在结束审批流程时，输出提示信息如'审批流程结束'或者'已结束'等提示信息，以便于用户得到审批链流程的审批详情。
此外，所述数据审批装置还包括：
处理模块，用于若当前需要再次进行流转，则返回继续流转的消息至工作流中，由工作流将审批流程流转至下一个节点，并在下一个节点中通过启动的服务在所述审批链规则中再次加载规则因子，以确定新的审批人。
在本实施例中，若当前需要再次进行流转，则返回继续流转的消息至工作流中，由工作流将审批流程流转至下一个节点，然后，在下一个节点中通过启动的服务在所述审批链规则中再次加载规则因子，以确定新的审批人。后续再次加载规则因子，并确定新的审批人的处理方式与上述一致，此处不再赘述。需要说明的是，在不同的节点中，数据审批设备加载的规则因子不同。
也就是说，在本实施例中，审批链规则不再通过工作流获取，而是在系统接口中通过调用URL获取相应的审批链规则，工作流仅仅是用于接收审批链的审批结论，并在该审批结论为继续进行审批流程时，将审批流程流转至下一个节点中。
在本实施例中，通过审批链中的流转条件决定是否继续审批流程还是结束审批流程，并在继续审批流程时，返回继续流转的消息至工作流中，由工作流将审批流程转至下一个节点，在下一个节点中通过启动的服务在所述审批链规则中再次加载规则因子，以确定新的审批人，从而保证了审批流程的继续流转。
进一步地，基于第二实施例提出本申请 数据 审批装置的第四实施例。
数据审批装置第四实施例与数据审批装置第二实施例的区别在于，所述数据审批装置还包括：
导出模块，用于在接收到规则因子的修改指令时，在数据库导出存储有规则因子的数据表；
修改模块，用于在所述数据表中基于修改操作修改规则因子，其中，所述修改操作包括增加、删除、更新和替换规则因子；
更新模块，用于将修改了规则因子的数据表更新到数据库中。
在本实施例中，在接收到规则因子的修改指令时，从数据库中导出存储有规则因子的数据表，然后在界面中显示导出的数据表，若在数据表中接收到修改操作，根据该修改操作修改规则因子，最终采用修改了规则因子的数据表更新数据表中原本的数据表。
本实施例中，通过对规则因子的修改，实现了数据审批过程中，规则因子可根据实际需要进行修改，从而提高了数据审批的灵活性。
进一步地，基于第二实施例提出本申请 数据 审批装置的第五实施例。
数据审批装置第五实施例与数据审批装置第二实施例的区别在于，所述确定模块，还用于在接收到审批人账号的修改指令时，确定待修改的审批人账号；
所述数据审批装置还包括：
校验模块，用于在待修改的审批人账号所在的账户栏中接收到替换账号时，对所述替换账号进行校验；
执行模块，用于在校验成功后，执行审批人账号的替换操作。
即，在接收到审批人账号的修改指令时，可在待修改的审批人账号所在的账户栏中进行修改，具体地，接收用户在所述账户栏中输入的替换账号，为了保证账号对应的审批人存在，在接到到替换账号之后，对替换账号进行校验，具体的校验方式是将该替换账号与系统中预存的各个预存账号进行比对，在检测到该替换账号与系统中的任一个预存账号匹配时，说明该替换账号存在，此时，采用该替换账号替换掉原来待替换的审批人账号。
本实施例中，通过对审批人账号的修改，实现了数据审批过程中，审批人可根据实际需要进行修改，从而提高了数据审批的灵活性。
进一步地，基于第一至第五实施例提出本申请 数据 审批装置第六实施例。
数据审批装置第六实施例与数据审批装置第一至第五实施例的区别在于，所述确定模块，还用于在接收到审批链的导出指令时，确定待导出的审批链；
所述导出模块，还用于在数据库中导出所述审批链对应的审批表，以便后续基于所述审批表进行审批链规则的统计、批量修改和更新。
在本实施例中，若接收到审批链的导出指令，先确定待导出的审批链，如待导出的是'平安机构'的审批链，此时，根据该确定的审批链，导出相应的审批表，以便后续基于所述审批表进行审批链规则的统计、批量修改和更新，从而提高数据审批的灵活性。
此外，本申请实施例还提出 一种计算机可读存储介质，所述计算机可读存储介质上存储有 数据审批 程序，所述 数据审批 程序被处理器执行时实现 如上文所述的数据审批方法的步骤。
需要说明的是，在本文中，术语'包括'、'包含'或者其任何其它变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其它要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句'包括一个……'限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在 其它 相关的技术领域，均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种数据 审批方法 ， 其特征在于，所述 数据 审批方法包括：
    在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台；
    在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL；
    在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。
  2. 如权利要求1所述的 数据 审批方法，其特征在于，所述在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批的步骤之后，所述 数据 审批方法还包括：
    在接收到数据审批指令时，在审批链的系统接口调用所述URL，以读取系统后台存储的审批链规则；
    在系统后台启动服务，以通过启动的服务加载审批链规则对应的规则因子；
    基于加载的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批。
  3. 如权利要求2所述的 数据 审批方法，其特征在于，所述在系统后台启动服务，以通过启动的服务加载审批链规则对应的规则因子的步骤包括：
    在系统后台启动服务时，获取数据审批指令中包含的维度信息，其中，所述维度信息包括险种、通道、机构；
    通过启动的服务在审批链规则中加载所述维度信息对应的规则因子。
  4. 如权利要求3所述的 数据 审批方法，其特征在于，所述基于加载的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批的步骤包括：
    在加载的规则因子包括多个规则因子时，获取与所述维度信息匹配率最高的规则因子；
    基于匹配率最高的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批。
  5. 如权利要求2所述的 数据 审批方法，其特征在于，所述基于加载的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批的步骤之后，所述 数据 审批方法还包括：
    根据审批链规则中的流转条件确定当前是否继续流转；
    若当前无须再次进行流转，则结束审批流程。
  6. 如权利要求5所述的 数据 审批方法，其特征在于，所述根据审批链规则中的流转条件确定当前是否继续流转的步骤之后，所述数据审批方法还包括：
    若当前需要再次进行流转，则返回继续流转的消息至工作流中，由工作流将审批流程流转至下一个节点，并在下一个节点中通过启动的服务在所述审批链规则中再次加载规则因子，以确定新的审批人。
  7. 如权利要求2所述的数据审批方法，其特征在于，所述数据审批方法还包括：
    在接收到规则因子的修改指令时，在数据库导出存储有规则因子的数据表；
    在所述数据表中基于修改操作修改规则因子，其中，所述修改操作包括增加、删除、更新和替换规则因子；
    将修改了规则因子的数据表更新到数据库中。
  8. 如权利要求1所述的数据审批方法，其特征在于，所述数据审批方法还包括：
    在接收到审批链的导出指令时，确定待导出的审批链；
    在数据库中导出所述审批链对应的审批表，以便后续基于所述审批表进行审批链规则的统计、批量修改和更新。
  9. 一种数据 审批装置 ， 其特征在于，所述 数据 审批装置包括：
    导入模块，用于在审批链设置界面中导入审批链规则，以将审批链规则存储至系统后台；
    生成模块，用于在系统后台中根据存储的审批链规则，生成审批链规则对应的统一资源定位符URL；
    设置模块，用于在系统后台中设置审批链的系统接口，以便后续在所述系统接口中调用所述URL以获取审批链规则进行数据的审批。
  10. 如权利要求9所述的 数据 审批装置，其特征在于，所述 数据 审批装置还包括：
    调用模块，用于在接收到数据审批指令时，在审批链的系统接口调用所述URL，以读取系统后台存储的审批链规则；
    加载模块，用于在系统后台启动服务，以通过启动的服务加载审批链规则对应的规则因子；
    转接模块，用于基于加载的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批。
  11. 如权利要求10所述的 数据 审批装置，其特征在于，所述加载模块包括：
    第一获取单元，用于在系统后台启动服务时，获取数据审批指令中包含的维度信息，其中，所述维度信息包括险种、通道、机构；
    加载单元，用于通过启动的服务在审批链规则中加载所述维度信息对应的规则因子。
  12. 如权利要求11所述的 数据 审批装置，其特征在于，所述转接模块包括：
    第二获取单元，用于在加载的规则因子包括多个规则因子时，获取与所述维度信息匹配率最高的规则因子；
    转接单元，用于基于匹配率最高的规则因子确定当前的审批人，并将审批流程转到确定的审批人所在节点进行数据的审批。
  13. 如权利要求10所述的 数据 审批装置，其特征在于，所述 数据 审批装置还包括：
    确定模块，用于根据审批链规则中的流转条件确定当前是否继续流转；
    结束模块，用于若当前无须再次进行流转，则结束审批流程。
  14. 如权利要求13所述的 数据 审批装置，其特征在于，所述数据审批装置还包括：
    处理模块，用于若当前需要再次进行流转，则返回继续流转的消息至工作流中，由工作流将审批流程流转至下一个节点，并在下一个节点中通过启动的服务在所述审批链规则中再次加载规则因子，以确定新的审批人。
  15. 如权利要求10所述的数据审批装置，其特征在于，所述数据审批装置还包括：
    导出模块，用于在接收到规则因子的修改指令时，在数据库导出存储有规则因子的数据表；
    修改模块，用于在所述数据表中基于修改操作修改规则因子，其中，所述修改操作包括增加、删除、更新和替换规则因子；
    更新模块，用于将修改了规则因子的数据表更新到数据库中。
  16. 如权利要求9所述的数据审批装置，其特征在于，所述数据审批装置还包括：
    校验模块，用于在待修改的审批人账号所在的账户栏中接收到替换账号时，对所述替换账号进行校验；
    执行模块，用于在校验成功后，执行审批人账号的替换操作。
  17. 一种 数据审批设备，其特征在于，所述数据审批设备包括 存储器、处理器及存储在所述存储器上并可在所述处理器上运行的 数据审批 程序，所述 数据审批 程序被所述处理器执行时实现如权利要求1所述的 数据审批 方法 的步骤 。
  18. 一种 数据审批设备，其特征在于，所述数据审批设备包括 存储器、处理器及存储在所述存储器上并可在所述处理器上运行的 数据审批 程序，所述 数据审批 程序被所述处理器执行时实现如权利要求 2 所述的 数据审批 方法 的步骤 。
  19. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有 数据审批 程序，所述 数据审批 程序被处理器执行时实现如权利要求1所述的 数据审批 方法的步骤。
  20. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有 数据审批 程序，所述 数据审批 程序被处理器执行时实现如权利要求 2 所述的 数据审批 方法的步骤。
PCT/CN2018/076156 2017-05-05 2018-02-10 数据审批方法、装置、设备和计算机可读存储介质 Ceased WO2018201774A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710315384.XA CN108804484A (zh) 2017-05-05 2017-05-05 数据审批方法、设备和计算机可读存储介质
CN201710315384.X 2017-05-05

Publications (1)

Publication Number Publication Date
WO2018201774A1 true WO2018201774A1 (zh) 2018-11-08

Family

ID=64016428

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076156 Ceased WO2018201774A1 (zh) 2017-05-05 2018-02-10 数据审批方法、装置、设备和计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN108804484A (zh)
WO (1) WO2018201774A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109767320A (zh) * 2018-12-17 2019-05-17 深圳壹账通智能科技有限公司 订单审核方法、装置、计算机设备和存储介质
CN109711816A (zh) * 2019-01-02 2019-05-03 深圳壹账通智能科技有限公司 合作机构信息管理方法、装置、计算机设备和存储介质
CN110020830A (zh) * 2019-03-21 2019-07-16 广东瑞恩科技有限公司 数据审批方法、装置、设备和计算机可读存储介质
CN109949013A (zh) * 2019-03-26 2019-06-28 北京致远互联软件股份有限公司 公文处理流转方法及系统
CN110210823A (zh) * 2019-05-15 2019-09-06 上海易点时空网络有限公司 审批流转的方法及装置
CN110798489A (zh) * 2020-01-06 2020-02-14 成都四方伟业软件股份有限公司 一种基于区块链的数据审批方法及系统
CN111369223A (zh) * 2020-03-11 2020-07-03 南京金信通信息服务有限公司 一种工作流的二次处理审批人方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101706889A (zh) * 2009-11-17 2010-05-12 深圳市监察局 行政审批电子监察的方法及系统
CN101763428A (zh) * 2010-01-04 2010-06-30 山东浪潮齐鲁软件产业股份有限公司 一种SOA对web服务的注册存储管理应用系统
CN101833714A (zh) * 2010-06-12 2010-09-15 山东中创软件工程股份有限公司 一种审批权限控制方法、装置及系统
CN102034208A (zh) * 2010-12-15 2011-04-27 中国民生银行股份有限公司 信贷业务审批数据处理系统及方法
CN103942722A (zh) * 2014-03-14 2014-07-23 郁建林 一种基于工作流的网络化数据协同报送统计系统及方法
CN104036019A (zh) * 2014-06-25 2014-09-10 北京奇虎科技有限公司 网页链接的开启方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101702212A (zh) * 2009-11-12 2010-05-05 上海众恒信息产业有限公司 一种审批系统及方法
CN103873345A (zh) * 2012-12-14 2014-06-18 上海格尔软件股份有限公司 一种基于规则实现邮件审批的方法
CN104144413A (zh) * 2013-05-10 2014-11-12 中国电信股份有限公司 基于移动终端的审批方法和系统
CN105809305A (zh) * 2014-12-30 2016-07-27 金蝶软件（中国）有限公司 实现流程自动审批的方法和装置
CN106485390A (zh) * 2015-09-01 2017-03-08 北京奇虎科技有限公司 审批流的生成方法和装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101706889A (zh) * 2009-11-17 2010-05-12 深圳市监察局 行政审批电子监察的方法及系统
CN101763428A (zh) * 2010-01-04 2010-06-30 山东浪潮齐鲁软件产业股份有限公司 一种SOA对web服务的注册存储管理应用系统
CN101833714A (zh) * 2010-06-12 2010-09-15 山东中创软件工程股份有限公司 一种审批权限控制方法、装置及系统
CN102034208A (zh) * 2010-12-15 2011-04-27 中国民生银行股份有限公司 信贷业务审批数据处理系统及方法
CN103942722A (zh) * 2014-03-14 2014-07-23 郁建林 一种基于工作流的网络化数据协同报送统计系统及方法
CN104036019A (zh) * 2014-06-25 2014-09-10 北京奇虎科技有限公司 网页链接的开启方法及装置

Also Published As

Publication number Publication date
CN108804484A (zh) 2018-11-13

Similar Documents

Publication Publication Date Title
WO2018201774A1 (zh) 数据审批方法、装置、设备和计算机可读存储介质
WO2020147385A1 (zh) 数据录入方法、装置、终端及计算机可读存储介质
WO2018076841A1 (zh) 数据分享方法、装置、存储介质及服务器
WO2018048118A1 (en) Server and method for controlling external device
WO2018076865A1 (zh) 数据分享方法、装置、存储介质及电子设备
WO2016183721A1 (zh) 一种终端设备刷机方法、装置和设备
WO2021012481A1 (zh) 系统性能监控方法、装置、设备及存储介质
WO2020087981A1 (zh) 风控审核模型生成方法、装置、设备及可读存储介质
WO2015018243A1 (zh) 一种基于iOS设备的网页拦截方法和设备
WO2020052247A1 (zh) 网络资源批量加载方法、智能电视、存储介质及装置
WO2020073615A1 (zh) 设备软件的升级方法、数据转化器及可读存储介质
WO2018076867A1 (zh) 数据备份的删除方法、装置、系统、存储介质和服务器
WO2018076844A1 (zh) 数据备份的方法、装置、存储介质及电子设备
WO2020253125A1 (zh) 日志管理方法、装置、设备及存储介质
WO2019223600A1 (zh) 蓝牙音频传输方法、装置及计算机可读存储介质
WO2020062615A1 (zh) 显示面板的伽马值调节方法、装置及显示设备
WO2020237849A1 (zh) 网络块设备快照读写方法、装置、设备及存储介质
WO2020199599A1 (zh) 工作队列的信息展示方法、装置、计算机设备和存储介质
WO2014044130A1 (zh) 业务巡检方法和系统、计算机存储介质
WO2017206881A1 (zh) 一种关联应用的处理方法、装置、存储介质及电子设备
WO2020135022A1 (zh) 显示面板的画面优化方法、装置及计算机可读存储介质
WO2019019341A1 (zh) 文件存储方法、终端和计算机可读存储介质
WO2017020620A1 (zh) 标签页同步方法、电子设备及存储介质
WO2016065878A1 (zh) 电子玩具的控制系统和方法、电子设备内容更新方法
WO2021107297A2 (ko) 서비스 요청 디바이스

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18793861

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 17/02/2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18793861

Country of ref document: EP

Kind code of ref document: A1