CN115292418B - Cross-system business process automatic processing method and system - Google Patents
Cross-system business process automatic processing method and system Download PDFInfo
- Publication number
- CN115292418B CN115292418B CN202211001038.1A CN202211001038A CN115292418B CN 115292418 B CN115292418 B CN 115292418B CN 202211001038 A CN202211001038 A CN 202211001038A CN 115292418 B CN115292418 B CN 115292418B
- Authority
- CN
- China
- Prior art keywords
- data
- service
- target
- source
- business
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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
-
- 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/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Abstract
The invention discloses a cross-system business process automation processing method and a system, wherein the method comprises the following steps: when a configuration request is received, determining a source service system and a target docking system according to the configuration request; modeling a source service system object and a target docking system object according to the source service system and the target docking system; acquiring service data associated with a source service system from a service system management module; determining a data processing rule according to the service data, and mapping the source service system object data into target docking system object data based on the data processing rule so that the data structure of the service data is adapted to the data structure of the target data; and writing the target data into the target docking system through the business process arranged by the execution engine to synchronize the data of the source business system to the target docking system, so as to achieve the aim of executing the automatic process.
Description
Technical Field
The invention relates to the technical field of computer data processing, in particular to a cross-system business process automatic processing method and system.
Background
With the rapid development of SaaS software industry, more and more business systems are used in enterprises, such as CRM (Customer Relationship Management ), OA (Office Automation, office automation), ERP (Enterprise Resource Planning ), and other system management software. Data inside an enterprise is distributed among various systems, and the data structures of business processes among the business systems have differences, so that synchronization is needed. At present, when the business processes of different systems are synchronous, the cross-system business process automation processing efficiency is low.
Disclosure of Invention
The embodiment of the application aims to improve the cross-system business process automatic processing efficiency by providing the cross-system business process automatic processing method and the cross-system business process automatic processing system.
The embodiment of the application provides a cross-system business process automatic processing method which is applied to a cross-system business process automatic processing system, wherein the cross-system business process automatic processing system comprises a business system management module, a design platform and an execution engine; the cross-system business process automation processing method comprises the following steps:
when the design platform receives a first configuration request, determining a source service system and a target docking system according to the first configuration request;
Acquiring service data associated with the source service system from the service system management module;
determining a data processing rule according to the service data, and mapping the service data into target data of the target docking system based on the data processing rule so that a data structure of the service data is adapted to a data structure of the target data;
and writing the target data into the target docking system through the execution engine so that the data of the source service system can be synchronized to the target docking system.
Optionally, before the step of determining the source service system and the target docking system according to the first configuration request when the design platform receives the first configuration request, the method further includes:
when the service system management module receives a second configuration request, determining a source service system, a product version and a functional module associated with the source service system according to the second configuration request;
acquiring a first metadata table associated with the source service system based on the source service system, the product version and a functional module associated with the source service system;
according to the first metadata table, mapping of the service object associated with the source service system and the API object associated with the source service system is completed;
And encapsulating the mapping relation between the service object associated with the source service system and the API object associated with the source service system into an interface encapsulation module, and associating the interface encapsulation module with the source service system.
Optionally, the step of completing mapping between the service object associated with the source service system and the API object associated with the source service system according to the first metadata table includes:
acquiring a business object associated with the source business system from the first metadata table;
acquiring a first field name and a first field path of the service object, and a second field name and a second field path of a sub-service object associated with the service object;
acquiring first service data associated with the first field name from the first field path and second service data associated with the second field name from the second field path, the first service data and the second service data including enterprise information, vendor information and product information;
mapping of the service object to an API object associated with the source service system is accomplished based on the first service data and the second service data.
Optionally, before the step of determining the source service system and the target docking system according to the first configuration request when the design platform receives the first configuration request, the method further includes:
when the business system management module receives a third configuration request, determining a target docking system, a product version and a functional module associated with the target docking system according to the third configuration request;
acquiring a second metadata table associated with the target docking system based on the target docking system, the product version and a functional module associated with the target docking system;
according to the second metadata table, mapping between the business object associated with the target docking system and the API object associated with the target docking system is completed;
and packaging the mapping relation between the business object associated with the target docking system and the API object associated with the target docking system into an interface packaging module, and associating the interface packaging module with the target docking system.
Optionally, the step of acquiring service data associated with the source service system from the service system management module includes:
acquiring an interface encapsulation module associated with the source service system from the service system management module;
And obtaining the service data associated with the source service system according to the interface packaging module associated with the source service system.
Optionally, the step of determining a data processing rule according to the service data and mapping the service data to target data of the target docking system based on the data processing rule includes:
determining a data source field according to a field name associated with service data of the source service system;
determining a data processing rule corresponding to the data source field, wherein the data processing rule comprises at least one of data mapping processing, cleaning processing, splitting processing, merging processing, statistical processing and comparison processing;
and carrying out data conversion on the business data based on the data structure of the target docking system based on the data processing rule to obtain target data adapted to the target docking system.
Optionally, after the step of determining a data processing rule according to the service data and mapping the service data to the target data of the target docking system based on the data processing rule, the data structure of the service data is adapted to the data structure of the target data, the method further includes:
Performing data debugging on the target data, wherein the data debugging comprises single-node debugging, single-scene debugging and multi-scene scheduling operation;
executing the step of writing the target data into the target docking system through the execution engine when the target data is successfully debugged, so that the data of the source service system can be synchronized to the target docking system;
the step of writing the target data to the target docking system by the execution engine includes:
the execution engine determining data nodes and data relationships based on the target data;
a directed acyclic graph is generated based on the data nodes and the data relationships to write the target data to the target docking system.
Optionally, after the step of writing the target data into the target docking system by the execution engine, the method further includes:
the execution engine generates data synchronization information when writing the target data into the target docking system, and feeds back the data synchronization result to the design platform;
and displaying the data synchronization result on the design platform.
Optionally, after the step of writing, by the execution engine, the target data to the target docking system to enable the data of the source service system to be synchronized to the target docking system, the method further includes:
When the design platform receives a query request, determining a query condition according to the query request;
acquiring associated data matched with the query condition from a storage module;
and displaying the associated data on a display interface of the design platform.
In addition, in order to achieve the above object, the present invention also provides a cross-system business process automation processing system, which includes:
the configuration module is used for determining a source service system and a target docking system according to a first configuration request when the design platform receives the first configuration request;
the acquisition module is used for acquiring service data associated with the source service system from the service system management module;
the mapping module is used for determining a data processing rule according to the service data and mapping the service data into target data of the target docking system based on the data processing rule so that a data structure of the service data is adapted to a data structure of the target data;
and the synchronization module is used for writing the target data into the target docking system through an execution engine so that the data of the source service system can be synchronized to the target docking system.
The technical scheme of the cross-system business process automatic processing method and the system provided by the embodiment of the application has at least the following technical effects or advantages: when the design platform receives the first configuration request, the source service system and the target docking system are determined according to the configuration request, service data associated with the source service system are acquired from the service system management module, data processing rules are determined according to the service data, the data structure of the service data of the source service system is converted according to the data structure of the target docking system based on the corresponding data processing rules, the service data is mapped into the target data of the target docking system, after the target data is acquired, the target data is written into the target docking system through the execution engine, and therefore the technical scheme of cross-system service process automation processing between the data of the source service system and the target docking system is achieved.
Drawings
FIG. 1 is a flow chart of a first embodiment of a cross-system business process automation processing method of the present invention;
FIG. 2 is a schematic flow chart of a business system management module according to the present invention;
FIG. 3 is a schematic diagram of a data processing flow in the design platform of the present invention;
FIG. 4 is a schematic flow chart before step S110 in a first embodiment of a cross-system business process automation processing method according to the present invention;
FIG. 5 is a schematic diagram of a refinement process of step S130 in a first embodiment of a cross-system business process automation processing method according to the present invention;
FIG. 6 is a flow chart of a second embodiment of the cross-system business process automation processing method of the present invention;
FIG. 7 is a functional block diagram of a cross-system business process automation processing system of the present invention.
The achievement of the objects, functional features and advantages of the present application will be further described with reference to embodiments, with reference to the accompanying drawings, which are only illustrations of one embodiment, but not all of the inventions.
Detailed Description
In order to improve the efficiency of cross-system business process automation processing, the present application provides a cross-system business process automation processing method, because the cross-system business process automation processing method adopts a technical scheme that when a design platform receives a first configuration request, a source business system and a target docking system are determined according to the configuration request, business data associated with the source business system are obtained from a business system management module, data processing rules are determined according to the business data, the data structure of the business data of the source business system is converted by the data structure of the target docking system based on the corresponding data processing rules, the business data is mapped into the target data of the target docking system, and after the target data is obtained, the target data is written into the target docking system through an execution engine, so that the cross-system business process automation processing between the data of the source business system and the target docking system is realized. Not only can the cross-system business process automation processing among different systems be realized, but also the cross-system business process automation processing efficiency is improved.
In order that the above-described aspects may be better understood, exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
First embodiment.
As shown in fig. 1, in a first embodiment of the present application, the cross-system business process automation processing method of the present application includes the following steps:
step S110, when the design platform receives a first configuration request, the source service system and the target docking system are determined according to the first configuration request.
In this embodiment, the cross-system business process automatic processing method is applied to a cross-system business process automatic processing system, and the cross-system business process automatic processing method runs on terminal equipment, where the terminal equipment includes, but is not limited to, a notebook computer, a desktop computer, a mobile phone, and the like. The cross-system business process automatic processing method can be executed on the terminal equipment through a webpage, an applet or an APP. For example, the design platform of the application can be visually displayed on the web page end, and functions such as configuration, debugging, inquiry and the like are performed in the design platform.
Optionally, the cross-system business process automation processing system of the application comprises a business system management module, a design platform and an execution engine.
Optionally, the service system management module is mainly used for managing the whole life cycle of the service system, including analyzing and packaging the objects of the source service system, including data input and audit of the source service system, API object modeling, service object packaging mapping, interface packaging module configuration, debugging, testing, publishing and warehousing, and the like. Specifically, the functions of the service system management module include, but are not limited to, the following functions:
data entry function of source business system: and inputting and managing enterprise information, manufacturer information, product information and the like related to the source business system.
API object modeling: packaging the IT information related to the API such as connection information, interface object, request/response parameter, authentication, encryption, unique identification, data type and the like into an API metadata structure;
modeling a business object: and managing 'window objects/fields', 'operation methods', 'data objects', 'association relations', and modeling the objects according to the business model. And mapping of the business object and the API object is completed, and IT attribute business and data object business are achieved.
Interface encapsulation module configuration: and managing the templates of the request and the response. The method is used for constructing request and response models and supporting different design habits and styles.
Referring to fig. 2, the main process flow of the service system management module is as follows: source business system interface, source business system data input, approval, API object modeling, business object mapping, template configuration, auditing, data debugging, interface debugging and release version. In the processing flow, API object modeling can be performed only when approval passes, and data debugging can be performed only when the approval passes, so that the accuracy in the cross-system business flow automatic processing and system docking process is improved.
Optionally, the main function of the design platform is to perform service configuration of different systems, including a source service system to be docked, a target docking system, service data related to the source service system, and the like. The metadata analyzed by the service system management module can be utilized to realize code-free flexible configuration on the visual page, and finally the scene model with the configuration completed is pushed to the execution engine. Specifically, on a design platform, different source service systems have different system configuration parameters to be filled, and flexible configuration is provided on a page for filling by users. According to the metadata information analyzed by the interface database, according to different integration requirements of enterprises, data processing processes of different modes, such as complex data processing processes of data merging, data splitting, data increasing and the like, can be completed, and a scene model is obtained. And pushing the completed scene model to an execution engine. Specifically, the functions of the design platform include, but are not limited to, the following functions:
Project scheme management: the perfect scheme planning process management and control comprises data object combing, scene flow perfection, business system planning, parameter comparison configuration, dry person management and version control.
Project task management: the method has the advantages that the roles are divided and the tasks are distributed clearly, the design planning, the implementation delivery, the debugging test and the online operation and maintenance are separated from functions, and the visual design platform is utilized to organically integrate all the parts together.
And (3) flow design: the visual 'flow workbench' realizes the design of information such as a business system, a scene, nodes, conditions, parameters, contrast and the like;
the modeling thought is adopted, and an 8-big model (an object model, a reading model, a mapping model, a storage model, a writing model, a query model, a condition model and a return model) of a design platform is externally provided through a model workbench; analyzing the log information returned by the engine, and displaying the final synchronous result in a platform, so that the final terminal user can conveniently check the log information; the data mapping, cleaning, splitting, merging, statistics, comparison and other rule configuration work is completed through a rule workbench;
Debugging & testing: the platform provides three operation modes of single-node debugging, single-scene testing and multi-scene scheduling operation; the execution condition of each step can be found through debugging; the circulation condition of each piece of data can be compared through testing; the process can be automatically executed according to the service requirement through scheduling.
Referring to fig. 3, the main execution flow of the design platform sequentially includes: flow design, scheme management, task management, system planning, scene design, node configuration, object modeling, model configuration, rule configuration, single-point testing, scene testing and publishing. By performing the above operations on the design platform, interfacing between different systems and synchronization of data between different systems is achieved.
Optionally, the execution engine is mainly used for running the scene model after receiving the configured scene model, so as to realize operations such as automatic reading, data processing and writing of data. Optionally, the execution engine mainly includes the following functions:
API engine: receiving an instruction of a design platform, generating a DAG graph model according to a flow model generated by the design platform and business system metadata, and performing reading and writing operations on a source interface and a target interface;
A data engine: receiving an instruction of a design platform, processing data according to an 8-big model and a data processing rule generated by the design platform, recording the data through a data table, a data version table and a data link table, and tracking the data blood-edge relationship between upstream and downstream;
specifically, the source service system can be a third party system such as Wanli cattle and Ji Keyun, an interface packaging module of the third party system is stored in the service system management module, and the interface data module can be called to realize the butt joint of the third party system and the cross-system service flow automatic processing system. The target docking system is a system to be docked by the source service system, and also docks the cross-system service flow automatic processing system. The target docking system may be a system preset by the design platform, and the source service system may be a service system connected to the target docking system before or a source service system not connected to the target docking system before. When the source service system is a service system connected with the target docking system before, a corresponding scene model exists, and the synchronization of the data between the source service system and the target docking system can be realized directly based on the scene model. When the source service system is not the service system connected with the target docking system before, namely, a corresponding scene model does not exist, when a configuration request is received, the source service system and the target docking system are determined based on the configuration request, and then the construction of the scene model is realized according to the follow-up steps.
In this embodiment, when the design platform receives the first configuration request, it may be that the design platform receives the first configuration request when detecting that the configuration page is entered. It may also be that the first configuration request is received when it is detected that any control on the configuration page is triggered. And when the first configuration request is received, acquiring the configured content according to the first configuration request. Under an application scenario, when cross-system business process automation processing between two systems is to be realized, a source business system and a target docking system need to be determined first. Thus, upon receiving the first configuration request, the source business system and the target docking system are determined based on the first configuration request.
Alternatively, the business system management module may receive a configuration request from the source business system. Optionally, referring to fig. 4, before the step of determining the source service system and the target docking system according to the first configuration request when the design platform receives the first configuration request, the method further includes:
step S210, when the service system management module receives a second configuration request, determining a source service system, a product version and a function module associated with the source service system according to the second configuration request;
Step S220, a first metadata table associated with the source service system is obtained based on the source service system, the product version and a functional module associated with the source service system;
and step S230, mapping the service object associated with the source service system and the API object associated with the source service system is completed according to the first metadata table.
In this embodiment, when the service system management module receives the second configuration request, the source service system, the product version and the function module associated with the source service system may be determined based on the second configuration request, and the first metadata table associated with the source service system may be acquired based on the source service system, the product version and the function module associated with the source service system; and mapping the service object associated with the source service system and the API object associated with the source service system according to the first metadata table.
Wherein, the first metadata table stores a business object associated with the source business system and all fields associated with the business object. A business object associated with the source business system may be obtained from the first metadata table. Alternatively, a first field name and a first field path associated with the business object may be obtained, and first business data associated with the first field name may be obtained from the first field path. For example, after the first metadata table is obtained, a first field name associated with a business object, such as "platform bill" in the first metadata table may be a platform ID, a store number, a status, a type, an association ticket number, a payment ticket number, revenue, and the like. Each field has a corresponding field path, and the field path is used for representing the source of service data corresponding to the field. The required field can be selected from the field names according to the actual scene requirement, and further the service data associated with the field names can be acquired according to the field paths of the selected fields. By the method, the service data of different service objects of the source service system service can be obtained. The first business data comprises enterprise information, manufacturer information and product information. After the first business data is acquired, mapping of the business object to the API object of the source business system may be completed based on the first business data.
Optionally, there are a plurality of sub-service objects in each service object, and the second field name and the second field path of the sub-service object associated with the service object may be further acquired, and the second service data associated with the second field name may be acquired from the second field path. The second service data may include enterprise information, manufacturer information, product information, and the like. After the second service data is acquired, mapping of the sub-service object to the API object of the source service system may be completed based on the second service data.
Alternatively, after the first service data and the second service data are acquired, mapping of the service object and the API object associated with the source service system may be completed based on the first service data and the second service data at the same time.
Step S240, packaging the mapping relationship between the service object associated with the source service system and the API object associated with the source service system into an interface packaging module, and associating the interface packaging module with the source service system.
In this embodiment, after mapping of the service object and the API object associated with the source service system is completed based on the first service data and the second service data, the mapping relationship between the service object associated with the source service system and the API object associated with the source service system may be encapsulated into an interface encapsulation module, and the interface encapsulation module is associated with the source service system, so that when the first configuration request is received at the design platform, the interface encapsulation module associated with the service object of the source service system may be acquired from the service system management module, and then the interface encapsulation module may be parsed, thereby obtaining metadata of the interface encapsulation module, that is, obtaining service data of the service object.
According to the technical scheme, when the service system management module receives the second configuration request, the source service system can be packaged according to the second configuration request to obtain the interface packaging module, so that the source service system can be quickly accessed to the design platform by calling the interface packaging module when the source service system is in butt joint with the design platform.
Optionally, the business system management module may also receive a third configuration request from the target docking system. Specifically, when the business system management module receives a third configuration request, determining a target docking system, a product version and a functional module associated with the target docking system according to the third configuration request; acquiring a second metadata table associated with the target docking system based on the target docking system, the product version and a functional module associated with the target docking system; according to the second metadata table, mapping between the business object associated with the target docking system and the API object associated with the target docking system is completed; and packaging the mapping relation between the business object associated with the target docking system and the API object associated with the target docking system into an interface packaging module, and associating the interface packaging module with the target docking system. The interface packaging module is used for packaging the target docking system according to the third configuration request when the service system management module receives the third configuration request, so that the target docking system can be quickly accessed to the design platform by calling the interface packaging module when the target docking system is docked with the design platform later.
Step S120, obtaining service data associated with the source service system from the service system management module.
In this embodiment, the business data includes, but is not limited to, business information, vendor information, and product information. For example, source business system instance name, project number, project name, vendor product version number, and the like. After the source service system and the target docking system are determined, the data in the source service system and the target docking system are further synchronized. In the process of cross-system business process automation processing, business data of a source business system needs to be acquired. Specifically, the configuring of the source service system essentially configures a source service object, and after determining the configured service object of the source service system, service data associated with the service object of the source service system is acquired. The service data of the service object is prestored in the service system management module in the form of an interface encapsulation module, and the interface encapsulation module corresponding to the service object of the source service system can be obtained from the service system management module, so that the service data associated with the service object can be obtained according to the interface encapsulation module. Wherein, each source service system corresponds to one service object, or each source service system corresponds to a plurality of service objects. For example, the target docking system wants to acquire a service object in the source service system as an attendance module, and can package the attendance module into an interface package module, and the target docking system invokes the interface package module of the attendance module to realize docking between the source service system and the target docking system.
Optionally, before acquiring the service data associated with the source service system from the service system management module, the service data of the service object of the source service system needs to be packaged into an interface packaging module, so that the interface packaging module can be used for calling subsequent service data.
Step S130, determining a data processing rule according to the service data, and mapping the service data into target data of the target docking system based on the data processing rule, so that a data structure of the service data is adapted to a data structure of the target data.
In this embodiment, after obtaining the service data of the service object, the service data needs to be further processed, so that the service data can be adapted to the target docking platform. In the process of processing the service data, corresponding data processing rules can be set according to the specific content of the service data, and the service data is converted into target data based on the data processing rules. Optionally, referring to fig. 5, in determining the data processing rule according to the service data, the step of mapping the service data to the target data of the target docking system based on the data processing rule includes:
Step S131, determining the data source field according to the field name associated with the service data of the source service system.
Step S132, determining a data processing rule corresponding to the data source field, where the data processing rule includes at least one of a data mapping process, a cleaning process, a splitting process, a merging process, a statistical process, and a comparison process.
And step S133, carrying out data conversion on the business data based on the data structure of the target docking system based on the data processing rule to obtain target data adapted to the target docking system.
Alternatively, the data processing rules corresponding to each data source field may be one or even more. The data processing rule comprises at least one of data mapping processing, cleaning processing, splitting processing, merging processing, statistical processing and comparison processing. For example, when the field name is the download time, the corresponding data source field is "R-C2. platform bill download time", and the corresponding data processing rule may be a function of judging whether the service object is null { [ R-C2. platform bill download time ] }, a function of judging the condition java { @ r1@=0, [ R-C2. platform bill download time ] }, or a function of transferring the timestamp { @ r2@.. Where R represents the business object and C2 represents the mapping model. When the field name is service description, the corresponding data source field is R-C2. platform bill, service description, and the corresponding data processing rule is an assignment function { [ R-C2. platform bill, service description ] }.
According to the method and the system, the corresponding data processing rule is set for each field, and then the service data is mapped into the target data which can be matched with the target docking system through the data processing rule, so that the service data of the service object of the source service system can be synchronized to the target object system.
Optionally, after mapping the salesman data into the target data, data debugging can be performed on the target data, wherein the data debugging comprises single-node debugging, single-scene debugging and multi-scene scheduling operation; when the target data is successfully debugged, the target data is written into the target docking system through the execution engine, so that the cross-system business process automation processing between the target docking system and the source business system is realized.
And step S140, writing the target data into the target docking system through the execution engine so that the data of the source service system can be synchronized to the target docking system.
In this embodiment, the set scene model in the receiving design platform analyzes the content of the scene model, and realizes operations such as automatic reading, data processing, and writing of data, so that the data of the source service system can be synchronized to the target docking system. Through code-free data acquisition and analysis, a comprehensive and intelligent data design platform is formed, so that enterprise data can be automatically circulated in each business system.
Optionally, the execution engine receives an instruction of the design platform, generates a DAG graph model according to a flow model generated by the design platform and service data of a service system, and performs reading and writing operations on a source interface and a target interface; optionally, the execution engine determines a data node and a data relationship based on the target data; a directed acyclic graph is generated based on the data nodes and the data relationships to write the target data to the target docking system. Alternatively, after the debugging is successful, the instruction indicating that the execution engine receives the design platform may be further indicated.
Optionally, after the target data in the scene model is written into the target docking system, the execution engine returns the running result to the design platform in real time in the process of running the data, where the running result may be data synchronization information, including cross-system business process automation processing success information, cross-system business process automation processing failure information, and the like. The design platform displays the data synchronization information on the design platform after receiving the data synchronization information generated by the execution engine. Specifically, the data synchronization information returned by the data engine is analyzed, and the data synchronization information is displayed in the design platform, so that the end terminal user can conveniently check the data synchronization information. Therefore, seamless linkage of the execution engine and the design platform and data interaction are guaranteed through a heartbeat mechanism.
According to the embodiment, when the first configuration request is received by the design platform, the source service system and the target docking system are determined according to the configuration request, service data associated with the source service system are acquired from the service system management module, and further data processing rules are determined according to the service data, and the data structure of the service data of the source service system is converted by the data structure of the target docking system based on the corresponding data processing rules, so that the service data is mapped into the target data of the target docking system, after the target data is obtained, the target data is written into the target docking system through the execution engine, so that the technical scheme of cross-system service flow automatic processing between the data of the source service system and the target docking system is realized.
Optionally, in the process of cross-system business process automation processing, when the design platform receives the first configuration request, a corresponding scene model is built based on different business scenes. Specifically, because the interface encapsulation module of the service object stored in the source service system in the database of the service system management module, the reading module, the mapping module and the writing module can be obtained from the database, the source service system can be configured in the reading module, the writing module is configured with the target docking system, the mapping module is provided with the data processing rule corresponding to the service data of the source service system, and then the scene module can be generated according to the reading module, the mapping module and the writing module, and is used for representing the data flow direction of the service data of the source service system so as to dock the source service system with the target docking system through the scene module. According to the method and the device, the corresponding scene model can be established according to different service scenes, so that the cross-system service flow automatic processing among different systems is realized under different service scenes.
Optionally, the execution engine may also perform a query of the data after writing the target data to the target docking system. Optionally, when the design platform receives the data query request, the query condition can be determined according to the data query request, and then the service data and the target data associated with the query condition can be obtained from the storage module, so that the service data and the target data are displayed on a visual interface of the design platform, and the trend and the progress of different system data can be conveniently and rapidly checked. When the query condition is the query time, for example, all the associated data including the associated order number, the amount of money, the order creation time, the remark information, and the like, of which the query time is 2022, 4, and 22 days may be acquired. After the corresponding associated data is obtained by inquiry, the associated data can be derived or downloaded so as to facilitate the further analysis of the data by staff. Thereby conveniently and quickly exporting data.
Second embodiment.
As shown in fig. 6, in a second embodiment of the present application, the cross-system business process automation processing method of the present application further includes the following steps:
step S110, when the design platform receives a first configuration request, determining a source service system and a target docking system according to the first configuration request;
step S310, modeling a source business system object and a target docking system object according to the source business system and the target docking system at the design platform;
step S120, in the design platform, configuring a source service system object model to acquire service data associated with the source service system from the service system management module;
step S130, determining a data processing rule according to the service data, and mapping the source service system object data into the target docking system object data based on the data processing rule so that the data structure of the service data is adapted to the data structure of the target data;
and step S320, configuring the object model of the target docking system according to the design platform to perform association operation on the target docking system. The design platform can be configured with single-target system multi-step operation and multi-target system multi-step operation at the same time so as to complete the targets of data synchronization and business flow design;
Step S330, in the design platform, the configuration stores or returns the response result corresponding to the target docking system association operation to the source service system so as to achieve the process interaction between the source service system and the target docking system;
step S140, writing the target data into the target docking system through the execution engine to synchronize the data of the source service system to the target docking system, thereby achieving the purpose of automatic process execution.
Embodiments of the present invention provide embodiments of a cross-system business process automation processing method, it being noted that although a logical sequence is illustrated in the flow diagrams, in some cases the steps illustrated or described may be performed in a different order than that illustrated herein.
As shown in fig. 7, the present application provides a cross-system business process automation processing system, where the cross-system business process automation processing system includes:
the configuration module 10 is configured to determine, when the design platform receives a first configuration request, a source service system and a target docking system according to the first configuration request;
an acquisition module 20, configured to acquire service data associated with the source service system from a service system management module;
A mapping module 30, configured to determine a data processing rule according to the service data, and map the service data to target data of the target docking system based on the data processing rule, so that a data structure of the service data is adapted to a data structure of the target data;
and the synchronization module 40 is configured to write the target data into the target docking system through an execution engine, so that the data of the source service system can be synchronized to the target docking system.
Optionally, before the configuration module 10, the cross-system business process automation processing system further includes an interface encapsulation module generating module, where the interface encapsulation module generating module is configured to determine, when the business system management module receives a second configuration request, a source business system, a product version, and a functional module associated with the source business system according to the second configuration request; acquiring a first metadata table associated with the source service system based on the source service system, the product version and a functional module associated with the source service system; according to the first metadata table, mapping of the service object associated with the source service system and the API object associated with the source service system is completed; and encapsulating the mapping relation between the service object associated with the source service system and the API object associated with the source service system into an interface encapsulation module, and associating the interface encapsulation module with the source service system.
Optionally, the interface packaging module generating module is further configured to obtain a service object associated with the source service system from the first metadata table; acquiring a first field name and a first field path of the service object, and a second field name and a second field path of a sub-service object associated with the service object; acquiring first service data associated with the first field name from the first field path and second service data associated with the second field name from the second field path, the first service data and the second service data including enterprise information, vendor information and product information; mapping of the service object to an API object associated with the source service system is accomplished based on the first service data and the second service data.
Optionally, the interface packaging module generating module is further configured to determine, when the service system management module receives a third configuration request, a target docking system, a product version, and a functional module associated with the target docking system according to the third configuration request; acquiring a second metadata table associated with the target docking system based on the target docking system, the product version and a functional module associated with the target docking system; according to the second metadata table, mapping between the business object associated with the target docking system and the API object associated with the target docking system is completed; and packaging the mapping relation between the business object associated with the target docking system and the API object associated with the target docking system into an interface packaging module, and associating the interface packaging module with the target docking system.
Optionally, the obtaining module 20 is further configured to obtain, from the service system management module, an interface encapsulation module associated with the source service system; and obtaining the service data associated with the source service system according to the interface packaging module associated with the source service system.
Optionally, the mapping module 30 is configured to determine a data source field according to a field name associated with service data of the source service system; determining a data processing rule corresponding to the data source field, wherein the data processing rule comprises at least one of data mapping processing, cleaning processing, splitting processing, merging processing, statistical processing and comparison processing; and carrying out data conversion on the business data based on the data structure of the target docking system based on the data processing rule to obtain target data adapted to the target docking system.
Optionally, a debug module is further connected to the mapping module 30, and the debug module is configured to perform data debug on the target data, where the data debug includes single-node debug, single-scenario debug, and multi-scenario scheduling operation; when the target data is successfully debugged, the target data is written into the target docking system through the execution engine, so that the data of the source service system can be synchronized to the target docking system; optionally, after the debug module, the debug module is connected with a synchronization module 40, the synchronization module 40 being used by the execution engine to determine data nodes and data relationships based on the target data; a directed acyclic graph is generated based on the data nodes and the data relationships to write the target data to the target docking system.
Optionally, a display module is further connected to the synchronization module 40, where the display module is configured to generate data synchronization information when the execution engine writes the target data into the target docking system, and feed back the data synchronization result to the design platform; and displaying the data synchronization result on the design platform.
Optionally, a query module is further connected after the synchronization module 40, and the query module is configured to determine a query condition according to the query request when the design platform receives the query request; acquiring associated data matched with the query condition from a storage module; and displaying the associated data on a display interface of the design platform.
The specific implementation manner of the cross-system business process automation processing system is basically the same as that of each embodiment of the cross-system business process automation processing method, and is not repeated here.
Based on the same inventive concept, the embodiments of the present application further provide a computer readable storage medium, where the computer readable storage medium stores a cross-system business process automation processing program, where each step of the cross-system business process automation processing method described above is implemented when the cross-system business process automation processing program is executed by a processor, and the steps can achieve the same technical effect, so that repetition is avoided and no further description is given here.
Because the storage medium provided in the embodiments of the present application is a storage medium used for implementing the method in the embodiments of the present application, based on the method described in the embodiments of the present application, a person skilled in the art can understand the specific structure and the modification of the storage medium, and therefore, the description thereof is omitted herein. All storage media used in the methods of the embodiments of the present application are within the scope of protection intended in the present application.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described 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 flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, 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 specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (8)
1. The cross-system business process automatic processing method is characterized by being applied to a cross-system business process automatic processing system, wherein the cross-system business process automatic processing system comprises a business system management module, a design platform and an execution engine, and the functions of the business system management module at least comprise: the method comprises the steps of data input and auditing of a source service system, API object modeling, service object encapsulation mapping, interface encapsulation module configuration, debugging, testing and publishing and warehousing, wherein the functions of the design platform at least comprise metadata analyzed by a service system management module, flexible configuration without codes is realized on a visual page, and finally, a scene model with the configuration completed is pushed into an execution engine; the cross-system business process automatic processing method comprises the following steps:
When the service system management module receives a second configuration request, determining a source service system, a product version and a functional module associated with the source service system according to the second configuration request;
acquiring a first metadata table associated with the source service system based on the source service system, the product version and a functional module associated with the source service system;
according to the first metadata table, mapping of the service object associated with the source service system and the API object associated with the source service system is completed;
packaging a mapping relation between the service object associated with the source service system and the API object associated with the source service system into an interface packaging module, and associating the interface packaging module with the source service system;
when the design platform receives a first configuration request, determining a source service system and a target docking system according to the first configuration request;
acquiring an interface encapsulation module associated with the source service system from the service system management module;
obtaining service data associated with the source service system according to an interface packaging module associated with the source service system;
determining a data processing rule according to the service data, and mapping the service data into target data of the target docking system based on the data processing rule so that a data structure of the service data is adapted to a data structure of the target data;
And writing the target data into the target docking system through the execution engine so that the data of the source service system can be synchronized to the target docking system.
2. The cross-system business process automation processing method of claim 1, wherein the step of completing mapping of the source business system associated business object and the source business system associated API object according to the first metadata table comprises:
acquiring a business object associated with the source business system from the first metadata table;
acquiring a first field name and a first field path of the service object, and a second field name and a second field path of a sub-service object associated with the service object;
acquiring first service data associated with the first field name from the first field path and second service data associated with the second field name from the second field path, the first service data and the second service data including enterprise information, vendor information and product information;
mapping of the service object to an API object associated with the source service system is accomplished based on the first service data and the second service data.
3. The method for automatically processing a cross-system business process according to claim 1, wherein before the step of determining a source business system and a target docking system according to the first configuration request when the design platform receives the first configuration request, the method further comprises:
when the business system management module receives a third configuration request, determining a target docking system, a product version and a functional module associated with the target docking system according to the third configuration request;
acquiring a second metadata table associated with the target docking system based on the target docking system, the product version and a functional module associated with the target docking system;
according to the second metadata table, mapping between the business object associated with the target docking system and the API object associated with the target docking system is completed;
and packaging the mapping relation between the business object associated with the target docking system and the API object associated with the target docking system into an interface packaging module, and associating the interface packaging module with the target docking system.
4. The cross-system business process automation processing method of claim 1, wherein the step of determining a data processing rule from the business data and mapping the business data to the target data of the target docking system based on the data processing rule comprises:
Determining a data source field according to a field name associated with service data of the source service system;
determining a data processing rule corresponding to the data source field, wherein the data processing rule comprises at least one of data mapping processing, cleaning processing, splitting processing, merging processing, statistical processing and comparison processing;
and carrying out data conversion on the business data based on the data structure of the target docking system based on the data processing rule to obtain target data adapted to the target docking system.
5. The cross-system business process automation processing method of claim 1, wherein after the step of determining a data processing rule according to the business data and mapping the business data to the target data of the target docking system based on the data processing rule so that the data structure of the business data is adapted to the data structure of the target data, further comprising:
performing data debugging on the target data, wherein the data debugging comprises single-node debugging, single-scene debugging and multi-scene scheduling operation;
executing the step of writing the target data into the target docking system through the execution engine when the target data is successfully debugged, so that the data of the source service system can be synchronized to the target docking system;
The step of writing the target data to the target docking system by the execution engine includes:
the execution engine determining data nodes and data relationships based on the target data;
a directed acyclic graph is generated based on the data nodes and the data relationships to write the target data to the target docking system.
6. The cross-system business process automation processing method of claim 1, wherein after the step of writing the target data to the target docking system by the execution engine, further comprising:
the execution engine generates data synchronization information when writing the target data into the target docking system, and feeds back a data synchronization result to the design platform;
and displaying the data synchronization result on the design platform.
7. The cross-system business process automation processing method of claim 1, wherein after the step of writing the target data to the target docking system by the execution engine to enable the data of the source business system to be synchronized to the target docking system, further comprising:
when the design platform receives a query request, determining a query condition according to the query request;
Acquiring associated data matched with the query condition from a storage module;
and displaying the associated data on a display interface of the design platform.
8. The cross-system business process automation processing system is characterized by comprising a business system management module, a design platform and an execution engine, wherein the functions of the business system management module at least comprise: the method comprises the steps of data input and auditing of a source service system, API object modeling, service object encapsulation mapping, interface encapsulation module configuration, debugging, testing and publishing and warehousing, wherein the functions of the design platform at least comprise metadata analyzed by a service system management module, flexible configuration without codes is realized on a visual page, and finally, a scene model with the configuration completed is pushed into an execution engine;
the cross-system business process automation processing system comprises: the configuration module is used for determining a source service system, a product version and a functional module associated with the source service system according to a second configuration request when the service system management module receives the second configuration request; acquiring a first metadata table associated with the source service system based on the source service system, the product version and a functional module associated with the source service system; according to the first metadata table, mapping of the service object associated with the source service system and the API object associated with the source service system is completed; packaging a mapping relation between the service object associated with the source service system and the API object associated with the source service system into an interface packaging module, and associating the interface packaging module with the source service system; when a first configuration request is received by a design platform, determining a source service system and a target docking system according to the first configuration request;
The acquisition module is used for acquiring an interface encapsulation module associated with the source service system from the service system management module; obtaining service data associated with the source service system according to an interface packaging module associated with the source service system;
the mapping module is used for determining a data processing rule according to the service data and mapping the service data into target data of the target docking system based on the data processing rule so that a data structure of the service data is adapted to a data structure of the target data;
and the synchronization module is used for writing the target data into the target docking system through an execution engine so that the data of the source service system can be synchronized to the target docking system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211001038.1A CN115292418B (en) | 2022-08-19 | 2022-08-19 | Cross-system business process automatic processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211001038.1A CN115292418B (en) | 2022-08-19 | 2022-08-19 | Cross-system business process automatic processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115292418A CN115292418A (en) | 2022-11-04 |
| CN115292418B true CN115292418B (en) | 2023-04-28 |
Family
ID=83830106
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211001038.1A Active CN115292418B (en) | 2022-08-19 | 2022-08-19 | Cross-system business process automatic processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115292418B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114565285A (en) * | 2022-03-01 | 2022-05-31 | 城云科技（中国）有限公司 | Flow control method and system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7610575B2 (en) * | 2003-01-08 | 2009-10-27 | Consona Crm Inc. | System and method for the composition, generation, integration and execution of business processes over a network |
| CN112328224B (en) * | 2021-01-06 | 2021-03-30 | 广州市玄武无线科技股份有限公司 | Service interface docking method and device, storage medium and electronic equipment |
| CN114089977A (en) * | 2021-11-16 | 2022-02-25 | 云镝智慧科技有限公司 | Receipt docking method and device for business system and computer equipment |
| CN114428621A (en) * | 2021-12-17 | 2022-05-03 | 华人运通(上海)云计算科技有限公司 | Operation automation deployment method |
-
2022
- 2022-08-19 CN CN202211001038.1A patent/CN115292418B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114565285A (en) * | 2022-03-01 | 2022-05-31 | 城云科技（中国）有限公司 | Flow control method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115292418A (en) | 2022-11-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8898643B2 (en) | Application trace replay and simulation systems and methods | |
| CN109783084A (en) | A kind of computer code automatic generation method, system, device and storage medium | |
| CN110413316B (en) | Non-invasive testing system and method for intelligent contracts of block chain | |
| US8311794B2 (en) | Testing executable logic | |
| US11436133B2 (en) | Comparable user interface object identifications | |
| CN107506190A (en) | XML file amending method and device based on Spring frameworks | |
| CN113018870A (en) | Data processing method and device and computer readable storage medium | |
| EP2196901A1 (en) | Systems and methods for tracking software stands in a software production landscape | |
| US8375365B2 (en) | Customization verification | |
| CN106201859A (en) | A kind of regression testing method and system | |
| Mainkar | Expert Android Programming: Master skills to build enterprise grade Android applications | |
| CN113342679A (en) | Interface test method and test device | |
| CN115292418B (en) | Cross-system business process automatic processing method and system | |
| US20080301645A1 (en) | Verification of customization results | |
| CN103955425A (en) | Webpage (WEB) exploring testing device and method | |
| CN115509913A (en) | Software automation test method, device, machine readable medium and equipment | |
| CN113672222A (en) | Application program interface management device and construction method thereof | |
| CN111240981A (en) | Interface testing method, system and platform | |
| US20080066005A1 (en) | Systems and Methods of Interfacing with Enterprise Resource Planning Systems | |
| CN111125073A (en) | Method, device and system for verifying data quality of big data platform | |
| Ashraf et al. | ATAM-based architecture evaluation using LOTOS formal method | |
| CN115543323B (en) | Page development method and device | |
| CN107527202B (en) | Transaction data diagnosis method and device and computing equipment | |
| Koller | Empirical Suitability Comparison of Java and Emerald for Concurrency and Distribution: Designing a Trial Workshop for Evaluating Language Usability | |
| CN116860636A (en) | Unit test code generation method, device, equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Huang Zhenhai Inventor after: Chen Jie Inventor after: Zhang Peijun Inventor after: Yin Qingjiao Inventor before: Huang Zhenhai Inventor before: Chen Jie Inventor before: Zhang Peijun Inventor before: Yin Qingjiao |