Rasa dialogue robot helpdesk (V)

One 、HelpDesk Analysis of verification function in business process of intelligent dialogue robot

stay HelpDesk When an intelligent dialogue robot runs a business process , The information entered by the user needs to be verified , The background microservice can only be called after the verification is passed , If the validation fails , Dialogue robots can continue to let users provide correct information , Do not submit until all the information to be collected has been verified form. Pass below Rasa Provided interactive Mode demonstrates how a dialogue robot verifies user input information . When the user queries the created incident When , Enter the following information ：

NLU The model correctly identifies the user's intention , Carry on ：

Continue to follow the prompts to run this form：

At this time, the dialogue robot asks the user to provide email Information , Input 123：

NLU The model identifies the user's intention as out_of_scope, And the prompt cannot be extracted email, there NLU Model means NLU pipeline The... Used in the configuration file duckling, Input information 123 Obviously not in line with email Format , therefore duckling Unable to extract email.

If you enter the following information , Even if it is not an effective email Address ：

At this time, it seems that the model can extract this email Information , Carry on ：

Slot “email” The value just entered has been filled in , see action server Output log for ：

You can see Rasa action server received Rasa server Authentication request sent , Then the validation micro service is successfully executed validate_incident_status_form, We are domain You can see that the following two validations are configured action:

As mentioned earlier HelpDesk The main business process of the dialogue robot includes creating according to user input incident And queries that have been created incident The state of , In these two processes, we will use open_incident_form and incident_status_form To collect user information , So for each form Will define a validate action To verify that each form Whether the information to be collected meets the requirements .

Two 、HelpDesk Dialogue robot business process validation microservice code parsing

1. establish incident Validate microservices

The following is the micro service class , Inherited from Rasa SDK Of form Validate framework classes FormValidationAction

stay name Method needs to return in domain Defined in the configuration action name:

Here is form The definition of ：

In the validation micro service, you can collect data according to the above definition slots The information provides corresponding verification methods , Only two important are provided here slot Information verification method .

This method calls the internal method _validate_email Execute specific validation logic ：

First, check the passed in parameter values ：

According to the user provided email From a third party incident Get the identity of the current user in the management system id：

- If caller_id If it is valid, it returns caller_id and email

- If you cannot return a single caller_id, shows email Invalid , At this point, it is necessary to slot The value of the set None

- If an error message appears , Also need to put slot The value of the set None：

The following method verifies priority Whether it works ：

If priority Valid returns the value , Otherwise, you need to slot The value of the set None, And call the template method utter_no_priority Output information to users ：

 2.  Inquire about incident Status verification microservice

The following is the micro service class , Inherited from Rasa SDK Of form Validate framework classes FormValidationAction, According to the naming convention , The name of the microservice class should be prefixed with ”Validate”：

stay name Method needs to return in domain Defined in the configuration action name:

Here is form The definition of ：

This form Just collect email Information , So there is only one verification method ：

It's actually calling the same internal method _validate_email To achieve email Verification logic of .