CN111651140A - Service method and device based on workflow - Google Patents
Service method and device based on workflow Download PDFInfo
- Publication number
- CN111651140A CN111651140A CN202010349213.0A CN202010349213A CN111651140A CN 111651140 A CN111651140 A CN 111651140A CN 202010349213 A CN202010349213 A CN 202010349213A CN 111651140 A CN111651140 A CN 111651140A
- Authority
- CN
- China
- Prior art keywords
- data
- service
- service data
- target process
- systems
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the application discloses a service method and a service device based on workflow, which are applied to a server, wherein the method comprises the following steps: receiving a service data source, wherein the service data source comprises at least one service data, determining at least one deployment object corresponding to the service data source according to the service data source, deploying each object in the at least one deployment object, and obtaining target process data, wherein the target process data comprises: the method comprises the steps of obtaining a target process definition file by running target process data and task data and process instance data, reading form data corresponding to the task data and submitting the form data, so that a service system is divided into different modules, each module is independent, the modules can be used for executing different tasks, coupling and influence among systems are reduced, complexity of system architecture design is reduced, and stability among the systems is improved.
Description
Technical Field
The present application relates to the technical field of workflows, and in particular, to a service method and device based on workflows.
Background
At present, a traditional workflow application mode needs to integrate an SDK (Software Development Kit) for Development, which leads to a huge database system in an application scene depending on the SDK, and increases the complexity of architecture design.
Disclosure of Invention
The embodiment of the application provides a service method and device based on workflow, which are beneficial to reducing the complexity of system architecture design and improving the stability among systems.
A first aspect of an embodiment of the present application provides a service method based on a workflow, which is applied to a server, and the method includes:
receiving a service data source, wherein the service data source comprises at least one service data;
determining at least one deployment object corresponding to the service data source according to the service data source;
deploying each object in the at least one deployment object to obtain target process data, wherein the target process data comprises: task data, process instance data;
operating the target process data to obtain a target process definition file;
and reading form data corresponding to the task data, and submitting the form data.
A second aspect of the embodiments of the present application provides an apparatus for a workflow-based service, where the apparatus is applied to a server, and the apparatus includes: a receiving unit, a determining unit, a deploying unit, an operating unit and a reading unit, wherein,
the receiving unit is configured to receive a service data source, where the service data source includes at least one service data;
the determining unit is configured to determine, according to the service data source, at least one deployment object corresponding to the service data source;
the deployment unit is configured to deploy each object in the at least one deployment object to obtain target process data, where the target process data includes: task data, process instance data;
the operation unit is used for operating the target process data to obtain a target process definition file;
and the reading unit is used for reading the form data corresponding to the task data and submitting the form data.
A third aspect of embodiments of the present application provides a server, where the server includes a processor, an input device, an output device, and a memory, where the processor, the input device, the output device, and the memory are connected to each other, where the memory is used to store a computer program, and the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to the first aspect of embodiments of the present application.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program for electronic data exchange, where the computer program makes a computer perform part or all of the steps as described in the first aspect of embodiments of the present application.
A fifth aspect of embodiments of the present application provides a computer program product, wherein the computer program product comprises a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps as described in the first aspect of embodiments of the present application. The computer program product may be a software installation package.
The embodiment of the application has at least the following beneficial effects:
the embodiment of the application is applied to a server, and can receive a service data source, wherein the service data source comprises at least one service data, at least one deployment object corresponding to the service data source is determined according to the service data source, each object in the at least one deployment object is deployed to obtain target process data, and the target process data comprises: the method comprises the steps of obtaining a target process definition file by running target process data and task data and process instance data, reading form data corresponding to the task data and submitting the form data, so that a service system is divided into different modules, each module is independent, the modules can be used for executing different tasks, coupling and influence among systems are reduced, complexity of system architecture design is reduced, and stability among the systems is improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1A is a schematic structural diagram of a workflow-based service according to an embodiment of the present application;
fig. 1B is a schematic flowchart of a workflow-based service method according to an embodiment of the present application;
FIG. 1C provides a system architecture diagram of a workflow-based service according to an embodiment of the present application;
FIG. 1D provides a system architecture diagram of a workflow-based service according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a workflow-based service method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a workflow-based service method according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a server according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a service device based on workflow according to an embodiment of the present application.
Detailed Description
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 making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," and the like in the description and claims of the present application and in the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
In order to better understand the embodiments of the present application, methods of applying the embodiments of the present application will be described below.
The servers mentioned in the embodiments of the present application may include, but are not limited to, a background server, a component server, a cloud server, a service system server, or a software server, which are merely examples, and are not exhaustive and include, but are not limited to, the above devices.
Referring to fig. 1A, as shown in fig. 1A, a schematic structural diagram of a workflow-based service system provided in this embodiment of the present application is applied to a server, and the workflow-based service system includes an interface service module 101, a deployment service module 102, a running service module 103, and a form service module 104, wherein,
the interface service module 101 is configured to receive a service data source, where the service data source includes at least one service data;
the deployment service module 102 is configured to determine, according to the business data source, at least one deployment object corresponding to the business data source, and deploy each object in the at least one deployment object to obtain target process data, where the target process data includes: task data, process instance data;
the operation service module 103 is configured to operate the target process data to obtain a target process definition file;
the form service module 104 is configured to read form data corresponding to the task data and submit the form data.
Optionally, the system may further include: the history service module 105 may, among other things,
the history service module 105 is configured to store the process instance data that is completed or terminated as history process instance data.
In a possible example, in the aspect of determining at least one deployment object corresponding to the service data source according to the service data source, the deployment module 102 is specifically configured to:
determining a file type of each service data in the at least one service data to obtain at least one file type, wherein each file type at least corresponds to one service data;
and determining at least one deployment object corresponding to the service data source according to the at least one file type.
In a possible example, in terms of the operating the target process data to obtain the target process definition file, the operation service module 103 is specifically configured to:
matching the task data with a plurality of label models in a preset database to obtain a plurality of matching values, wherein each label model in the preset database is obtained by training a plurality of historical data, and the historical data comprises at least one of the following data: historical task data, historical process instance data and historical variable data;
selecting a mark model corresponding to the maximum matching value in the multiple matching values as a target mark model;
acquiring a target service scene corresponding to the target marking model;
and determining the process definition file corresponding to the target service scene as a target process definition file.
In one possible example, the interface service module 101 is further specifically configured to:
sending N calling requests to N systems, wherein N is a positive integer greater than 1;
if M calling requests pass, detecting whether M systems corresponding to the M calling requests can be called or not, wherein M is a positive integer less than or equal to N;
if P systems can be called, P service data corresponding to the P systems are obtained through an interface, and the P service data form the service data source, wherein P is a positive integer smaller than or equal to M.
In a possible example, in the aspect of detecting whether M systems corresponding to M call requests can be called, the interface service module 101 is further specifically configured to:
acquiring current operating states of the M systems to obtain M current operating states, wherein each system corresponds to one current operating state;
obtaining P systems corresponding to the current operating states which are idle states according to the M current operating states;
and determining that P systems exist in the M systems corresponding to the M calling requests and can be called.
It can be seen that, according to the workflow-based service system provided by the embodiment of the application, the service system is divided into different modules, and each module is independent from the other module, so that different tasks can be executed, the coupling and influence between the systems are reduced, the complexity of system architecture design is reduced, and the stability between the systems is improved.
Referring to fig. 1B, fig. 1B is a schematic flowchart of a workflow-based service method according to an embodiment of the present application, where the method includes the following steps:
101. receiving a service data source, wherein the service data source comprises at least one service data.
The method may be applied to a server including a service system based on a workflow, where the service data source may be from different platforms or systems, the server may access different platforms or systems through an HTTP (HyperText Transfer Protocol) Protocol to invoke different service data, the service data source may include at least one service data, each service data may correspond to one platform or system, the platform or system may support a front-end application party, an android application party, an ios (internet operating system) application party, and the like, and is not limited herein, and the platform or system may also be a cloud server or a local database, and the like, and is not limited herein.
In addition, the business data may refer to a business object that is a flow supported in the workflow process, such as an application report, a contract countersign, and the like, which is not limited herein.
Optionally, as shown in fig. 1C, which is a system architecture diagram of a workflow-based service system, as shown in the diagram, a service invoker may be used to represent a platform or a system from which the service data comes, and the service invoker may include: a front-end application party, an android application party, an ios (internet Operating system) application party, and the like, which are not limited herein, the workflow-based service system includes: the service calling party can carry out information interaction with the service system based on the workflow, namely the service system can call the service data of the service calling party to generate a service data source.
Optionally, before the step 101, before receiving the service data source, the method may further include the following steps:
a1, sending N calling requests to N systems, wherein N is a positive integer greater than 1;
a2, if M calling requests pass, detecting whether M systems corresponding to the M calling requests can be called, wherein M is a positive integer less than or equal to N;
a3, if P systems can be called, obtaining P service data corresponding to the P systems through an interface, wherein the P service data form the service data source, and P is a positive integer less than or equal to M.
Wherein, if the service system based on the workflow needs to call service data of other systems, or other systems need to transmit data to the service system, the server can send N call requests to the N systems, the call requests are used for calling or extracting service data, the N systems are N different systems, the N systems can be obtained by dividing types corresponding to the service data, in a specific implementation, the server can broadcast N call requests to the N systems through an interface, the call requests can also carry call information, N is a positive integer greater than 1, since not all the requests can successfully reach the N systems, if M call requests in the N call requests are passed, it can further detect whether M systems corresponding to the M call requests can be called, wherein M is a positive integer less than or equal to N.
Further, there may be some systems that cannot be called due to being occupied or overtime request, that is, if there are P systems that can be called in the M systems, the service data corresponding to the P systems can be obtained through the interface to obtain P service data, where the P service data constitute the service data source, and P is a positive integer less than or equal to M.
In one possible example, the step a2, detecting whether M systems corresponding to M invocation requests can be invoked, may include the following steps:
a21, obtaining the current operation states of the M systems to obtain M current operation states, wherein each system corresponds to one current operation state;
a22, obtaining P systems corresponding to the current operation state being an idle state according to the M current operation states;
a23, determining that P systems exist in the M systems corresponding to the M calling requests and can be called.
In a specific implementation, the server may query information returned by the M systems, and if the returned information is delayed, it means that the system is in a busy state, then the server may obtain current operating states of the M systems to obtain the M current operating states, and since each system is not necessarily in an idle state, P systems, part of which is in an idle state, may be deleted from the M current operating states, indicating that the P systems all have a call condition.
102. And determining at least one deployment object corresponding to the service data source according to the service data source.
In addition, each service data included in the service data source may correspond to one deployment object, and the deployment object may be used to deploy, query, or delete the service data in the workflow.
In a possible example, in the step 102, determining, according to the service data source, at least one deployment object corresponding to the service data source may include the following steps:
21. determining a file type of each service data in the at least one service data to obtain at least one file type, wherein each file type at least corresponds to one service data;
22. and determining at least one deployment object corresponding to the service data source according to the at least one file type.
Wherein the file type may include at least one of: the method includes the steps of storing a file, a local file, a database file, a coding file acquired from an interface, and the like in a cloud, wherein each service data may correspond to one file type, and in a specific implementation, at least one file type may be obtained based on the file type corresponding to each service data in at least one service data, and finally, at least one deployment object corresponding to at least one service data in the service data source is generated, so that the at least one deployment object may be deployed in a targeted manner.
103. Deploying each object in the at least one deployment object to obtain target process data, wherein the target process data comprises: task data, process instance data.
After the deployment of the at least one deployment object is completed, that is, after each service data is deployed, the server generates target process data, where the target process data may include at least one of the following: task data, process instance data, variable data, event data, and the like, without limitation.
104. And operating the target process data to obtain a target process definition file.
For example, if the deployment object corresponds to a query object, a task of generating query data may be executed, the query task may be executed, task data after query is obtained, and the target flow definition file may be generated according to the task data.
In one possible example, the step 104 of executing the target process data to obtain the target process definition file may include the following steps:
41. matching the task data with a plurality of label models in a preset database to obtain a plurality of matching values, wherein each label model in the preset database is obtained by training a plurality of historical data;
42. selecting a mark model corresponding to the maximum matching value in the multiple matching values as a target mark model;
43. acquiring a target service scene corresponding to the target marking model;
44. and determining the process definition file corresponding to the target service scene as a target process definition file.
The preset database can be set by system default or a user, the preset database can include a plurality of label models, a neural network model can be preset, and a plurality of historical data corresponding to the service system are trained through the preset neural network model to obtain the plurality of label models, each label model can correspond to a service scenario, and the service scenario can include at least one of the following: cloud services, local services, administrative services, form services, and the like, without limitation, the historical data may include at least one of: historical task data, historical process instance data, historical variable data, and the like, and the task data may refer to data generated by executing the business data, without being limited thereto.
In specific implementation, the task data may be matched with a plurality of label models in a preset database to obtain a plurality of matching degrees, and a label model corresponding to a maximum matching value is selected as a target label model, so that a model with the highest matching degree with the task data may be obtained, a target service scene corresponding to the target label model may be obtained, a mapping relationship between the service scene and a process definition file may be preset, specifically, templates of different process definition files may be preset based on different service scenes, and finally, a target process definition file corresponding to the target service scene may be determined based on the mapping relationship.
105. And reading form data corresponding to the task data, and submitting the form data.
In the workflow-based service system, a server can read form contents corresponding to the task data during execution, submit the task form data and upload the form data.
Optionally, the method may further include the steps of:
b1, determining at least one service type corresponding to the at least one service data, wherein each service data at least corresponds to one service type;
and B2, packaging the form data and the target flow data into at least one template data based on the at least one service type, wherein each template data corresponds to one service type.
In addition, each of the service data may correspond to a service type, and the service type may include at least one of the following: query, delete, create, etc., without limitation; in a specific implementation, at least one service type corresponding to at least one service data corresponding to the service data source may be determined, based on the at least one service type, both form data and target process data obtained by executing the completed service data are encapsulated as one template data, and each template data corresponds to one service type.
Optionally, a template database may be preset in the server, the at least one template data is stored in the preset template database, when new service data is accessed to the system, the service type of the service data may be determined, template data matched with the service type is extracted from the preset template data, and a process definition file corresponding to the service data is generated based on the template data.
Optionally, after the step 105, the following steps may be further included: and storing the process instance data of which the operation is finished or terminated as historical process instance data.
The server may be preset with a historical database, and store the process instance data generated by executing the at least one service data or historical tasks, related variables and the like related to the process instance into the preset historical database, so as to facilitate data re-search or data check, or facilitate management of the service system.
Optionally, as shown in fig. 1D, which is a system architecture diagram of a workflow-based service system, based on fig. 1C, fig. 1D further includes a service middleware, where the service middleware includes: the historical database and the template database may be configured to provide an intermediate service for the workflow-based service system, for example, may be configured to store process instance data generated by the at least one service data, or historical tasks, related variables, and the like related to the process instance, or store the at least one template data in a preset template database, when a new service data is accessed to the system, determine a service type of the service data, extract template data matching the service type from the preset template data, and generate a process definition file corresponding to the service data based on the template data.
It can be seen that, the workflow-based service method described in the embodiment of the present application is applied to a server, and the method includes: receiving a service data source, wherein the service data source comprises at least one service data, determining at least one deployment object corresponding to the service data source according to the service data source, deploying each object in the at least one deployment object, and obtaining target process data, wherein the target process data comprises: the method comprises the steps of obtaining a target process definition file by running target process data and task data and process instance data, reading form data corresponding to the task data and submitting the form data, so that a service system is divided into different modules, each module is independent, the modules can be used for executing different tasks, coupling and influence among systems are reduced, complexity of system architecture design is reduced, and stability among the systems is improved.
In accordance with the above, please refer to fig. 2, fig. 2 is a flowchart illustrating a workflow-based service method disclosed in an embodiment of the present application, and the workflow-based service method is applied to a server, and the workflow-based service method may include the following steps:
201. receiving a service data source, wherein the service data source comprises at least one service data.
202. And determining the file type of each service data in the at least one service data to obtain at least one file type, wherein each file type at least corresponds to one service data.
203. And determining at least one deployment object corresponding to the service data source according to the at least one file type.
204. Deploying each object in the at least one deployment object to obtain target process data, wherein the target process data comprises: task data, process instance data.
205. And operating the target process data to obtain a target process definition file.
206. And reading form data corresponding to the task data, and submitting the form data.
The workflow-based service method described in the above steps 201 to 206 may refer to the corresponding steps of the workflow-based service method described in fig. 1B.
It can be seen that the service method based on workflow described in the embodiment of the present application may receive a service data source, where the service data source includes at least one service data, determine a file type of each service data in the at least one service data, and obtain at least one file type, where each file type at least corresponds to one service data, determine at least one deployment object corresponding to the service data source according to the at least one file type, deploy each object in the at least one deployment object, and obtain target process data, where the target process data includes: the method comprises the steps of running task data and process instance data to obtain a target process definition file, reading form data corresponding to the task data and submitting the form data, so that a service system is divided into different modules, each module is independent of the other module and can be used for executing different tasks, coupling and influence among systems are reduced, complexity of system architecture design is reduced, and stability among the systems is improved.
In accordance with the above, please refer to fig. 3, fig. 3 is a flowchart illustrating a workflow-based service method disclosed in an embodiment of the present application, and the workflow-based service method is applied to a server, and the workflow-based service method may include the following steps:
301. receiving a service data source, wherein the service data source comprises at least one service data.
302. And determining the file type of each service data in the at least one service data to obtain at least one file type, wherein each file type at least corresponds to one service data.
303. And determining at least one deployment object corresponding to the service data source according to the at least one file type.
304. Deploying each object in the at least one deployment object to obtain target process data, wherein the target process data comprises: task data, process instance data.
305. And operating the target process data to obtain a target process definition file.
306. And reading form data corresponding to the task data, and submitting the form data.
307. And storing the process instance data of which the operation is finished or terminated as historical process instance data.
308. And determining at least one service type corresponding to the at least one service data, wherein each service data at least corresponds to one service type.
309. And packaging the form data and the target process data into at least one template data based on the at least one service type, wherein each template data corresponds to one service type.
The workflow-based service method described in the above steps 301 to 309 may refer to the corresponding steps of the workflow-based service method described in fig. 1B.
It can be seen that the service method based on workflow described in this embodiment of the present application may receive a service data source, where the service data source includes at least one service data, determine a file type of each service data in the at least one service data, and obtain at least one file type, where each file type at least corresponds to one service data, determine at least one deployment object corresponding to the service data source according to the at least one file type, and deploy each object in the at least one deployment object to obtain target process data, where the target process data includes: the method comprises the steps of task data, process instance data, target process data running to obtain a target process definition file, form data corresponding to the task data are read, the form data are submitted, the process instance data which are run completely or are run and terminated are stored as historical process instance data, at least one service type corresponding to at least one service data is determined, each service data at least corresponds to one service type, the form data and the target process data are packaged into at least one template data based on the at least one service type, each template data corresponds to one service type, therefore, after tasks in a system are executed, the form data and the target process data can be packaged into module data according to the service types, convenience is provided for subsequent services, and reduction of system pressure is facilitated.
In accordance with the above, please refer to fig. 4, fig. 4 is a schematic structural diagram of a server according to an embodiment of the present application, and as shown in fig. 4, the server includes a processor, a communication interface, a memory and one or more programs, where the processor, the communication interface and the memory are connected to each other, the memory is used for storing a computer program, the computer program includes program instructions, the processor is configured to call the program instructions, and the one or more program programs include instructions for performing the following steps:
receiving a service data source, wherein the service data source comprises at least one service data;
determining at least one deployment object corresponding to the service data source according to the service data source;
deploying each object in the at least one deployment object to obtain target process data, wherein the target process data comprises: task data, process instance data;
operating the target process data to obtain a target process definition file;
and reading form data corresponding to the task data, and submitting the form data.
It can be seen that, the server described in this embodiment of the present application may receive a service data source, where the service data source includes at least one service data, determine, according to the service data source, at least one deployment object corresponding to the service data source, deploy each object in the at least one deployment object, and obtain target process data, where the target process data includes: the method comprises the steps of obtaining a target process definition file by running target process data and task data and process instance data, reading form data corresponding to the task data and submitting the form data, so that a service system is divided into different modules, each module is independent, the modules can be used for executing different tasks, coupling and influence among systems are reduced, complexity of system architecture design is reduced, and stability among the systems is improved.
In a possible example, in terms of determining, according to the service data source, at least one deployment object corresponding to the service data source, the processor is specifically configured to:
determining a file type of each service data in the at least one service data to obtain at least one file type, wherein each file type at least corresponds to one service data;
and determining at least one deployment object corresponding to the service data source according to the at least one file type.
In a possible example, in terms of operating the target process data to obtain the target process definition file, the processor is specifically configured to:
matching the task data with a plurality of label models in a preset database to obtain a plurality of matching values, wherein each label model in the preset database is obtained by training a plurality of historical data;
selecting a mark model corresponding to the maximum matching value in the multiple matching values as a target mark model;
acquiring a target service scene corresponding to the target marking model;
and determining the process definition file corresponding to the target service scene as a target process definition file.
In a possible example, before the receiving the service data source, the processor is further specifically configured to:
sending N calling requests to N systems, wherein N is a positive integer greater than 1;
if M calling requests pass, detecting whether M systems corresponding to the M calling requests can be called or not, wherein M is a positive integer less than or equal to N;
if P systems can be called, P service data corresponding to the P systems are obtained through an interface, and the P service data form the service data source, wherein P is a positive integer smaller than or equal to M.
In a possible example, in terms of detecting whether M systems corresponding to M call requests can be called, the processor is further specifically configured to:
acquiring current operating states of the M systems to obtain M current operating states, wherein each system corresponds to one current operating state;
obtaining P systems corresponding to the current operating states which are idle states according to the M current operating states;
and determining that P systems exist in the M systems corresponding to the M calling requests and can be called.
In one possible example, the processor is further configured to:
determining at least one service type corresponding to the at least one service data, wherein each service data at least corresponds to one service type;
and packaging the form data and the target process data into at least one template data based on the at least one service type, wherein each template data corresponds to one service type.
The above description has introduced the solution of the embodiment of the present application mainly from the perspective of the method-side implementation process. It is understood that the server includes hardware structures and/or software modules for performing the respective functions in order to implement the above-described functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative elements and algorithm steps described in connection with the embodiments provided herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiment of the present application, the server may be divided into the functional units according to the above method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
In accordance with the above, please refer to fig. 5, fig. 5 is a schematic structural diagram of an apparatus for workflow-based services, which is applied to a server and includes: a receiving unit 501, a determining unit 502, a deploying unit 503, an executing unit 504 and a reading unit 505, wherein:
the receiving unit 501 is configured to receive a service data source, where the service data source includes at least one service data;
the determining unit 502 is configured to determine, according to the service data source, at least one deployment object corresponding to the service data source;
the deploying unit 503 is configured to deploy each object of the at least one deployment object to obtain target process data, where the target process data includes: task data, process instance data;
the running unit 504 is configured to run the target process data to obtain a target process definition file;
the reading unit 505 is configured to read form data corresponding to the task data, and submit the form data.
It can be seen that, the apparatus for workflow-based services described in this embodiment of the present application is applied to a server, and the apparatus may receive a service data source, where the service data source includes at least one service data, determine, according to the service data source, at least one deployment object corresponding to the service data source, deploy each object in the at least one deployment object, and obtain target process data, where the target process data includes: the method comprises the steps of obtaining a target process definition file by running target process data and task data and process instance data, reading form data corresponding to the task data and submitting the form data, so that a service system is divided into different modules, each module is independent, the modules can be used for executing different tasks, coupling and influence among systems are reduced, complexity of system architecture design is reduced, and stability among the systems is improved.
In a possible example, in terms of determining, according to the service data source, at least one deployment object corresponding to the service data source, the determining unit 502 is specifically configured to:
determining a file type of each service data in the at least one service data to obtain at least one file type, wherein each file type at least corresponds to one service data;
and determining at least one deployment object corresponding to the service data source according to the at least one file type.
In a possible example, in terms of operating the target process data to obtain the target process definition file, the operating unit 504 is specifically configured to:
matching the task data with a plurality of label models in a preset database to obtain a plurality of matching values, wherein each label model in the preset database is obtained by training a plurality of historical data;
selecting a mark model corresponding to the maximum matching value in the multiple matching values as a target mark model;
acquiring a target service scene corresponding to the target marking model;
and determining the process definition file corresponding to the target service scene as a target process definition file.
Embodiments of the present application also provide a computer-readable storage medium, wherein the computer storage medium stores a computer program for electronic data exchange, and the computer program enables a computer to execute part or all of the steps of any one of the workflow-based service methods as described in the above method embodiments.
Embodiments of the present application also provide a computer program product comprising a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any one of the workflow-based services methods as recited in the above method embodiments.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit may be implemented in the form of hardware, or may be implemented in the form of a software program module.
The integrated units, if implemented in the form of software program modules and sold or used as stand-alone products, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned memory comprises: various media capable of storing program codes, such as a usb disk, a read-only memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and the like.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash disk, ROM, RAM, magnetic or optical disk, and the like.
The foregoing detailed description of the embodiments of the present application has been presented to illustrate the principles and implementations of the present application, and the above description of the embodiments is only provided to help understand the method and the core concept of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A workflow-based service method, applied to a server, the method comprising:
receiving a service data source, wherein the service data source comprises at least one service data;
determining at least one deployment object corresponding to the service data source according to the service data source;
deploying each object in the at least one deployment object to obtain target process data, wherein the target process data comprises: task data, process instance data;
operating the target process data to obtain a target process definition file;
and reading form data corresponding to the task data, and submitting the form data.
2. The method of claim 1, further comprising:
and storing the process instance data of which the operation is finished or terminated as historical process instance data.
3. The method according to claim 1, wherein the determining, according to the service data source, at least one deployment object corresponding to the service data source includes:
determining a file type of each service data in the at least one service data to obtain at least one file type, wherein each file type at least corresponds to one service data;
and determining at least one deployment object corresponding to the service data source according to the at least one file type.
4. The method of claim 1, wherein the running the target process data to obtain a target process definition file comprises:
matching the task data with a plurality of label models in a preset database to obtain a plurality of matching values, wherein each label model in the preset database is obtained by training a plurality of historical data;
selecting a mark model corresponding to the maximum matching value in the multiple matching values as a target mark model;
acquiring a target service scene corresponding to the target marking model;
and determining the process definition file corresponding to the target service scene as a target process definition file.
5. The method of claim 1, wherein prior to said receiving a traffic data source, the method further comprises:
sending N calling requests to N systems, wherein N is a positive integer greater than 1;
if M calling requests pass, detecting whether M systems corresponding to the M calling requests can be called or not, wherein M is a positive integer less than or equal to N;
if P systems can be called, P service data corresponding to the P systems are obtained through an interface, and the P service data form the service data source, wherein P is a positive integer smaller than or equal to M.
6. The method according to claim 5, wherein the detecting whether M systems corresponding to M call requests can be called comprises:
acquiring current operating states of the M systems to obtain M current operating states, wherein each system corresponds to one current operating state;
obtaining P systems corresponding to the current operating states which are idle states according to the M current operating states;
and determining that P systems exist in the M systems corresponding to the M calling requests and can be called.
7. The method according to any one of claims 1-6, further comprising:
determining at least one service type corresponding to the at least one service data, wherein each service data at least corresponds to one service type;
and packaging the form data and the target process data into at least one template data based on the at least one service type, wherein each template data corresponds to one service type.
8. A workflow-based service apparatus, wherein the apparatus is applied to a server, and the apparatus comprises: a receiving unit, a determining unit, a deploying unit, an operating unit and a reading unit, wherein,
the receiving unit is configured to receive a service data source, where the service data source includes at least one service data;
the determining unit is configured to determine, according to the service data source, at least one deployment object corresponding to the service data source;
the deployment unit is configured to deploy each object in the at least one deployment object to obtain target process data, where the target process data includes: task data, process instance data;
the operation unit is used for operating the target process data to obtain a target process definition file;
and the reading unit is used for reading the form data corresponding to the task data and submitting the form data.
9. A server comprising a processor, an input device, an output device, and a memory, the processor, the input device, the output device, and the memory being interconnected, wherein the memory is configured to store a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the method of any of claims 1-7.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions that, when executed by a processor, cause the processor to carry out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010349213.0A CN111651140B (en) | 2020-04-28 | 2020-04-28 | Service method and device based on workflow |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010349213.0A CN111651140B (en) | 2020-04-28 | 2020-04-28 | Service method and device based on workflow |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111651140A true CN111651140A (en) | 2020-09-11 |
| CN111651140B CN111651140B (en) | 2022-05-03 |
Family
ID=72346580
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010349213.0A Active CN111651140B (en) | 2020-04-28 | 2020-04-28 | Service method and device based on workflow |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111651140B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112559813A (en) * | 2021-01-29 | 2021-03-26 | 广州技象科技有限公司 | Internet of things gateway data processing method and device based on instruction association pushing |
| CN112650598A (en) * | 2020-12-21 | 2021-04-13 | 思创数码科技股份有限公司 | Multi-application access method for workflow system |
| CN112866143A (en) * | 2021-02-10 | 2021-05-28 | 北京物芯科技有限责任公司 | Device and chip for realizing 802.1CB protocol |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101226612A (en) * | 2007-12-29 | 2008-07-23 | 中国建设银行股份有限公司 | Data processing management system facing to process flow |
| US20080307392A1 (en) * | 2002-01-15 | 2008-12-11 | Racca Felix G | System architecture for business process development and execution |
| CN102291464A (en) * | 2011-08-29 | 2011-12-21 | 上海普元信息技术股份有限公司 | System and method for dynamically generating Web Service by business flow in BPM (Business Process Management) |
| CN104572062A (en) * | 2014-04-15 | 2015-04-29 | 武汉中地数码科技有限公司 | Construction method for geospatial information workflow service function flow templates |
| CN105700888A (en) * | 2016-01-14 | 2016-06-22 | 国网山东省电力公司物资公司 | Visualization rapid developing platform based on jbpm workflow engine |
| US20160335142A1 (en) * | 2014-12-27 | 2016-11-17 | Huawei Technologies Co., Ltd. | Notification Service Processing Method for Business Process Management and Business Process Management Engine |
| CN108920277A (en) * | 2018-06-27 | 2018-11-30 | 阿里巴巴集团控股有限公司 | Business executes system, method and device, business shielding system |
| CN109542556A (en) * | 2018-10-30 | 2019-03-29 | 珠海伟诚科技股份有限公司 | A kind of process based on Activiti and list exchange method and system |
| CN113741918A (en) * | 2021-09-10 | 2021-12-03 | 安超云软件有限公司 | Method for deploying applications on cloud and applications |
-
2020
- 2020-04-28 CN CN202010349213.0A patent/CN111651140B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080307392A1 (en) * | 2002-01-15 | 2008-12-11 | Racca Felix G | System architecture for business process development and execution |
| CN101226612A (en) * | 2007-12-29 | 2008-07-23 | 中国建设银行股份有限公司 | Data processing management system facing to process flow |
| CN102291464A (en) * | 2011-08-29 | 2011-12-21 | 上海普元信息技术股份有限公司 | System and method for dynamically generating Web Service by business flow in BPM (Business Process Management) |
| CN104572062A (en) * | 2014-04-15 | 2015-04-29 | 武汉中地数码科技有限公司 | Construction method for geospatial information workflow service function flow templates |
| US20160335142A1 (en) * | 2014-12-27 | 2016-11-17 | Huawei Technologies Co., Ltd. | Notification Service Processing Method for Business Process Management and Business Process Management Engine |
| CN105700888A (en) * | 2016-01-14 | 2016-06-22 | 国网山东省电力公司物资公司 | Visualization rapid developing platform based on jbpm workflow engine |
| CN108920277A (en) * | 2018-06-27 | 2018-11-30 | 阿里巴巴集团控股有限公司 | Business executes system, method and device, business shielding system |
| CN109542556A (en) * | 2018-10-30 | 2019-03-29 | 珠海伟诚科技股份有限公司 | A kind of process based on Activiti and list exchange method and system |
| CN113741918A (en) * | 2021-09-10 | 2021-12-03 | 安超云软件有限公司 | Method for deploying applications on cloud and applications |
Non-Patent Citations (2)
| Title |
|---|
| 左方: "基于工作流的Web服务系统设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》 * |
| 王一飞， 等: "基于工作流的Web服务组合系统的设计与实现", 《信息化纵横》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112650598A (en) * | 2020-12-21 | 2021-04-13 | 思创数码科技股份有限公司 | Multi-application access method for workflow system |
| CN112650598B (en) * | 2020-12-21 | 2023-08-18 | 思创数码科技股份有限公司 | Multi-application access method for workflow system |
| CN112559813A (en) * | 2021-01-29 | 2021-03-26 | 广州技象科技有限公司 | Internet of things gateway data processing method and device based on instruction association pushing |
| CN112866143A (en) * | 2021-02-10 | 2021-05-28 | 北京物芯科技有限责任公司 | Device and chip for realizing 802.1CB protocol |
| CN112866143B (en) * | 2021-02-10 | 2023-10-10 | 北京物芯科技有限责任公司 | Device and chip for realizing 802.1CB protocol |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111651140B (en) | 2022-05-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111651140B (en) | Service method and device based on workflow | |
| CN113918232B (en) | Algorithm service calling method, device, server and storage medium | |
| CN108804399B (en) | Form verification method and device | |
| CN111858727A (en) | Multi-data-source data export system and method based on template configuration | |
| CN112037061A (en) | Processing method and device for transactions in block chain, electronic equipment and storage medium | |
| CN109766123B (en) | Application program packaging method and device | |
| CN113360300B (en) | Interface call link generation method, device, equipment and readable storage medium | |
| CN112422450A (en) | Computer equipment, and flow control method and device for service request | |
| CN111752820A (en) | Pressure testing method of gPC interface, computer equipment and storage medium | |
| CN113923144A (en) | Service test system, method, electronic device and storage medium | |
| CN116628141B (en) | Information processing method, device, equipment and storage medium | |
| CN112559124A (en) | Model management system and target operation instruction processing method and device | |
| CN108427599A (en) | Method, apparatus and storage medium is uniformly processed in asynchronous task | |
| CN112015496A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN112579960A (en) | Webpage evidence obtaining method, webpage evidence obtaining device and server | |
| CN108076067B (en) | Method and system for authorized crawler configuration simulation login | |
| CN115934305A (en) | Cloud platform management method, server and computer-readable storage medium | |
| CN113297358A (en) | Data processing method, device, server and computer readable storage medium | |
| CN112114931A (en) | Deep learning program configuration method and device, electronic equipment and storage medium | |
| CN109857450B (en) | Verification service arrangement method and device | |
| CN110795068B (en) | Method and system for automatically generating executable scheme from user requirement in industry cloud environment | |
| CN115242625B (en) | Service deployment method, device, computer equipment and readable storage medium | |
| CN111400058B (en) | Method, device, computer equipment and storage medium for calling message | |
| CN114331350A (en) | Service arrangement processing method and device | |
| CN117591190A (en) | Application data loading optimization method, device, equipment and storage medium thereof |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220520 Address after: 518000 China Aviation Center 2901, No. 1018, Huafu Road, Huahang community, Huaqiang North Street, Futian District, Shenzhen, Guangdong Province Patentee after: Shenzhen Ping An medical and Health Technology Service Co.,Ltd. Address before: Room 12G, Area H, 666 Beijing East Road, Huangpu District, Shanghai 200001 Patentee before: PING AN MEDICAL AND HEALTHCARE MANAGEMENT Co.,Ltd. |
|
| TR01 | Transfer of patent right |