Document process management method and device, storage medium and server

Abstract

The embodiment of the invention discloses a document process management method and device, a storage medium and a server, and relates to the field of process processing. Related attribute information is set through a shared organization and a shared center interface, and meanwhile, a pool entering rule is configured on a shared pool interface. When a receipt instance submitted by a user and a process thereof are detected, a process chain including a plurality of links can be identified. In the process execution process, the task attribute of the current link can be captured. If the link meets the pool entering condition, adding the link as a shared task into a task pool of the corresponding shared center according to attribute information of the shared center and the organization; and if not, directly pushing to the user corresponding to the post role for processing. And the system can also count the task execution condition in the shared task pool and display a statistical result on a shared portal page. In conclusion, the complexity and the operation and maintenance cost of system configuration can be reduced, and the efficiency and the accuracy of task allocation can be improved.

Description

Technical Field

[0001] The present application relates to the field of process processing, and in particular to a method, device, storage medium and server for managing a document process. Background Art

[0002] With the acceleration of economic globalization and the deepening of corporate internationalization, coupled with the vigorous development of information technology, large corporate groups are facing the dual challenges of economic pressure and intensified market competition, and have chosen to build financial shared service centers as a response. This initiative aims to significantly reduce operating costs and significantly improve work efficiency by eliminating redundant work processes and promoting work process standardization.

[0003] The application of financial shared centers has become a standard for many large enterprises and multinational companies to optimize resource allocation and enhance competitiveness. However, with the continuous expansion and changes in the business of group enterprises, the challenges faced by financial shared centers in the business pooling process have become increasingly prominent. Especially in the initialization stage of sharing, the configuration work of task pooling is particularly heavy and complicated. Summary of the invention

[0004] The embodiments of the present application provide a document flow management method, device, storage medium and server, which can solve the problem of heavy and complex shared task management in the document flow in the prior art. The technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a method for managing a document flow, the method comprising:

[0006] Set the shared organization attribute information and shared center attribute information through the shared organization interface;

[0007] Set the pooling configuration through the shared pool setting interface, which includes: specifying the service unit, specifying the source system, specifying the sharing role and specifying the business type;

[0008] When detecting a document instance submitted by a user and a document process initiated for the document instance, determining that the document process includes multiple process links;

[0009] When the execution status of a process link is monitored to be in execution, the task attribute information of the process link is obtained, and the task attribute information includes: service unit, source system, job role and business type;

[0010] Checking whether the process link complies with the pool entry configuration according to the task attribute information;

[0011] If yes, query the corresponding sharing center according to the sharing center attribute information and the sharing organization attribute information, and add the process link as a sharing task to the sharing task pool of the sharing center;

[0012] If not, push the process link to the user corresponding to the position role for processing;

[0013] Statistics are collected on the execution status of each shared task in the shared task pool, and the statistical information is displayed on the shared portal page.

[0014] In a second aspect, an embodiment of the present application provides a document flow management device, the device comprising:

[0015] A setting unit, used to set shared organization attribute information and shared center attribute information through a shared organization interface;

[0016] The setting unit is further used to set the pool entry configuration through the shared pool setting interface, and the pool entry configuration includes: specifying a service unit, specifying a source system, specifying a shared role, and specifying a business type;

[0017] A determination unit, configured to, when detecting a document instance submitted by a user and a document process initiated for the document instance, determine that the document process includes multiple process links;

[0018] The monitoring unit is used to obtain task attribute information of a process link when the execution status of a process link is detected to be in execution, wherein the task attribute information includes: service unit, source system, job role and business type;

[0019] A checking unit, used for checking whether the process link complies with the pool entry configuration according to the task attribute information;

[0020] an adding unit, configured to, if yes, query the corresponding sharing center according to the sharing center attribute information and the sharing organization attribute information, and add the process link as a sharing task to the sharing task pool of the sharing center;

[0021] A push unit, for pushing the process link to the user corresponding to the position role for processing if the answer is no;

[0022] The statistical unit is used to collect statistics on the execution status of each shared task in the shared task pool and display the statistical information on the shared portal page.

[0023] In a third aspect, an embodiment of the present application provides a computer storage medium, wherein the computer storage medium stores a plurality of instructions, wherein the instructions are suitable for being loaded by a processor and executing the above-mentioned method steps.

[0024] In a fourth aspect, an embodiment of the present application provides a server, which may include: a processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the above-mentioned method steps.

[0025] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:

[0026] By setting up the shared organization interface and the shared pool setting interface, the flexible configuration of organization attributes and shared center attributes, as well as the customization of pool configuration (including service units, source systems, shared roles and business types) are realized. This enables document process links that meet specific conditions to be automatically identified and added to the shared task pool, and processed by a dedicated shared center, thereby reducing the flow time of tasks between different positions and roles and improving the efficiency of overall business processing. It can automatically monitor the execution status of the document process, and match the task attribute information with the pool configuration, and allocate the qualified process links to the corresponding shared center. This automated resource allocation mechanism avoids the tedious task accumulation and manual intervention, so that resources can be used more reasonably and efficiently. By collecting statistics on the execution status of each shared task in the shared task pool and displaying the statistical information on the shared portal page, relevant personnel can understand the processing progress and status of the task in real time. This transparent management method helps to discover and solve potential problems in a timely manner and improve the reliability and controllability of business processing. Through the setting of the shared center and shared task pool, cross-organizational and cross-system business collaboration is achieved. Tasks from different service units, source systems, and job roles can be managed and processed in a unified manner, breaking down barriers and restrictions in traditional business processing and promoting information sharing and collaboration between organizations. The solution can automatically process document flow links that meet the pooling configuration, reducing users' manual operations and waiting time. At the same time, through the statistical information display on the shared portal page, users can more easily understand the processing status of tasks, improving user satisfaction and experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0028] Figure 1 It is a schematic diagram of the network architecture provided by the embodiment of the present application;

[0029] Figure 2 It is a flowchart of a method for managing a document flow provided in an embodiment of the present application;

[0030] Figure 3 It is a schematic diagram of the document flow and document example provided in the embodiment of the present application;

[0031] Figure 4 is a schematic diagram of a shared organization setting interface provided in an embodiment of the present application;

[0032] Figure 5 is a schematic diagram of a sharing center maintenance window provided in an embodiment of the present application;

[0033] Figure 6 It is a schematic diagram of a source system setting sub-interface in a shared pooling interface provided in an embodiment of the present application;

[0034] Figure 7 is a schematic diagram of a service type setting sub-interface provided in an embodiment of the present application;

[0035] Figure 8 It is a schematic diagram of a service pooling setting sub-interface provided in an embodiment of the present application;

[0036] Fig. 9 is a schematic diagram of a shared portal page provided in an embodiment of the present application;

[0037] Fig.10 It is a structural diagram of a document flow management device provided by the present application;

[0038] Fig.11 It is a structural diagram of a server provided by this application. DETAILED DESCRIPTION

[0039] In order to make the objectives, technical solutions and advantages of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings.

[0040] It should be noted that the document flow management method provided in the present application is generally executed by a terminal device, and correspondingly, the document flow management device is generally set in a server.

[0041] Figure 1 An exemplary system architecture that can be applied to the document flow management method or document flow management device of the present application is shown.

[0042] like Figure 1As shown, the system architecture may include: a terminal device 101 and a server 102. The terminal device 101 and the server 102 may communicate via a network, and the network is used as a medium for providing communication links between the above-mentioned units. The network may include various types of wired communication links or wireless communication links, for example: a wired communication link includes an optical fiber, a twisted pair or a coaxial cable, etc., and a wireless communication link includes a Bluetooth communication link, a wireless fidelity (WIreless-FIdelity, Wi-Fi) communication link or a microwave communication link, etc.

[0043] It should be noted that the terminal device 101 and the server 102 can be hardware or software. When the terminal device 101 and the server 102 are hardware, they can be implemented as a distributed server cluster consisting of multiple servers, or as a single server. When the terminal device 101 and the server 102 are software, they can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module, which is not specifically limited here.

[0044] Various communication client applications can be installed on the terminal device of the present application, such as: video recording applications, video playback applications, voice interaction applications, search applications, instant messaging tools, email clients, social platform software, etc.

[0045] The terminal device can be hardware or software. When the terminal device is hardware, it can be various terminal devices with a display screen, including but not limited to smart phones, tablet computers, laptops, and desktop computers. When the terminal device is software, it can be installed in the terminal devices listed above. It can be implemented as multiple software or software modules (for example: used to provide distributed services), or it can be implemented as a single software or software module, which is not specifically limited here.

[0046] When the terminal device is hardware, a display device and a camera may be installed thereon. The display device may be any device capable of realizing a display function, and the camera is used to collect video streams; for example, the display device may be a cathode ray tube display (CR), a light-emitting diode display (LED), an electronic ink screen, a liquid crystal display (LCD), a plasma display panel (PDP), etc. The user may use the display device on the terminal device to view displayed text, pictures, videos and other information.

[0047] It should be understood that Figure 1The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be used as required.

[0048] The following will be combined with the attached Figure 2 , the document flow management method provided by the embodiment of the present application is described in detail. Among them, the document flow management device in the embodiment of the present application can be Figure 1 The server shown.

[0049] See also Figure 2 , which is a flow chart of a method for managing a document flow in an embodiment of the present application. Figure 2 As shown, the method of the embodiment of the present application may include the following steps:

[0050] S201. Set shared organization attribute information and shared center attribute information through a shared organization interface.

[0051] The server provides a shared organization interface for system administrators or users with relevant permissions to configure. Users can enter or select the following shared organization attribute information through this interface:

[0052] Sharing organization name: used to identify and distinguish different sharing organizations.

[0053] Sharing organization number: serves as the unique identifier of the sharing organization and is used for management and reference within the system.

[0054] At the same time, users also need to set the following sharing center attribute information:

[0055] Sharing center name: used to identify and distinguish different sharing centers.

[0056] Sharing Center Alias: Provide a more understandable and memorable alias for the sharing center (optional).

[0057] Service address: Specify the service address of the sharing center, including the IP address and port number, for network communication.

[0058] Whether it is a tenant mode: Indicates whether the sharing center adopts a multi-tenant mode, that is, whether it supports multiple independent users or organizations to share the same set of infrastructure and services.

[0059] Whether it is a virtual sharing center: Indicates whether the sharing center is virtualized, that is, whether dynamic allocation and management of resources are achieved through virtualization technology.

[0060] Sharing center status: indicates the current operating status of the sharing center, such as normal, maintenance, fault, etc.

[0061] Creation Unit: records the unit or organization that created the sharing center.

[0062] The server receives and stores this information, providing basic data support for subsequent business processing.

[0063] In some embodiments of the present application, see Figure 4 The schematic diagram of the shared organization setting interface shown, the server displays the shared organization setting interface;

[0064] Set the shared organization attribute information on the shared organization setting interface, and pop up the sharing center maintenance window by controlling the controls on the shared organization setting interface; the shared organization attribute information includes: shared organization number and shared organization name;

[0065] In the sharing center maintenance window, set the sharing center attribute information, including: sharing center name, sharing center alias, service address, whether it is a tenant mode, whether it is a virtual sharing center, sharing center status and creation unit.

[0066] The shared organization setting interface is divided into the basic organization setting area on the left and the shared organization setting area on the right. Users can set up multiple shared organizations for a specified unit in the shared organization setting area, and maintain the hierarchical relationship of shared organizations. The shared organization setting interface is equipped with a "View shared center attribute information" control. Users can trigger the control to pop up a Figure 5 The shared center maintenance window shown in the figure includes a shared center detail table. Each data row in the shared center detail table corresponds to a shared center. The data row is used to store the following field values: serial number, shared center name, service address, tenant mode, virtual shared center, work center status, and creation unit. The field values ​​of the shared center name and shared center alias in the shared center detail table are in Figure 5 Read and write back in the shared organization settings area.

[0067] S202. Setting the pool entry configuration through the shared pool setting interface, the pool entry configuration includes: specifying a service unit, specifying a source system, specifying a shared role, and specifying a business type.

[0068] Among them, in the shared pool setting interface, the server also receives the pool entry configuration information entered by the user. These configuration information specifically include: Specify service units: determine which service units (such as subsidiaries, departments, etc.) need to include their document processes in the shared center for processing. Specify source systems: clarify which source system data or documents need to be processed by the shared center. Specify shared roles: set the job roles responsible for processing tasks in the shared center. Specify business types: clarify which types of business need to be included in the shared center for processing. The server stores these configuration information to provide a basis for judgment for subsequent document instance processing.

[0069] In some embodiments of the present application, see Figure 6 The schematic diagram of the shared pool setting interface shown in the figure, the server displays the shared pool setting interface; the shared pool setting interface has three tabs: the source system setting tab, the business type attribute setting tab and the business as usual setting tab;

[0070] When detecting a trigger action on the source system settings tab, the source system settings sub-interface is displayed;

[0071] Set the system name, system type, data center code, service address, system version number, and configuration data push address of the specified system through the source system settings sub-interface;

[0072] When a trigger action on the business type attribute setting tab is detected, the business type attribute setting sub-interface is displayed;

[0073] On the business attribute setting sub-interface, set the source system name, system type, business type name, business type name ID, function address and parameter information of the specified business type;

[0074] When a trigger action is detected on the business pool setting tab, the business pool setting sub-interface is displayed;

[0075] Set the service unit, source system name, business type, and shared role through the business pool setting sub-interface.

[0076] Among them, the task of entering the sharing center may come from the internal system (the same data center) or from the external system. Therefore, a place is needed to maintain system information, enter and save the information of the business system, so as to facilitate the reference of the subsequent business pool setting function and the pool configuration data to be pushed to the business system. The source system setting sub-interface includes a source system detail table, which retains the relevant attributes of the specified source system. Each data row corresponds to a system, and the data row is used to store the field values ​​of the system name, system type, data center code, service address, system version number, and configuration data push address. Above the source system detail table, there are also save controls, add controls, delete controls, deactivate controls, restore controls, and test link controls. The save control is used to save the data in the source system detail table based on the user's trigger operation, the add control is used to add a data row in the source system detail table based on the user's trigger operation, the deactivate control is used to set a data row in the source system detail table to an invalid state, the restore state is used to restore a data row in the source system detail table from an invalid state to a valid state, and the test link control is used to test whether the server corresponding to the service address and the configuration data push address is normal.

[0077] See also Figure 7The schematic diagram of the business type setting sub-interface shown in the figure includes: a business type detail table, each data row in the business type detail table corresponds to a specified business type, and the data row is used to store the serial number, the field value of the source system name, the field value of the system type, the field value of the business type name, the field value of the business type name ID, the field value of the function address, and the field value of the parameter information. Furthermore, a save control, a new control, a delete control, a deactivate control, and a restore control are also provided above the business type detail table. The save control is used to save the data in the business type detail table, the new control is used to add a data row in the business type detail table, the delete control is used to delete a data row in the business type detail table, the deactivate control is used to set a data row in the business type detail table to an invalid state, and the restore control is used to set a data row in the business type detail table from an invalid state to a valid state.

[0078] See also Figure 8 The schematic diagram of the business pooling sub-interface shown in the figure, the business pooling sub-page includes a pooling configuration detail table representing the pooling configuration, each data row in the pooling configuration detail table corresponds to a pooling configuration, that is, multiple pooling configurations can be set, and the data row is used to store the field value of the service unit, the field value of the source system name, the field value of the business type, and the field value of the shared role. The top of the pooling configuration detail table is also provided with a save control, a new control, a delete control, and a service unit level setting control. The new control is used to add a data row in the pooling configuration detail table, and the delete control is used to delete a data row in the pooling configuration detail table. The service unit level setting is used to set the hierarchical relationship between multiple service units when the number of field values ​​of the service unit is multiple. Furthermore, the bottom of the pooling configuration detail table is also provided with a service unit display area, a business type display area, and a shared role display area, which are used to display the field value of the service unit, the field value of the business type, and the field value of the shared role of the selected data row when a data row in the pooling configuration detail table is selected.

[0079] S203: When a document instance submitted by a user and a document process initiated for the document instance are detected, it is determined that the document process includes multiple process links.

[0080] The server continuously monitors document instances submitted by users in the system, such as purchase orders, sales contracts, etc., and identifies the document processes related to them. Document processes usually include multiple process links, such as approval, review, and execution. The server determines the specific links and order of each document process by parsing the document instance and its associated process definition.

[0081] In the embodiment of the present application, the server, as the execution subject, is responsible for creating and managing new document models. The document model is the basis for defining the structure and attributes of the document, which specifies which fields can be included in the document, the type of the field, whether it is required, and other information. The server creates a new document model by receiving input from the system administrator or a user with corresponding authority, and stores it in the database. These document models provide a basic framework for subsequent document instance generation and process management. The server generates a document instance using a predefined document model based on the information filled in by the user. The document instance is the concretization of the document model, which contains the specific data filled in by the user. The server stores these document instances in the database in the form of an entity table to ensure the persistence and queryability of the data. When the user submits the document instance, the server selects one (or more, according to the business rules) document process from the associated document process to initiate. Initiating a document process means that the server begins to monitor the execution status of the process and triggers corresponding operations according to the rules in the process definition.

[0082] For example, see Figure 3 Schematic diagram of the document flow and document instance shown.

[0083] The user creates a new document model, and the application and interaction logic of the document encapsulated by the program include defining the data structure (the fields and attributes contained in the document model, defining the type and length of the field, etc.), setting default values, etc. For example, the document model of "expense reimbursement form" includes: document number, person in charge, handling department, start date, end date, reimbursement items, reimbursement amount and other field information;

[0084] The document instance references the document model, creates an entity table in the database, generates a document instance, and stores specific business data. When using the "Expense Reimbursement Form" model to create a specific document entity table, an entity table will be created in the database to store the actual business data, for example: the document instance generated when the user raises the bill, expense reimbursement form 001 (specific document), person in charge: Zhang San, department in charge: Product R&D Department, start date: October 1, 2024, end date: October 7, 2024, reimbursement item: expense reimbursement, reimbursement amount: 1800.00, business trip reason: business trip to Guangzhou, base location: Zhuhai, business trip location: Guangzhou, transportation method: high-speed rail, and other information.

[0085] according to Figure 3 It can be seen that there is a close connection between the document model and the document instance. The relationship between the document model and the document instance can be one-to-one or one-to-many. The document model provides the structure and definition for the document instance, while the document instance is the specific implementation and embodiment of the document model.

[0086] A document instance is a specific embodiment of a document process. Each document instance corresponds to one or more document processes. For example, in an expense reimbursement document instance, a travel reimbursement form corresponds to a travel expense reimbursement process, welfare expenses correspond to a welfare reimbursement process, and employee car reimbursement corresponds to an employee car business reimbursement process. Each document process has multiple process links. Figure 3 Taking the travel reimbursement process as an example, the process has a total of 8 steps: initiation by the person in charge, review by the department leader, review by the leader in charge, preliminary financial review, financial review, voucher issuance, voucher review and fund payment.

[0087] S204. When it is monitored that the execution status of a certain process link is in execution, the task attribute information of the process link is obtained. The task attribute information includes: service unit, source system, job role and business type.

[0088] When the server detects that a process link has entered the execution state, it will automatically obtain the task attribute information of the link. This information includes but is not limited to the service unit (the organization responsible for executing the link), the source system (the system that generates the document instance), the position role (the user role responsible for processing the link) and the business type (such as procurement, sales, etc.). The server obtains this information by querying the database or calling the relevant interface to provide a basis for subsequent judgment and processing.

[0089] S205. Check whether the process link complies with the pool entry configuration according to the task attribute information.

[0090] The server compares the acquired task attribute information one by one according to the pooling configuration set in step S202. This includes checking whether the service unit, source system, job role and business type match the specified conditions in the pooling configuration. Through this step, the server can determine whether the current process link meets the conditions for being added to the shared task pool.

[0091] S206: If yes, query the corresponding sharing center according to the sharing center attribute information and the sharing organization attribute information, and add the process link as a shared task to the shared task pool of the sharing center.

[0092] Among them, if the server determines that the current process link meets the pool configuration, it will query the corresponding sharing center according to the sharing center attribute information and the shared organization attribute information. Then, the process link is added to the shared task pool of the sharing center as a shared task. The shared task pool is a dynamically updated task queue used to store shared tasks waiting to be processed. The server ensures that the allocation and scheduling of tasks in the pool follow certain priorities and load balancing strategies to improve processing efficiency and resource utilization.

[0093] S207: If not, push the process link to the user corresponding to the job role for processing.

[0094] If the server determines that the current process link does not meet the pool configuration, it will push the process link to the corresponding user for processing based on the job role information in the task attribute information. This usually means that the process link needs to be manually executed or approved by users with specific roles. The server ensures that users can receive tasks in a timely manner and take corresponding actions through message notifications, email reminders, etc.

[0095] S208: Count the execution status of each shared task in the shared task pool, and display the statistical information on the shared portal page.

[0096] Among them, after the shared tasks are assigned to the sharing center and start to be executed, the server will continue to monitor the execution of these shared tasks. Including but not limited to: Task status: monitor whether the task is being executed, completed, paused, canceled, etc. Task progress: For ongoing tasks, monitor its completion percentage or progress bar. Task duration: record the time required for the task from start to completion. Task results: record the results of task execution, such as success, failure, exception, etc., and may include detailed error logs or success information. Task priority: If the system supports task priority management, it is also necessary to monitor the priority information of the task.

[0097] The server will collect and organize these statistics regularly or in real time, and generate corresponding statistical reports or charts. Then, the server will display these statistics to relevant personnel, such as the administrator of the sharing center, the task executor or the business manager, through the sharing portal page.

[0098] The shared portal page is a user interface that allows relevant personnel to view the execution of shared tasks, analyze task processing efficiency, identify potential problems or bottlenecks, and make corresponding decisions or adjustments accordingly. Through the shared portal page, relevant personnel can grasp the working status of the shared center in real time to ensure the smooth progress of the document process.

[0099] For example, see Fig. 9The schematic diagram of the shared portal page shown in the figure, the shared portal page includes a shared task list, each data row in the shared task list corresponds to a shared task in the shared task pool, and the data row is used to store the field value of the sequence number, the field value of the voucher number, the field value of the document number, the field value of the work item, the resource value of the document type, the field value of the form filling date, the field value of the reporting unit, the field value of the person in charge, the field value of the amount, the field value of the summary, and the field value of the time of entering the pool. A refresh control, a batch approval control, a return task pool control, a suspend task control, and a receive task control are also provided above the shared task list. The refresh control is used to periodically update the shared task list according to the shared tasks in the shared task pool, the batch approval control is used to batch approve the selected data rows in the shared task list, the return task pool is used to return the shared tasks corresponding to the selected data rows in the shared task list to the shared task output, the suspend task is used to suspend the execution of the shared tasks corresponding to the selected data rows in the shared task list, and the domain task is used to dispatch the shared tasks corresponding to the data rows selected by the user in the shared task list to the user. Furthermore, statistical controls are provided above the shared task details table, which are used to count the shared task pool's pending tasks, daily processing volume, monthly processing volume, ranking within the processing group, daily expectations and other statistical information.

[0100] The present application specifically includes the following beneficial effects:

[0101] In the prior art, the process links are usually directly associated with the shared center to achieve the allocation of tasks to the shared task pool. However, when dealing with complex business processes, this method often requires a lot of time and energy to configure due to the large number of process links involved, and the effect is often unsatisfactory.

[0102] This application starts from the upper layer of the process - the document model, and optimizes task allocation by building a corresponding relationship between the document model and the shared center. Specifically, this solution focuses on the corresponding common roles in the process links, which usually have unified and standardized naming and management within the enterprise. Therefore, by maintaining the correspondence between roles and shared centers, the amount of data is greatly controlled and simplified compared to directly processing a large number of process links.

[0103] More importantly, after the application establishes the corresponding relationship at the upper layer, not only the amount of data is significantly reduced, but also the batch selection capability is available. This feature greatly reduces the complexity of system configuration and operation and maintenance costs. Enterprises can allocate and manage tasks more efficiently, thereby improving the automation and overall efficiency of business processes.

[0104] In summary, the technical solution of this application achieves effective improvement and optimization of the existing technology. It not only reduces the complexity of system configuration and operation and maintenance costs, but also improves the efficiency and accuracy of task allocation, providing strong technical support for enterprises to achieve intelligent management of business processes.

[0105] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.

[0106] See also Fig.10 , which shows a schematic diagram of the structure of a document flow management device provided by an exemplary embodiment of the present application, hereinafter referred to as device 10. The device 4 can be implemented as all or part of the server through software, hardware or a combination of both. The device 10 includes: a setting unit 1001, a determination unit 1002, a monitoring unit 1003, a checking unit 1004, an adding unit 1005, a pushing unit 1006 and a statistical unit 1007.

[0107] A setting unit 1001 is used to set the shared organization attribute information and the shared center attribute information through the shared organization interface;

[0108] The setting unit 1001 is further used to set the pool entry configuration through the shared pool setting interface, and the pool entry configuration includes: specifying a service unit, specifying a source system, specifying a shared role, and specifying a business type;

[0109] The determining unit 1002 is configured to, when detecting a document instance submitted by a user and a document process initiated for the document instance, determine that the document process includes multiple process links;

[0110] The monitoring unit 1003 is used to obtain task attribute information of a process link when the execution status of a process link is detected to be in execution, wherein the task attribute information includes: service unit, source system, job role and business type;

[0111] A checking unit 1004 is used to check whether the process link complies with the pool entry configuration according to the task attribute information;

[0112] Adding unit 1005, for, if yes, searching the corresponding sharing center according to the sharing center attribute information and the sharing organization attribute information, and adding the process link as a sharing task to the sharing task pool of the sharing center;

[0113] Push unit 1006, for pushing the process link to the user corresponding to the position role for processing if the answer is no;

[0114] The statistical unit 1007 is used to collect statistics on the execution status of each shared task in the shared task pool, and display the statistical information on the shared portal page.

[0115] In one or more possible embodiments, setting the shared organization attribute information and the shared center attribute information through the shared organization interface includes:

[0116] Display the shared organization settings interface;

[0117] Setting the shared organization attribute information on the shared organization setting interface, and popping up a sharing center maintenance window by controlling the controls on the shared organization setting interface; the shared organization attribute information includes: a shared organization number and a shared organization name;

[0118] The sharing center attribute information is set on the sharing center maintenance window, and the sharing center attribute information includes: sharing center name, sharing center alias, service address, whether tenant mode, whether virtual sharing center, sharing center status and creation unit.

[0119] In one or more possible embodiments, setting the pool configuration through the shared pool setting interface includes:

[0120] The shared pooling setting interface is displayed; the shared pooling setting interface has three tabs: a source system setting tab, a business type attribute setting tab, and a business as usual setting tab;

[0121] When detecting a trigger action on the source system setting tab, displaying a source system setting sub-interface;

[0122] Set the field values ​​of the system name, system type, data center code, service address, system version number, and configuration data push address of the specified system through the source system setting sub-interface;

[0123] When a triggering action on the service type attribute setting tab is detected, a service type attribute setting sub-interface is displayed;

[0124] On the business attribute setting sub-interface, set the field values ​​of the source system name, system type, business type name, business type name ID, function address and parameter information of the specified business type;

[0125] When a trigger action is detected on the business pool setting tab, the business pool setting sub-interface is displayed;

[0126] The field values ​​of service unit, source system name, business type, and shared role are set through the business pool setting sub-interface.

[0127] In one or more possible embodiments, the business pool entry sub-page of the pool entry setting sub-interface includes a pool entry configuration detail table representing the pool entry configuration, a service unit display area, a business type display area, and a shared role display area; each data row in the pool entry configuration detail table corresponds to a pool entry configuration, and the data row is used to store the field value of the service unit, the field value of the source system name, the field value of the business type, and the field value of the shared role;

[0128] When a data row in the pool configuration details table is selected, the field values ​​of the service unit, the field values ​​of the business type and the field values ​​of the shared role of the selected data row are displayed in the service unit display area, the business type display area and the shared role display area respectively.

[0129] In one or more possible embodiments, the shared portal interface includes a shared task details table, each data row of the shared task details table corresponds to a shared task in the shared task pool, and the data row is used to store field values ​​of serial number, document number, work item, document type, filling date, filling unit, handler, amount, summary and pool entry time; the statistical information includes: the number to be assigned, the number processed per day, the number processed that month, the ranking within the processing group and the number overdue on that day.

[0130] In one or more possible embodiments, a refresh control, a batch review control, a return to task pool control, a suspend task control, and a receive task control are provided on the shared portal page.

[0131] In one or more possible embodiments, it further includes:

[0132] Initiating unit, used to create a new document model;

[0133] Generate document instances using the document model, and store the filled-in document instances in the database in the form of entity tables;

[0134] Associate the document instance with at least one document process;

[0135] A document flow is selected from the at least one document flow, and the selected document flow is initiated according to the document entity submitted by the user.

[0136] It should be noted that the device 10 provided in the above embodiment only uses the division of the above functional modules as an example when executing the document flow management method. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the above functions. In addition, the document flow management device provided in the above embodiment and the document flow management method embodiment belong to the same concept, and the implementation process thereof is detailed in the method embodiment, which will not be repeated here.

[0137] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0138] The present application also provides a computer storage medium, which can store multiple instructions, and the instructions are suitable for being loaded and executed by a processor as described above. Figure 2 The method steps of the embodiment shown in the figure can be found in the specific implementation process. Figure 2 The specific description of the illustrated embodiment will not be repeated here.

[0139] The present application also provides a computer program product, which stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the document flow management method described in the above embodiments.

[0140] See also Fig.11 , which is a schematic diagram of the structure of a server provided in the embodiment of the present application. Fig.11 As shown, the server 1100 may include: at least one processor 1101 , at least one network interface 1104 , a user interface 1103 , a memory 1105 , and at least one communication bus 1102 .

[0141] The communication bus 1102 is used to realize the connection and communication between these components.

[0142] The user interface 1103 may include a display screen (Display) and a camera (Camera), and the optional user interface 1103 may also include a standard wired interface and a wireless interface.

[0143] The network interface 1104 may optionally include a standard wired interface or a wireless interface (such as a WI-FI interface).

[0144] Among them, the processor 1101 may include one or more processing cores. The processor 1101 uses various interfaces and lines to connect the various parts of the entire server 1100, and executes various functions and processes data of the server 1100 by running or executing instructions, programs, code sets or instruction sets stored in the memory 1105, and calling data stored in the memory 1105. Optionally, the processor 1101 can be implemented in at least one hardware form of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), and programmable logic array (Programmable Logic Array, PLA). The processor 1101 can integrate one or more combinations of a central processing unit (Central Processing Unit, CPU), a graphics processing unit (Graphics Processing Unit, GPU) and a modem. Among them, the CPU mainly processes the operating system, user interface and application programs; the GPU is responsible for rendering and drawing the content to be displayed on the display screen; and the modem is used to process wireless communications. It can be understood that the above-mentioned modem may not be integrated into the processor 1101, and it can be implemented separately through a chip.

[0145] Among them, the memory 1105 may include a random access memory (Random Access Memory, RAM) and may also include a read-only memory (Read-Only Memory). Optionally, the memory 1105 includes a non-transitory computer-readable storage medium. The memory 1105 can be used to store instructions, programs, codes, code sets or instruction sets. The memory 1105 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playback function, an image playback function, etc.), instructions for implementing the above-mentioned various method embodiments, etc.; the data storage area may store data involved in the above-mentioned various method embodiments, etc. The memory 1105 may also be optionally at least one storage device located away from the aforementioned processor 1101. As Fig.11 As shown, the memory 1105 as a computer storage medium may include an operating system, a network communication module, a user interface module and an application program.

[0146] exist Fig.11In the server 1100 shown in FIG. 1 , the user interface 1103 is mainly used to provide an input interface for the user and obtain the data input by the user; and the processor 1101 can be used to call the application stored in the memory 1105 and specifically execute the following steps: Figure 2 The specific process can be referred to Figure 2 As shown, no further description is given here.

[0147] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium, and when the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium can be a disk, an optical disk, a read-only storage memory, or a random access memory, etc.

[0148] The above disclosure is only the preferred embodiment of the present application, which certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A document flow management method, characterized in that: include: Set the shared organization attribute information and shared center attribute information through the shared organization interface; Set the pooling configuration through the shared pool setting interface, which includes: specifying the service unit, specifying the source system, specifying the sharing role and specifying the business type; When detecting a document instance submitted by a user and a document process initiated for the document instance, determining that the document process includes multiple process links; When the execution status of a process link is monitored to be in execution, the task attribute information of the process link is obtained, and the task attribute information includes: service unit, source system, job role and business type; Checking whether the process link complies with the pool entry configuration according to the task attribute information; If yes, query the corresponding sharing center according to the sharing center attribute information and the sharing organization attribute information, and add the process link as a sharing task to the sharing task pool of the sharing center; If not, push the process link to the user corresponding to the position role for processing; Statistics are collected on the execution status of each shared task in the shared task pool, and the statistical information is displayed on the shared portal page.

2. The method according to claim 1, characterized in that: The setting of shared organization attribute information and shared center attribute information through the shared organization interface includes: Display the shared organization settings interface; Setting the shared organization attribute information on the shared organization setting interface, and popping up a sharing center maintenance window by controlling the controls on the shared organization setting interface; the shared organization attribute information includes: a shared organization number and a shared organization name; The sharing center attribute information is set on the sharing center maintenance window, and the sharing center attribute information includes: sharing center name, sharing center alias, service address, whether tenant mode, whether virtual sharing center, sharing center status and creation unit.

3. The method according to claim 1 or 2, characterized in that: The pool configuration is set through the shared pool setting interface, including: The shared pooling setting interface is displayed; the shared pooling setting interface has three tabs: a source system setting tab, a business type attribute setting tab, and a business as usual setting tab; When detecting a trigger action on the source system setting tab, displaying a source system setting sub-interface; Set the field values ​​of the system name, system type, data center code, service address, system version number, and configuration data push address of the specified system through the source system setting sub-interface; When a triggering action on the service type attribute setting tab is detected, a service type attribute setting sub-interface is displayed; On the business attribute setting sub-interface, set the field values ​​of the source system name, system type, business type name, business type name ID, function address and parameter information of the specified business type; When a trigger action is detected on the business pool setting tab, the business pool setting sub-interface is displayed; The field values ​​of service unit, source system name, business type, and shared role are set through the business pool setting sub-interface.

4. The method according to claim 3, characterized in that The business pool entry subpage of the pool entry setting sub-interface includes a pool entry configuration detail table representing the pool entry configuration, a service unit display area, a business type display area, and a shared role display area; each data row in the pool entry configuration detail table corresponds to a pool entry configuration, and the data row is used to store the field value of the service unit, the field value of the source system name, the field value of the business type, and the field value of the shared role; When a data row in the pool configuration details table is selected, the field values ​​of the service unit, the field values ​​of the business type and the field values ​​of the shared role of the selected data row are displayed in the service unit display area, the business type display area and the shared role display area respectively.

5. The method according to claim 4, characterized in that The shared portal interface includes a shared task details table, each data row of the shared task details table corresponds to a shared task in the shared task pool, and the data row is used to store the field values ​​of serial number, document number, work item, document type, filling date, filling unit, person in charge, amount, summary and pool entry time; the statistical information includes: the number to be assigned, the number processed per day, the number processed that month, the ranking within the processing group and the number overdue on that day.

6. The method according to claim 1 or 2 or 4 or 5, characterized in that: The shared portal page is provided with a refresh control, a batch review control, a return task pool control, a suspend task control and a receive task control.

7. The method according to claim 6, characterized in that Also includes: Create a new document model; Generate document instances using the document model, and store the filled-in document instances in the database in the form of entity tables; Associate the document instance with at least one document process; A document flow is selected from the at least one document flow, and the selected document flow is initiated according to the document entity submitted by the user.

8. A document flow management device, characterized in that: include: A setting unit, used to set shared organization attribute information and shared center attribute information through a shared organization interface; The setting unit is further used to set the pool entry configuration through the shared pool setting interface, and the pool entry configuration includes: specifying a service unit, specifying a source system, specifying a shared role, and specifying a business type; A determination unit, configured to, when detecting a document instance submitted by a user and a document process initiated for the document instance, determine that the document process includes multiple process links; The monitoring unit is used to obtain task attribute information of a process link when the execution status of a process link is detected to be in execution, wherein the task attribute information includes: service unit, source system, job role and business type; A checking unit, used for checking whether the process link complies with the pool entry configuration according to the task attribute information; an adding unit, configured to, if yes, query the corresponding sharing center according to the sharing center attribute information and the sharing organization attribute information, and add the process link as a sharing task to the sharing task pool of the sharing center; A push unit, for pushing the process link to the user corresponding to the position role for processing if the answer is no; The statistical unit is used to collect statistics on the execution status of each shared task in the shared task pool and display the statistical information on the shared portal page.

9. A computer storage medium, characterized in that: The computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the method steps according to any one of claims 1 to 7.

10. A server, characterized in that: include: A processor and a memory; wherein the memory stores a computer program, and the computer program is suitable for being loaded by the processor and executing the method steps as claimed in any one of claims 1 to 7.

Images