Document flow management method and device, storage medium and server

Abstract

The embodiment of the application discloses a kind of management methods, devices, storage medium and server of bill flow, involve process processing field.The application is related to the attribute information of sharing organization and sharing center interface setting, while in the pool interface configuration pool rule.When detecting the bill instance submitted by user and its flow, the process chain containing multiple links will be identified.In the process execution, the task attribute of current link will be captured.If the link meets the pool condition, the link will be added as shared task to the task pool of corresponding sharing center according to the attribute information of sharing center and organization;If not, it will be directly pushed to the user corresponding to post role for processing.The system will also count the execution of task in shared task pool, and show the statistical result on the sharing portal page.In summary, the application not only can reduce the complexity and operation and maintenance cost of system configuration, but also can improve the efficiency and accuracy of task allocation.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of process processing, in particular to a management method and device of a bill process, a storage medium and a server. BACKGROUND

[0002] With the acceleration of economic globalization and the deepening of enterprise internationalization, combined with the vigorous development of information technology, large enterprise groups have chosen to build a financial shared service center as a countermeasure in the face of the dual challenges of economic pressure and market competition. The purpose of this move is to eliminate redundant work processes and promote standardization of work processes, thereby achieving significant reduction in operating costs and significant improvement in work efficiency.

[0003] The application of the financial shared center has become a standard for many large enterprises and multinational companies to optimize resource allocation and improve competitiveness. However, as the business of the group enterprise continues to expand and change, the challenges faced by the financial shared center in the business entry process have become increasingly prominent. In particular, during the shared initialization phase, the configuration of task entry is particularly heavy and complex. SUMMARY

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

[0005] In a first aspect, the embodiments of the present application provide a management method of a bill process, which comprises:

[0006] setting shared organization attribute information and shared center attribute information through a shared organization interface;

[0007] setting an entry configuration through a shared pool setting interface, the entry configuration including: a specified service unit, a specified source system, a specified shared role and a specified business type;

[0008] When a bill instance submitted by a user and a bill process initiated for the bill instance are detected, it is determined that the bill process includes a plurality of process links;

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

[0010] According to the task attribute information, it is checked whether the process link meets the entry configuration;

[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 shared task to the shared task pool of the sharing center;

[0012] If not, push the process link to the user corresponding to the job 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 a 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 sharing role, and specifying a business type;

[0017] a determining unit configured to, upon 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 configured to obtain task attribute information of a process link when detecting that the execution status of the process link is in execution, wherein the task attribute information includes: service unit, source system, job role, and business type;

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

[0020] an adding unit, configured to, if the answer is 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 is used to push the process link to the user corresponding to the job 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 can include a processor and a memory; wherein the memory stores a computer program, and the computer program is adapted to be loaded by the processor and execute the method steps described above.

[0025] The technical solutions provided by some embodiments of the present application have at least the following beneficial effects:

[0026] By setting the shared organization interface and the shared pool setting interface, flexible configuration of organization attributes and shared center attributes, as well as customization of pool entry configuration (including service units, source systems, shared roles, and business types) is achieved. This enables document process links that meet specific conditions to be automatically identified and added to the shared task pool for processing by a dedicated shared center, thereby reducing the flow time of tasks between different post roles and improving the efficiency of overall business processing. The execution status of the document process can be automatically monitored, and the process links that meet the conditions can be assigned to the corresponding shared center according to the task attribute information and the pool entry configuration. This automated resource allocation mechanism avoids the tediousness of manual intervention and makes resources more reasonably and efficiently utilized. By statistically analyzing the execution of each shared task in the shared task pool and displaying the statistical information on the shared portal page, relevant personnel can real-time understand the processing progress and status of the tasks. This transparent management method helps to timely discover and solve potential problems, improving the reliability and controllability of business processing. Through the setting of the shared center and the shared task pool, cross-organizational and cross-system business collaboration is achieved. Tasks of different service units, source systems, and post roles can be uniformly managed and processed, breaking down the barriers and limitations in traditional business processing and promoting inter-organizational information sharing and collaboration. The scheme can automatically process document process links that meet the pool entry configuration, reducing manual operation and waiting time for users. At the same time, through the display of statistical information on the shared portal page, users can more conveniently understand the processing of tasks, improving user satisfaction and experience. BRIEF DESCRIPTION OF DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor based on these drawings.

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

[0029] Figure 2 is a flowchart of a document process management method provided by an embodiment of the present application;

[0030] Figure 3 This is a schematic diagram of the document process and document examples provided in the embodiments 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 shared center maintenance window provided in an embodiment of the present application;

[0033] Figure 6 Schematic diagram of the source system setting sub-interface in the shared pool interface provided in an embodiment of the present application;

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

[0035] Figure 8 Schematic diagram of the service pool setting sub-interface provided in an embodiment of the present application;

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

[0037] Figure 10 This is a structural diagram of a document flow management device provided by this application;

[0038] Figure 11 This 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 clearer, the embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

[0040] It should be noted that the document process management method provided in this application is generally executed by a terminal device, and accordingly, the document process management device is generally set in the 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, which 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: wired communication links include optical fibers, twisted pairs, or coaxial cables, and wireless communication links include Bluetooth communication links, wireless fidelity (Wi-Fi) communication links, or microwave communication links.

[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, without specific limitation herein.

[0044] Various communication client applications can be installed on the terminal device of this 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 either hardware or software. When the terminal device is hardware, it can be various terminal devices with a display screen, including but not limited to smartphones, tablet computers, laptop computers, 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, 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, it may also be equipped with a display device and a camera. The display device can be any device capable of displaying a video, and the camera is used to capture 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), or a plasma display panel (PDP). Users can use the display device on the terminal device to view displayed text, images, videos, and other information.

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

[0048] The following will be combined with the 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 Figure 2 , provides a flow chart of a document flow management method for 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 property information of the sharing center:

[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 shared center: Indicates whether the shared 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 this application, see Figure 4 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 settings interface, and use the controls on the shared organization settings interface to pop up the sharing center maintenance window; 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 Sharing Center Property Information" control. Users can trigger the control to pop up the 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 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. Set 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: Specifying service units: Determining which service units (such as subsidiaries, departments, etc.) need to include their document processes in the shared center for processing. Specifying source systems: Clarifying which source systems' data or documents need to be processed by the shared center. Specifying shared roles: Setting the job roles responsible for processing tasks in the shared center. Specifying business types: Clarifying which types of business need to be included in the shared center for processing. The server stores this configuration information to provide a basis for judgment for subsequent document instance processing.

[0069] In some embodiments of this application, see Figure 6 The shared pooling settings interface is shown in the figure. The server displays the shared pooling settings interface. The shared pooling settings interface has three tabs: the source system settings tab, the business type attribute settings tab, and the business as usual settings 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 Pooling Settings tab, the Business Pooling Settings 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] Tasks entering the shared center may originate from internal systems (within the same data center) or external systems. Therefore, a place is needed to maintain system information, enter and save business system information, and facilitate subsequent reference in business pooling setup functions and the push of pooling configuration data to business systems. The source system settings sub-screen includes a source system detail table, which stores the relevant attributes of a specified source system. Each data row corresponds to a system and stores field values ​​for system name, system type, data center code, service address, system version number, and configuration data push address. Above the source system detail table are controls for saving, adding, deleting, deactivating, restoring, and testing. The saving control saves data in the source system detail table based on user triggers. The adding control adds a new row to the source system detail table based on user triggers. The deactivating control invalidates a row in the source system detail table. The restoring state restores a row from invalid to valid. The test link is used to test the health of the servers corresponding to the service address and configuration data push address.

[0077] See also Figure 7The schematic diagram of the business type setting sub-interface shown is that the business type setting sub-interface includes: a business type detail table, each data row of 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 to 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 diagram shows a schematic diagram of the service pooling sub-interface. The service pooling sub-page includes a pooling configuration detail table that represents the pooling configuration. Each data row in the pooling configuration detail table corresponds to a pooling configuration, meaning that multiple pooling configurations can be set. The data rows are used to store the field values ​​for the service unit, the source system name, the service type, and the shared role. Above the pooling configuration detail table are controls for saving, adding, and deleting data, as well as controls for setting the service unit hierarchy. The add control is used to add a data row to the pooling configuration detail table, and the delete control is used to delete a data row from the pooling configuration detail table. The service unit hierarchy setting is used to set the hierarchical relationship between multiple service units if there are multiple service unit field values. Furthermore, below the pooling configuration detail table are areas for displaying service units, business types, and shared roles. When a data row in the pooling configuration detail table is selected, these areas display the selected data row's field values ​​for the service unit, business type, and shared role, respectively.

[0079] S203: When detecting the document instance submitted by the user and the document process initiated for the document instance, 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 and sales contracts, and identifies the associated document processes. Document processes typically include multiple steps, such as approval, review, and execution. The server parses document instances and their associated process definitions to determine the specific steps and sequence of each document process.

[0081] In an embodiment of the present application, the server acts as the execution entity, responsible for creating and managing new document models. The document model is the basis for defining the structure and attributes of a document. It specifies information such as which fields can be included in a document, the type of fields, and whether they are required. The server creates new document models by receiving input from a system administrator or a user with corresponding permissions and stores them in a database. These document models provide the basic framework for subsequent document instance generation and process management. The server generates document instances using pre-defined document models based on the information entered by the user. The document instance is a concretization of the document model, containing the specific data entered by the user. The server stores these document instances in the database in the form of entity tables to ensure data persistence and queryability. When a user submits a document instance, the server selects one (or more, depending on business rules) document process from the associated document processes to initiate. Initiating a document process means that the server begins monitoring the execution status of the process and triggers corresponding operations based on the rules in the process definition.

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

[0083] Users create new document models, which encapsulate the application and interaction logic of the document through the program, including defining the data structure (the fields and attributes included in the document model, defining the field type and length, etc.), setting default values, etc. For example, the document model of "expense reimbursement form" includes: document number, handler, handling department, start date, end date, reimbursement item, reimbursement amount and other fields;

[0084] Document instances reference document models, establish entity tables in the database, generate document instances, and store specific business data. When creating a specific document entity table using the "Expense Reimbursement Form" model, an entity table is created in the database to store the actual business data. For example, the document instance generated when a user submits a bill of lading is Expense Reimbursement Form 001 (specific document), with the following information: Handled by: Zhang San, Handled by: 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 Destination: Guangzhou, Transportation Method: High-speed Rail, etc.

[0085] according to Figure 3 The close connection between document models and document instances can be seen. The relationship between document models and document instances 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 concrete manifestation 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 the travel expense reimbursement process, welfare expenses correspond to the welfare reimbursement process, and employee car reimbursement corresponds to the 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 step has entered the execution state, it automatically retrieves the task attribute information for that step. This information includes, but is not limited to, the service unit (the organization responsible for executing the step), the source system (the system that generates the document instance), the job role (the user role responsible for processing the step), and the business type (such as procurement, sales, etc.). The server obtains this information by querying the database or calling relevant interfaces, providing a basis for subsequent judgment and processing.

[0089] S205: Check whether the process link complies with the pool entry configuration based on the task attribute information.

[0090] The server then compares each acquired task attribute against the pooling configuration set in step S202. This includes checking whether the service provider, source system, job role, and business type match the specified pooling conditions. This allows the server to determine whether the current process link meets the requirements for inclusion in 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] If the server determines that the current process link meets the pooling configuration, it will query the corresponding shared center based on the shared center attribute information and shared organization attribute information. It will then add the process link as a shared task to the shared task pool of that shared center. The shared task pool is a dynamically updated task queue that stores shared tasks awaiting processing. The server ensures that the allocation and scheduling of tasks within the pool adhere to certain priorities and load balancing strategies to improve processing efficiency and resource utilization.

[0093] S207, if no, the process node is pushed to the user corresponding to the post role for processing.

[0094] If the server determines that the current process node does not meet the pool configuration, it will push the process node to the corresponding user for processing according to the post role information in the task attribute information. This usually means that the process node needs to be manually executed or approved by the user of a specific role. The server ensures that the user can receive the task in time and take appropriate action through message notification, email reminder, etc.

[0095] S208, statistics of the execution of each shared task in the shared task pool are counted, and the statistical information is displayed on the shared portal page.

[0096] Among them, after the shared task is assigned to the shared center and starts to execute, the server will continue to monitor the execution of these shared tasks. Including but not limited to: task status: monitoring whether the task is executing, completed, paused, canceled, etc. Task progress: for tasks in progress, monitor the percentage or progress bar of completion. Task time consumption: record the time required from the start to the completion of the task. Task result: record the results of task execution, such as success, failure, exception, etc., and may contain detailed error logs or success information. Task priority: if the system supports task priority management, the priority information of the task also needs to be monitored.

[0097] The server will collect and organize these statistical information regularly or in real time, and generate the corresponding statistical report or chart. Then, the server will display these statistical information to the relevant personnel through the shared portal page, such as the administrator of the shared center, the task executor or the business responsible person, etc.

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

[0099] For example, see Figure 9The schematic diagram of the shared portal page shown in FIG. 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. The data row is used to store field values ​​for the serial number, voucher number, document number, work item, document type, document date, reporting unit, handler, amount, summary, and pool entry time. Also located above the shared task list are a refresh control, a batch approval control, a return task pool control, a suspend task control, and a claim task control. The refresh control is used to periodically update the shared task list based on shared tasks in the shared task pool. The batch approval control is used to batch approve 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 pool. The suspend task is used to suspend the execution of the shared tasks corresponding to the selected data rows in the shared task list. 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, a statistical control is provided above the shared task details table, which is 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] This application specifically includes the following beneficial effects:

[0101] In existing technologies, tasks are typically assigned to a shared task pool by directly associating process links with a shared center. However, this approach, when dealing with complex business processes involving numerous process links, often requires significant time and effort to configure, and often produces unsatisfactory results.

[0102] This application starts from the document model, the upper layer of the process, and optimizes task allocation by establishing a corresponding relationship between the document model and the shared center. Specifically, this solution focuses on the common roles corresponding to the process links. These roles are usually named and managed in a unified and standardized manner within the enterprise. Therefore, by maintaining the corresponding relationship between roles and the shared center, the amount of data is greatly controlled and simplified compared to directly processing a large number of process links.

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

[0104] In summary, the technical solution of this application effectively improves and optimizes existing technologies. 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 are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

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

[0107] Setting unit 1001, used to set shared organization attribute information and 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 sharing role, and specifying a business type;

[0109] The determining unit 1002 is configured to, upon 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 configured to obtain task attribute information of a process link when the execution status of the process link is detected to be in execution. The task attribute information includes: service unit, source system, job role, and business type;

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

[0112] Adding unit 1005 is 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;

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

[0114] The statistical unit 1007 is configured 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 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 it is a tenant mode, whether it is a 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 pool setting interface is displayed; 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;

[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 trigger action on the business type attribute setting tab is detected, a business 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 Pooling Settings tab, the Business Pooling Settings 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, business type and shared role of the selected data row are displayed in the service unit display area, business type display area and 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 the 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 per month, the ranking within the processing group and the number overdue on the 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 claim 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, when executing the document flow management method, only uses the division of the above functional modules as an example. In actual application, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be 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 are based on the same concept. The implementation process is detailed in the method embodiment and will not be repeated here.

[0137] The serial numbers of the above 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 that can store multiple instructions, which are suitable for being loaded and executed by a processor as described above. Figure 2 The method steps of the embodiment shown, the specific execution process can be found in Figure 2 The detailed 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 Figure 11 , provides a structural diagram of a server according to an embodiment of the present application. Figure 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 implement the connection and communication between these components.

[0142] The user interface 1103 may include a display screen (Display) and a camera (Camera). Optionally, the 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] The processor 1101 may include one or more processing cores. The processor 1101 utilizes various interfaces and circuits to connect various components within the server 1100. It executes various functions and processes data for the server 1100 by running or executing instructions, programs, code sets, or instruction sets stored in the memory 1105, as well as accessing data stored in the memory 1105. Optionally, the processor 1101 may be implemented using at least one hardware form selected from the group consisting of a digital signal processing (DSP), a field-programmable gate array (FPGA), and a programmable logic array (PLA). The processor 1101 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), and a modem. The CPU primarily processes the operating system, user interface, and application programs; the GPU is responsible for rendering and drawing the content displayed on the display screen; and the modem handles wireless communications. It is understood that the modem may not be integrated into the processor 1101 and may be implemented separately on a separate 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 Figure 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 Figure 11In the shown server 1100, the user interface 1103 is mainly used to provide an interface for the user to input, 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 processes as shown in the above method. Figure 2 The specific process can refer to the method shown in the above embodiment. Figure 2 The specific process can refer to the method shown in the above embodiment.

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

[0148] The above disclosure is only the preferred embodiment of the present application, and of course cannot limit the scope of the right of the present application, so the equivalent changes made according to the claims of the present application still belong to the scope covered by the present application.

Claims

1. A document flow management method, characterized in that: include: Set shared organization attribute information and shared center attribute information through the shared organization interface; Set up pooling configuration via the shared pool settings interface. The pooling configuration 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 as being executed, 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 shared task to the shared task pool of the sharing center; If not, push the process link to the user corresponding to the job role for processing; 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; The step of setting the pool configuration through the shared pool setting interface includes: The shared pooling settings interface is displayed; the shared pooling settings interface has three tabs: the source system settings tab, the business type attribute settings tab, and the business pooling settings 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 trigger action on the business type attribute setting tab is detected, a business 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 Pooling Settings tab, the Business Pooling Settings sub-interface is displayed; Set the service unit, source system name, business type, and shared role field values ​​through the business pool setting sub-interface; The service pooling setting sub-interface includes a pooling configuration detail table representing the pooling configuration, a service unit display area, a service type display area, and a shared role display area; each data row in the pooling configuration detail table corresponds to a pooling 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 service 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, business type and shared role of the selected data row are displayed in the service unit display area, business type display area and shared role display area respectively.

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 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 it is a tenant mode, whether it is a virtual sharing center, sharing center status and creation unit.

3. The method according to claim 1, characterized in that The shared portal page 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, handler, amount, summary and pool entry time; the statistical information includes: the number to be assigned, the number processed per day, the number processed per month, the ranking within the processing group and the number overdue on the day.

4. The method according to claim 1, wherein 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.

5. The method according to claim 4, 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.

6. 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 sharing role, and specifying a business type; a determining unit configured to, upon 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 configured to obtain task attribute information of a process link when detecting that the execution status of the process link is in execution, wherein the task attribute information includes: service unit, source system, job role, and business type; A checking unit, configured to check whether the process link complies with the pool entry configuration according to the task attribute information; an adding unit, configured to, if the answer is 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 is used to push the process link to the user corresponding to the job role for processing if the answer is no; A statistics unit, configured to collect statistics on the execution status of each shared task in the shared task pool and display the statistical information on a shared portal page; The step of setting the pool configuration through the shared pool setting interface includes: The shared pooling settings interface is displayed; the shared pooling settings interface has three tabs: the source system settings tab, the business type attribute settings tab, and the business pooling settings 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 trigger action on the business type attribute setting tab is detected, a business 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 Pooling Settings tab, the Business Pooling Settings sub-interface is displayed; Set the service unit, source system name, business type, and shared role field values ​​through the business pool setting sub-interface; The service pooling setting sub-interface includes a pooling configuration detail table representing the pooling configuration, a service unit display area, a service type display area, and a shared role display area; each data row in the pooling configuration detail table corresponds to a pooling 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 service 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, business type and shared role of the selected data row are displayed in the service unit display area, business type display area and shared role display area respectively.

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

8. 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 according to any one of claims 1 to 5.

Images