CN116993287A - Method and device for creating flow business file, computer equipment and storage medium - Google Patents

Method and device for creating flow business file, computer equipment and storage medium Download PDF

Info

Publication number
CN116993287A
CN116993287A CN202310953241.7A CN202310953241A CN116993287A CN 116993287 A CN116993287 A CN 116993287A CN 202310953241 A CN202310953241 A CN 202310953241A CN 116993287 A CN116993287 A CN 116993287A
Authority
CN
China
Prior art keywords
flow
data
service
state
node
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.)
Pending
Application number
CN202310953241.7A
Other languages
Chinese (zh)
Inventor
沈洪波
赵春生
范晓群
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou Lifesmart Technology Co ltd
Original Assignee
Hangzhou Lifesmart Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hangzhou Lifesmart Technology Co ltd filed Critical Hangzhou Lifesmart Technology Co ltd
Priority to CN202310953241.7A priority Critical patent/CN116993287A/en
Publication of CN116993287A publication Critical patent/CN116993287A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Quality & Reliability (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The invention relates to the technical field of flow business, and discloses a method and a device for creating a flow business file, computer equipment and a storage medium. Based on the flow service request instruction, a state machine model comprising a plurality of flow state nodes is created, and flow prefabrication data, flow instance data, flow service data and flow log data are written in each flow state node of the state machine model, so that the creation efficiency of the flow file can be improved, the labor cost is reduced, and the creation accuracy of the flow service file is also ensured.

Description

Method and device for creating flow business file, computer equipment and storage medium
Technical Field
The present invention relates to the field of flow service technologies, and in particular, to a method and apparatus for creating a flow service file, a computer device, and a storage medium.
Background
The process service file refers to a service file containing a plurality of process links, for example, job entering, contract changing, job leaving and the like, and many similar process links exist, for example: file generation, event processing, physical submission, online stamping and the like. In the related art, the creation of the flow business file by manual verification is not only inefficient but also prone to error.
Disclosure of Invention
In view of the above, the present invention provides a method, apparatus, computer device and storage medium for creating a flow service file, so as to solve the problem that the creation of the flow service file by manual verification is not only inefficient but also prone to error.
In a first aspect, the present invention provides a method for creating a flow service file, where the method includes:
acquiring a flow service request instruction submitted by a user;
based on the flow service request instruction, creating a state machine model comprising a plurality of flow state nodes, wherein each flow state node is generated through a flow state, a flow event and a flow action;
writing flow prefabrication data, flow instance data, flow business data and flow log data in each flow state node based on a plurality of flow state nodes; the method comprises the steps that flow prefabrication data are generated based on flow names, flow types, flow information and file paths, flow instance data are generated based on flow names, flow types, flow states, current nodes, participants, node data and service identifiers, flow service data are generated based on service requester information, service request reasons, service request time and service related data, and flow log data are flow operation information of each flow state node;
and generating a flow service file based on each written flow state node.
By executing the embodiment, the state machine model comprising a plurality of flow state nodes is created based on the flow service request instruction, and the flow prefabrication data, the flow instance data, the flow service data and the flow log data are written in each flow state node of the state machine model, so that the creation efficiency of the flow file can be improved, the labor cost is reduced, and the creation accuracy of the flow service file is also ensured.
In an alternative embodiment, the flow state is determined based on the identification information; the process event comprises: basic events and custom events, the basic events include the entry, start and exit actions of each flow state node.
By executing the embodiment, the basic event and the custom event are defined, which is beneficial to generating the flow service file.
In an alternative embodiment, the base events are automatically triggered at each flow state node stream, and the custom events are composed based on user naming.
By executing the embodiment, the flow service file is generated by setting specific basic events and custom events.
In an alternative embodiment, the process of creating a plurality of flow state nodes includes loading and/or launching and/or triggering and/or circulation of each flow state node.
By implementing the above embodiments, the loading and/or starting and/or triggering and/or circulation of each flow state node is facilitated to create a plurality of flow state nodes.
In an alternative embodiment, the flow information includes: the flow processor and the flow initialization data are implemented by the flow processor based on dynamic filling or dynamic modification.
By executing the above embodiment, the flow information can be flexibly modified.
In an alternative embodiment, after each flow state node is run, the flow business data and the flow instance data are stored continuously based on a preset time.
By executing the above embodiment, it is advantageous to make full use of the flow prefabrication data and the flow instance data.
In an alternative embodiment, in the process of creating the state machine model, loading a flow state node, starting a flow state node, triggering a flow event, flowing a flow state node, and jumping the flow state node are included.
By implementing the above embodiments, it is advantageous to fully create a state machine model.
According to a second aspect, an embodiment of the present invention further provides a device for creating a flow service file, where the device includes:
the service request acquisition module is used for acquiring a flow service request instruction submitted by a user;
the system comprises a state machine creation module, a state machine generation module and a state machine generation module, wherein the state machine creation module is used for creating a state machine model comprising a plurality of flow state nodes based on a flow service request instruction, and each flow state node is generated through a flow state, a flow event and a flow action;
the flow data writing module is used for writing flow prefabrication data, flow instance data, flow business data and flow log data into each flow state node based on a plurality of flow state nodes; the flow prefabrication data is generated based on a flow name, a flow type, flow information and a file path, the flow instance data is generated based on the flow name, the flow type, the flow state, a current node, participants, node data and a service identifier, the flow service data is generated based on service requester information, service request reasons, service request time and service association data, and the flow log data is flow operation information of each flow state node;
and the flow file generating module is used for generating a flow service file based on each written flow state node.
In a third aspect, the present invention provides a computer device comprising: the system comprises a memory and a processor, wherein the memory and the processor are in communication connection, the memory stores computer instructions, and the processor executes the computer instructions, so that the method for creating the flow service file according to the first aspect or any implementation mode corresponding to the first aspect is executed.
In a fourth aspect, the present invention provides a computer readable storage medium, where computer instructions are stored, where the computer instructions are configured to cause a computer to execute the method for creating a flow service file according to the first aspect or any embodiment corresponding to the first aspect.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow diagram of a method of creating a flow business file according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of another process state node according to an embodiment of the invention;
FIG. 3 is a state machine operation schematic according to an embodiment of the present invention;
fig. 4 is a block diagram of a flow service file creation apparatus according to an embodiment of the present invention.
Fig. 5 is a schematic diagram of a hardware structure of a computer device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
According to an embodiment of the present invention, there is provided an embodiment of a method for creating a flow service file, it should be noted that the steps shown in the flowchart of the drawings may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in an order different from that herein.
In this embodiment, a method for creating a flow service file is provided, which may be used in a mobile terminal, such as a mobile phone, a tablet computer, etc., fig. 1 is a flowchart of a method for creating a flow service file according to an embodiment of the present invention, as shown in fig. 1, where the flow includes the following steps:
step S101, a flow service request instruction submitted by a user is obtained.
Specifically, for example: the flow service request instruction that the user can submit may be a leave request instruction or a request instruction to upload a certificate or submit an order or bill reimbursement.
Step S102, based on the flow service request instruction, a state machine model comprising a plurality of flow state nodes is created, and each flow state node is generated through a flow state, a flow event and a flow action.
Specifically, the object of the state machine model is based on finite state machine concepts, and is formed by combining a customized state node and a series of function functions, and a plurality of flow state nodes are one of elements for constructing the state machine model.
Illustratively, each flow State node is generated by a flow State (State), a flow Event (Event), and a flow Action (Action).
In an alternative embodiment, the flow state is determined based on the identification information; the process event comprises: basic events and custom events, the basic events include the entry, start and exit actions of each flow state node.
In an alternative embodiment, the base events are automatically triggered at each flow state node stream, and the custom events are composed based on user naming.
In an alternative embodiment, the process of creating a plurality of flow state nodes includes loading and/or launching and/or triggering and/or circulation of each flow state node.
Specifically, the unique names identify different flow states (states); the process Event (Event) comprises a basic Event and a custom Event, wherein an ENTRY Node (ENTRY), a START node (START) and an EXIT node (EXIT) are taken as basic events, the basic events are automatically triggered when a state node flows, the custom Event is named and written by a user, and the custom Event is triggered according to input conditions and a state machine function; each event is bound with a corresponding Action (Action), which is a logic unit for implementing different business scenarios.
In an alternative embodiment, in the process of creating the state machine model, loading a flow state node, starting a flow state node, triggering a flow event, flowing a flow state node, and jumping the flow state node are included.
As shown in fig. 2, a schematic diagram of a flow state node is shown.
Specifically, during the process of creating the state machine model, the state machine core code takes the flow state node as an input condition, and only keeps the function functions related to the state machine, such as creating the state machine, loading the flow state node, starting the state machine, triggering the flow event, circulating the flow node, jumping the flow state node, and the like. The function functions related to the state machine refer to functions for creating and controlling the state machine objects, the Action functions (actions) refer to Action functions bound by the flow events in the flow state nodes, the Action functions are customized by users to realize different service requirements, a plurality of flow state nodes form a flow file, the state machine objects are created by the flow service file to execute defined logic in the flow service file, for example, the flow service file can define a leave-out flow, cancel the flow, and the like, and the invention is used for realizing different service scenes. The function is the basis of the execution logic of the state machine, the current state machine adopts the design of separating the execution logic from the service logic, the service logic is defined in the flow state node, the received input content is injected into the state machine, the expandability of the state machine is improved, and the state machine objects constructed by loading different state nodes can be adapted to different service scenes. The business logic refers to business requirements that need to be completed by a state machine, such as a leave-in process and an order process, the business logic is defined by a process business file and then is injected into a state machine object, so that a general state machine can adapt to different business scenes, and only the process file needs to be written according to rules and business requirements.
As shown in fig. 3, in loading different state node building state machine objects to adapt to different service scenarios, the method includes: starting a state machine: the state machine instantiation runs in the memory, the current state is A, and the state machine instantiation is sequentially triggered when started so that the node and the starting event execute corresponding triggering actions.
The state machine operates: the current state is A, the receiving event is successful, the corresponding action (the logic of the jump B is set in the unit) is executed, the state is migrated to the rollback event of the A node is triggered before the state is migrated to the B, and then the entering node and the starting event of the B are triggered in sequence.
The state machine operates: when the state is B, receiving the event rollback, executing the corresponding trigger action (the logic of the unit which is set to return to A), triggering the rollback event of the node B before the state is migrated to A, and then triggering the entering node and the starting event of the A in sequence.
Step S103, writing flow prefabrication data, flow instance data, flow business data and flow log data into each flow state node based on a plurality of flow state nodes; the flow prefabrication data is generated based on a flow name, a flow type, flow information and a file path, the flow instance data is generated based on the flow name, the flow type, the flow state, a current node, participants, node data and a service identifier, the flow service data is generated based on service requester information, service request reasons, service request time and service association data, and the flow log data is flow operation information of each flow state node.
Step S104, generating a flow service file based on each written flow state node.
Specifically, based on the state machine model, the flow business file may be written in a specified format. The flow service file mainly comprises a state node set and flow file instance data. Defining a flow business flow (such as leave-out flow and cancel-out flow) as a plurality of state nodes, wherein the state nodes at least comprise a starting node and an ending node, and three basic events are defined under the nodes: the method comprises the steps of entering a node, starting the node, returning the node and a plurality of custom events beginning with E_each binding a corresponding trigger action, automatically triggering or actively triggering the event in state node switching and then executing the bound trigger actions (for example, binding the trigger actions of a person who handles the node in the starting event), writing flow service demand processing logic in a flow service file, completing event triggering and state circulation in cooperation with a state machine function, and performing parameter verification, authority judgment, service processing, remote calling, message pushing, log recording and other operations on conventional service logic. In a specific operation, initialization may be accomplished by loading into a state machine and returning a flow instantiation object.
The most core in the flow service file is the event and action, and the realization of the flow service is written in the flow service file. For example, the requirement of the leave-out flow is met, only the approval of a manager is required within 3 days of leave-out, and the approval of the manager is required after the approval of the main manager passes over 3 days, so that the approval under the nodes of the manager passes the action corresponding to event binding, and if the leave-out number is less than or equal to 3 days, the flow approval is finished, and the leave-out is successful; if the leave-asking days are more than 3 days, skipping to the manager approval node for processing; different nodes, events and actions are defined according to requirements and combined into a flow file.
In an alternative embodiment, the flow information includes: the flow processor and the flow initialization data are implemented by the flow processor based on dynamic filling or dynamic modification.
Illustratively, the flow preset data defines the following information: flow name, flow type, flow business data, flow file path. The flow business data comprises a flow processor and flow initialization data, wherein the flow processor can specify a user ID, a user role and a macro definition code, the macro definition code is analyzed into the specified user ID or role in the process of creating the flow, dynamic filling of the node processor is realized through flow preset data, the code is not required to be changed when the node processor is modified, and convenient operation is provided for changing and modifying the personnel. The flow initialization data is used to initialize certain values when the flow is created. And the flow Cheng Yuzhi data persistent storage is independently maintained and used with the flow control module.
In an alternative embodiment, after each process state node is finished running, the process service data and the process instance data are stored continuously based on a preset time.
Illustratively, the flow instance data is dependent on flow prefabrication data, and the flow business file and initialization information are injected into the state machine. Stored in the flow instance data are information related to flow operation, such as flow name, type, status, current node, participant, node data, service ID, etc. And recovering the flow state machine to the memory to run by means of the flow instance data, and storing the flow instance in a lasting manner after the running is finished.
The process business data is, for example, information to be saved in the actual process requirement, such as information related to business, such as dummy please, dummy please days, dummy please reasons, dummy please time, etc. In a mode of separating a flow instance from flow data, the flow instance and the flow service are bound by means of a service ID, the flow expansibility is improved, meanwhile, a basis is provided for processing statistics of the service data, and in a mode of integrating the service data with the flow data and storing the service data in the flow instance, the mode is suitable for some simple service flows, a separate service model and an interface are not needed, and a new service flow can be quickly online only by editing a flow file and prefabricated data.
Illustratively, the flow log data records data of the operation of a flow, with a certain flow migrating from one state to another state at a certain time.
Therefore, in the method for creating the flow service file in the embodiment, based on the flow service request instruction, a state machine model including a plurality of flow state nodes is created, and the flow prefabrication data, the flow instance data, the flow service data and the flow log data are written in each flow state node of the state machine model, so that the efficiency of creating the flow file can be improved, the labor cost is reduced, and the accuracy of creating the flow service file is also ensured.
The embodiment also provides a device for creating a flow service file, which is used for implementing the foregoing embodiments and preferred embodiments, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
The present embodiment provides a device for creating a flow service file, as shown in fig. 4, including:
the service request obtaining module 41 is configured to obtain a flow service request instruction submitted by a user.
The state machine creation module 42 is configured to create a state machine model including a plurality of flow state nodes based on the flow service request instruction, where each flow state node is generated by a flow state, a flow event, and a flow action.
A flow data writing module 43, configured to write flow prefabrication data, flow instance data, flow business data, and flow log data in each flow state node based on a plurality of flow state nodes; the flow prefabrication data is generated based on a flow name, a flow type, flow information and a file path, the flow instance data is generated based on the flow name, the flow type, the flow state, a current node, participants, node data and a service identifier, the flow service data is generated based on service requester information, service request reasons, service request time and service association data, and the flow log data is flow operation information of each flow state node.
The flow file generating module 44 is configured to generate a flow service file based on each written flow state node.
In an alternative embodiment, the flow state is determined based on the identification information; the process event comprises: basic events and custom events, the basic events include the entry, start and exit actions of each flow state node.
In an alternative embodiment, the base events are automatically triggered at each flow state node stream, and the custom events are composed based on user naming.
In an alternative embodiment, the process of creating a plurality of flow state nodes includes loading and/or launching and/or triggering and/or circulation of each flow state node.
In an alternative embodiment, the flow information includes: the flow processor and the flow initialization data are implemented by the flow processor based on dynamic filling or dynamic modification.
In an alternative embodiment, the process pre-run data and the process instance data are stored persistently after each process state node is run.
In an alternative embodiment, in the process of creating the state machine model, loading a flow state node, starting a flow state node, triggering a flow event, flowing a flow state node, and jumping the flow state node are included.
Further functional descriptions of the above respective modules and units are the same as those of the above corresponding embodiments, and are not repeated here.
The flow service file creation means in this embodiment is presented in the form of functional units, where the units refer to ASIC (Application Specific Integrated Circuit ) circuits, processors and memories executing one or more software or fixed programs, and/or other devices that can provide the above described functionality.
The embodiment of the invention also provides a computer device which is provided with the creating device of the flow service file shown in the figure 4.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a computer device according to an alternative embodiment of the present invention, as shown in fig. 5, the computer device includes: one or more processors 10, memory 20, and interfaces for connecting the various components, including high-speed interfaces and low-speed interfaces. The various components are communicatively coupled to each other using different buses and may be mounted on a common motherboard or in other manners as desired. The processor may process instructions executing within the computer device, including instructions stored in or on memory to display graphical information of the GUI on an external input/output device, such as a display device coupled to the interface. In some alternative embodiments, multiple processors and/or multiple buses may be used, if desired, along with multiple memories and multiple memories. Also, multiple computer devices may be connected, each providing a portion of the necessary operations (e.g., as a server array, a set of blade servers, or a multiprocessor system). One processor 10 is illustrated in fig. 5.
The processor 10 may be a central processor, a network processor, or a combination thereof. The processor 10 may further include a hardware chip, among others. The hardware chip may be an application specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general-purpose array logic, or any combination thereof.
Wherein the memory 20 stores instructions executable by the at least one processor 10 to cause the at least one processor 10 to perform the methods shown in implementing the above embodiments.
The memory 20 may include a storage program area that may store an operating system, at least one application program required for functions, and a storage data area; the storage data area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include high-speed random access memory, and may also include non-transitory memory, such as at least one magnetic disk storage device, flash memory device, or other non-transitory solid-state storage device. In some alternative embodiments, memory 20 may optionally include memory located remotely from processor 10, which may be connected to the computer device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Memory 20 may include volatile memory, such as random access memory; the memory may also include non-volatile memory, such as flash memory, hard disk, or solid state disk; the memory 20 may also comprise a combination of the above types of memories.
The computer device also includes a communication interface 30 for the computer device to communicate with other devices or communication networks.
The embodiments of the present invention also provide a computer readable storage medium, and the method according to the embodiments of the present invention described above may be implemented in hardware, firmware, or as a computer code which may be recorded on a storage medium, or as original stored in a remote storage medium or a non-transitory machine readable storage medium downloaded through a network and to be stored in a local storage medium, so that the method described herein may be stored on such software process on a storage medium using a general purpose computer, a special purpose processor, or programmable or special purpose hardware. The storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, a solid state disk or the like; further, the storage medium may also comprise a combination of memories of the kind described above. It will be appreciated that a computer, processor, microprocessor controller or programmable hardware includes a storage element that can store or receive software or computer code that, when accessed and executed by the computer, processor or hardware, implements the methods illustrated by the above embodiments.
Although embodiments of the present invention have been described in connection with the accompanying drawings, various modifications and variations may be made by those skilled in the art without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope of the invention as defined by the appended claims.

Claims (10)

1. A method for creating a flow service file, the method comprising:
acquiring a flow service request instruction submitted by a user;
based on the flow service request instruction, creating a state machine model comprising a plurality of flow state nodes, wherein each flow state node is generated through a flow state, a flow event and a flow action;
writing flow prefabrication data, flow instance data, flow business data and flow log data in each flow state node based on the plurality of flow state nodes; the flow prefabrication data is generated based on a flow name, a flow type, flow information and a file path, the flow instance data is generated based on the flow name, the flow type, a flow state, a current node, participants, node data and service identification, the flow service data is generated based on service requester information, service request reasons, service request time and service association data, and the flow log data is flow operation information of each flow state node;
and generating a flow service file based on each written flow state node.
2. The method of claim 1, wherein the flow state is determined based on identification information; the process event includes: basic events and custom events, wherein the basic events comprise entering, starting and exiting actions of each flow state node.
3. The method of claim 2, wherein the base event is automatically triggered upon each flow state node flow, and wherein the custom event is composed based on user naming.
4. Method according to claim 1, characterized in that in the creation of the plurality of flow state nodes, loading and/or starting and/or triggering and/or circulation of each flow state node is included.
5. The method of claim 1, wherein the flow information comprises: a flow handler and flow initialization data, the flow handler implemented based on dynamic population or dynamic modification.
6. The method of any one of claims 1-5, wherein the process business data and the process instance data are stored continuously based on a preset time after the end of each process state node.
7. The method of claim 1, wherein creating the state machine model comprises loading a flow state node, starting a flow state node, triggering a flow event, flowing a flow state node, and jumping a flow state node.
8. A device for creating a flow service file, the device comprising:
the service request acquisition module is used for acquiring a flow service request instruction submitted by a user;
the state machine creation module is used for creating a state machine model comprising a plurality of flow state nodes based on the flow service request instruction, and each flow state node is generated through a flow state, a flow event and a flow action;
the flow data writing module is used for writing flow prefabrication data, flow instance data, flow business data and flow log data into each flow state node based on the plurality of flow state nodes; the flow prefabrication data is generated based on a flow name, a flow type, flow information and a file path, the flow instance data is generated based on the flow name, the flow type, a flow state, a current node, participants, node data and service identification, the flow service data is generated based on service requester information, service request reasons, service request time and service association data, and the flow log data is flow operation information of each flow state node;
and the flow file generating module is used for generating a flow service file based on each written flow state node.
9. A computer device, comprising:
a memory and a processor, the memory and the processor being communicatively connected to each other, the memory having stored therein computer instructions, the processor executing the computer instructions to perform the method of creating a flow service file according to any one of claims 1 to 7.
10. A computer-readable storage medium, wherein computer instructions for causing a computer to execute the creation method of the flow service file according to any one of claims 1 to 7 are stored on the computer-readable storage medium.
CN202310953241.7A 2023-07-31 2023-07-31 Method and device for creating flow business file, computer equipment and storage medium Pending CN116993287A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310953241.7A CN116993287A (en) 2023-07-31 2023-07-31 Method and device for creating flow business file, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310953241.7A CN116993287A (en) 2023-07-31 2023-07-31 Method and device for creating flow business file, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN116993287A true CN116993287A (en) 2023-11-03

Family

ID=88520928

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310953241.7A Pending CN116993287A (en) 2023-07-31 2023-07-31 Method and device for creating flow business file, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN116993287A (en)

Similar Documents

Publication Publication Date Title
CN111625452A (en) Flow playback method and system
CN106940428B (en) Chip verification method, device and system
CN105045602B (en) Method and device for constructing Hadoop application development framework and electronic device
CN109731334B (en) State switching method and device, storage medium and electronic device
CN112579455B (en) Automatic interface testing method and device, electronic equipment and storage medium
CN111598428A (en) Method and device for managing process nodes, storage medium and server
CN112306471A (en) Task scheduling method and device
CN111049913B (en) Data file transmission method and device, storage medium and electronic equipment
CN111782201A (en) Method and device for realizing linkage of service codes and layout topological graph
CN113835822A (en) Cross-cloud-platform virtual machine migration method and device, storage medium and electronic device
CN107566480B (en) User activity information acquisition method and device for mobile terminal application and storage medium
CN114443058A (en) Method for creating private mirror image in public cloud and related equipment
CN115480785A (en) Container-based service deployment method and device and server
CN113467782B (en) Method, device and equipment for determining business process
CN111144837A (en) Flow arrangement method and device, storage medium and electronic equipment
CN109450724A (en) A kind of test method and relevant apparatus of NFS internal memory optimization function
CN109151021B (en) Distributed storage system file lock characteristic testing method and device
CN112631920A (en) Test method, test device, electronic equipment and readable storage medium
CN112699046A (en) Application program testing method and device, electronic equipment and storage medium
CN116993287A (en) Method and device for creating flow business file, computer equipment and storage medium
CN113157452B (en) Application service request method, device, computer equipment and storage medium
CN117009626A (en) Service processing method, device, equipment and storage medium of game scene
CN110221952B (en) Service data processing method and device and service data processing system
JP5913155B2 (en) Packet replay device and packet replay method
CN114675926A (en) Virtual machine attribute changing method and device, storage medium and electronic device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination