Project process processing method and processing system thereof

Abstract

The invention provides a project process processing method and a processing system thereof. The processing method comprises the following steps. The processor defines a matching model according to a relationship between the plurality of document data and a relationship between the plurality of document data and the plurality of components. In a design phase of the target project, the processor calculates a plurality of components according to the matching model to output a plurality of recommended components. The processor performs a packaging operation to form a scheme in accordance with the plurality of selected components. Each node in the scheme comprises a corresponding scheme coordinate. In the runtime phase, the processor specifies a first node of the plurality of nodes as a starting node to start executing the target item according to scheme coordinates of the input data instance. The first node and the input data instance have the same scheme coordinate, and the project process is designed based on data as a main body.

Description

Technical Field

[0001] The present invention relates to a processing method, in particular to a processing method for designing and operating a project flow and a processing system thereof. Background Art

[0002] Enterprises can use workflow engines to design the process of target projects to implement various business services through multiple tasks connected in series. However, since the current workflow engine designs project processes based on process instances, the following scenarios will be encountered when running projects and they cannot be continued. For example, when the materials required for the manufacturing industry need to be split, the running project cannot process these materials in batches or jump to other processes. Furthermore, when various materials need to be merged and processed based on commonality, the running project cannot perform corresponding processing on these materials. For another example, when the materials change, the running project cannot respond to the change and cause process abnormalities. Summary of the invention

[0003] The present invention is directed to a project process processing method, which is applied to the manufacturing industry and can design the project process based on data to increase the operational flexibility of the project process.

[0004] According to an embodiment of the present invention, a method for processing a project flow of the present invention includes the following steps. A matching model is defined by a processor according to a relationship between a plurality of document data, and a relationship between a plurality of document data and a plurality of components. In the design phase of a target project, a plurality of components are calculated by a processor according to the matching model to output a plurality of recommended components. In the design phase, a packaging operation is performed by a processor according to a plurality of components and a plurality of selected components among a plurality of recommended components to form a first solution. Each of the plurality of nodes in the first solution includes corresponding solution coordinates. In the running phase, a first node among the plurality of nodes is designated by a processor as a starting node for executing an input data instance in a target project according to the solution coordinates of an input data instance to start executing the target project. The first node and the input data instance have the same solution coordinates.

[0005] According to an embodiment of the present invention, a processing system of a project flow of the present invention includes a storage device and a processor. The storage device stores a matching model. The processor is coupled to the storage device. The processor performs the following operations. A matching model is defined according to the relationship between multiple document data, and the relationship between multiple document data and multiple components. In the design phase of a target project, multiple components are calculated according to the matching model to output multiple recommended components. In the design phase, a packaging operation is performed to form a first solution based on multiple components and multiple selected components in a plurality of recommended components. Each of the multiple nodes in the first solution includes corresponding solution coordinates. In the running phase, according to the solution coordinates of the input data instance, a first node among the multiple nodes is designated as a starting node for executing the input data instance in the target project to start executing the target project. The first node and the input data instance have the same solution coordinates.

[0006] Based on the above, the project flow processing method and project flow processing system of the present invention can establish a target project of a data instance system by encapsulating selected components into a solution according to a matching model associated with the data. Therefore, the project flow processing method can specify a starting node according to the solution coordinates of the input data instance during operation to respond to various data requirements, thereby increasing the operational flexibility of the target project.

[0007] In order to make the above features and advantages of the present invention more clearly understood, embodiments are given below with reference to the accompanying drawings for detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a circuit block diagram of a project flow processing system according to an embodiment of the present invention;

[0009] Figure 2 is a flowchart of a method for processing a project flow according to an embodiment of the present invention;

[0010] Figure 3 is an operational schematic diagram of a processing system according to an embodiment of the present invention;

[0011] Figure 4 is a schematic diagram of the operation of a processing system in a design phase according to an embodiment of the present invention;

[0012] Figure 5 is an operational schematic diagram of a processing system according to an embodiment of the present invention;

[0013] Figure 6 is an operation schematic diagram of a processing system in an operation stage according to an embodiment of the present invention;

[0014] FIG. 7A to FIG. 7C is an operation schematic diagram of a processing system in a running stage according to another embodiment of the present invention;

[0015] FIG. 8A to FIG. 8B is an operation schematic diagram of a processing system in a running stage according to another embodiment of the present invention;

[0016] Fig. 9 is an operation schematic diagram of a processing system in a running stage according to another embodiment of the present invention;

[0017] Fig.10 FIG. 4 is a schematic diagram of the operation of a processing system in a running stage according to another embodiment of the present invention.

[0018] Description of Reference Numerals

[0019] 100: Processing system;

[0020] 110: storage device;

[0021] 120: processor;

[0022] 111: matching model;

[0023] 200: Enterprise systems;

[0024] 311: Registered Entity;

[0025] D1: document data;

[0026] D11: Purchase order data;

[0027] D12: Purchase requisition data;

[0028] D2: Components;

[0029] D21: API component for converting a purchase requisition into a purchase order (i.e., request to purchase);

[0030] D3: Recommended components;

[0031] DIN, DIN': input data instances;

[0032] DIN0: input data;

[0033] DN1: source data instance;

[0034] DN11, DN12, DN13: source data instances;

[0035] DN2: task data instance;

[0036] DN21, DN21-1, DN21-2, DN23, DN24: task data instance;

[0037] DN23DN24: the third data instance;

[0038] DN24: the fourth data instance;

[0039] DN3: mapping relationship table;

[0040] DN31, DN32, DN33, DN34, DN35: columns;

[0041] IDS1~IDSi, IDS2, IDS2', IDS4': scheme coordinates;

[0042] L1~L4: directed connection;

[0043] N1~Ni, N1~N6, N4', N31, N31_1, N32, N33_2, N33_3, N33_4, N34, N34_1, N35: nodes;

[0044] PN1: first option;

[0045] PN2: second option;

[0046] S210~S240, S710~S770: steps. DETAILED DESCRIPTION

[0047] Reference will now be made in detail to exemplary embodiments of the present invention, examples of which are illustrated in the accompanying drawings. Whenever possible, the same reference numerals are used in the drawings and the description to refer to the same or like parts.

[0048] Figure 1 FIG. 1 is a circuit block diagram of a project flow processing system according to an embodiment of the present invention. Figure 1 The project process processing system 100 applies data mining and workflow engine. The processing system 100 performs packaging operations according to application data such as data type, state and characteristics of source data in the enterprise system 200 to create an executable target project.

[0049] In this embodiment, the processing system 100 of the project flow can be set in the cloud, so that the user can connect to the processing system 100 through an electronic device to execute the processing system 100. The processing system 100 can be, for example, a Software as a Service (SaaS) server to execute the corresponding SaaS application through an application programming interface (API). In some embodiments, the processing system 100 can be set in the ground terminal within the enterprise, so that the user can connect the processing system 100 with other systems set in the cloud through an electronic device to input / output data, so as to execute the corresponding SaaS application through the API.

[0050] In the present embodiment, the processing system 100 is coupled to the enterprise system 200. The processing system 100 can call the enterprise system 200 through an API to access and process source data in the enterprise system 200. The source data may, for example, include various documents regarding business services, and various orders. In the present embodiment, a user may operate an electronic device to execute the enterprise system 200 through an API, and then execute various business services through the enterprise system 200. For example, an electronic device may call the enterprise system 200 through an API to implement various functions (such as signing and approving purchase orders) in manufacturing scenario applications. The enterprise system 200 may, for example, be an enterprise resource planning (ERP) system. The electronic device may, for example, be a mobile phone, a tablet computer, a laptop computer, and a desktop computer.

[0051] In this embodiment, the processing system 100 may include a storage device 110 and a processor 120. The storage device 110 stores a matching model 111. The storage device 110 accesses the enterprise system 200 to obtain source data. In this embodiment, the storage device 110 may also store computing software and the like for implementing the algorithms, programs and data related to the functions of data mining, software design, software packaging, various calculations, tests, and software operation of the present invention. The storage device 110 may be, for example, a dynamic random access memory (DRAM), a flash memory, a non-volatile random access memory (NVRAM), or a combination of these memories.

[0052] In the present embodiment, the processor 120 is coupled to the storage device 110. The processor 120 accesses the storage device 110 and can execute data in the storage device 110 and source data from the enterprise system 200. In the present embodiment, the processor 120 can be, for example, a signal converter, a Field Programmable Gate Array (FPGA), a Central Processing Unit (CPU), or other programmable general-purpose or special-purpose microprocessor (Microprocessor), a Digital Signal Processor (DSP), a programmable controller, an Application Specific Integrated Circuits (ASIC), a Programmable Logic Device (PLD) or other similar devices or a combination of these devices, which can load and execute computer program related firmware or software to achieve data mining, software design, software packaging, various calculations, testing, software operation, and execution functions.

[0053] Figure 2 This is a flowchart of a method for processing a project flow according to an embodiment of the present invention. Figure 1 as well as Figure 2 , the processing system 100 may execute steps S210 to S240. The order of these steps S210 to S240 is only an example and is not limited thereto. In this embodiment, steps S210 to S240 may be applied to the following exemplary situations.

[0054] In this embodiment, the processor 120 accesses and processes source data in the enterprise system 200. The processed source data may include, for example, a plurality of document data D1 and a plurality of components D2. The document data D1 may be, for example, instantiated source data to indicate various state characteristics of the document. The components D2 may be, for example, instantiated source data to indicate various logical characteristics of processing a single play.

[0055] In step S210, the processor 120 defines a matching model 111 according to the relationship between the plurality of document data D1 and the relationship between the plurality of document data D1 and the plurality of components D2. The matching model 111 may be, for example, a structured data model to indicate the relationship between various data D1 and D2.

[0056] In this embodiment, the processing system 100 can be operated at design time to package one or more solutions into an executable target project. In detail, in step S220, in the design phase of the target project, the processor 120 calculates multiple components D2 according to the matching model 111 to output multiple recommended components D3. In other words, the processor 120 performs data driving according to the matching model 111 and these components D2 to select multiple recommended components D3 with association from these components D2.

[0057] Continuing with the above description, in step S230, in the design phase of the target project, the processor 120 performs a packaging operation to form a first solution PN1 based on a plurality of selected components from the plurality of components D2 and the plurality of recommended components D3. That is, the user operates the electronic device to access the plurality of components D2 and the plurality of recommended components D3, so that the user and the processing system 100 interactively process (e.g., select) the plurality of selected components as the components required in the target project. In this embodiment, the processor 120 may repeatedly perform step S230 multiple times to form one or more other solutions (not shown).

[0058] In this embodiment, the first scheme PN1 may include multiple nodes N1~Ni, where i is a positive integer. These nodes N1~Ni may respectively include one or more selected components. These nodes N1~Ni indicate various process operations. These nodes N1~Ni may also include multiple scheme coordinates IDS1~IDSi respectively. These scheme coordinates IDS1~IDSi respectively indicate the positions of these nodes N1~Ni themselves in the target project. For example, the first node M1 among these nodes N1~Ni includes the scheme coordinate IDS1 to indicate that this node N1 is located at a certain node N1 in the first scheme PN1.

[0059] In this embodiment, the processing system 100 can be operated in the operation phase to execute the target project according to the input data. In the operation phase, the processing system 100 accesses and processes the input data in the enterprise system 200. The input data can be, for example, the data to be processed in the enterprise system 200 (for example, an actual order). The input data instance DIN can be, for example, instantiated input data. The input data instance DIN can include a solution coordinate IDS2. The solution coordinate IDS2 indicates the location of the operation bit associated with the input data instance DIN in the target project.

[0060] Specifically, in step S240, in the running stage, the processor 120 specifies the first node (e.g., node N1) in the first solution PN1 as the starting node for executing the input data instance DIN in the target project according to the solution coordinates IDS2 of the input data instance DIN to start executing the target project. In other words, the processor 120 finds the matching node N1 in the process according to the characteristics of the input data instance DIN (e.g., solution coordinates IDS2), and starts executing the target project with this node N1.

[0061] In this embodiment, the first node N1 as the starting node and the input data instance DIN have the same solution coordinates, that is, the solution coordinates IDS1 of the first node N1 and the solution coordinates IDS2 of the input data instance DIN are the same.

[0062] It is worth mentioning here that the processing method of the project flow is a design and operation method based on data. By encapsulating multiple selected components into a first solution PN1 according to a matching model 111 associated with the data, the processing method can establish a target project of the data instance system. In this way, when running the target project, the processing method can specify the starting node according to the solution coordinate IDS2 of the input data instance DIN, so as to respond to various requirements of input data and source data in the enterprise system 200, so as to be applied to the manufacturing industry and increase the operational flexibility of the project flow.

[0063] Figure 3 FIG. 1 is a schematic diagram of the operation of a processing system according to an embodiment of the present invention. Figure 1 as well as Figure 3 The project process processing system 100 establishes a data instance system and defines a matching model 111 (for example, Figure 3 The registration entity 311) is used to illustrate the implementation details of the instantiated document data D1 and the component D2, and step S210.

[0064] In this embodiment, the processor 120 accesses a plurality of documents in the enterprise system 200. Such documents may be, for example, various documents related to business services, and may include documents in the physical world such as purchase orders, purchase orders, and maintenance orders.

[0065] In this embodiment, the processor 120 performs instantiation and data mining on multiple documents to generate multiple document data D1 and multiple components D2. Specifically, the processor 120 performs data mining on multiple documents to generate multiple features related to these documents. In addition, the processor 120 instantiates these features to generate multiple document data D1 and multiple components D2 with an ontology structure. The processor 120 can also perform data mining on these document data D1 and multiple components D2 to enrich the multiple document data D1 and multiple components D2. In other words, the processor 120 maps the data of the physical world to the knowledge ontology in the digital world, and creates attributes and logical relationships between these instantiated data to form a large and complex relationship network (i.e., matching model 111).

[0066] In detail, the plurality of document data D1 is first multi-element structure data and can be abstracted as a data ontology. The data ontology indicates a certain type of data and can be further abstracted into other multiple related sub-data ontologies by the processor 100.

[0067] In this embodiment, the definition of the first multivariate structure data (i.e., data ontology) may include, for example, a data type definition, a data field description, a unique keyword (key) in the data, and a data status. The data type definition indicates that the document data D1 belongs to a certain type of data, such as financial data such as a purchase order or a purchase requisition. The data field description indicates the fields included in the document data D1, such as order number, orderer, time, and other fields. The unique keyword in the data indicates that a certain field included in the document data D1 can identify the document data D1 as a unique identifier of the document data D1. The data status indicates the status of the document data D1.

[0068] In this embodiment, the relationship between different first multi-structured data (i.e., data ontologies) may include, for example, inheritance relationships, mapping relationships, and including relationships. An inheritance relationship indicates that there is an inheritance relationship between multiple data ontologies, such as humans inheriting from animals. A mapping relationship indicates that multiple data ontologies have the same meaning, such as the Chinese word apple and the English word apple have the same meaning. An including relationship indicates that multiple data ontologies have a tree-like relationship to include the definitions of other data ontologies, such as a family including a father, a mother, and a child.

[0069] For example, if Figure 3As shown, the document data D1 may include, for example, purchase order data D11 and purchase requisition data D12. The purchase order data D11 defines a purchase order based on the node N31. The purchase order data D11 may include a field description node N33_1 represented as "purchase requisition number" and a field description node N34_1 represented as "purchase order number". The purchase requisition data D12 defines a purchase requisition based on the node N32. The purchase requisition data D12 may include a field description node N33_2 represented as "purchase requisition number".

[0070] In addition, the plurality of components D2 are second multi-element structure data and can be abstracted as a component ontology. The component ontology indicates certain logical concepts and can be further abstracted into other plurality of related sub-component ontologies by the processor 100.

[0071] In this embodiment, the second multivariate structure data (i.e., component ontology) is used to process data and to combine with other component ontology to complete various complex business logics. The types of component ontology may include, for example, execution class components, judgment class components, control class components, storage class components, and user interface (UI) class components. Execution class components indicate the execution of a section of logic, such as calling an API, and executing a script. Judgment class components indicate the execution of logical judgment. Control class components indicate the execution of control processes, such as stop, pause, loop, and gateway processes. Storage class components indicate the storage or acquisition of data. UI class components indicate the display of data.

[0072] In this embodiment, the relationship between different second multivariate structure data (i.e., component ontologies) may include, for example, dependency relationships, output relationships, and include relationships. A dependency relationship indicates that the execution of a component ontology depends on other data ontologies or other component ontologies. An output relationship indicates that the execution of a component ontology includes external output, such as including returning certain parameters in the operation of calling an API. An include relationship indicates that multiple component ontologies have a tree-like relationship to include other component ontologies, such as a large component ontology that is composed of multiple small component ontologies.

[0073] For example, if Figure 3 As shown, the component D2 may include, for example, an API component D21 for converting a purchase requisition into a purchase order (i.e., request transfer). The request transfer API component D21 defines a logic for executing an API call based on the node N35. The request transfer API component D21 may include a dependent node N33_3 represented as "purchase requisition number" and an output node N33_4 represented as "return purchase order". In other words, the request transfer API component D21 depends on a field of a purchase requisition number and outputs a purchase order accordingly.

[0074] In this embodiment, the matching model 111 includes structural data matching multiple document data D1 (i.e., first multi-element structural data) and multiple components D2 (i.e., second multi-element structural data). In other words, the matching model 111 indicates the ontological relationship between the first multi-element structural data (i.e., data ontology) and the second multi-element structural data (i.e., component ontology), and is represented by a relationship graph.

[0075] For example, if Figure 3 As shown, the matching model 111 may include, for example, a registration entity 311. The registration entity 311 defines a registration entity related to a purchase requisition. The registration entity 311 may include a node N33 represented as "purchase requisition number" and a node N34 represented as "purchase order number". The registration entity 311 can be formed by mapping data structures having equivalent meanings in the purchase order data D11, the purchase requisition data D12, and the purchase requisition API component D21 into one entity.

[0076] Figure 4 FIG. 1 is a schematic diagram of the operation of a processing system in a design phase according to an embodiment of the present invention. Figure 1 as well as Figure 4 , the project process processing system 100 operates at design time, and the implementation details of steps S220 to S230 are illustrated by way of example.

[0077] During the design time, the processor 120 generates a solution (e.g., the first solution PN1) by constructing various components D2-D3, and generates the final target project by constructing various solutions. The constructions between the various components D2-D3 and the various solutions are multiple executable processes, and indicate corresponding business services respectively.

[0078] In this embodiment, since the processing system 100 constructs a data instance system including multiple document data D1, multiple components D2, and matching model 111, the processing system 100 can perform data driving according to the matching model 111 to recommend multiple suitable recommended components D3 through the processor 100. In some embodiments, the processor 100 can also recommend packaged solutions stored in the storage device 110 according to the matching model 111, so as to provide users and the processing system 100 with interactive use or modified use.

[0079] In this embodiment, the user and the processing system 100 interact with each other to select components (i.e., selected components) used in the design flow from the plurality of components D2 and the plurality of recommended components D3 recommended by the processor 100. Then, the user and the processing system 100 interact with each other to package the selected components into one or more solutions according to a flow structure, and package the aforementioned solutions into a target project.

[0080] In detail, taking the design of the first scheme PN1 as an example, the processor 120 gathers multiple selected components to generate multiple nodes N1~N6. That is, each node N1~N6 may include one or more selected components (which may be different components D2). For example, node N1 is a module represented as "obtaining purchase requisition information" and includes one or more calling API components. Node N2 is a module represented as "converting purchase requisition to purchase order" and includes one or more calling API components. Node N3 is a module represented as "determining whether it is successful" and includes one or more control-type components. Node N4 is a module represented as "temporary storage" and includes one or more storage-type components. Node N5 is a module represented as "judgment result" and includes one or more judgment-type components. Node N6 is a module represented as "approval" and includes one or more execution-type components.

[0081] In addition, taking the design of the first scheme PN1 as an example, the processor 120 connects multiple nodes N1 to N6 in series according to multiple directed links (Links) L1 to L4 to form the first scheme PN1. That is, each directed connection L1 to L4 is directed from one node to and connected to another node, and may include one or more conditions. For example, directed connection L1 points from node N1 to node N2. Directed connection L2 points from node N2 to node N3. Directed connection L3 is a line segment represented as "failure" and points from node N3 to node N4. Directed connection L4 is a line segment represented as "success" and points from node N5 to node N6.

[0082] It should be noted that the first scheme PN1 includes a first identifier. The first identifier serves as a unique entity identifier of this scheme PN1 and can be represented as planId. In this scheme PN1, multiple nodes N1~N6 include different multiple second identifiers. These second identifiers serve as unique entity identifiers of these nodes N1~N6 in this scheme PN1, and can be represented as nodeId. In this way, the scheme coordinates of each node N1~N6 include a first identifier planId and a corresponding second identifier nodeId. In other words, the scheme coordinates of node N1 can be represented as two-dimensional coordinates of (planId, nodeId) as positioning coordinates in the entire target project. Other nodes N2~N6 respectively include their own independent scheme coordinates, so that the processor 100 can directly locate specific nodes N2~N6 according to the scheme coordinates.

[0083] Figure 5 FIG. 1 is a schematic diagram of the operation of a processing system according to an embodiment of the present invention. Figure 1 as well as Figure 5The project process processing system 100 encapsulates a batch of specific data according to the source data (such as multiple orders and multiple documents) in the enterprise system 200 and defines a mapping relationship table related to the aforementioned specific data to illustrate the implementation details of step S240.

[0084] In this embodiment, the processor 120 accesses multiple documents and multiple task data in the enterprise system 200. These documents may be, for example, various documents related to business services, and may include documents in the physical world such as purchase orders, purchase orders, and maintenance orders. These task data may be, for example, various specific orders for business services, and may include a combination of various documents. In other words, each task data may include one or more corresponding documents.

[0085] In this embodiment, the processor 120 instantiates multiple documents and task data to generate multiple source data instances DN1 and multiple task data instances DN2 respectively. The processor 120 defines a mapping relationship table according to the relationship between the multiple source data instances DN1 and the multiple task data instances DN2. In other words, the processor 120 maps the real data to be substituted into the process into the digital world, and creates a mapping relationship between the instantiated data to form a mapping relationship table DN3.

[0086] In detail, the multiple source data instances DN1 are various instantiated documents. Each source data instance DN1 may include a corresponding third identifier (expressed as "dataId") and a corresponding document (expressed as "data"). These third identifiers serve as unique entity identifiers of the multiple source data instances DN1. These documents are the documents themselves of the multiple source data instances DN1. In this embodiment, the multiple source data instances DN1 are stored in the storage device 110.

[0087] For example, taking source data instance DN11 as an example, source data instance DN11 is an instantiated document (for example, a purchase order). Source data instance DN11 may include a third identifier represented as "data001". This third identifier ("data001") serves as the unique entity identifier of this source data instance DN11. In addition, taking source data instance DN13 as an example, source data instance DN13 is an instantiated document (for example, a purchase order). Source data instance DN13 may include a third identifier represented as "data003". This third identifier ("data003") serves as the unique entity identifier of this source data instance DN13. Source data instances DN11 and DN13 may also respectively include structural data such as corresponding documents (for example, purchase orders), source data types, and source data status.

[0088] In addition, multiple task data instances DN2 are various specific orders that have been instantiated. Each task data instance DN2 may include a corresponding fourth identifier (expressed as "instanceId") and a corresponding solution coordinate (expressed as "location"). These fourth identifiers serve as unique entity identifiers of multiple task data instances DN2. These solution coordinates are the current locations of multiple task data instances DN2 when executing the target project.

[0089] For example, taking task data instance DN21 as an example, task data instance DN21 is an instantiated order (for example, an order including a purchase requisition and a purchase order). Task data instance DN21 may include a fourth identifier represented as "inst001". This fourth identifier ("inst001") serves as the unique entity identifier of this task data instance DN21. Task data instance DN21 may include a plan coordinate represented as "plan01, node01". This plan coordinate ("plan01, node01") serves as the current position of this task data instance DN21 when executing the target project.

[0090] In this embodiment, the task data instance DN21 may also include structural data such as a data ontology identifier, variables, and document images. The data ontology identifier indicates a source data type. The variable indicates the process variable carried when executing the target project. The document image indicates the image of a document (such as a purchase requisition and a purchase order). In this embodiment, the task data instance DN21 may also include document mappings such as a purchase requisition corresponding to the source data instance DN11 and a purchase order corresponding to the source data instance DN13.

[0091] Continuing with the above description, the mapping relationship table DN3 indicates the mapping relationship between the task data instance DN21 and multiple source data instances DN11 and DN13. Taking the task data instance DN21 as an example, the mapping relationship table DN3 includes multiple columns DN31-DN32 related to the task data instance DN21. In detail, column DN31 may include an identifier represented as "inst001", an identifier represented as "data001", and a scheme coordinate represented as "plan01, node01" to indicate that the location ("plan01, node01") of the task data instance DN21 in the target project accesses the source data instance DN11 corresponding to the purchase order. In addition, column DN32 may include an identifier represented as "inst001", an identifier represented as "data003", and a scheme coordinate represented as "plan02, node03" to indicate that the same task data instance DN21 accesses the source data instance DN13 corresponding to the purchase order at another location ("plan02, node03") in the target project.

[0092] Figure 6 FIG. 1 is a schematic diagram of the operation of a processing system in an operation stage according to an embodiment of the present invention. Figure 1 as well as Figure 6 The project process processing system 100 operates in the running stage, and the implementation details of step S240 are illustrated by way of example.

[0093] In the running phase, the processor 120 accesses the input data to be substituted into the process in the enterprise system 200. The processor 120 instantiates the input data into an input data instance DIN based on the aforementioned data instance system. That is, the input data instance DIN can be, for example, Figure 5 The task data instance DN21 is shown. The input data instance DIN may include a plan coordinate IDS2 represented as "plan01, node01".

[0094] In this embodiment, since the input data instance DIN carries the solution coordinate IDS2, and the node N2 in the target project has the same solution coordinate IDS2, the processor 120 locates the input data instance DIN on the solution coordinate IDS2. That is, the processor 120 specifies the node N2 in the first solution PN1 for executing the input data instance DIN according to the solution coordinate IDS2. Then, the processor 120 starts to execute the input data instance DIN in the node N2, and after completing the operation in the node N2, the processor 120 points to the next node N3 according to the process.

[0095] In some applications, since the input data instance DIN carries variables, when the input data instance DIN is changed to the input data instance DIN' in the running stage, the processor 120 jumps the input data instance DIN' to the corresponding position according to the solution coordinates IDS2' of the changed input data instance DIN'. The aforementioned position may be, for example, a node N4' in another solution PN2. This node N4' has the same solution coordinates IDS4' as the solution coordinates IDS2'.

[0096] It is understandable that the designed multiple solutions PN1-PN2 constitute a map (ie, target project). As long as the starting position of the input data instance DIN is specified, various input data instances DIN can arbitrarily shuttle in this map and continue to be executed according to the corresponding solution.

[0097] FIG. 7A to FIG. 7C FIG. 1 is a schematic diagram of the operation of a processing system in another embodiment of the present invention during the operation phase. Figure 1 , Fig. 7A as well as Figure 7CThe project process processing system 100 operates in the running stage and executes multiple steps S710~S770 to illustrate the implementation details of step S240.

[0098] exist Fig. 7A In the operation phase shown, the processor 120 encapsulates the input data DIN0 in the enterprise system 200 into (i.e., instantiates) an input data instance DIN executable by the project. In step S710, the processor 120 determines whether the input data instance DIN specifies the solution coordinate IDS2 in the project based on the input data instance DIN. When the input data instance DIN does not specify the solution coordinate IDS2, it means that the input data instance DIN does not carry the solution coordinate IDS2, and the processing system 100 continues with steps S721 to S722.

[0099] In step S721, the processor 120 performs a solution matching calculation based on the input data instance DIN. In detail, the processor 120 calculates the input data instance DIN based on the mapping relationship table DN3 to find one or more recommended solutions with a matching data structure. In this embodiment, the user and the processing system 100 interactively process (for example, select) a matching solution to continue the project. In step S722, the user and the processing system 100 interactively select the best solution (for example, the first solution PN1) to assign the input data instance DIN to this solution PN1 to continue step S723.

[0100] On the other hand, when the input data instance DIN specifies the solution coordinates IDS2, it means that the input data instance DIN carries the solution coordinates IDS2, and the processing system 100 specifies the input data instance DIN to the first solution PN1 to continue step S723. In step S723, taking the specified or selected first solution PN1 as an example, the processor 120 executes the first solution PN1 by executing steps S731 to S737. In this embodiment, after the execution of the first solution PN1 is completed, the processor 120 continues step S770 according to the current data instance to execute the second solution PN2, thereby completing the entire process project.

[0101] exist Figure 7B In the operation phase shown, the processor 120 executes the first solution PN1. Specifically, in step S731, the processor 120 locates the input data instance DIN to a specified node (e.g., Figure 6 Alternatively, in step S731, when the input data instance DIN does not specify the solution coordinate IDS2, the processor 120 searches for a starting node (e.g., Figure 6 Node N2).

[0102] In step S732, the processor 120 persists the information of the current data instance (i.e., the input data instance DIN). The aforementioned information is, for example, a process variable including the input data instance DIN. In step S733, the processor 120 issues a start node execution event. In step S734, the processor 120 parses the current node (e.g., Figure 6 That is, the processor 120 determines the component type included in the node according to the node type of the current node, so as to Figure 7C The corresponding parsing operation is performed in the steps.

[0103] exist Figure 7C In the operation phase shown, at step S741, the processor 120 determines the node type of the current node. For example, at step S751, the processor 120 determines that the node type of the current node is a control node, indicating that the node includes one or more control components. At step S761, when the node type of the current node is a control node, the processor 120 obtains the related components of the control node to perform operations such as starting and ending the process node, initiating events, looping, and splitting.

[0104] In other examples of node types, the processor 120 determines that the node type of the current node is a gateway node, indicating that the node includes one or more control class components. The processor 120 obtains the relevant components of the node to perform operations such as exclusive gateway and parallel gateway. Alternatively, the processor 120 determines that the node type of the current node is a storage node, indicating that the node includes one or more storage class components. The processor 120 obtains the relevant components of the node to perform various storage medium support add, delete, query and modify (CRUD) operations.

[0105] For another example, the processor 120 determines that the node type of the current node is an execution node, indicating that this node includes one or more execution-type components. The processor 120 obtains the relevant components of this node to perform operations such as executing API calls, scripts, and java codes. Alternatively, the processor 120 determines that the node type of the current node is a rendering node, indicating that this node includes one or more UI-type components. The processor 120 obtains the relevant components of this node to perform operations such as initiating a manual task rendering page. Alternatively, the processor 120 determines that the node type of the current node is other types of nodes, so that the processor 120 obtains the relevant components of this node to perform operations such as executing various other extension nodes.

[0106] Back to Figure 7BIn the operation phase shown, the processor 120 executes steps S735 to S737 after executing the current node N2. In step S735, the processor 120 persists the information of the current data instance (i.e., the input data instance DIN of the node N2) after execution. The aforementioned information includes, for example, the process variables of the current data instance. In step S736, the processor 120 issues an event to end the execution of the node. In step S737, the processor 120 outputs the current data instance after execution to enter the next node (e.g., Figure 6 Node N3), and repeat steps S731 to S737 according to the current data instance.

[0107] It should be noted that since the project is a data-based design process, data instances in the running stage can be split, merged, or changed, so that the processor 100 continues to execute the processed data instances in the corresponding specified solution coordinates.

[0108] FIG. 8A to FIG. 8B FIG. 1 is a schematic diagram of the operation of a processing system in another embodiment of the present invention during the operation phase. Figure 1 , Fig. 8A as well as Figure 8B , the project process processing system 100 operates in the running stage to illustrate the implementation details of the splitting operation.

[0109] Taking the input data instance DIN as a task data instance DN21 as an example (hereinafter referred to as input data instance DN21), according to the mapping relationship table DN3, the input data instance DN21 includes the purchase requisition corresponding to the source data instance DN11 and the purchase order corresponding to the source data instance DN13. Figure 5 The same applies to the description of task data instance DN21.

[0110] like Figure 8BAs shown, in the running stage, the processor 120 splits the input data instance DN21 into a first data instance DN21-1 and a second data instance DN21-2 according to the mapping relationship table DN3. The first data instance DN21-1 includes a fourth identifier represented as "inst001" and includes a scheme coordinate represented as "plan01, node01". The second data instance DN21-2 includes a fourth identifier represented as "inst002" and includes a scheme coordinate represented as "plan02, node03". In other words, the processor 100 splits the original input data instance DN21 into two data instances DN21-1 and DN21-2. The first data instance DN21-1 is a copied data instance to include part of the data in the original input data instance DN21. The second data instance DN21-2 is a newly created data instance to divide the other part of the data in the original input data instance DN21.

[0111] In this embodiment, according to column DN31 in mapping relationship table DN3, first data instance DN21-1 indicates accessing source data instance DN11 corresponding to purchase requisition at corresponding plan coordinate ("plan01, node01"). In addition, according to column DN33 in mapping relationship table DN3, second data instance DN21-2 indicates accessing source data instance DN13 corresponding to purchase order at corresponding plan coordinate ("plan02, node03").

[0112] like Fig. 8A As shown, in the running stage, after the input data instance DN21 is split, the processor 120 specifies the corresponding node N2 among the multiple nodes as the starting node for executing this first data instance DN21-1 in the target project according to the plan coordinates ("plan01, node01") of the first data instance ("inst001") DN21-1. The aforementioned node N2 has the same plan coordinates as the first data instance DN21-1, and can be, for example, the node N2 represented as "node 01" in the first plan PN1.

[0113] In addition, in the running stage, after the input data instance DN21 is split, the processor 120 specifies the corresponding node N3 among the multiple nodes as the starting node for executing this second data instance DN21-2 in the target project according to the plan coordinates ("plan02, node03") of the second data instance ("inst002") DN21-2. The aforementioned node N3 has the same plan coordinates as the second data instance DN21-2, and can be, for example, the node N3 represented as "node 03" in the second plan PN2.

[0114] Fig. 9FIG. 1 is a schematic diagram of the operation of a processing system in another embodiment of the present invention during the operation phase. Figure 1 as well as Fig. 9 , the project flow processing system 100 operates in the running stage to illustrate the implementation details of the merging operation.

[0115] Taking the input data instance DIN as a task data instance DN21-1 as an example (hereinafter referred to as input data instance DN21-1), according to the column DN31 in the mapping relationship table DN3, the input data instance DN21-1 includes a fourth identifier represented as "inst001", a plan coordinate represented as "plan01,node01", and a document mapping corresponding to the purchase requisition of the source data instance DN11. The input data instance DN21-1 can refer to Figure 8B The same applies to the description of the first data instance DN21-1.

[0116] Taking another task data instance DN23 as an example (hereinafter referred to as the third data instance DN23), according to column DN34 in the mapping relationship table DN3, the third data instance DN23 includes a fourth identifier represented as "inst002", a plan coordinate represented as "plan01,node03", and other documents corresponding to the source data instance DN12, and a document mapping such as a purchase order corresponding to the source data instance DN13. The third data instance DN23 can refer to Figure 8B The same applies to the description of the second data instance DN21-2.

[0117] like Fig. 9 As shown, in the running stage, the processor 120 merges the input data instance DN21-1 and the third data instance DN23 into a fourth data instance DN24 according to the mapping relationship table DN3. The fourth data instance DN24 includes a fourth identifier represented as "inst003" and includes plan coordinates represented as "plan01, node01". According to column DN35 in the mapping relationship table DN3, the merged fourth data instance DN24 also includes a purchase requisition corresponding to the source data instance DN11, other documents corresponding to the source data instance DN12, and a purchase order corresponding to the source data instance DN13 and other document mappings. In other words, the processor 100 integrates the existing multiple data instances DN21-1 and DN24 into a newly created data instance to merge all the data in these data instances DN21-1 and DN24.

[0118] In the running stage, after the multiple data instances DN21-1 and DN24 are merged, the processor 120 designates a corresponding fourth node among the multiple nodes as a starting node for executing the merged fourth data instance DN24 in the target project according to the plan coordinates ("plan01, node01") of the fourth data instance ("inst003") DN24. The aforementioned fourth node has the same plan coordinates as the fourth data instance DN24, which may be, for example, Fig. 8A The node N2 is shown as "node 01" in the first solution PN1.

[0119] Fig.10 FIG. 1 is a schematic diagram of the operation of a processing system in another embodiment of the present invention during the operation phase. Figure 1 as well as Fig.10 The project process processing system 100 operates in the running stage to illustrate the implementation details of the change operation.

[0120] Taking the input data instance DIN as a task data instance DN21 as an example, according to the mapping relationship table DN3, the task data instance DN21 includes the purchase requisition corresponding to the source data instance DN11 and the purchase order corresponding to the source data instance DN13. Figure 5 The same applies to the description of task data instance DN21.

[0121] like Fig.10 As shown, in the operation phase, when multiple documents in the enterprise system 200 are changed, the instantiated documents (i.e., multiple source data instances DN1) are also changed accordingly. When multiple documents are changed, the processor 120 accesses multiple task data instances associated with the multiple documents that have changed according to the mapping relationship table DN3.

[0122] Taking the source data instance DN12 represented as "data002" as an example, it is assumed that the source data instance DN12 is changed to be modified into an additional purchase order. Since the purchase order is associated with the source data instance DN11, and according to the mapping relationship table DN3, it can be known that the purchase order is also associated with the task data instance DN21, the processor 120 traces back other source data instances DN11 related to the changed source data instance DN12. In addition, the processor 120 traces back the task data instance DN21 related to this source data instance DN11.

[0123] That is, the processor 120 traces the task data instance DN21 related to the changed document according to the mapping table DN3. In this embodiment, the user and the processing system 100 interactively process to read the task data instance DN21, or add a mark to the task data instance DN21 for subsequent processing.

[0124] In summary, the project flow processing method and processing system of the present invention are data-based design and operation methods. At design time, by encapsulating multiple selected components into solutions in the target project according to the matching model associated with the data, the processing method can establish a target project of the data instance system. In the operation stage, the processing method does not need to construct design instances such as process instances and node instances based on the flow, so the processing method can execute the target project in a lightweight mode. In addition, since the target project is designed with data as the main body, in the operation stage, the processing method can jump the current data instance to any node or any solution in the target project according to the solution coordinates of the data instance, and no adverse side effects such as conflicts will occur. In some embodiments, the processing method can perform operations such as splitting and merging data instances according to the image relationship table to increase the operational flexibility of the project flow. In some embodiments, the processing method can trace back to the relevant data instance when the document changes to increase the operational flexibility of the project flow.

[0125] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or perform equivalent replacements on some or all of the technical features therein. However, these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for processing a project process, characterized in that: include: By means of a processor, a matching model is defined according to the relationship between the plurality of document data and the relationship between the plurality of document data and the plurality of components; By means of the processor, in a design phase of a target project, the plurality of components are calculated according to the matching model to output a plurality of recommended components; By the processor, in the design phase, performing a packaging operation to form a first solution according to the plurality of components and a plurality of selected components from the plurality of recommended components, wherein each of the plurality of nodes in the first solution comprises a corresponding solution coordinate; as well as Through the processor, in the running stage, according to the solution coordinates of the input data instance, the first node among the multiple nodes is designated as the starting node for executing the input data instance in the target project to start executing the target project, wherein the first node and the input data instance have the same solution coordinates.

2. The method for processing a project flow according to claim 1, characterized in that: Also includes: Accessing a plurality of documents in an enterprise system through the processor; as well as The processor performs instantiation and data mining on the plurality of documents to generate the plurality of document data and the plurality of components.

3. The method for processing a project flow according to claim 1, characterized in that: The plurality of document data and the plurality of components are first multivariate structure data and second multivariate structure data respectively, wherein the matching model includes structure data matching the first multivariate structure data and the second multivariate structure data.

4. The method for processing a project flow according to claim 1, characterized in that: In the design phase, the step of performing the packaging operation to form the first solution according to the plurality of components and the plurality of selected components from the plurality of recommended components includes: By the processor, assembling the plurality of selected components to generate the plurality of nodes; and The processor connects the plurality of nodes in series according to a plurality of directed connections to form the first solution.

5. The method for processing a project flow according to claim 4, characterized in that: The first scheme includes a first identifier, and the plurality of nodes include a plurality of different second identifiers, such that the scheme coordinates of each of the plurality of nodes include the first identifier and the corresponding second identifier.

6. The method for processing a project flow according to claim 1, characterized in that: Also includes: Accessing, by means of the processor, a plurality of documents and a plurality of task data in the enterprise system, wherein each of the plurality of task data includes the corresponding plurality of documents; By means of the processor, instantiating the plurality of documents and the task data to generate a plurality of source data instances and a plurality of task data instances respectively; as well as A mapping relationship table is defined by the processor according to the relationship between the multiple source data instances and the multiple task data instances.

7. The method for processing a project flow according to claim 6, characterized in that: Each of the source data instances includes a corresponding third identifier and the corresponding document, and each of the task data instances includes a corresponding fourth identifier and the corresponding solution coordinates.

8. The method for processing a project flow according to claim 6, characterized in that: Also includes: By means of the processor, according to the mapping relationship table, the input data instance is split into a first data instance and a second data instance; By the processor, according to the solution coordinates of the first data instance, specifying a corresponding second node among the plurality of nodes as a starting node for executing the first data instance in the target project; as well as By the processor, according to the solution coordinates of the second data instance, a corresponding third node among the multiple nodes is designated as a starting node for executing the second data instance in the target project.

9. The method for processing a project flow according to claim 6, characterized in that: Also includes: By means of the processor, according to the mapping relationship table, merging the input data instance and a third data instance in the plurality of task data instances into a fourth data instance; as well as By the processor, according to the solution coordinates in the fourth data instance, a corresponding fourth node among the plurality of nodes is designated as a starting node for executing the fourth data instance in the target project.

10. The method for processing a project flow according to claim 6, characterized in that: Also includes: When the multiple documents are changed, the processor accesses the multiple task data instances associated with the multiple documents that have changed according to the mapping relationship table.

11. A project process processing system, characterized in that: include: A storage device for storing a matching model; as well as A processor, coupled to the storage device, performs the following operations: Defining the matching model according to the relationship between a plurality of document data and the relationship between the plurality of document data and a plurality of components; In a design phase of a target project, calculating the plurality of components according to the matching model to output a plurality of recommended components; In the design phase, a packaging operation is performed to form a first solution according to the plurality of components and a plurality of selected components from the plurality of recommended components, wherein each of the plurality of nodes in the first solution comprises a corresponding solution coordinate; as well as During the running phase, according to the scheme coordinates of the input data instance, a first node among the multiple nodes is designated as a starting node for executing the input data instance in the target project to start executing the target project, wherein the first node and the input data instance have the same scheme coordinates.

12. The processing system according to claim 11, characterized in that The processor also performs the following operations: Access multiple documents in enterprise systems; and Instantiation and data mining are performed on the plurality of documents to generate the plurality of document data and the plurality of components.

13. The processing system according to claim 11, characterized in that The plurality of document data and the plurality of components are first multivariate structure data and second multivariate structure data respectively, wherein the matching model includes structure data matching the first multivariate structure data and the second multivariate structure data.

14. The processing system according to claim 11, characterized in that The processor also performs the following operations: By the processor, assembling the plurality of selected components to generate the plurality of nodes; and The processor connects the plurality of nodes in series according to a plurality of directed connections to form the first solution.

15. The processing system according to claim 14, characterized in that The first scheme includes a first identifier, and the plurality of nodes include a plurality of different second identifiers, such that the scheme coordinates of each of the plurality of nodes include the first identifier and the corresponding second identifier.

16. The processing system according to claim 11, characterized in that The processor also performs the following operations: Accessing a plurality of documents and a plurality of task data in an enterprise system, wherein each of the plurality of task data includes the corresponding plurality of documents; Instantiating the plurality of documents and the task data to generate a plurality of source data instances and a plurality of task data instances respectively; as well as A mapping relationship table is defined according to the relationship between the multiple source data instances and the multiple task data instances.

17. The processing system according to claim 16, characterized in that Each of the source data instances includes a corresponding third identifier and the corresponding document, and each of the task data instances includes a corresponding fourth identifier and the corresponding solution coordinates.

18. The processing system according to claim 16, characterized in that The processor also performs the following operations: According to the mapping relationship table, split the input data instance into a first data instance and a second data instance; According to the solution coordinates of the first data instance, specifying a corresponding second node among the plurality of nodes as a starting node for executing the first data instance in the target project; as well as According to the solution coordinates of the second data instance, a corresponding third node among the plurality of nodes is designated as a starting node for executing the second data instance in the target project.

19. The processing system according to claim 16, characterized in that The processor also performs the following operations: According to the mapping relationship table, merging the input data instance and a third data instance in the plurality of task data instances into a fourth data instance; as well as According to the solution coordinates in the fourth data instance, a corresponding fourth node among the plurality of nodes is designated as a starting node for executing the fourth data instance in the target project.

20. The processing system according to claim 16, characterized in that The processor also performs the following operations: When the multiple documents are changed, the multiple task data instances associated with the multiple documents that have changed are accessed according to the mapping relationship table.

Images