Method, device and equipment for establishing approval flow of business scene, medium and program product

Abstract

The invention provides a business scene approval flow establishment method which can be applied to the field of artificial intelligence. The approval flow establishment method comprises the following steps: translating a business process of a business scene to obtain a workflow corresponding to the business scene; the nodes of the workflow comprise a first node; based on the business elements corresponding to the first node, constructing a first node input page corresponding to the business scene; performing role authorization on the service function of the workflow; and based on the first node entry page and the workflow after role authorization, establishing an approval flow corresponding to the business scene. The invention further provides a business scene approval flow establishment device and equipment, a storage medium and a program product.

Description

Technical Field

[0001] The present application relates to the field of artificial intelligence, specifically to the field of process automation, and more specifically to a method, device, equipment, medium and program product for establishing an approval flow for a business scenario. Background Art

[0002] With the development of intelligent cloud platforms, modern hospital resource planning (HRP) systems have become a modern information system for hospital management. The typical business scenario approval process in HRP is a cloud-based process management service. Each business scenario has unique business elements and approval flows, with its own personalized business information and unique approval processes that meet the hospital's internal control requirements. Within HRP, there can be hundreds of approval flows for various business scenarios, and this number is increasing.

[0003] In hospital HRP, there are multiple and different business scenario approval flows. Every time a new business scenario appears, it needs to be coded once, which is complicated, the coding volume is large and the development efficiency is low. Summary of the Invention

[0004] In view of the above problems, the present application provides an approval flow establishment method, apparatus, device, medium and program product for quickly establishing an approval flow for business scenarios.

[0005] According to the first aspect of the present application, a method for establishing an approval flow for a business scenario is provided, comprising: translating the business process of the business scenario to obtain a workflow corresponding to the business scenario; the nodes of the workflow include a first node; based on the business elements corresponding to the first node, constructing a first node entry page corresponding to the business scenario; performing role authorization on the business functions of the workflow; and establishing an approval flow corresponding to the business scenario based on the first node entry page and the workflow after role authorization.

[0006] According to an embodiment of the present application, translating the business process of the business scenario to obtain the workflow corresponding to the business scenario includes: translating the business process of the business scenario based on translation rules to obtain the workflow corresponding to the business scenario; wherein the translation rules include serial, parallel, transfer and delegated node approval relationships.

[0007] According to an embodiment of the present application, the constructing the first node entry page corresponding to the business scenario based on the business element corresponding to the first node comprises: determining the business element corresponding to the first node according to a mapping relationship table of an approval process scenario and a first node entry business element; and obtaining coding data of the business element corresponding to the first node to construct the first node entry page corresponding to the business scenario.

[0008] According to an embodiment of the present application, the role authorization on the business function of the workflow comprises: configuring a role corresponding to a node in the workflow to obtain a node role; mapping a business function corresponding to the node role based on a business process of the business scenario; and performing user permission allocation based on the business function corresponding to the node role.

[0009] According to an embodiment of the present application, the mapping the business function corresponding to the node role based on the business process of the business scenario comprises: determining a role operable function based on the business process of the business scenario; determining an operation function corresponding to the node role according to the role operable function and the node role; and mapping the business function corresponding to the node role based on the operation function corresponding to the node role.

[0010] According to an embodiment of the present application, the node of the workflow further comprises an approval node, and the method further comprises: obtaining user entry data through the first node entry page and automatically passing the user entry data to the approval node; and in the case that any of the approval nodes is rejected, backtracking the rejected approval node to the first node.

[0011] The second aspect of the present application provides an approval flow establishment device of a business scenario, comprising: a translation module configured to translate a business process of a business scenario to obtain a workflow corresponding to the business scenario; a node of the workflow comprises a first node; a first node entry module configured to construct a first node entry page corresponding to the business scenario based on a business element corresponding to the first node; a role authorization module configured to authorize a role on a business function of the workflow; and an approval flow establishment module configured to establish an approval flow corresponding to the business scenario based on the first node entry page and the workflow after the role authorization.

[0012] According to an embodiment of the present application, the translation module comprises: a translation unit configured to translate a business process of a business scenario based on a translation rule to obtain a workflow corresponding to the business scenario; wherein the translation rule comprises a node approval relationship of series, parallel, transfer and delegation.

[0013] According to an embodiment of the present application, the first node entry module comprises: a mapping relationship unit configured to determine the business element corresponding to the first node according to a mapping relationship table of the approval process scenario and the first node entry business element; and an encoding unit configured to obtain the encoding data of the business element corresponding to the first node to construct the first node entry page corresponding to the business scenario.

[0014] According to an embodiment of the present application, the role authorization module comprises: a node role unit configured to configure the role corresponding to the node in the workflow to obtain the node role; a business function unit configured to map the business function corresponding to the node role based on the business process of the business scenario; and a permission allocation unit configured to perform user permission allocation based on the business function corresponding to the node role.

[0015] According to an embodiment of the present application, the business function unit comprises: an operable function sub-unit configured to determine the role operable function based on the business process of the business scenario; an operation function corresponding sub-unit configured to determine the operation function corresponding to the node role according to the role operable function and the node role; and a business function corresponding sub-unit configured to map the business function corresponding to the node role based on the operation function corresponding to the node role.

[0016] According to an embodiment of the present application, the node of the workflow further comprises an approval node, and the device further comprises: a data flow conversion module configured to obtain user input data through the first node entry page and automatically pass the user input data to the approval node; and in the case that any of the approval nodes is rejected, the rejected approval node is rolled back to the first node.

[0017] The third aspect of the present application provides an electronic device, comprising: one or more processors; a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the above method.

[0018] The fourth aspect of the present application further provides a computer readable storage medium having a computer program or instructions stored thereon, wherein the computer program or instructions are executed by a processor to implement the steps of the above method.

[0019] The fifth aspect of the present application further provides a computer program product comprising a computer program or instructions, wherein the computer program or instructions are executed by a processor to implement the steps of the above method.

[0020] According to an embodiment of the present application, a business flow of a business scenario is translated, a work flow corresponding to the business scenario is obtained; a node of the work flow includes a first node; a first node entry page corresponding to the business scenario is constructed based on a business element corresponding to the first node; a role authorization is performed on a business function of the work flow; and an approval flow corresponding to the business scenario is established based on the first node entry page and the work flow after the role authorization. Through the mode of the first node entry page combined with the work flow engine driving, the development of the hospital HRP approval process is simplified from full-process coding to front-end entry interface development, replacing the previous complicated code mode of coding once for a new business scenario. The approval flow of various different business scenarios in the hospital HRP can be quickly supported, low coding, high configurability and strong expansibility are realized, and the research and development efficiency of the bank-hospital cooperation can be greatly improved. BRIEF DESCRIPTION OF DRAWINGS

[0021] The above content and other purposes, features and advantages of the present application will be more clearly understood through the following description of the embodiments of the present application with reference to the accompanying drawings, in which:

[0022] Figure 1 An application scenario diagram of an approval flow establishment method of a business scenario according to an embodiment of the present application is schematically shown;

[0023] Figure 2 A flowchart of an approval flow establishment method of a business scenario according to an embodiment of the present application is schematically shown;

[0024] Figure 3 A translation diagram of a contract co-signing flow according to an embodiment of the present application is schematically shown;

[0025] Figure 4 A node approval relationship diagram according to an embodiment of the present application is schematically shown;

[0026] FIG. 5 schematically shows an approval node relationship diagram of a contract co-signing flow according to an embodiment of the present application; wherein, Figure 5a the approval node relationship diagram shown in FIG. 5 is for a contract co-signing flow diagram; Figure 5b

[0027] FIG. 6 schematically shows a delegation node relationship diagram of a procurement application flow according to an embodiment of the present application; wherein, Figure 6a the delegation node relationship diagram shown in FIG. 6 is for a procurement application flow diagram; Figure 6b

[0028] Figure 7 A first node entry page diagram of a procurement application flow according to an embodiment of the present application is schematically shown;

[0029] Figure 8 ​​A first node entry page diagram of a contract countersignature process according to an embodiment of the present application is illustratively shown;

[0030] Figure 9 An administrative expense approval process diagram according to an embodiment of the present application is illustratively shown;

[0031] Figure 10 A first node entry page diagram of an administrative expense approval process according to an embodiment of the present application is illustratively shown;

[0032] Figure 11 A role function diagram of a contract countersignature process according to an embodiment of the present application is illustratively shown;

[0033] Figure 12 A structural block diagram of an approval flow establishment apparatus of a business scenario according to an embodiment of the present application is illustratively shown; and

[0034] Figure 13 A block diagram of an electronic device suitable for implementing an approval flow establishment method of a business scenario according to an embodiment of the present application is illustratively shown. DETAILED DESCRIPTION

[0035] Hereinafter, embodiments of the present application will be described with reference to the accompanying drawings. It should be understood, however, that the description which follows is merely illustrative and is not intended to limit the scope of the present application. In the following detailed description of embodiments of the present application, numerous specific details are set forth in order to provide a thorough understanding of the present application. However, it will be apparent to one skilled in the art that one or more embodiments of the present application can be practiced without these specific details. In other instances, well-known structures and functions have not been described in detail in order to avoid obscuring aspects of the present application.

[0036] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used herein, the term "includes" and tautological expressions thereof, such as "including," "includes," "include," "contains," "containing," and so forth, mean the term "comprises."

[0037] All terms used herein (including technical and scientific terms) have the meanings commonly understood by one of ordinary skill in the art unless otherwise defined herein. It should be noted that the terms used herein are to be interpreted as having a meaning that is consistent with the understanding of those terms by those in the relevant art, and not in an overly literal or overly formal manner.

[0038] In the case of using expressions such as "at least one of A, B, and C, etc.", it should generally be interpreted to include one or more of A, B, or C in all of the ways that such a phrase can be interpreted when recited by a person of ordinary skill in the art (e.g., when read aloud, "a system having at least one of A, B, and C" should be interpreted to include, but is not limited to, a system that has A alone, a system that has B alone, a system that has C alone, a system that has both A and B, a system that has both A and C, a system that has both B and C, and / or a system that has A, B, and C, etc.).

[0039] The asset management in the hospital HRP includes three modules of budget, recruitment, and assets. In the three modules, independent business approval processes in respective modules are included. Taking the recruitment module as an example, at least approval processes of procurement application, contract signing, and framework agreement execution are included. In each business scenario of the hospital HRP, business elements and approval processes are different, and have respective personalized business information and specific approval processes meeting the internal control requirements of the hospital.

[0040] Taking the approval process of contract signing in several typical business scenarios in the hospital HRP as an example, the existing implementation mode is usually as follows:

[0041] 1. After determining the business elements and approval processes of one kind of business scenario each time, the business detail table and the business approval process table are fixed. Taking the contract signing business as an example, two tables of the contract signing business detail table and the contract signing business approval process table are fixed. The two tables are linked by the contract number (primary key). The contract signing business detail table is shown in Table 1 below, and the contract signing business approval process table is shown in Table 2 below.

[0042] Table 1

[0043]

[0044] Table 2

[0045]

[0046] 2. As described above, in the hospital HRP, the approval processes of various different business scenarios can be as many as dozens. According to the existing implementation mode, for a new business scenario, a developer needs to design one business detail table and one approval process table, and perform corresponding code coding implementation.

[0047] 3. According to the business development needs of the hospital, any business scenario that has been launched may be continuously optimized and adjusted in terms of business elements and approval processes. When the business elements of the contract compilation are adjusted (such as adding or deleting some elements), the contract co-signing business details table can only be adjusted by adding or deleting fields. When the business approval process of the contract co-signing changes, not only is it necessary to add fields or delete certain fields, but the data dictionary of the fields also needs to be adjusted (such as the latest status of the data dictionary). The greater workload lies in supporting the logical processing rules of the new approval flow through code encoding.

[0048] In summary, the existing implementation method requires developers to do a lot of coding. It is a complicated coding method that requires coding every time for a new business scenario. The establishment process of approval flows for different business scenarios is cumbersome, which increases process management costs, is not conducive to quickly responding to business changes, and reduces the efficiency of cross-departmental collaboration.

[0049] Therefore, an embodiment of the present application provides a method for establishing an approval flow for a business scenario, translating the business process of the business scenario to obtain a workflow corresponding to the business scenario; the nodes of the workflow include a first node; based on the business elements corresponding to the first node, constructing a first node entry page corresponding to the business scenario; performing role authorization on the business functions of the workflow; and establishing an approval flow corresponding to the business scenario based on the first node entry page and the workflow after role authorization. By combining the first node entry page with a workflow engine-driven model, the development of the hospital HRP approval process is simplified from full-process coding to front-end entry interface development, replacing the original complicated coding method of coding once for each new business scenario, and can quickly support the approval flows of various business scenarios in the hospital HRP, achieve low-code, high configurability and strong scalability, and greatly improve the R&D efficiency of bank-hospital cooperation.

[0050] Figure 1 An application scenario diagram of a method for establishing an approval flow for a business scenario according to an embodiment of the present application is schematically shown.

[0051] like Figure 1 As shown, an application scenario 100 according to this embodiment may include establishing an approval process in a business scenario in a hospital HPR. A network 104 is used as a medium to provide a communication link between a first terminal device 101, a second terminal device 102, a third terminal device 103, and a server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0052] The user can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications can be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0053] The first terminal device 101, the second terminal device 102, and the third terminal device 103 can be various electronic devices with display screens and supporting web browsing, including but not limited to smartphones, tablet computers, laptop computers, desktop computers, etc.

[0054] The server 105 can be a server providing various services, such as a background management server supporting websites browsed by the user using the first terminal device 101, the second terminal device 102, and the third terminal device 103 (only as examples). The background management server can analyze and process received user requests and other data, and feed back the processing results (such as web pages, information, or data, etc. obtained or generated according to user requests) to the terminal device.

[0055] It should be noted that the business scenario approval flow establishment method provided in the embodiments of the present application can generally be executed by the server 105. Correspondingly, the business scenario approval flow establishment apparatus provided in the embodiments of the present application can generally be arranged in the server 105. The business scenario approval flow establishment method provided in the embodiments of the present application can also be executed by a server or a server cluster different from the server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or the server 105. Correspondingly, the business scenario approval flow establishment apparatus provided in the embodiments of the present application can also be arranged in a server or a server cluster different from the server 105 and capable of communicating with the first terminal device 101, the second terminal device 102, the third terminal device 103, and / or the server 105.

[0056] It should be understood that Figure 1 The number of terminal devices, networks, and servers in the above description is only illustrative. According to the implementation needs, there can be any number of terminal devices, networks, and servers.

[0057] The business scenario approval flow establishment method according to the embodiments of the present application will be described in detail below based on the scenario described above. Figure 1 Figures 2-11

[0058] Figure 2 ​​A flowchart of a method for establishing an approval flow of a business scenario according to an embodiment of the present application is shown.

[0059] As shown in Figure 2 The method for establishing an approval flow of a business scenario of this embodiment includes operations S210-S240, and can quickly establish an approval flow by interacting with a user.

[0060] In operation S210, the business flow of the business scenario is translated to obtain a workflow corresponding to the business scenario. The nodes of the workflow include a first node.

[0061] The business scenario is the actual scenario of various specific business activities in hospital operation, covering the links from business initiation, execution to end, such as supply chain management, asset and equipment management, budget management, performance management, medical income management, expense reimbursement, etc. The supply chain management includes budget application process, procurement application process, contract signing process, contract expense approval process, administrative expense approval process and other business processes. Each business process may include one or more approval processes.

[0062] By way of example, the translation of the business flow of the business scenario can be achieved by a graphical translation method. A graphical tool can be used to translate the business flowchart of the business scenario into a workflow chart. First, the natural language processing (NLP) technology can be used to analyze the business scenario text, extract key nodes, roles, transfer rules and other elements, map the business flow elements to the pre-defined workflow meta-model, use the front-end graphical rendering technology to generate a visual workflow chart, automatically identify business rules (such as conditional branching, approval level) and convert them into executable process expressions, verify the translation accuracy through process simulation algorithm, and automatically identify redundant nodes and recommend optimization solutions.

[0063] By way of example, the translation of the business flow of the business scenario can also be achieved by a deep learning model translation method. A deep learning-based network model (such as a convolutional neural network CNN or a graph neural network GNN) can be constructed to perform image recognition or structured analysis on the business flowchart, extract nodes, flow direction, approval conditions, transfer rules and other elements. Through training model learning, the mapping relationship between business logic and workflow rules is learned to automatically generate a workflow chart containing nodes and approval paths, realizing intelligent conversion of the process chart to an executable workflow and reducing the cost of manual modeling.

[0064] The business flow of the business scenario starts the establishment process of the approval flow. In this mode, the coding error rate of the developer can be reduced, because the key factors affecting the business approval process have been changed from the product manager's analysis of the flowchart and the developer's coding support to only the product manager's analysis of the flowchart, weakening the developer's coding support.

[0065] The product manager / developer accurately combs out the approval process of a certain business scenario of the hospital by using a flowchart during requirement analysis, obtains a business flowchart of the business scenario, the developer obtains the provided business flowchart, and inputs the hospital HRP. The hospital HRP converts the business flow into a workflow by using the above translation method. Figure 3 The translation diagram of the contract signing process according to an embodiment of the present application is schematically shown in FIG. 5. Figure 3 As shown in FIG. 5, the developer only needs to input the business flowchart to obtain the corresponding workflow diagram, which can separate the developer from the traditional understanding of business requirements and code development work. The developer does not need to pay too much attention to how to realize the business requirements through coding, but only needs to obtain the business flowchart combed by the product manager from the demand side, and convert the business flow into a workflow, which helps subsequent rapid business online. Figure 1 The translation diagram of the contract signing process according to an embodiment of the present application is schematically shown in FIG. 5.

[0066] According to an embodiment of the present application, the business flow of the business scenario is translated in operation S210 to obtain the workflow corresponding to the business scenario, including converting the business flow of the business scenario based on the translation rule to obtain the workflow corresponding to the business scenario; wherein the translation rule includes the node approval relationship of serial, parallel, transfer and delegation.

[0067] Figure 4 The node approval relationship diagram according to an embodiment of the present application is schematically shown in FIG. 4. Figure 4 As shown in FIG. 4, under the translation rule, the workflow engine fully covers the node approval relationship of serial, parallel, transfer, and delegation of various node requirements in the approval process, and fully meets the approval flow requirements of various business scenarios in the hospital HRP.

[0068] In an embodiment of the present application, based on the transfer rule, the workflow engine fully covers the serial approval, parallel approval, transfer, and delegation of various node requirement relationships in the approval process, and fully meets the approval flow requirements of various business scenarios in the hospital HRP.

[0069] The approval node relationship diagram of the contract signing process according to an embodiment of the present application is schematically shown in FIG. 5. Figure 5a As shown in FIG. 5, the contract signing process, as shown in the approval node relationship, Figure 5b In the workflow corresponding to the contract signing process, there are serial and parallel of the workflow. After the contract is prepared by the procurement officer, the contract content is reviewed by the review officer, which belongs to the serial workflow. After the contract is reviewed by the review officer, it is reviewed in parallel by the director in charge, the director of the use department, the director of the audit office, and the director of the finance department.

[0070] The delegation node relationship diagram of the procurement application process according to an embodiment of the present application is schematically shown in FIG. 6. Figure 6a As shown in FIG. 6, the procurement application process, as shown in the delegation node relationship,Figure 6b The delegation node relationship shown from the scene that the task delegated from the current node needs to return to the current node for re-approval, the director of the procurement office can delegate to the procurement review officer, the procurement review officer returns the delegation result to the director, and the director makes a second review, which belongs to the delegation workflow.

[0071] For the workflow, it means that the task transferred from the current node does not need to return to the current node for re-approval, which will not be described in detail here.

[0072] In operation S220, a first node entry page corresponding to a business scenario is constructed based on a business element corresponding to the first node.

[0073] Different business elements need to be entered for different approval process scenarios corresponding to different business scenarios, and the corresponding first node entry page needs to be constructed. One business scenario may include one or more approval process scenarios, so the approval process scenarios may be the same in different business scenarios, and the corresponding business elements may overlap, and the business element data of other business scenarios can be reused in these scenarios. The first node entry page is used for subsequent nodes to make approval viewing and display in the subsequent approval flow.

[0074] Exemplarily, as shown in a procurement application process, Figure 6a a first node entry page diagram of the procurement application process according to an embodiment of the present application is schematically shown, as shown in Figure 7 The business elements of the procurement application process include procurement form, procurement application unit price, delivery location, supporting consumable reagent situation, expected arrival event, service project nature, last year's service acceptance report, and the like. Figure 7 Exemplarily, as shown in a contract signing process,

[0075] a first node entry page diagram of the contract signing process according to an embodiment of the present application is schematically shown, as shown in Figure 5a The business elements of the contract signing process include contract name, supplier name, goods name, specification, quantity, payment method, acceptance situation, and identification validity period, goods warranty period, and the like. Figure 8 Figure 8 Exemplarily, a first node entry page diagram of the administrative expense approval process according to an embodiment of the present application is schematically shown, as shown in

[0076] The business elements of the administrative expense approval process include borrowing situation, total application amount, application reason, electronic invoice situation, payment method, transfer situation, and the like. Figure 9 Figure 10 Figure 10

[0077] ​​​In operation S230, role authorization is performed on the business functions of the workflow.

[0078] Different business functions are included in the workflow. Taking the workflow of the contract signing process as an example, the business functions include contract preparation, contract preparation, contract review, contract signing, etc. For different business functions, the role needs to be set and the actual personnel role needs to be authorized.

[0079] In operation S240, based on the first node entry page and the workflow after role authorization, an approval flow corresponding to the business scenario is established.

[0080] Taking the contract signing process as an example, the establishment of the approval flow process corresponding to the contract signing process is as follows: first, the business elements (such as contract data) entered in the first node entry page are bound to the workflow engine of the workflow after role authorization, and the data transmission rule is defined. Then, configure the subsequent approval nodes (such as review and signing) according to the role permission, set the transfer condition (such as the amount threshold to trigger different levels of approval). Finally, integrate the rejection mechanism to ensure that the data is returned to the first node for modification when the approval is rejected, forming a closed-loop process.

[0081] In the embodiments of the present application, through the mode of the first node entry page combined with the workflow engine driven mode, the development of the hospital HRP approval process is simplified from full-process coding to front-end entry interface development, replacing the previous complex code method of coding once for each new business scenario. It can quickly support various different business scenarios in the hospital HRP approval flow, realize low code, high configurability and strong extensibility, and greatly improve the research and development efficiency of bank-hospital cooperation.

[0082] Users can quickly realize the online of specific business scenario processes by using the specific scenario business approval process, one-key translation of the workflow engine, first node page entry coding, and supporting methods of role authorization of each business function in the approval flow. With this idea, any new hospital HRP approval flow in the hospital HRP can be quickly realized online through this method, which can quickly support various different business scenarios in the hospital HRP approval flow, replacing the previous complex code method of coding once for each new business scenario. It is an exploration to improve the efficiency of bank-hospital cooperation.

[0083] According to the embodiments of the present application, in operation S220, based on the business elements corresponding to the first node, the first node entry page corresponding to the business scenario is constructed, including operation S2201~operation S2202.

[0084] In operation S2201, the business elements corresponding to the first node are determined according to the mapping relationship table of the approval flow scenario and the first node entry business elements.

[0085] According to the different approval process scenarios in the hospital HRP, the relevant business elements that need to be entered at the first node under the scenario are corresponding. For example, the mapping relationship table between typical approval process scenarios and the business elements entered at the first node is shown in Table 3 below.

[0086] Table 3

[0087]

[0088] First-node entry business elements represent the business elements required for first-node entry and represent the business-related elements in the approval process of the business scenario's business process. When a new approval process scenario is added, that is, a new first-node entry business element is added, a corresponding first-node entry element page is added.

[0089] In operation S2202, the coding data of the business element corresponding to the first node is obtained to construct the first node entry page corresponding to the business scenario.

[0090] For business scenarios, after converting the business process diagram to a workflow diagram, developers' coding tasks are reduced to developing the page entry function for the procurement specialist to compile the contract, corresponding to the first node. This requires providing the coding data corresponding to the first node entry page, namely the first node coding code. This makes coding relatively simple for developers. The coding data obtained by the hospital HRP can be used to build the first node entry page.

[0091] Exemplarily, the process of constructing the first-node entry page corresponding to the business scenario is as follows: First, the data structure in the first-node coding code provided by the developer is extracted through a code parsing tool, and the form fields (such as input boxes, drop-down boxes, text fields, etc.) and their corresponding business elements (such as contract numbers, budget amounts, applicants, etc.) are identified. Regular expressions or abstract syntax trees can be used to parse the code and extract related business fields. Secondly, a mapping rule between code elements and business elements is established, and the mapping relationship is stored through a configuration file or metadata. Then, based on a low-code platform or visual designer, the visual structure of the first-node entry page is automatically generated according to the mapping relationship, supporting drag-and-drop layout adjustment, and binding data interfaces to achieve two-way data binding.

[0092] Finally, the workflow engine is integrated to associate the generated page with the approval process, configure field verification rules (such as non-empty and format verification) and data transfer logic, ensure that the data entered at the first node is automatically transferred to the subsequent approval node according to the process definition, and support data write-back and page status recovery when rejected.

[0093] In the embodiments of the present application, the coding data of the business elements corresponding to the first node is acquired to construct the first node entry page corresponding to the business scene, and the developer only needs to perform simple coding of the business element entry function of the first node according to each business scene, so that the code coding work of the developer is greatly reduced, the development efficiency is quickly improved, and the market requirements of quickly responding to customer needs can be met.

[0094] In addition, the workflow engine is adopted, the approval flow of different business scenes can be met, and the business elements of each scene are still independent. Since the business scene approval flow supported by the workflow engine can be quickly online published, the worry and concern of the developer to the frequent adjustment of the demand side business is almost eliminated. Even if the demand side needs to be adjusted, the most frequent adjustment is mainly the addition and deletion adjustment of the approval flow node or the addition and deletion adjustment of the business element. The workflow approval flow can be simply adjusted according to the new business process Figure 1 , or the business elements entered on the home page are adjusted, so that the business adjustment of the demand side can be met. For the demand of the hospital HRP such as multiple approval flow scenes, the adaptability is high.

[0095] According to the embodiments of the present application, in the role authorization of the business function of the workflow in operation S230, operations S2301-S2303 are included.

[0096] In operation S2301, the role corresponding to the node in the workflow is configured, and the node role is obtained.

[0097] According to the role configuration of each node in the workflow, the node role corresponding to the node is configured, and each node in the workflow is associated to a specific business role (such as a procurement officer, a contract review officer), so that a role-node mapping table can be formed. Taking the contract signing process as an example, the workflow of the contract signing is as follows: Figure 3 The first node is configured as a procurement officer, and the remaining nodes are respectively configured as a contract review officer, a department director, and the like.

[0098] In operation S2302, the business function corresponding to the node role is mapped based on the business process of the business scene.

[0099] According to the embodiments of the present application, in operation S2302, the business function corresponding to the node role is mapped based on the business process of the business scene, operations S21-S23 are included.

[0100] In operation S21, the role operable function is determined based on the business process of the business scene.

[0101] Taking the contract signing process as an example, Figure 11 the role function diagram of the contract signing process according to the embodiments of the present application is schematically shown as follows:Figure 11 As shown in the figure, the contract signing process swim lanes clearly indicate the functions that each role can perform. The functions that the roles can perform in their respective swim lanes are independent and related and do not affect each other.

[0102] In operation S22, the operation function corresponding to the node role is determined according to the operable functions of the role and the node role.

[0103] The role's operable function indicates that a node role can operate a certain function, corresponding to Figure 11 The roles and functions in the contract countersigning workflow can determine its operational functions, such as "Purchasing specialists can prepare (contracts)", "(Review specialists) can review contracts", "Responsible director can countersign", "Director of using department can countersign", "Director of the Audit Office can countersign", "Director of the Finance Department can countersign", and "Leaders in charge of the hospital can give final approval".

[0104] In operation S23 , based on the operation functions corresponding to the node roles, the business functions corresponding to the node roles are mapped.

[0105] A node role in the workflow can operate a certain function, which can be mapped to the business functions that the role can operate. Taking the contract countersigning process as an example, the role function mapping table is shown in Table 4 below. By determining the business functions of the node role and then authorizing specific personnel, it is possible to realize which business functions the node role can operate in the contract countersigning process.

[0106] Table 4

[0107]

[0108] In the embodiments of the present application, based on the operational functions corresponding to the node roles, the business functions corresponding to the node roles are mapped, which can achieve clear matching of rights and responsibilities, improve process execution efficiency, ensure business standardization and standardized operation, and reduce management costs.

[0109] In operation S2303, user rights are allocated based on the business functions corresponding to the node roles.

[0110] User rights allocation is to grant users permission to perform specific operations, access data, or use resources in the system based on the roles they assume in business scenarios and their corresponding business functions, ensuring that users can only perform operations consistent with their responsibilities and achieving refined management and control of rights. For example, user rights allocation may include the following process:

[0111] (1) Functional authority definition: Configure an operation set for each node (such as view, edit, and approve). For example, the "Contract Preparation" node opens editing authority, while the "Final Review" node only retains approval authority.

[0112] (2) User-role assignment: associate a specific person (e.g. Ma XX) to a corresponding role (purchasing specialist) through the role-based access control model, and the system automatically inherits all node permissions of the role.

[0113] (3) Data permission control: refine the access range based on departments, amounts, etc. For example, the department director can only approve contracts in his department, and the finance director can view all contract amounts.

[0114] (4) Dynamic permission verification: real-time verification of user permissions during process flow, such as automatically filtering non-supervising hospital leaders in the final review node to ensure operational compliance.

[0115] Through the mapping of role-node-function-permission, the deep coupling of permissions and business processes is achieved, reducing manual configuration costs and improving system security.

[0116] In the embodiments of the present application, based on the business process of the business scenario, the business function corresponding to the node role is mapped, realizing the precise matching of business process, role and business function, and guaranteeing the standardization and flexibility of the approval process.

[0117] According to the embodiments of the present application, the node of the workflow also includes an approval node, and after the operation S240 establishes the approval flow corresponding to the business scenario, it further includes the operation S2501~operation S2502.

[0118] In operation S2501, user input data is obtained through the first node entry page, and the user input data is automatically transmitted to the approval node.

[0119] The first node entry page is used for user approval viewing and display, and the first node function user can enter relevant data from this page as core data of the process, which is transmitted to the subsequent approval node along with the workflow for other users to view and decide. The hospital HRP automatically drives the process node flow, and the process logic (such as flow path, permission control) of the subsequent node (such as review, approval) is pre-configured through the workflow engine, without the need for repeated coding by developers.

[0120] In operation S2502, in the case of approval rejection at any approval node, the rejected approval node is rolled back to the first node.

[0121] In the subsequent approval node of the first node, once the subsequent node is rejected by the user, it is returned to the first node, and the operation permission of the intermediate approval node is locked, and the first node function user modifies it again and then goes through the approval process. Therefore, for a kind of approval process scenario, the developer only needs to focus on coding the business element entry function of the first node, and the coding work is relatively simple.

[0122] In the embodiments of the present application, the data is obtained through the first node entry page and automatically transmitted to the approval node, the workflow engine automatically drives the process node flow, the data flow efficiency can be improved, the information consistency can be ensured, the manual transmission error can be reduced, and the approval process experience can be optimized.

[0123] Based on the approval flow establishment method of the above business scenario, the present application further provides an approval flow establishment device of a business scenario. The following will be described in detail in combination with Figure 12 The device is described in detail.

[0124] Figure 12 The structure block diagram of the approval flow establishment device of a business scenario according to the embodiments of the present application is schematically shown.

[0125] As Figure 12 shown, the approval flow establishment device 1200 of a business scenario of the embodiments includes a translation module 1210, a first node entry module 1220, a role authorization module 1230, and an approval flow establishment module 1240.

[0126] The translation module 1210 is configured to translate the business process of the business scenario to obtain the workflow corresponding to the business scenario; the nodes of the workflow include the first node. In an embodiment, the translation module 1210 can be configured to perform the operation S210 described above, and details are not repeated here.

[0127] The first node entry module 1220 is configured to construct the first node entry page corresponding to the business scenario based on the business elements corresponding to the first node. In an embodiment, the first node entry module 1220 can be configured to perform the operation S220 described above, and details are not repeated here.

[0128] The role authorization module 1230 is configured to perform role authorization on the business functions of the workflow. In an embodiment, the role authorization module 1230 can be configured to perform the operation S230 described above, and details are not repeated here.

[0129] The approval flow establishment module 1240 is configured to establish the approval flow corresponding to the business scenario based on the first node entry page and the workflow after role authorization. In an embodiment, the approval flow establishment module 1240 can be configured to perform the operation S240 described above, and details are not repeated here.

[0130] According to the embodiments of the present application, the translation module 1210 includes a translation unit configured to translate the business process of the business scenario based on a translation rule to obtain the workflow corresponding to the business scenario; wherein the translation rule includes the node approval relationship of series, parallel, transfer, and delegation.

[0131] According to an embodiment of the present application, the first node entry module 1220 comprises: a mapping relationship unit configured to determine the business element corresponding to the first node according to a mapping relationship table of the approval process scenario and the first node entry business element; and an encoding unit configured to obtain the encoding data of the business element corresponding to the first node to construct the first node entry page corresponding to the business scenario.

[0132] According to an embodiment of the present application, the role authorization module 1230 comprises: a node role unit configured to configure the role corresponding to the node in the workflow to obtain the node role; a business function unit configured to map the business function corresponding to the node role based on the business process of the business scenario; and a permission allocation unit configured to perform user permission allocation based on the business function corresponding to the node role.

[0133] According to an embodiment of the present application, the business function unit comprises: an operable function sub-unit configured to determine the role operable function based on the business process of the business scenario; an operation function corresponding sub-unit configured to determine the operation function corresponding to the node role according to the role operable function and the node role; and a business function corresponding sub-unit configured to map the business function corresponding to the node role based on the operation function corresponding to the node role.

[0134] According to an embodiment of the present application, the node of the workflow further comprises an approval node, and the device 1200 further comprises: a data flow conversion module configured to obtain the user input data through the first node entry page and automatically pass the user input data to the approval node; and in the case of approval rejection at any approval node, the rejected approval node is rolled back to the first node.

[0135] According to an embodiment of the present application, any of the plurality of modules of the translation module 1210, the first node entry module 1220, the role authorization module 1230 and the approval flow establishment module 1240 can be combined in one module, or any of the modules can be split into a plurality of modules. Alternatively, at least part of the functions of one or more of the modules can be combined with at least part of the functions of the other modules, and implemented in one module. According to an embodiment of the present application, at least one of the translation module 1210, the first node entry module 1220, the role authorization module 1230 and the approval flow establishment module 1240 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on chip, a system on board, a system on package, an application specific integrated circuit (ASIC), or any other reasonable manner of integrating or packaging a circuit, etc. in hardware or firmware, or implemented in any one of software, hardware and firmware or in a proper combination of any of them. Alternatively, at least one of the translation module 1210, the first node entry module 1220, the role authorization module 1230 and the approval flow establishment module 1240 can be at least partially implemented as a computer program module which, when executed, can perform the corresponding functions.

[0136] Figure 13 A block diagram of an electronic device suitable for implementing the approval flow establishment method according to the embodiments of the present application is schematically shown.

[0137] As shown in Figure 13 The electronic device 900 according to the embodiments of the present application includes a processor 901 which can perform various appropriate actions and processes according to programs stored in a read only memory (ROM) 902 or loaded from a storage portion 908 into a random access memory (RAM) 903. The processor 901 can include, for example, a general purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special purpose microprocessor (such as an application specific integrated circuit (ASIC)), etc. The processor 901 can also include an on-board memory for cache use. The processor 901 can include a single processing unit or a plurality of processing units for performing different actions of the method processes according to the embodiments of the present application.

[0138] In the RAM 903, various programs and data required for the operation of the electronic device 900 are stored. The processor 901, the ROM 902, and the RAM 903 are connected to each other via the bus 904. The processor 901 performs various operations of the method flow according to the embodiments of the present application by executing the programs in the ROM 902 and / or the RAM 903. It should be noted that the programs can also be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 can also perform various operations of the method flow according to the embodiments of the present application by executing the programs stored in the one or more memories.

[0139] According to the embodiments of the present application, the electronic device 900 can further include an input / output (I / O) interface 905, which is also connected to the bus 904. The electronic device 900 can further include one or more of the following components connected to the input / output (I / O) interface 905: an input part 906 including a keyboard, a mouse, and the like; an output part 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), and the like, and a speaker, and the like; a storage part 908 including a hard disk, and the like; and a communication part 909 including a network interface card such as a LAN card, a modem, and the like. The communication part 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the input / output (I / O) interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, and the like is mounted on the drive 910 as necessary, so that a computer program read therefrom is installed in the storage part 908 as necessary.

[0140] The present application also provides a computer readable storage medium, which can be included in the device / apparatus / system described in the above embodiments; or can exist separately without being assembled into the device / apparatus / system. The above computer readable storage medium carries one or more programs, when the one or more programs are executed, the method according to the embodiments of the present application is implemented.

[0141] According to an embodiment of the present application, the computer readable storage medium can be a non-transitory computer readable storage medium, for example, can include but is not limited to: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this application, a computer readable storage medium can be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to an embodiment of the present application, the computer readable storage medium can include one or more of the above-described ROM 902 and / or RAM 903 and / or a memory other than the ROM 902 and the RAM 903.

[0142] Embodiments of the present application also include a computer program product, which includes a computer program containing program codes for executing the methods shown in the flowcharts. When the computer program product is run in a computer system, the program codes are used to make the computer system implement the approval flow establishment method of the business scenario provided by the embodiments of the present application.

[0143] The above-described functions defined in the system / device / apparatus of the embodiments of the present application are performed when the computer program is executed by the processor 901. According to an embodiment of the present application, the above-described system, device, module, unit, etc. can be implemented by computer program modules.

[0144] In one embodiment, the computer program can rely on tangible storage media such as optical storage media, magnetic storage media, etc. In another embodiment, the computer program can also be transmitted, distributed, and downloaded in the form of a signal on a network medium, and be downloaded and installed through the communication part 909, and / or installed from the detachable medium 911. The program codes contained in the computer program can be transmitted by any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

[0145] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 909, and / or installed from the detachable medium 911. When the computer program is executed by the processor 901, the above-described functions defined in the system of the embodiments of the present application are performed. According to an embodiment of the present application, the above-described system, device, apparatus, module, unit, etc. can be implemented by computer program modules.

[0146] According to embodiments of the present application, program code for implementing the computer programs provided by embodiments of the present application can be written in any combination of one or more programming languages, and can be implemented in a high-level procedural and / or object-oriented programming language, and / or in assembly / machine language. Programming languages include, but are not limited to, Java, C++, python, "C", or the like. Program code can execute entirely on a user's computing device, partly on the user's device, as a stand-alone software package, partly on a remote computing device, or entirely on the remote computing device or server. In the latter scenario, the remote computing device can be connected to the user's computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computing device, such as through the Internet using an Internet Service Provider.

[0147] The computer program instructions can also be loaded onto a computer or other programmable information processing apparatus to cause a series of operations to be performed on the computer or other programmable information processing apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable information processing apparatus implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0148] Those skilled in the art will understand that features recited in the various embodiments of the present application can be combined and / or integrated in various combinations and / or permutations, even if such combinations and / or permutations are not expressly noted in the present application. In particular, features recited in the various embodiments of the present application can be combined and / or integrated in various combinations and / or permutations without departing from the spirit and teachings of the present application. All such combinations and / or integrations are within the scope of the present application.

Claims

1. A method for establishing an approval flow for a business scenario, characterized in that: The method comprises: Translate the business process of the business scenario to obtain a workflow corresponding to the business scenario; the nodes of the workflow include the first node; Based on the business elements corresponding to the first node, construct a first node entry page corresponding to the business scenario; Performing role authorization on the business functions of the workflow; and Based on the first node entry page and the workflow after the role authorization, an approval flow corresponding to the business scenario is established.

2. The method according to claim 1, characterized in that The business process of the business scenario is translated to obtain a workflow corresponding to the business scenario, including: Based on the translation rules, the business process of the business scenario is translated to obtain the workflow corresponding to the business scenario; The translation rules include serial, parallel, transfer and delegated node approval relationships.

3. The method according to claim 1, characterized in that The step of constructing a first node entry page corresponding to the business scenario based on the business elements corresponding to the first node includes: Determine the business element corresponding to the first node according to the mapping relationship table between the approval process scenario and the business element entered at the first node; and Obtain the coding data of the business elements corresponding to the first node to construct the first node entry page corresponding to the business scenario.

4. The method according to claim 1, wherein The role authorization for the business function of the workflow includes: Configure the roles corresponding to the nodes in the workflow to obtain the node roles; Based on the business process of the business scenario, mapping the business functions corresponding to the node roles; and User rights are allocated based on the business functions corresponding to the node roles.

5. The method according to claim 4, characterized in that The business process based on the business scenario maps the business functions corresponding to the node roles, including: Determine the operational functions of the role based on the business process of the business scenario; Determining the operation function corresponding to the node role according to the role's operable function and the node role; and Based on the operation function corresponding to the node role, the business function corresponding to the node role is mapped.

6. The method according to claim 4, characterized in that The nodes of the workflow also include an approval node, and the method further includes: Acquiring user input data through the first node input page, and automatically transmitting the user input data to the approval node; and In the case that any of the approval nodes rejects the approval, the rejected approval node is rolled back to the first node.

7. A device for establishing an approval flow for a business scenario, characterized in that: The device comprises: A translation module, configured to translate the business process of a business scenario to obtain a workflow corresponding to the business scenario; the nodes of the workflow include a first node; A first node entry module, configured to construct a first node entry page corresponding to the business scenario based on the business elements corresponding to the first node; A role authorization module, configured to perform role authorization on the business functions of the workflow; and The approval flow establishment module is used to establish the approval flow corresponding to the business scenario based on the first node input page and the workflow after the role authorization.

8. An electronic device comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images