CN111176641B - Flow node execution method, device, medium and electronic equipment - Google Patents
Flow node execution method, device, medium and electronic equipment Download PDFInfo
- Publication number
- CN111176641B CN111176641B CN201911222294.1A CN201911222294A CN111176641B CN 111176641 B CN111176641 B CN 111176641B CN 201911222294 A CN201911222294 A CN 201911222294A CN 111176641 B CN111176641 B CN 111176641B
- Authority
- CN
- China
- Prior art keywords
- node
- flow
- identification
- activity
- page
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- 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
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
Abstract
The invention provides a flow node execution method, which comprises the following steps: acquiring an application process, wherein the application process comprises a plurality of process nodes and a plurality of node activities; determining an execution sequence among the plurality of process nodes according to the plurality of node activities; when the plurality of process nodes are executed, the page content of the process nodes is determined according to the content of the process nodes, and the page content of the process nodes is sent, so that at least the problem of low page reusability is solved, and a developer is not required to redevelop a page due to different application flows, for example, the address of the page in the next step in the page content is reset, thereby reducing the workload of the developer and improving the speed of online insurance products. The invention also provides a flow node executing device, a medium and electronic equipment.
Description
Technical Field
The present invention relates to the technical field of data processing, and in particular, to a method, an apparatus, a medium, and an electronic device for executing a flow node.
Background
Currently, a wide variety of insurance products are becoming more popular, for example, insurance products may be car insurance, health insurance, accident insurance, and the like. The user may make an application by accessing an application associated with an insurance product, for example, the user purchases an insurance product a, where the application flow of the insurance product a is: commodity detail browse- > applicant fill- > insured person fill- > beneficiary fill- > insuring confirmation. Before the user makes an application, a developer needs to develop the content of each page in the application flow of the insurance product A, and when the developer makes an application, the next page address can be placed in each page, and when the user makes the application in the application, the execution sequence of the application flow is determined according to the next page address set in each page.
When the inventor realizes the inventive concept of the present invention, the inventor finds that at least the following technical problems exist in the related art: the page address of the next step of the insurance flow in the related art is set in the page of the last step, and the setting mode leads to that page contents in different insurance flows need to be redeveloped, but the flows of the insurance flows are reorganized, so that the reusability of the pages is extremely low, the workload of developers is increased, and even the speed of online insurance products is delayed.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the invention and thus may include information that does not form the prior art that is already known to those of ordinary skill in the art.
Disclosure of Invention
The embodiment of the invention aims to provide a flow node executing method, a device, a medium and electronic equipment, and further at least solves the problems of extremely low reusability of pages, large workload of developers and low speed of online insurance products to a certain extent.
Other features and advantages of the invention will be apparent from the following detailed description, or may be learned by the practice of the invention.
According to a first aspect of an embodiment of the present invention, there is provided a flow node execution method, including: acquiring an application process, wherein the application process comprises a plurality of process nodes and a plurality of node activities; determining an execution sequence among the plurality of process nodes according to the plurality of node activities; and when the plurality of flow nodes are executed, determining the page content of the flow nodes according to the content of the flow nodes, and sending the page content of the flow nodes.
In some embodiments of the invention, the content of each flow node includes any one or more of: the process node identification, the process node type, the process node template and the application process identification.
In some embodiments of the invention, the content of each node activity includes any one or more of: the identification of node activity, activity coding, the identification of current flow node, the identification of next flow node.
In some embodiments of the invention, determining an execution order between the plurality of flow nodes based on the plurality of node activities comprises: determining a next flow node to be executed according to the identification of the current flow node, the identification of the next flow node and the activity code of the current node activity, wherein the activity code of the current node activity is a first jump identification; or determining the next flow node to be executed according to the identification of the current flow node, the identification of the next flow node and the activity code of the current node activity, wherein the activity code of the current node activity is a second jump identification, and the second jump identification is different from the first jump identification.
In some embodiments of the present invention, the flow node type is a page flow node, a flow node template of the page flow node is a storage address of page content, determining the page content of the flow node according to the content of the flow node, and sending the page content of the flow node includes: and acquiring the page content of the flow node according to the storage address of the page content, and sending the page content of the flow node.
In some embodiments of the present invention, the flow node type is a functional flow node, a flow node template of the functional flow node is an interface identifier of the functional flow node, determining page content of the flow node according to content of the flow node, and sending the page content of the flow node includes: calling an interface of the functional flow node according to the interface identifier of the functional flow node; processing data related to the functional flow node by using an interface of the functional flow node; and generating the page content of the functional flow node based on the processed data, and sending the page content of the functional flow node.
In some embodiments of the invention, obtaining the application flow includes: and acquiring the corresponding insurance application flow from the flow library according to the identification of the insurance product.
In some embodiments of the invention, the method further comprises: if the insurance process corresponding to the insurance product identifier is not queried from the process library based on the insurance product identifier, querying a process node related to the insurance product identifier from a process node database based on the insurance product identifier, querying a node activity related to the insurance product identifier from a node activity database based on the insurance product identifier, and generating the insurance process of the insurance product based on the process node and the node activity related to the insurance product identifier.
According to a second aspect of an embodiment of the present invention, there is provided a flow node execution apparatus, including: the system comprises an acquisition module, a storage module and a storage module, wherein the acquisition module is used for acquiring an application flow, and the application flow comprises a plurality of flow nodes and a plurality of node activities; a first determining module, configured to determine an execution order among the plurality of flow nodes according to the activities of the plurality of nodes; and the second determining module is used for determining the page content of the flow node according to the content of the flow node and sending the page content of the flow node when the plurality of flow nodes are executed.
In some embodiments of the invention, the content of each flow node includes any one or more of: the process node identification, the process node type, the process node template and the application process identification.
In some embodiments of the invention, the content of each node activity includes any one or more of: the identification of node activity, activity coding, the identification of current flow node, the identification of next flow node.
In some embodiments of the present invention, the first determining module is configured to: determining the execution sequence among the plurality of flow nodes according to the activity code of each node activity, the identification of the current flow node and the identification of the next flow node.
In some embodiments of the present invention, the flow node type is a page flow node, a flow node template of the page flow node is a storage address of page content, and the second determining is configured to: determining a next flow node to be executed according to the identification of the current flow node, the identification of the next flow node and the activity code of the current node activity, wherein the activity code of the current node activity is a first jump identification; or determining the next flow node to be executed according to the identification of the current flow node, the identification of the next flow node and the activity code of the current node activity, wherein the activity code of the current node activity is a second jump identification, and the second jump identification is different from the first jump identification.
In some embodiments of the present invention, the flow node type is a functional flow node, and the flow node template of the functional flow node is an interface identifier of the functional flow node, and the second determining includes: the calling module is used for calling the interface of the functional flow node according to the interface identifier of the functional flow node; the processing module is used for processing data related to the functional flow node by using the interface of the functional flow node; and the generating module is used for generating the page content of the functional flow node based on the processed data and sending the page content of the functional flow node.
In some embodiments of the present invention, the acquiring module is configured to: and acquiring the corresponding insurance application flow from the flow library according to the identification of the insurance product.
In some embodiments of the invention, the apparatus further comprises: and the query module is used for querying the related process nodes from the database of the process nodes based on the identification of the insurance product and generating the insurance process of the insurance product based on the process nodes related to the identification of the insurance product if the insurance process corresponding to the identification of the insurance product cannot be queried from the process library based on the identification of the insurance product. .
According to a third aspect of an embodiment of the present invention, there is provided an electronic apparatus including: one or more processors; and a storage device for storing one or more programs, which when executed by the one or more processors, cause the one or more processors to implement the flow node execution method according to the first aspect in the above embodiment.
According to a fourth aspect of embodiments of the present invention, there is provided a computer readable medium having stored thereon a computer program which, when executed by a processor, implements a flow node execution method as described in the first aspect of the above embodiments.
The technical scheme provided by the embodiment of the invention can have the following beneficial effects:
in the technical scheme provided by some embodiments of the present invention, the application flow includes a plurality of flow nodes and a plurality of node activities, the execution sequence among the plurality of flow nodes is determined according to the plurality of node activities, and when the plurality of flow nodes are executed, the page content of the flow nodes can be determined according to the content of the flow nodes, so that at least the problem of low page reusability is solved, and a developer is not required to redevelop a page due to different application flows, for example, the address of the page in the next step in the page content is reset, thereby reducing the workload of the developer and improving the speed of online insurance products.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention. It is evident that the drawings in the following description are only some embodiments of the present invention and that other drawings may be obtained from these drawings without inventive effort for a person of ordinary skill in the art. In the drawings:
FIG. 1 illustrates a schematic diagram of an exemplary system architecture of a process node execution method or process node execution apparatus to which embodiments of the present invention may be applied;
FIG. 2 schematically illustrates a flow chart of a method of flow node execution according to an embodiment of the invention;
FIG. 3 schematically illustrates a schematic diagram of an insurance product application flow in accordance with an embodiment of the invention;
FIG. 4 schematically illustrates a flow chart of a method of execution of a flow node according to another embodiment of the invention;
FIG. 5 schematically illustrates a block diagram of a flow node performing apparatus according to an embodiment of the invention;
Fig. 6 schematically shows a block diagram of a flow node executing arrangement according to another embodiment of the invention;
fig. 7 shows a schematic diagram of a computer system suitable for use in implementing an embodiment of the invention.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
The block diagrams depicted in the figures are merely functional entities and do not necessarily correspond to physically separate entities. That is, the functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The flow diagrams depicted in the figures are exemplary only, and do not necessarily include all of the elements and operations/steps, nor must they be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.
Fig. 1 shows a schematic diagram of an exemplary system architecture of a flow node execution method or a flow node execution apparatus to which an embodiment of the present invention may be applied.
As shown in fig. 1, the system architecture 100 may include one or more of terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is used as a medium to provide communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
It should be understood that the number of terminal devices, networks and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, the server 105 may be a server cluster formed by a plurality of servers.
The user may interact with the server 105 via the network 104 using the terminal devices 101, 102, 103 to receive or send messages or the like. The terminal devices 101, 102, 103 may be various electronic devices with display screens including, but not limited to, smartphones, tablet computers, portable computers, desktop computers, and the like.
The server 105 may be a server providing various services. For example, the user uploads the identifier of the insurance product to the server 105 by using the terminal device 103 (may also be the terminal device 101 or 102), and the server 105 may obtain an insurance process from a process library according to the identifier of the insurance product, where the insurance process includes a plurality of process nodes and a plurality of node activities, and determine an execution sequence between the plurality of process nodes according to the plurality of node activities; when executing a plurality of process nodes, determining the page content of the process nodes according to the content of the process nodes, and sending the page content of the process nodes to the terminal equipment 103 (also can be the terminal equipment 101 or 102), so that at least the problem of low page reusability is solved, and a developer is not required to redevelop a page due to different insurance procedures, for example, the page address of the next step in the page content is reset, thereby reducing the workload of the developer and improving the speed of online insurance products.
In some embodiments, the flow node executing method provided by the embodiments of the present invention is generally executed by the server 105, and accordingly, the flow node executing device is generally disposed in the server 105. In other embodiments, some terminals may have similar functions as servers to perform the method. Therefore, the flow node execution method provided by the embodiment of the invention is not limited to be executed at the server side.
Fig. 2 schematically shows a flow chart of a method of execution of a flow node according to an embodiment of the invention.
As shown in fig. 2, the method of constructing a knowledge graph may include steps S210 to S230.
In step S210, an application flow is acquired, where the application flow includes a plurality of flow nodes and a plurality of node activities.
In step S220, an execution order between the plurality of flow nodes is determined according to the plurality of node activities.
In step S230, when executing the plurality of flow nodes, determining the page content of the flow node according to the content of the flow node, and transmitting the page content of the flow node.
The method can determine the execution sequence among the plurality of process nodes according to the activities of the plurality of process nodes by acquiring the insuring process, wherein the insuring process comprises the plurality of process nodes and the plurality of node activities, and when the plurality of process nodes are executed, the page content of the process nodes can be determined according to the content of the process nodes, so that the problem of low page reusability is at least solved, a developer is not required to redevelop a page due to different insuring processes, for example, the page address of the next step in the page content is reset, thereby reducing the workload of the developer and improving the speed of online insurance products.
In one embodiment of the invention, acquiring the insurance flows may include acquiring the insurance flows corresponding thereto from a flow library according to the identification of the insurance product. For example, a user makes an application on an insurance application, and when the user selects an insurance product, the client sends an identification (for example, a 00001) of the insurance product, a server associated with the application receives the identification, and based on the identification, an application process corresponding to the identification can be matched from a process library, wherein the application process comprises a plurality of process nodes and a plurality of node activities.
In one embodiment of the invention, each flow node is stored in a designated database. The method further comprises the steps of: if the insurance process corresponding to the identifier of the insurance product is not queried from the process library based on the identifier of the insurance product, querying the process node related to the insurance product from the process node database based on the identifier of the insurance product, querying the node activity related to the insurance product from the node activity database based on the identifier of the insurance product, and generating the insurance process of the insurance product based on the process node and the node activity related to the identifier of the insurance product, so that the process node and the node activity related to the insurance product can be directly acquired from the process node database and the node activity database when the new insurance product is online, and the reusability of the process node and the node activity is improved. Then, based on the node activity and the process node, the application process of the new insurance product can be generated, and the application process is stored in the process library, so that the application process can be conveniently acquired based on the identification of the insurance product. Wherein node activity may also be stored in a designated database. In this example, the process node and node activity associated therewith is obtained from a database of process nodes and a database of node activity, and the business requirement of the insurance product, which may be newly online, is associated with the identity of the process node and the identity of the node activity.
In one embodiment of the invention, when a new insurance product is on line, whether the corresponding insurance flow exists or not can be inquired from a flow library based on the requirement flow designated by the service, if the insurance flow which is the same as the requirement flow exists, the insurance flow can be directly selected, and then the execution sequence of the insurance flow is determined according to the method of the invention. If the process node in the demand process is not the same as the demand process, inquiring whether the process node is the same as the demand process or not from a database of the process node according to the process node in the demand process, if the process node is not the same, customizing the process node in the demand process by a developer, and storing the customized process node into the database of the process node so as to facilitate the use of the subsequent new insurance product when the new insurance product is on line, thereby realizing the dynamic customization of the process node, improving the reuse rate of the process node, saving manpower consumption resources and accelerating the online speed of the insurance product. That is, because the process node can be dynamically configured, each new application process can be saved to the process library, when a new product is connected to the online process, if the new product process is already in the process library, only the process in the process library needs to be fetched, and the new process does not need to be reconfigured.
In one embodiment of the invention, the page content of each flow node is stored in a specified database, so that the page content of the flow node can be conveniently called from the database according to the content of the flow node when a user applies for protection, and the reusability of the page content is improved.
In one embodiment of the invention, the insurance product's application flow may include multiple flow nodes and multiple node activities. Referring to FIG. 3, product_AF30 may be an insurance product's application flow, product_AF30 including flow node f31 and node activity f32, where the starting flow node is product detail page id001. Specifically, the flow node f31 fills out the page id002 for the product detail page, the insured life, the push order function id003, the insuring confirmation page id004, the insuring success page id005, and the like. The node activity f32 is id 001-id 006, which is used for stringing the product detail page id001, the insured person filling page id002, the push order function id003, the insuring confirmation page id004 and the insuring success page id005, namely, is used for determining the execution sequence of a plurality of flow nodes.
In one embodiment of the invention, the content of each flow node includes any one or more of the following: the process node identification, the process node type, the process node template and the application process identification. Referring to FIG. 3, the flow node identification may be a product detail page id001, a cast insured fill page id002, a push order function id003, a cast validation page id004, a cast success page id005. The flow node types may be pageable nodes (e.g., product detail page, underwriter fill page, underwriter confirm page, underwriter success page) and functional nodes (e.g., push order function). The process node template may be property, which may refer to a storage address of page content corresponding to the process node or an interface identifier of the process node. The application flow identification may be product_a.
In one embodiment of the invention, the content of each node activity includes any one or more of the following: the identification of node activity, activity coding, the identification of current flow node, the identification of next flow node. Referring to FIG. 3, the identity of node activity may be id 001-id 006. The activity codes may be codes, for example, the activity codes of node activity ids 001, id002, id003, id005 are all next, and the activity code of node activity id004 is modified. The identification of the current flow node can be node, and the node can be a product detail page id001, a cast insured filling page id002, a push order function id003, a cast insuring confirmation page id004 and a cast successful page id005. The identity of the next flow node may be default_next_node_id 002-id 005.
In one embodiment of the invention, determining an execution order between the plurality of flow nodes based on the plurality of node activities comprises: determining the execution sequence among a plurality of flow nodes according to the activity code of each node activity, the identification of the current flow node and the identification of the next flow node. For example, determining an execution order among the plurality of flow nodes based on the plurality of node activities may include determining a next flow node to be executed based on an identification of a current flow node, an identification of the next flow node, and an activity code of the current node activity, the activity code of the current node activity being a first jump identification; or determining the next flow node to be executed according to the identification of the current flow node, the identification of the next flow node and the activity code of the current node activity, wherein the activity code of the current node activity is a second jump identification, and the second jump identification is different from the first jump identification. In this example, the active encoding code of the node activity may be next (i.e., first hop identification) or modified (i.e., second hop identification).
Referring to fig. 3, the active code of the node activity is next, the identifier node of the current flow node is id001, and the identifier of the next flow node is default_next_node_id002, in this case, after the product detail page id001 is executed, the executed insured person can be determined to continue to fill in the page id002 according to the contents of the three.
The active code of the node activity is next, the identifier node of the current flow node is id002, the identifier of the next flow node is default_next_node_id003, in this case, after the product detail page id002 is executed, the insured person can be continuously executed to fill in the page id003 according to the contents of the three.
The active code of the node activity is next, the identifier node of the current flow node is id003, the identifier of the next flow node is default_next_node_id004, in this case, after the product detail page id003 is executed, the insured person can be continuously executed to fill in the page id004 according to the contents of the three.
The active code of the node activity is modification, the identification node of the current flow node is id004, the identification of the next flow node is default_next_node_id002, in this case, after the execution of the product detail page id004 is completed, the execution of the insured person filling page id002 can be returned according to the contents of the three. If the active code of the node activity is next, the identifier node of the current flow node is id004, and the identifier of the next flow node is default_next_node_id005, in this case, the insured filling page id005 is continuously executed.
The active code of the node activity is next, the identifier node of the current flow node is id005, the identifier of the next flow node is default_next_node_id006, in this case, after the product detail page id005 is executed, the executed insured filling page id006 can be continuously executed according to the contents of the three.
In summary, the next flow node to be executed may be determined according to the activity code of the node activity, the identifier of the current flow node, and the identifier of the next flow node.
In one embodiment of the present invention, when the flow node type is a page flow node, and the flow node template of the page flow node is a storage address of page content, determining the page content of the flow node according to the content of the flow node, and sending the page content of the flow node may include obtaining the page content of the flow node according to the storage address of the page content, and sending the page content of the flow node. For example, the current flow node is a product detail page, and the flow node template of the page flow node is D: \insurance product A\page content\product detail page\, in this case, the page content of the current flow node (namely, the page content of the product detail page) is obtained according to the condition that the product is D: \insurance product A\page content\product detail page\ ".
Fig. 4 schematically shows a flow chart of a method of executing a flow node according to another embodiment of the invention.
As shown in fig. 4, when the flow node type is a functional flow node, and the flow node template of the functional flow node is the interface identifier of the functional flow node, step S230 may specifically include steps S410 to S430.
In step S410, the interface of the functional flow node is called according to the interface identifier of the functional flow node.
In step S420, data related to the functional flow node is processed using the interface of the functional flow node.
In step S430, page content of the functional flow node is generated based on the processed data, and the page content of the functional flow node is transmitted.
According to the method, the interface of the functional flow node can be called according to the interface identification of the functional flow node, the data related to the functional flow node are processed by using the interface of the functional flow node, the page content of the functional flow node is generated based on the processed data, and the page content of the functional flow node is sent.
In one embodiment of the present invention, the flow node type may be a functional flow node, and the flow node template of the functional flow node is an interface identifier of the functional flow node. For example, the interface identifier may be an interface001 (e.g., an interface identifier of a push order function node), an interface of the push order function node may be called according to the interface001, data related to the interface of the push order function node (e.g., product information in an order, the number of orders, etc.) may be processed using the interface of the push order function node, page content of the push order function node may be generated based on the processed data, and at this time, the page content of the push order function node may be sent, so that the page content of the function flow node may be generated by using the data processed by the interface of the function flow node, without developing the page content of the function flow node offline by a developer, so as to further reduce workload of the developer.
Fig. 5 schematically shows a block diagram of a flow node executing arrangement according to an embodiment of the invention.
As shown in fig. 5, the flow node executing apparatus 500 includes an obtaining module 510, a first determining module 520, and a second determining module 530.
Specifically, the obtaining module 510 is configured to obtain an application flow, where the application flow includes a plurality of flow nodes and a plurality of node activities.
A first determining module 520 is configured to determine an execution order among the plurality of flow nodes according to the plurality of node activities.
The second determining module 530 determines, when executing the plurality of flow nodes, page contents of the flow nodes according to contents of the flow nodes, and sends the page contents of the flow nodes.
The process node executing device 500 may obtain an application process, where the application process includes a plurality of process nodes and a plurality of node activities, determine an execution sequence among the plurality of process nodes according to the plurality of node activities, and determine a page content of the process nodes according to a content of the process nodes when executing the plurality of process nodes, so that at least a problem of low page reusability is solved, and a developer is not required to redevelop a page due to different application processes, for example, redevelop a page address of a next step in the page content is reset, thereby reducing workload of the developer and improving a speed of online insurance products.
The flow node execution apparatus 500 may be used to implement the flow node execution method described in the embodiment of fig. 2, according to an embodiment of the present invention.
Fig. 6 schematically shows a block diagram of a flow node executing arrangement according to another embodiment of the invention.
As shown in fig. 6, the second determining module 530 includes a calling module 531, a processing module 532, and a generating module 533.
Specifically, the calling module 531 is configured to call an interface of the functional flow node according to the interface identifier of the functional flow node.
The processing module 532 processes data related to the functional flow node using the interface of the functional flow node.
The generating module 533 generates the page content of the functional flow node based on the processed data, and sends the page content of the functional flow node.
The second determining module 530 may call the interface of the functional flow node according to the interface identifier of the functional flow node, process data related to the functional flow node using the interface of the functional flow node, generate page content of the functional flow node based on the processed data, and send the page content of the functional flow node, so that the page content of the functional flow node may be generated by using the data processed by the interface of the functional flow node, without developing the page content of the functional flow node offline by a developer, and further reduce workload of the developer.
The second determining module 530 may be used to implement the flow node execution method described in the embodiment of fig. 4, according to an embodiment of the present invention.
In one embodiment of the present invention, when the flow node type is a page flow node, and the flow node template of the page flow node is a storage address of the page content, the second determining module 530 may be configured to: and acquiring the page content of the flow node according to the storage address of the page content, and sending the page content of the flow node. For example, the current flow node is a product detail page, and the flow node template of the page flow node is D: \insurance product A\page content\product detail page\, in this case, the page content of the current flow node (namely, the page content of the product detail page) is obtained according to the condition that the product is D: \insurance product A\page content\product detail page\ ".
In one embodiment of the present invention, the flow node type may be a functional flow node, and the flow node template of the functional flow node is an interface identifier of the functional flow node. For example, the interface identifier may be an interface001 (e.g., an interface identifier of a push order function node), an interface of the push order function node may be called according to the interface001, data related to the interface of the push order function node (e.g., product information in an order, the number of orders, etc.) may be processed using the interface of the push order function node, page content of the push order function node may be generated based on the processed data, and at this time, the page content of the push order function node may be sent, so that the page content of the function flow node may be generated by using the data processed by the interface of the function flow node, without developing the page content of the function flow node offline by a developer, so as to further reduce workload of the developer.
Since each module of the flow node execution device according to the exemplary embodiment of the present invention may be used to implement the steps of the exemplary embodiment of the flow node execution method described in the foregoing description of fig. 2 and fig. 4, for details not disclosed in the embodiment of the apparatus according to the present invention, please refer to the embodiment of the flow node execution method described in the foregoing description of the embodiment of the present invention.
It is understood that the obtaining module 510, the first determining module 520, the second determining module 530, the invoking module 531, the processing module 532, and the generating module 533 may be combined in one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the invention, at least one of the acquisition module 510, the first determination module 520, the second determination module 530, the invocation module 531, the processing module 532, and the generation module 533 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or any other reasonable manner in which circuitry is integrated or packaged, or as hardware or firmware, or as a suitable combination of software, hardware, and firmware implementations. Alternatively, at least one of the acquisition module 510, the first determination module 520, the second determination module 530, the calling module 531, the processing module 532, and the generating module 533 may be at least partially implemented as computer program modules, which when executed by a computer, may perform the functions of the respective modules.
Referring now to FIG. 7, there is illustrated a schematic diagram of a computer system 600 suitable for use in implementing an electronic device of an embodiment of the present invention. The computer system 600 of the electronic device shown in fig. 7 is only an example and should not be construed as limiting the functionality and scope of use of embodiments of the invention.
As shown in fig. 7, the computer system 600 includes a Central Processing Unit (CPU) 601, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage section 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data required for system operation are also stored. The CPU 601, ROM 602, and RAM 603 are connected to each other through a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
The following components are connected to the I/O interface 605: an input portion 606 including a keyboard, mouse, etc.; an output portion 607 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 608 including a hard disk and the like; and a communication section 609 including a network interface card such as a LAN card, a modem, or the like. The communication section 609 performs communication processing via a network such as the internet. The drive 610 is also connected to the I/O interface 605 as needed. Removable media 611 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on drive 610 so that a computer program read therefrom is installed as needed into storage section 608.
In particular, according to embodiments of the present invention, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network through the communication portion 609, and/or installed from the removable medium 611. The above-described functions defined in the system of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 601.
The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present invention may be implemented by software, or may be implemented by hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by one of the electronic devices, cause the electronic device to implement the flow node execution method as described in the above embodiments.
For example, the electronic device may implement the method as shown in fig. 2: in step S210, an application flow is acquired, where the application flow includes a plurality of flow nodes and a plurality of node activities. In step S220, an execution order between the plurality of flow nodes is determined according to the plurality of node activities. In step S230, when executing the plurality of process nodes, determining the page content of the process node according to the content of the process node, and sending the page content of the process node, so at least the problem of low page reusability is solved, and the developer is not required to redevelop the page due to different insurance procedures, for example, the address of the page in the next step in the page content is reset, thereby reducing the workload of the developer and improving the speed of online insurance products.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the invention. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present invention may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, and includes several instructions to cause a computing device (may be a personal computer, a server, a touch terminal, or a network device, etc.) to perform the method according to the embodiments of the present invention.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the invention and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
It is to be understood that the invention is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the invention is limited only by the appended claims.
Claims (9)
1. A method for executing a process node, comprising:
acquiring an application process, wherein the application process comprises a plurality of process nodes and a plurality of node activities;
determining an execution sequence among the plurality of process nodes according to the plurality of node activities;
when executing the plurality of flow nodes, determining the page content of the flow nodes according to the content of the flow nodes, and sending the page content of the flow nodes;
Wherein the content of each node activity includes any one or more of: the method comprises the steps of identifying node activity, activity coding, identifying current flow nodes and identifying next flow nodes;
wherein said determining an execution order between the plurality of process nodes based on the plurality of node activities comprises:
determining a next flow node to be executed according to the identification of the current flow node, the identification of the next flow node and the activity code of the current node activity, wherein the activity code of the current node activity is a first jump identification; or alternatively
Determining a next flow node to be executed according to the identification of the current flow node, the identification of the next flow node and the activity code of the current node activity, wherein the activity code of the current node activity is a second jump identification, and the second jump identification is different from the first jump identification.
2. The method of claim 1, wherein the content of each flow node comprises any one or more of: the process node identification, the process node type, the process node template and the application process identification.
3. The method of claim 2, wherein the process node type is a page process node, the process node template of the page process node is a storage address of page content,
Determining the page content of the process node according to the content of the process node, and sending the page content of the process node comprises:
and acquiring the page content of the flow node according to the storage address of the page content, and sending the page content of the flow node.
4. The method of claim 2, wherein the process node type is a function process node, the process node template of the function process node is an interface identifier of the function process node,
determining the page content of the process node according to the content of the process node, and sending the page content of the process node comprises:
calling an interface of the functional flow node according to the interface identifier of the functional flow node;
processing data related to the functional flow node by using an interface of the functional flow node;
and generating the page content of the functional flow node based on the processed data, and sending the page content of the functional flow node.
5. The method of claim 1, wherein obtaining the application flow comprises: and acquiring the corresponding insurance application flow from the flow library according to the identification of the insurance product.
6. The method of claim 5, further comprising:
if the insurance process corresponding to the identification of the insurance product is not queried from the process library based on the identification of the insurance product, querying a process node related to the identification of the insurance product from a database of process nodes based on the identification of the insurance product, and querying a node activity related to the identification of the insurance product from a database of node activities based on the identification of the insurance product, and generating the insurance process of the insurance product based on the process node and the node activity related to the identification of the insurance product.
7. A flow node execution apparatus, comprising:
the system comprises an acquisition module, a storage module and a storage module, wherein the acquisition module is used for acquiring an application flow, and the application flow comprises a plurality of flow nodes and a plurality of node activities;
a first determining module, configured to determine an execution order among the plurality of flow nodes according to the activities of the plurality of nodes;
the second determining module is used for determining the page content of the flow node according to the content of the flow node and sending the page content of the flow node when the plurality of flow nodes are executed;
Wherein the content of each node activity includes any one or more of: the method comprises the steps of identifying node activity, activity coding, identifying current flow nodes and identifying next flow nodes;
the first determining module is further configured to determine a next process node to be executed according to the identifier of the current process node, the identifier of the next process node, and an activity code of the current node activity, where the activity code of the current node activity is a first jump identifier; or alternatively
Determining a next flow node to be executed according to the identification of the current flow node, the identification of the next flow node and the activity code of the current node activity, wherein the activity code of the current node activity is a second jump identification, and the second jump identification is different from the first jump identification.
8. An electronic device, comprising:
one or more processors; and
storage means for storing one or more programs which when executed by the one or more processors cause the one or more processors to implement the method of any of claims 1-6.
9. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911222294.1A CN111176641B (en) | 2019-12-03 | 2019-12-03 | Flow node execution method, device, medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911222294.1A CN111176641B (en) | 2019-12-03 | 2019-12-03 | Flow node execution method, device, medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111176641A CN111176641A (en) | 2020-05-19 |
| CN111176641B true CN111176641B (en) | 2023-06-02 |
Family
ID=70648842
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911222294.1A Active CN111176641B (en) | 2019-12-03 | 2019-12-03 | Flow node execution method, device, medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111176641B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111652580B (en) * | 2020-05-29 | 2023-02-14 | 深圳平安医疗健康科技服务有限公司 | Method and device for processing data of nodes |
| CN112465599B (en) * | 2020-12-04 | 2023-11-07 | 车智互联（北京）科技有限公司 | Order processing method, order processing system and computing equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105404507A (en) * | 2015-11-04 | 2016-03-16 | 山东中创软件工程股份有限公司 | Process template construction method and system |
| CN108665129A (en) * | 2017-03-31 | 2018-10-16 | 华为软件技术有限公司 | A kind of Workflow Custom method and device |
| CN109324787A (en) * | 2017-08-18 | 2019-02-12 | 深圳怡化电脑股份有限公司 | A kind of business software development approach, device and terminal device |
| CN109359939A (en) * | 2018-09-26 | 2019-02-19 | 中国平安人寿保险股份有限公司 | Business datum method of calibration, device, computer equipment and storage medium |
| CN109658059A (en) * | 2018-12-12 | 2019-04-19 | 泰康保险集团股份有限公司 | File checking method, device, electronic equipment and computer-readable medium |
| CN110008118A (en) * | 2019-03-13 | 2019-07-12 | 深圳壹账通智能科技有限公司 | Page data test method, device, computer equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9300545B2 (en) * | 2011-10-11 | 2016-03-29 | Google Inc. | Page layout in a flow visualization |
| US10262148B2 (en) * | 2012-01-09 | 2019-04-16 | Visa International Service Association | Secure dynamic page content and layouts apparatuses, methods and systems |
-
2019
- 2019-12-03 CN CN201911222294.1A patent/CN111176641B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105404507A (en) * | 2015-11-04 | 2016-03-16 | 山东中创软件工程股份有限公司 | Process template construction method and system |
| CN108665129A (en) * | 2017-03-31 | 2018-10-16 | 华为软件技术有限公司 | A kind of Workflow Custom method and device |
| CN109324787A (en) * | 2017-08-18 | 2019-02-12 | 深圳怡化电脑股份有限公司 | A kind of business software development approach, device and terminal device |
| CN109359939A (en) * | 2018-09-26 | 2019-02-19 | 中国平安人寿保险股份有限公司 | Business datum method of calibration, device, computer equipment and storage medium |
| CN109658059A (en) * | 2018-12-12 | 2019-04-19 | 泰康保险集团股份有限公司 | File checking method, device, electronic equipment and computer-readable medium |
| CN110008118A (en) * | 2019-03-13 | 2019-07-12 | 深圳壹账通智能科技有限公司 | Page data test method, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111176641A (en) | 2020-05-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110852882B (en) | Packet consensus method, apparatus, device, and medium for blockchain networks | |
| CN109857577B (en) | Access control method, device, medium, and electronic apparatus | |
| CN111176641B (en) | Flow node execution method, device, medium and electronic equipment | |
| CN113076153B (en) | Interface calling method and device | |
| CN109325744B (en) | Payment processing method, payment processing device, payment processing medium and electronic equipment | |
| CN111538545A (en) | Java application running method, device, medium and electronic equipment | |
| CN112650804B (en) | Big data access method, device, system and storage medium | |
| CN109343970B (en) | Application program-based operation method and device, electronic equipment and computer medium | |
| CN110930253B (en) | Method and device for generating main key inside intelligent contract, computer equipment and storage medium | |
| CN112884098A (en) | Card number generation method and device | |
| CN108804442B (en) | Serial number generation method and device | |
| CN111460020B (en) | Method, device, electronic equipment and medium for resolving message | |
| CN114302207A (en) | Bullet screen display method, device, system, equipment and storage medium | |
| CN113537893A (en) | Order processing method, device, equipment and computer readable medium | |
| CN109669679B (en) | Service detection and processing method and device and electronic equipment | |
| CN109657179B (en) | Service processing method, system and storage medium | |
| CN109840073B (en) | Method and device for realizing business process | |
| CN113127561A (en) | Method and device for generating service order number, electronic equipment and storage medium | |
| CN113760487A (en) | Service processing method and device | |
| CN116204201B (en) | Service processing method and device | |
| CN112688863B (en) | Gateway data processing method and device and electronic equipment | |
| CN117132245B (en) | Method, device, equipment and readable medium for reorganizing online article acquisition business process | |
| CN114969059B (en) | Method and device for generating order information, electronic equipment and storage medium | |
| CN111027809B (en) | Message notification method, device, medium and electronic equipment | |
| CN113765868B (en) | Service processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |