CN112990738A

CN112990738A - Examination and approval path configuration method and system

Info

Publication number: CN112990738A
Application number: CN202110342395.3A
Authority: CN
Inventors: 张如琳
Original assignee: Beijing Mininglamp Software System Co ltd
Current assignee: Beijing Mininglamp Software System Co ltd
Priority date: 2021-03-30
Filing date: 2021-03-30
Publication date: 2021-06-18

Abstract

The application discloses an approval path configuration method and system, wherein the approval path configuration method comprises the following steps: the setting step: setting an approval authority according to the requirement of the files to be approved; configuring an approver: configuring an approver according to the approval authority; an approval path generation step: generating an approval path by using a process engine according to the approval authority and the approver; and (3) approval step: and examining and approving the files to be examined according to the examination and approval path. The invention provides an approval path configuration method and system, which do not additionally increase flow lines and flow conditions through the automatic skip function of a flow engine, only change node approval personnel without integrally considering the flow conditions of all paths when the flow adjustment is changed, and realize the requirement of approval path configuration, so that the approval path configuration principle is simple and easy to understand, the flow diagram is clear, and the configuration workload is greatly reduced.

Description

Examination and approval path configuration method and system

Technical Field

The application relates to the technical field of examination and approval path configuration, in particular to an examination and approval path configuration method and system.

Background

The existing process engine supports the same approver with the same approval authority to automatically skip, when the approval process is configured according to the service scene, the same process has the conditions of different application for different types of services and different approval paths, and the summary table of the service scene in the prior art is shown as follows. The conventional general flow configuration implementation manner is to distinguish different approval paths of different application types by drawing a flow condition line. The approval path configuration flow diagram is shown in fig. 2 for the scenario described in the following table. Different approval paths of different types of applications are realized by adding a process condition line, a process diagram is messy and not intuitive, and configuration conditions have large workload and are easy to make mistakes. In an actual more complex business scenario, more different types of approval paths may exist in the same process, and the original manner is to increase an approval process line and configure corresponding and, or, and or, or not conditions, which is usually large in workload and prone to the situation that the condition configuration is insufficient and the process path is wrong.

	Approval node one	Approval node two	Approval node three	Approval node four
					Application type A	Person a	Need not to examine and approve	Person b	Person c
Application type B	Person a	Person d	Need not to examine and approve	Person e
					Application type C	Person a	Person f	Person g	Need not to examine and approve

Prior art service scenario overview

Disclosure of Invention

The embodiment of the application provides an approval path configuration method and system, which at least solve the problems that different approval paths of different types of applications are realized by adding a process condition line, a flow chart is messy and unobservable, configuration condition workload is large, errors are easy to occur and the like.

The invention provides an approval path configuration method, which comprises the following steps:

the setting step: setting an approval authority according to the requirement of the files to be approved;

configuring an approver: configuring an approver according to the approval authority;

an approval path generation step: generating an approval path by using a process engine according to the approval authority and the approver;

and (3) approval step: and examining and approving the files to be examined according to the examination and approval path.

According to the approval path configuration method, the approval authority comprises the application type and the approval nodes, and the approval nodes comprise approval nodes without approval.

In the approval path configuration method, the approver configuration step includes configuring, on the approval nodes that do not need to be approved, the approver that is the same as the previous approval node of the application type corresponding to the approval nodes that do not need to be approved.

According to the approval path configuration method, the approval path generation step comprises the step of generating the approval path through the automatic skipping function of the process engine according to the approval authority and the approver.

According to the approval path configuration method, the approval step comprises the step of approving the document to be approved according to the approval node sequence on the approval path.

The invention also provides an approval path configuration system, which is suitable for the approval path configuration method, and comprises the following steps:

a setting unit: setting an approval authority according to the requirement of the files to be approved;

the approver configuration unit: configuring an approver according to the approval authority;

an approval path generation unit: generating an approval path by using a process engine according to the approval authority and the approver;

an approval unit: and examining and approving the files to be examined according to the examination and approval path.

According to the approval path configuration system, the approval authority comprises the application type and the approval nodes, and the approval nodes comprise approval nodes without approval.

According to the approval path configuration system, the approver configuration unit configures the approver which is the same as the previous approval node of the application type corresponding to the approval node which does not need to be approved on the approval node which does not need to be approved.

According to the approval path configuration system, the approval path generation unit generates the approval path through the automatic skipping function of the process engine according to the approval authority and the approver.

In the approval path configuration system, the approval unit approves the document to be approved according to the order of the approval nodes on the approval path.

Compared with the prior art, the invention provides an approval path configuration method and system, the invention configures the same approver as the previous node of the type through the node without approval during process configuration, utilizes the automatic skipping function of the process engine, does not additionally increase the process line and the process conditions, does not need to integrally consider the process conditions of each path when the process adjustment is changed, only changes the node approval personnel, realizes the approval path configuration requirement, ensures that the approval path configuration principle is simple and easy to understand, has clear process diagram, and greatly reduces the configuration workload.

The details of one or more embodiments of the application are set forth in the accompanying drawings and the description below to provide a more thorough understanding of the application.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

FIG. 1 is a flow chart of an approval path configuration method according to an embodiment of the present application;

FIG. 2 is a prior art approval path configuration flow diagram;

FIG. 3 is a flow diagram of an approval path configuration according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of an approval path configuration system according to the present invention;

fig. 5 is a frame diagram of an electronic device according to an embodiment of the present application.

Wherein the reference numerals are:

a setting unit: 51;

the approver configuration unit: 52;

an approval path generation unit: 53;

an approval unit: 54, a first electrode;

80 parts of a bus;

a processor: 81;

a memory: 82;

a communication interface: 83.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments provided in the present application without any inventive step are within the scope of protection of the present application.

It is obvious that the drawings in the following description are only examples or embodiments of the present application, and that it is also possible for a person skilled in the art to apply the present application to other similar contexts on the basis of these drawings without inventive effort. Moreover, it should be appreciated that such a development effort might be complex and tedious, but would nevertheless be a routine undertaking of design, fabrication, and manufacture for those of ordinary skill having the benefit of this disclosure, and thus should not be construed as a limitation of this disclosure.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of ordinary skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.

Unless defined otherwise, technical or scientific terms referred to herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this application belongs. Reference to "a," "an," "the," and similar words throughout this application are not to be construed as limiting in number, and may refer to the singular or the plural. The present application is directed to the use of the terms "including," "comprising," "having," and any variations thereof, which are intended to cover non-exclusive inclusions; for example, a process, method, system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to the listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Reference to "connected," "coupled," and the like in this application is not intended to be limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as referred to herein means two or more. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, for example, "A and/or B" may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Reference herein to the terms "first," "second," "third," and the like, are merely to distinguish similar objects and do not denote a particular ordering for the objects.

The invention is based on an approval path configuration method and system, and is briefly introduced below.

An Engine (Engine) is a core component of a development program or system on an electronic platform. By using the engine, the developer can quickly establish, lay out the functions required by the program, or utilize the operation of its auxiliary programs. The workflow engine is used for determining information transfer routing, content level and other core solutions which have determination effects on each application system according to different roles, division of labor and conditions. The workflow engine includes important functions of node management, flow direction management, process sample management and the like of the process. The process engine can receive fixed input data under various trigger conditions, automatically execute a series of operations to complete the whole business process, reduce repeated development and improve efficiency. There are three characteristics, the various trigger conditions: to trigger a process, the process may be triggered directly under a variety of conditions, such as adding data, updating data, deleting data, or without any data manipulation. Fixed input data: the process binds a specific data model, and the data structures of all input processes are compatible with the model structure, so that only variables defined in the model can participate in condition judgment in the process. Automatically executing the operation: the flow circulation is automatically carried out without additional coding. The flow engine has the following modules, form design center: the form design center is responsible for designing and configuring forms; form data service: the form data service is responsible for inserting, updating and deleting form data; a form rendering engine: the form rendering engine is responsible for rendering the form designed by the form design center into a front-end page which can be interacted by a user; the center of the process model: the process model center is responsible for designing and configuring the process of the business; a process flow transfer engine: the process flow engine is responsible for converting the process model designed by the process model design center into a specific process example, namely actual task scheduling, wherein personnel allocation is completed; a flow management background: the process management background provides a monitoring function of the process instance, so that the progress can be checked, and the operations of ending an abnormal process or redistributing candidates and the like are performed; the flow center is as follows: the flow center is a list of initiatable flows; a to-do center: the to-do center is responsible for viewing the I's initiation, processing the to-do list, and viewing the list that I have already approved. The process engine can be matched with the form engine to be used in the Baas ecological closed loop, and also provides a standard interface to be used as a strong secondary development platform. The simple use scenario is to use a built-in business module of the Baas, such as a flow center and a proxy center, to complete operations such as initiating a flow and completing a flow task for a simple business. Service development and deployment can be rapidly completed through 0 codes, but the limitation is that only the trigger condition can be new form data, and the flow task has no complex logic. The secondary development and use scene is a service aiming at the fact that a page has a newly added function or the triggering time of a process is changed, and the page has the newly added function: because the default rendering page of the form rendering engine is relatively simple, complex requirements may not be met. Such as adding some other functions, such as menus, breadcrumbs, operation record lists, etc., where the form page requires secondary development, but the form layout and style does not change. There is a change in the trigger timing: the process initiated in the default process center takes the newly added form data as the trigger time, but the trigger time of some services is not the newly added data, and may be triggered when the form data is modified or deleted. The traditional development uses specific complex special services, most complex services can be developed for the second time, and in some cases, for example, in order to be compatible with old third-party pages or customers have special requirements on form layout styles, the whole form page needs to be completely re-developed. The process flow engine provides all complete interfaces required to be used in the process flow life cycle, and can be conveniently accessed. For example, to develop a system, the most critical part is not the interface of the system, nor the information exchange with the database, but how to develop the program logic according to the actual needs and ensure its stability, maintainability (modularization and structurization) and flexibility (it is easy to make changes in the program according to the changes of the actual business logic, such as changes in decision-making right, changes in organization structure and completely new business logic due to changes of business direction, etc.). The Workflow engine solves this problem: if an application lacks a powerful logical layer, it tends to become error-prone (routing errors, dead loops, etc. of information). A service-oriented architecture is a component model that relates different functional units of an application (called services) through well-defined interfaces and contracts between these services. The interface is defined in a neutral manner and should be independent of the hardware platform, operating system and programming language in which the service is implemented. The workflow engine enables services built into various such systems to interact in a unified and universal manner.

Business processes are a series of activities that are performed by different people together to achieve a specific value goal. Not only are the activities strictly defined in sequence, but also the content, manner, responsibility and the like of the activities must be clearly arranged and defined, so that the transfer of different activities between different post roles is possible. There may be a large span in time and space between activities. Whereas a narrowly defined business process is considered to be merely a series of activities associated with the fulfillment of customer value. The business process is a working process formed by orderly process nodes and execution modes. The significance of the business process to the enterprise is not only one description of the key business of the enterprise; the method has guiding significance on business operation of enterprises, and the significance is embodied in optimization of resources, optimization of enterprise organizations and a series of changes of management systems. The business process is hierarchical, and the hierarchy is from top to bottom, from whole to part, from macro to micro, and from abstract to concrete logical relationship. The hierarchical relationship accords with the thinking habits of people and is beneficial to establishing an enterprise business model. Generally speaking, we can establish the overall operation process of the main business process (including the big strategy of the whole enterprise), then refine each activity therein, implement the business process to each department, establish the relatively independent sub business processes and the auxiliary business processes for serving the sub business processes. The hierarchical relationship between the business processes also reflects the hierarchical relationship between the enterprise departments to a certain extent. Departments at different levels have different hierarchical management authorities to the business process. The decision layer, the manager and the user can clearly check the business processes of the subordinate departments. In order to enable the established business process to run more smoothly, the improvement of the business process and the optimization of the enterprise organization structure are mutually restricted and promoted processes.

The invention provides an approval path configuration method and system, wherein an approver with the same type of previous node is configured on a node without approval during process configuration, the automatic skipping function of a process engine is utilized, no additional process line and process conditions are added, if the process adjustment is changed, the process conditions of all paths do not need to be considered integrally, only node approval personnel are changed, the approval path configuration requirement is realized, the approval path configuration principle is simple and easy to understand, the process diagram is clear, and the configuration workload is greatly reduced.

The following describes embodiments of the present application by taking an example of an approval path configuration.

Example one

The embodiment provides an approval path configuration method. Referring to fig. 1 to 3, fig. 1 is a flowchart illustrating an approval path configuration method according to an embodiment of the present disclosure; FIG. 2 is a prior art approval path configuration flow diagram; fig. 3 is a flowchart of an approval path configuration according to an embodiment of the present application, and as shown in the figure, the approval path configuration method includes the following steps:

setting step S1: setting an approval authority according to the requirement of the files to be approved;

approver configuration step S2: configuring an approver according to the approval authority;

approval path generation step S3: generating an approval path by using a process engine according to the approval authority and the approver;

approval step S4: and examining and approving the files to be examined according to the examination and approval path.

In the embodiment, the approval authority comprises an application type and an approval node, and the approval node comprises an approval node which does not need to be approved.

In an embodiment, the approver configuring step S2 includes configuring, on the approval-free node, the approver that is the same as the previous approval node of the application type corresponding to the approval-free node.

In an embodiment, the step S3 of generating the approval path includes generating the approval path through an automatic skip function of the process engine according to the approval authority and the approver.

In an embodiment, the approval step S4 includes approving the document to be approved according to the order of the approval nodes on the approval path.

In a specific implementation, the examination and approval path configuration flow chart is shown in fig. 3 for a scenario described in the following chart.

	Approval node one	Approval node two	Approval node three	Approval node four
					Application type A	Person a	Person a	Person b	Person c
Application type B	Person a	Person d	Person d	Person e
					Application type C	Person a	Person f	Person g	Person g

Summary of service scenarios

The invention configures the approver with the same last node of the type through the node without approval during process configuration, utilizes the automatic skipping function of the process engine without additionally increasing the process line and the process condition, only changes the node approvers without integrally considering the process condition of each path if the process adjustment is changed, realizes the requirement of the approval path configuration, ensures that the approval path configuration principle is simple and easy to understand, has clear process diagram, and greatly reduces the configuration workload.

Example two

Referring to fig. 4, fig. 4 is a schematic structural diagram of an approval path configuration system according to the present invention. As shown in fig. 4, the approval path configuration system according to the present invention is applied to the approval path configuration method described above, and includes:

the setting unit 51: setting an approval authority according to the requirement of the files to be approved;

approver configuration unit 52: configuring an approver according to the approval authority;

approval path generation unit 53: generating an approval path by using a process engine according to the approval authority and the approver;

the approval unit 54: and examining and approving the files to be examined according to the examination and approval path.

In this embodiment, the approval authority includes an application type and an approval node, and the approval node includes an approval node that does not require approval.

In this embodiment, the approver configuring unit 52 configures the approver, which is the same as the previous approver node of the application type corresponding to the approver node without approval, on the approver node without approval.

In this embodiment, according to the approval authority and the approver, the approval path generating unit 53 generates the approval path through an automatic skipping function of the process engine.

In this embodiment, the approval unit 54 approves the document to be approved according to the order of the approval nodes on the approval path.

EXAMPLE III

As shown in FIG. 5, the present embodiment discloses an embodiment of an electronic device. The electronic device may include a processor 81 and a memory 82 storing computer program instructions.

Specifically, the processor 81 may include a Central Processing Unit (CPU), or A Specific Integrated Circuit (ASIC), or may be configured to implement one or more Integrated circuits of the embodiments of the present Application.

Memory 82 may include, among other things, mass storage for data or instructions. By way of example, and not limitation, memory 82 may include a Hard Disk Drive (Hard Disk Drive, abbreviated to HDD), a floppy Disk Drive, a Solid State Drive (SSD), flash memory, an optical Disk, a magneto-optical Disk, tape, or a Universal Serial Bus (USB) Drive or a combination of two or more of these. Memory 82 may include removable or non-removable (or fixed) media, where appropriate. The memory 82 may be internal or external to the approval path configuration device, where appropriate. In a particular embodiment, the memory 82 is a Non-Volatile (Non-Volatile) memory. In particular embodiments, Memory 82 includes Read-Only Memory (ROM) and Random Access Memory (RAM). The ROM may be mask-programmed ROM, Programmable ROM (PROM), Erasable PROM (FPROM), Electrically Erasable PROM (EFPROM), Electrically rewritable ROM (EAROM), or FLASH Memory (FLASH), or a combination of two or more of these, where appropriate. The RAM may be a Static Random-Access Memory (SRAM) or a Dynamic Random-Access Memory (DRAM), where the DRAM may be a Fast Page Mode Dynamic Random-Access Memory (FPMDRAM), an Extended data output Dynamic Random-Access Memory (EDODRAM), a Synchronous Dynamic Random-Access Memory (SDRAM), and the like.

The memory 82 may be used to store or cache various data files for processing and/or communication use, as well as possible computer program instructions executed by the processor 81.

The processor 81 implements the arbitrary approval path configuration method in the above embodiments by reading and executing computer program instructions stored in the memory 82.

In some of these embodiments, the electronic device may also include a communication interface 83 and a bus 80. As shown in fig. 5, the processor 81, the memory 82, and the communication interface 83 are connected via the bus 80 to complete communication therebetween.

The communication interface 83 is used for implementing communication between modules, devices, units and/or equipment in the embodiment of the present application. The communication port 83 may also be implemented with other components such as: and the external equipment, the image/approval path configuration equipment, the database, the external storage, the image/approval path configuration workstation and the like are in data communication.

The bus 80 includes hardware, software, or both to couple the components of the electronic device to one another. Bus 80 includes, but is not limited to, at least one of the following: data Bus (Data Bus), Address Bus (Address Bus), Control Bus (Control Bus), Expansion Bus (Expansion Bus), and Local Bus (Local Bus). By way of example, and not limitation, Bus 80 may include an Accelerated Graphics Port (AGP) or other Graphics Bus, an Enhanced Industry Standard Architecture (EISA) Bus, a Front-Side Bus (FSB), a Hyper Transport (HT) Interconnect, an ISA (ISA) Bus, an InfiniBand (InfiniBand) Interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a microchannel Architecture (MCA) Bus, a PCI (Peripheral Component Interconnect) Bus, a PCI-Express (PCI-X) Bus, a Serial Advanced Technology Attachment (SATA) Bus, a Video Electronics Bus (audio Electronics Association), abbreviated VLB) bus or other suitable bus or a combination of two or more of these. Bus 80 may include one or more buses, where appropriate. Although specific buses are described and shown in the embodiments of the application, any suitable buses or interconnects are contemplated by the application.

The electronic device may be connected to an approval path configuration system to implement the methods described in connection with fig. 1-3.

The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. An approval path configuration method, comprising:

2. The approval path configuration method according to claim 1, wherein the approval authority comprises an application type and an approval node, and the approval node comprises an approval node requiring no approval.

3. The approval path configuration method according to claim 2, wherein the approver configuration step comprises configuring the approver on the approval-free node that is identical to a previous approval node of the application type corresponding to the approval-free node.

4. The approval path configuration method according to claim 1, wherein the approval path generating step includes generating the approval path through an automatic skip function of the process engine according to the approval authority and the approver.

5. The approval path configuration method according to claim 1, wherein the approval step comprises approving the document to be approved according to the order of the approval nodes on the approval path.

6. An approval path configuration system suitable for the approval path configuration method according to any one of claims 1 to 5, the approval path configuration system comprising:

7. The approval path configuration system of claim 6 wherein the approval authority comprises an application type and an approval node, wherein the approval node comprises an approval node that does not require approval.

8. The approval path configuration system according to claim 7, wherein the approver configuring unit configures the approver identical to the previous approval node of the application type corresponding to the approval node requiring no approval on the approval node requiring no approval.

9. The approval path configuration system according to claim 8, wherein the approval path generating unit generates the approval path by an automatic skip function of the process engine according to the approval authority and the approver.

10. The approval path configuration system according to claim 9, wherein the approval unit approves the document to be approved according to the order of the approval nodes on the approval path.