Rule Verification (Expired and Not Recommended)

Node Name: name of a node.
Description: details of a node.
Text Variable: variable whose value has been obtained before this node. For example, if a customer wants to query the bills of a month and the customer says "13", this month can be saved as a flow variable using the Semantic Recognition diagram element. In this case, the variable is extracted for month verification.
Rule Expression: expression to verify the type of customer input. For example, if you select month verification, the month format is yyyyMM.

Validate mobile number format (with # and *)
1. * — true branch
2. # — true branch
3. 11-digit number ending with a number sign (#) and starting with 135 to 139, 150 to 152, 157 to 159, 147, 182 to 184, 187, 188, or 198 — true branch
4. 11-digit number ending with a number sign (#) and starting with 1340 to 1348 — true branch
Validate mobile number format (without # or *)
1. 11-digit number starting with 135 to 139, 150 to 152, 157 to 159, 147, 182 to 184, 187, 188, or 198 — true branch
2. 11-digit number starting with 1340 to 1348 — true branch
Validate password format (with # and *)
1. * — true branch
2. # — true branch
3. 6-digit number — true branch
Validate password format (with *)
1. * — true branch
2. 6-digit number — true branch
Validate mobile number (with # and *)
1. * — true branch
2. # — true branch
3. 11-digit number — true branch
Validate mobile number (with *)
1. * — true branch
2. 11-digit phone number — true branch
Validate month input
1. * — true branch
2. # — true branch
3. Valid month in yyyyMM format — true branch

Keyboard Input Type: If this parameter is left blank, the month input verification is performed by default (Rule Expression must be set to Validate month input). The entered month must be in yyyyMM format.
- keyBoard_phone: input from a phone keyboard. Enter this value when the OpenEye or a mobile phone is used.
- checkoldpassword: input from a password keyboard.
Variable: variable for saving customer input.
Context: used to filter intentions to be matched to improve the matching speed. When Keyboard Input Type is set to checkoldpassword, this parameter is invalid, because semantic recognition is not performed on the keyboard input.

This diagram element is used to verify the customer voice or keyboard input based on rules.

Click the diagram element or drag it to the canvas, and set parameters based on the parameter description.

The following describes how to use the Rule Validation diagram element to verify whether the customer input is a valid month.

Sign in to the AICC and choose Configuration Center > Chatbot Management > Flow Configuration.
Configure an intelligent IVR flow.
1. Choose Flow > Orchestration and click New to add a simple flow.
2. Click + in the Flow Variable area. In the dialog box that is displayed, set the variable name and data type. The default value of the variable will be played to the customer.
  Figure 1 Add Variable
  
  In this example, the Business Interface Invocation diagram element does not invoke an interface. Instead, it is used to assign values to parameters.
  
  Figure 2 Flow orchestration example (Rule Validation diagram element)
  - For the false condition branch of the Robot Reply diagram element, set Reply Variable to FLOW.FalseResponse to reply to the customer with "The month you entered is invalid".
  - For the true condition branch of the Robot Reply diagram element, set Reply Variable to FLOW.TrueResponse to reply to the customer with "The month you entered is valid".
3. Save and publish the flow.
Choose Intelligent Chatbot and bind the flow to a robot.
Choose Intelligent Chatbot. In the last column corresponding to the robot, click Test Call.

In the test dialog box that is displayed, click Start Call to test the robot. If the robot answers that the month is valid or invalid based on the month entered by the customer, the configuration is successful.
Figure 3 Testing the robot