CN117557206A - Flow processing method and device, electronic equipment and readable storage medium - Google Patents
Flow processing method and device, electronic equipment and readable storage medium Download PDFInfo
- Publication number
- CN117557206A CN117557206A CN202310279523.3A CN202310279523A CN117557206A CN 117557206 A CN117557206 A CN 117557206A CN 202310279523 A CN202310279523 A CN 202310279523A CN 117557206 A CN117557206 A CN 117557206A
- Authority
- CN
- China
- Prior art keywords
- callback
- flow
- service system
- center
- http
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 90
- 238000003860 storage Methods 0.000 title claims abstract description 23
- 238000005111 flow chemistry technique Methods 0.000 title claims abstract description 22
- 230000008569 process Effects 0.000 claims abstract description 70
- 238000012545 processing Methods 0.000 claims abstract description 66
- 238000012423 maintenance Methods 0.000 claims description 19
- 230000005856 abnormality Effects 0.000 claims description 15
- 238000011161 development Methods 0.000 abstract description 8
- 238000010586 diagram Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 7
- 238000004590 computer program Methods 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001902 propagating effect Effects 0.000 description 2
- RYGMFSIKBFXOCR-UHFFFAOYSA-N Copper Chemical compound [Cu] RYGMFSIKBFXOCR-UHFFFAOYSA-N 0.000 description 1
- 230000002159 abnormal effect Effects 0.000 description 1
- 229910052802 copper Inorganic materials 0.000 description 1
- 239000010949 copper Substances 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 210000001503 joint Anatomy 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0633—Workflow analysis
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention discloses a flow processing method, a device, electronic equipment and a readable storage medium, wherein the method comprises the following steps: the process center receives a process approval request initiated by a service system; when the state of the flow approval request in the flow center is the finishing state, the flow center calls back an http callback interface of the service system, wherein all flows of the service system correspond to the same http callback interface; after the callback is successful, the flow center returns feedback information to the service system, wherein the feedback information at least comprises a result of flow approval; and the service system calls the processing logic corresponding to the flow according to the feedback information. According to the invention, by setting that all flows of the service system correspond to the same http callback interface, for any flow of the service system, the flow center calls the same http callback interface of the service system, and when a new flow is added in the service system, the interface corresponding to the new flow does not need to be developed in the service system, so that the development cost is reduced.
Description
Technical Field
The present invention relates to the field of flow processing technologies, and in particular, to a flow processing method, a device, an electronic apparatus, and a readable storage medium.
Background
The process approval has diversity, various process configurations are scattered in each service system, and each service system is docked through a process center. The final state interaction of the flow between the flow center and the business system, such as flow withdrawal, flow approval passing, flow rejection and the like, is realized by the way of dubbo api docking. The dubbo interfaces need to be independently developed in each service system, and each flow in the service system corresponds to one dubbo interface. Every time a process is newly added, a corresponding dubbo interface needs to be developed in a service system, the process center needs to be informed of the corresponding dubbo interface of the newly added process, development is also needed at the rear end of the process center to butt joint the dubbo interface of the newly added process, and development cost is high.
Disclosure of Invention
It is an object of the present invention to provide a new solution for flow processing.
According to a first aspect of the present invention, there is provided a flow processing method, the method comprising:
the process center receives a process approval request initiated by a service system;
when the state of the flow approval request in the flow center is an ending state, the flow center calls back an http callback interface of the service system, wherein all flows of the service system correspond to the same http callback interface;
after the callback is successful, the flow center returns feedback information to the service system, wherein the feedback information at least comprises the result of the flow approval;
and the service system calls the processing logic corresponding to the flow according to the feedback information.
Optionally, after the flow center calls back the http callback interface of the service system, the method further includes:
under the condition that callback abnormality is detected, the flow center stores callback information into a callback record failure table, wherein the callback information at least comprises an address of an http callback interface of the service system and the feedback information;
the flow center acquires callback information in the callback record failure table every time a preset time passes;
the flow center carries out callback according to callback information in each callback record failure table;
and after the callback is successful, the flow center deletes the corresponding callback information from the callback record failure table.
Optionally, in the case of detecting the callback exception, storing the callback information to a callback record failure table, including:
under the condition that callback abnormality is detected, the flow center acquires an http state code of a callback result;
under the condition that the http state code is consistent with a preset state code, the flow center stores callback information into a callback record failure table, wherein the callback information at least comprises an address of an http callback interface of the service system and the feedback information;
the process center recalls an http callback interface of the service system under the condition that the http state code is inconsistent with a preset state code;
and under the condition that continuous N times of callback abnormality are detected, storing callback information into a callback record failure table, wherein N is a positive integer.
Optionally, the process center includes an operation and maintenance workbench, and the method further includes:
displaying callback information in the callback record failure table in the operation and maintenance workbench;
the process center receives the selected operation of the user on callback information displayed in the operation and maintenance workbench;
and responding to the selected operation, and performing callback retry by the flow center according to the callback information selected by the user.
Optionally, the service system includes a configuration file, a correspondence between an ID of each flow of the service system and a processing logic corresponding to each flow is stored in the configuration file, and before the service system invokes the processing logic corresponding to the flow according to the feedback information, the method further includes:
and the service system inquires processing logic corresponding to the flow from the configuration file according to the ID of the flow.
Optionally, the method further comprises:
and under the condition of adding a new flow in the service system, correspondingly storing the ID of the new flow and the processing logic corresponding to the new flow in the configuration file.
Optionally, the process center calls an http callback interface of the service system, including:
and the flow center calls an http callback interface of the service system in an http post request mode.
According to a second aspect of the present invention, there is provided a flow processing apparatus, the apparatus comprising:
the receiving module is used for receiving a flow approval request initiated by the service system;
the callback module is used for callback an http callback interface of the service system when the state of the flow approval request in the flow center is an ending state, wherein all flows of the service system correspond to the same http callback interface;
and the sending module is used for returning feedback information to the service system after the callback is successful, so that the service system calls processing logic corresponding to the flow according to the feedback information, wherein the feedback information at least comprises the result of flow approval.
According to a third aspect of the present invention, there is provided an electronic device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps performed by a flow centre in a flow processing method according to the first aspect of the present invention.
According to a fourth aspect of the present invention, there is provided a readable storage medium having stored thereon a program or instructions which, when executed by a processor, implement the steps performed by a flow center in a flow processing method according to the first aspect of the present invention.
According to the method and the device, all flows of the service system correspond to the same http callback interface, for any flow of the service system, the flow center calls the same http callback interface of the service system, and a result of flow approval is returned to the service system.
Other features of the present invention and its advantages will become apparent from the following detailed description of exemplary embodiments of the invention, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a block diagram of a hardware configuration of an electronic device implementing a flow processing method according to an embodiment of the present application.
FIG. 2 is a flow chart of a flow processing method in an embodiment of the present application.
FIG. 3 is a schematic diagram of a process flow of a flow center in an embodiment of the present application.
FIG. 4 is a flow chart of a flow center callback in an embodiment of the present application.
FIG. 5 is a schematic diagram of a flow center callback retry in an embodiment of the present application.
FIG. 6 is a schematic diagram of a flow center callback retry in another embodiment of the present application.
FIG. 7 is a schematic diagram of a flow processing apparatus according to an embodiment of the present application.
Detailed Description
Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless it is specifically stated otherwise.
The following description of at least one exemplary embodiment is merely exemplary in nature and is in no way intended to limit the invention, its application, or uses.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail, but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any specific values should be construed as merely illustrative, and not a limitation. Thus, other examples of exemplary embodiments may have different values.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further discussion thereof is necessary in subsequent figures.
As shown in fig. 1, fig. 1 is a block diagram of a hardware configuration of an electronic device implementing a flow processing method according to an embodiment of the present application. The electronic device 1000 may be a terminal or a server. Further, the terminal may be a headset, a portable computer, a tablet computer, a palm computer, or the like. The server may be a cloud server or the like. The electronic device 1000 may include a processor 1100, a memory 1200, an interface device 1300, a communication device 1400, a display device 1500, an input device 1600, a speaker 1700, a microphone 1800, and so forth. The processor 1100 may be a central processing unit CPU, a microprocessor MCU, or the like. The memory 1200 includes, for example, ROM (read only memory), RAM (random access memory), nonvolatile memory such as a hard disk, and the like. The interface device 1300 includes, for example, a USB interface, a headphone interface, and the like. The communication device 1400 can perform wired or wireless communication, for example. The display device 1500 is, for example, a liquid crystal display, a touch display, or the like. The input device 1600 may include, for example, a touch screen, keyboard, etc. A user may input/output voice information through the speaker 1700 and microphone 1800.
Although a plurality of devices are shown for the electronic apparatus 1000 in fig. 1, the present application may relate to only some of the devices, for example, the electronic apparatus 1000 relates to only the memory 1200 and the processor 1100.
As shown in fig. 2, the present embodiment describes a flow processing method, which includes steps 2100-2400.
Step 2100: and the flow center receives a flow approval request initiated by the service system.
The flow center may interface with multiple business systems. The process center can receive a process approval request initiated by any one business system. The flow approval request contains flow information such as content to be approved, approval expiration time, approver and the like. The process center performs approval aiming at a process approval request initiated by the service system, and a process approval result can be that the process approval passes and the process is rejected. Before the process center approves, the business system can also actively withdraw the process approval request, and the process can also enter a finishing state after withdrawal.
Only one task may be included in one flow. As shown in fig. 3, when the task approval is completed and no new task needs approval, the state of the process in the process center is the finished state.
The process center needs to sequentially examine and approve the plurality of tasks according to the examination and approval sequence. When all tasks in the process pass approval, the state of the process in the process center is the ending state. Or when any task in the process is approved and refused, the state of the process in the process center is the ending state. For example, the process includes task 1, task 2 and task 3, and when all of task 1, task 2 and task 3 pass approval, the process is in a finished state. If task 1 is rejected, then task 2 and task 3 are no longer approved and the process likewise enters the finished state.
Step 2200: when the state of the flow approval request in the flow center is the ending state, the flow center calls back the http callback interface of the service system, wherein all flows of the service system correspond to the same http callback interface.
Each service system is configured with an http callback interface, and all flows of the service system correspond to the http callback interface. And after any flow initiated by the service system is approved by the flow center, the flow center calls an http callback interface of the service system. Each service system can send the address of each http callback interface to the flow center in advance.
In one embodiment, the flow center calls an http callback interface of the service system in the form of an http post request. Security can be improved by means of an http post request.
Step 2300: and after the callback is successful, the flow center returns feedback information to the service system, wherein the feedback information at least comprises the result of the flow approval.
The feedback information is information corresponding to the process approval initiated by the business system. The feedback information includes results of the process approval. The feedback information may also include information such as the time of the procedure approval, the person who is the procedure approval, etc. For one flow, after the approval of the flow center is finished, the flow center generates feedback information and encapsulates the feedback information.
After the http callback interface of the business system is successfully called back by the flow center, the flow center sends feedback information to the business system through the http callback interface of the business system, and the business system is informed of the flow approval result. As shown in fig. 4, the flow center may encrypt the feedback information using the AES encryption algorithm, thereby improving the security of the feedback information.
Step 2400: and the service system calls the processing logic corresponding to the flow according to the feedback information.
After receiving the feedback information, the business system carries out corresponding processing according to the flow approval result. The processing logic corresponding to different flows in the service system is different, and the processing logic corresponding to each flow can be packaged in a class. And after the service system receives feedback information corresponding to a certain flow, the service system calls a class corresponding to the flow and executes processing logic corresponding to the flow.
According to the invention, by setting that all flows of the service system correspond to the same http callback interface, for any flow of the service system, the flow center calls the same http callback interface of the service system, and returns the result of flow approval to the service system, when a flow is newly added in the service system, the interface corresponding to the newly added flow is not required to be developed in the service system, and the development cost is reduced.
When the state of a flow approval request in the flow center is the ending state, the flow center can call back the http callback interface of the service system. If callback abnormality occurs, the state of the process in the business system is still in approval, so that the state of the same process in the business system is inconsistent with the state in the process center, and the system stability is affected. In order to solve the technical problem, after the process center calls back the http callback interface of the service system, the method further comprises steps 3100-3400.
Step 3100: and under the condition that callback abnormality is detected, the flow center stores callback information into a callback record failure table, wherein the callback information at least comprises an address of an http callback interface of the service system and the feedback information.
When the process center calls back the http callback interface of the service system, callback abnormality may occur. Such as network fluctuations, resulting in callback exceptions. When callback abnormality occurs, the http callback interface of the flow center callback service system is indicated to fail, and the service system does not receive feedback information corresponding to the flow. And under the condition, storing callback information of the callback in a callback record table. The callback information comprises the address of the http callback interface of the service system and feedback information corresponding to the flow. And storing callback information of all callback exceptions in a callback record failure list.
If the http callback interface of the flow center callback service system A has callback abnormality, the address and feedback information of the http callback interface of the service system A are stored in a callback record failure table.
Step 3200: and the flow center acquires callback information in the callback record failure table every time a preset time passes.
And after the preset time, the flow center reads all callback information in the callback record failure table. As shown in FIG. 6, the scheduling task may be initiated by the task scheduling platform xxl-job, reading callback information from the callback record failure table every 5 minutes.
Step 3300: and the flow center carries out callback according to the callback information in each callback record failure table.
And aiming at each piece of callback information in the callback record failure table, the flow center performs callback retry. For example, 5 callback information is stored in the callback record failure table, and then the flow center performs callback 5 times.
Step 3400: and after the callback is successful, the flow center deletes the corresponding callback information from the callback record failure table.
If the callback for one piece of callback information is successful, deleting the callback information from the callback record failure table, and returning the corresponding feedback information to the service system. For example, one piece of callback information comprises the address and the feedback information of the http callback interface of the service system A, callback is carried out aiming at the callback information, and the flow center recalls the http callback interface of the service system A. If the callback is successful, deleting the callback information from the callback record failure table, and returning feedback information in the callback information to the service system A.
According to the method and the device, callback information of all callback failures is stored in the callback record failure list, callback retries are conducted on the callback information in the callback failure record list, the condition that the same flow is in a service system is consistent with the condition in a flow center is guaranteed, and system stability is improved.
In this embodiment, step 3100 includes steps 3110-3140.
Step 3110: and under the condition that callback abnormality is detected, the flow center acquires an http state code of a callback result.
As shown in fig. 5, when the callback is abnormal, the flow center acquires an http status code of the callback result. The http status code may reflect the cause of the callback exception.
Step 3120: and under the condition that the http state code is consistent with the preset state code, the flow center stores callback information into a callback record failure table.
As shown in fig. 5, the preset status code is 200. If the http status code obtained by the flow center is 200, the callback request of the flow center is indicated to be received by the service system. But in this case a callback exception still occurs, indicating that the callback exception was not caused by the flow center. And storing callback information corresponding to the callback in a callback record failure table. The callback information comprises the address and feedback information of an http callback interface of the service system which is called back by the service.
Step 3130: and under the condition that the http state code is inconsistent with the preset state code, the flow center recalls an http callback interface of the service system.
If the http status code acquired by the flow center is not 200, the callback request of the flow center is not received by the service system. And under the condition, retrying is carried out, so that the flow center recalls the http callback interface of the service system.
Step 3140: and under the condition that continuous N callback exceptions are detected, the flow center stores callback information into a callback record failure table, wherein N is a positive integer.
Callback retries can be performed using spring-retry techniques, and the number of callback retries can be 3. If all 3 callback retries fail, the corresponding callback information is stored in a callback record failure table.
In one example, a process center receives a process approval request initiated by business system a. After the flow approval passes, the flow center calls an http callback interface of the service system A. Callback abnormality occurs in the process of calling an http callback interface of the service system A by the flow center, and the flow center acquires that the http state code is not 200. In this case, the flow center performs callback retry, and calls the http callback interface of the service system a 3 times again. If the 3 calls fail, the address of the http callback interface of the service system A and the flow approval result are written into a callback record failure table. If one callback is successful in the 3 retries, the flow approval result is directly sent to the service system A, and a callback record failure table does not need to be written.
In this embodiment, the process center includes an operation and maintenance workbench, and the method further includes: displaying callback information in the callback record failure table in the operation and maintenance workbench; the process center receives the selected operation of the user on callback information displayed in the operation and maintenance workbench; and responding to the selected operation, and performing callback retry by the flow center according to the callback information selected by the user.
As shown in fig. 6, a developer in the flow center can view callback information in the callback record failure table through the operation and maintenance workbench. The developer of the flow center can select part of callback information from all callback information displayed by the operation and maintenance workbench, and the flow center retries callback according to the callback information selected by the developer. The developer can also select all callback information displayed in the operation and maintenance workbench.
For example, callback information A, callback information B and callback information C are displayed in the operation and maintenance workbench, a developer selects the callback information A and the callback information B, and then the flow center performs callback retry according to the callback information A and the callback information B.
According to the embodiment, the operation and maintenance workbench is arranged in the flow center, callback information in the callback record failure table is displayed in the operation and maintenance workbench, and manual callback retry can be performed through the operation and maintenance workbench, so that the stability of the system is further improved.
In this embodiment, the service system includes a configuration file, and a correspondence between an ID of each flow of the service system and processing logic corresponding to each flow is stored in the configuration file. Before the business system calls the processing logic corresponding to the flow according to the flow approval result, the method further comprises the following steps: and the service system inquires processing logic corresponding to the flow from the configuration file according to the ID of the flow.
A plurality of processes can be arranged in one business system, and after each process is approved by a process center, the business system can call the processing logic corresponding to the process. Different flows correspond to different processing logic. For the same flow, different approval results of the flow correspond to different processing logic. In the service system, a corresponding processing class can be configured for each flow, and all processing logic corresponding to the flow is encapsulated in the processing class corresponding to the flow. And after the process approval is finished, calling the processing class corresponding to the process to execute the corresponding processing logic according to the process approval result. For example, for the flow a, when the flow a passes the approval, the first processing logic is executed, and when the flow a rejects the approval, the second processing logic is executed, and both the first processing logic and the second processing logic are encapsulated in the processing class corresponding to the flow a. The configuration file of the service system can be maintained by combining the init method of PostConstruct annotation of the Spring framework with the annotation mode.
Setting configuration files in the service system, and storing the IDs of all the processes of the service system and the corresponding relation between the corresponding processing logics in the configuration files. For example, a business system includes a flow a, a flow B and a flow C, all processing logic corresponding to the flow a is encapsulated in a processing class a, all processing logic corresponding to the flow B is encapsulated in a processing class B, and all processing logic corresponding to the flow C is encapsulated in a processing class C. In the configuration file, the flow a corresponds to the processing class a, the flow B corresponds to the processing class B, and the flow C corresponds to the processing class C.
After the business system obtains the flow approval result, the business system inquires the processing logic corresponding to the flow from the configuration file according to the ID of the flow. And then the business system executes corresponding processing logic according to the result of the flow approval.
In one example, the business system initiates approval of the process a to the process center, and the process center returns the approved result to the business system by calling the http callback interface of the business system. And the service system inquires the corresponding processing class as ClassA from the configuration file according to the ID of the flow A, and the service system calls the processing class ClassA to execute the first processing logic.
In one embodiment, the method further comprises: and under the condition of adding a new flow in the service system, correspondingly storing the ID of the new flow and the processing logic corresponding to the new flow in the configuration file.
After a new flow is added in the service system, developing processing logic corresponding to the flow in the service system. For example, a process D is newly added in the service system, so that a class D corresponding to the process D can be developed in the service system, and all processing logic corresponding to the process D is encapsulated in the class D.
And correspondingly storing the ID of the new flow and the processing logic corresponding to the new flow in the configuration file of the service system. For example, a new flow D and a class D corresponding to the flow D are added in the service system.
In the embodiment, by setting the configuration file in the service system, the corresponding relation between the ID of each flow of the service system and the processing logic corresponding to each flow is stored in the configuration file, and when a new flow is added in the service system, only the ID of the new flow and the processing logic corresponding to the new flow are added in the configuration file, so that development of a flow center is not required, and development cost is reduced. Meanwhile, new developers of the service system can maintain the service system conveniently, and development efficiency is improved.
As shown in fig. 7, this embodiment describes a flow processing apparatus 700, which includes:
a receiving module 701, configured to receive a flow approval request initiated by a service system;
the callback module 702 is configured to callback an http callback interface of the service system when the state of the flow approval request in the flow center is an ending state, where all flows of the service system correspond to the same http callback interface;
and the sending module 703 is configured to return feedback information to the service system after the callback is successful, so that the service system invokes processing logic corresponding to the flow according to the feedback information, where the feedback information at least includes a result of approval of the flow.
According to the invention, by setting that all flows of the service system correspond to the same http callback interface, for any flow of the service system, the flow center calls the same http callback interface of the service system, and returns the result of flow approval to the service system, when a flow is newly added in the service system, the interface corresponding to the newly added flow is not required to be developed in the service system, and the development cost is reduced.
Optionally, the apparatus further comprises:
the processing module is used for storing callback information to a callback record failure table under the condition that callback abnormality is detected, wherein the callback information at least comprises an address of an http callback interface of the service system and the feedback information;
the obtaining module is used for obtaining callback information in the callback record failure table by the flow center every time a preset time passes;
the callback retrying module is used for carrying out callback according to the callback information in each callback record failure table;
and the deleting module is used for deleting the corresponding callback information from the callback record failure table after the callback is successful.
Optionally, the processing module is specifically configured to:
under the condition that callback abnormality is detected, acquiring an http state code of a callback result;
storing callback information to a callback record failure table under the condition that the http state code is consistent with a preset state code, wherein the callback information at least comprises an address of an http callback interface of the service system and the feedback information;
re-calling an http callback interface of the service system under the condition that the http state code is inconsistent with a preset state code;
and under the condition that continuous N times of callback abnormality are detected, storing callback information into a callback record failure table, wherein N is a positive integer.
Optionally, the apparatus includes an operation and maintenance workbench, and the apparatus further includes:
the display module is used for displaying callback information in the callback record failure table in the operation and maintenance workbench;
the receiving module is also used for receiving the selected operation of the callback information displayed in the operation and maintenance workbench by a user;
and the callback retry module is also used for responding to the selected operation and performing callback retry according to the callback information selected by the user.
Optionally, the callback module is specifically configured to:
and the flow center calls an http callback interface of the service system in an http post request mode.
This embodiment describes an electronic device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement steps performed by a flow center in a flow processing method according to any of the embodiments of the present invention.
This embodiment describes a readable storage medium having stored thereon a program or instructions which when executed by a processor implement the steps performed by a flow center in a flow processing method according to any of the embodiments of the present invention.
The present invention may be a system, method, and/or computer program product. The computer program product may include a computer readable storage medium having computer readable program instructions embodied thereon for causing a processor to implement aspects of the present invention.
The computer readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: portable computer disks, hard disks, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static Random Access Memory (SRAM), portable compact disk read-only memory (CD-ROM), digital Versatile Disks (DVD), memory sticks, floppy disks, mechanical coding devices, punch cards or in-groove structures such as punch cards or grooves having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media, as used herein, are not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., optical pulses through fiber optic cables), or electrical signals transmitted through wires.
The computer readable program instructions described herein may be downloaded from a computer readable storage medium to a respective computing/processing device or to an external computer or external storage device over a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmissions, wireless transmissions, routers, firewalls, switches, gateway computers and/or edge servers. The network interface card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium in the respective computing/processing device.
Computer program instructions for carrying out operations of the present invention may be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, c++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present invention are implemented by personalizing electronic circuitry, such as programmable logic circuitry, field Programmable Gate Arrays (FPGAs), or Programmable Logic Arrays (PLAs), with state information for computer readable program instructions, which can execute the computer readable program instructions.
Various aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable medium having the instructions stored therein includes an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. It is well known to those skilled in the art that implementation by hardware, implementation by software, and implementation by a combination of software and hardware are all equivalent.
The foregoing description of embodiments of the invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the technical improvement of the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.
Claims (10)
1. A flow processing method, the method comprising:
the process center receives a process approval request initiated by a service system;
when the state of the flow approval request in the flow center is an ending state, the flow center calls back an http callback interface of the service system, wherein all flows of the service system correspond to the same http callback interface;
after the callback is successful, the flow center returns feedback information to the service system, wherein the feedback information at least comprises the result of the flow approval;
and the service system calls the processing logic corresponding to the flow according to the feedback information.
2. The method of claim 1, wherein after the flow center recalls the http callback interface of the business system, the method further comprises:
under the condition that callback abnormality is detected, the flow center stores callback information into a callback record failure table, wherein the callback information at least comprises an address of an http callback interface of the service system and the feedback information;
the flow center acquires callback information in the callback record failure table every time a preset time passes;
the flow center carries out callback according to callback information in each callback record failure table;
and after the callback is successful, the flow center deletes the corresponding callback information from the callback record failure table.
3. The method according to claim 2, wherein in the case of detecting a callback exception, saving the callback information to the callback record failure table comprises:
under the condition that callback abnormality is detected, the flow center acquires an http state code of a callback result;
under the condition that the http state code is consistent with a preset state code, the flow center stores callback information into a callback record failure table, wherein the callback information at least comprises an address of an http callback interface of the service system and the feedback information;
the process center recalls an http callback interface of the service system under the condition that the http state code is inconsistent with a preset state code;
and under the condition that continuous N callback exceptions are detected, the flow center stores callback information into a callback record failure table, wherein N is a positive integer.
4. The method of claim 2, wherein the flow center comprises an operation and maintenance workbench, the method further comprising:
displaying callback information in the callback record failure table in the operation and maintenance workbench;
the process center receives the selected operation of the user on callback information displayed in the operation and maintenance workbench;
and responding to the selected operation, and performing callback retry by the flow center according to the callback information selected by the user.
5. The method of claim 1, wherein the business system includes a configuration file, wherein a correspondence between an ID of each flow of the business system and processing logic corresponding to each flow is stored in the configuration file, and wherein before the business system invokes the processing logic corresponding to the flow according to the feedback information, the method further comprises:
and the service system inquires processing logic corresponding to the flow from the configuration file according to the ID of the flow.
6. The method of claim 5, wherein the method further comprises:
and under the condition of adding a new flow in the service system, correspondingly storing the ID of the new flow and the processing logic corresponding to the new flow in the configuration file.
7. The method of claim 1, wherein the flow center invokes an http callback interface of the business system, comprising:
and the flow center calls an http callback interface of the service system in an http post request mode.
8. A flow processing apparatus, the apparatus comprising:
the receiving module is used for receiving a flow approval request initiated by the service system;
the callback module is used for callback an http callback interface of the service system when the state of the flow approval request in the flow center is an ending state, wherein all flows of the service system correspond to the same http callback interface;
and the sending module is used for returning feedback information to the service system after the callback is successful, so that the service system calls processing logic corresponding to the flow according to the feedback information, wherein the feedback information at least comprises the result of flow approval.
9. An electronic device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, performs the steps performed by a flow center in the flow processing method of any of claims 1-7.
10. A readable storage medium, wherein a program or instructions is stored on the readable storage medium, which when executed by a processor, implements the steps performed by a flow center in a flow processing method according to any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310279523.3A CN117557206A (en) | 2023-03-21 | 2023-03-21 | Flow processing method and device, electronic equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310279523.3A CN117557206A (en) | 2023-03-21 | 2023-03-21 | Flow processing method and device, electronic equipment and readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117557206A true CN117557206A (en) | 2024-02-13 |
Family
ID=89817290
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310279523.3A Pending CN117557206A (en) | 2023-03-21 | 2023-03-21 | Flow processing method and device, electronic equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117557206A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117950766A (en) * | 2024-03-26 | 2024-04-30 | 智道网联科技(北京)有限公司 | Callback processing method and device, callback processing system and electronic equipment |
-
2023
- 2023-03-21 CN CN202310279523.3A patent/CN117557206A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117950766A (en) * | 2024-03-26 | 2024-04-30 | 智道网联科技(北京)有限公司 | Callback processing method and device, callback processing system and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10546052B2 (en) | Structured touch screen interface for mobile forms generation for customer relationship management (CRM) | |
| US9952749B2 (en) | Reproducing state of source environment when image was screen captured on a different computing device using resource location, resource navigation and positional metadata embedded in image | |
| US10630399B2 (en) | Testing distributed applications that have an established exchange in an advanced message queuing protocol (AMQP) message broker | |
| CN110007936B (en) | Data processing method and device | |
| US20180275957A1 (en) | Assistive technology for code generation using voice and virtual reality | |
| CN117557206A (en) | Flow processing method and device, electronic equipment and readable storage medium | |
| TW202030665A (en) | Method and apparatus for displaying digital object identifier | |
| US20160162984A1 (en) | Processing unstructured messages | |
| CN110620806B (en) | Information generation method and device | |
| CN110059064B (en) | Log file processing method and device and computer readable storage medium | |
| US9912572B2 (en) | Decomposing application topology data into transaction tracking data | |
| US20170278031A1 (en) | System and Method for Crisis and Business Resiliency Management | |
| CN116701053B (en) | Method, device, equipment and medium for restoring data backup of production environment database | |
| US9338117B2 (en) | Electronic notification systems and methods | |
| CN112988600A (en) | Service scene testing method and device, electronic equipment and storage medium | |
| CN111105210A (en) | Approval task processing method and device, electronic equipment and storage medium | |
| CN109190876B (en) | Safe access method and device for service product | |
| CN111049883A (en) | Data reading method, device and system of distributed table system | |
| CN112395194B (en) | Method and device for accessing test platform | |
| CN114428815A (en) | Data storage method and device, electronic equipment and computer readable medium | |
| US20140215392A1 (en) | Connections identification | |
| CN111367898A (en) | Data processing method, device, system, electronic equipment and storage medium | |
| CN111147470A (en) | Account authorization method and device and electronic equipment | |
| CN112749073B (en) | Service testing method and device, storage medium and electronic equipment | |
| US10126993B2 (en) | Routing outputs from jobs submitted on a mainframe system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |