Verification method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a verification method and device, electronic equipment and a storage medium, and the verification method comprises the steps: determining a to-be-verified field in a to-be-processed flow chart and a to-be-verified attribute of the to-be-verified field according to the configuration information of the to-be-processed flow chart; determining a target verification mode according to the to-be-verified attribute of the to-be-verified field; and performing verification processing on the to-be-verified field according to the target verification mode to obtain a field verification result, and determining a verification result of the to-be-processed flow chart according to the field verification result. Therefore, the repeated verification configuration work can be reduced, and the verification efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a verification method, device, electronic device and storage medium. Background Art

[0002] At present, the application of IVR (Interactive Voice Response) technology is becoming more and more widespread. For example, when the number of human agents is limited, IVR technology can be used to provide self-service answering services for the questioning object, thereby reducing the workload of human agents and improving answering efficiency. Usually, the IVR answering service has a pre-designed IVR process, based on which an IVR flow chart describing the workflow of the IVR answering service can be generated. Summary of the invention

[0003] The embodiments of the present application provide a verification method, device, electronic device and storage medium, which can reduce repeated verification configuration work and improve verification efficiency.

[0004] In a first aspect, an embodiment of the present application provides a verification method, including:

[0005] Determine, according to the configuration information of the flowchart to be processed, the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked;

[0006] Determining a target verification method according to the to-be-verified attribute of the to-be-verified field;

[0007] The field to be checked is checked according to the target check method to obtain a field check result, and the check result of the flowchart to be processed is determined according to the field check result.

[0008] In a second aspect, an embodiment of the present application provides a verification device, including:

[0009] A determination unit, configured to determine, according to the configuration information of the flowchart to be processed, the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked;

[0010] The determining unit is further configured to determine a target verification mode according to the to-be-verified attribute of the to-be-verified field;

[0011] The verification unit is used to perform verification processing on the field to be verified according to the target verification method, obtain a field verification result, and determine the verification result of the flowchart to be processed according to the field verification result.

[0012] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor; and a memory configured to store computer-executable instructions, wherein the computer-executable instructions, when executed, cause the processor to perform the verification method described in the first aspect.

[0013] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium for storing computer-executable instructions, which, when executed by a processor, implement the verification method described in the first aspect.

[0014] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which implements the verification method described in the first aspect when executed by a processor.

[0015] It can be seen that in the embodiment of the present application, first, according to the configuration information of the flowchart to be processed, the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked are determined; then, according to the attributes to be checked of the fields to be checked, the target verification method is determined; finally, the fields to be checked are verified according to the target verification method to obtain the field verification result, and the verification result of the flowchart to be processed is determined according to the field verification result. In this way, considering that the flowchart to be processed may include multiple fields to be checked, each field to be checked may have some personalized characteristics, and it is difficult to verify all the fields to be checked by a unified verification method, by determining the target verification method according to the attributes to be checked of the fields to be checked, and verifying the fields to be checked according to the target verification method to obtain the field verification result, it is conducive to reusing some ready-made verification methods by configuring the attributes to be checked of the fields to be checked when processing the verification work of personalized fields to be checked. Compared with designing a corresponding personalized verification process for each field to be checked, repeated verification configuration work is reduced, and in the overall verification process of the flowchart to be processed, when processing each field to be checked in turn, there is no need to rely on manual experience to switch the verification method, thereby improving the verification efficiency of the flowchart to be processed. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor.

[0017] Figure 1 A schematic diagram of an implementation environment of a verification method provided in an embodiment of the present application;

[0018] Figure 2A processing flow chart of a verification method provided in an embodiment of the present application;

[0019] Figure 3 A first schematic diagram of a verification method applied to a call center provided in an embodiment of the present application;

[0020] Figure 4 A second schematic diagram of a verification method applied to a call center provided in an embodiment of the present application;

[0021] Figure 5 A processing flow chart of another verification method provided in an embodiment of the present application;

[0022] Figure 6 A node configuration page of a first node of the first type provided in an embodiment of the present application;

[0023] Figure 7 A node configuration page of the second first node provided in an embodiment of the present application;

[0024] Figure 8 A node configuration page of the third first node provided in an embodiment of the present application;

[0025] Fig. 9 A node configuration page of the fourth first node provided in an embodiment of the present application;

[0026] Fig.10 A process management interface provided for an embodiment of the present application;

[0027] Fig.11 A process variable management interface provided for an embodiment of the present application;

[0028] Fig.12 A speech management interface provided in an embodiment of the present application;

[0029] Fig.13 An audio management interface provided in an embodiment of the present application;

[0030] Fig.14 An interface management interface provided for an embodiment of the present application;

[0031] Fig.15 A language setting interface provided in an embodiment of the present application;

[0032] Fig.16 A flowchart of a first processing sub-process of a verification method provided in an embodiment of the present application;

[0033] Fig.17 A flowchart of a second processing sub-process of a verification method provided in an embodiment of the present application;

[0034] Fig.18 A flowchart of a third processing sub-process of a verification method provided in an embodiment of the present application;

[0035] Fig.19 A flowchart of a fourth processing sub-process of a verification method provided in an embodiment of the present application;

[0036] Fig. 20 A flowchart of the fifth processing sub-process of a verification method provided in an embodiment of the present application;

[0037] Fig.21 A flowchart of the sixth processing sub-process of a verification method provided in an embodiment of the present application;

[0038] Fig. 22 A flowchart of the seventh processing sub-process of a verification method provided in an embodiment of the present application;

[0039] Fig.23 A flowchart of an eighth processing sub-process of a verification method provided in an embodiment of the present application;

[0040] Fig.24 A flowchart of the ninth processing sub-process of a verification method provided in an embodiment of the present application;

[0041] Fig.25 The first data verification method provided in the embodiment of the present application;

[0042] Fig.26 The second data verification method provided in the embodiment of the present application;

[0043] Fig. 27 The third data verification method provided in the embodiment of the present application;

[0044] Fig.28 The fourth data verification method provided in the embodiment of the present application;

[0045] Fig.29 The fifth data verification method provided in the embodiment of the present application;

[0046] Fig.30 The sixth data verification method provided in the embodiment of the present application;

[0047] Fig.31 The seventh data verification method provided in the embodiment of the present application;

[0048] Fig.32 The eighth data verification method provided in the embodiment of the present application;

[0049] Fig.33 The ninth data verification method provided in the embodiment of the present application;

[0050] Fig.34 The tenth data verification method provided in the embodiment of the present application;

[0051] Fig.35 A schematic diagram of a verification device provided in an embodiment of the present application;

[0052] Fig.36 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0054] This specification provides a verification method embodiment:

[0055] Before any service described by a flowchart is officially put into use, it is often necessary to perform a verification first to detect possible problems with each diagram element and prompt the user to modify it. Considering that each diagram element has different data content and may have unique personality, it is impossible to use a unified verification method to batch process diagram elements. For this reason, it is often necessary to design a personalized verification process for the diagram element before verification.

[0056] In the actual production environment, there are not just one or two flowcharts waiting to be verified, but a huge number of flowcharts. Different flowcharts may have different data contents, but because they describe the same type of service, in different flowcharts, under the premise that the overall flowchart is not completely consistent, there may be diagram elements with the same or similar content. The more flowcharts are processed, the higher the possibility of duplication. Therefore, when users design personalized verification processes for each diagram element in each flowchart, there is a high probability that a large amount of repeated verification configuration work will occur, which is inefficient.

[0057] If you want to reuse the existing data verification methods in order to save configuration time, you may need to rely on manual experience to switch back and forth between the various data verification methods, which makes the verification efficiency of the flowchart to be processed low.

[0058] Therefore, in order to solve the above problems, an embodiment of the present application provides a verification method.

[0059] The verification method provided in one or more embodiments of this specification may be applicable to the implementation environment of the verification method, such as Figure 1 As shown, the implementation environment at least includes a server 101 for verifying the flowchart to be processed.

[0060] The server 101 may be a single server, or a server cluster consisting of a plurality of servers, or one or more cloud servers in a cloud computing platform, for verifying the flowchart to be processed.

[0061] In this implementation environment, during the process of verifying the flowchart to be processed, the server 101 first determines the fields to be verified in the flowchart to be processed and the attributes to be verified of the fields to be verified according to the configuration information of the flowchart to be processed; then, according to the attributes to be verified of the fields to be verified, the target verification method is determined; finally, the fields to be verified are verified according to the target verification method to obtain the field verification result, and the verification result of the flowchart to be processed is determined according to the field verification result. Therefore, considering that the flowchart to be processed may include multiple fields to be checked, each field to be checked may have some personalized characteristics, and it is difficult to verify all the fields to be checked through a unified verification method, the target verification method is determined according to the attributes to be checked of the field to be checked, and the field to be checked is verified according to the target verification method to obtain the field verification result, which is conducive to reusing some ready-made verification methods by configuring the attributes to be checked of the field to be checked when processing the verification work of the personalized field to be checked. Compared with designing a corresponding personalized verification process for each field to be checked, the repeated verification configuration work is reduced, and in the overall verification process of the flowchart to be processed, when processing each field to be checked in turn, there is no need to rely on manual experience to switch the verification method, thereby improving the verification efficiency of the flowchart to be processed.

[0062] Figure 2 A processing flow chart of a verification method provided in an embodiment of the present application. Figure 2 The verification method provided in this embodiment specifically includes steps S202 to S206:

[0063] Step S202: Determine the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked according to the configuration information of the flowchart to be processed.

[0064] The flowchart to be processed may be a flowchart describing the workflow of the target service.

[0065] The flowchart to be processed may be a flowchart with verification requirements. For example, after the target service configuration is completed and before the target service is officially put into use, the flowchart to be processed needs to be verified to find out the problems in the configuration information and prompt the user to modify them in time.

[0066] A flowchart is a graphical representation method used to show the steps, decision points, and process sequence in a process or system. It uses different symbols and connecting lines to represent the relationship between the steps, making complex processes intuitive and easy to understand. Flowcharts are often used in business process analysis, software design, project management and other fields to help people better understand and optimize workflows.

[0067] The workflow of the target service may be pre-configured by the service provider of the target service. After the configuration of the workflow is completed, a corresponding flowchart, ie, a flowchart to be processed, may be generated based on the workflow.

[0068] The target service may be any service that can provide a specific function or solve a specific problem. For example, the target service may be an IVR service, a transaction service, a resource lending service, and the like.

[0069] The configuration information of the flowchart to be processed may include one or more configuration parameters to be verified, wherein each configuration parameter may be represented by a corresponding field to be verified. That is, the field to be verified may represent the configuration parameter to be verified in the configuration information of the flowchart to be processed.

[0070] In a flowchart, configuration parameters usually refer to specific parameters or options that need to be set in a node or step of the process. These parameters are used to guide the execution of the process and ensure that the process can run according to the expected logic and rules. The parameter value of a configuration parameter can be a number, string, Boolean value, or other type of data, depending on the needs of the process.

[0071] For example, the configuration information of the IVR flowchart includes the following configuration parameters: allowed input keys, speech, timeout period, etc.

[0072] Among them, the field to be checked 1 can be used to represent the configuration parameter "keys allowed to be input", the field to be checked 2 can be used to represent the configuration parameter "speech", and the field to be checked 3 can be used to represent the configuration parameter "timeout period".

[0073] In some implementations, the configuration information of the flowchart to be processed includes one field, and the field needs to be verified. Alternatively, the configuration information of the flowchart to be processed includes N fields, and the N fields all need to be verified. N is an integer greater than 1.

[0074] Determining the fields to be checked in the flowchart to be processed may include obtaining configuration information of the flowchart to be processed and determining the fields in the configuration information as the fields to be checked.

[0075] In some other implementations, the configuration information of the flowchart to be processed includes multiple fields, among which one or more fields are pre-marked with a designated identification mark to be checked.

[0076] In other implementations, determining the fields to be checked in the flowchart to be processed may be to obtain multiple fields in the configuration information of the flowchart to be processed, and determine the fields to be checked that participate in the check in the multiple fields according to the identification to be checked.

[0077] In other implementations, before executing step S202, the configuration information of the graph element in the flowchart to be processed may also be obtained. Further, the fields to be checked in the flowchart to be processed may be determined by determining the fields to be checked in the configuration information of the graph element. The graph element may be a node, an edge, or other pre-designed graphic symbol, etc.

[0078] The flowchart to be processed may include one or more nodes and may also include one or more edges. If the graph element in the flowchart to be processed includes a first node, obtaining the configuration information of the graph element may be obtaining the node configuration information of the first node. The node configuration information may be data generated by pre-configuration processing for the first node. If the graph element in the flowchart to be processed includes a first edge, obtaining the configuration information of the graph element may be obtaining the edge configuration information of the first edge. The edge configuration information may be data generated by pre-configuration processing for the first edge. The configuration information of other graphic symbols can refer to the node configuration information and the edge configuration information, which will not be repeated here.

[0079] In this specification, ordinal numbers such as "first" and "second" are used to distinguish different technical features and have no actual meaning, and will not be elaborated below.

[0080] When the flowchart to be processed includes multiple first nodes, the node types of any two of the first nodes may be the same or different. Similarly, when the flowchart to be processed includes multiple first edges, the edge types of any two of the first edges may be the same or different.

[0081] For each first node, the node type of the first node may be one of a set of preset node types. Similarly, for each first edge, the edge type of the first edge may be one of a set of preset edge types.

[0082] For example, the preset node type set includes node type 1, node type 2, node type 3, and node type 4. The preset edge type set includes edge type 1 and edge type 2. The flowchart to be processed is IVR flowchart A, which includes 3 first nodes: node 1, node 2, node 3, and the IVR flowchart A also includes 2 first edges: edge 1 and edge 2. Among them, node 1 belongs to node type 1, node 2 belongs to node type 3, and node 3 belongs to node type 3. Edge 1 belongs to edge type 1, and edge 2 belongs to edge type 2.

[0083] Next, we take the target service, which is the IVR service, as an example to illustrate the diagram elements in the flowchart to be processed:

[0084] The flowchart to be processed may be an IVR flowchart, which may include multiple nodes. Among the multiple nodes, one node may be used to indicate that a call is connected, one or more nodes may be used to indicate instructions received during a call, one or more nodes may be used to indicate that a service is terminated and the call may be terminated, etc. The instructions received during a call may carry key input information or voice input information.

[0085] The IVR flowchart may also include edges between nodes, each edge being used to represent a corresponding processing flow. The processing flow may be to broadcast a pre-recorded guidance voice, or to provide a specified sub-service to the user, or to broadcast a guidance voice and provide a specified sub-service, etc. The edges in the IVR flowchart may be directed edges. For example, the two nodes connected by edge 1 are node 1 and node 2, and the direction of edge 1 is from node 1 to node 2, then node 1 is said to be adjacent to node 2, and node 1 is located before node 2.

[0086] For another example, node 1 is connected to node 2 through edge 1, and the direction of edge 1 is from node 1 to node 2; node 2 is connected to node 3 through edge 2, and the direction of edge 2 is from node 2 to node 3. Then node 1 is said to be adjacent to node 2, node 2 is adjacent to node 3, node 1 is not adjacent to node 3, and node 1 is located before node 2, node 1 is located before node 3, and node 2 is located before node 3.

[0087] Next, we take the target service as a transaction service as an example to illustrate the following in the process flow chart:

[0088] The process flow chart to be processed may be a transaction process flow chart, which may include multiple nodes. Among the multiple nodes, one or more nodes may be used to provide a product search function, one or more nodes may be used to provide an order establishment function, one or more nodes may be used to provide a payment function, one or more nodes may be used to provide a transaction evaluation generation function, and so on.

[0089] The IVR flow chart may also include edges between nodes, each edge being used to represent a corresponding page jump process. The page jump process may be jumping from a product search page to a display page of a selected target product, from an order page to a payment page, from a payment page to a transaction evaluation page, and so on.

[0090] For any service, in the flowchart describing the workflow of the service, for each diagram element, the diagram element can be pre-configured according to the personalized needs of the service. Due to similar technical concepts, the pending flowcharts describing the workflow of other services can refer to the corresponding description parts of the IVR service or transaction service.

[0091] After the fields to be checked that participate in the check are determined in the configuration information of the graph element, the attributes to be checked of the fields to be checked can be obtained; each attribute to be checked is one of the preset attribute sets.

[0092] The flowchart to be processed may include one or more graph elements. For each graph element, the configuration information of the graph element may include one or more fields to be checked, and may also include attributes to be checked for each field to be checked. Each field to be checked may have one or more attributes to be checked.

[0093] Each field to be checked can represent a configuration parameter. The reason why each field to be checked can have multiple attributes to be checked is that, for the same configuration parameter, the data type of the parameter value of the configuration parameter can be checked, the numerical range of the parameter value of the configuration parameter can be checked, whether the parameter value of the configuration parameter is empty can be checked, etc. Therefore, the target sub-segment can have a variety of attributes to be checked. In this embodiment, each field to be checked has one attribute to be checked as an example for exemplary description. In the case where the field to be checked has multiple attributes to be checked, the corresponding description part of the field to be checked having one attribute to be checked can be referred to.

[0094] Multiple fields to be checked of the same graph element may have the same attribute to be checked or different attributes to be checked. Multiple fields to be checked of different graph elements may have the same attribute to be checked or different attributes to be checked.

[0095] In contrast, when the preset attribute set includes multiple attributes, for any one of the attributes, the attribute may not be used by any field to be checked, may be used by one field to be checked, may be reused by multiple fields to be checked of the same graph element, may be reused by multiple fields to be checked of different graph elements, and so on.

[0096] In some implementations, the configuration information of the graph element includes a field to be checked, and the field to be checked needs to participate in the check. Alternatively, the configuration information of the graph element includes N fields to be checked, and the N fields to be checked need to participate in the check.

[0097] In other implementations, the configuration information of the graphic element includes multiple fields, among which one or more fields are pre-marked with a designated identification to be verified. Furthermore, after obtaining the configuration information of the graphic element, the fields to be verified that participate in the verification can be determined from the multiple fields based on the identification to be verified.

[0098] The preset attribute set may include multiple attributes, each of which may describe the characteristics of the graph element from an angle corresponding to the attribute. The flowchart to be processed is an IVR flowchart for exemplary description:

[0099] The preset attribute set may include: working time attribute, process attribute, speech attribute, input attribute, process variable attribute, etc. Working time attribute may be reflected in the configuration information describing the characteristics of the diagram element from the "time perspective", process attribute may be reflected in the configuration information describing the characteristics of the diagram element from the "process perspective", and so on.

[0100] Process variables refer to the parameters in the entire IVR process operation, which can be the user's call information, the identification information obtained by query, or the information entered by the user.

[0101] The IVR flow chart includes multiple first nodes, and the node configuration information of each first node includes one or more fields to be verified, wherein the attributes to be verified of each field to be verified are one of the following: working time attributes, process attributes, speech attributes, input attributes, process variable attributes, etc.

[0102] By determining the attribute to be checked of the field to be checked in the configuration information of the graph element, multiple fields to be checked of the same graph element can reuse the same attribute, and multiple fields to be checked of different graph elements can also reuse the same attribute.

[0103] Step S204, determining a target verification method according to the to-be-verified attribute of the to-be-verified field.

[0104] The number of target verification methods may be one or more. In the case where the number of target verification methods is more than one, the execution order of the multiple target verification methods may be determined by the priority order pre-configured for each target verification method. The target verification method may be determined based on the attributes to be verified of the field to be verified, and the verification method corresponding to the attributes to be verified may be used as the target verification method.

[0105] In specific implementation, the data verification method of the attribute to be verified of the field to be verified can be queried in the preset correspondence set according to the attribute to be verified of the field to be verified, and the target verification method can be obtained; the preset correspondence set includes: for each attribute in the preset attribute set, the correspondence between the attribute and at least one data verification method.

[0106] The preset attribute set may include one or more attributes. For each attribute, the attribute may correspond to one data verification method, or may correspond to multiple data verification methods.

[0107] For example, the preset attribute set includes attribute 1, attribute 2, and attribute 3. The preset correspondence set includes: the correspondence between attribute 1 and data verification mode 1, the correspondence between attribute 1 and data verification mode 2; the correspondence between attribute 2 and data verification mode 1; the correspondence between attribute 3 and data verification mode 1, and the correspondence between attribute 3 and data verification mode 3.

[0108] Each data verification method may be one of a set of preset data verification methods. The specific implementation process of each data verification method may be preconfigured. Different attributes may reuse the same data verification method in the set of preset data verification methods.

[0109] The flowchart to be processed is an IVR flowchart for exemplary description:

[0110] The preset attribute set may include: working time attribute, process attribute, speech attribute, input attribute, process variable attribute, etc. Working time attribute may be reflected in the configuration information describing the characteristics of the diagram element from the "time perspective", process attribute may be reflected in the configuration information describing the characteristics of the diagram element from the "process perspective", and so on.

[0111] In contrast, the preset data verification method set may include: working time usage verification, process usage verification, speech usage verification, non-empty verification, process variable usage verification, and so on.

[0112] The preset correspondence set includes:

[0113] (a1) Correspondence between working time attributes and working time usage verification 1;

[0114] (a2) Correspondence between working time attribute and non-empty check 2;

[0115] (a3) Correspondence between process attributes and process usage verification 3;

[0116] (a4) Correspondence between process attributes and non-empty checks 4;

[0117] (a5) Correspondence between speech attributes and speech usage verification 5;

[0118] (a6) Correspondence between speech attributes and non-empty check 6;

[0119] (a7) Correspondence between input attributes and non-empty check 7;

[0120] (a8) Correspondence between process variable attributes and non-empty check 8;

[0121] (a9) The correspondence between process variable attributes and process variable usage verification 9, and so on.

[0122] According to the attributes to be checked of the field to be checked, the data verification method of the attributes to be checked of the field to be checked is queried in the preset corresponding relationship set to obtain the target verification method. It can be that according to the attributes to be checked of the field to be checked, one or more data verification methods corresponding to the attributes to be checked of the field to be checked are queried in the preset corresponding relationship set, and the data verification method obtained by the query is used as the target verification method.

[0123] According to the attributes to be verified of the field to be verified, the data verification method of the attributes to be verified of the field to be verified is queried in the preset corresponding relationship set to obtain the target verification method. Alternatively, according to the attributes to be verified of the field to be verified, one or more data verification methods corresponding to the attributes to be verified of the field to be verified are queried in the preset corresponding relationship set. When the number of data verification methods obtained by the query is greater than the preset number threshold, according to the preset priority order of various data verification methods, the first number of data verification methods are selected as the target verification method from the data verification methods obtained by the query. The first number can be an integer greater than zero and can be customized.

[0124] The target verification method is determined according to the to-be-verified attribute of the to-be-verified field, and a random number may be generated within a preset numerical range, and the target verification method is determined from candidate verification methods of the to-be-verified attribute according to the random number.

[0125] For each attribute to be verified, multiple candidate verification methods corresponding to the attribute to be verified with the same verification purpose but different verification means can be pre-configured. The candidate verification methods corresponding to the same attribute to be verified can replace each other.

[0126] For example, the attribute to be checked is the first attribute, and the purpose of checking the first attribute is to check whether the numerical range of the field value of the field to be checked is within the first numerical range. The candidate verification method 1 corresponding to the first attribute is to achieve the verification purpose by detecting the verification means for the configuration information of the numerical range, and the candidate verification method 2 corresponding to the first attribute is to achieve the verification purpose by inputting multiple numerical values ​​outside the first numerical range.

[0127] For another example, the attribute to be checked is the second attribute, and the purpose of checking the second attribute is to check whether the first parameter and the second parameter corresponding to the field to be checked can be used as comparison objects. The candidate check method 1 corresponding to the second attribute is to compare the first parameter and the second parameter by calling the comparison technology provided by the first interface to achieve the check purpose. The candidate check method 2 corresponding to the second attribute is to compare the first parameter and the second parameter by calling the comparison technology provided by the second interface to achieve the check purpose. The comparison technology provided by the first interface and the comparison technology provided by the second interface respectively adopt different algorithms.

[0128] Taking into account that different flowcharts have their own characteristics, the fact that the same verification method performs well in the verification process of a part of the flowcharts does not mean that the verification method is very accurate in the verification process of all flowcharts. The performance of the same verification method in the verification process of different flowcharts may be different. Compared with adopting a fixed verification method, randomly determining the target verification method from multiple candidate verification methods with the same verification purpose and different verification methods is more conducive to finding abnormal fields to be verified.

[0129] Step S206, verify the field to be verified according to the target verification method to obtain the field verification result, and determine the verification result of the flowchart to be processed according to the field verification result.

[0130] The number of target verification methods can be one or more. When there are more than one target verification methods, the field to be verified is verified by each target verification method to obtain the check sub-result of each target verification method, and then the field verification result of the field to be verified is determined according to each check sub-result.

[0131] The verification result of the flowchart to be processed can be determined based on the field verification results of each field to be verified in the flowchart to be processed. Specifically, if the field verification results of each field to be verified in the flowchart to be processed are all verified, it can be determined that the verification result of the flowchart to be processed is verified; if the field verification result of at least one field to be verified in the flowchart to be processed is verified failed, it can be determined that the verification result of the flowchart to be processed is verified failed.

[0132] When the verification result of the flowchart to be processed is verification failure, a prompt information can be generated, which includes the field to be checked whose field verification result is verification failure, and is used to prompt the user to update the configuration information of the flowchart to be processed for the field to be checked that failed the verification.

[0133] In a specific implementation method, when the target verification method includes a first verification method, the field verification result includes a first verification result, and the field to be verified is verified according to the target verification method to obtain a field verification result, including: according to the field to be verified, determining a first data identifier representing the input and output parameter data and a first variable identifier for the first variable for the field to be verified in the configuration information of the flow chart to be processed; according to the first data identifier, querying the data type of the input and output parameter data in the correspondence between the pre-configured data identifier and the data type, and, according to the first variable identifier, querying the data type of the first variable in the correspondence between the pre-configured variable identifier and the data type; comparing the data type of the input and output parameter data with the data type of the first variable to obtain a first comparison result; and determining a first verification result of verifying the field to be verified by the first verification method according to the first comparison result.

[0134] The first verification method can be used to determine whether the data type of the input and output parameter data is the same as the data type of the first variable corresponding to the field to be verified. For example, if the data type of the input and output parameter data is an integer and the data type of the first variable is an integer, then the data type of the input and output parameter data is the same as the data type of the first variable corresponding to the field to be verified. For another example, if the data type of the input and output parameter data is a string and the data type of the first variable is a floating point number, then the data type of the input and output parameter data is not the same as the data type of the first variable corresponding to the field to be verified.

[0135] Taking into account that the target verification method is determined according to the attributes to be verified of the field to be verified, when the target verification method includes the first verification method, it means that there is a corresponding relationship between the attributes to be verified of the field to be verified and the first verification method, and the field to be verified can be used as index information. In the configuration information of the flow chart to be processed, the first data identifier representing the input and output parameter data and the first variable identifier of the first variable corresponding to the field to be verified can be determined through the index information.

[0136] The configuration information of the flowchart to be processed may include the correspondence between pre-configured data identifiers and data types, and may also include the correspondence between pre-configured variable identifiers and data types.

[0137] According to the first data identifier, query processing can be performed in the correspondence between the pre-configured data identifier and the data type to obtain the data type of the input and output parameter data.

[0138] Input and output parameter data include input parameter data and output parameter data. Input parameter refers to the parameters that need to be passed in a function or method, and output parameter refers to the value returned by the function or method from the running result.

[0139] For each output parameter data or input parameter data, a data identifier representing the output parameter data or input parameter data can be pre-configured, and then, using the data identifier, the attribute information of the output parameter data or input parameter data can be queried in the configuration information of the flowchart to be processed.

[0140] Each output parameter data or input parameter data may have one or more types of attribute information, and each attribute information describes a feature of the output parameter data or input parameter data at an angle corresponding to the attribute information.

[0141] For example, the attribute information of each input parameter data may include the data type, data size, applicable scope, etc. of the variable.

[0142] According to the first variable identifier, query processing can be performed in the pre-configured correspondence between the variable identifier and the data type to obtain the data type of the first variable.

[0143] For each variable, a variable identifier representing the variable may be pre-configured, and then, using the variable identifier, the attribute information of the variable may be queried in the configuration information of the flowchart to be processed.

[0144] Each variable may have one or more types of attribute information, and each attribute information describes a feature of the variable at an angle corresponding to the attribute information.

[0145] For example, the attribute information of each variable may include the data type, data size, applicable scope, etc. of the variable.

[0146] A comparison is performed based on the data type of the input and output parameter data and the data type of the first variable to obtain a first comparison result.

[0147] There may be two types of first comparison results: one first comparison result indicates that the data type of the input parameter data is the same as the data type of the first variable, and the other first comparison result indicates that the data type of the input parameter data is different from the data type of the first variable.

[0148] If the first comparison result indicates that the data type of the input and output parameter data is the same as the data type of the first variable, it is determined that the first verification result of the field to be verified by the first verification method is that the verification passed.

[0149] If the first comparison result indicates that the data type of the input parameter data is different from the data type of the first variable, it is determined that the first verification result of the field to be verified by the first verification method is verification failure.

[0150] In a specific implementation method, when the target verification method includes the second verification method, the field verification result includes the second verification result, and the field to be verified is verified according to the target verification method to obtain the field verification result, including: according to the field to be verified, determining the second variable identifier of the second variable located at both ends of the preset type symbol and the third variable identifier of the third variable in the configuration information of the flowchart to be processed; according to the second variable identifier, querying the data type of the second variable in the correspondence between the pre-configured variable identifier and the data type, and, according to the third variable identifier, querying the data type of the third variable in the correspondence between the variable identifier and the data type; comparing the data type of the second variable with the data type of the third variable to obtain a second comparison result; and determining the second verification result of the field to be verified by the second verification method according to the second comparison result.

[0151] The preset type symbol may include comparison symbols, for example, "=", "<", ">", etc. The preset type symbol may also include an assignment symbol "=".

[0152] Taking into account that the target verification method is determined according to the attributes to be verified of the field to be verified, when the target verification method includes a second verification method, it means that there is a corresponding relationship between the attributes to be verified of the field to be verified and the second verification method, and the field to be verified can be used as index information. In the configuration information of the flowchart to be processed, the second variable identifier of the second variable and the third variable identifier of the third variable located at both ends of the preset type symbol can be determined through the index information.

[0153] The configuration information of the flowchart to be processed may include a correspondence between pre-configured variable identifiers and data types.

[0154] According to the second variable identifier, query processing is performed in the correspondence between the pre-configured variable identifier and the data type to obtain the data type of the second variable, and, according to the third variable identifier, query processing is performed in the correspondence between the variable identifier and the data type to obtain the data type of the third variable.

[0155] For each variable, a variable identifier representing the variable may be pre-configured, and then, using the variable identifier, the attribute information of the variable may be queried in the configuration information of the flowchart to be processed.

[0156] Each variable may have one or more types of attribute information, and each attribute information describes a feature of the variable at an angle corresponding to the attribute information.

[0157] For example, the attribute information of each variable may include the data type, data size, applicable scope, etc. of the variable.

[0158] A comparison process is performed based on the data type of the second variable and the data type of the third variable to obtain a second comparison result.

[0159] There may be two types of second comparison results: one second comparison result indicates that the data type of the second variable is the same as the data type of the third variable, and the other second comparison result indicates that the data type of the second variable is different from the data type of the third variable.

[0160] If the second comparison result indicates that the data type of the second variable is the same as the data type of the third variable, it is determined that the second verification result of the field to be verified by the second verification method is verification passed.

[0161] If the second comparison result indicates that the data type of the second variable is different from the data type of the third variable, it is determined that the second verification result of the field to be verified by the second verification method is verification failure.

[0162] In a specific implementation method, when the target verification method includes a third verification method, the field verification result includes the third verification result, and the verification process is performed on the field to be verified according to the target verification method to obtain the field verification result, including: obtaining the target speech identifier of the field to be verified; verifying whether the speech synthesis parameters of the target speech identifier exist to obtain a first verification sub-result; verifying whether the audio data of the target speech identifier is uploaded to obtain a second verification sub-result; and determining the third verification result of the field to be verified by the third verification method based on the first verification sub-result and the second verification sub-result.

[0163] Taking into account that the target verification method is determined according to the attributes to be verified of the field to be verified, when the target verification method includes a third verification method, it means that there is a corresponding relationship between the attributes to be verified of the field to be verified and the third verification method, and the field to be verified can be used as index information. The target speech identifier of the field to be verified can be determined through the index information in the configuration information of the flowchart to be processed.

[0164] In specific implementation, a speech set may be preconfigured, the speech set including multiple speech sets, each speech having a unique speech identifier, each speech having corresponding speech synthesis parameters, and each speech having corresponding audio data.

[0165] Verifying whether the speech synthesis parameters of the target speech identification exist and obtaining the first check sub-result may be to determine whether the speech synthesis parameters of the speech corresponding to the target speech identification have been configured according to the target speech identification. If it is determined that the speech synthesis parameters have been configured, it means that the first check sub-result indicates that the verification has passed; if it is determined that the speech synthesis parameters have not been configured, it means that the first check sub-result indicates that the verification has not passed.

[0166] Verify whether the audio data of the target speech identifier has been uploaded and obtain the second verification sub-result. It can be based on the target speech identifier to determine whether the audio data of the speech corresponding to the target speech identifier has been uploaded. If it is determined that the audio data has been uploaded, it means that the second verification sub-result indicates that the verification has passed; if it is determined that the audio data has not been uploaded, it means that the second verification sub-result indicates that the verification has failed.

[0167] When the first syndrome result indicates that the verification is passed, and the second syndrome result indicates that the verification is passed, it can be determined that the third verification result indicates that the verification is passed.

[0168] In a case where the first syndrome result indicates that the verification has passed and the second syndrome result indicates that the verification has not passed, it may be determined that the third verification result indicates that the verification has passed.

[0169] In the case where the first syndrome result indicates that the verification has failed, and the second syndrome result indicates that the verification has passed, it may be determined that the third verification result indicates that the verification has passed.

[0170] In the case where the first syndrome result represents that the verification has not been passed and the second syndrome result represents that the verification has not been passed, it can be determined that the third verification result represents that the verification has not been passed.

[0171] In a specific implementation, the flowchart to be processed includes a first node; the verification method also includes: determining the node type of each first node based on a preset node type set; for each first node, determining an input and output parameter verification method suitable for the first node based on the node type of the first node; verifying the first node according to the input and output parameter verification method to obtain a node verification result; determining the verification result of the flowchart to be processed based on the field verification result, including: determining the verification result of the flowchart to be processed based on the node verification result and the field verification result.

[0172] The first node may be any node in the process flow chart to be processed. The node type of the first node may be one of the following node types: a start node, an end node, an on-hook node, an intermediate node, and the like.

[0173] For each node type, you can pre-configure the input and output parameter verification method corresponding to the node type.

[0174] For example, the input and output parameter verification methods corresponding to each node type are as follows:

[0175] The node type of the first node may be a start node, and a suitable input and output parameter verification method for the first node is: verify whether the first node satisfies simultaneously: there is no input parameter, and there is one and only one output parameter.

[0176] The node type of the first node may be an end node, and a suitable input and output parameter verification method for the first node is: verifying whether the first node simultaneously satisfies: having input parameters and having no output parameters.

[0177] The node type of the first node may be an idle node, and a suitable input and output parameter verification method for the first node is: verifying whether the first node simultaneously satisfies: having input parameters and having no output parameters.

[0178] The node type of the first node may be an intermediate node. Then, the input and output parameter verification method suitable for the first node is: verify whether the first node satisfies one of the following two conditions: (1) there is at least one input parameter, only one output parameter, and no connection condition of the first node is configured; (2) there is at least one input parameter, N output parameters, and N connection conditions of the first node are configured. N is an integer greater than 1.

[0179] The connection condition can be understood as: for each first node, when the connection condition of the first node is met, the first node can be connected to another first node pointed to by the connection condition through an edge.

[0180] For example, when [X] = [Y], node A points to node B, then "[X] = [Y]" is the connection condition.

[0181] The input and output parameter verification method for each node type listed above is an example to facilitate understanding of the present implementation method. In actual applications, the input and output parameter verification method applicable to each node type of the flowchart to be processed can be configured according to the connection relationship between the first nodes in the flowchart to be processed.

[0182] The first node is verified according to the input and output parameter verification method to obtain a node verification result of the first node.

[0183] There are two types of node verification results for the first node: one indicating that the verification has passed, and the other indicating that the verification has not passed.

[0184] When it is determined that the node verification result of the first node indicates that the verification has failed, the verification operation record of the first node may be analyzed and processed to obtain analysis data of the first node, and the analysis data may be used to determine the reason why the verification of the first node has failed.

[0185] For example, the node type of the first node is a start node, and the input and output parameter verification method suitable for the first node is: verify whether the first node simultaneously satisfies: there is no input parameter, and there is one and only one output parameter.

[0186] The first node is verified according to the input and output parameter verification method to obtain a node verification result, which can be to verify whether the input parameter of the first node exists, to verify whether the output parameter of the first node exists, and, if it is determined that the output parameter of the first node exists, then to verify whether the output parameter quantity of the first node is one.

[0187] If it is determined through verification that the input parameter of the first node exists, and it is determined through verification that the output parameter of the first node exists and the number is one, then it can be determined that the node verification result of the first node is verification failure;

[0188] If it is determined through verification that the input parameter of the first node exists, and it is determined through verification that the output parameter of the first node exists and the number is multiple, then it can be determined that the node verification result of the first node is verification failure;

[0189] If it is determined through verification that the input parameter of the first node exists, and it is determined through verification that the output parameter of the first node does not exist, then it can be determined that the node verification result of the first node is verification failure;

[0190] If it is determined through verification that the input parameter of the first node does not exist, and it is determined through verification that the output parameter of the first node exists and the number is one, then it can be determined that the node verification result of the first node is verification passed;

[0191] If it is determined through verification that the input parameter of the first node does not exist, and it is determined through verification that the output parameter of the first node exists and the number is multiple, then it can be determined that the node verification result of the first node is verification failure;

[0192] If it is determined through verification that the input parameter of the first node does not exist, and it is determined through verification that the output parameter of the first node does not exist, then it can be determined that the node verification result of the first node is verification failure.

[0193] For another example, the flowchart to be processed includes node 1 and node 2, and node 1 points to node 2. The node type of node 1 is a start node, and the node type of node 2 is an end node.

[0194] The start node has no input parameter, and the start node has one and only one output parameter. No node in the flowchart to be processed points to node 1, and node 1 in the flowchart to be processed only points to a node other than node 1.

[0195] If it is confirmed through verification that node 1 has input parameters, it means that there is an abnormal connection between node 1 in the flowchart to be processed and another node outside node 1 in the flowchart to be processed. The other node incorrectly transmits the output parameter data to node 1, which conflicts with the data processing flow described in the flowchart to be processed, and an error is reported. Further investigation is needed to investigate why there are extra input parameters.

[0196] If it is confirmed after verification that node 1 has no output parameters, it means that there is a problem with the connection between node 1 and node 2, and an error is reported. Further investigation is needed to find out why the output parameters are missing.

[0197] The end node has no outgoing parameters, and the end node has incoming parameters. Node 2 in the pending flow chart does not point to any node, and node 1 in the pending flow chart points to node 2.

[0198] If it is confirmed after verification that node 2 has output parameters, it means that there is a problem with the configuration information of node 2. The process should have ended at node 2, but it output unexpected parameter data. An error is reported and the cause is analyzed.

[0199] If it is confirmed after verification that node 2 has no input parameters, it means that there is a problem with the connection between node 1 and node 2, resulting in the output parameter data output by node 1 not reaching node 2 smoothly. An error is reported and the cause is analyzed.

[0200] Each first node in the flowchart to be processed needs to undergo an input and output parameter verification in combination with the node type of each first node. When the node verification results of each first node are all verified to pass, the data processing process corresponding to the flowchart to be processed can proceed smoothly according to the data flow in the flowchart to be processed.

[0201] The verification result of the flowchart to be processed is determined based on the node verification result and the field verification result.

[0202] If the node verification results of each first node are all verified to be passed, and the field verification results of each field to be verified are all verified to be passed, it can be determined that the verification result of the flowchart to be processed is verified to be passed.

[0203] If the node verification result of at least one first node is verification failed, and the field verification results of each field to be verified are verification passed, it can be determined that the verification result of the flowchart to be processed is verification failed.

[0204] If the node verification results of each first node are all verified, and the field verification result of at least one field to be verified is verified failed, it can be determined that the verification result of the flowchart to be processed is verified failed.

[0205] If the node check result of at least one first node is check failure, and the field check result of at least one field to be checked is check failure, it can be determined that the check result of the flowchart to be processed is check failure.

[0206] In a specific implementation, the verification method also includes: determining the risk level of the field to be verified in the configuration information of the flowchart to be processed to obtain the target risk level; verifying the field to be verified according to the target verification method, and after obtaining the field verification result, the verification method also includes: if the field verification result indicates that the verification of the field to be verified has failed, then generating risk control prompt information that meets the target risk level.

[0207] For each field to be checked, a risk level of the field to be checked, ie, a target risk level, may be preconfigured.

[0208] The risk level can reflect the degree of impact on the normal operation of the target service described in the processing flowchart when the verification of the field to be verified fails.

[0209] If the field verification result indicates that the verification of the field to be verified has failed, a risk control prompt message that meets the target risk level is generated.

[0210] For each risk level, a corresponding speech template can be pre-configured.

[0211] To generate risk control prompt information that meets the target risk level, the characteristic data of the field to be checked can be determined in the configuration information of the graph element based on the field to be checked, and the speech template corresponding to the target risk level is filled in according to the characteristic data to obtain the risk control prompt information that meets the target risk level.

[0212] For example, the first level is higher than the second level, and the second level is higher than the third level.

[0213] The risk level is the first level, which means that if the verification fails, the target service of the flowchart to be processed cannot run smoothly without changing it. That is, if the verification fails, the field to be verified may bring greater risks to the use of the target service corresponding to the flowchart to be processed. The prompt information needs to emphasize to the user that it must be modified.

[0214] The risk level is the second level, which means that if the verification fails, not changing the flowchart to be processed may lead to a poor user experience, but the target service can still run. That is, if the verification fails, the field to be verified may bring a medium risk to the use of the target service corresponding to the flowchart to be processed, so the prompt message reminds the user to pay attention to the modification.

[0215] The risk level is the third level, which means that if the verification fails, the operation of the target service will not be affected if the process flowchart to be processed is not changed, and the negative impact on the user experience is relatively small. It is better to modify it, and it can be used without modification. That is, in the case of verification failure, the field to be verified may bring a small risk to the use of the target service corresponding to the flowchart to be processed. The prompt message reminds the user that it is optional to modify it.

[0216] When a large number of flowcharts to be processed are processed in the same time period, the verification method provided in the embodiment of the present application may verify many problems and give prompts. In the process of users modifying the configuration information based on the prompts, they need to distinguish the primary from the secondary. If the errors in all the configuration information are modified in sequence, it may take a long time and be very inefficient. This implementation method is conducive to giving priority to problems with the highest risk level, and then processing problems with average risk levels. In addition, users can evaluate by themselves whether to ignore problems with minor impacts or to modify them together after processing problems with other risk levels.

[0217] In a specific implementation method, the field to be checked is checked according to a target verification method. After the field verification result is obtained, the verification method also includes: after the flowchart to be processed is modified, if a parameter change of the field to be checked in the configuration information of the flowchart to be processed is detected, the field to be checked is checked again according to the target verification method.

[0218] The configuration information of the flowchart to be processed may include multiple fields to be checked. After the user modifies the configuration information of the flowchart to be processed based on the risk control prompt information, the secondary verification does not need to re-verify the entire flowchart to be processed. Instead, if any parameter changes are detected, it can be verified again according to the determined target verification method.

[0219] The field to be checked is subjected to a secondary check according to the target check method, and reference may be made to the corresponding description section of "the field to be checked is subjected to a check according to the target check method to obtain a field check result" in the aforementioned step S206.

[0220] In such Figure 2In the embodiment shown, first, according to the configuration information of the flowchart to be processed, the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked are determined; then, according to the attributes to be checked of the fields to be checked, the target verification method is determined; finally, the fields to be checked are verified according to the target verification method to obtain the field verification result, and the verification result of the flowchart to be processed is determined according to the field verification result. In this way, considering that the flowchart to be processed may include multiple fields to be checked, each field to be checked may have some personalized characteristics, and it is difficult to verify all the fields to be checked by a unified verification method, by determining the target verification method according to the attributes to be checked of the fields to be checked, and verifying the fields to be checked according to the target verification method to obtain the field verification result, it is conducive to reusing some ready-made verification methods by configuring the attributes to be checked of the fields to be checked when processing the verification work of personalized fields to be checked. Compared with designing a corresponding personalized verification process for each field to be checked, repeated verification configuration work is reduced, and in the overall verification process of the flowchart to be processed, when processing each field to be checked in turn, there is no need to rely on manual experience to switch the verification method, thereby improving the verification efficiency of the flowchart to be processed.

[0221] The following takes the application of a verification method provided by this embodiment in a call center as an example, combined with Figure 3 and Figure 4 The verification method provided in this embodiment is further described.

[0222] Figure 3 A first schematic diagram of a verification method applied to a call center provided in an embodiment of the present application.

[0223] A call center is a place where people interact and conduct transactions through telephone, such as service, sales, emergencies, etc. It also includes manual service and self-service.

[0224] The target service may be an IVR service, and the flowchart to be processed may be an IVR flowchart. The graph element may include a first node or a first edge.

[0225] The IVR process can be represented by an IVR flow chart, which includes multiple first nodes and edges connecting the first nodes, each first node has corresponding attribute information, and the IVR flow chart to be verified can be manually configured. The verification method provided in this embodiment can be used to check for omissions in manual configuration work, quickly locate problems and specifically prompt users where modifications are required.

[0226] When the graph element includes the first node, node check 302 may be performed; when the graph element includes the first edge, edge check 306 may be performed. In addition, after node check 302 and edge check 306 are completed, speech check 304 may be performed.

[0227] Considering that the speech itself is not a graph element, the following briefly explains why the speech check 304 is listed in parallel with the node check 302 and the edge check 306:

[0228] In specific implementation, a speech set can be pre-configured, and the set includes multiple speech, each speech has a unique corresponding speech identifier. When configuring any graph element, if the graph element needs to use a speech, the speech identifier is inserted into the configuration information of the graph element. Among the multiple speech included in the speech set, the speech identifiers of some speech may be inserted into the configuration information of the graph element, that is, the speech identifiers of some speech have been put into use, and the other speech has not been put into use yet.

[0229] During the execution of the node verification 302 , some of the graph elements may involve speech. Then, the speech corresponding to the speech identifier inserted into the configuration information of the graph element is speech verified during the execution of the node verification 302 .

[0230] In actual applications, there may be a need to verify all the words regardless of whether they have been put into use. Therefore, after all first nodes and all first edges have been verified, the word verification 304 can be performed using the word set to verify both the words that have been put into use and the words that have not been put into use.

[0231] In the node configuration information of the first node, the fields to be checked and the attributes to be checked of the fields to be checked can be determined, and each attribute to be checked can be one of the preset attribute set 1.

[0232] The preset attribute set 1 may include: working time attribute 308 , process attribute 310 , speech attribute 312 , input attribute 314 , process variable attribute 316 , and input or process variable attribute 318 .

[0233] Considering that in actual applications, some input boxes only allow users to input spelled content and do not provide users with optional process variables, some input boxes only allow users to select one of the optional multiple process variables and do not allow users to input content, and some input boxes allow users to input both spelled content and select one of the optional multiple process variables. Therefore, in the aforementioned preset attribute set, "input attribute 314", "process variable attribute 316" and "input or process variable attribute 318" are three different attributes, "input attribute 314" and "input or process variable attribute 318" are not repeated, and "process variable attribute 316" and "input or process variable attribute 318" are not repeated. "Input attribute 314" is for an input box that only allows users to input spelled content and does not provide users with optional process variables, "process variable attribute 316" is for an input box that only allows users to select one of the optional multiple process variables and does not allow users to input content, and "input or process variable attribute 318" is for an input box that allows users to input both spelled content and select one of the optional multiple process variables.

[0234] In the edge configuration information of the first edge, the fields to be checked and the attributes to be checked of the fields to be checked can be determined, and each attribute to be checked can be one of the preset attribute set 2.

[0235] The preset attribute set 2 may include: process variable attributes 316 , and input or process variable attributes 318 .

[0236] In the speech configuration information, the fields to be checked and the attributes to be checked of the fields to be checked, that is, the speech attributes 312, can be determined.

[0237] After determining the attributes to be checked of the field to be checked, the data verification method of the attributes to be checked of the field to be checked can be queried in the preset corresponding relationship set according to the attributes to be checked of the field to be checked, and the target verification method can be obtained; the preset corresponding relationship set includes: for each attribute in the preset attribute set, the corresponding relationship between the attribute and at least one data verification method. For details, please refer to the corresponding description of the aforementioned step S204.

[0238] Figure 3 The various corresponding relationships included in the preset corresponding relationship set are clearly and intuitively shown:

[0239] (b1) Correspondence 1 between the working time attribute 308 and the working time usage check 320;

[0240] (b2) Correspondence 2 between the working time attribute 308 and the non-empty check 326;

[0241] (b3) Correspondence 3 between process attribute 310 and process usage check 322;

[0242] (b4) Correspondence 4 between process attribute 310 and non-empty check 326;

[0243] (b5) Correspondence 5 between speech attribute 312 and speech usage check 324;

[0244] (b6) Correspondence 6 between the speech attribute 312 and the non-empty check 326;

[0245] (b7) Correspondence 7 between input attribute 314 and non-empty check 326;

[0246] (b8) Correspondence 8 between process variable attribute 316 and non-empty check 326;

[0247] (b9) Correspondence 9 between process variable attributes 316 and process variable usage verification 328;

[0248] (b10) Correspondence 10 between input or process variable attribute 318 and non-empty check 326;

[0249] (b11) Correspondence 11 between input or process variable attributes 318 and process variable usage checks 328.

[0250] like Figure 3 As shown, from a holistic perspective, the verification method provided in this embodiment divides the verification process of the flowchart to be processed into three layers, wherein the first layer is the graph elements, the second layer is the attributes, and the third layer is the data verification method. The second layer pre-configures a fixed set of preset attributes, and the second layer also pre-configures one or more data verification methods corresponding to each attribute in the preset attribute set. The third layer pre-configures a fixed set of preset data verification methods.

[0251] In the process of processing different flowcharts to be processed, the contents of the second and third layers are universal for any flowchart to be processed, and only the configuration information of the graph elements located in the first layer is different. By determining the attributes by the graph elements and determining the data verification method by the attributes, different fields to be verified of the same graph element can reuse the same data verification method, and multiple fields of different graph elements can reuse the same data verification method. Therefore, when verifying any flowchart to be processed, it is not necessary to design a personalized data verification process for each graph element in the flowchart to be processed. It is only necessary to design the fields to be verified involved in the verification and the attributes to be verified of each field in the configuration information of the graph element, which reduces a lot of repeated configuration work, is conducive to the flexible combination of data verification methods, and improves verification efficiency.

[0252] Since the technical concept is the same, the description in this embodiment is relatively simple, and the relevant parts may refer to the corresponding description of the method embodiment provided above.

[0253] Figure 4 A second schematic diagram of a verification method applied to a call center provided in an embodiment of the present application. Figure 3 and Figure 4 Includes the same parts, which can refer to the aforementioned Figure 3 Corresponding instructions.

[0254] The target service may be an IVR service, and the flowchart to be processed may be an IVR flowchart. The graph element may include a first node or a first edge.

[0255] When the graph element includes the first node, node check 402 and node internal relevance check 408 may be performed; when the graph element includes the first edge, edge check 406 and edge relevance check 410 may be performed. In addition, after node check 402 and edge check 406 are completed, speech check 404 may also be performed.

[0256] In the node configuration information of the first node, the fields to be checked and the attributes to be checked of the fields to be checked can be determined, and each attribute to be checked can be one of the preset attribute set 3.

[0257] The preset attribute set 3 may include: working time attribute 412, process attribute 414, speech attribute 416, input attribute 418, process variable attribute 420, input or process variable attribute 422, type consistency of process variable 424, and type consistency of node entry and exit participating process variables 426.

[0258] In the edge configuration information of the first edge, the fields to be checked and the attributes to be checked of the fields to be checked can be determined, and each attribute to be checked can be one of the preset attribute sets 4.

[0259] The preset attribute set 4 may include: process variable attributes 420 , input or process variable attributes 422 , type consistency of process variables 424 , and type consistency of node entry and exit participating process variables 426 .

[0260] In the speech configuration information, the fields to be checked and the attributes to be checked of the fields to be checked, that is, the speech attributes 416, can be determined.

[0261] After determining the attributes to be checked of the field to be checked, the data verification method of the attributes to be checked of the field to be checked can be queried in the preset corresponding relationship set according to the attributes to be checked of the field to be checked, and the target verification method can be obtained; the preset corresponding relationship set includes: for each attribute in the preset attribute set, the corresponding relationship between the attribute and at least one data verification method. For details, please refer to the corresponding description of the aforementioned step S204.

[0262] Figure 4 The various corresponding relationships included in the preset corresponding relationship set are clearly and intuitively shown:

[0263] (c1) Correspondence 1 between the working time attribute 412 and the working time usage check 428;

[0264] (c2) Correspondence 2 between the working time attribute 412 and the non-empty check 434;

[0265] (c3) Correspondence 3 between process attribute 414 and process usage check 430;

[0266] (c4) Correspondence 4 between process attribute 414 and non-empty check 434;

[0267] (c5) Correspondence 5 between speech attribute 416 and speech usage verification 432;

[0268] (c6) Correspondence 6 between the speech attribute 416 and the non-empty check 434;

[0269] (c7) Correspondence 7 between input attribute 418 and non-empty check 434;

[0270] (c8) Correspondence 8 between process variable attribute 420 and non-empty check 434;

[0271] (c9) Correspondence 9 between process variable attributes 420 and process variable usage verification 436;

[0272] (c10) Correspondence 10 between input or process variable attribute 422 and non-empty check 434;

[0273] (c11) Correspondence 11 between input or process variable attributes 422 and process variable usage checks 436;

[0274] (c12) Correspondence 12 between the type consistency 424 of the process variable and the type consistency check 438 of the process variable;

[0275] (c13) Correspondence 13 between the type consistency 424 of the process variable and the consistency check 440 of the input parameter type of the process variable;

[0276] (c14) Correspondence 14 between the type consistency 426 of the node entry and exit participating process variables and the type consistency check 438 of the process variables;

[0277] (c15) Correspondence 15 between the type consistency 426 of the node input and output process variables and the input parameter type consistency check 440 of the process variables.

[0278] The type consistency check 438 of the process variable may refer to the corresponding description part of the implementation method of the aforementioned “target verification method includes the second verification method”.

[0279] The input parameter type consistency check 440 of the process variable may refer to the corresponding description part of the implementation method of the aforementioned “target verification method includes the first verification method”.

[0280] Figure 4 The principle of the calibration method shown is similar to Figure 3 Similarly, please refer to the corresponding description section.

[0281] Since the technical concept is the same, the description in this embodiment is relatively simple, and the relevant parts may refer to the corresponding description of the method embodiment provided above.

[0282] Figure 5 A processing flow chart of another verification method provided in an embodiment of the present application.

[0283] Step S502: node arrangement attributes.

[0284] In the case where the graph element includes the first node, the fields to be checked and the attributes to be checked of the fields to be checked are determined in the configuration information of the graph element. Figure 2 The corresponding description part of step S202 in the embodiment. According to the to-be-checked attribute of the to-be-checked field, the data verification method of the to-be-checked attribute of the to-be-checked field is queried in the preset corresponding relationship set to obtain the target verification method, which can be referred to Figure 2 The corresponding description part of step S204 in the embodiment. The verification process is performed on the verification field according to the target verification method to obtain the field verification result. Figure 2 The corresponding description part of step S206 in the embodiment.

[0285] Step S504: Arrange attributes.

[0286] In the case where the graph element includes the first edge, the fields to be checked and the attributes to be checked of the fields to be checked are determined in the configuration information of the graph element. Figure 2The corresponding description part of step S202 in the embodiment. According to the to-be-checked attribute of the to-be-checked field, the data verification method of the to-be-checked attribute of the to-be-checked field is queried in the preset corresponding relationship set to obtain the target verification method, which can be referred to Figure 2 The corresponding description part of step S204 in the embodiment. The verification process is performed on the verification field according to the target verification method to obtain the field verification result. Figure 2 The corresponding description part of step S206 in the embodiment.

[0287] Step S506: Verify the associated attributes within the node.

[0288] In the case where the graph element includes the first node, the fields to be checked and the attributes to be checked of the fields to be checked are determined in the configuration information of the graph element: the type consistency of the process variables or the type consistency of the process variables involved in the node entry and exit, which can be referred to Figure 2 The corresponding description part of step S202 in the embodiment. According to the to-be-checked attribute of the to-be-checked field, the data verification method of the to-be-checked attribute of the to-be-checked field is queried in the preset corresponding relationship set to obtain the target verification method, which can be referred to Figure 2 The corresponding description part of step S204 in the embodiment. The verification process is performed on the verification field according to the target verification method to obtain the field verification result. Figure 2 The corresponding description part of step S206 in the embodiment.

[0289] In order to more intuitively illustrate the node-internal association attribute verification, the following can be combined with Figure 6-Figure 9 The diagram elements shown are for illustrative purposes only.

[0290] Figure 6 This is a node configuration page of the first node of the first type provided in an embodiment of the present application.

[0291] like Figure 6 As shown, the first node may be a branch node 600 .

[0292] The branch node 600 can go to different nodes based on different tags or different input contents of the user. In addition, the branch node 600 also needs to determine whether the data type of the input content is the same as the data type of the judgment condition. For example, if the input content is not a pre-configured character such as 0-9 and *, #, it will be determined that the check fails and a targeted prompt will be given.

[0293] In a specific implementation, the variable identifier of the process variable 602 and the variable identifier of the process variable 606, which are respectively located at both ends of the preset type symbol 604, can be determined in the node configuration information of the branch node 600 according to the field to be checked; the data type of the process variable 602 can be queried according to the variable identifier of the process variable 602, and the data type of the process variable 606 can be queried according to the variable identifier of the process variable 606; the data type of the process variable 602 is compared with the data type of the process variable 606 to obtain a second comparison result; and according to the second comparison result, a second verification result of verifying the field to be verified by a second verification method is determined.

[0294] For details, please refer to the corresponding description section on the implementation method of the aforementioned "second verification method".

[0295] Figure 7 This is a node configuration page of the second first node provided in an embodiment of the present application.

[0296] like Figure 7 As shown, the first node may be a process variable assignment node 700 .

[0297] The process variable assignment node 700 assigns a process variable to another process variable. Considering that the process variable assignment node 700 will be successful only when the data types of the two process variables are the same, it is necessary to verify whether the data types of the two process variables are consistent, for example, whether they are both integers, or whether they are both sets, etc.

[0298] like Figure 7 As shown, for example, to ensure that the previous score is assigned to the current score, it is necessary to verify whether the data type of the previous score is the same as the data type of the current score, and whether the data types of the two are pre-specified data types, such as integers.

[0299] In a specific implementation, the variable identifier of the process variable 702 corresponding to the "current scoring" and the variable identifier of the process variable 706 corresponding to the "previous scoring" respectively located at both ends of the preset type symbol 704 can be determined in the node configuration information of the process variable assignment node 700 according to the field to be checked; the data type of the process variable 702 is queried and obtained according to the variable identifier of the process variable 702, and the data type of the process variable 706 is queried and obtained according to the variable identifier of the process variable 706; the data type of the process variable 702 is compared with the data type of the process variable 706 to obtain a second comparison result; and according to the second comparison result, a second verification result of verifying the field to be verified by a second verification method is determined.

[0300] For details, please refer to the corresponding description section on the implementation method of the aforementioned "second verification method".

[0301] Figure 8 This is a node configuration page of the third first node provided in an embodiment of the present application.

[0302] like Figure 8 As shown, the input parameter configuration interface 800 can be a sub-interface of the interface call node, which is mainly used to configure and process the input parameter data of the interface. The input parameter configuration interface 800 displays input parameter data 802, and the name of the input parameter data 802 is "mobile phone number".

[0303] Fig. 9 This is a node configuration page of the fourth first node provided in an embodiment of the present application.

[0304] like Fig. 9 As shown, the first node may be an interface calling node 900. In the node configuration page of the interface calling node 900, an input parameter configuration area 902 and an output parameter configuration area 904 may be included.

[0305] In a specific implementation, the data identifier representing the input and output parameter data and the first variable identifier of the first variable corresponding to the field to be checked can be determined in the node configuration information of the interface calling node 900 according to the field to be checked; the data type of the input and output parameter data is queried according to the data identifier, and the data type of the first variable is queried according to the first variable identifier; the data type of the input and output parameter data is compared with the data type of the first variable to obtain a first comparison result; and based on the first comparison result, a first verification result of the field to be checked by using a first verification method is determined.

[0306] For details, please refer to the corresponding description section on the implementation method of the aforementioned "first verification method".

[0307] Step S508: edge association check.

[0308] In the case where the graph element includes the first edge, the fields to be checked and the attributes to be checked of the fields to be checked are determined in the configuration information of the graph element: the type consistency of the process variables or the type consistency of the process variables involved in the node entry and exit, which can be referred to Figure 2 The corresponding description part of step S202 in the embodiment. According to the to-be-checked attribute of the to-be-checked field, the data verification method of the to-be-checked attribute of the to-be-checked field is queried in the preset corresponding relationship set to obtain the target verification method, which can be referred to Figure 2 The corresponding description part of step S204 in the embodiment. The verification process is performed on the verification field according to the target verification method to obtain the field verification result. Figure 2 The corresponding description part of step S206 in the embodiment.

[0309] Step S510: inter-node verification.

[0310] This step can refer to the corresponding description part of the implementation method of the aforementioned "input and output parameter verification method".

[0311] Step S512: speech verification.

[0312] Since the technical concept is the same, the description in this embodiment is relatively simple, and the relevant parts may refer to the corresponding description of the method embodiment provided above.

[0313] The following takes the application of a verification method provided in an embodiment of the present application in a call center as an example, combined with Figure 10-Figure 34 The verification method provided in the embodiment of the present application is further explained.

[0314] The target service may be an IVR service, and each flowchart to be processed may be an IVR flowchart. The system components supporting the implementation of the verification method may include: Ivr-manager.

[0315] Ivr-manager can be used to accept the user's process-related configuration, verify the user's configuration, and give corresponding prompts.

[0316] First, create the IVR.

[0317] Then, create an IVR version and configure the process, process variables, scripts, audio, interface, speech synthesis configuration, etc. within the IVR version.

[0318] Fig.10 A process management interface provided in an embodiment of the present application.

[0319] like Fig.10 As shown, the process management interface 1000 includes a toolbar area 1002 and a flow chart configuration area 1004. Node 1006 is a start node, node 1008 is an intermediate node, node 1010 is an end node, and edge 1002 is located between the two nodes.

[0320] Fig.11 A process variable management interface provided in an embodiment of the present application.

[0321] like Fig.11 As shown, the process variable management interface 1100 displays the added process variable 1102 .

[0322] Fig.12 A speech management interface provided in an embodiment of the present application.

[0323] like Fig.12 As shown, the added speech 1202 is displayed in the speech management interface 1200.

[0324] Fig.13 An audio management interface provided in an embodiment of the present application.

[0325] like Fig.13 As shown, the audio management interface 1300 displays the imported audio data 1302 .

[0326] Audio management is to manage the audio corresponding to the content of the speech. During the operation of the IVR process, the speech broadcast to the user can be uploaded by yourself or synthesized by voice. If you broadcast what you uploaded yourself, you can upload the corresponding audio in the audio management. After uploading, you can audition and download the audio. If you do not use the uploaded audio for broadcasting, you do not need to upload it. Audio management can also check which speech the audio is referenced by, so as to know which speech will play the audio.

[0327] Fig.14 An interface management interface provided for the embodiment of the present application

[0328] like Fig.14 As shown, the interface management interface 1400 displays an added interface 1402 .

[0329] Fig.15 A language setting interface is provided in an embodiment of the present application.

[0330] like Fig.15 As shown, the language setting interface 1500 displays the added speech synthesis information 1502 .

[0331] As mentioned above Figure 11-Figure 15 The various interfaces shown can be used to configure processes, process variables, scripts, audio, interfaces, speech synthesis, and other related configurations.

[0332] Next, click Verify, and the backend will verify all the contents in the IVR version. Figure 2 The embodiments correspond to the description section.

[0333] Finally, for the verification results, if any problems are found, they will be marked and prompts will be given.

[0334] The specific steps for backend verification are as follows:

[0335] 1. Perform node-related verification first;

[0336] 2. Check the connection properties again;

[0337] 3. Verify the associated attributes within the node;

[0338] 4. Verify the connection condition and associated attributes;

[0339] 5. Verify the connection between nodes;

[0340] 6. Verify the speech skills.

[0341] Next, taking the first step of node-related verification as an example, the layered verification is illustrated by the verification method provided in the embodiment of the present application. The layered verification divides the entire verification process into three layers.

[0342] The first layer includes graph elements. The configuration information of the graph elements includes fields to be checked and attributes to be checked of the fields to be checked. Therefore, the fields to be checked and attributes to be checked of the fields to be checked that participate in the check can be determined in the configuration information of the graph elements. Figure 2 The corresponding description part of step S202 in the embodiment.

[0343] Below, some specific configuration information may be used for exemplary description.

[0344] Playback node:

[0345] Configuration Content Check Items level Talk Speech configuration Error

[0346] Table 1: Announcement and number receiving nodes:

[0347]

[0348]

[0349] Table 2 Message nodes:

[0350] Configuration Content Check Items level Talk Speech configuration Error Message duration Input Configuration Error End message method Input Configuration Error

[0351] Table 3 Language selection nodes:

[0352] Configuration Content Check Items level Talk Speech configuration Error Number of received numbers Input Configuration Error Timeout Input Configuration Error Language button Input Configuration Error

[0353] Table 4 Read channel variables:

[0354] Configuration Content Check Items level Channel variable name Input Configuration Warn Process variables Process variable configuration Warn

[0355] Table 5 Write channel variables:

[0356] Configuration Content Check Items level Channel variable name Input Configuration Warn Write value Input or process variable configuration Warn

[0357] Table 6 variable assignment:

[0358] Configuration Content Check Items level Process variables Process variable configuration verification Warn Assignment Input or process variable configuration Warn

[0359] Working hours:

[0360] Configuration Content Check Items level Working hours Working hours configuration Error

[0361] Table 8 Sub-process:

[0362] Configuration Content Check Items level Subprocess Process Configuration Error

[0363] Table 9 Interface call:

[0364] Configuration Content Check Items level interface Interface Configuration Error

[0365] Table 10 Transfer skill group:

[0366] Configuration Content Check Items level Skill Group Input or process variable configuration Error Transfer Speech Speech configuration Warn Waiting tone Speech configuration Error

[0367] Table 11 transfer to external line:

[0368] Configuration Content Check Items level Number Input or process variable configuration Error Transfer Speech Speech configuration Warn

[0369] Table 12 Voice navigation:

[0370] Configuration Content Check Items level Business Line Business Line Configuration Error Talk Speech configuration Error

[0371] Table 13 Hash split:

[0372]

[0373]

[0374] Table 14 Playback and reception:

[0375] Configuration Content Check Items level Talk 1 Speech configuration Error Talk 2 Speech configuration Error

[0376] Table 15 Voice scene switching:

[0377] Configuration Content Check Items level Speech Synthesis Scenario Verify speech synthesis configuration Error

[0378] Table 16 Limited diversion:

[0379] Configuration Content Check Items level Repeat cycle Input Configuration Warn Limited number of times Input Configuration Warn Repeating dimensions Input Configuration Warn

[0380] Table 17

[0381] Referring to Tables 1 to 17 above, the various fields to be checked in the process flow chart to be processed can be read in the "Configuration Content" column. For each field to be checked, the "Check Item" of the field to be checked can be used to determine the attributes to be checked of the field to be checked. "Level" can refer to the risk level of the field to be checked, Error can refer to the first risk level, and Warn can refer to the second risk level.

[0382] The second layer includes attributes, and the attributes can be determined by the "check items" in the configuration information of the graph elements of the first layer.

[0383] In the case of a known preset correspondence set, the data verification method of the attribute to be verified of the field to be verified can be queried in the preset correspondence set according to the attribute to be verified of the field to be verified, and the target verification method can be obtained. Figure 2 The corresponding description part of step S204 in the embodiment.

[0384] When the check item is a speech configuration, the attribute to be checked of the field to be checked can be considered as a speech attribute. The preset correspondence set can include a correspondence between speech attributes and non-empty checks, and can also include a correspondence between speech attributes and speech usage checks.

[0385] Fig.16 A flowchart of the first processing sub-process of a verification method provided in an embodiment of the present application.

[0386] Step S1602, whether the non-empty check is successful.

[0387] If yes, execute step S1604; if no, execute step S1606.

[0388] Step S1604, whether the speech usage verification is successful.

[0389] If yes, execute step S1608; if no, execute step S1606.

[0390] Step S1606, determining that verification has failed.

[0391] Step S1608, determine whether the verification is successful.

[0392] For the field to be checked, if the configuration item of the field to be checked is "speech configuration", it can be determined that the attribute to be checked of the field to be checked is the speech attribute, and then, steps S1062 to S1608 can be executed.

[0393] When the check item is a process configuration, the attribute to be checked of the field to be checked can be considered as a process attribute. The preset correspondence set can include a correspondence between a process attribute and a non-empty check, and can also include a correspondence between a process attribute and a process usage check.

[0394] Fig.17 A flowchart of the second processing sub-process of a verification method provided in an embodiment of the present application.

[0395] Step S1702, whether the non-empty check is successful.

[0396] If yes, execute step S1704; if no, execute step S1706.

[0397] Step S1704, the process usage verification is successful.

[0398] If yes, execute step S1708; if no, execute step S1706.

[0399] Step S1706, determining that verification has failed.

[0400] Step S1708, determine whether the verification is successful.

[0401] For the field to be checked, if the configuration item of the field to be checked is "process configuration", it can be determined that the attribute to be checked of the field to be checked is a process attribute, and then, steps S1702 to S1708 can be executed.

[0402] When the check item is a process variable configuration, the attribute to be checked of the field to be checked can be regarded as a process variable attribute. The preset correspondence set can include a correspondence between a process variable attribute and a non-empty check, and can also include a correspondence between a process attribute and a process variable usage check.

[0403] Fig.18 A flowchart of the third processing sub-process of a verification method provided in an embodiment of the present application.

[0404] Step S1802, whether the non-empty check is successful.

[0405] If yes, execute step S1804; if no, execute step S1806.

[0406] Step S1804: Check whether the process variable usage is successful.

[0407] If yes, execute step S1808; if no, execute step S1806.

[0408] Step S1806, determining that verification has failed.

[0409] Step S1808, determine whether the verification is successful.

[0410] For the field to be checked, if the configuration item of the field to be checked is "process variable configuration", it can be determined that the attribute to be checked of the field to be checked is a process variable attribute, and then, steps S1802 to S1808 can be executed.

[0411] When the check item is an input configuration, the attribute to be checked of the field to be checked can be regarded as an input attribute. The preset correspondence set can include a correspondence between the input attribute and the non-empty check.

[0412] Fig.19 A flowchart of the fourth processing sub-process of a verification method provided in an embodiment of the present application.

[0413] Step S1902, whether the non-empty check is successful.

[0414] If yes, execute step S1904; if no, execute step S1906.

[0415] Step S1906, determine whether verification has failed.

[0416] Step S1904, determine whether the verification is successful.

[0417] For the field to be checked, if the configuration item of the field to be checked is "input configuration", it can be determined that the attribute to be checked of the field to be checked is an input attribute, and then, steps S1902 to S1906 can be executed.

[0418] When the check item is an interface configuration, the attribute to be checked of the field to be checked can be considered as an interface attribute. The preset correspondence set can include a correspondence between an interface attribute and a non-empty check, and can also include a correspondence between an interface attribute and an interface input parameter check.

[0419] Fig. 20 This is a flowchart of the fifth processing sub-process of a verification method provided in an embodiment of the present application.

[0420] Step S2002, whether the non-empty check is successful.

[0421] If yes, execute step S2004; if no, execute step S2006.

[0422] Step S2004: Check whether the interface input parameters are successful.

[0423] If yes, execute step S2008; if no, execute step S2006.

[0424] Step S2006, determining that verification has failed.

[0425] Step S2008, determine whether the verification is successful.

[0426] For the field to be checked, if the configuration item of the field to be checked is "interface configuration", it can be determined that the attribute to be checked of the field to be checked is an interface attribute, and then, steps S2002 to S2008 can be executed.

[0427] When the check item is input or process configuration, the attribute to be checked of the field to be checked can be regarded as an input or process configuration attribute. The preset correspondence set may include a correspondence between an input or process configuration attribute and a non-empty check, and may also include a correspondence between an input or process configuration attribute and a process variable usage check.

[0428] Fig.21 This is a flowchart of the sixth processing sub-process of a verification method provided in an embodiment of the present application.

[0429] Step S2102, whether the input is non-empty and the verification is successful.

[0430] If yes, execute step S2104; if no, execute step 2106.

[0431] Step S2104, determine whether the verification is successful.

[0432] Step S2106, whether the process variable is non-null check is successful.

[0433] If yes, execute step S2108; if no, execute step 2110.

[0434] Step S2108, whether the process variable usage verification is successful.

[0435] If yes, execute step S2104; if no, execute step S2110.

[0436] For the field to be checked, if the configuration item of the field to be checked is "input or process variable configuration", it can be determined that the attribute to be checked of the field to be checked is an input or process attribute, and then, steps S2102 to S2108 can be executed.

[0437] When the check item is working time configuration, the attribute to be checked of the field to be checked can be considered as the working time attribute. The preset correspondence set may include the correspondence between the working time attribute and the non-empty check, and may also include the correspondence between the working time attribute and the working time usage check.

[0438] Fig. 22 A flowchart of the third processing sub-process of a verification method provided in an embodiment of the present application.

[0439] Step S2202, whether the non-empty check is successful.

[0440] If yes, execute step S2204; if no, execute step S2206.

[0441] Step S2204, whether the working time usage verification is successful.

[0442] If yes, execute step S2208; if no, execute step S2206.

[0443] Step S2206, determine whether verification has failed.

[0444] Step S2208, determine whether the verification is successful.

[0445] For the field to be checked, if the configuration item of the field to be checked is "working time configuration", it can be determined that the attribute to be checked of the field to be checked is the working time attribute, and then, steps S2202 to S2208 can be executed.

[0446] When the check item is a business line configuration, the attribute to be checked of the field to be checked can be considered as a business line attribute. The preset correspondence set may include a correspondence between a business line attribute and a non-empty check, and may also include a correspondence between a business line attribute and a business line usage check.

[0447] Fig.23 This is a flowchart of the eighth processing sub-process of a verification method provided in an embodiment of the present application.

[0448] Step S2302, whether the non-empty check is successful.

[0449] If yes, execute step S2304; if no, execute step S2306.

[0450] Step S2304: Check whether the business line usage is successful.

[0451] If yes, execute step S2308; if no, execute step S2306.

[0452] Step S2306, determine whether verification has failed.

[0453] Step S2308, determine whether the verification is successful.

[0454] For the field to be checked, if the configuration item of the field to be checked is "working time configuration", it can be determined that the attribute to be checked of the field to be checked is the working time attribute, and then, steps S2302 to S2308 can be executed.

[0455] When the check item is a language synthesis configuration, the attribute to be checked of the field to be checked can be considered as a speech attribute. The preset correspondence set can include a correspondence between speech attributes and non-empty checks, and can also include a correspondence between speech attributes and language synthesis checks.

[0456] Fig.24 A flowchart of the ninth processing sub-process of a verification method provided in an embodiment of the present application.

[0457] Step S2402, whether the non-empty check is successful.

[0458] If yes, execute step S2404; if no, execute step S2406.

[0459] Step S2404: Verify whether the language synthesis is successful.

[0460] If yes, execute step S2408; if no, execute step S2406.

[0461] Step S2406, determine whether verification has failed.

[0462] Step S2408, determine whether the verification is successful.

[0463] For the field to be checked, if the configuration item of the field to be checked is "language synthesis configuration", it can be determined that the attribute to be checked of the field to be checked is the speech attribute, and then, steps S2402 to S2408 can be executed.

[0464] The third layer includes data verification methods, which can be determined by the attributes of the second layer.

[0465] Fig.25 This is the first data verification method provided in the embodiment of the present application. Specifically, Fig.25 The processing flow of non-null check is shown.

[0466] Step S2502, determine whether it is empty.

[0467] If yes, execute step S2504; if no, end the current processing flow.

[0468] Step S2504, return verification failure.

[0469] Fig.26 This is the second data verification method provided in the embodiment of the present application. Specifically, Fig.26 The processing flow of speech usage verification is shown.

[0470] Step S2602, query the speech script according to the version identifier and the speech script identifier.

[0471] Step S2604, determine whether it is empty.

[0472] If yes, execute step S2606; if no, execute step S2608.

[0473] Step S2606, return verification failure.

[0474] Step S2608, determine the configuration content.

[0475] If the configuration content includes audio, execute step S2610; if the configuration content includes others, execute step S2612.

[0476] Step S2610, determining whether to upload the corresponding audio file based on the content.

[0477] If yes, execute step S2614; if no, end the current processing flow.

[0478] Step S2612, checking whether language synthesis is configured.

[0479] If yes, execute step S2614; if no, execute step S2610.

[0480] Step S2614, confirm that the verification is passed.

[0481] Fig. 27 This is the third data verification method provided in the embodiment of the present application. Specifically, Fig. 27 The process flow of process usage verification is shown.

[0482] Step S2702, query the process according to the version identifier and the process identifier.

[0483] Step S2704, determine whether it is empty.

[0484] If yes, execute step S2706; if no, end the current processing flow.

[0485] Step S2706, return verification failure.

[0486] Fig.28 This is the fourth data verification method provided in the embodiment of the present application. Specifically, Fig.28 The figure shows the process flow of process variable usage verification.

[0487] Step S2802, query the process variable according to the version identifier and the process variable identifier.

[0488] Step S2804, determine whether it is empty.

[0489] If yes, execute step S2806; if no, end the current processing flow.

[0490] Step S2806, return verification failure.

[0491] Fig.29 This is the fifth data verification method provided in the embodiment of the present application. Specifically, Fig.29 The processing flow of working time usage verification is shown.

[0492] Step S2902, query the working time configuration according to the working time identifier.

[0493] Step S2904, determine whether it is empty.

[0494] If yes, execute step S2906; if no, end the current processing flow.

[0495] Step S2906, return verification failure.

[0496] Fig.30 This is the sixth data verification method provided in the embodiment of the present application. Specifically, Fig.30 The processing flow of business line usage verification is shown.

[0497] Step S3002, query the business line configuration according to the business line identifier.

[0498] Step S3004, determine whether it is empty.

[0499] If yes, execute step S3006; if no, end the current processing flow.

[0500] Step S3006, return verification failure.

[0501] Fig.31 This is the seventh data verification method provided in the embodiment of the present application. Specifically, Fig.31 The process flow of speech synthesis using verification is shown.

[0502] Step S3102: query the language synthesis configuration according to the language synthesis identifier.

[0503] Step S3104, determine whether it is empty.

[0504] If yes, execute step S3106; if no, end the current processing flow.

[0505] Step S3106, return verification failure.

[0506] Fig.32 This is the eighth data verification method provided in the embodiment of the present application. Specifically, Fig.32 The figure shows the processing flow of the process variable type consistency check.

[0507] Step S3202, query process variable A according to the version identifier and the process variable identifier.

[0508] Step S3204, determine whether it is empty.

[0509] If yes, execute step S3206; if no, execute step S3208.

[0510] Step S3206, return verification failure.

[0511] Step S3208, query process variable B according to the version identifier and the process variable identifier.

[0512] Step S3210, determine whether it is empty.

[0513] If yes, execute step S3206; if no, execute step S3212.

[0514] Step S3212, determine whether the type of process variable A is the same as the type of process variable B.

[0515] If yes, then end the current processing flow; if no, execute step S3206.

[0516] Fig.33 This is the ninth data verification method provided in the embodiment of the present application. Specifically, Fig.33 The following figure shows the processing flow of consistency check of process variables and input parameter types.

[0517] Step S3302, querying the process variable according to the version identifier and the process variable identifier;

[0518] Step S3304, determine whether it is empty.

[0519] If yes, execute step S3306; if no, execute step S3308.

[0520] Step S3306, return verification failure.

[0521] Step S3308, determine whether the process variable is of the same type as the one passed in.

[0522] If yes, then end the current processing flow; if no, execute step S3306.

[0523] Fig.34 This is the tenth data verification method provided in the embodiment of the present application. Specifically, Fig.34 The processing flow of interface input parameter verification is shown.

[0524] Step S3402, querying the interface configuration according to the version identifier and the interface identifier;

[0525] Step S3404, determine whether it is empty.

[0526] If yes, execute step S3406; if no, execute step S3408.

[0527] Step S3406, return verification failure.

[0528] Step S3408: Check whether the process variables are configured based on whether the input parameters of the interface must be passed.

[0529] If yes, then end the current processing flow; if no, execute step S3406.

[0530] Since the technical concept is the same, the description in this embodiment is relatively simple, and the relevant parts may refer to the corresponding description of the method embodiment provided above.

[0531] An embodiment of a verification device provided in this specification is as follows:

[0532] In the above-mentioned embodiment, a verification method is provided. Based on the same technical concept, the embodiment of the present application also provides a verification device, which is described below in conjunction with the accompanying drawings.

[0533] Fig.35 A schematic diagram of a verification device provided in an embodiment of the present application. This embodiment provides a verification device 3500, including:

[0534] The determining unit 3502 is used to determine the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked according to the configuration information of the flowchart to be processed;

[0535] The determining unit 3502 is further configured to determine a target verification method according to the to-be-verified attribute of the to-be-verified field;

[0536] The verification unit 3504 is used to verify the field to be verified according to the target verification method, obtain a field verification result, and determine the verification result of the flowchart to be processed according to the field verification result.

[0537] Optionally, the flowchart to be processed includes a first node;

[0538] The determining unit 3502 is further configured to determine the node type of each first node according to a preset node type set; for each first node, determine an input and output parameter verification method suitable for the first node according to the node type of the first node;

[0539] The verification unit 3504 is further used to perform verification processing on the first node according to the input and output parameter verification method to obtain a node verification result;

[0540] When determining the verification result of the flowchart to be processed according to the field verification result, the verification unit 3504 performs the following steps:

[0541] The verification result of the flowchart to be processed is determined according to the node verification result and the field verification result.

[0542] Optionally, when the target verification mode includes a first verification mode, the field verification result includes a first verification result, and when the verification unit 3504 performs verification processing on the field to be verified according to the target verification mode and obtains the field verification result, the following steps are performed:

[0543] According to the field to be checked, determining in the configuration information of the flowchart to be processed a first data identifier representing input and output parameter data and a first variable identifier of a first variable for which the field to be checked is targeted;

[0544] According to the first data identifier, query the data type of the input and output parameter data in the correspondence relationship between the pre-configured data identifier and the data type, and according to the first variable identifier, query the data type of the first variable in the correspondence relationship between the pre-configured variable identifier and the data type;

[0545] Comparing the data type of the input and output parameter data with the data type of the first variable to obtain a first comparison result;

[0546] A first verification result of verifying the field to be verified by using the first verification method is determined according to the first comparison result.

[0547] Optionally, when the target verification mode includes a second verification mode, the field verification result includes a second verification result, and when the verification unit 3504 performs verification processing on the field to be verified according to the target verification mode and obtains the field verification result, the following steps are performed:

[0548] According to the field to be checked, determining the second variable identifier of the second variable located at both ends of the preset type symbol and the third variable identifier of the third variable in the configuration information of the flowchart to be processed;

[0549] According to the second variable identifier, querying the data type of the second variable in the pre-configured correspondence between the variable identifier and the data type, and, according to the third variable identifier, querying the data type of the third variable in the correspondence between the variable identifier and the data type;

[0550] Performing a comparison process according to the data type of the second variable and the data type of the third variable to obtain a second comparison result;

[0551] A second verification result of verifying the field to be verified by using the second verification method is determined according to the second comparison result.

[0552] Optionally, when the target verification mode includes a third verification mode, the field verification result includes a third verification result, and when the verification unit 3504 performs verification processing on the field to be verified according to the target verification mode and obtains the field verification result, the following steps are performed:

[0553] Obtain the target speech identifier of the field to be checked;

[0554] Verify whether the speech synthesis parameter of the target speech identification exists, and obtain a first verification sub-result;

[0555] Verify whether the audio data of the target speech mark is uploaded, and obtain a second verification result;

[0556] A third verification result of verifying the field to be verified by using the third verification method is determined according to the first syndrome result and the second syndrome result.

[0557] Optionally, the determining unit 3504 is further configured to:

[0558] Determine the risk level of the field to be checked in the configuration information of the flowchart to be processed, and obtain a target risk level;

[0559] The verification device 3500 further includes:

[0560] A generating unit is used to generate risk control prompt information that meets the target risk level if the field verification result indicates that the verification of the field to be verified fails.

[0561] Optionally, the verification unit 3508 is further used to:

[0562] After the flowchart to be processed is modified, if a parameter change of the field to be checked in the configuration information of the flowchart to be processed is detected, a secondary check is performed on the field to be checked according to the target check method.

[0563] In an embodiment of the present application, the verification device includes: a determination unit, which is used to determine the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked according to the configuration information of the flowchart to be processed; the determination unit is also used to determine the target verification method according to the attributes to be checked of the fields to be checked; the verification unit is used to verify the fields to be checked according to the target verification method, obtain the field verification result, and determine the verification result of the flowchart to be processed according to the field verification result. Therefore, considering that the flowchart to be processed may include multiple fields to be checked, each field to be checked may have some personalized characteristics, and it is difficult to verify all the fields to be checked through a unified verification method, the target verification method is determined according to the attributes to be checked of the field to be checked, and the field to be checked is verified according to the target verification method to obtain the field verification result, which is conducive to reusing some ready-made verification methods by configuring the attributes to be checked of the field to be checked when processing the verification work of the personalized field to be checked. Compared with designing a corresponding personalized verification process for each field to be checked, the repeated verification configuration work is reduced, and in the overall verification process of the flowchart to be processed, when processing each field to be checked in turn, there is no need to rely on manual experience to switch the verification method, thereby improving the verification efficiency of the flowchart to be processed.

[0564] Corresponding to the verification method described above, based on the same technical concept, an embodiment of the present application further provides an electronic device, which is used to execute the verification method provided above. Fig.36 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0565] like Fig.36As shown, the electronic device may have relatively large differences due to different configurations or performances, and may include one or more processors 3601 and memory 3602, and the memory 3602 may store one or more storage applications or data. Among them, the memory 3602 may be a short-term storage or a persistent storage. The application stored in the memory 3602 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the electronic device. Furthermore, the processor 3601 may be configured to communicate with the memory 3602 and execute a series of computer executable instructions in the memory 3602 on the electronic device. The electronic device may also include one or more power supplies 3603, one or more wired or wireless network interfaces 3604, one or more input / output interfaces 3605, one or more keyboards 3606, etc.

[0566] In a specific embodiment, the electronic device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions for the electronic device, and the one or more programs configured to be executed by one or more processors include the following computer executable instructions:

[0567] According to the configuration information of the flowchart to be processed, determine the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked;

[0568] Determine the target verification method according to the attributes of the field to be verified;

[0569] The check field to be checked is checked according to the target check method to obtain the field check result, and the check result of the flowchart to be processed is determined according to the field check result.

[0570] The computer-readable storage medium provided in this embodiment is used to store computer-executable instructions. When the computer-executable instructions are executed by a processor, the following process is implemented:

[0571] According to the configuration information of the flowchart to be processed, determine the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked;

[0572] Determine the target verification method according to the attributes to be verified of the field to be verified;

[0573] The check field to be checked is checked according to the target check method to obtain the field check result, and the check result of the flowchart to be processed is determined according to the field check result.

[0574] It should be noted that the embodiment of the computer-readable storage medium in this specification and the embodiment of the verification method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding method mentioned above, and the repeated parts will not be repeated.

[0575] Another embodiment of the present disclosure further provides a computer program product, the computer program product including a computer program, and when the computer program is executed by a processor, the following process is implemented:

[0576] According to the configuration information of the flowchart to be processed, determine the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked;

[0577] Determine the target verification method according to the attributes to be verified of the field to be verified;

[0578] The check field to be checked is checked according to the target check method to obtain the field check result, and the check result of the flowchart to be processed is determined according to the field check result.

[0579] The computer program product in the embodiment of the present disclosure can implement each process of the above-mentioned verification method embodiment and achieve the same effect and function, which will not be repeated here.

[0580] In an embodiment of the present application, first, according to the configuration information of the flowchart to be processed, the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked are determined; then, according to the attributes to be checked of the fields to be checked, the target verification method is determined; finally, the fields to be checked are verified according to the target verification method to obtain the field verification result, and the verification result of the flowchart to be processed is determined according to the field verification result. In this way, considering that the flowchart to be processed may include multiple fields to be checked, each field to be checked may have some personalized characteristics, and it is difficult to verify all the fields to be checked by a unified verification method, by determining the target verification method according to the attributes to be checked of the fields to be checked, and verifying the fields to be checked according to the target verification method to obtain the field verification result, it is conducive to reusing some ready-made verification methods by configuring the attributes to be checked of the fields to be checked when processing the verification work of personalized fields to be checked. Compared with designing a corresponding personalized verification process for each field to be checked, repeated verification configuration work is reduced, and in the overall verification process of the flowchart to be processed, when processing each field to be checked in turn, there is no need to rely on manual experience to switch the verification method, thereby improving the verification efficiency of the flowchart to be processed.

[0581] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0582] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the embodiments of the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this specification may adopt the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0583] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable electronic device to produce a machine, so that the instructions executed by the processor of the computer or other programmable electronic device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0584] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable electronic device to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0585] These computer program instructions may also be loaded onto a computer or other programmable electronic device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0586] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0587] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0588] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0589] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0590] Embodiments of the present application may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communications network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0591] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0592] The above description is only an embodiment of this document and is not intended to limit this document. For those skilled in the art, this document may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this document should be included in the scope of the claims of this document.

Claims

1. A verification method, characterized in that: include: Determine, according to the configuration information of the flowchart to be processed, the fields to be checked in the flowchart to be processed and the attributes to be checked of the fields to be checked; Determining a target verification method according to the to-be-verified attribute of the to-be-verified field; The field to be checked is checked according to the target check method to obtain a field check result, and the check result of the flowchart to be processed is determined according to the field check result.

2. The method according to claim 1, characterized in that The flowchart to be processed includes a first node; the method further includes: Determine the node type of each first node according to a preset node type set; For each first node, determining an input and output parameter verification method suitable for the first node according to the node type of the first node; Perform verification processing on the first node according to the input and output parameter verification method to obtain a node verification result; Determining the verification result of the flowchart to be processed according to the field verification result includes: The verification result of the flowchart to be processed is determined according to the node verification result and the field verification result.

3. The method according to claim 1, characterized in that: In the case where the target verification method includes a first verification method, the field verification result includes a first verification result; and the verification process is performed on the field to be verified according to the target verification method to obtain the field verification result, including: According to the field to be checked, determining in the configuration information of the flowchart to be processed a first data identifier representing input and output parameter data and a first variable identifier of a first variable for which the field to be checked is targeted; According to the first data identifier, query the data type of the input and output parameter data in the correspondence relationship between the pre-configured data identifier and the data type, and according to the first variable identifier, query the data type of the first variable in the correspondence relationship between the pre-configured variable identifier and the data type; Comparing the data type of the input and output parameter data with the data type of the first variable to obtain a first comparison result; A first verification result of verifying the field to be verified by using the first verification method is determined according to the first comparison result.

4. The method according to claim 1, characterized in that: In the case where the target verification method includes the second verification method, the field verification result includes the second verification result; and the verification processing of the field to be verified according to the target verification method to obtain the field verification result includes: According to the field to be checked, determining the second variable identifier of the second variable located at both ends of the preset type symbol and the third variable identifier of the third variable in the configuration information of the flowchart to be processed; According to the second variable identifier, querying the data type of the second variable in the pre-configured correspondence between the variable identifier and the data type, and, according to the third variable identifier, querying the data type of the third variable in the correspondence between the variable identifier and the data type; Performing a comparison process according to the data type of the second variable and the data type of the third variable to obtain a second comparison result; A second verification result of verifying the field to be verified by using the second verification method is determined according to the second comparison result.

5. The method according to claim 1, characterized in that In the case where the target verification mode includes the third verification mode, the field verification result includes the third verification result; and the verification processing of the field to be verified according to the target verification mode to obtain the field verification result includes: Obtain the target speech identifier of the field to be checked; Verify whether the speech synthesis parameter of the target speech identification exists, and obtain a first verification sub-result; Verify whether the audio data of the target speech mark is uploaded, and obtain a second verification result; A third verification result of verifying the field to be verified by using the third verification method is determined according to the first syndrome result and the second syndrome result.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: Determine the risk level of the field to be checked in the configuration information of the flowchart to be processed, and obtain a target risk level; After the field to be checked is checked according to the target check method and a field check result is obtained, the method further includes: If the field verification result indicates that the verification of the field to be verified fails, risk control prompt information that meets the target risk level is generated.

7. The method according to any one of claims 1 to 5, characterized in that: After the field to be checked is checked according to the target check method and a field check result is obtained, the method further includes: After the flowchart to be processed is modified, if a parameter change of the field to be checked in the configuration information of the flowchart to be processed is detected, a secondary check process is performed on the field to be checked according to the target check method.

8. An electronic device, characterized in that: include: processor; And, a memory configured to store computer executable instructions, which, when executed, cause the processor to perform the verification method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store computer-executable instructions, and the computer-executable instructions, when executed by a processor, implement the verification method according to any one of claims 1 to 7.

10. A computer program product, characterized in that The invention comprises a computer program, which implements the verification method according to any one of claims 1 to 7 when executed by a processor.

Images