CN113626644A - Method and device for converting formats of business process data - Google Patents
Method and device for converting formats of business process data Download PDFInfo
- Publication number
- CN113626644A CN113626644A CN202111014398.0A CN202111014398A CN113626644A CN 113626644 A CN113626644 A CN 113626644A CN 202111014398 A CN202111014398 A CN 202111014398A CN 113626644 A CN113626644 A CN 113626644A
- Authority
- CN
- China
- Prior art keywords
- business process
- process data
- node
- format
- configuration information
- 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
- 238000000034 method Methods 0.000 title claims abstract description 336
- 230000008569 process Effects 0.000 title claims abstract description 307
- 238000006243 chemical reaction Methods 0.000 claims description 25
- 238000007405 data analysis Methods 0.000 claims description 7
- 238000013500 data storage Methods 0.000 claims description 7
- 238000012795 verification Methods 0.000 claims description 6
- 230000008676 import Effects 0.000 claims description 3
- 238000013461 design Methods 0.000 description 5
- 230000005012 migration Effects 0.000 description 4
- 238000013508 migration Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 238000012938 design process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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/80—Information retrieval; Database structures therefor; File system structures therefor of semi-structured data, e.g. markup language structured data such as SGML, XML or HTML
- G06F16/84—Mapping; Conversion
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Document Processing Apparatus (AREA)
Abstract
The application provides a method and a device for converting formats of business process data, wherein the method comprises the following steps: acquiring first business process data in a first format; analyzing various basic element information describing the business process in the first business process data, wherein the various basic element information at least comprises the following steps: a plurality of node primitives forming the service process and configuration information related to the service process; determining a second format to which the first business process data needs to be converted; creating an XML object or a JSON object which accords with a second business process modeling specification and adopts a second programming language; adding a plurality of node primitives and configuration information into the storage object to obtain reconstructed second business process data in a second format; and storing the second business process data in the second format. The scheme of the application can reduce the situation that the original business process data cannot be designed and optimized by using the new business process modeling specification due to the incompatibility of the business process data.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method and an apparatus for format conversion of business process data.
Background
The design of the business process refers to designing or optimizing a relevant process required by business execution according to market requirements or enterprise requirements to obtain a designed file containing the business process.
In practical application, due to various reasons such as technical maintenance, a new business process modeling specification is often required to be replaced to perform process design work. However, since the rules and formats for designing and storing the business process according to different business process modeling specifications are different, the business process data stored in the original business process modeling specification cannot be opened and identified after the new business process modeling specification is adopted, and thus the business process data is not compatible.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for format conversion of business process data, so as to convert business process data designed according to an original business process modeling specification into business process data supported by a new business process modeling specification, and reduce a situation that the original business process data cannot be designed and optimized according to the new business process modeling specification due to incompatibility of the business process data.
In order to achieve the above object, in one aspect, the present application provides a method for converting a format of business process data, including:
obtaining first business process data in a first format, wherein the first business process data are business process data which accord with a first business process modeling specification and are described by adopting a first programming language;
analyzing various basic element information describing the business process in the first business process data, wherein the various basic element information at least comprises the following steps: a plurality of node primitives forming the business process and configuration information related to the business process;
determining a second format to which the first business process data needs to be converted, wherein the second format corresponds to a second business process modeling specification and a second programming language;
creating a storage object which accords with the second business process modeling specification and adopts a second programming language, wherein the storage object is an extensible markup language (XML) object or an object notation (JSON) object;
adding the plurality of node primitives and the configuration information to the storage object to obtain reconstructed second business process data in the second format;
and storing the second business process data in the second format.
In a possible implementation manner, the configuration information related to the business process includes: the node primitive configuration information, the connection relation among different node primitives, the primitive relation configuration information and the service comprehensive configuration information;
the adding the plurality of node primitives and the configuration information to the storage object includes:
adding the plurality of node primitives and service comprehensive configuration information into the storage object;
importing a connection relation between different node primitives into the storage object;
configuring the primitive relation configuration information of the plurality of node primitives into the storage object;
and configuring node primitive configuration information corresponding to the node primitives in the storage object.
In another possible implementation manner, the configuration information related to the business process further includes: the position information of the pixel of the node pixel and the position information of the connecting line;
after the importing the connection line relationship between different node primitives into the storage object, the method further includes:
and adding the primitive position information of the node primitives and the position information of the connecting line between the node primitives to the storage object.
In another possible implementation manner, the storing the second business process data in the second format includes:
determining a plurality of business links related to the first business process data and the interrelation thereof based on a plurality of node primitives corresponding to the first business process data and the configuration information related to the business process;
and verifying that the second business process data has no format conversion error based on a second business process modeling rule according to a plurality of business links related to the first business process data and the interrelation of the business links, and storing the second business process data in the second format.
In another possible implementation manner, the verifying whether the second business process data has a format conversion error based on the second business process modeling rule according to the multiple business links involved in the first business process data and the interrelation of the multiple business links includes:
and sending the second business process data, the business links involved in the first business process and the interrelations of the business links to a block chain, wherein the block chain stores the second business process data in the block chain under the condition that the second business process data has no format conversion error by combining the business links involved in the first business process data and the interrelations of the business links based on the second business process modeling rule configured in an intelligent contract.
In another aspect, an apparatus for converting a format of business process data includes:
the data acquisition unit is used for acquiring first business process data in a first format, wherein the first business process data are business process data which accord with a first business process modeling specification and are described by adopting a first programming language;
a data analysis unit, configured to analyze multiple types of basic element information describing a business process in the first business process data, where the multiple types of basic element information at least include: a plurality of node primitives forming the business process and configuration information related to the business process;
the format determining unit is used for determining a second format to which the first business process data needs to be converted, wherein the second format corresponds to a second business process modeling specification and a second programming language;
the object creating unit is used for creating a storage object which accords with the second business process modeling specification and adopts a second programming language, and the storage object is an extensible markup language (XML) object or an object notation (JSON) object;
the information reconstruction unit is used for adding the plurality of node primitives and the configuration information into the storage object to obtain reconstructed second business process data in the second format;
and the data storage unit is used for storing the second business process data in the second format.
In another possible implementation manner, the configuration information related to the service flow obtained by the analysis of the data analysis unit includes: the node primitive configuration information, the connection relation among different node primitives, the primitive relation configuration information and the service comprehensive configuration information;
the information reconstruction unit includes:
the first information reconstruction unit is used for adding the plurality of node primitives and service comprehensive configuration information into the storage object;
the second information reconstruction unit is used for importing the connection line relation among different node primitives into the storage object;
a third information reconstructing unit, configured to configure the primitive relationship configuration information of the plurality of node primitives in the storage object;
and the fourth information reconstruction unit is used for configuring node primitive configuration information corresponding to the node primitives in the storage object.
In another possible implementation manner, the configuration information related to the service flow obtained by the analysis of the data analysis unit further includes: the position information of the pixel of the node pixel and the position information of the connecting line;
the device further comprises:
and the fifth information reconstruction unit is used for adding the primitive position information of the node primitives and the position information of the connecting line between the node primitives to the storage object after the second information reconstruction unit imports the connecting line relation between different node primitives into the storage object.
In another possible implementation manner, the data storage unit includes:
a link determining unit, configured to determine, based on a plurality of node primitives corresponding to the first business process data and configuration information related to the business process, a plurality of business links related to the first business process data and a correlation thereof;
and the verification storage unit is used for verifying that the second business process data has no format conversion error based on a second business process modeling rule according to the plurality of business links related to the first business process data and the interrelation of the plurality of business links, and storing the second business process data in the second format.
In another possible implementation manner, the verifying the storage unit includes:
and the checking and storing subunit is configured to send the second service flow data, the plurality of service links involved in the first service flow, and the interrelations among the plurality of service links to a block chain, where the block chain stores the second service flow data in the block chain when it is checked that the second service flow data has no format conversion error based on the second service flow modeling rule configured in the intelligent contract and in combination with the plurality of service links involved in the first service flow data and the interrelations among the plurality of service links.
As can be seen from the above, after the first business process data in the first format is obtained, the multiple pieces of basic element information included in the first business process data can be analyzed, and based on the second format to be converted, the XML object or JSON object conforming to the second format is constructed. Because the XML object or the JSON object is an object conforming to the second format, the primitive node information and the related configuration information in the analyzed plurality of basic element information are added into the XML object or the JSON object, and the primitive node information and the configuration information of the business process are actually reconstructed according to the second format, so that the first business process data is converted into the second business process data in the second format, and the processing requirement of the second business process modeling rule corresponding to the second format on the business process data can be met.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on the provided drawings without creative efforts.
Fig. 1 is a schematic flow chart illustrating a security management method according to an embodiment of the present application;
fig. 2 is a schematic flow chart illustrating a security management method according to an embodiment of the present application.
Fig. 3 is a flowchart illustrating an implementation of checking second service flow data based on a block chain in an embodiment of the present application;
fig. 4 shows a schematic structural diagram of a safety management and control device according to an embodiment of the present application.
Detailed Description
The method and the device are suitable for the situation that the format of the business process data needs to be changed due to the fact that the business process modeling specification is updated in a business process design scene, and the business process data designed based on one business process modeling specification can be converted into the business process data designed based on another business process modeling specification through the scheme of the embodiment of the method and the device, so that the situation that the business process data are incompatible in the business process design process is avoided.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without inventive step, are within the scope of the present disclosure.
Fig. 1 shows a format conversion method for business process data according to the present application, which is applied to any computer device, for example, an adapter may be run in the computer device, and the adapter may implement conversion of business process data to meet format requirements of different business process modeling specifications on the business process data. The method of the embodiment may include:
s101, first business process data in a first format is obtained.
The first business process data are business process data which accord with the first business process modeling specification and are described by adopting a first programming language.
It can be understood that the business process modeling specifications adopted by different business process designers are different, and the difference of the business process modeling specifications in designing the business process is mainly reflected by the difference of the adopted programming languages. For the convenience of distinction, the business process data which needs to be subjected to format conversion is referred to as first business process data which adopts a first business process modeling specification and has a first format.
For example, the first business process data may be business process data implemented based on HTML5, or process data implemented based on BPMN 2.0.
The first business process data comprises all business nodes and structural relations thereof in the business process designed based on the first business process modeling specification, configuration information and other related information required by the business process, and the business nodes are links forming the business process or steps required to be executed.
S102, analyzing various basic element information describing the business process in the first business process data.
The multiple kinds of basic element information are data components forming the business process corresponding to the first business process data.
It can be understood that, since the service flow is composed of service nodes, one service node can be represented graphically in the service flow design, and the graphical representation corresponding to each node is a node primitive, the node primitive represents one step or link in the service flow.
On the basis, the various basic elements of the first business process data at least comprise: a plurality of node primitives forming the business process and configuration information related to the business process. The information of the node primitive may include related information such as a name of the node primitive.
The configuration information related to the service flow may be configuration information related to each node primitive, and may further include other related configurations for reflecting specific implementation contents of the service flow, which is not limited herein.
S103, determining a second format to which the first business process data needs to be converted.
The second format corresponds to a second business process modeling specification and a second programming language.
The second format is different from the first format. The second format is a format of business process data designed by a second programming language corresponding to the second business process modeling specification.
The specific information of the second format may be configured in advance or input by the user, which is not limited.
If the business process data in the first format is the business process data realized based on the HTML5, the business process data in the second format is the business process data required to be realized based on the BPMN 2.0; alternatively, the business process data in the first format is business process data implemented based on BPMN2.0, and the business process data in the second format is business process data that needs to be implemented based on HTML 5.
And S104, creating a storage object which accords with the second business process modeling specification and adopts a second programming language.
The storage object is an extensible markup language (XML) object or an object notation (JSON) object.
Object Notation (JS) is a lightweight data exchange format. It stores and represents data in a text format that is completely independent of the programming language, based on a subset of ECMAScript (js specification set by the european computer association). The compact and clear hierarchy makes JSON an ideal data exchange language. The network transmission method is easy to read and write by people, is easy to analyze and generate by machines, and effectively improves the network transmission efficiency.
It will be appreciated that in a computer, an object is a special variable, in this application an object may be used for data storage, and the object has its own storage space.
In the application, the XML object or the JSON object is an XML object or a JSON object conforming to the second format, and therefore, the business process related data can be stored in the object in a form conforming to the second format.
And S105, adding a plurality of node primitives and configuration information to the storage object to obtain the reconstructed second business process data in the second format.
Because the storage object meets the second format, adding the node primitives and the configuration information to the storage object actually reconstructs the node primitives and the configuration information in the storage object according to the second format, so that the multiple primitive nodes and the configuration information of the business process stored in the storage object meet the second format, and second business process data meeting the second format is obtained.
It is understood that after the node primitives are added to the storage object, the relevant configuration information and other configuration information corresponding to the business process may be sequentially added for the node primitives.
The following description is made in conjunction with one possible scenario of the configuration information related to a business process.
In a possible case, the configuration information related to the business process at least includes: node primitive configuration information corresponding to each node primitive, connection line relations among different node primitives, primitive relation configuration information and service comprehensive configuration information.
The node primitive configuration information corresponding to the node primitive may include parameters in the node primitive, such as parameters representing a specific form of the node primitive and presentation contents in the node primitive. The node primitive configuration information may also include dependency relationship information of the node primitive, such as information of other node primitives that the node primitive needs to depend on or other trigger conditions.
The connection line relationship between the node primitives refers to information of an association relationship (also referred to as a migration line, such as a direction line representing an execution sequence or a dependency relationship, etc.) of connection lines between the node primitives, such as specific representation forms and directions of the connection lines, for example, the connection line of the node primitive 1 pointing to the node primitive 2 may be represented by the connection line 1 of an arrow.
The primitive relationship configuration information is also referred to as flow information, and is information reflecting a flow relationship between node primitives.
The service integrated configuration information may be other configuration information related to the service process besides the above configuration information, which is not limited to this.
Accordingly, adding a plurality of node primitives to a storage object and the configuration information may include the following:
adding the multiple node primitives and service comprehensive configuration information into a storage object;
importing a connection relation between different node primitives into the storage object;
configuring the primitive relation configuration information of the plurality of node primitives in a storage object;
and configuring node primitive configuration information corresponding to the node primitives in the storage object.
It can be understood that when various information is added to the storage object, a page to which the above related information is added in the storage object may be displayed, and therefore, the user may also perform other configuration or modification operations in the storage object as needed.
It can be understood that, in the service flow design, the position information of the primitive of each node primitive and the position information of the connection line between the node primitives are also designed. On the basis, in order to enable the position relationship of each primitive node and the connecting line thereof in the service flow obtained by the first service flow data to be reflected more accurately in the follow-up process, the method and the device can also add the primitive position information of each node primitive and the position information of the connecting line to the storage node after adding the relation between a plurality of node primitives to the storage object.
And S106, storing the second business process data in the second format.
It is understood that after storing the second business process data in the second format, the second business process data may be subsequently opened and identified based on the second business process modeling specification, so as to modify or optimize the business process based on the second business process data.
As can be seen from the above, after the first business process data in the first format is obtained, the multiple pieces of basic element information included in the first business process data can be analyzed, and based on the second format to be converted, the XML object conforming to the second format or the JSON object is constructed. Because the XML object or the JSON object is an object conforming to the second format, the primitive node information and the related configuration information in the analyzed plurality of basic element information are added into the XML object or the JSON object, and the primitive node information and the configuration information of the business process are actually reconstructed according to the second format, so that the first business process data is converted into the second business process data in the second format, and the processing requirement of the second business process modeling rule corresponding to the second format on the business process data can be met.
It can be understood that, in order to avoid a business process error caused by a conversion error of first business process data in a first format to second business process data in a second format, the process of storing the second business process data in the present application further includes a verification of the business process data. And if the second business process data is checked to have no format conversion error, storing the second business process data in the second format.
The following description is made in conjunction with one possible case of a format conversion method for business process data.
As shown in fig. 2, which shows another flow diagram of a method for converting a format of business process data according to the present application, the method of this embodiment may include:
s201, first business process data in a first format is obtained.
The first business process data are business process data which accord with the first business process modeling specification and are described by adopting a first programming language.
S202, analyzing various basic element information describing the business process in the first business process data.
Wherein, the multiple basic element information at least comprises: a plurality of node primitives forming the business process and configuration information related to the business process.
The configuration data related to the business process may specifically include: the method comprises the following steps of node primitive configuration information, connection line information among different node primitives, primitive relation configuration information, primitive position information of the node primitives, connection line position information and service comprehensive configuration information.
In the present embodiment, a case of configuration information of a business process is taken as an example for explanation, and other possible cases of configuration data related to the aforementioned business process are also applicable to the present embodiment, which is not limited to this.
S203, determining a second format to which the first business process data needs to be converted.
The second format corresponds to a second business process modeling specification and a second programming language.
S204, creating an XML object which accords with the second business process modeling specification and adopts a second programming language.
The above steps S201 to S204 can refer to the related description of the previous embodiment, and are not described herein again.
S205, adding a plurality of node primitives and service comprehensive configuration information into the XML object.
S206, importing the connection relation among different node primitives into the XML object.
For example, a specific form of a connecting line between different associated node primitives is introduced into the XML object to reflect the connection relationship between the node primitives.
S207, adding the primitive position information of the node primitives and the position information of the connecting line between the node primitives to the XML object.
For example, a connecting line and a position thereof between different node primitives may be configured for the imported node primitive in the XML object, and position information and the like corresponding to the node primitive may be set based on the primitive position information of the node primitive.
S208, configuring the primitive relation configuration information of the plurality of node primitives in the XML object.
For example, primitive relationship configuration information such as dependency relationships between node primitives is imported into the XML object.
S209, configuring node primitive configuration information corresponding to the node primitives in the XML object.
To understand the above steps S204 to S209, an example is described:
suppose that business process data designed based on HTML5 technology needs to be saved into an xml object that satisfies the bpmn rules. Then:
after the business process data is designed based on the HTML5, the designed node primitives and configuration information such as the structure of the node primitives can be sent to the engine adapter through a JSON format. The received business process data is divided into primitive node information, business comprehensive configuration information, node primitive configuration information, position information of node primitives and connecting lines and the like by a resolver of the adapter, and then the resolved information is packaged into an intermediate model of the adapter.
The intermediate model is converted at two ends, and specifically comprises the following steps: and creating an xml object doc which has a bpmn2.0 business modeling rule and meets the BPM flow format. Firstly, adding primitive node information and service comprehensive configuration information of an intermediate model in doc, secondly, adding a relationship between a migration line and a node primitive into doc, wherein the two relationships are established through a unique identifier ID of the node primitive (the relationship is that a primitive 1 points to a primitive 2 and is connected by the migration line 1), thirdly, adding position information of the node primitive and the migration line, wherein the position information describes positions of the node primitive and the line when a flow chart is opened for display, the primitive position information can be coordinate information, thirdly, adding primitive relation configuration information (for example, some basic information of a service flow, such as flow name, related data (for example, number of false days day is 3), service variables (which may be variable data related to the flow in service)), and lastly, adding node primitive configuration information (the relationship is established with the node through the unique identifier ID of the node (each node primitive has a unique node identifier ID), here, the relation is a rule configured for a certain node primitive, for example: running to the node triggers some event, configuring someone on the node to specify someone or some role to handle the node.
In the flow data realized based on the HTML5 technology, corresponding primitive nodes and configuration setting data are explained in a json structure, and after the adaptation, the related information is stored in an XML format. The realization is a model storage mode of the existing process, can meet the use requirement of the existing process and can get rid of the dependence on the prior art.
In this embodiment, the creation of the XML object is taken as an example, but it can be understood that if the JSON object which conforms to the second business process modeling specification and adopts the second programming language is created, the JSON object is also applicable to the embodiment, and no limitation is imposed on the JSON object.
S210, determining a plurality of business links related to the first business process data and the interrelation thereof based on a plurality of node primitives corresponding to the first business process data and the configuration information related to the business process.
For example, because the node primitive represents one service link, a plurality of service links related to the service flow described by the first service flow data can be determined according to a plurality of node primitives included in the first service flow data, and on this basis, the correlation between the service links can be determined according to the configuration information related to the service flow.
S211, according to the plurality of business links related to the first business process data and the interrelation of the plurality of business links, verifying that the second business process data has no format conversion error based on the second business process modeling rule, and storing the second business process data in the second format.
For example, it may be checked whether the service links of the service flow represented by the second service flow data are consistent with the types and the number of the service links represented by the first service flow data, it may also be checked whether the relationship of each service link in the service flow corresponding to the second service flow data is consistent with the relationship of each service link in the service flow corresponding to the first service flow data, and if both are consistent, it is determined that there is no format conversion error.
Further, in order to improve validity and reliability of the second business process data verification, the second business process data can be verified by combining the block chain.
For example, in one possible implementation, the second business process data, the plurality of business links involved in the first business process, and the interrelations of the plurality of business links may be sent to the blockchain. And the block chain stores the second business process data in the block chain under the condition that the second business process data has no format conversion error by combining a plurality of business links related to the first business process data and the interrelation of the business links based on a second business process modeling rule configured in the intelligent contract.
And pre-configuring an intelligent contract in the block chain according to a second business process modeling specification in advance, so that the intelligent contract can be used for identifying and verifying the second business process data.
It is understood that the blockchain system may incorporate a consensus mechanism in conjunction with the intelligent contract to store the second business process data, for example, referring to fig. 3, which shows a schematic flow chart of checking and storing the second business process data through the blockchain, and the flow may include:
s301, the computer device registers and obtains a public key and a private key of the computer device through the adapter.
S302, after the computer device signs an intelligent contract formulated based on the business process modeling specification of the second format by using a private key, the signed intelligent contract is transmitted into a block chain network.
After the intelligent contracts are transmitted into the block chain network, the block chain system utilizes a public key corresponding to the computer equipment to carry out an interface, then the block chain network is required to carry out unified verification, the intelligent contracts are diffused through the network and stored in each node of the block chain, once a consensus mechanism is triggered and started, the effectiveness of the intelligent contracts is verified by an administrator, once the intelligent contracts are successfully verified by an authority node (main node), the intelligent contracts are integrated into a Hash block ID and rapidly diffused to the whole network, and other nodes store the intelligent contracts.
S303, the computer equipment sends a plurality of business links related to the first business process data, the interrelation of the business links and second business process data to be stored to the block chain network.
S304, the block chain network verifies the second business process data based on the interrelation of the business links and the business links involved by the first business process data, and stores the second business process data in the block chain network system after the second business process data is verified to be qualified.
After determining that the second service process data can be stored in the blockchain network based on the intelligent contract, the blockchain network system stores the second service process data in the blockchain system in a similar process to the process of storing data in the blockchain system, which is not described herein again.
The application also provides a format conversion device of the business process data.
As shown in fig. 4, which shows a schematic structural diagram of a format conversion apparatus for business process data according to the present application, the apparatus of this embodiment may include:
a data obtaining unit 401, configured to obtain first business process data in a first format, where the first business process data is business process data that conforms to a first business process modeling specification and is described by using a first programming language;
a data parsing unit 402, configured to parse multiple types of basic element information describing a business process in the first business process data, where the multiple types of basic element information at least include: a plurality of node primitives forming the business process and configuration information related to the business process;
a format determining unit 403, configured to determine a second format to which the first business process data needs to be converted, where the second format corresponds to a second business process modeling specification and a second programming language;
an object creating unit 404, configured to create a storage object that meets the second business process modeling specification and adopts a second programming language, where the storage object is an extensible markup language XML object or an object notation JSON object;
an information reconstructing unit 405, configured to add the multiple node primitives and the configuration information to the storage object to obtain reconstructed second service flow data in the second format;
a data storage unit 406, configured to store the second business process data in the second format.
In a possible implementation manner, the configuration information related to the service flow obtained by the data analysis unit includes: the node primitive configuration information, the connection relation among different node primitives, the primitive relation configuration information and the service comprehensive configuration information;
the information reconstruction unit includes:
the first information reconstruction unit is used for adding the plurality of node primitives and service comprehensive configuration information into the storage object;
the second information reconstruction unit is used for importing the connection line relation among different node primitives into the storage object;
a third information reconstructing unit, configured to configure the primitive relationship configuration information of the plurality of node primitives in the storage object;
and the fourth information reconstruction unit is used for configuring node primitive configuration information corresponding to the node primitives in the storage object.
Optionally, the configuration information related to the service flow obtained by the analysis of the data analysis unit further includes: the position information of the pixel of the node pixel and the position information of the connecting line;
the device further comprises:
and the fifth information reconstruction unit is used for adding the primitive position information of the node primitives and the position information of the connecting line between the node primitives to the storage object after the second information reconstruction unit imports the connecting line relation between different node primitives into the storage object.
In yet another possible implementation manner, a data storage unit includes:
a link determining unit, configured to determine, based on a plurality of node primitives corresponding to the first business process data and configuration information related to the business process, a plurality of business links related to the first business process data and a correlation thereof;
and the verification storage unit is used for verifying that the second business process data has no format conversion error based on a second business process modeling rule according to the plurality of business links related to the first business process data and the interrelation of the plurality of business links, and storing the second business process data in the second format.
As an optional way, the verifying the storage unit includes:
and the checking and storing subunit is configured to send the second service flow data, the plurality of service links involved in the first service flow, and the interrelations among the plurality of service links to a block chain, where the block chain stores the second service flow data in the block chain when it is checked that the second service flow data has no format conversion error based on the second service flow modeling rule configured in the intelligent contract and in combination with the plurality of service links involved in the first service flow data and the interrelations among the plurality of service links.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. Meanwhile, the features described in the embodiments of the present specification may be replaced or combined with each other, so that those skilled in the art can implement or use the present application. For the device-like embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.
Claims (10)
1. A method for converting the format of service flow data is characterized by comprising the following steps:
obtaining first business process data in a first format, wherein the first business process data are business process data which accord with a first business process modeling specification and are described by adopting a first programming language;
analyzing various basic element information describing the business process in the first business process data, wherein the various basic element information at least comprises the following steps: a plurality of node primitives forming the business process and configuration information related to the business process;
determining a second format to which the first business process data needs to be converted, wherein the second format corresponds to a second business process modeling specification and a second programming language;
creating a storage object which accords with the second business process modeling specification and adopts a second programming language, wherein the storage object is an extensible markup language (XML) object or an object notation (JSON) object;
adding the plurality of node primitives and the configuration information to the storage object to obtain reconstructed second business process data in the second format;
and storing the second business process data in the second format.
2. The method of claim 1, wherein the configuration information related to the business process comprises: the node primitive configuration information, the connection relation among different node primitives, the primitive relation configuration information and the service comprehensive configuration information;
the adding the plurality of node primitives and the configuration information to the storage object includes:
adding the plurality of node primitives and service comprehensive configuration information into the storage object;
importing a connection relation between different node primitives into the storage object;
configuring the primitive relation configuration information of the plurality of node primitives into the storage object;
and configuring node primitive configuration information corresponding to the node primitives in the storage object.
3. The method of claim 2, wherein the configuration information related to the business process further comprises: the position information of the pixel of the node pixel and the position information of the connecting line;
after the importing the connection line relationship between different node primitives into the storage object, the method further includes:
and adding the primitive position information of the node primitives and the position information of the connecting line between the node primitives to the storage object.
4. The method of claim 1, wherein storing the second business process data in the second format comprises:
determining a plurality of business links related to the first business process data and the interrelation thereof based on a plurality of node primitives corresponding to the first business process data and the configuration information related to the business process;
and verifying that the second business process data has no format conversion error based on a second business process modeling rule according to a plurality of business links related to the first business process data and the interrelation of the business links, and storing the second business process data in the second format.
5. The method of claim 4, wherein the verifying whether the second business process data has a format conversion error according to the business links involved in the first business process data and the interrelations of the business links based on the second business process modeling rule comprises:
and sending the second business process data, the business links involved in the first business process and the interrelations of the business links to a block chain, wherein the block chain stores the second business process data in the block chain under the condition that the second business process data has no format conversion error by combining the business links involved in the first business process data and the interrelations of the business links based on the second business process modeling rule configured in an intelligent contract.
6. A device for converting a format of business process data, comprising:
the data acquisition unit is used for acquiring first business process data in a first format, wherein the first business process data are business process data which accord with a first business process modeling specification and are described by adopting a first programming language;
a data analysis unit, configured to analyze multiple types of basic element information describing a business process in the first business process data, where the multiple types of basic element information at least include: a plurality of node primitives forming the business process and configuration information related to the business process;
the format determining unit is used for determining a second format to which the first business process data needs to be converted, wherein the second format corresponds to a second business process modeling specification and a second programming language;
the object creating unit is used for creating a storage object which accords with the second business process modeling specification and adopts a second programming language, and the storage object is an extensible markup language (XML) object or an object notation (JSON) object;
the information reconstruction unit is used for adding the plurality of node primitives and the configuration information into the storage object to obtain reconstructed second business process data in the second format;
and the data storage unit is used for storing the second business process data in the second format.
7. The apparatus according to claim 2, wherein the configuration information related to the service flow obtained by the data analysis unit includes: the node primitive configuration information, the connection relation among different node primitives, the primitive relation configuration information and the service comprehensive configuration information;
the information reconstruction unit includes:
the first information reconstruction unit is used for adding the plurality of node primitives and service comprehensive configuration information into the storage object;
the second information reconstruction unit is used for importing the connection line relation among different node primitives into the storage object;
a third information reconstructing unit, configured to configure the primitive relationship configuration information of the plurality of node primitives in the storage object;
and the fourth information reconstruction unit is used for configuring node primitive configuration information corresponding to the node primitives in the storage object.
8. The apparatus according to claim 7, wherein the configuration information related to the service flow obtained by the data parsing unit further includes: the position information of the pixel of the node pixel and the position information of the connecting line;
the device further comprises:
and the fifth information reconstruction unit is used for adding the primitive position information of the node primitives and the position information of the connecting line between the node primitives to the storage object after the second information reconstruction unit imports the connecting line relation between different node primitives into the storage object.
9. The apparatus of claim 7, wherein the data storage unit comprises:
a link determining unit, configured to determine, based on a plurality of node primitives corresponding to the first business process data and configuration information related to the business process, a plurality of business links related to the first business process data and a correlation thereof;
and the verification storage unit is used for verifying that the second business process data has no format conversion error based on a second business process modeling rule according to the plurality of business links related to the first business process data and the interrelation of the plurality of business links, and storing the second business process data in the second format.
10. The apparatus of claim 9, wherein the verification storage unit comprises:
and the checking and storing subunit is configured to send the second service flow data, the plurality of service links involved in the first service flow, and the interrelations among the plurality of service links to a block chain, where the block chain stores the second service flow data in the block chain when it is checked that the second service flow data has no format conversion error based on the second service flow modeling rule configured in the intelligent contract and in combination with the plurality of service links involved in the first service flow data and the interrelations among the plurality of service links.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111014398.0A CN113626644B (en) | 2021-08-31 | 2021-08-31 | Format conversion method and device for business process data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111014398.0A CN113626644B (en) | 2021-08-31 | 2021-08-31 | Format conversion method and device for business process data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113626644A true CN113626644A (en) | 2021-11-09 |
| CN113626644B CN113626644B (en) | 2024-03-15 |
Family
ID=78388614
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111014398.0A Active CN113626644B (en) | 2021-08-31 | 2021-08-31 | Format conversion method and device for business process data |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113626644B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118014334A (en) * | 2024-04-08 | 2024-05-10 | 微神马科技（大连）有限公司 | Service recording method and system |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799962A (en) * | 2012-06-27 | 2012-11-28 | 南京合荣欣业信息技术有限公司 | Configuration type business flow system and realization method thereof |
| CN103077185A (en) * | 2012-12-18 | 2013-05-01 | 厦门雅迅网络股份有限公司 | Object-based user-defined information-expanding method |
| CN103179211A (en) * | 2013-03-26 | 2013-06-26 | 北京视博数字电视科技有限公司 | Cloud-computing-based data processing method and system of comprehensive operation support system |
| CN104991817A (en) * | 2015-06-25 | 2015-10-21 | 国网山东省电力公司 | Configurable integration method and system for information system |
| WO2019071230A1 (en) * | 2017-10-05 | 2019-04-11 | Baton Systems, Inc. | Data ingestion systems and methods |
| CN111177246A (en) * | 2019-12-27 | 2020-05-19 | 腾讯云计算（北京）有限责任公司 | Service data processing method and device |
| CN111427561A (en) * | 2020-03-26 | 2020-07-17 | 中国建设银行股份有限公司 | Service code generation method and device, computer equipment and storage medium |
| CN112597741A (en) * | 2020-12-14 | 2021-04-02 | 北京中电普华信息技术有限公司 | Data adaptation method and device |
| CN112860463A (en) * | 2021-03-22 | 2021-05-28 | 平安商业保理有限公司 | Service request forwarding method and device, computer equipment and readable storage medium |
-
2021
- 2021-08-31 CN CN202111014398.0A patent/CN113626644B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799962A (en) * | 2012-06-27 | 2012-11-28 | 南京合荣欣业信息技术有限公司 | Configuration type business flow system and realization method thereof |
| CN103077185A (en) * | 2012-12-18 | 2013-05-01 | 厦门雅迅网络股份有限公司 | Object-based user-defined information-expanding method |
| CN103179211A (en) * | 2013-03-26 | 2013-06-26 | 北京视博数字电视科技有限公司 | Cloud-computing-based data processing method and system of comprehensive operation support system |
| CN104991817A (en) * | 2015-06-25 | 2015-10-21 | 国网山东省电力公司 | Configurable integration method and system for information system |
| WO2019071230A1 (en) * | 2017-10-05 | 2019-04-11 | Baton Systems, Inc. | Data ingestion systems and methods |
| CN111177246A (en) * | 2019-12-27 | 2020-05-19 | 腾讯云计算（北京）有限责任公司 | Service data processing method and device |
| CN111427561A (en) * | 2020-03-26 | 2020-07-17 | 中国建设银行股份有限公司 | Service code generation method and device, computer equipment and storage medium |
| CN112597741A (en) * | 2020-12-14 | 2021-04-02 | 北京中电普华信息技术有限公司 | Data adaptation method and device |
| CN112860463A (en) * | 2021-03-22 | 2021-05-28 | 平安商业保理有限公司 | Service request forwarding method and device, computer equipment and readable storage medium |
Non-Patent Citations (3)
| Title |
|---|
| D PENG等: "json documents proceesing using situation oriented database", ACTA POLYTECHNICA HUNGARICA, vol. 17, no. 8, 31 August 2020 (2020-08-31), pages 29 - 40 * |
| 康波;马庆珍;司道军;孟祥飞;: "云化与业务流技术支撑的新一代超级计算应用平台", 计算机工程与科学, vol. 42, no. 10, 15 October 2020 (2020-10-15), pages 1852 - 1858 * |
| 王永超;鲁鸣鸣;: "面向金融行业的大数据迁移的研究与实现", 计算机工程与应用, vol. 54, no. 13, 1 July 2018 (2018-07-01), pages 93 - 99 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118014334A (en) * | 2024-04-08 | 2024-05-10 | 微神马科技（大连）有限公司 | Service recording method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113626644B (en) | 2024-03-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11699201B2 (en) | System and method for blockchain-based network transitioned by a legal contract | |
| Petriu et al. | Applying the UML performance profile: Graph grammar-based derivation of LQN models from UML specifications | |
| Malavolta et al. | Providing architectural languages and tools interoperability through model transformation technologies | |
| CN102395950A (en) | Communicating with data storage systems | |
| EP1387262A1 (en) | Method to generate synchronization contracts for software components and web services | |
| WO2019090005A1 (en) | System and method for a blockchain-based network transitioned by a legal contract | |
| Kourtesis et al. | Increased reliability in SOA environments through registry-based conformance testing of web services | |
| CN112882844B (en) | Joint debugging method, device and storage medium based on network front end and network back end | |
| Mirandola et al. | A reliability model for service component architectures | |
| CN110750243A (en) | Project code development method and system | |
| CN113434175A (en) | Data processing method, device, storage medium and equipment | |
| Li et al. | Breeze graph grammar: a graph grammar approach for modeling the software architecture of big data‐oriented software systems | |
| van Berlo et al. | Creating information delivery specifications using linked data | |
| CN113626644B (en) | Format conversion method and device for business process data | |
| Altamimi et al. | Performance analysis roundtrip: automatic generation of performance models and results feedback using cross-model trace links | |
| CN110737431A (en) | Software development method, development platform, terminal device and storage medium | |
| CN114510262A (en) | Interface request parameter verification method and device | |
| Tounsi et al. | Using SoaML models and event-B specifications for modeling SOA design patterns | |
| CN117850771A (en) | Business application development platform, method and storage medium for web service | |
| Shan et al. | Towards integrated service adaptation a new approach combining message and control flow adaptation | |
| Popovic et al. | Formal verification of distributed transaction management in a SOA based control system | |
| US10157360B1 (en) | Smart bricks information system | |
| Woods et al. | The system context architectural viewpoint | |
| Habibi et al. | Generating test as a web service (TaaWS) through a method-based attribute grammar | |
| Karimpour et al. | Early performance assessment in component‐based software systems |
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 |