CN118245532A

CN118245532A - Service operation processing method, device, computer equipment and storage medium

Info

Publication number: CN118245532A
Application number: CN202410172458.9A
Authority: CN
Inventors: 贾武阳
Original assignee: Kingdee Software China Co Ltd
Current assignee: Kingdee Software China Co Ltd
Priority date: 2024-02-06
Filing date: 2024-02-06
Publication date: 2024-06-25

Abstract

The present application relates to a business operation processing method, apparatus, computer device, storage medium and computer program product. The method comprises the following steps: acquiring target business operation aiming at a published business object; searching a component identifier from a component description table based on a service object type corresponding to the issued service object and an operation identifier corresponding to the target service operation to obtain a component identifier set; based on the processing priority corresponding to the component identifications in the component description table, combining the components respectively corresponding to the component identifications to obtain the service pipeline type corresponding to the issued service object on the target service operation; and processing the operation parameters of the issued service object on the target service operation by the first service pipeline instance obtained by instantiating the service pipeline type to obtain an operation processing result. The method can improve the flexibility of business operation processing.

Description

Service operation processing method, device, computer equipment and storage medium

Technical Field

The present application relates to the field of computer technology, and in particular, to a business operation processing method, apparatus, computer device, storage medium, and computer program product.

Background

With the development of computer technology, when an enterprise manages and analyzes service data through a service model, a component needs to be bound on a service object, and custom service processing logic is injected through a component interface. For example, the business object may be a business document, a visual chart, or the like, that carries business data. When the business operation is triggered on the business object, based on the component bound by the business operation, corresponding data processing is carried out on the business data carried by the business operation, and a processing result is returned.

However, when the conventional method develops the business objects, corresponding components are developed for the business operations corresponding to different business objects according to the requirements of the business objects, the components are bound with the corresponding business operations, and when the business operations are responded, the operation processing is required to be performed according to the components bound by the business operations of the business document, so that the coupling between the components and the business objects is stronger, and the flexibility of the business operation processing is low.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a business operation processing method, apparatus, computer device, computer readable storage medium, and computer program product that can improve the flexibility of business operation processing.

The application provides a business operation processing method. The method comprises the following steps:

acquiring target business operation aiming at a published business object;

Searching a component identifier from a component description table based on a service object type corresponding to the issued service object and an operation identifier corresponding to the target service operation to obtain a component identifier set;

Based on the processing priority corresponding to the component identifications in the component description table, combining the components respectively corresponding to the component identifications to obtain the service pipeline type corresponding to the issued service object on the target service operation;

The service pipeline type is instantiated to obtain a first service pipeline instance, and the operation parameters of the issued service object on the target service operation are processed through the first service pipeline instance to obtain an operation processing result corresponding to the target service operation of the issued service object.

The application also provides a business operation processing device. The device comprises:

The operation acquisition module is used for acquiring target business operation aiming at the issued business object;

The identification acquisition module is used for searching the component identification from the component description table based on the service object type corresponding to the issued service object and the operation identification corresponding to the target service operation to obtain a component identification set;

The pipeline type determining module is used for combining the components respectively corresponding to the component identifications based on the processing priorities corresponding to the component identifications in the component description table in the component identification set to obtain the service pipeline types corresponding to the issued service objects on the target service operation;

the processing module is used for instantiating the service pipeline type to obtain a first service pipeline instance, and processing the operation parameters of the issued service object on the target service operation through the first service pipeline instance to obtain an operation processing result corresponding to the target service operation of the issued service object.

A computer device comprising a memory storing a computer program and a processor implementing the steps of the business operation processing method described above when the processor executes the computer program.

A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the business operation processing method described above.

A computer program product comprising a computer program which, when executed by a processor, implements the steps of the business operations processing method described above.

According to the business operation processing method, the business operation processing device, the computer equipment, the storage medium and the computer program product, the component identification is searched from the component description table by acquiring the target business operation aiming at the issued business object and based on the business object type corresponding to the issued business object and the operation identification corresponding to the target business operation, so that the component identification set is obtained. And combining the components corresponding to the component identifiers respectively based on the processing priorities corresponding to the component identifiers in the component description table to obtain the service pipeline types corresponding to the published objects on the target service operation. And further, processing the operation parameters of the issued service object on the target service operation by the first service pipeline instance obtained by instantiating the service pipeline type to obtain an operation processing result corresponding to the target service operation of the issued service object. When the target service operation is obtained, the corresponding component identifiers are searched in the component description table, and based on the processing priority among the component identifiers recorded in the component description table, the corresponding components are combined and instantiated, so that the service pipeline instance corresponding to the target service operation can be obtained quickly and accurately. The method and the device avoid directly binding the business operation and the component, realize decoupling between the business object and the component, and can enhance the flexibility of business operation processing.

Drawings

FIG. 1 is an application environment diagram of a business operation processing method in one embodiment;

FIG. 2 is a flow chart of a business operation processing method in one embodiment;

FIG. 3 is a flow chart of a business operation processing method in another embodiment;

FIG. 4 is a flow diagram of acquiring a component identification set in one embodiment;

FIG. 5 is a flow chart of a business operation processing method according to another embodiment;

FIG. 6 is a schematic diagram of a business operation processing method in one embodiment;

FIG. 7 is a flow chart of a business operation processing method in another embodiment;

FIG. 8 is a schematic diagram of a business operation processing method according to another embodiment;

FIG. 9 is a block diagram of a business operation processing device in one embodiment;

FIG. 10 is an internal block diagram of a computer device in one embodiment;

fig. 11 is an internal structural view of a computer device in another embodiment.

Detailed Description

The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.

The business operation processing method provided by the embodiment of the application can be applied to the application environment shown in the figure 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, which may be smart televisions, smart car devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be implemented as a stand-alone server or as a server cluster of multiple servers. The terminal 102 and the server 104 may be directly or indirectly connected through wired or wireless communication, and the present application is not limited herein.

The terminal and the server can be used independently for executing the business operation processing method provided in the embodiment of the application.

For example, the terminal obtains a target business operation for the published business object, searches the component identifier from the component description table based on the business object type corresponding to the published business object and the operation identifier corresponding to the target business operation, and obtains a component identifier set. The terminal combines the components corresponding to the component identifiers respectively based on the processing priorities corresponding to the component identifiers in the component description table in the component identifier set to obtain the service pipeline types corresponding to the published service object on the target service operation, and combines the service sub-pipeline types based on the processing sequence among the component types to obtain the service pipeline types corresponding to the published service object on the target service operation. The terminal instantiates the service pipeline type to obtain a first service pipeline instance, and the operation parameters of the issued service object on the target service operation are processed through the first service pipeline instance to obtain an operation processing result corresponding to the target service operation of the issued service object.

In one embodiment, as shown in fig. 2, a service operation processing method is provided, and the method is applied to a computer device, which is a terminal or a server, and is executed by the terminal or the server, or may be implemented through interaction between the terminal and the server. The business operation processing method comprises the following steps:

step S202, a target business operation for the published business object is acquired.

The service object refers to a data model instance corresponding to the service field and is used for describing, organizing and operating data. For example, the business object may be a document, an Excel table, an XML document, or the like. The published service object refers to a service object which is already deployed in the database and is available for use and operation, and in particular, the published service object may refer to one service object or may refer to a plurality of service objects belonging to the same service object type. The business operations are operations indicating various processes and management performed on the business pairs. For example, the business operation may be a business object auditing operation, a business object preservation operation, and the like. The target business operation is a business operation to be processed of the issued business object.

The service object designer creates service objects corresponding to the types of the plurality of service objects respectively, and each service object creates corresponding service operations, so that each service object is published, namely, the service objects are stored in the database, so that a user can view and operate the service objects. The computer equipment obtains target business operation which is triggered by a user and aims at the issued business object.

Step S204, based on the service object type corresponding to the issued service object and the operation identifier corresponding to the target service operation, searching the component identifier from the component description table to obtain a component identifier set.

The service object type refers to a service object type obtained by classifying the service object in order to improve management and processing efficiency of the service object. The implementation methods of the business operations (i.e., business pipeline types) are the same for business operations belonging to the same business object type, and may be different for business operations of different business object types. The operation identifier refers to a unique identifier corresponding to a service operation, and is used for distinguishing different service operations, for example, a service object saving operation and a service object auditing operation respectively correspond to a unique document identifier. Components refer to reusable software units, i.e., software entities with relatively independent functionality that can be independently deployed and assembled, resulting from simple packaging of data and methods. The component identifier refers to a unique identifier corresponding to a component and is used for distinguishing different components. The component description table refers to a descriptive table that records component characteristics respectively corresponding to each component deployed in the operating environment. In particular, the service object type and service operation type to which each component is applicable, the component type to which each component belongs, the processing priority to which each component corresponds, and other component characteristics, for example, whether or not the other component characteristics are asynchronous execution, whether or not to rely on declarations, and the like, may be included. The component identification set refers to a set composed of the searched component identifications.

The computer device searches the corresponding component identifier from the component description table based on the service object type corresponding to the issued service object and the operation identifier corresponding to the target service operation, and obtains a component identifier set. Specifically, firstly, based on a service object type corresponding to a published service object, searching each component identifier aiming at the published service object in a component description table, and further, based on operation identifiers corresponding to target service operations, determining each operation identifier corresponding to the target service operations aiming at the published service object in each searched component identifier, so as to obtain a component identifier set.

In one embodiment, not only can the matched component identification set be looked up through the component description table, but other additional matching bases, such as establishing a text contract, can be set. Corresponding text contracts can be set for each service object type in the component description table, wherein the text contracts refer to predefined rules and conditions for expanding the service object types in the component description table, and a large amount of redundant data are prevented from being recorded in the component description table, so that computer resources are saved. For example, a text contract for business object type a may be that business object types with business object type a_x are each business object types associated with business object type a, sharing component description information corresponding to business object type a in a component description table, where x represents any character string. Searching each component identifier aiming at the released service object in the component description table based on the service object type corresponding to the released service object, and determining the target service object type associated with the service object type of the released service object in the component description table based on the text contract corresponding to each service object type in the component description table when the matched component identifier cannot be searched. And further, based on the operation identifier corresponding to the target service operation, determining each operation identifier corresponding to the target service operation aiming at the issued service object from each component identifier corresponding to the target service object type in the component description table, and obtaining a component identifier set. Similarly, for each operation identifier in the component description table, a corresponding text contract may also be set respectively. By setting the text contract, flexible expansion of the component description table can be realized, and efficiency and flexibility of component matching are improved.

Step S206, based on the processing priority corresponding to the component identifications in the component description table, combining the components corresponding to the component identifications respectively to obtain the service pipeline type corresponding to the issued service object on the target service operation.

The processing priority corresponding to the component identifier refers to the processing sequence corresponding to the component identifier in each component identifier belonging to the same component type. The service pipeline type refers to a complete function class corresponding to the target service operation. The service pipe type is an abstract model describing the basic structure of the service pipe.

The computer device combines the components corresponding to the component identifiers belonging to the same component type based on the processing priorities corresponding to the component identifiers in the component description table, so as to obtain service sub-pipeline types corresponding to the component types related to the component identifier set, and combines the service sub-pipeline types based on the processing sequence among the component types, so as to obtain the service pipeline types corresponding to the issued service object on the target service operation.

Specifically, the computer device obtains the processing priority and the component type respectively corresponding to each component identifier in the component description table. In the process of object-oriented programming, the code implementation of the business operation can be divided into a plurality of independent modules, and each module is a business section, so that specific business functions are independently completed. The components belonging to the same service section and used for realizing the specific service function corresponding to the same service section are components belonging to the same component type. Aiming at each component identifier belonging to the same component type in the component identifier set, the components respectively corresponding to each component identifier belonging to the same component type are combined based on the processing priority corresponding to the component identifier, and the service sub-pipeline type corresponding to the component type is constructed. And determining the service sub-pipeline types corresponding to other component types in the component identification set respectively by the same method. The service sub-pipeline type corresponding to the component type refers to a function class corresponding to a service section to which the component type belongs, and is used for realizing a service function corresponding to the service section to which the component type belongs. The processing sequence among the component types is the sequence among the service sections to which the component types belong. For example, when the code implementation of the service operation is split, three service sections of verification, processing and message are sequentially obtained, the processing sequence among the component types is the verification type, the processing type and the message type. And combining the service sub-pipeline types based on the processing sequence among the component types to construct the service pipeline type corresponding to the issued service object on the target service operation.

Step S208, instantiating the service pipeline type to obtain a first service pipeline instance, and processing the operation parameters of the issued service object on the target service operation through the first service pipeline instance to obtain an operation processing result corresponding to the target service operation of the issued service object.

The pipeline object obtained by instantiating the service pipeline type is a first service pipeline instance, and can be used for executing specific service logic and tasks, namely, for executing target service operations. The operation parameters refer to parameters to be processed carried by the target business operation, and the operation parameters can be context business data, namely parameters for describing a specific business background of a business object or providing additional information, or can be business data to be processed, which are contained in the issued business object and correspond to the target business operation. The operation processing result refers to a result obtained by executing the target business operation.

Illustratively, the computer device instantiates the structured service pipe type to obtain a first service pipe instance. And operating the first service pipeline instance, and operating and processing the operation parameters corresponding to the issued service object on the target service operation through the first service pipeline instance to obtain an operation processing result corresponding to the target service operation of the issued service object. When the operation processing result is obtained through the first service pipeline instance, the first service pipeline instance can be directly recovered, or the first service pipeline instance is marked as a finished state, the service pipeline instance in the finished state is periodically recovered, occupied computer resources are timely released, and the overall performance and the processing efficiency of the computer equipment are improved.

In one embodiment, a hand-in device is bound to a business object, and when an interaction event occurs, the hand-in device is triggered, and business operation processing is initiated through the hand-in device. Specifically, when the business object is a document, as shown in fig. 3, a business document designer creates or designs a business document, and defines an operation type for the business document. And the service bill designer issues the service bill into the operation environment, and after the service bill is issued, a user can open the bill and trigger corresponding bill operation. At this time, the computer equipment calls the cut-in device, the bill type and the operation identifier of the business bill are transmitted into the cut-in device, the cut-in device searches the matched component identifier in the component description table based on the bill type and the operation identifier, and the service pipeline type is constructed according to the processing priority and the component type respectively corresponding to the searched matched component identifier through the component container, and the service pipeline instance corresponding to the service pipeline type is created. And operating the service pipeline instance to obtain an operation processing result corresponding to the bill operation. When the cutting-in device cannot find a matched component in the component container, an empty pipeline is constructed and operates in a default mode, so that the occurrence of abnormality is avoided. The cut-in device is equivalent to a main inlet of service processing bound on a service bill, when the bill operation aiming at the service bill is obtained, the cut-in device is directly called, matched components are searched through the cut-in device, a corresponding service pipeline instance is built based on the searched components, and when the components corresponding to the bill operation are not deployed in an operation environment, the cut-in device builds an empty pipeline, so that abnormal or error reporting is avoided. The abnormal situation caused by the fact that components bound by the bill are not deployed in the running environment in time in the traditional method is solved, and the stability of business operation processing can be improved.

In the service operation processing method, the component identification is searched from the component description table by acquiring the target service operation aiming at the issued service object and based on the service object type corresponding to the issued service object and the operation identification corresponding to the target service operation, so as to obtain the component identification set. And combining the components corresponding to the component identifiers respectively based on the processing priorities corresponding to the component identifiers in the component description table to obtain the service pipeline types corresponding to the published objects on the target service operation. And further, processing the operation parameters of the issued service object on the target service operation by the first service pipeline instance obtained by instantiating the service pipeline type to obtain an operation processing result corresponding to the target service operation of the issued service object. When the target service operation is obtained, the corresponding component identifiers are searched in the component description table, and based on the processing priority among the component identifiers recorded in the component description table, the corresponding components are combined and instantiated, so that the service pipeline instance corresponding to the target service operation can be obtained quickly and accurately. The method and the device avoid directly binding the business operation and the component, realize decoupling between the business object and the component, and can enhance the flexibility of business operation processing.

In one embodiment, as shown in fig. 4, based on the service object type corresponding to the published service object and the operation identifier corresponding to the target service operation, searching the component identifier from the component description table to obtain a component identifier set, including:

In step S402, when the component description table includes component identifiers that match operation identifiers corresponding to both the service object type corresponding to the published service object and the target service operation, a component identifier set is obtained based on each matched component identifier.

In step S404, when the component description table does not include the component identifier that matches the operation identifier corresponding to the operation object type and the target operation corresponding to the issued operation object, the parent operation object corresponding to the target operation object is obtained, and the component identifier that matches the operation identifier corresponding to the operation object type and the target operation corresponding to the parent operation object is searched from the component description table, so as to obtain the component identifier set.

When the target service object is derived based on a certain original service object recorded in the component description table, the original service object corresponding to the target service object is the father service object corresponding to the target service object.

The computer device searches the component description table for each component identifier matched with the service object type corresponding to the issued service object, and further searches the searched component identifiers matched with the operation identifier corresponding to the target service operation to obtain a component identifier set. When the component identification which is matched with the operation identification corresponding to the service object type and the target service operation corresponding to the released service object is not found in the component description table, determining the father service object corresponding to the released service object from the service object attribute information corresponding to the released service object. The service object attribute information may be a piece of parameter information included in the published service object itself, and is used to indicate whether the published service object is a derivative service object and from which service object is derived. And further determining the service object type corresponding to the father service object, searching each component identifier matched with the service object type corresponding to the father service object in the component description table, and further searching the component identifier matched with the operation identifier corresponding to the target service operation in each searched component identifier to obtain a component identifier set.

In the above embodiment, the matching basis of querying the component identifier in the component description table can be flexibly extended based on the derivative relation between the service objects, so as to improve the flexibility of component matching. For the service object derived from the service object type recorded in the component description table, the component description table is not required to be updated, and the corresponding component identifier is queried in the component description table directly based on the service object type corresponding to the father service object corresponding to the service object, so that the maintenance complexity of the component description table can be reduced.

In one embodiment, the business operation processing method further includes:

When the components corresponding to the component identifiers in the component identifier set are not deployed, an empty pipeline instance is constructed, the empty pipeline instance is operated, and retry prompt information is sent to an operation initiator of target service operation; the retry prompt message is used for prompting the operation initiator to trigger the target business operation again after the preset waiting time.

The operation initiator refers to a terminal which triggers the operation of the target service.

Illustratively, in the product development process for continued iteration of the published business object, each time an extension function is newly added in the published business object, various components for implementing the newly added extension function need to be deployed in the execution environment. When each component corresponding to the newly added expansion function is not deployed in the running environment, and the target business operation aiming at the newly added expansion function is obtained, the traditional method can report errors directly due to component missing. In the scheme, when the target business operation is obtained, a component identification set for realizing the business operation is determined, and if components corresponding to the component identifications in the component identification set are not deployed in the running environment, the components corresponding to the newly-added expansion function are not deployed in the running environment in time. At this point, an empty pipe instance is built for the target business operation. The empty pipe instance refers to a service pipe instance including only a function module for transmitting retry prompt information. And running the empty pipeline instance and sending retry prompt information to an operation initiator of the target service operation. The retry prompt message is used to prompt the operation initiator to re-trigger the target service operation after a preset waiting time, which can be set according to actual needs, and is generally determined based on the time required for deploying each component corresponding to the service object into the operation environment.

In one embodiment, when components corresponding to part of component identifications in the component identification set are deployed in the operation environment, an empty pipe instance can be constructed and operated as well until components corresponding to the component identifications in the component identification set are deployed in the operation environment, and a service pipe type corresponding to the published service object on the target service operation is constructed. Under the condition that all components in the component identification set are not completely deployed in the operation environment, by constructing an empty pipeline instance, the abnormity generated in the service object and component release process can be reduced, the reliability of service operation processing is ensured, and smooth deployment is realized.

In one embodiment, in the product development process of continuous iteration for the published service object, the existing functions contained in the published service object can be updated, other sub-functions for perfecting the existing functions are newly added in the existing functions, and components corresponding to the sub-functions are deployed in the running environment. Such as adding a user authentication sub-function to the a-function. When the component corresponding to the newly added sub-function is not deployed in the running environment, and the target service operation for the existing function is acquired, a service pipeline instance containing a function module for sending retry prompt information can be created based on the historical service pipeline type corresponding to the existing function, and the corresponding operation parameters are processed based on the created service pipeline instance to obtain an operation processing result, and the operation processing result and the retry prompt information are returned to the user. Therefore, the abnormity generated in the release process of the business object and the component is reduced, the reliability of business operation processing is ensured, and smooth deployment is realized.

In the above embodiment, the service object is not closely dependent on component operation, and when the service object has been released and each component corresponding to the service object has not been deployed in time into the operation environment, by creating and operating the empty pipeline instance, the problem of dysmorphism and error reporting can be avoided, the problem of unsynchronized release of the service object and deployment of the component can be effectively solved, and the flexibility and reliability of service operation processing can be improved.

In one embodiment, the business operation processing method further includes:

storing the service pipeline type; when the target business operation of the corresponding type of the issued business object is obtained, determining a second business pipeline instance based on the business pipeline type; and processing the operation parameters of the same type of service objects on the target service operation through the second service pipeline instance to obtain an operation processing result corresponding to the target service operation of the same type of service objects.

The service objects of the same type corresponding to the published service objects refer to published service objects which belong to the same service object type as the published service objects.

Illustratively, the computer device stores the service pipe type corresponding to the created published service object on the target service operation. When the target business operation aiming at the business object of the same type corresponding to the issued business object is obtained, firstly checking whether the component description table is updated, if not, determining a second business pipeline instance directly based on the stored business pipeline type, if so, indicating that the stored business pipeline type also needs to be updated, creating a corresponding business pipeline type again based on the business object type corresponding to the issued business object and the operation identifier corresponding to the target business operation, and instantiating the newly created business pipeline type to obtain the second business pipeline instance, thereby ensuring the accuracy and the reliability of business operation processing. And further, according to the second service pipeline instance, the operation parameters of the same type of service objects on the target service operation are processed, and an operation processing result corresponding to the target service operation of the same type of service objects is obtained.

For example, as shown in fig. 3, when the document type and the operation identifier corresponding to the service pipe type are transferred into the cut-in device again, that is, the stored service pipe type is called again, the cut-in device instantiates the stored service pipe type to obtain a corresponding service pipe instance, and the corresponding service processing is executed through the service pipe instance to obtain an operation processing result.

In the above embodiment, the created service pipe type is stored in time, and when the target service operation for the service object of the same type corresponding to the published service object is obtained later, the service pipe instance can be created directly based on the stored service pipe type, so that the service operation processing efficiency is improved.

In one embodiment, determining a second service pipe instance based on the service pipe type includes:

When a first service pipeline instance exists in the pipeline instance container, taking the first service pipeline instance as a second service pipeline instance; the pipeline instance container is used for storing the service pipeline instance after the service pipeline instance is generated and before the operation processing result is obtained based on the service pipeline instance; when the first service pipeline instance does not exist in the pipeline instance container, the service pipeline type is instantiated to obtain a second service pipeline instance.

Illustratively, the pipeline instance container is used to store and manage business pipeline instances, providing operations such as creation, reclamation, querying, etc., ensuring that stored instances are properly created and scheduled. And the first service pipeline instance is obtained by instantiating the service pipeline type for the first time, and can be recovered by the pipeline instance container when the operation is finished, namely the first pipeline instance is removed from the system, and the occupied resources are released. Thus, when determining the service pipe type, the computer device first looks for whether there is an unrecovered first service pipe instance in the pipe instance container. If the first service pipeline instance which is not recovered exists in the pipeline instance container, the first service pipeline instance is used as a second service pipeline instance, and if the first service pipeline instance does not exist in the pipeline instance container, the service pipeline type is instantiated, and the second service pipeline instance is obtained.

In one embodiment, when the business object is a document, the complete flow of business operations processing is shown in FIG. 5. Firstly, when a target bill operation for a current bill is acquired, the computer equipment determines the bill type corresponding to the current bill and an operation identifier corresponding to the target bill operation. And further searching whether a business pipeline type matched with the bill type corresponding to the current bill and the operation identifier corresponding to the target bill operation exists or not. If the matched service pipeline types do not exist, a first component identification set corresponding to the first component type is searched in a component description table according to the bill type and the operation identification, all components in the first component identification set are ordered, and the service sub-pipeline types corresponding to the first component type are constructed. And then searching a second component identification set corresponding to the second component type, sequencing all components in the second component identification set, and constructing the service sub-pipeline type corresponding to the second component type. And continuing to search the component identification set corresponding to the next component type until the service sub-pipeline types corresponding to the component types are obtained, and combining the service sub-pipeline types corresponding to the component types based on the processing sequence table among the component types to obtain the service pipeline types. If the matched service pipeline type exists, checking whether the component description table is updated by the discovery device, and if so, entering the step of searching a first component identification set corresponding to the first component type in the component description table according to the bill type and the operation identification to execute, thereby obtaining the service pipeline type. If no update occurs, further judging whether an idle unrecovered pipeline instance corresponding to the service pipeline type exists in the pipeline instance container, if the idle unrecovered pipeline instance corresponding to the service pipeline type exists, operating the service pipeline instance to perform corresponding operation processing on bill data corresponding to bill operation, and if the idle unrecovered service pipeline instance corresponding to the service pipeline type does not exist, creating the service pipeline instance according to the service pipeline type. And finally, running the service pipeline instance to perform corresponding operation processing on the bill data corresponding to the bill operation, marking the service pipeline instance as a finished state, and recovering the service pipeline instance in the finished state, overtime or abnormal service pipeline instance.

In the above embodiment, the service pipe instance obtained by instantiating the service pipe type is stored through the pipe instance container, when the service pipe instance corresponding to the service pipe type needs to be created again, whether the first unrecovered service pipe instance corresponding to the service pipe type exists is firstly queried in the pipe instance container, if so, the first unrecovered service pipe instance is directly used as the second service pipe instance, so that the efficiency of service operation processing can be improved, and the created service pipe instance can be fully utilized.

In one embodiment, the service data processing method further includes:

Responding to the component discovery request, determining a newly deployed target component, and extracting a service object type, an operation identifier and a processing priority corresponding to the target component from component description information corresponding to the target component; taking the component type of the abstract component class inherited by the target component as the component type corresponding to the target component; and writing the component identifier, the service object type, the operation identifier, the processing priority and the component type corresponding to the target component into a component description table.

The component description information refers to information of the business object type, the operation identifier and the processing priority corresponding to the recording component. The component description information may be hard coded in the component code in an annotated manner, for example, by adding a normalized data structure to the component class header of the program code in a manner commonly used for AOP (Aspect-Oriented Programming, slice-oriented programming) annotation, or may be saved as a separate file, for example, as a json file. The abstract component class is an abstract class used for representing the abstract structure of the component, provides a basic and universal framework, and enables a developer to create the component with the similar structure by inheriting the abstract component type, thereby realizing flexible expansion and customization of the component.

Illustratively, the computer device, in response to the component discovery request, looks up the newly deployed target component in the runtime environment, i.e., the component newly deployed into the runtime environment. The component discovery request may be triggered periodically according to a preset component discovery period, or may be triggered in real time when a component is deployed in an operating environment, and in response to the component discovery request, a component newly added in the operating environment may be discovered in time, so that the component description table is updated based on component description information corresponding to the component newly added in the operating environment. And when the newly deployed target component is determined, extracting the service object type, the operation identifier and the processing priority corresponding to the target component from the component description information corresponding to the target component. Specifically, when the component description information is included in the component code corresponding to the target component, the service object type, the operation identifier and the processing priority corresponding to the target component may be extracted from the component description information carried in the component code corresponding to the target component, or the service object type, the operation identifier and the processing priority corresponding to the target component may be extracted from the file corresponding to the target component and recorded with the component description information. And analyzing the component code corresponding to the target component to obtain an abstract component class inherited by the target component, and taking the component type of the abstract component class inherited by the target component as the component type corresponding to the target component. And recording the component identification, the service object type, the operation identification, the processing priority and the component type corresponding to the target component in a component description table.

For example, as shown in fig. 3, when the service object is a document, the component developer develops the document component, declares the document type and the operation identifier corresponding to the document component, that is, which document types and document operations the document component can use, and declares the corresponding processing priority of the component in the document components of the same type. Specifically, the component developer may hard code the information such as the document type, the operation identifier, the processing priority and the like corresponding to the document component in the component code in an annotating manner, may save the component description information into a single josn file, and may directly record the component description information in the component description table. The component developer in turn deploys the document component in the operating environment of the computer device and triggers a deployment event. The component discovery party triggers a component discovery request in response to the deployment event. Furthermore, the component discovery request may also be automatically triggered upon restarting the computer device. The computer equipment responds to the component discovery request, searches each newly deployed bill component and component description information corresponding to each bill component respectively, and transmits the searched bill components and the component description information corresponding to each bill component respectively to a component discovery party. The component discovery party extracts declaration and global names corresponding to the bill components from the component description information and updates the declaration and global names to the component container. The component container is used to load, manage and execute components, providing lifecycle management, communication and deployment support for the components. The component container extracts the information such as the component type, the operation identification, the processing priority and the like corresponding to the bill component from the component description information, and updates the information to the component description table. In the actual implementation process, the component discovery party, the component container and the cut-in device are all functional modules in the computer equipment, namely, the computer equipment realizes component things, component management and initiates business operation processing.

In the above embodiment, the component description information corresponding to the component is recorded in the program code of the component in an annotated manner, or is directly stored as a separate file. And then, in response to the component discovery request, the component newly added into the running environment is discovered in time, and the component information is updated into the component description table based on the component description information corresponding to the component. The components can be designed independently of the business objects, when the newly added expansion function appears, corresponding components are newly added, and the association relation between the newly added components and the business object types and operation identifiers is recorded through the component description information, so that the existing components are not required to be modified, and the influence caused by modifying the components can be reduced. In the traditional method, the business operation corresponding to the business object is bound with the corresponding component, and the component corresponding to the business operation is not split into finer component modules, so that the reusability of the component is not strong and the maintenance is not easy. In the scheme, the components are designed independently of the business document, the components corresponding to the business operation are split into a plurality of finer components, and the finer components are assembled to obtain complete processing logic corresponding to the business operation, so that the reusability of the components is enhanced. Compared with the traditional method for binding the business object and the component, the method can greatly improve the expansibility and the flexibility of the component. And the component description information is recorded in the component code in an annotating way, so that clear self-description of the accuracy of the component information through self-description declaration is realized.

In one embodiment, the service data processing method further includes:

Acquiring target business operation aiming at a business object set; the service object set comprises a plurality of service object subsets corresponding to the service object types respectively; taking each service object subset as a published service object, entering operation identifiers corresponding to service object types and target service operations based on the published service objects, searching component identifiers from a component description table, and executing the step of obtaining a component identifier set to obtain first service pipeline examples respectively corresponding to each service object subset on the target service operations; and carrying out batch processing on each business object in the business object subset through a first business pipeline instance corresponding to the business object subset on the target business operation, and respectively obtaining operation processing results corresponding to each business object in each business object subset on the target business operation.

The target business operation may be a business operation for a single published business object, or a business operation for a set of business objects, i.e., performing the same business operation for a collection of published business objects. For example, business object auditing operations are performed on individual business objects created on the day. Based on the service object types respectively corresponding to the issued service objects in the service object set, dividing each service object belonging to the same service object type into the same service object subset to obtain service object subsets respectively corresponding to a plurality of service object types. And taking each service object subset as a published service object, entering operation identifiers corresponding to service object types and target service operations based on the published service objects, searching the component identifiers from the component description table, and executing the step of obtaining a component identifier set to obtain first service pipeline examples respectively corresponding to each service object subset on the target service operations. And carrying out batch processing on each business object in the business object subset through a first business pipeline instance corresponding to the business object subset on the target business operation, and respectively obtaining operation processing results corresponding to each business object in each business object subset on the target business operation.

For example, as shown in FIG. 6, the computer device obtains a target business operation (i.e., business event) for a set of business objects, and passes the set of business objects and the target business operation into the hand-in device. The cut-in device divides each business object included in the business object set based on the business object type, and a business object subset corresponding to the business object types can be obtained. And searching the component identification sets respectively corresponding to the service object subsets in the component description table through the component container based on the service object types and the operation types corresponding to the service object subsets. The component container loads corresponding components according to the component identification sets corresponding to the service object subsets, creates service pipeline types corresponding to the service object subsets according to the processing priorities (namely the processing sequence numbers) corresponding to the components in the component identification sets, and instantiates the service pipeline types corresponding to the service object subsets to obtain service pipeline instances corresponding to the service object subsets. The individual business pipe instances are stored in a pipe instance container.

In the above embodiment, by classifying the service object sets to obtain each service object subset, respectively constructing a corresponding service pipeline instance for each service object subset, and performing batch processing on the service object subsets by using the service pipeline instance corresponding to the service object subset, multiple service objects can be processed simultaneously, and processing efficiency is improved. And the differentiation processing, namely pipeline grouping processing, is realized on a large number of business objects belonging to different business object types, and the efficiency of business operation processing is improved.

In one embodiment, the published business object is a published document and the target business operation is a target document operation.

Illustratively, the published business object may be a published document and the target business operation may be a target document operation. The steps of the business operation processing method are shown in fig. 7, and the cut-in device is bound on the issued bill first. And the component developer develops the bill components by taking characteristic processing as a unit, namely developing the bill components respectively corresponding to the types of the components. And creating component description information corresponding to the bill component, wherein the component description information comprises the bill type acted by the bill component, the component description information of corresponding operation identification and processing priority and the component type corresponding to the bill component. Component developers can record component description information in component code in an annotated manner. And further deploy the individual document assemblies into an application system environment of the computer device. The computer equipment scans the newly added bill assembly through the assembly discovery device, extracts assembly description information corresponding to the bill assembly, and updates the assembly description table based on the assembly description information. And the computer equipment responds to the target bill operation aiming at the issued bill, and transmits the bill type corresponding to the issued bill and the operation identifier corresponding to the target bill operation into the cut-in device. The cut-in device searches the matched component identification in the component description table based on the bill type and the operation identification, constructs the service pipeline type according to the processing priority and the component type respectively corresponding to the matched component identification through the component container, and creates a service pipeline instance corresponding to the service pipeline type. And operating the service pipeline instance to obtain an operation processing result corresponding to the bill operation. In the whole, as shown in fig. 8, each document is deployed in a database, each component carrying component description information (i.e. self-description word) is deployed in an operation environment, a discovery device periodically scans the operation environment, extracts declarations and global names corresponding to newly added components, updates the declarations and global names to component containers, the component containers are equivalent to a registration and construction center, can uniformly manage service pipeline types, and constructs service pipeline instances in the operation environment based on each deployed component.

In a specific embodiment, the business operation processing method provided by the application can be applied to a bill management system for processing bill operation. As shown in fig. 7, the business operation processing method includes the steps of:

1. Deployment component

The document management system first binds the cut-in device on the business document. The component developer develops the bill component by taking characteristic processing as a unit, namely develops the bill component corresponding to each component type respectively, and creates component description information corresponding to the bill component, wherein the component description information comprises the bill type acted by the bill component, corresponding operation identification and component description information of processing priority and the component type corresponding to the bill component. Component developers can record component description information in component code in an annotated manner. And further deploy the individual document assemblies into an application system environment of the computer device.

2. Updating component description tables

The bill management system scans newly deployed bill assemblies through the assembly discovery device, extracts assembly description information corresponding to the bill assemblies, updates the assembly description information corresponding to the newly deployed bill assemblies into an assembly description table, extracts declaration and global names corresponding to the bill assemblies from the assembly description information, and updates the declaration and global names into an assembly container.

3. Document operation processing

And the bill management system responds to the target bill operation aiming at the issued service bill, and transmits the bill type corresponding to the service bill and the operation identifier corresponding to the target bill operation into the cut-in device. The cut-in device searches the matched component identification in the component description table based on the bill type and the operation identification, constructs the service pipeline type according to the processing priority and the component type respectively corresponding to the matched component identifications through the component container, and creates the service pipeline instance corresponding to the service pipeline type. And operating the service pipeline instance to obtain an operation processing result corresponding to the bill operation.

In the embodiment, the components are independent of the business document design, are simple and easy to maintain, and if a newly added expansion function appears, the corresponding components are directly added, the existing components are not required to be modified, and the influence caused by modification can be reduced. In the traditional method, corresponding service components are respectively created for different service bills, bill operations corresponding to the service bills are bound with corresponding components, namely one bill operation is bound with one component, and the components corresponding to the bill operations are not split into finer component units, so that the reusability of the components is low, and the components are not easy to maintain. In the scheme, the components corresponding to the bill operation are split more finely, the components corresponding to the multiple component types are split, so that the reusability of the components obtained by splitting is stronger, when a new function needs to be added in the bill operation, the components corresponding to the function can be directly added, the existing components are not required to be modified, the maintainability of a bill management system can be improved, the bill management system is more suitable for a product development process of continuous iteration, and smooth deployment and upgrading can be realized.

It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.

Based on the same inventive concept, the embodiment of the application also provides a service operation processing device for realizing the above related service operation processing method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of one or more service operation processing devices provided below may refer to the limitation of the service operation processing method in the above description, which is not repeated here.

In one embodiment, as shown in fig. 9, there is provided a business operation processing apparatus, including: an operation acquisition module 902, an identification acquisition module 904, a pipe type determination module 906, and a processing module 908, wherein:

An operation obtaining module 902 is configured to obtain a target business operation for a published business object.

The identifier obtaining module 904 is configured to search the component identifier from the component description table based on the service object type corresponding to the published service object and the operation identifier corresponding to the target service operation, so as to obtain a component identifier set.

The pipeline type determining module 906 is configured to combine components corresponding to the component identifiers respectively based on the processing priorities corresponding to the component identifiers in the component description table in the component identifier set, so as to obtain a service pipeline type corresponding to the published service object on the target service operation.

The processing module 908 is configured to instantiate a service pipeline type to obtain a first service pipeline instance, and process, through the first service pipeline instance, an operation parameter of the published service object on the target service operation to obtain an operation processing result corresponding to the target service operation of the published service object.

In one embodiment, the identification acquisition module 904 is further configured to:

When the component description table comprises component identifiers matched with the operation identifiers corresponding to the service object types and the target service operations corresponding to the issued service objects at the same time, obtaining a component identifier set based on the matched component identifiers; when the component description table does not comprise the component identifiers matched with the operation identifiers corresponding to the service object types and the target service operations corresponding to the issued service objects, the father service object corresponding to the target service object is obtained, and the component identifiers matched with the operation identifiers corresponding to the service object types and the target service operations corresponding to the father service object are searched from the component description table, so that a component identifier set is obtained.

In one embodiment, the service operation processing device further comprises a prompt module, wherein the prompt module is used for constructing an empty pipeline instance, running the empty pipeline instance and sending retry prompt information to an operation initiator of target service operation when components corresponding to each component identifier in the component identifier set are not deployed respectively; the retry prompt message is used for prompting the operation initiator to trigger the target business operation again after the preset waiting time.

In one embodiment, the processing module 908 is further to:

In one embodiment, the service operation processing device further includes a component description table maintenance module, where the component description table maintenance module is configured to determine a newly deployed target component in response to a component discovery request, and extract, from component description information corresponding to the target component, a service object type, an operation identifier, and a processing priority corresponding to the target component; taking the component type of the abstract component class inherited by the target component as the component type corresponding to the target component; and writing the component identifier, the service object type, the operation identifier, the processing priority and the component type corresponding to the target component into a component description table.

In one embodiment, the processing module 908 is further to:

According to the service operation processing device, the target service operation aiming at the issued service object is obtained, and the component identification is searched from the component description table based on the service object type corresponding to the issued service object and the operation identification corresponding to the target service operation, so that the component identification set is obtained. And combining the components corresponding to the component identifiers respectively based on the processing priorities corresponding to the component identifiers in the component description table to obtain the service pipeline types corresponding to the published objects on the target service operation. And further, processing the operation parameters of the issued service object on the target service operation by the first service pipeline instance obtained by instantiating the service pipeline type to obtain an operation processing result corresponding to the target service operation of the issued service object. When the target service operation is obtained, the corresponding component identifiers are searched in the component description table, and based on the processing priority among the component identifiers recorded in the component description table, the corresponding components are combined and instantiated, so that the service pipeline instance corresponding to the target service operation can be obtained quickly and accurately. The method and the device avoid directly binding the business operation and the component, realize decoupling between the business object and the component, and can enhance the flexibility of business operation processing.

The above-described respective modules in the business operation processing device may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.

In one embodiment, a computer device is provided, which may be a server, and the internal structure of which may be as shown in fig. 10. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is used for storing data such as component identification sets, component description tables and the like. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a business operation processing method.

In one embodiment, a computer device is provided, which may be a terminal, and the internal structure thereof may be as shown in fig. 11. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a business operation processing method. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.

It will be appreciated by persons skilled in the art that the structures shown in FIGS. 10 and 11 are block diagrams of only some of the structures associated with the present inventive arrangements and are not limiting of the computer device to which the present inventive arrangements may be implemented, and that a particular computer device may include more or fewer components than shown, or may be combined with certain components, or may have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having stored therein a computer program, the processor implementing the steps of the method embodiments described above when the computer program is executed.

In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, implements the steps of the method embodiments described above.

In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps in the above-described method embodiments.

It should be noted that, the user information (including but not limited to user equipment information, user personal information, etc.) and the data (including but not limited to data for analysis, stored data, presented data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party, and the collection, use and processing of the related data need to comply with the related laws and regulations and standards of the related country and region.

Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magneto-resistive random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.

The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.

The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims

1.A business operation processing method, the method comprising:

acquiring target business operation aiming at a published business object;

searching a component identifier from a component description table based on the service object type corresponding to the issued service object and the operation identifier corresponding to the target service operation to obtain a component identifier set;

Based on the processing priority corresponding to the component identifications in the component description table, combining the components corresponding to the component identifications respectively to obtain the service pipeline type corresponding to the issued service object on the target service operation;

instantiating the service pipeline type to obtain a first service pipeline instance, and processing the operation parameters of the issued service object on the target service operation through the first service pipeline instance to obtain an operation processing result corresponding to the target service operation of the issued service object.

2. The method according to claim 1, wherein the searching the component identifier from the component description table based on the service object type corresponding to the published service object and the operation identifier corresponding to the target service operation to obtain the component identifier set includes:

When the component description table comprises component identifiers matched with the service object types corresponding to the issued service objects and the operation identifiers corresponding to the target service operations at the same time, obtaining a component identifier set based on the matched component identifiers;

and when the component description table does not comprise the component identifiers which are matched with the service object types corresponding to the issued service objects and the operation identifiers corresponding to the target service operation at the same time, acquiring the father service object corresponding to the target service object, and searching the component identifiers which are matched with the service object types corresponding to the father service object and the operation identifiers corresponding to the target service operation at the same time from the component description table to obtain a component identifier set.

3. The method according to claim 1, wherein the method further comprises:

When the components corresponding to the component identifiers in the component identifier set are not deployed, an empty pipeline instance is constructed, the empty pipeline instance is operated, and retry prompt information is sent to an operation initiator of the target service operation; the retry prompt message is used for prompting the operation initiator to trigger the target business operation again after the preset waiting time.

4. The method according to claim 1, wherein the method further comprises:

Storing the service pipeline type;

When the target business operation of the corresponding type of business object aiming at the issued business object is obtained, determining a second business pipeline instance based on the business pipeline type;

and processing the operation parameters of the same type of service objects on the target service operation through the second service pipeline instance to obtain an operation processing result corresponding to the target service operation of the same type of service objects.

5. The method of claim 4, wherein the determining a second service pipe instance based on the service pipe type comprises:

When a first service pipeline instance exists in the pipeline instance container, the first service pipeline instance is used as a second service pipeline instance; the pipeline instance container is used for storing the service pipeline instance after the service pipeline instance is generated and until an operation processing result is obtained based on the service pipeline instance;

When the first service pipeline instance does not exist in the pipeline instance container, the service pipeline type is instantiated to obtain a second service pipeline instance.

6. The method according to claim 1, wherein the method further comprises:

responding to a component discovery request, determining a newly deployed target component, and extracting a service object type, an operation identifier and a processing priority corresponding to the target component from component description information corresponding to the target component;

taking the component type of the abstract component class inherited by the target component as the component type corresponding to the target component;

And writing the component identifier, the service object type, the operation identifier, the processing priority and the component type corresponding to the target component into the component description table.

7. The method according to any one of claims 1-6, further comprising:

acquiring target business operation aiming at a business object set; the service object set comprises a plurality of service object subsets corresponding to the service object types respectively;

Taking each service object subset as a published service object, entering the operation identifier corresponding to the service object type and the target service operation based on the published service object, searching the component identifier from the component description table, and executing the step of obtaining a component identifier set to obtain a first service pipeline instance corresponding to each service object subset on the target service operation;

And carrying out batch processing on each business object in the business object subset through a first business pipeline instance corresponding to the business object subset on the target business operation to respectively obtain operation processing results corresponding to each business object in each business object subset on the target business operation.

8. A business operation processing device, characterized in that the device comprises:

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 7 when the computer program is executed.

10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 7.