CN114895989A

CN114895989A - Configuration method, device and equipment of business event and storage medium

Info

Publication number: CN114895989A
Application number: CN202210473834.9A
Authority: CN
Inventors: 张后礼
Original assignee: Beijing Whale Stork Technology Co ltd
Current assignee: Beijing Whale Stork Technology Co ltd
Priority date: 2022-04-29
Filing date: 2022-04-29
Publication date: 2022-08-12

Abstract

The application provides a configuration method, a device, equipment and a storage medium of a business event, comprising the following steps: configuring a service event list at the flow node in response to the configuration request; configuring an execution condition and an execution result of a business event aiming at any business event in a business event list; the execution condition includes a plurality of sub-conditions connected by logical operators, the sub-conditions including a first reference field, the execution result including at least one second reference field, the first and second reference fields for referencing corresponding metadata from the data center. According to the method of the embodiment of the application, the flexibility and the degree of freedom of the configuration of the business event are improved.

Description

Configuration method, device and equipment of business event and storage medium

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a method, an apparatus, and a storage medium for configuring a service event.

Background

In the related art, a Flowable workflow engine (an open source workflow engine) is generally used for configuration of a business event. The Flowable is implemented by Java (a computer Programming language) -based software of BPMN (Business Process Modeling and labeling), and includes not only BPMN, but also DMN (Business Decision Management standard) Decision tables and CMMN Management engines (Case Management Model and Notation Management engine), and has a series of functions such as user Management and micro-service API (Application Programming Interface), which is a workflow service platform.

The service code executed by each node in the above-mentioned Flowable workflow engine is fixed, and if the service logic changes, the code needs to be changed every time, so that the change cost is high, and the later maintenance is not facilitated. In addition, the entry of the process conditions can only be obtained by setting constants and process contexts, and the values are relatively rigid and inflexible.

Disclosure of Invention

The embodiment of the application provides a configuration method, device equipment and storage medium of a business event, so as to solve the problems in the related technology, and the technical scheme is as follows:

in a first aspect, an embodiment of the present application provides a method for configuring a service event, including:

configuring a service event list at the flow node in response to the configuration request;

configuring an execution condition and an execution result of a business event aiming at any business event in a business event list; the execution condition includes a plurality of sub-conditions connected by logical operators, the sub-conditions including a first reference field, the execution result including at least one second reference field, the first and second reference fields for referencing corresponding metadata from the data center.

In one embodiment, configuring the execution condition of the business event comprises:

and aiming at any sub-condition, configuring a first reference field, a comparison character, an insertion value and a reference value of the sub-condition, wherein the first reference field of the sub-condition is used for referencing corresponding metadata from a data center as the insertion value of the sub-condition, and the comparison character of the sub-condition is used for comparing the insertion value of the sub-condition and the reference value of the sub-condition.

In one embodiment, the business event includes a message event, and configuring an execution result of the business event includes:

acquiring a preset insertion position in a message template of a message event;

and configuring a second reference field corresponding to the preset insertion position, wherein the second reference field is used for referencing metadata of the data center as a variable value of the preset insertion position.

In one embodiment, the first referenced field and/or the second referenced field includes a multi-level field that matches a consanguinity relationship of metadata of the data center.

In one embodiment, the method further comprises:

responding to the node change request, and configuring at least one change condition of a target service event corresponding to the node change request at the gateway branch node; and the number of the first and second groups,

and configuring a change result corresponding to each change condition, wherein the change result is used for changing the approver information corresponding to the target business event into the target approver information under the condition that the change condition is met.

In one embodiment, the change condition is a mutually exclusive plurality.

In one embodiment, configuring a list of service events at a flow node comprises:

configuring service description information for any service event in the service event list, wherein the service description information comprises at least one item of an event name, an event ID, an execution sequence, an operation type and a condition name.

In a second aspect, an embodiment of the present application further provides a device for configuring a service event, including:

a list configuration module for configuring a service event list at the process node in response to the configuration request;

the service event configuration module is used for configuring the execution conditions and the execution results of the service events aiming at any service event in the service event list; the execution condition includes a plurality of sub-conditions connected by logical operators, the sub-conditions including a first reference field, the execution result including at least one second reference field, the first and second reference fields for referencing corresponding metadata from the data center.

In one embodiment, the service event configuration module comprises:

and the first configuration sub-module is used for configuring a first reference field, a comparison character, an insertion value and a reference value of the sub-condition aiming at any sub-condition, the first reference field of the sub-condition is used for referencing corresponding metadata from a data center as the insertion value of the sub-condition, and the comparison character of the sub-condition is used for comparing the insertion value of the sub-condition and the reference value of the sub-condition.

In one embodiment, the service event includes a message event, and the service event configuration module includes:

the preset insertion position acquisition sub-module is used for acquiring a preset insertion position in a message template of a message event;

and the second configuration submodule is used for configuring a second reference field corresponding to the preset insertion position, and the second reference field is used for referencing metadata of the data center as a variable value of the preset insertion position.

In one embodiment, the apparatus further comprises:

the change condition configuration module is used for responding to the node change request and configuring at least one change condition of a target service event corresponding to the node change request at the gateway branch node; and the number of the first and second groups,

and the change result configuration module is used for configuring change results corresponding to all the change conditions, and the change results are used for changing the approver information corresponding to the target business event into the target approver information under the condition that the change conditions are met.

In one embodiment, the change condition is a mutually exclusive plurality.

In one embodiment, the list configuration module is further configured to:

and configuring service description information for any service event in the service event list, wherein the service description information comprises at least one item of an event name, an event ID, an execution sequence, an operation type and a condition name.

In a third aspect, an embodiment of the present application provides an electronic device, including: a memory and a processor. Wherein the memory and the processor are in communication with each other via an internal connection path, the memory is configured to store instructions, the processor is configured to execute the memory-stored instructions, and the processor is configured to cause the processor to perform the method of any of the above-described aspects when executing the memory-stored instructions.

In a fourth aspect, the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, and when the computer program runs on a computer, the method in any one of the above-described aspects is executed.

According to the configuration method of the business event, the corresponding metadata in the data center can be referred to the execution condition and the execution result through the first reference field for configuring the execution condition of the business event and the second reference field for configuring the execution result of the business event, so that the flexibility and the degree of freedom for configuring the execution condition and the execution result are improved.

The foregoing summary is provided for the purpose of description only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features of the present application will be readily apparent by reference to the drawings and following detailed description.

Drawings

In the drawings, like reference numerals refer to the same or similar parts or elements throughout the several views unless otherwise specified. The figures are not necessarily to scale. It is appreciated that these drawings depict only some embodiments in accordance with the disclosure and are not to be considered limiting of its scope.

Fig. 1 shows a flow chart of a configuration method of a business event according to an embodiment of the application;

fig. 2 is a flowchart illustrating a configuration execution result of a configuration method of a business event according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a configuration change condition and a change result of a configuration method of a business event according to an embodiment of the present application;

FIG. 4 illustrates a schematic diagram of configuring a business event list according to an embodiment of the application;

FIG. 5 shows a schematic diagram of configuring execution conditions according to an embodiment of the application;

FIG. 6 shows a schematic diagram of configuration execution results according to an embodiment of the application;

fig. 7 shows a schematic diagram of a configuration change condition according to an embodiment of the present application;

FIG. 8 illustrates an application diagram of a business event after configuration is completed according to an embodiment of the application;

FIG. 9 shows a schematic diagram of a configuration device for business events according to an embodiment of the application;

fig. 10 shows a block diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In the following, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments may be modified in various different ways, all without departing from the spirit or scope of the present application. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.

Fig. 1 shows a flowchart of a configuration method of a business event according to an embodiment of the present application.

In a specific application example, the configuration method of the business event of the embodiment of the present application may be used for

As shown in fig. 1, the configuration method of the service event may include:

s101: configuring a service event list at the flow node in response to the configuration request;

s102: configuring an execution condition and an execution result of a business event aiming at any business event in a business event list; the execution condition includes a plurality of sub-conditions connected by logical operators, the sub-conditions including a first reference field, the execution result including at least one second reference field, the first and second reference fields for referencing corresponding metadata from the data center.

It is understood that a business event refers to a code segment related to business logic processing that needs to be executed during the running process of a program and can return a running result. Metadata refers to data for describing data, and mainly includes information for describing data attributes and association relationships between data.

Illustratively, in step S101, the configuration request may be initiated by the user by clicking on a flow node page. The business event list comprises at least one business event related to the approver information of the current process node, and the approver information is used for representing an executor for executing approval operation on each business event in the business event list under the current process node.

More specifically, each service event has service description information. As shown in fig. 4, the service description information includes an event name, an event ID, an execution event, an operation type, a condition name, and an operation option. Wherein the operation options include an edit option and a delete option. Responding to the click operation of the user on the editing options, and editing the execution conditions and the execution results of the business events; and in response to the click operation of the user on the deletion option, deleting the business event in the business event list.

Illustratively, in step S102, in response to a click operation of a user on an editing option corresponding to any business event, the execution condition and the execution result are configured in an editing page of the business event.

The editing page comprises an event information editing module, an execution condition editing module and an execution result editing module. The event information editing module comprises an event name editing submodule, an operation type editing submodule and an execution sequence editing submodule; the execution condition editing module comprises a condition name editing submodule, a trigger condition editing submodule, an output type editing submodule, a sub-condition editing submodule and an execution condition expression editing submodule.

The sub-condition editing sub-module is used for configuring a first reference field, a comparison character, an insertion value and a reference value. For example, the reference field may be "operation type", the comparison character may be "═", the insertion value is the corresponding metadata referenced by the reference field in the data center, and the reference value is "audit pass". And in the case that the insertion value is 'approved', the comparison result of the insertion value and the reference value accords with the judgment logic of the comparison character, namely the insertion value is equal to the reference value, and the sub-condition is satisfied.

Executing the conditional expressions as simultaneous results of the respective sub-conditions by the logical operators. Wherein the logical operator may be at least one of "AND", "OR", AND "NOT". For example, if the plurality of sub-conditions include condition 1, condition 2, AND condition 3, the execution condition expression may be "1 AND 2AND 3", that is, in a case where all of condition 1, condition 2, AND condition 3 are satisfied, the execution condition of the business event is satisfied. For another example, the execution condition expression may also be "1 OR 2 OR 3", that is, in a case where at least one of the condition 1, the condition 2, and the condition 3 is satisfied, the execution condition of the service event is satisfied.

And triggering an execution result corresponding to the business event under the condition that the execution condition is satisfied. In the embodiment of the present application, the type of the service event may include a service type, a message type, and a change type. The execution result can be configured correspondingly according to the type of the service event.

For example, for a service event of which the type is a message type, the execution result of the service event may be a sending message. In the editing page of the execution result, the message content can be edited by adding the reference field.

For another example, for a business event whose type is a change type, the execution result of the business event may be a change result of at least one event description information of the business event.

In the embodiment of the present application, according to the ranking order of each service event in the service event list, the back-reference (i.e., the execution result) of any service event can be used as the reference of the execution condition of the next service event. Therefore, the entry and counter-entry process conditions required by the business event are connected in series, the execution conditions and the execution results required to be executed are determined according to different states of the business data, and the counter-entry of the business event can be used as the entry of the next business event or the entry of a certain execution condition.

In one embodiment, step S102 includes:

In this case, the comparison character may be any one of ">", "<" or "═ to characterize the numerical relationship between the interpolated value and the reference value when the sub-condition is satisfied. That is, in the case where the numerical relationship between the insertion value and the reference value does not conform to the comparison character, the sub-condition does not hold.

Illustratively, as shown in fig. 5, the execution condition includes a plurality of sub-conditions of condition 1, condition 2, and condition 3, respectively. In condition 1, the first reference field is "operation type", the comparison character is "═ and the insertion value is metadata referenced in the data center by the first reference field" operation type ", and the reference value is" audit pass ", whereby condition 1 is established in the case where the insertion value is" audit pass "which is the same as the reference value. In condition 2, the first reference field is "payout amount", the comparison character is "< >", the insertion value is metadata referenced in the data center by the first reference field "payout amount", and the reference value is "0", whereby condition 2 is satisfied in the case where the insertion value is different from the reference value, that is, the payout amount is not 0. In condition 3, the first reference field is "pay method", the comparison character is "═", the insertion value is metadata referenced in the data center by the first reference field "pay method", and the reference value is "pad payment", whereby condition 3 is satisfied in the case where the insertion value is "pad payment" identical to the reference value.

In the embodiment of the present application, the first reference field of the sub-condition may be set according to actual needs, and this is not specifically limited in the embodiment of the present application.

Through the embodiment, for each sub-condition of the execution condition of the business event, the corresponding first reference field can be configured, so that the metadata referred by the first reference field is used as the reference of the sub-condition, and the corresponding reference value and the comparison character are configured as the basis for judging whether the sub-condition is established, thereby improving the flexibility and the degree of freedom of setting the sub-condition.

As shown in fig. 2, in one embodiment, the service event includes a message event, and step S102 includes:

s201: acquiring a preset insertion position in a message template of a message event;

s202: and configuring a second reference field corresponding to the preset insertion position, wherein the second reference field is used for referencing metadata of the data center as a variable value of the preset insertion position.

Illustratively, the message template includes a preset message content, and the preset insertion position may be obtained through a variable field inserted in advance in the message content. And configuring a second reference field corresponding to the variable field aiming at the variable field in the message content, wherein the second reference field is used for referencing metadata of a data center and replacing the variable field in the message content so as to be used as a variable value of a preset insertion position.

In a specific example, as shown in fig. 6, the message template has a plurality of preset insertion positions, and each preset insertion position is provided with a variable field. The method for inserting the variable value into each variable field may be implemented in a manner of assigning, field referencing, and process context filling. And configuring a corresponding second reference field for the variable field according to the field reference mode, wherein the second reference field is inserted into the preset insertion position where the variable field is located from the metadata referenced by the data center as the variable value. The second reference fields corresponding to the variable fields may be "real name", "time to issue claim", "user name", and "customer service telephone", respectively.

Therefore, by configuring the second reference field to reference the metadata from the data center as the variable value at the preset insertion position of the message template, the edited message content can be quickly generated, and compared with a manual editing mode, the processing efficiency of the execution result is improved, and the labor cost of manual editing is reduced.

It is understood that metadata stored by the data center has a blood-based relationship, and the blood-based relationship of the metadata is obtained based on data blood-based analysis of the data center. The blood relationship analysis refers to the blood relationship of the acquired data, records the relationship among the source, the processing process, the carding system, the table, the view, the storage process, the ETL, the program code, the field and the like of the data in a historical fact mode, and adopts a graph database for visual display. Through the blood relationship of the metadata, for some key indexes, the calculation process of the indexes can be checked, and the related data sources are traced back.

In one example, as shown in fig. 7, the multi-level field includes a plurality of levels of fields that match the relationship of the blood relationship of the metadata, and the plurality of levels of fields have a superior-inferior relationship. For example, the multi-level fields include a first-level field, a second-level field, and a third-level field in order of upper and lower levels, wherein the first-level field may include an associated object, the second-level field includes a plurality of lower-level fields of the associated object, i.e., an owner ID (user information table), an organization ID (enterprise information), a product ID (product information), a plan ID (plan information table), a personal group ID (user policy), and a responsibility ID (responsibility information), and the third-level field includes a plurality of lower-level fields of the organization ID, i.e., a parent ID, an enterprise name, an enterprise status identifier, an organization ID, and a client type.

Through the embodiment, the setting range of the execution conditions and the participation of the execution results is further enlarged, so that the flexibility and the degree of freedom of configuring the execution events are further improved.

As shown in fig. 3, in one embodiment, the method further comprises:

s301: responding to the node change request, and configuring at least one change condition of a target service event corresponding to the node change request at the gateway branch node; and the number of the first and second groups,

s302: and configuring a change result corresponding to each change condition, wherein the change result is used for changing the approver information corresponding to the target business event into the target approver information under the condition that the change condition is met.

The execution result of the service event can be used as the entry of the change condition of the corresponding target service event configured by the gateway branch node.

Illustratively, the process node includes approver information for characterizing an approver responsible for approving all business events in the list of business events. The node change request is used for requesting to change the approver information of any business event in the business event list. The change conditions may be a plurality of different ones, and each change condition corresponds to a change result, and the change result is used to change the approver information of the target business event into the target approver information when the change condition is satisfied.

In one example, as shown in FIG. 7, an altered condition includes a plurality of altered sub-conditions connected by logical operators. Configuring a change condition of a target service event corresponding to a node change request at a gateway branch node, wherein the change condition comprises the following steps:

the third reference field, the comparison character, the insertion value, and the reference value of the alteration sub-condition are configured for any one of the plurality of alteration sub-conditions. And the third reference field is used for referencing metadata from the data center as an insertion value, and the comparison character is used for representing the numerical relationship between the insertion value and the reference value under the condition that the change sub-condition is satisfied. The plurality of alteration sub-conditions are connected by at least one of the logical operators "AND", "OR", "NOT" to form an alteration condition.

For example, the plurality of change sub-conditions may include condition 1, condition 2, AND condition 3, AND the change condition may be "condition 1AND condition 2AND condition 3", that is, when all of the three change sub-conditions are satisfied, the change condition is satisfied.

With the above embodiment, when the change condition is satisfied, the approver information of the target business event corresponding to the change request node is changed to the target approver information, thereby realizing automatic circulation of the business event.

In one embodiment, the change condition is a mutually exclusive plurality.

In other words, when one of the plurality of change conditions is satisfied, the other change condition is not satisfied.

In an exemplary case, the plurality of change conditions correspond to different target approver information, that is, when any one of the plurality of change conditions is satisfied, the approver information of the target business event is changed to the target approver information corresponding to the satisfied change condition.

By the implementation mode, the business events can be automatically transferred among the plurality of approval nodes, and the user can customize the change conditions and the corresponding target approver information, so that the diversity of the transfer of the business events is improved.

And when the metadata is referred from the data center through the event ID and the first reference field and/or the second reference field, the metadata associated with the business event can be referred according to the event ID.

An application example of the configuration method of the service event according to the embodiment of the present application after the configuration is completed is described below with reference to fig. 8.

As shown in fig. 8, for the approval node 1, the bound service events are executed in the order of the service event list during the approval process. Firstly, inquiring a service event list under a current node; then, whether the business event has an execution condition is judged, and if the execution condition does not exist, the business event is directly executed.

If an execution condition exists, then the conditional service is invoked. The conditional service calls a data center, metadata in the conditions are analyzed into an arithmetic expression through the data center and returned to the conditional service, and the conditional service obtains a judgment result according to the conditional expression; and executing the business event under the condition that the judgment result is that the condition is satisfied. The data center analyzes the association relationship between the data tables stored in the data center and the relationship between the fields and the data tables according to the description of the metadata, and dynamically changes the service data.

In the course of executing each business event in the event list. And for the business event 1, calling a business logic interface preset by the business event to acquire a corresponding service, and receiving a result v1 returned by the corresponding service. And taking the returned result v1 as the entry parameter of the business event 2, sending v1 as a parameter to the data center, and calling corresponding metadata as a back parameter through the data center to return to the business event 2. Then, the back-participation of the data center is taken as the participation of the business event 3. And circulating until all the service events are executed.

And executing a node change process through the gateway under the condition that the user initiates a node change request. Specifically, the node change request has corresponding branch condition 1and branch condition 2, and when the branch condition 1 is satisfied, the approver information of the target business event corresponding to the node change request is changed into the target approver information of the approval node 2; when the branching condition 2 is satisfied, the approver information of the target business event corresponding to the node change request is changed to the target approver information of the approval node 3.

According to the configuration method of the business event, the incidence relation and the process of the business event are decoupled, the entry and counter-entry process conditions required by the business event are connected in series, the execution conditions and the execution results required to be executed are determined according to different states of the business data, and the entry and counter-entry of the business event can be used as the entry of the next business event or the entry of a certain condition.

In a second aspect, an embodiment of the present application further provides a device for configuring a service event.

As shown in fig. 9, the configuration apparatus of the service event includes:

a list configuration module 901, configured to configure a service event list at a flow node in response to a configuration request;

a service event configuration module 902, configured to configure an execution condition and an execution result of a service event for any service event in the service event list; the execution condition includes a plurality of sub-conditions connected by logical operators, the sub-conditions including a first reference field, the execution result including at least one second reference field, the first and second reference fields for referencing corresponding metadata from the data center.

In one embodiment, the business event configuration module 902 includes:

In one embodiment, the service event includes a message event, and the service event configuration module 902 includes:

In one embodiment, the apparatus further comprises:

In one embodiment, the change condition is a mutually exclusive plurality.

In one embodiment, the list configuration module 901 is further configured to:

The functions of each module in each apparatus in the embodiments of the present invention may refer to the corresponding description in the above method, and are not described herein again.

Fig. 10 shows a block diagram of an electronic device according to an embodiment of the present invention. As shown in fig. 10, the electronic apparatus includes: a memory 1010 and a processor 1020, the memory 1010 having stored therein computer programs operable on the processor 1020. The processor 1020, when executing the computer program, implements the configuration method of the service event in the above-described embodiment. The number of the memory 1010 and the processor 1020 may be one or more.

The electronic device further includes:

and a communication interface 1030, configured to communicate with an external device, and perform data interactive transmission.

If the memory 1010, the processor 1020, and the communication interface 1030 are implemented independently, the memory 1010, the processor 1020, and the communication interface 1030 may be connected to each other through a bus and perform communication with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 10, but this is not intended to represent only one bus or type of bus.

Optionally, in a specific implementation, if the memory 1010, the processor 1020, and the communication interface 1030 are integrated on a chip, the memory 1010, the processor 1020, and the communication interface 1030 may complete communication with each other through an internal interface.

Embodiments of the present invention provide a computer-readable storage medium, which stores a computer program, and when the program is executed by a processor, the computer program implements the method provided in the embodiments of the present application.

The embodiment of the present application further provides a chip, where the chip includes a processor, and is configured to call and execute the instruction stored in the memory from the memory, so that the communication device in which the chip is installed executes the method provided in the embodiment of the present application.

An embodiment of the present application further provides a chip, including: the system comprises an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected through an internal connection path, the processor is used for executing codes in the memory, and when the codes are executed, the processor is used for executing the method provided by the embodiment of the application.

It should be understood that the processor may be a Central Processing Unit (CPU), other general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or any conventional processor or the like. It is noted that the processor may be an advanced reduced instruction set machine (ARM) architecture supported processor.

Further, optionally, the memory may include a read-only memory and a random access memory, and may further include a nonvolatile random access memory. The memory may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile memory may include a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can include Random Access Memory (RAM), which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available. For example, Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the present application are generated in whole or in part when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.

In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process. And the scope of the preferred embodiments of the present application includes other implementations in which functions may be performed out of the order shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved.

The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.

It should be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. All or part of the steps of the method of the above embodiments may be implemented by hardware that is configured to be instructed to perform the relevant steps by a program, which may be stored in a computer-readable storage medium, and which, when executed, includes one or a combination of the steps of the method embodiments.

In addition, functional units in the embodiments of the present application may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module may also be stored in a computer-readable storage medium if it is implemented in the form of a software functional module and sold or used as a separate product. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various changes or substitutions within the technical scope of the present application, and these should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for configuring a service event, comprising:

configuring an execution condition and an execution result of the business event aiming at any business event in the business event list; the execution condition includes a plurality of sub-conditions connected by logical operators, the sub-conditions including a first reference field, the execution result including at least one second reference field, the first and second reference fields for referencing corresponding metadata from a data center.

2. The method of claim 1, wherein configuring the execution condition of the service event comprises:

and configuring a first reference field, a comparison character, an insertion value and a reference value of the sub-condition aiming at any one of the sub-conditions, wherein the first reference field of the sub-condition is used for referencing corresponding metadata from a data center as the insertion value of the sub-condition, and the comparison character of the sub-condition is used for comparing the insertion value of the sub-condition and the reference value of the sub-condition.

3. The method of claim 1, wherein the service event comprises a message event, and wherein configuring the result of executing the service event comprises:

acquiring a preset insertion position in a message template of the message event;

4. The method of claim 1, wherein the first referenced field and/or the second referenced field comprises a multi-level field that matches a consanguinity relationship of metadata of the data center.

5. The method of claim 1, further comprising:

responding to a node change request, and configuring at least one change condition of a target service event corresponding to the node change request at a gateway branch node; and (c) a second step of,

and configuring a change result corresponding to each change condition, wherein the change result is used for changing the approver information corresponding to the target business event into target approver information under the condition that the change condition is met.

6. The method according to claim 5, wherein the change condition is a mutually exclusive plurality.

7. The method of claim 1, wherein configuring the list of traffic events at the flow node comprises:

8. An apparatus for configuring a business event, comprising:

a service event configuration module, configured to configure an execution condition and an execution result of the service event for any service event in the service event list; the execution condition includes a plurality of sub-conditions connected by logical operators, the sub-conditions including a first reference field, the execution result including at least one second reference field, the first and second reference fields for referencing corresponding metadata from a data center.

9. The apparatus of claim 8, wherein the service event configuration module comprises:

the first configuration sub-module is used for configuring a first reference field, a comparison character, an insertion value and a reference value of the sub-condition aiming at any one of the sub-conditions, the first reference field of the sub-condition is used for referencing corresponding metadata from a data center as the insertion value of the sub-condition, and the comparison character of the sub-condition is used for comparing the insertion value of the sub-condition with the reference value of the sub-condition.

10. The apparatus of claim 8, wherein the service event comprises a message event, and wherein the service event configuration module comprises:

the preset insertion position acquisition sub-module is used for acquiring a preset insertion position in a message template of the message event;

and the second configuration submodule is used for configuring a second reference field corresponding to the preset insertion position, and the second reference field is used for referencing the metadata of the data center as a variable value of the preset insertion position.

11. The apparatus of claim 8, wherein the first referenced field and/or the second referenced field comprises a multi-level field that matches a consanguinity relationship of metadata of the data center.

12. The apparatus of claim 8, further comprising:

the change condition configuration module is used for responding to the node change request and configuring at least one change condition of a target service event corresponding to the node change request at a gateway branch node; and the number of the first and second groups,

and the change result configuration module is used for configuring a change result corresponding to each change condition, and the change result is used for changing the approver information corresponding to the target business event into target approver information under the condition that the change condition is met.

13. The apparatus of claim 12, wherein the change condition is a mutually exclusive plurality.

14. The apparatus of claim 8, wherein the list configuration module is further configured to:

15. An electronic device, comprising: a processor and a memory, the memory having stored therein instructions that are loaded and executed by the processor to implement the method of any of claims 1 to 7.

16. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-7.