CN115222345A - Auditing operation method and device - Google Patents

Abstract

The application provides a method and a device for auditing operation; the method relates to a cloud computing technology and a block chain technology, and comprises the following steps: acquiring a database query statement, and generating a flow model based on the database query statement; acquiring data of a plurality of operating systems corresponding to the checking process from the process model; receiving a reference function for registering the operation to be checked in the checking process, and generating a uniform interface for inquiring the operation to be checked based on the reference function; calling a unified interface, and displaying the operation to be audited related to the login account in a window of an audit center platform based on data; receiving the auditing operation aiming at the operation to be audited, and updating the auditing state of the operation to be audited in the auditing flow; and detecting the operation to be audited and displaying the reminding information corresponding to the operation to be audited. By the method and the device, centralized auditing of jobs of different systems can be realized, and job processing efficiency is improved.

Description

A kind of audit operation method and device

technical field

The present application relates to cloud computing technology, and in particular, to a method and device for auditing operations.

Background technique

Cloud technology refers to a kind of hosting technology that unifies a series of resources such as hardware, software, and network in a wide area network or a local area network to realize the calculation, storage, processing and sharing of data. Cloud Technology is a general term for network technology, information technology, integration technology, management platform technology, application technology, etc. based on the application of cloud computing business models. All kinds of industry data need strong system backing support, which can be realized through cloud computing.

Taking the application of enterprise resource planning (ERP, Enterprise Resource Planning) system as an example, in related technologies, the operating systems such as procurement, quality, sales, production, finance, auditing, human resources and other operating systems running within the enterprise all involve the approval process. Documents need to be approved and signed by leaders at all levels according to the process, and the ERP system did not reach a consensus on the handling method of document approval during the initial design, resulting in a variety of different types of review methods in the ERP system, that is, each operating system in the ERP system has its own With the audit function, due to different audit methods, leaders at all levels need to open each operating system when auditing, and only know which documents to audit after entering the specific audit module window. This audit operation method is not only inconvenient for audit operations, but also brings about the problem that a large number of documents cannot be audited in time.

Therefore, the related art lacks an effective solution for auditing the operations in each operating system.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a method, apparatus, electronic device, and computer-readable storage medium for auditing operations, which can implement centralized auditing of operations in different systems and improve operation processing efficiency.

The technical solutions of the embodiments of the present application are implemented as follows:

The embodiment of the present application provides an audit operation method, which is applied to an audit center platform, and the audit center platform integrates multiple operation systems, including:

Obtaining a database query statement, and generating a process model based on the database query statement, wherein the process model is associated with the multiple operating systems;

Acquiring data of the plurality of operating systems corresponding to the review process from the process model;

receiving a lookup function for registering the job to be reviewed in the review process, and generating a unified interface for querying the job to be reviewed based on the lookup function;

Calling the unified interface, and based on the data, displaying jobs to be reviewed related to the login account on the window of the review center platform;

receiving an audit operation for the job to be reviewed, and updating the review status of the job to be reviewed in the review process;

The job to be reviewed is detected, and reminder information corresponding to the job to be reviewed is displayed, wherein the reminder information is used to remind the job to be reviewed that has not been reviewed.

The embodiment of the present application provides an audit operation device, including:

The audit process management module is used to obtain database query statements, and based on the database query statements, generate a process model, wherein the process model is associated with multiple operating systems; and from the process model, multiple data corresponding to the audit process are acquired. data of an operating system;

an audit job type registration module, configured to receive a lookup function for registering the to-be-approved job in the approval process, and to generate a unified interface for querying the to-be-approved job based on the lookup function;

The audit center module is used to call the unified interface, and based on the data, display the jobs to be reviewed related to the login account in the window of the audit center platform; receive the review operations for the jobs to be reviewed, and update the jobs to be reviewed The review status in the review process; the job to be reviewed is detected, and reminder information corresponding to the job to be reviewed is displayed, wherein the reminder information is used to remind that there is the job to be reviewed that has not been reviewed.

In the above solution, the review process management module is further configured to perform registration processing on the multiple operating systems in response to the registration operation for the multiple operating systems; Database query statements of the multiple operating systems; load the multiple operating systems based on the database query statements, use the multiple operating systems as the root node of the process model, and store the relevant information of the multiple operating systems As a child node of the process model, a process model combined with the multiple operating systems is obtained.

In the above solution, the audit center module is further configured to parse and process the data, and determine the content information of the process model; wherein, the content information includes the audit steps of the audit process, the audit steps Based on the content information of the process model, determine the audit node corresponding to the login account; call the unified interface corresponding to the job of the audit node to display the audit center platform The window displays the pending jobs related to the login account.

In the above solution, the audit job type registration module is further configured to determine a process type code corresponding to the registered job; generate an audit job identifier corresponding to the process type code for the audit center platform based on The audit job identifier queries the task list of the job to be audited.

In the above solution, the audit job type registration module is further configured to obtain an audit job identifier corresponding to the login account; A task list for reviewing jobs.

In the above solution, the audit job type registration module is further configured to display the form setting page of the job to be reviewed, and display the display style of the form on the form setting page; A selection operation, displaying a preview page of the selected style of the form; in response to a confirmation operation for the style of the form, using the selected style of the form as the display style of the job to be reviewed, so as to be used in the review process. The central platform displays the jobs to be reviewed in the display style.

In the above solution, the audit job category registration module is further configured to display a plurality of form options in response to a creation operation for the form. In response to a selection operation for the plurality of form options, in the job to be reviewed The form setting page displays the preview pages of the selected multiple forms in the job to be reviewed; in response to the confirmation operation for the selected multiple forms, the confirmed multiple forms are used as the sheet.

In the above solution, the audit center module is further configured to jump the audit status of the job to be audited to the next-level audit node when the audit operation satisfies the circulation conditions for passing the audit; When the circulation conditions for passing the review are not met, the review status of the job to be reviewed is jumped to the upper-level review node or the initial review node.

In the above solution, the audit center module is further configured to jump the audit status of the job to be audited to the next-level audit node when the audit operation satisfies the circulation conditions for passing the audit; When the circulation conditions for passing the review are not met, the review status of the job to be reviewed is jumped to the upper-level review node or the initial review node.

In the above solution, the audit center module is further configured to display a hosting page, and display at least one hosting account on the hosting page; in response to the hosting operation for the hosting account, the pending review related to the login account is displayed. The job is hosted to the hosting account corresponding to the hosting operation.

The embodiment of the present application provides an electronic device, including:

memory for storing executable instructions;

The processor is configured to implement the audit operation method provided by the embodiment of the present application when executing the executable instructions stored in the memory.

The embodiments of the present application provide a computer-readable storage medium storing executable instructions for implementing the audit operation method provided by the embodiments of the present application when executed by a processor.

The embodiment of the present application has the following beneficial effects:

Through database query statements, a process model integrating multiple operating systems is generated, and a unified interface for querying jobs to be reviewed is generated through a registered query function. Based on the unified interface and the data in the process model, multiple jobs with different auditing methods can be integrated The function of the system, combined with the data of multiple operating systems corresponding to the auditing process, can realize centralized auditing in the window of the auditing center platform, meet the needs of centralized auditing operations for jobs, and improve the efficiency of job processing.

Description of drawings

FIG. 1 is a schematic structural diagram of an auditing operation system 100 provided by an embodiment of the present application;

FIG. 2 is a schematic structural diagram of a server 200 provided by an embodiment of the present application;

3A is a schematic flowchart of a review operation method provided by an embodiment of the present application;

FIG. 3B is a schematic flowchart of a review operation method provided by an embodiment of the present application;

3C is a schematic flow chart of the audit operation method provided by the embodiment of the present application;

4 is a schematic diagram of a process model provided by an embodiment of the present application;

5 is a schematic diagram of the architecture of an audit management system provided by an embodiment of the present application;

6 is a schematic diagram of a business process of an audit process management module provided by an embodiment of the present application;

7 is a schematic diagram of a business process of an audit job type registration module provided by an embodiment of the present application;

8 is a schematic diagram of a business process of an audit center module provided by an embodiment of the present application;

9 is a schematic structural diagram of a workflow management system provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of node flow provided by an embodiment of the present application;

FIG. 11 is a schematic flowchart of an audit operation method provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be described in further detail below with reference to the accompanying drawings. All other embodiments obtained under the premise of creative work fall within the scope of protection of the present application.

In the following description, reference is made to "some embodiments" which describe a subset of all possible embodiments, but it is understood that "some embodiments" can be the same or a different subset of all possible embodiments, and Can be combined with each other without conflict.

In the following description, the term "first\second\third" is only used to distinguish similar objects, and does not represent a specific ordering of objects. It is understood that "first\second\third" Where permitted, the specific order or sequence may be interchanged to enable the embodiments of the application described herein to be practiced in sequences other than those illustrated or described herein.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the technical field to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of the present application, and are not intended to limit the present application.

Before further describing the embodiments of the present application in detail, the terms and terms involved in the embodiments of the present application are described, and the terms and terms involved in the embodiments of the present application are suitable for the following explanations.

1) Role: Account field "Role", different roles have different access rights to different resources.

2) Enterprise Resource Planning (ERP, Enterprise Resource Planning) refers to the management that is based on information technology, integrates information technology and advanced management ideas, and provides decision-making means for employees and decision-makers with systematic management ideas. platform.

3) Workflow is a kind of business process that can be fully or partially executed automatically. It can be transmitted and executed between different executors according to a series of process rules, documents, information or tasks.

4) Workflow technology is the computational model of the workflow, that is, the logic and rules of how the work in the workflow is organized together before and after are represented in a computer by an appropriate model, and the calculation is performed. The application characteristics of workflow technology determine that it has the characteristics of openness. In order to realize the integration of different services and products with different architectures, the workflow management alliance defines the reference model of the workflow management system architecture to adapt to the development situation.

5) Workflow management system is a common reference model, which does not limit which tools, platforms, and development methods are adopted for specific implementation, but only stipulates how to associate it with various implementations.

With the emergence of the Internet and the rapid development of computer technology, the information system is no longer just a means in many enterprises, but a strategic resource to ensure the success of the enterprise. There are still deficiencies in the implementation of management resource informatization such as storage, production, human, financial, and material. When it comes to the approval process, all kinds of documents need to be approved and signed by leaders at all levels according to the process. Because the ERP system is gradually expanded on the basis of the original production management and quality management systems, each subsystem in the ERP system is initially designed. There is no consensus on the handling method of document approval, resulting in a variety of different types of auditing methods. Although these subsystems each have auditing functions, due to different processing methods, leaders at all levels need to open each subsystem and enter the specific auditing method. After the module window, you will know which documents to review. Even if there is a reminder, it is a one-time reminder of the pop-up modal window when logging in, which not only inconvenients the review operation, but also brings about the problem that a large number of documents cannot be reviewed in time.

In view of the above technical problems, the embodiments of the present application provide a method, apparatus, electronic device, and computer-readable storage medium for reviewing operations, which can implement centralized review of jobs in different systems and improve job processing efficiency. The following describes the methods provided by the embodiments of the present application. As an exemplary application of the audit operation method, the audit operation method provided by the embodiments of the present application may be implemented by various electronic devices, for example, may be implemented as a server. In the following, exemplary applications when the electronic device is implemented as a server will be described.

Referring to FIG. 1, FIG. 1 is a schematic diagram of the architecture of the audit operation system 100 provided by the embodiment of the present application, wherein the audit operation system 100 includes a server 200 and a terminal (exemplarily shows a terminal 400-1 and a terminal 400-2) and Network 300. The terminal is connected to the server 200 through a network 300, and the network 300 may be a wide area network or a local area network, or a combination of the two.

In some embodiments, the audit process management module in the server 200 receives the data of multiple operating systems corresponding to the audit process set by the process administrator on the audit process management interface of the terminal 400-1; the audit job type registration in the server 200 The module receives the lookup function used by the process manager to register the jobs to be reviewed in the review process on the review job type registration interface of the terminal 400-1, and generates a unified interface for querying the jobs to be reviewed based on the lookup function; the review center in the server 200 When the module receives the operation of the login account in the window of the audit center platform of the terminal 400-2, the module calls the unified interface, and based on the data, displays the jobs to be audited related to the login account in the window of the audit center platform; in the server 200 The audit center module receives the audit operations of the audit personnel for the jobs to be audited in the window of the audit center platform of the terminal 400-2, and updates the audit status of the jobs to be audited in the audit process, so that the users (auditors) can perform the auditing operations under the same interface. The need for centralized approval greatly simplifies the review operation and improves the review efficiency. It should be noted that the audit process management module, the audit job type registration module, and the audit center module may be integrated into one server as the background server of the terminal 400-1.

In some embodiments, the server 200 may be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers, or may provide cloud services, cloud databases, cloud computing, cloud functions, cloud storage, Cloud servers for basic cloud computing services such as network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal 400-1, the terminal 400-2, and the server 200 may be directly or indirectly connected through wired or wireless communication, which is not limited in this embodiment of the present application.

Next, the structure of the electronic device for implementing the audit operation method provided by the embodiment of the present application will be described. As mentioned above, the electronic device provided by the embodiment of the present application may be the server 200 in FIG. 1 . Referring to FIG. 2 , FIG. 2 is a schematic structural diagram of a server 200 provided by an embodiment of the present application. The server 200 shown in FIG. 2 includes: at least one processor 210 and a memory 250 . The various components in server 200 are coupled together by bus system 240 . It will be appreciated that the bus system 240 is used to implement connection communication between these components. In addition to the data bus, the bus system 240 also includes a power bus, a control bus and a status signal bus. However, for clarity of illustration, the various buses are labeled as bus system 240 in FIG. 2 .

The processor 210 may be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc., where a general-purpose processor may be a microprocessor or any conventional processor or the like.

Memory 250 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid state memory, hard drives, optical drives, and the like. Memory 250 optionally includes one or more storage devices that are physically remote from processor 210 .

Memory 250 includes volatile memory or non-volatile memory, and may also include both volatile and non-volatile memory. The non-volatile memory may be Read Only Memory (RON, Read Only Memory), and the volatile memory may be Random Access Memory (RAN, Random Access Memory). The memory 250 described in the embodiments of the present application is intended to include any suitable type of memory.

In some embodiments, memory 250 is capable of storing data to support various operations, examples of which include programs, modules, and data structures, or subsets or supersets thereof, as exemplified below.

Operating system 251, including system programs for processing various basic system services and performing hardware-related tasks, such as framework layer, core library layer, driver layer, etc., for implementing various basic services and processing hardware-based tasks;

A network communication module 252 for reaching other computing devices via one or more (wired or wireless) network interfaces 220, exemplary network interfaces 220 including: Bluetooth, Wireless Compatibility (WiFi), and Universal Serial Bus ( USB, Universal Serial Bus), etc.;

In some embodiments, the audit operation device provided by the embodiments of the present application may be implemented in software. FIG. 2 shows the audit operation device 255 stored in the memory 250, which may be software in the form of programs and plug-ins, including the following Software modules: audit process management module 2551, audit job type registration module 2552, and audit center module 2553, these modules are logical, so they can be arbitrarily combined or further divided according to the functions implemented. The function of each module will be explained below.

In some embodiments, the job to be reviewed is uploaded to the state database of the blockchain network for storage; the smart contract in the blockchain network is invoked, so that the smart contract performs the following processing: Obtain the job to be reviewed in the blockchain; perform consensus processing on the job to be reviewed, and return the job to be reviewed as the calling result when the consensus is passed. In the embodiment of this application, the blockchain network includes a server, and through the consensus mechanism between nodes, the reliability of the job to be reviewed and the reliability of the obtained review status of the job to be reviewed can be guaranteed; of course, the updated pending review The audit status of the job can also be stored on the chain.

Hereinafter, an example will be given by taking the server 200 in FIG. 1 independently executing the audit operation method provided by the embodiment of the present application. The audit center platform is implemented by the server 200, and the audit center platform integrates multiple operation systems. Referring to FIG. 3A, FIG. 3A is a schematic flowchart of the audit operation method provided by the embodiment of the present application, which will be described in conjunction with the steps shown in FIG. 3A. .

In step 101, a database query statement is obtained, and a process model is generated based on the database query statement. Among them, the process model is associated with multiple operating systems.

In some embodiments, acquiring the database query statement may be implemented in the following ways: in response to the registration operation for the multiple operating systems, performing registration processing on the multiple operating systems; System database query statement; load multiple operating systems based on the database query statement, use multiple operating systems as the root node of the process model, and use the relevant information of multiple operating systems as the child nodes of the process model to obtain a combination of multiple operating systems process model.

In some examples, the audit process management module in the server performs registration processing on multiple operating systems to integrate the multiple operating systems into the server, and in response to a database query statement for managing the registered multiple operating systems, based on the database query The statement generates the process model of the combination of multiple operating systems, which can be realized by the following methods: querying the database, loading the name of the registered operating system, using the name of the operating system as the root node, and according to the relevant information of multiple operating systems ( For example, the review steps of the review process in the operating system, the flow conditions of the review steps, the review department and the reviewers), edit the child nodes of the root node to generate a process model. For example, when the variable value of the database query statement is -1, all registered operating system names are loaded, and the root node is displayed as the name of the operating system by default. Process model, that is, a process model that includes a complete life cycle of the review process.

For example, referring to FIG. 4 , FIG. 4 is a schematic diagram of a process model provided by an embodiment of the present application. In the audit process management module, the process model can be displayed in a tree structure, and the hierarchical relationship between parent and child nodes is established and displayed through parent fields (Parent), child fields and description fields.

For example, the maximum level of the process model has 7 nodes, which are the root node (operation system), process type, sub-audit process, audit step, department cluster, audit department, and auditor. Among them, the root node (operating system) and the process type node add/delete functions, which can be added/deleted through the developer code. Based on the operating system and process type operated by the developer, the structure of the process model is formed, and the rest Nodes (sub-audit processes, audit steps, department clusters, audit departments, auditors, etc.) can be used by process managers to edit themselves according to business needs. There are process types for different applications in one operating system. For example, in the purchase guarantee system, there are process types such as material purchase application approval, supplier review and approval, purchase transaction mode approval, purchase fund application approval, and material arrival acceptance review. There may be multiple sub-review processes under one process type. Taking the substance purchase application process type as an example, there are application processes for computer substances, equipment substances, and raw material substances. For these specific substances, it may be possible in one review process. Includes multiple sub-review processes. In the operating system, the corresponding sub-audit process can be selected according to the substances of different process types.

In the embodiment of the present application, the functions of multiple business systems with different auditing methods are integrated through the process model, so as to implement the function of centralized auditing in the same auditing window based on the process model.

In step 102, data of multiple operating systems corresponding to the review process are acquired from the process model.

In some embodiments, the data of multiple operating systems corresponding to the review process includes review steps of the review process, flow conditions of the review steps, review departments, reviewers, and the like. When the flow condition is true, determine the status of the current audit node (inflow or outflow). It should be noted that an audit process includes multiple audit steps, and an audit node is a node in the audit step, which is used to determine the audit status in the audit process.

In step 103, a lookup function for registering a job to be reviewed in the review process is received, and a unified interface for querying the job to be reviewed is generated based on the lookup function.

In some embodiments, a unified standard interface function is created through a workflow technology, and a unified interface for querying jobs in the review process is generated in response to a registration operation for a query function of a job in the review process.

For example, a job in the approval process can be a document that needs to be reviewed in the approval process, and the query function is an interface function for querying a document. Through the unified API interface function specification, the audit tasks implemented by different software manufacturers are integrated into the server, and the access to the jobs in the audit process is realized in a unified way.

In step 104, the unified interface is invoked, and based on the data, the jobs to be reviewed related to the login account are displayed on the window of the review center platform.

In some embodiments, referring to FIG. 3B , FIG. 3B is a schematic flowchart of the review operation method provided by the embodiment of the present application, which shows that step 104 in FIG. 3A can be implemented by executing steps 1041 to 1043 . Each step will be explained.

In step 1041, the data of a plurality of operating systems corresponding to the review process is analyzed and processed to determine the content information of the process model. The content information includes the review steps of the review process, the circulation conditions of the review steps, the review department, and the reviewers.

In some examples, since multiple operating systems with multiple auditing methods are integrated into the process model, it is necessary to parse the data of the multiple operating systems corresponding to the auditing process, and determine the auditing steps corresponding to the operating systems involved in the data. The order, the circulation conditions corresponding to each audit step, the audit department corresponding to each audit step, and the auditor corresponding to each audit step.

As an example, the flow condition includes whether the approval step is allowed to be skipped, the inflow condition of the approval step, and the outflow condition of the approval step. For example, for the purchase approval step, it can be set: when the purchase amount is less than 10,000, the purchase approval step is allowed to be skipped , then jump directly to the next-level audit node, such as the supplier audit step.

In the embodiment of the present application, by analyzing the data, multiple operating systems are integrated into the server, so as to realize unified management of the multiple operating systems, so as to facilitate subsequent centralized approval.

In step 1042, an audit node corresponding to the login account is determined based on the content information of the process model.

In some examples, the process model includes review steps of multiple business systems involved in the review process, and each review step corresponds to one or more review departments and reviewers. Based on the corresponding content information in the process model, the review process is determined. The audit node of the entire life cycle of the process, obtains the audit node corresponding to the login account from the audit nodes of the entire life cycle of the audit process. It should be noted that each review node is only for reviewers, that is, only the reviewer's account can display the pending review related to the login account in the window of the review center platform.

In other examples, the audit node can be directed to the accounts of all personnel, that is, all personnel accounts can log in to the platform of the audit center to query the audit node, but only the accounts of the auditors can perform audit operations.

In this embodiment of the present application, the accounts of all staff are supported to query the current audit node to know the audit progress of the audit process, and only audit operations are supported through the accounts of the auditors to ensure the rigor of the audit process.

In step 1043, the unified interface corresponding to the pending jobs of the audit node is called to display the pending jobs related to the login account on the window of the audit center platform.

In some examples, the unified interface corresponding to the job of the current audit node is determined from the unified interface corresponding to the job (for example, a document) of each audit node in the audit process, where the current audit node may be one or more, and the current audit node Corresponding to the login account; call the unified interface to display the pending auditing jobs related to the login account in the window of the audit center platform.

In the embodiment of the present application, through a unified interface, it is supported to display jobs to be reviewed related to the login account in the window of the review center platform, thereby realizing the convenience of review and improving the efficiency of review.

In step 105, a review operation for the job to be reviewed is received, and the review status of the job to be reviewed in the review process is updated.

In some embodiments, referring to FIG. 3C , FIG. 3C is a schematic flowchart of the audit operation method provided by the embodiment of the present application, which shows step 105 in 3A, which can also be implemented by executing steps 1051 to 1052 . Each step is explained.

In step 1051, when the auditing operation satisfies the flow condition for passing the auditing, the auditing state of the job to be audited is jumped to the next-level auditing node.

In some examples, the flow condition for approval can be set as the approval button being clicked. When the approval operation is to click the agree button and the flow condition for approval is satisfied, it is determined that the current approval node of the job to be reviewed has passed, and The audit status jumps from the current audit node to the next level audit node. The audit operation is performed by the account of the auditor corresponding to the next-level audit node.

In step 1052, when the audit operation does not meet the flow condition for passing the audit, the audit status of the job to be audited is jumped to the upper-level audit node or the initial audit node.

In some examples, the flow condition for approval is set as the approval button is clicked, and when the approval operation is to click the disagree button, that is, when the approval operation does not meet the flow condition for approval, it is determined that the current approval node of the job to be approved fails, and Jumps the review status of the job to be reviewed from the current review node to the previous review node.

In other examples, the job to be reviewed belongs to a certain review node among the interrelated review nodes in the review process. When the current review node corresponding to the job to be reviewed fails, the content of the job to be reviewed needs to be updated again, that is, The entire review process needs to be redone. That is to say, when the audit operation does not meet the circulation conditions for passing the audit, the audit status of the job to be audited is jumped to the initial audit node to update the pending job of the initial audit node, and the audit process is re-examined. The jobs to be audited corresponding to each audit node of .

In the embodiment of the present application, an audit center platform for centralized approval is provided, and centralized audit operations are performed based on the jobs to be audited displayed in the window of the audit center platform, which greatly improves the convenience of the audit operations and improves the audit operation. Efficiency, to meet the needs of the daily audit operations of the enterprise business.

In step 106, the job to be reviewed is detected, and reminder information corresponding to the job to be reviewed is displayed. The reminder information is used to remind that there are unreviewed jobs to be reviewed.

In some embodiments, when the window of the audit center platform has been opened and is not an active window, the jobs to be reviewed related to the login account are regularly detected; when it is detected that there are jobs to be reviewed, it is displayed in the window of the audit center platform. Reminder information; the reminder information is used to remind that there are unreviewed pending jobs.

When the Moderation Hub Platform's window is open but not currently the active window (for example, the user may be browsing a web page or editing a document), when a pending job is detected, the Moderation Hub Platform's window's taskbar button flashes once and highlights It is displayed until the query operation of the login user (that is, the reviewer) in the window of the review center platform is received, and the taskbar button returns to normal (not flashing or highlighting). It should be noted that the task bar button is a display identifier in the window of the audit center platform used to indicate whether there is a job to be audited.

In some other embodiments, when the window of the audit center platform is not opened, periodically detect the jobs to be reviewed related to the login account; when it is detected that there are jobs to be reviewed, a reminder message is displayed in the window of the audit center platform; wherein , the reminder information is used to remind that there are unapproved pending jobs.

As an example, the audit center module in the server is used to manage all jobs to be audited for multiple operating systems. Start the audit center module, and display an icon on the tray in a certain area of the audit center platform window. When the audit center platform window is not opened, the audit center module in the server will regularly detect the pending audit jobs related to the login account. When it is detected that there is a job to be reviewed, a flashing icon is displayed. In response to the trigger operation of the reviewer (for example, double-clicking the icon to open the window of the review center platform), the flashing icon is stopped flashing, and the review center is displayed on the task bar. The task button of the platform's window. It should be noted that the icon is a display mark used to indicate that the audit center module has been activated. In some embodiments, the process type code corresponding to the registered job to be reviewed is determined; the review job identifier corresponding to the process type code is generated, so that the review center platform can query the task list of the job to be reviewed based on the review job identifier.

In some examples, the audit job category registration module in the server pre-registers the process type code, and in response to the process type added by the developer, the audit job category registration module loads the pre-registered process type code to generate a process type corresponding to the process type coding. An audit job identifier corresponding to the process type code is generated, so as to realize the association between the process type code and the audit job identifier. In the subsequent application, the audit center module in the server uses the audit job identifier as the type of business to be audited, so as to support the auditor to query the task list of all audit job identifiers related to the auditor's account on the audit center platform. It should be noted that the process type node can support developers to customize the rule parameter name and parameter type, and the rule parameters defined by the upper-level node can be inherited and used by the lower-level node.

In the embodiment of the present application, through the association established between the process type code and the audit job identifier, the login account is supported to query the task list of the job to be reviewed, which improves the convenience of the review job and improves the review efficiency.

In some embodiments, a table setting page of the job to be reviewed is displayed, and a display style of the table is displayed in the table setting page; in response to a selection operation for the style of the table, a preview page of the selected style of the table is displayed; For the confirmation operation of the style of the table, the selected style of the table is used as the display style of the job to be reviewed, so that the job to be reviewed is displayed in the display style on the review center platform.

In some examples, the job to be reviewed here is a document, and the display styles of the form of the document include: one-to-one master-slave table, one-to-many master-slave table, single-table structure (one master table) and other forms. The audit job type registration module of the server supports the developer to register the display style of the form of the document through the data source function of the document. Therefore, the audit job type registration module of the server can support the form setting operation, that is, the form setting page of the document is displayed, and the form setting page includes the display style of the form registered by the developer. A preview page showing the selected display style of the table. The server's audit job category registration module also supports process managers to set table properties (for example: width, height, tree layer display, multi-table header, etc.), column properties (for example: Chinese title, column width, alignment, etc.) and Dataset properties (eg: display format, etc.). It should be noted that the parameters of the display style can also be stored in the database.

In some embodiments, in response to a creation operation for the form, a plurality of form options are displayed; in response to a selection operation for the plurality of form options, a form setting page of the job to be reviewed displays a plurality of forms selected in the job to be reviewed The preview page of ; in response to the confirmation operation for the selected multiple forms, the confirmed multiple forms are used as the forms of the job to be reviewed.

In some examples, the creation of the table may also be achieved by: determining the details of multiple records in the job to be reviewed, and automatically matching the properties of the table for the record details, where the properties of the table include display style and table number. Furthermore, the audit job type registration module of the server can support the auditor to query the updated information of a certain record detail among the multiple record details in the document. Display the details of multiple records corresponding to the document in the display style of the created table, so that the auditor can query the updated information of a certain record of the document.

In some embodiments, after generating the audit job identifier corresponding to the process type code, the following steps may be performed: obtaining the audit job identifier corresponding to the login account; 's task list for jobs pending review. In some embodiments, a hosting page is displayed, and at least one hosting account is displayed on the hosting page; in response to the hosting operation for the hosting account, in response to the hosting operation for the login account on the hosting page, the pending operation related to the login account is hosted to the escrow account corresponding to the escrow operation.

In some examples, the audit center module in the server supports the hosting function, the audit center module in the server displays a hosting page, and displays on the hosting page at least one hosting account that can perform hosting operations; in response to the reviewer checking the hosting account on the hosting page The escrow operation of the escrow account (that is, the selection operation of the escrow account), the pending operation related to the login account is managed to the escrow account corresponding to the escrow operation.

In the embodiment of the present application, it is supported to host the pending review operations related to the login account to other accounts, so that when the reviewers of the current review node cannot review, the review progress of the review process is not affected, and the convenience of the review process is improved.

Below, an exemplary application of the embodiments of the present application in a practical application scenario will be described. Take the function of the audit management system integrating the audit operation method provided by the embodiment of the present application in the server as an example. Referring to FIG. 5 , FIG. 5 is a schematic structural diagram of an audit management system provided by an embodiment of the present application. The auditing management system includes an auditing process management module, an auditing operation type registration module, and an auditing center module, where the auditing management system (ie, the auditing operation device) is a software system that implements the auditing operation method provided by the embodiment of the present application, and is integrated in the server. middle. The three modules in the audit management system are described in detail below.

The audit process management module receives the relevant data corresponding to the audit process of the business uploaded by the user on the process management interface (that is, the data of multiple operating systems corresponding to the audit process, including the audit steps of the audit process, the circulation conditions of the audit steps, and the audit process. Departments, reviewers, etc.), analyze the data uploaded by users, and obtain a process model. The process module involves two types of users: developers and process managers.

In some embodiments, referring to FIG. 6 , FIG. 6 is a schematic diagram of a business process of an audit process management module provided by an embodiment of the present application.

In step 601, the review process management module receives the root node name of each operating system defined by the developer. It should be noted that the name of the root node here is generally the name of the subsystem (ie, the name of the operating system).

In step 602, the review process management module receives the process type defined by the developer. According to the defined operation system, the audit process management module integrates all the defined operation systems into the audit process management module, which can be called by the audit center module.

In step 603, the review process management module receives the rule parameters added by the developer. The rule parameter name and parameter type can be customized under the process type node, and the rule parameters defined by the upper-level node can be inherited and used by the lower-level node.

In step 604, the audit process management module receives the sub-audit process added by the process manager.

It should be noted that there are process types for different applications in a subsystem. For example, in the purchase guarantee system, there are material purchase application approval, supplier review and approval, purchase transaction mode approval, purchase fund application approval, and material arrival. Process types such as acceptance review. Similarly, there may be multiple review processes under one process type. Taking the substance purchase application process type as an example, there may be application approval processes for computer substances, equipment substances, and raw material substances. In some embodiments, for multiple types of substances, an audit process may include multiple sub-audit processes, that is, the audit process management module receives multiple sub-audit processes selected by the process manager according to substances of different process types on the process management interface to generate multiple sub-approval processes.

In step 605, the review process management module receives the review steps added by the process manager.

It should be noted that the order and name of the audit steps of each audit process added are managed, and the rule conditions of the audit steps set by the process manager (that is, the flow conditions of the audit steps, whether to allow skipping, inflow conditions, outflow conditions, etc.) conditions, etc.). When the specified rule condition is true, the auditing state of the auditing node can be determined (transfer to the corresponding auditing node, for example, the upper-level auditing node, the next-level auditing node, or the initial auditing node, etc.). The next level of each audit node cannot have child nodes with duplicate names.

In step 606, the review process management module receives the department cluster added by the process manager.

It should be noted that a cluster represents an abstract department, and an abstract department can contain multiple instance departments, but only one of them can be used as the audit department during auditing.

In step 607, the audit process management module receives the audit department added by the process manager.

In some embodiments, when the audit department of the process is managed, the department name can be imported from the human resources system into the audit process management module, which is globally unique. Receive the rule conditions of the audit department set by the process manager (that is, the flow conditions of the audit step, whether to allow skipping, inflow conditions, outflow conditions, etc.).

In step 608, the review process management module receives reviewers added by the process management personnel.

In some embodiments, the audit process management module receives the level of rights in the auditor group set by the process manager, and whether the auditor has the ability to finalize the audit. There are multiple auditors in the same department, and the one with the highest authority is the effective auditor.

The audit job type registration module is a secondary development platform for developers. By specifying the relationship between the activities in the workflow process and the application components that support users, a complete workflow management system in the ERP system is established. Considering that the content formats of the master and slave tables of documents, contracts and other data involved in each subsystem are completely different, the workflow management system adopts the data query function for registering various documents by the program developer and dynamically sets the properties of the display table. In the audit and use stage, the audit program dynamically parses the table design and presents it to the end user according to the designer's wishes, so that various documents can be browsed and displayed on the same window.

In some embodiments, referring to FIG. 7 , FIG. 7 is a schematic business flow diagram of the audit job category registration module provided by the embodiments of the present application.

In step 701, the audit work type registration module registers the audit work type. Receive the developer's registration operation for the audit job type, and register the audit job type.

In some embodiments, the audit job type registration module receives the developer's operation of creating an audit job identifier, and generates an audit job identifier for each document of the audit type. The audit job type registration module supports developers to register the display content of documents, and generates a unique ID for each type of review document, that is, the audit job ID.

In step 702, the audit job type registration module registers the audit process type codes of each subsystem. Receive the registration operation of the audit process type code of each subsystem from the developer, and register the audit process type code of each subsystem.

In some embodiments, the audit process type code is registered. After the type added to the process type in the audit process management module, the audit process type code will be automatically generated, and developers can register through the program to realize the association between the audit process type code and the audit job identification. In the later application, the audit center module uses the audit job identifier as the type of audit job, and supports users to query the task list of all audit job identifiers related to the login account based on the audit job identifier on the audit center platform.

In the embodiment of the present application, by registering the audit process type codes of each subsystem, the audit platform can take over all audit tasks of each subsystem, and realize unified management of audit processes of each subsystem in the enterprise.

In step 703, the audit operation type registration module registers the documents of the audit process. Receive the registration operation of the document information by the developer, and register the document in the review process.

In some embodiments, the audit job category registration module supports the registration of various forms of documents such as one-to-one master-slave table, one-to-many master-slave table, single-table structure (one master table), etc. When registering the data source function of these documents Afterwards, process managers can be supported to arbitrarily set the table properties (for example: width, height, tree layer display, multiple headers, etc.), column properties (for example: Chinese title, column width, alignment, etc.) and dataset properties (for example: Chinese title, column width, alignment, etc.) For example: display format, etc.).

It should be noted that the audit job type registration module supports developers to log in to their own accounts, and associate the job ID to be audited, the audit process type code, the audit job name, and the document name through information registration. Considering that different systems and different types of documents will involve data expansion processing before and after the audit, the audit job type registration module pre-registers the corresponding database to store the data in the database, and the subsequent data can be further based on the data stored in the database. Extended processing.

In step 704, the audit job type registration module receives the display style selected by the process manager, and dynamically changes the table attributes in real time.

In some embodiments, the audit job category registration module receives the display style selected by the process manager, reads the stored display style parameters from the database, and dynamically changes the table attributes in real time.

In step 705, the audit job category registration module receives the right-click menu of the form added by the process manager.

In some embodiments, a right-click menu of a form added by a process manager is received, multiple form tabs are created on the menu, and multiple contents are displayed in the same pop-up window. In addition to supporting the user to query the content of the document, it also supports the user to query the updated information of a record in the document details.

The audit center module is a client tool for auditors at all levels to conduct audit operations and provide audit-related functions. Based on the creation of the audit process management module and the audit job type registration module, the audit center module will automatically take over the audit job, and the audit job can be displayed in the window of the audit center platform, and is responsible for arranging the execution time of each activity in the process and calling the appropriate personnel. and application resources, etc.

In some embodiments, referring to FIG. 8 , FIG. 8 is a schematic diagram of a business process of an audit center module provided by an embodiment of the present application.

In step 801, the audit center module detects the pending operations related to the login account.

In step 802, the audit center module receives the query operation and displays the jobs to be audited.

In step 803, the audit center module receives the reference operation, and displays the document details of the operation to be audited.

In step 804, the audit center module receives the audit operation. When it is detected that the approval is passed, step 805 is performed, and when it is detected that the approval is not approved, step 801 is performed to display other jobs to be reviewed.

In step 805, the audit center module jumps the audit status of the job to be audited in the audit process to the next-level audit node.

In step 806, the audit center module stores the audit data in the database as historical records.

It should be noted that the audit center module mainly includes three parts: audit operation center, timing reminder, and system parameter setting. 1) Timely reminder. The audit center program takes over all audit tasks of the ERP system. In some embodiments, after the audit center module is started, an icon is only displayed on the system tray of a certain area of the display page. Once a job to be reviewed is found, the icon is flashed and displayed, and a trigger operation of the job to be reviewed is received, for example, double-clicking icon to open the general audit window (ie, the window of the Audit Center platform). At this time, the icon is displayed without blinking, and the task button of the window is displayed on the task bar. If the general audit window is open but not currently the active window (for example, the user may be browsing a web page or editing a document), if the timer detector finds a job to be reviewed, the icon does not flash, and the general audit window taskbar button flashes once and high It will be displayed on the taskbar until it receives the query operation from the logged-in user (that is, the reviewer) in the general review window, and the taskbar button will return to normal (not flashing and not highlighted). 2) Review the operation center. The audit operation center page is the main work page of the audit center module, which mainly involves two aspects of work: one is to obtain the log-in user's pending work according to the login user ID, which can support the audit user to review the documents submitted by various departments and query the detailed information corresponding to the documents. and document attachments to understand the review progress of documents. Then, after receiving the user (auditor) to perform an audit operation on the document and confirm it with a signature, update the audit status of the pending operation in the audit process; the second is to display the archived or audited documents, the detailed information and document files corresponding to the documents. It enables users (auditors) to know more about the audit results of documents, archived or audited documents. 3) System parameter setting. The system parameter settings include the frequency that the audit management system automatically detects the job records to be audited, whether the audit management system is automatically popped up, and whether the audit management system is automatically started when it is turned on.

In some embodiments, the establishment of an audit management system based on a workflow management system is taken as an example. Referring to FIG. 9, FIG. 9 is a schematic structural diagram of a workflow management system provided by an embodiment of the present application. Among them, the audit management system mainly includes three parts: software components, system control data, and other applications and application data. The specific descriptions are as follows:

1) Model establishment in the initial stage, and a workflow model is established through modeling tools. As an example, there are no specific constraints on the modeling tools, and professional modeling tools from third-party manufacturers can be used, or text, graphics, or language symbols can be used to describe the process definition, and the workflow model can be established visually. In the running phase of the workflow model, the audit management system mainly parses the workflow model according to the agreed syntax and semantics. The extracted workflow model includes attributes and interface specifications of the entire life cycle of the review process: A. Describe a meta model. The meta-model describes the related properties of the entire life cycle of the workflow instance, such as: workflow type, activity, transition condition, workflow-related data, organization, role and other types of properties. B. Publish API function specifications. One situation is between different workflow systems, and the other is between workflow processes defining specifications between products. Through the unified release of API functions, the workflow products implemented by different software manufacturers can be integrated into the audit management system, and the access to the workflow process definition can be realized in a unified way.

Review process scheduling in the running phase: In the complex applications of large enterprises, there are review processes for different specific businesses at the same time. An audit process will have a series of states in the life cycle, such as creation, pending allocation, execution, suspension, and end. Referring to the workflow model designed in the modeling stage, a review process will involve many specific operation steps, and will interact with different organizations and tools to complete state transitions. The workflow execution service can be understood as a state transition machine. When an audit process responds to external events, it can automatically determine the next state change of the audit process in combination with the set rules. After the process instance ends and is destroyed, the log analysis of each audit process and execution status provides a basis for the improvement of the audit process design.

As an example, refer to FIG. 10 , which is a schematic diagram of node flow provided by an embodiment of the present application. Taking the "Submitted" node to jump to the "Published" node as an example, when the review status of the bid is submitted, the reviewer will review the pending work of the bid. For example, the circulation condition for passing the review is to click the publish button. , when the review operation meets the approved circulation conditions, the bid will be released and the review status will be updated to Published.

Client human-computer interaction in the application stage: This part is the application of the audit management system. First, the tasks to be reviewed in the task table of the audit management system are allocated to different customers (auditors). Review actions. Depending on the operation result, the status of the job to be reviewed will change, and the workflow execution service will determine whether it should continue to take over the job to be reviewed corresponding to the next-level node of the job to be reviewed. A plurality of corresponding workflow models are established for multiple operating systems of different software vendors, and a general task manager is used to uniformly schedule the jobs to be reviewed in the task manager.

2) System control data. It mainly refers to the data that the workflow system controls its operation during the execution phase. One is the control data used in the execution of the process instance, and this part of the data is designed and implemented by the workflow model provider; the other is the rule or constraint data, which is extracted from the specific audit management system and defines the description, which can be used by the workflow Engine identification. For example, the specific amount of the document specifies rules such as approval by the reviewer.

3) Other applications and application data. The workflow management system provides a software support environment for the operation of multiple operating systems, and needs to interact with multiple operating systems to play a role. The workflow management system supports the operating systems by establishing standardized external interfaces and various types of API interfaces. function to implement. At the same time, it can be considered to directly call the job of the operating system for transaction processing, and this call can be carried out in distributed and heterogeneous systems. Application data refers to the business data (such as documents) of the operating system, and is the service object of the workflow management system. The standardized flow of business data is realized through the workflow management system.

In the embodiment of the present application, the integration of multiple operating systems is realized through the audit management system, which satisfies the needs of users (auditors) for centralized examination and approval under the same interface, and can meet the business requirements of the daily examination and approval of the enterprise information system. Advanced auditing and auditing process customization functions, and the method of registering based on job types simplifies the development tasks of developers.

In some embodiments, FIG. 11 is a schematic flowchart of an audit operation method provided by an embodiment of the present application. Referring to FIG. 11 , the audit operation method provided by an embodiment of the present application is implemented by a terminal and a server collaboratively. Methods include:

Step 1101: The terminal acquires the database query statement received in the audit process management interface, and sends it to the server.

Step 1102: The server generates a process model based on the database query statement; and obtains data of multiple operating systems corresponding to the audit process from the process model.

Step 1103: The terminal acquires the lookup function for registering the job to be reviewed in the review process received in the review job type registration interface, and sends it to the server.

Step 1104: The server generates a unified interface for querying jobs to be reviewed based on the query function.

Step 1105: The server parses the data to determine the content information of the process model. The content information includes the review steps of the review process, the circulation conditions of the review steps, the review department, and the reviewers.

Step 1106: The server determines an audit node corresponding to the login account based on the content information of the process model.

Step 1107: The server invokes the unified interface corresponding to the pending jobs of the audit node to display the pending jobs related to the login account on the window of the audit center platform.

Step 1108: When the audit operation satisfies the circulation conditions for passing the audit, the server jumps the audit status of the job to be audited to the next-level audit node; The status jumps to the upper-level audit node or the initial audit node.

Step 1109: The server detects the job to be reviewed, and sends the detection result to the terminal.

Step 1110: The terminal displays reminder information corresponding to the job to be reviewed. The reminder information is used to remind that there are unreviewed jobs to be reviewed.

By applying the above-mentioned embodiment, centralized auditing on the window of the auditing center platform can be realized, the demand for centralized auditing operations of the jobs to be audited can be met, and the processing efficiency of the jobs to be audited can be improved.

The following will continue to describe the exemplary structure of the audit operation device 255 provided by the embodiments of the present application implemented as software modules. In some embodiments, as shown in FIG. 2 , the software modules stored in the audit operation device 255 of the memory 250 may include :

The audit process management module 2551 is used to obtain a database query statement, and generate a process model based on the database query statement, wherein the process model is associated with a plurality of operating systems; acquire from the process model corresponding to the audit process Data of multiple operating systems; the audit job type registration module 2552 is used to receive a lookup function for registering the jobs to be reviewed in the review process, and generate a unified interface for querying the jobs to be reviewed based on the lookup function ; Audit center module 2553, for calling the unified interface, and based on the data in the window of the audit center platform to display the job to be reviewed related to the login account; Receive the review operation for the job to be reviewed, update the job to be reviewed Review the review status of the job in the review process; detect the job to be reviewed, and display reminder information corresponding to the job to be reviewed, wherein the reminder information is used to remind that there is the job to be reviewed that is not reviewed.

In some embodiments, the review process management module 2551 is further configured to perform registration processing on the multiple operating systems in response to the registration operations for the multiple operating systems; The database query statements of the multiple operating systems; load the multiple operating systems based on the database query statements, use the multiple operating systems as the root node of the process model, and load the multiple operating systems based on the database query statement. The relevant information is used as a child node of the process model to obtain the process model combined with the multiple operating systems. In some embodiments, the audit center module 2553 is further configured to parse and process the data, and determine content information of the process model; wherein the content information includes the audit steps of the audit process, the The flow conditions of the auditing step, the auditing department and the auditing personnel; based on the content information of the process model, determine the auditing node corresponding to the login account; call the unified interface corresponding to the to-be-audited job of the auditing node to The window of the audit center platform displays the jobs to be audited related to the login account.

In some embodiments, the audit job type registration module 2552 is further configured to determine a process type code corresponding to the registered job to be audited; generate an audit job identifier corresponding to the process type code for the The review center platform queries the task list of the job to be reviewed based on the review job identifier.

In some embodiments, the audit job type registration module 2552 is further configured to obtain an audit job identifier corresponding to the login account; based on the audit job identifier, display on the window of the audit center platform related to the login account 's task list for jobs pending review.

In some embodiments, the review job category registration module 2552 is further configured to display a form setting page of the job to be reviewed, and display the display style of the form in the form setting page; a style selection operation, displaying a preview page of the selected style of the form; in response to the confirmation operation for the style of the form, using the selected style of the form as the display style of the job to be reviewed, to The job to be reviewed is displayed in the display style on the review center platform.

In some embodiments, the audit job category registration module 2552 is further configured to display a plurality of table options in response to a creation operation for the table; in response to a selection operation for the plurality of table options, in the The form setting page of the job to be reviewed displays the preview pages of the multiple forms selected in the job to be reviewed; in response to the confirmation operation for the selected multiple forms, the confirmed multiple forms are used as the to-be-approved multiple forms. A form for reviewing assignments.

In some embodiments, the audit center module 2553 is further configured to jump the audit status of the job to be audited to the next-level audit node when the audit operation satisfies the flow conditions for passing the audit; When the audit operation does not meet the circulation conditions for passing the audit, the audit status of the job to be audited is jumped to the upper-level audit node or the initial audit node.

In some embodiments, the audit center module 2553 is further configured to jump the audit status of the job to be audited to the next-level audit node when the audit operation satisfies the flow conditions for passing the audit; When the audit operation does not meet the circulation conditions for passing the audit, the audit status of the job to be audited is jumped to the upper-level audit node or the initial audit node.

In some embodiments, the audit center module 2553 is further configured to display a hosting page, and display at least one hosting account on the hosting page; in response to the hosting operation for the hosting account, the login account related The job to be reviewed is hosted on the hosting account corresponding to the hosting operation.

Embodiments of the present application provide a computer program product or computer program, where the computer program product or computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the above-mentioned audit operation method in the embodiment of the present application.

The embodiments of the present application provide a computer-readable storage medium storing executable instructions, wherein the executable instructions are stored, and when the executable instructions are executed by a processor, the processor will be caused to execute the audit operation method provided by the embodiments of the present application , for example, as shown in Figures 3A, 3B, and 3C for the audit operation method.

In some embodiments, the computer-readable storage medium may be memory such as FRAM, ROM, PROM, EP ROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories of various equipment.

In some embodiments, executable instructions may take the form of programs, software, software modules, scripts, or code, written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and which Deployment may be in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

As an example, executable instructions may, but do not necessarily correspond to files in a file system, may be stored as part of a file that holds other programs or data, for example, in a Hyper Text Markup Language (HTML) document One or more scripts of a , stored in a single file dedicated to the program in question, or in multiple cooperating files (eg, files that store one or more modules, subprograms, or code sections).

As an example, executable instructions may be deployed to be executed on one computing device, or on multiple computing devices located at one site, or alternatively, distributed across multiple sites and interconnected by a communication network execute on.

To sum up, by generating a unified interface for querying different documents based on the embodiments of the present application, the requirements for integrating the auditing functions of multiple operating systems are realized, thereby realizing the centralized auditing function of the window of the auditing center platform, which satisfies the needs of enterprises. The needs of the daily audit operations of the business. Through the audit management system, the integration of multiple operating systems is realized, which satisfies the needs of users for centralized approval under the same interface, and can meet the business needs of the daily approval of the enterprise information system. It has multi-level audit and audit process customization functions. The method of category registration simplifies development tasks for developers. The blockchain network includes servers. Through the consensus mechanism between nodes, the reliability of the job to be reviewed and the reliability of the obtained review status of the job to be reviewed can be guaranteed; of course, the updated review status of the job to be reviewed can also be listed on the chain storage. Through data analysis, multiple operating systems are integrated into the server to achieve unified management of multiple operating systems. Support the account of all staff to query the current audit node, understand the audit progress of the audit process, and only support the audit operation through the account of the auditor to ensure the rigor of the audit process. Through the unified interface, it supports the display of pending audit jobs related to the login account in the window of the audit center platform, which realizes the convenience of audit and improves the efficiency of audit. An audit center platform for centralized approval is provided, and centralized audit operations are performed based on the jobs to be audited displayed in the window of the audit center platform, which greatly improves the convenience of audit operations, improves the audit efficiency of audit operations, and satisfies the needs of enterprise business. The needs of daily audit work.

The above descriptions are merely examples of the present application, and are not intended to limit the protection scope of the present application. Any modifications, equivalent replacements and improvements made within the spirit and scope of this application are included within the protection scope of this application.

Claims (10)

1. A processing method for audit operation is applied to an audit center platform, wherein the audit center platform integrates a plurality of operation systems, and the method comprises the following steps:

acquiring a database query statement, and generating a flow model based on the database query statement, wherein the flow model is associated with the plurality of operating systems;

acquiring data of the plurality of operating systems corresponding to the checking process from the process model;

receiving a reference function for registering the operation to be audited in the auditing process, and generating a uniform interface for inquiring the operation to be audited based on the reference function;

calling the unified interface, and displaying the operation to be audited related to the login account in a window of an audit center platform based on the data;

receiving the auditing operation aiming at the operation to be audited, and updating the auditing state of the operation to be audited in the auditing process;

and detecting the operation to be audited, and displaying reminding information corresponding to the operation to be audited, wherein the reminding information is used for reminding that the operation to be audited which is not audited exists.

2. The method of claim 1, wherein obtaining a database query statement and generating a flow model based on the database query statement comprises:

performing registration processing on the plurality of operating systems in response to a registration operation for the plurality of operating systems;

receiving a database query statement for managing the plurality of operating systems subjected to the registration processing;

and loading the plurality of operating systems based on the database query statement, taking the plurality of operating systems as root nodes of a process model, and taking the relevant information of the plurality of operating systems as child nodes of the process model to obtain a process model of the combination of the plurality of operating systems.

3. The method according to claim 1, wherein the invoking the unified interface and displaying the to-be-audited job related to the login account in the window of the audit center platform based on the data comprises:

analyzing the data to determine the content information of the process model;

the content information comprises an auditing step of the auditing process, circulation conditions of the auditing step, an auditing department and an auditor;

determining an auditing node corresponding to the login account based on the content information of the process model;

and calling a unified interface corresponding to the operation to be audited of the audit node so as to display the operation to be audited related to the login account in a window of the audit center platform.

4. The method of claim 1, wherein after receiving a lookup function that registers jobs to be audited in the audit flow, the method further comprises:

determining a process type code corresponding to the registered job to be audited;

and generating an auditing operation identifier corresponding to the flow type code so that the auditing center platform can inquire a task list of the operation to be audited based on the auditing operation identifier.

5. The method of claim 4, wherein after generating an audit job identification corresponding to the flow type code, the method further comprises:

acquiring an auditing operation identifier corresponding to the login account;

and displaying a task list of the to-be-audited operation related to the login account in a window of the audit center platform based on the audit operation identifier.

6. The method of claim 1, further comprising:

displaying the table setting page of the operation to be checked, and displaying the display style of the table in the table setting page;

displaying a preview page of the selected style of the table in response to a selection operation for the style of the table;

and in response to the confirmation operation of the form style, taking the selected form of the form as the display form of the job to be checked, and displaying the job to be checked in the display form on a checking center platform.

7. The method of claim 6, further comprising:

displaying a plurality of table options in response to a create operation for the table;

responding to the selection operation of the plurality of table options, and displaying preview pages of the selected plurality of tables in the job to be checked on a table setting page of the job to be checked;

and in response to the confirmation operation aiming at the selected plurality of tables, taking the confirmed plurality of tables as the tables of the job to be audited.

8. The method according to claim 1, wherein the receiving an audit operation for the job to be audited and updating an audit state of the job to be audited in the audit process includes:

when the auditing operation meets the circulation condition of approved operation, skipping the auditing state of the operation to be audited to the next level of auditing node;

and when the auditing operation does not meet the circulation condition of approved operation, jumping the auditing state of the operation to be audited to the upper-level auditing node or the initial auditing node.

9. The method of claim 1, further comprising:

displaying a managed page, and displaying at least one managed account number on the managed page;

and in response to the hosting operation aiming at the hosting account, hosting the to-be-audited operation related to the login account to the hosting account corresponding to the hosting operation.

10. An audit task apparatus, comprising:

the auditing flow management module is used for acquiring database query statements and generating a flow model based on the database query statements, wherein the flow model is associated with the plurality of operating systems;

acquiring data of a plurality of operating systems corresponding to an auditing process from the process model;

the auditing operation type registering module is used for receiving a consulting function for registering the operation to be audited in the auditing flow and generating a uniform interface for inquiring the operation to be audited based on the consulting function;

the auditing center module is used for calling the unified interface and displaying the operation to be audited related to the login account in a window of an auditing center platform based on the data;

receiving the auditing operation aiming at the operation to be audited, and updating the auditing state of the operation to be audited in the auditing process;

and detecting the operation to be audited, and displaying reminding information corresponding to the operation to be audited, wherein the reminding information is used for reminding the existence of the operation to be audited which is not audited.

Images