CN115292418A - Cross-system business process automatic processing method and system - Google Patents
Cross-system business process automatic processing method and system Download PDFInfo
- Publication number
- CN115292418A CN115292418A CN202211001038.1A CN202211001038A CN115292418A CN 115292418 A CN115292418 A CN 115292418A CN 202211001038 A CN202211001038 A CN 202211001038A CN 115292418 A CN115292418 A CN 115292418A
- Authority
- CN
- China
- Prior art keywords
- data
- business
- target
- service
- source
- 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.)
- Granted
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]
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Entrepreneurship & Innovation (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a cross-system service flow automatic 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; the execution engine writes the target data into the target docking system according to the business process arranged by the design platform, so that the data of the source business system is synchronized to the target docking system, and the purpose of executing the automatic process is achieved.
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 a cross-system business process automatic processing system.
Background
With the rapid development of the SaaS software industry, more and more business systems are used in enterprises, for example, system Management software such as CRM (Customer Relationship Management), OA (Office Automation), ERP (Enterprise Resource Planning), and the like. Data inside an enterprise are dispersed in each system, and the data structures of business processes between the business systems are different and need to be synchronized. At present, when business processes of different systems are synchronous, the automatic processing efficiency of the cross-system business processes is low.
Disclosure of Invention
The embodiment of the application aims to improve the automatic processing efficiency of the cross-system business process 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 service flow automatic processing method, which is applied to a cross-system service flow automatic processing system, wherein the cross-system service flow automatic processing system comprises a service system management module, a design platform and an execution engine; the cross-system business process automatic 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 business data, and mapping the business data into target data of the target docking system based on the data processing rule so that a data structure of the business 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 business 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 function 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 function module associated with the source service system;
mapping between 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;
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 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 business object, and a second field name and a second field path of a sub business object associated with the business object;
acquiring first business data associated with the first field name from the first field path, and acquiring second business data associated with the second field name from the second field path, wherein the first business data and the second business data comprise enterprise information, manufacturer information and product information;
and completing the mapping of the business object and the API object associated with the source business system based on the first business data and the second business 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 function module associated with the target docking system according to the third configuration request;
obtaining a second metadata table associated with the target docking system based on the target docking system, the product version, and a function module associated with the target docking system;
completing the mapping of the business object associated with the target docking system and the API object associated with the target docking system according to the second metadata table;
and encapsulating 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 encapsulation module, and associating the interface encapsulation module with the target docking system.
Optionally, the step of obtaining the service data associated with the source service system from the service system management module includes:
acquiring an interface packaging 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 the field name associated with the 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 performing data conversion on the service data based on the data structure of the target docking system based on the data processing rule to obtain target data adaptive 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 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, 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;
when the target data is successfully debugged, executing the step of writing the target data into the target docking system through the execution engine so as to enable the data of the source business system to 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 determines data nodes and data relationships based on the target data;
and generating a directed acyclic graph based on the data nodes and the data relations so as to write the target data into 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:
when the execution engine writes the target data into the target docking system, generating data synchronization information and feeding 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 the target data into the target docking system through the execution engine so that the data of the source business system can 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, to achieve the above object, the present invention further provides an automated processing system for cross-system business process, including:
the system comprises a configuration module, a target docking system and a service processing module, wherein the configuration module is used for determining the source service system and the 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 the 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 business data and mapping the business data into target data of the target docking system based on the data processing rule so that a data structure of the business data is adapted to the 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 as to enable the data of the source service system to 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 at least has the following technical effects or advantages: the method comprises the steps of determining a source business system and a target docking system according to a configuration request when the first configuration request is received by a design platform, obtaining business data associated with the source business system from a business system management module, further determining a data processing rule according to the business data, converting a data structure of the business data of the source business system according to the data structure of the target docking system based on the corresponding data processing rule, further mapping the business data into the target data of the target docking system, and writing the target data into the target docking system through an execution engine after the target data is obtained, so that the cross-system business process between the data of the source business system and the target docking system is automatically processed.
Drawings
FIG. 1 is a schematic flow chart of a first embodiment of a cross-system business process automated processing method according to the present invention;
FIG. 2 is a 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 of the cross-system service flow automatic processing method according to the first embodiment of the present invention before step S110;
fig. 5 is a detailed flowchart of step S130 in the first embodiment of the cross-system business process automation processing method according to the present invention;
FIG. 6 is a flowchart illustrating a cross-system business process automation processing method according to a second embodiment of the present invention;
FIG. 7 is a functional block diagram of an automated processing system for cross-system traffic flow in accordance with the present invention.
The objects, features, and advantages of the present application are further described in connection with the embodiments, with reference to the accompanying drawings, which are a single embodiment and are not intended to be a complete description of the invention.
Detailed Description
The method comprises the steps of determining a source business system and a target docking system according to a configuration request when a first configuration request is received by a design platform, acquiring business data associated with the source business system from a business system management module, further determining a data processing rule according to the business data, converting the data structure of the business data of the source business system according to the data processing rule corresponding to the data processing rule, further mapping the business data into target data of the target docking system, writing the target data into the target docking system through an execution engine after the target data is acquired, and further determining the data processing rule according to the business data associated with the source business system and the target docking system. The method not only can realize the automatic processing of the cross-system service flow among different systems, but also can improve the automatic processing efficiency of the cross-system service flow.
For a better understanding of the above technical solutions, 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.
A first embodiment.
As shown in fig. 1, in a first embodiment of the present application, a 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, determining a source service system and a target docking system according to the first configuration request.
In this embodiment, the cross-system service flow automatic processing method of the present application is applied to a cross-system service flow automatic processing system, and the cross-system service flow automatic processing method is executed on a terminal device, where the terminal device 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 present application can be visually displayed on the web page side, and functions such as configuration, debugging, query, and the like are performed in the design platform.
Optionally, the cross-system business process automation processing system of the present application includes 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 source service system object, including data entry and audit of the source service system, API object modeling, service object packaging mapping, interface packaging module configuration, debugging, testing, publishing, 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 the source service system: and inputting and managing enterprise information, manufacturer information, product information and the like related to the source service system.
API object modeling: the IT information related to the API, such as connection information, interface objects, request/response parameters, authentication, encryption, unique identification, data types and the like, is packaged into an API metadata structure;
modeling a business object: the method manages the window objects/fields, the operation method, the data objects and the association relation, and models the objects according to the service model. And the mapping between the service object and the API object is completed, and IT attribute business and data object business are achieved.
Interface packaging module configuration: and managing the template of the request and the response. The method is used for constructing a request and response model and supports different design habits and styles.
Referring to fig. 2, the main processing flow of the service system management module sequentially comprises: the method comprises the steps of source business system interface, source business system data entry, approval, API object modeling, business object mapping, template configuration, auditing, data debugging, interface debugging and release version. In the processing flow, the API object modeling can be carried out only when the examination and approval is passed, and the data debugging is carried out only when the examination and approval is passed, so that the accuracy in the automatic processing and system docking processes of the cross-system business flow is improved.
Optionally, the design platform is mainly used for performing 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 flexible code-free configuration on a visual page, and finally, the configured scene model is pushed to an 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 a user. Metadata information analyzed through the interface database can complete data processing processes in different modes, such as complex data processing processes of data combination, data splitting, data increase and the like, according to different integration requirements of enterprises, 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 control comprises data object combing, scene flow perfecting, service system planning, parameter comparison configuration, dry system management and version control.
Project task management: clear role division and task allocation separate 'design planning', 'implementation delivery', 'debugging test', 'online operation and maintenance' from functions, and organically integrate all parts together by using a 'visual design platform'.
Designing a flow: the visual 'process workbench' realizes the design of information such as a service system, a scene, a node, conditions, parameters, comparison and the like;
by adopting a modeling idea, 8 large models (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 are provided externally through a model workbench; analyzing the log information returned by the engine, and displaying the final synchronous result in the platform, so that the final end user can conveniently check the log information; the rule configuration work of data mapping, cleaning, splitting, merging, counting, comparison and the like is completed through a rule workbench;
debugging and 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 business requirement through scheduling.
Referring to fig. 3, the main execution flow of the design platform sequentially includes: the method comprises the steps of process design, scheme management, task management, system planning, scene design, node configuration, object modeling, model configuration, rule configuration, single-point test, scene test and release. By executing the operation on the design platform, the docking between different systems and the synchronization of data between different systems are realized.
Optionally, the execution engine is mainly configured to run the configured scene model after receiving the configured scene model, so as to implement operations such as automatic reading, data processing, and writing of data. Optionally, the execution engine mainly includes the following functions:
an 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 combining service system metadata, and performing read and write 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-large 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 relationship between upstream and downstream;
specifically, the source service system may be a third-party system such as a kaleidoscope and a giemyun, an interface encapsulation module of the third-party systems is stored in the service system management module, and the interface data modules are called to realize the docking 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 the target docking system is also docked with the cross-system service flow automatic processing system. The target docking system may be a system preset by a design platform, and the source service system may be a service system previously connected with the target docking system or a source service system not previously connected with the target docking system. When the source service system is a service system which is connected with the target docking system before, a corresponding scene model exists, and the data synchronization 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 a service system connected with the target docking system before, that is, 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 scene model is constructed according to the subsequent steps.
In this embodiment, when the design platform receives the first configuration request, it may be that when the entry into the configuration page is detected, the design platform receives the first configuration request. It may also be that the first configuration request is received when detecting 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. In an application scenario, when cross-system service flow automation processing between two systems is to be implemented, a source service 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.
Optionally, the business system management module may receive a configuration request from the source business system. Optionally, referring to fig. 4, when the design platform receives the first configuration request, before the step of determining, according to the first configuration request, the source service system and the target docking system, 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, acquiring a first metadata table associated with the source service system based on the source service system, the product version and the function module associated with the source service system;
step S230, 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.
In this embodiment, when the service system management module receives a second configuration request, a source service system, a product version, and a function module associated with the source service system may be determined based on the second configuration request, and a first metadata table associated with the source service system may be obtained based on the source service system, the product version, and the function module associated with the source service system; and completing the mapping of 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 the service object associated with the source service system and all the fields associated with the service object. A business object associated with the source business system can be obtained from the first metadata table. Optionally, a first field name and a first field path associated with the business object may be obtained, and the 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, the first field name associated with the business object, e.g., "platform bill", in the first metadata table may be platform ID, store number, status, type, associated order number, payment order number, revenue, and the like. Each field has a corresponding field path, and the field path is used for characterizing the source of the service data corresponding to the field. Required fields can be selected from the field names according to actual scene requirements, and then business data related to the field names are obtained according to field paths of the selected fields. The method can obtain the service data of different service objects of the source service system service. The first business data comprises enterprise information, manufacturer information and product information. After the first service data is obtained, mapping of the service object and the API object of the source service system may be completed based on the first service data.
Optionally, each service object has a plurality of sub-service objects, and a second field name and a second field path of the sub-service object associated with the service object may also be obtained, and second service data associated with the second field name may be obtained from the second field path. The second business data may include enterprise information, vendor information, product information, and the like. After obtaining the second service data, mapping the sub-service object to the API object of the source service system may be completed based on the second service data.
Optionally, after the first service data and the second service data are obtained, mapping between 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, encapsulating 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 encapsulation module, and associating the interface encapsulation module with the source service system.
In this embodiment, after the mapping between 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 a first configuration request is subsequently 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 is analyzed, thereby obtaining metadata of the interface encapsulation module, and obtaining the 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 encapsulated according to the second configuration request to obtain the interface encapsulation module, so that the source service system can be rapidly accessed to the design platform by calling the interface encapsulation module when the source service system is subsequently connected with the design platform.
Optionally, the business system management module may further receive a third configuration request from the target docking system. Specifically, when the service system management module receives a third configuration request, a target docking system, a product version and a function module associated with the target docking system are determined according to the third configuration request; obtaining a second metadata table associated with the target docking system based on the target docking system, the product version, and a function module associated with the target docking system; completing the mapping of the business object associated with the target docking system and the API object associated with the target docking system according to the second metadata table; and encapsulating 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 encapsulation module, and associating the interface encapsulation module with the target docking system. The target docking system can be packaged according to the third configuration request to obtain the interface packaging module 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 subsequently docked with the design platform.
Step S120, obtaining the service data associated with the source service system from the service system management module.
In the present embodiment, the business data includes, but is not limited to, enterprise information, vendor information, and product information. Such as source business system instance name, item number, item name, vendor product name, and vendor product version number, etc. After determining the source service system and the target docking system, further synchronizing data in the source service system and the target docking system. In the process of automatic processing of the cross-system service process, service data of the source service system needs to be acquired. Specifically, the configuring of the source service system is substantially configuring a source service object, and after determining the configured service object of the source service system, the service data associated with the service object of the source service system is acquired. The service data of the service object is pre-stored 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 acquired from the service system management module, so that the service data associated with the service object can be acquired according to the interface encapsulation module. 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 may package an attendance module as an interface package module when it wants to acquire a service object in the source service system, and the target docking system may call the interface package module of the attendance module to further implement the docking between the source service system and the target docking system.
Optionally, before obtaining 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 encapsulated into an interface encapsulation module, and then the interface encapsulation module can be used for calling the subsequent service data.
Step S130, 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, so that a data structure of the service data is adapted to a data structure of the target data.
In this embodiment, after the service data of the service object is obtained, 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, a corresponding data processing rule 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 rule. Optionally, referring to fig. 5, in determining the data processing rule according to the service data, the step of mapping the service data into the target data of the target docking system based on the inter-data processing rule includes:
step S131, determining a 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, wherein the data processing rule comprises at least one of data mapping processing, cleaning processing, splitting processing, merging processing, statistical processing and comparison processing.
Step S133, performing data conversion on the service 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 rule corresponding to each data source field may be one or 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 download time, the corresponding data source field is "R-c2. Platform bill.download time", and the corresponding data processing rule may be to determine whether the business object is an empty function { [ R-c2. Platform bill.download time ] }, may also be a conditional determination function java { @ R1@ =0, [ R-c2. Platform bill.download time ] }, or may be a timestamp to date function { @ R2@ }. Wherein R represents a business object and C2 represents a mapping model. When the field name is service description, the corresponding data source field is R-C2 platform bill and service description, and the corresponding data processing rule is a valuation function { [ R-C2 platform bill and service description ] }.
According to the method and the device, the corresponding data processing rule is set for each field, and then the business data are mapped into the target data which can be adapted to the target docking system through the data processing rule, so that the business data of the business object of the source business system can be synchronized to the target object system.
Optionally, after the salesman data is mapped 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; and when the target data is successfully debugged, writing the target data into the target docking system through the execution engine, and realizing the automatic processing of the cross-system service flow between the target docking system and the source service system.
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, a scene model set in the receiving design platform is analyzed, and operations such as automatic data reading, data processing, and data writing are implemented, so that data of the source service system can be synchronized to the target docking system. Through code-free data acquisition and analysis, a set of comprehensive and intelligent data design platform is formed, and enterprise data can be automatically transferred in each business system.
Optionally, the execution engine receives an instruction of the design platform, generates a DAG graph model according to the flow model generated by the design platform and the service data of the service system, and performs read and write operations on the source interface and the target interface; optionally, the execution engine determines data nodes and data relationships based on the target data; and generating a directed acyclic graph based on the data nodes and the data relations so as to write the target data into the target docking system. Alternatively, after the debugging is successful, the instruction indicating that the execution engine receives the design platform may also be received.
Optionally, after the target data in the scene model is written into the target docking system, the execution engine returns an operation result to the design platform in real time in a data operation process, where the operation result may be data synchronization information including information on success of cross-system service flow automatic processing, information on failure of cross-system service flow automatic processing, and the like. The design platform displays the data synchronization information generated by the execution engine on the design platform after receiving the data synchronization information. Specifically, the data synchronization information returned by the data engine is analyzed, and the data synchronization information is displayed in a design platform, so that the data synchronization information is convenient for a final end user to check. Therefore, seamless connection and data interaction between the execution engine and the design platform are guaranteed through a heartbeat mechanism.
According to the scheme of the embodiment, when the design platform receives the first configuration request, the source business system and the target docking system are determined according to the configuration request, business data associated with the source business system are obtained from the business system management module, a data processing rule is further determined according to the business data, the data structure of the business data of the source business system is converted according to the corresponding data processing rule and the data structure of the target docking system, the business data are mapped into the target data of the target docking system, and after the target data are obtained, the target data are written into the target docking system through the execution engine, so that the cross-system business flow between the data of the source business system and the target docking system is automatically processed.
Optionally, in the process of cross-system business process automation processing, when the design platform receives the first configuration request, the corresponding scenario model may be established based on different business scenarios. Specifically, since the interface encapsulation module of the service object of the source service system is stored in the database of the service system management module, a reading module, a mapping module and a writing module may be obtained from the database, the reading module may be configured with the source service system, the writing module is configured with the target docking system, the mapping module is configured with a data processing rule corresponding to the service data of the source service system, and then a scenario model may be generated according to the reading module, the mapping module and the writing module, where the scenario module is configured to represent a 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 scenario model. According to the method and the device, the corresponding scene models can be established according to different service scenes, so that cross-system service processes among different systems are automatically processed 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 a data query request, a query condition can be determined according to the data query request, and then the business data and the target data associated with the query condition can be acquired from the storage module, so that the business 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 quickly checked. When the query condition is query time, for example, all the associated data including the associated order number, amount, order creation time, remark information, and the like, which is query time of 2022, 4 months, and 22 days, can be obtained. After the corresponding associated data is obtained through query, the associated data can be exported or downloaded, so that the data can be further analyzed by the staff conveniently. Thereby conveniently and quickly exporting data.
A second embodiment.
As shown in fig. 6, in a second embodiment of the present application, the method for automatically processing cross-system business process 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 on the design platform according to the source business system and the target docking system;
step S120, configuring a business data associated with a source business system from the business system management module according to a source business system object model on the design platform;
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;
step S320, configuring and carrying out correlation operation on the target docking system according to the target docking system object model on the design platform. The design platform can simultaneously configure multi-step operation of a single-target system and multi-step operation of a multi-target system so as to complete the targets of data synchronization and business process design;
step S330, storing or returning a response result corresponding to the target docking system correlation operation to the source service system in the design platform, so as to achieve 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 business system to the target docking system, so as to achieve the purpose of executing an automated process.
While a logical order is shown in the flowcharts, in some cases, the steps shown or described may be performed in a different order than that shown or described herein.
As shown in fig. 7, an inter-system business process automation processing system provided in the present application includes:
the system comprises a configuration module 10, a target docking system and a service management module, wherein the configuration module is used for determining a source service system and the target docking system according to a first configuration request when the design platform receives the first configuration request;
an obtaining module 20, configured to obtain, from a service system management module, service data associated with the source service system;
a mapping module 30, configured to determine a data processing rule according to the service data, and map 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;
a synchronization module 40, configured to write the target data into the target docking system through an execution engine, so that the data of the source business system can be synchronized to the target docking system.
Optionally, before the configuration module 10, the cross-system service flow automation processing system further includes an interface encapsulation module generating module, where the interface encapsulation module generating module is configured to determine, according to a second configuration request, a source service system, a product version, and a function module associated with the source service system 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 function module associated with the source service system; mapping between 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; 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 encapsulation 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 business object, and a second field name and a second field path of a sub business object associated with the business object; acquiring first business data associated with the first field name from the first field path, and acquiring second business data associated with the second field name from the second field path, wherein the first business data and the second business data comprise enterprise information, manufacturer information and product information; and completing the mapping of the business object and the API object associated with the source business system based on the first business data and the second business data.
Optionally, the interface encapsulation 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 function module associated with the target docking system according to the third configuration request; obtaining a second metadata table associated with the target docking system based on the target docking system, the product version, and a function module associated with the target docking system; completing the mapping of the business object associated with the target docking system and the API object associated with the target docking system according to the second metadata table; and encapsulating 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 encapsulation module, and associating the interface encapsulation 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 the 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 performing data conversion on the service data based on the data structure of the target docking system based on the data processing rule to obtain target data adaptive to the target docking system.
Optionally, a debugging module is connected behind the mapping module 30, and the debugging module is used for performing data debugging on the target data, where the data debugging includes single-node debugging, single-scene debugging, and multi-scene scheduling operation; when the target data is successfully debugged, writing the target data into the target docking system through the execution engine so that the data of the source business system can be synchronized to the target docking system; optionally, after the debugging module, the debugging module is connected with a synchronization module 40, and the synchronization module 40 is used for the execution engine to determine a data node and a data relationship based on the target data; and generating a directed acyclic graph based on the data nodes and the data relation so as to write the target data into the target docking system.
Optionally, a display module is further connected after the synchronization module 40, and 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, an inquiry module is further connected behind the synchronization module 40, and the inquiry module is configured to determine an inquiry condition according to an inquiry request when the design platform receives the inquiry 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 of the cross-system service flow automatic processing system of the present invention is basically the same as the above-mentioned embodiments of the cross-system service flow automatic processing method, and will not be described herein again.
Based on the same inventive concept, an embodiment of the present application further provides a computer-readable storage medium, where a cross-system service flow automation processing program is stored, and when executed by a processor, the cross-system service flow automation processing program implements the steps of the cross-system service flow automation processing method described above, and can achieve the same technical effect, and is not described herein again to avoid repetition.
Since 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 a specific structure and a modification of the storage medium, and thus details are not described here. Any storage medium used in the method of the embodiment of the present application is intended to be protected by the present application.
As will be appreciated by one skilled in the art, 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 has been 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 usage of the words first, second and third, etcetera do not indicate any ordering. 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. Therefore, it is intended that the appended claims be interpreted as including 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 changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (10)
1. A cross-system business process automatic processing method is characterized in that the method is applied to a cross-system business process automatic processing system, and 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 automatic 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 business data, and mapping the business data into target data of the target docking system based on the data processing rule so that a data structure of the business 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 as to enable the data of the source business system to be synchronized to the target docking system.
2. The cross-system business process automation processing method of claim 1, wherein prior to the step of determining a source business system and a target docking system according to a first configuration request when the design platform receives the first configuration request, further comprising:
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;
acquiring a first metadata table associated with the source service system based on the source service system, the product version and a function module associated with the source service system;
mapping between 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;
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.
3. The cross-system business process automation processing method of claim 2, wherein the step of completing the mapping of the business object associated with the source business system to the API object associated with the source business system according to the first metadata table comprises:
acquiring 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 business object, and a second field name and a second field path of a sub business object associated with the business object;
acquiring first business data associated with the first field name from the first field path, and acquiring second business data associated with the second field name from the second field path, wherein the first business data and the second business data comprise enterprise information, manufacturer information and product information;
and completing the mapping of the business object and the API object associated with the source business system based on the first business data and the second business data.
4. The cross-system business process automation processing method of claim 1, wherein prior to the step of determining a source business system and a target docking system according to a first configuration request when the design platform receives the first configuration request, further comprising:
when the business system management module receives a third configuration request, determining a target docking system, a product version and a function module associated with the target docking system according to the third configuration request;
obtaining a second metadata table associated with the target docking system based on the target docking system, the product version, and a function module associated with the target docking system;
completing the mapping of the business object associated with the target docking system and the API object associated with the target docking system according to the second metadata table;
and encapsulating 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 encapsulation module, and associating the interface encapsulation module with the target docking system.
5. The cross-system business process automation processing method of claim 2, the step of obtaining business data associated with the source business system from the business system management module comprising:
acquiring an interface packaging 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.
6. 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 target data of the target docking system based on the data processing rule comprises:
determining a data source field according to the field name associated with the 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 performing data conversion on the service data based on the data structure of the target docking system based on the data processing rule to obtain target data adaptive to the target docking system.
7. The cross-system business process automated processing method of claim 1, wherein the step of determining data processing rules from the business data and mapping the business data to target data of the target docking system based on the data processing rules to adapt a data structure of the business data to a data structure of the target data further comprises:
performing data debugging 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, executing the step of writing the target data into the target docking system through the execution engine so as to enable the data of the source business system to 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 determines data nodes and data relationships based on the target data;
and generating a directed acyclic graph based on the data nodes and the data relations so as to write the target data into the target docking system.
8. The cross-system business process automation processing method of claim 1, after the step of writing the target data to the target docking system by the execution engine, further comprising:
when the execution engine writes the target data into the target docking system, generating data synchronization information and feeding back a data synchronization result to the design platform;
and displaying the data synchronization result on the design platform.
9. The cross-system business process automation processing method of claim 1, the step of writing the target data to the target docking system by the execution engine to enable synchronization of the data of the source business system to the target docking system further comprising, after the step of:
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.
10. An inter-system business process automation processing system, comprising:
the system comprises a configuration module, a target docking system and a service module, wherein the configuration module is used for determining the source service system and the 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 business data and mapping the business data into target data of the target docking system based on the data processing rule so that a data structure of the business data is adapted to the 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 as to enable the data of the source service system to 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 true CN115292418A (en) | 2022-11-04 |
| CN115292418B 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 (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040133876A1 (en) * | 2003-01-08 | 2004-07-08 | Craig Sproule | System and method for the composition, generation, integration and execution of business processes over a network |
| CN112328224A (en) * | 2021-01-06 | 2021-02-05 | 广州市玄武无线科技股份有限公司 | 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 |
| CN114565285A (en) * | 2022-03-01 | 2022-05-31 | 城云科技（中国）有限公司 | Flow control method and system |
-
2022
- 2022-08-19 CN CN202211001038.1A patent/CN115292418B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040133876A1 (en) * | 2003-01-08 | 2004-07-08 | Craig Sproule | System and method for the composition, generation, integration and execution of business processes over a network |
| CN112328224A (en) * | 2021-01-06 | 2021-02-05 | 广州市玄武无线科技股份有限公司 | 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 |
| CN114565285A (en) * | 2022-03-01 | 2022-05-31 | 城云科技（中国）有限公司 | Flow control method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115292418B (en) | 2023-04-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102236549B (en) | Across the motion time of dynamic boundary analyse visual | |
| CN103246602B (en) | Code coverage determines method and system, code coverage detection method and system | |
| CN109302522A (en) | Test method, device and computer system and medium | |
| CN106648556B (en) | Method and device for front-end and back-end integrated development test | |
| US20080276225A1 (en) | Testing Executable Logic | |
| CN111290951B (en) | Test method, terminal, server, system and storage medium | |
| CN110083342A (en) | A kind of program creating method, device and computer readable storage medium | |
| CN112905441A (en) | Test case generation method, test method, device and equipment | |
| CN106201859A (en) | A kind of regression testing method and system | |
| CN103955425B (en) | Webpage (WEB) exploring testing device and method | |
| CN113778878A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN114185874A (en) | Big data based modeling method and device, development framework and equipment | |
| CN111221721A (en) | Automatic recording and executing method and device for unit test cases | |
| Mainkar | Expert Android Programming: Master skills to build enterprise grade Android applications | |
| CN111240678B (en) | Pop-up window setting method and device, electronic equipment and storage medium | |
| Wieczorek et al. | Test data provision for ERP systems | |
| CN115292418B (en) | Cross-system business process automatic processing method and system | |
| CN109542775A (en) | A kind of generation and execution method and device of test script | |
| US11681511B2 (en) | Systems and methods for building and deploying machine learning applications | |
| CN115509913A (en) | Software automation test method, device, machine readable medium and equipment | |
| CN114168456A (en) | Front-end performance automatic testing method based on 3D-GIS | |
| CN113641628A (en) | Data quality detection method, device, equipment and storage medium | |
| CN113688031A (en) | Testing positioning method based on byte code enhancement technology | |
| US8321844B2 (en) | Providing registration of a communication | |
| CN115543323B (en) | Page development method and device |
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 |
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 |
|
| CB03 | Change of inventor or designer information |