CN110348803A - Cooperate with approval system - Google Patents

Abstract

The invention provides a collaborative approval system. Collaborative approval system, including: enterprise data service bus, used to receive business data, adapt the business data to the corresponding front-end database, and send the business data to the corresponding front-end database; multiple front-end databases , are respectively connected to the enterprise data service bus, and the front-end database is used to receive and store business data; multiple approval units are connected to multiple front-end databases one by one, and the approval unit is used to obtain data from the corresponding front-end database Read the business data in to approve the business data. The collaborative approval system provided by the present invention can efficiently solve the problem of cross-system data sharing through the mode of "enterprise data service bus + front-end database", realize scalability, data traceability, and easy troubleshooting of wrong data.

Description

Collaborative Approval System

technical field

The invention relates to the technical field of electronic government affairs, in particular to a collaborative approval system.

Background technique

In software development, it is often encountered that the data of various departments is connected, and collaborative approval is handled for some businesses. For example, the collaborative approval system involves the handling of more than 400 items in 16 functional departments, requiring "one-window acceptance, parallel processing, and responsibility-based supervision." , Whole-process supervision' to promote efficient, transparent, and scientific project supervision. If the government departments and business system suppliers in various urban areas are inconsistent, the system architecture, data structure, and systematization level are inconsistent, the cost of communication and coordination is high, and various departments coordinate approval , The implementation of data sharing is difficult to imagine.

The existing technical solution adopts the message queue activemq to realize data sharing and synchronization, and the collaborative approval system puts the relevant information of the receipt into the message queue, and opens the interface to each committee and bureau, and each committee and bureau reads the information of the message queue, and then Analytical data. Although this technical solution is simple and easy to implement, it has the following disadvantages:

1. The error data is not easy to track, the message queue hangs up, and the data will be lost;

2. Unable to send large attachments, causing the message queue to freeze;

3. All committees, offices and bureaus need to write interfaces to read message queue data, which increases the coupling of the system.

In order to meet the above situation, related technologies use WebService to realize data sharing through remote procedure call (RPC). However, due to the two-way sharing of data in the collaborative approval system, the collaborative approval system provides WebService interfaces to the commissions, offices, and bureaus, and the commissions, offices, and bureaus also provide data interfaces for platform calls. Too many services are not conducive to management, and the coupling of the system is greatly increased. Large, the wrong data is not easy to troubleshoot.

Contents of the invention

The present invention aims to solve at least one of the technical problems existing in the prior art or related art.

Therefore, one aspect of the present invention is to propose a collaborative approval system.

In view of this, the present invention proposes a collaborative approval system, including: an enterprise data service bus for receiving business data, adapting the business data to the corresponding front-end database, and sending the business data to the corresponding front-end Set-up database; multiple front-end databases are respectively connected to the enterprise data service bus, and the front-end database is used to receive and store business data; multiple approval units are connected to multiple front-end databases one by one, and the approval The unit is used to read business data from the corresponding front-end database to approve the business data.

According to the collaborative approval system of the present invention, the enterprise data service bus is a key part of the infrastructure used when constructing SOA solutions based on service-oriented architecture, and is a group of infrastructure functions that are implemented by middleware technology and support SOA. The information exchange service bus iESB and digital iETL work together. The front-end database is the database of each collaborative approval department (committee, office and bureau). The enterprise data service bus is connected to each front-end database, and all synchronous collaboration, adaptation and distribution, and integration optimization related to the collaborative approval system are all dispatched through the enterprise data service bus. Specifically, the user submits an application for approval through the online service hall, and the collaborative approval system receives the documents. The business data to be approved enters the collaborative approval system, and the attachments enter the file system. The collaborative approval system calls the enterprise data service bus. After receiving the business data, it passes The iESB adapts the business data to the department it belongs to, which may be one department or multiple departments, and pushes the business data to the front-end database of the department through the specified delivery interface, and connects to the front-end database through the The approval unit reads business data and approves it. The collaborative approval system provided by the present invention realizes unified receipt, cross-system distribution, and collaborative approval through the mode of "enterprise data service bus + front-end database", which greatly improves the efficiency of collaborative approval by various committees, offices, and bureaus. Moreover, each committee office has a dedicated database docking to avoid excessive data volume, guarantee system performance, and high scalability. If more committee offices are added, only the front-end database needs to be added. In addition, the coupling degree of the system is basically No, there are no restrictions on the implementation technologies of the systems of the various commissions and bureaus.

In the above technical solution, preferably, the enterprise data service bus is also used to set the identification of the first flag when sending the business data to the corresponding front-end database; the approval unit is also used to check the business data Before the step of approval, it is judged whether the identifier of the first flag is the first preset identifier, and if so, the business data is approved.

In this technical solution, the business data is sent to the front-end database of the department, and the identification of the first marking position is set, so that after the approval unit reads the business data, it can be based on the identification of the first identification. Determine whether the business data has been consumed, or whether the enterprise data service bus has initiated a new business process. Specifically, when the identifier of the first identification bit is the first preset identifier, it means that the business data has not been consumed. At this time, the approval unit can approve the business data, thereby avoiding repeated approval and making the business data It can be tracked, and the cause of the error can be quickly located in a complex environment, and various departments will not shirk their responsibilities in the collaborative process, which further improves the efficiency of the collaborative approval of various committees, offices, and bureaus.

In any of the above technical solutions, preferably, the enterprise data service bus is also used to perform polling every first preset time length to check whether there is any business data that fails to be delivered, and if so, to deliver it again.

In this technical solution, the enterprise data service bus polls every first preset time, checks the business data that failed to be delivered, and re-delivers, thereby forming a timing reissue mechanism, avoiding the failure of business data delivery and affecting collaboration Approval progress.

In any of the above technical solutions, preferably, the approval unit is also used to write back the approval result to the corresponding front-end database, and set the identification of the second flag; the enterprise data service bus is specifically used to Perform one polling for two preset durations, read the data whose second flag is the second preset flag in each front-end database, and write back the approval result to the database of the collaborative approval system according to the agreed flag.

In this technical solution, the approval unit writes back the approval result to the corresponding front-end computer database, and sets the write-back flag, specifically including the second flag and the agreed mark of the approval result, the second flag When the flag is the second preset flag, it means that the business data has been approved. The enterprise data service bus polls once every second preset time length through iETL, reads the data that has been approved, and reads the agreement of the approval result mark, write back the corresponding approval result to the database of the collaborative approval system, and further display the approval result in the collaborative approval system. The collaborative approval system provided by the present invention can efficiently solve the problem of cross-system data sharing through the mode of "enterprise data service bus + front-end database" combined with iESB and IETL technologies, and realize scalability, data traceability, Easy to troubleshoot wrong data.

In any of the above technical solutions, preferably, the examination and approval results include any one or a combination of the following: whether to pass, supplementary materials, and supplementary materials.

In this technical solution, the approval unit conducts the approval after obtaining the business data to be approved, or if the data is found to be incomplete or incorrect, it will initiate business processes such as supplementary submission of materials, supplementary materials, etc., and finally according to the previously agreed signs, the The approval results are written back to the front-end database.

In any of the above technical solutions, preferably, the first preset duration ranges from 5 to 10 minutes.

In this technical solution, the range of the first preset duration is 5 to 10 minutes, but is not limited thereto.

In any of the above technical solutions, preferably, the second preset duration ranges from 10 minutes to 20 minutes.

In this technical solution, the second preset duration ranges from 10 minutes to 20 minutes, but is not limited thereto.

In any of the above technical solutions, preferably, the enterprise data service bus is also used to send the pre-set delivery data table and write-back data table to each front-end database before the step of receiving business data; The issued data table at least includes: the first flag and its corresponding logo, the second flag and its corresponding logo; the write-back data table at least includes: the first flag and its corresponding logo, the second flag and its corresponding Corresponding logos, approval results and their corresponding agreed signs.

In this technical solution, the preparatory work of the present invention needs to design the table structure of the front-end computer database according to the situation of collaborative business, and issue the same set of data tables to all committees, offices, and bureaus, including sending them from the collaborative approval system to each committee. The data sheets issued by the offices and bureaus, as well as the write-back data sheets reported from the commissions, offices, and bureaus to the collaborative approval system. Each table has the first flag and its corresponding logo and the second flag and its corresponding logo to agree on the marking rules for data read and unread; in addition, the write-back data table also includes approval results, such as approval Approval, approval failure, supplementary materials, etc., as well as the agreed signs corresponding to the approval results. For example, each table has JHFLAG_IN and JHFLAG_OUT write-back flag fields. It is agreed that JHFLAG_IN=0 means that the Commission has not read this data; JHFLAG_IN=1 means that the Commission has consumed this record; JHFLAG_OUT=0 means collaboration The approval system has not read this record yet, and JHFLAG_OUT=1 indicates that the enterprise service bus has consumed this processing result record; the present invention uses the unified definition of the enterprise data service bus to issue the agreement, and all committees, offices and bureaus abide by it, and mark the data status to Judging whether the data has been consumed, or a new business process has been initiated, greatly improves the efficiency of data exchange between various committees, offices and bureaus.

In any of the above technical solutions, preferably, the issued data table further includes any one or a combination of the following: acceptance serial number, original business serial number, approval item number, approval item name, specified processing time limit, acceptance unit name, The code of the application unit, the name of the applicant of the application unit, the name of the person responsible for the application unit, and the time of acceptance; the write-back data sheet also includes any of the following items or a combination: acceptance serial number, original business serial number, approval item number, and completion person Name, closing time.

In this technical solution, the issued data sheet includes but is not limited to any of the following or a combination thereof: acceptance serial number, original business serial number, approval item number, approval item name, prescribed processing time limit, acceptance unit name, application unit code , the name of the applicant of the application unit, the name of the person responsible for the application unit, and the time of acceptance; the write-back data sheet includes but is not limited to any of the following or a combination: acceptance serial number, original business serial number, approval item number, and name of the person in charge , Closing time. By designing the same set of table structures, uniformly defining and issuing agreements, all commissions, offices and bureaus abide by it, so that business data can be traced, and the cause of positioning errors can be quickly checked in complex environments, and various departments will not shirk their responsibilities in coordination.

In any of the above technical solutions, preferably, the front-end database is a Mysql database.

In this technical solution, the front-end database is a Mysql database, but not limited thereto.

Additional aspects and advantages of the invention will become apparent in the description which follows, or may be learned by practice of the invention.

Description of drawings

The above and/or additional aspects and advantages of the present invention will become apparent and comprehensible from the description of the embodiments in conjunction with the following drawings, wherein:

FIG. 1 shows a schematic diagram of a collaborative approval system according to an embodiment of the present invention;

Fig. 2 shows a schematic diagram of a collaborative approval system according to a specific embodiment of the present invention.

Detailed ways

In order to understand the above-mentioned purpose, features and advantages of the present invention more clearly, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be noted that, in the case of no conflict, the embodiments of the present application and the features in the embodiments can be combined with each other.

In the following description, many specific details are set forth in order to fully understand the present invention. However, the present invention can also be implemented in other ways different from those described here. Therefore, the protection scope of the present invention is not limited by the specific details disclosed below. EXAMPLE LIMITATIONS.

As shown in FIG. 1 , it is a schematic diagram of a collaborative approval system according to an embodiment of the present invention. Wherein, the collaborative approval system 100 includes:

The enterprise data service bus 102 is used to receive business data, adapt the business data to the corresponding front-end database 104, and deliver the business data to the corresponding front-end database 104;

A plurality of front-end databases 104 are respectively connected to the enterprise data service bus 102, and the front-end databases 104 are used to receive and store business data;

A plurality of approval units 106 are connected to a plurality of front-end databases 104 in one-to-one correspondence, and the approval unit 106 is used to read business data from the corresponding front-end database 104 to approve the business data.

In the collaborative approval system 100 provided by the present invention, the enterprise data service bus 102 is a key part of the infrastructure used when constructing SOA solutions based on service-oriented architecture, and is a group of infrastructure functions that are implemented by middleware technology and support SOA. It is composed of information exchange service bus iESB and digital iETL. The front-end database 104 is the database of each collaborative approval department (committee office). The enterprise data service bus 102 is connected to each front-end database 104 , and all synchronous collaboration, adaptation distribution, and integration optimization related to the collaborative approval system 100 are generally dispatched through the enterprise data service bus 102 . Specifically, the user submits an application for approval through the online service hall, and the collaborative approval system 100 receives the application. The business data to be approved enters the collaborative approval system 100, and the attachments enter the file system. The collaborative approval system 100 invokes the enterprise data service bus 102, and receives the business After the data is collected, the business data is adapted to the department through iESB, which may be one department or multiple departments, and the business data is pushed to the front-end database 104 of the department through the specified delivery interface. The approval unit 106 connected to the machine database 104 reads and approves business data. The collaborative approval system provided by the present invention realizes unified receipt, cross-system distribution, and collaborative approval through the mode of "enterprise data service bus + front-end database", which greatly improves the efficiency of collaborative approval by various committees, offices, and bureaus. In addition, each committee office has a dedicated database docking to avoid excessive data volume, guarantee system performance, and high scalability. If more committee offices are added, only the front-end database 104 needs to be added. In addition, the coupling degree of the system Basically none, there are no restrictions on the implementation technologies of the systems of various committees, offices and bureaus.

In one embodiment of the present invention, preferably, the enterprise data service bus 102 is also used to set the identification of the first flag when sending the business data to the corresponding front-end database 104; the approval unit 106 is also Before the step of approving the business data, it is used to judge whether the identifier of the first flag is the first preset identifier, and if so, to approve the business data.

In this embodiment, the business data is sent to the front-end database 104 of the department, and the identification of the first flag is set, so that after the approval unit 106 reads the business data, it can , to determine whether the business data has been consumed, or the enterprise data service bus 102 has initiated a new business process. Specifically, when the identifier of the first identifier is the first preset identifier, it means that the business data has not been consumed. At this time, the approval unit 106 can approve the business data, thereby avoiding repeated approval and making the business The data can be tracked, and the cause of the error can be quickly located in a complex environment. The collaborative handling of various departments will not cause each other to shirk their responsibilities, which further improves the efficiency of the collaborative approval of various committees, offices and bureaus.

In one embodiment of the present invention, preferably, the enterprise data service bus 102 is also used to perform polling every first preset time length to check whether there is any business data that failed to be delivered, and if so, to re-deliver .

In this embodiment, the enterprise data service bus 102 polls once every first preset time length, checks the business data that failed to be delivered, and re-delivers, thereby forming a timing reissue mechanism, avoiding the failure of delivering business data and affecting Coordinate approval progress.

In one embodiment of the present invention, preferably, the approval unit 106 is also used to write back the approval result to the corresponding front-end database 104, and set the identification of the second flag; the enterprise data service bus 102 is specifically used to Carry out polling every second preset time length, read the data whose second flag in each front-end processor database 104 is the second preset flag, and write back the approval result to the collaborative approval system according to the agreed flag database.

In this embodiment, the approval unit 106 writes back the approval result to the corresponding front-end processor database 104, and sets the write-back flag, specifically including the second flag and the agreed flag of the approval result, the second flag When the flag of the bit is the second preset flag, it means that the business data has been approved, and the enterprise data service bus 102 polls once every second preset time length through iETL, reads the data that has been approved, and reads the approved data. The agreed sign of the result writes back the corresponding approval result to the database of the collaborative approval system, and further displays the approval result in the collaborative approval system. The collaborative approval system 100 provided by the present invention can efficiently solve the problem of cross-system data sharing through the mode of "enterprise data service bus + front-end database" combined with iESB and IETL technologies, and realize scalability, data traceability, Easy to troubleshoot wrong data.

In an embodiment of the present invention, preferably, the approval result includes any one or a combination of the following: whether to pass, supplementary materials, supplementary materials.

In this embodiment, after obtaining the business data to be approved, the approval unit 106 conducts the approval, or finds that the data is incomplete or incorrect, and then initiates business processes such as supplementary submission of materials, supplementary materials, etc., and finally according to the pre-agreed sign, Write back the approval result to the front-end database 104.

In an embodiment of the present invention, preferably, the first preset duration ranges from 5 to 10 minutes.

In this embodiment, the first preset duration ranges from 5 to 10 minutes, but is not limited thereto.

In an embodiment of the present invention, preferably, the second preset duration ranges from 10 minutes to 20 minutes.

In this embodiment, the second preset duration ranges from 10 minutes to 20 minutes, but is not limited thereto.

In one embodiment of the present invention, preferably, the enterprise data service bus 102 is also used to deliver the pre-set delivery data table and write-back data table to each front-end processor before the step of receiving business data Database 104; the issued data table at least includes: the first flag and its corresponding logo, the second flag and its corresponding logo; the write-back data table at least includes: the first flag and its corresponding logo, the second flag bit and its corresponding identification, approval result and its corresponding agreed sign.

In this embodiment, the preparatory work of the present invention needs to design the table structure of the front-end computer database 104 according to the situation of the collaborative business, and issue the same set of data tables to each committee, office and bureau, including from the collaborative approval system 100 to each committee. The data sheet issued by the office and bureau, and the write-back data sheet reported to the collaborative approval system 100 by each committee, office, and bureau. Each table has the first flag and its corresponding logo and the second flag and its corresponding logo to agree on the marking rules for data read and unread; in addition, the write-back data table also includes approval results, such as approval Approval, approval failure, supplementary materials, etc., as well as the agreed signs corresponding to the approval results. For example, each table has JHFLAG_IN and JHFLAG_OUT write-back flag fields. It is agreed that JHFLAG_IN=0 means that the Commission has not read this data; JHFLAG_IN=1 means that the Commission has consumed this record; JHFLAG_OUT=0 means collaboration The approval system has not read this record, and JHFLAG_OUT=1 indicates that the enterprise service bus has consumed this processing result record; the present invention uniformly defines and issues agreements through the enterprise data service bus 102, and all committees, offices and bureaus abide by it, and pass the flag data status To judge whether the data has been consumed, or a new business process has been initiated, which greatly improves the efficiency of data exchange between various committees, offices and bureaus.

In one embodiment of the present invention, preferably, the issued data table also includes any one or a combination of the following: acceptance serial number, original business serial number, approval item number, approval item name, specified processing time limit, and acceptance unit name , the code of the application unit, the name of the applicant of the application unit, the name of the person responsible for the application unit, and the time of acceptance; the write-back data sheet also includes any of the following items or a combination: acceptance serial number, original business serial number, approval item number, settlement The name of the person and the closing time.

In this embodiment, the issued data table includes but is not limited to any of the following or a combination thereof: acceptance serial number, original business serial number, approval item number, approval item name, prescribed processing time limit, acceptance unit name, application unit code , the name of the applicant of the application unit, the name of the person responsible for the application unit, and the time of acceptance; the write-back data sheet includes but is not limited to any of the following or a combination: acceptance serial number, original business serial number, approval item number, and name of the person in charge , Closing time. By designing the same set of table structures, uniformly defining and issuing agreements, all commissions, offices and bureaus abide by it, so that business data can be traced, and the cause of positioning errors can be quickly checked in complex environments, and various departments will not shirk their responsibilities in coordination.

In an embodiment of the present invention, preferably, the front-end database 104 is a Mysql database.

In this embodiment, the front-end database 104 is a Mysql database, but it is not limited thereto.

A specific embodiment, as shown in FIG. 2 , provides a collaborative approval system, including: a pre-examination unit, an enterprise data service bus, four front-end databases, and four commissioning and bureau systems.

Among them, the enterprise data service bus is a key part of the infrastructure used when building SOA solutions based on service-oriented architecture. It is a set of infrastructure functions implemented by middleware technology and supports SOA. It is composed of iESB and iETL. work. The front-end computer database is the Mysql database of each neighborhood committee office system. The collaborative approval system is connected to the other four commissioning and bureau systems through the enterprise data service bus. All synchronous collaboration, adaptation and distribution, and integration optimization related to the collaborative approval system are all dispatched through the enterprise data service bus. The enterprise data service bus drives data delivery (from the collaborative approval system to the committees, offices and bureaus) and reporting (from the committees, offices and bureaus to the collaborative approval system) through iESB event-driven, polling, etc., data cleaning, conversion, Loading is achieved through iETL, which in turn is dispatched by the Enterprise Data Service Bus.

The preparatory work of the embodiment of the present invention needs to designate an interface for sending and reporting according to the needs of collaborative services. According to the business situation, design the table structure of the front-end computer database, and issue the same set of database tables to each committee, office and bureau. Each table has JHFLAG_IN and JHFLAG_OUT write-back flag fields. It is agreed that JHFLAG_IN＝0 means that the committee has not read this data; JHFLAG_IN＝1 means that the committee has consumed this record; JHFLAG_OUT＝0 means that the collaborative approval system This record has not been read yet, JHFLAG_OUT=1 indicates that the enterprise service bus has consumed this processing result record, and the unified definition of the distribution agreement, all committees, offices and bureaus abide by it, and judge whether the data has been consumed by marking the data status, or A new business process was initiated. The following collaborative approval system will issue data sheets, and the approval systems of various committees, offices and bureaus will write back the data sheets:

Table 1 Release data table

Table 2 write back data table

The specific implementation plan of the collaborative approval business is as follows:

1. The user submits an approval application through the online service hall, and the pre-examination unit receives the application and conducts a pre-examination. After the pre-examination is passed, the business data enters the database of the collaborative approval system, and the attachment enters the file system;

2. The collaborative approval system calls the iESB interface of the enterprise data service bus, adapts the business data to the department through the iESB, pushes the business data to the corresponding front-end computer database of the committee, office, and bureau through the delivery interface, and sets the marking bit, and the The receiving information is sent to the front-end computer of the commission office;

3. Each committee, office and bureau system reads the items to be approved from their corresponding front-end computers, and then approves them, or if they find that the materials are incomplete, they initiate businesses such as resubmitting materials, supplementing and correcting, etc., and finally write the results back to the front-end computers. And set the flag position;

4. The enterprise data service bus polls and reads the front-end processors of all committees, offices and bureaus through iETL every 5 minutes, reads the data of JHFLAG_OUT=0, the enterprise service bus passes the agreed flag, and judges that the data is the result of approval, supplementary materials, Complete the corrections, write back to the collaborative approval system database, and display in the collaborative approval system;

5. The enterprise data service bus iESB polls once every 10 minutes, checks the data that failed to be delivered, and sends it again.

Since then, business data has implemented a process, as shown in Figure 2.

Compared with the prior art, the present invention has the following beneficial effects:

1. Greatly improved the efficiency of data exchange between committees, offices and bureaus. Each committee, office, and bureau has a dedicated database connection, the amount of data will not be too large, and the performance is guaranteed;

2. The data can be traced, and the cause of positioning errors can be quickly checked in a complex environment, and the coordination of various departments will not cause each other to shirk responsibility. In addition, if the data delivery fails, there is a timing reissue mechanism;

3. There is basically no coupling degree of the system, and there are no restrictions on the implementation technology of the system of various committees and bureaus;

4. High scalability. If you add more committees and bureaus, you only need to add a database front-end processor.

In the present invention, the terms "first" and "second" are only used for the purpose of description, and should not be understood as indicating or implying relative importance; the term "plurality" means two or more. Those of ordinary skill in the art can understand the specific meanings of the above terms in the present invention according to specific situations.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. a kind of collaboration approval system characterized by comprising

The business datum is fitted to corresponding front end processor database for receiving business datum by business data service bus, And the business datum is issued to corresponding front end processor database；

Multiple front end processor databases, are connected with the business data service bus respectively, and the front end processor database is used In receiving and storing the business datum；

Multiple examination & approval units connect one to one with multiple front end processor databases, and the examination & approval unit is used for from corresponding The business datum is read in front end processor database, to examine to the business datum.

2. collaboration approval system according to claim 1, which is characterized in that

The business data service bus is also used to the business datum being issued to corresponding front end processor database When, the mark of the first mark of setting position；

The examination & approval unit, was also used to before the step of examining to the business datum, judged first mark position Identify whether as the first default mark, if so, being examined to the business datum.

3. collaboration approval system according to claim 1, which is characterized in that

The business data service bus is also used to carry out a poll every the first preset duration, has checked whether to issue mistake The business datum lost, if so, then re-issuing.

4. collaboration approval system according to claim 1, which is characterized in that

The examination & approval unit is also used to for approval results being written back to corresponding front end processor database, and the second mark position is arranged Mark；

The business data service bus, be specifically used for every the second preset duration carry out a poll, read it is each it is described before The data for being identified as the second default mark for setting the second mark position described in machine database, according to promissory marker, by the examination & approval As a result it is written back to the database of the collaboration approval system.

5. collaboration approval system according to claim 4, which is characterized in that

Whether the approval results include any one of following or combinations thereof: passing through, hand in material, correction material retroactively.

6. collaboration approval system according to claim 3, which is characterized in that

The range of first preset duration: 5 to 10 minutes.

7. collaboration approval system according to claim 4, which is characterized in that

The range of second preset duration: 10 minutes to 20 minutes.

8. collaboration approval system according to any one of claim 1 to 7, which is characterized in that

The business data service bus will be pre-set down before being also used to the reception business datum the step of Hair tables of data and write-back table are issued to each front end processor database；

It is described to issue tables of data and include at least: the first mark position and its corresponding mark, the second mark position and its corresponding mark Know；

The write-back table includes at least: first mark position and its it is corresponding mark, second mark position and its it is corresponding mark, Approval results and its corresponding promissory marker.

9. collaboration approval system according to claim 8, which is characterized in that

The tables of data that issues further includes any one of following or combinations thereof: accepting serial number, former business serial number, examination and approval procedure and compiles Number, examination and approval procedure title, regulation handle the time limit, accept organization, applying unit coding, applying unit's applicant's title, Shen Please unit finish name claim, handling time；

The write-back table further includes any one of following or combinations thereof: accepting serial number, former business serial number, examination and approval procedure and compiles Number, finish people's name, finish the time.

10. collaboration approval system according to any one of claim 1 to 7, which is characterized in that

The front end processor database is Mysql database.