Systems and methods of implementing platforms for bot interfaces within an intelligent development platform
The present disclosure relates to the development and design of bot interfaces and, more particularly, to one or more components, systems and methods of an intelligent development and design platform configured to assist users in the design, development and deployment of bot applications.
1. A computer-implemented method for creating bot applications, the method comprising:
receiving one or more tags corresponding to a scene within a designer view of a designer tool, implemented using a computing system, wherein the one or more tags further comprise one or more tags of one or more utterances of the scene as requiring a service call configured to link to an external computing system;
providing, in a shared database between the designer tool and a developer tool, one or more shared definitions corresponding to the scene, wherein the one or more shared definitions are defined as a database schema that includes database entities used to: define a plurality of attributes corresponding to a conversation within the scene, and create one or more nodes within a dialog task based on the conversation; and
creating automatically the dialog task in a developer view of the developer tool using the one or more shared definitions from the shared database corresponding to the scene wherein the one or more shared definitions comprise the one or more tags that are associated with one or more service nodes configured to link to an external computing system, the dialog task being implemented using the computing system and comprising the one or more nodes corresponding to the scene.
2. The computer-implemented method of claim 1 , wherein the one or more shared definitions within the shared database are used to create both the developer view and the designer view.
3. The computer-implemented method of claim 1 , wherein the shared database further comprises records that are used to output instructions to create part of the designer view or the developer view.
4. The computer-implemented method of claim 1 , wherein two or more of the database entities comprise a one-to-one, a one-to-many, or a many-to-one relationship with each other, and wherein values of the plurality of attributes of the two or more of the database entities are populated in real-time when the scene is created.
5. The computer-implemented method of claim 1 , wherein the at least one of the attributes is used to create a visualization of the designer view and the developer view.
6. The computer-implemented method of claim 1 , wherein the scene includes an entity and an entity tag, and a change of the entity tag in the scene automatically reflects as a change in an entity type in the dialog task using the one or more shared definitions.
7. The computer-implemented method of claim 1 , wherein the one or more nodes comprise an entity node, a message node, an intent node, a service node or a script node based on the one or more shared definitions.
8. The computer-implemented method of claim 1 , wherein the scene includes a sequence of message texts corresponding to a message type comprising at least one of: a user message, a bot question or a bot information;
the message texts are associated with tag types and tag values;
the sequence of message texts of the user message are associated with a sequence of the bot question and the bot information; and
the sequence of the bot question and the bot information are linked to at least another bot question and/or bot information based on the user message;
wherein the message type, the tag types and the tag values are defined as the one or more definitions.
9. The computer-implemented method of claim 1 , wherein the one or more shared definitions further comprise one or more utterances of the scene tagged as a response to a confirmation question.
10. A system comprising:
a processor; and
a memory comprising programmed instructions stored thereon with the processor configured to execute the stored programmed instructions to:
receive one or more tags corresponding to a conversation design within a designer view of a designer tool, wherein the one or more tags further comprise one or more tags of one or more utterances of the scene as requiring a service call configured to link to an external computing system;
create a bot definition in a developer view of a developer tool; and
provide, in a shared database between the designer tool and the developer tool, one or more shared definitions corresponding to the created conversation design and the created bot definition such that any change in the created conversation design or the created bot definition automatically changes the corresponding bot definition or the conversation design, respectively, based on the one or more shared definitions, wherein the one or more shared definitions are defined as a database schema that includes database entities used to: define a plurality of attributes corresponding to a conversation within the conversation design, and create one or more nodes within the bot definition based on the conversation, wherein the one or more shared definitions comprise one or more the one or more tags that are associated with one or more service nodes configured to link to an external computing system.
11. The system of claim 10 , wherein the bot definition comprises a dialog task and the conversation design comprises a scene.
12. The system of claim 10 , wherein the at least one of the attributes is used to create a visualization of the designer view and the developer view.
13. The system of claim 11 , wherein the scene includes an entity and an entity tag, and a change of the entity tag in the scene automatically reflects as a change in an entity type in the dialog task using the one or more shared definitions.
14. The system of claim 10 , wherein the one or more shared definitions within the shared database are used to create both the developer view and the designer view.
15. The system of claim 10 , wherein the shared database further comprises records that are used to output instructions to create part of the designer view or the developer view.
16. The system of claim 10 , wherein two or more of the database entities comprise a one-to-one, a one-to-many, or a many-to-one relationship with each other, and wherein values of the plurality of attributes of the two or more of the database entities are populated in real-time when the conversation design is created.
17. The system of claim 10 , wherein the one or more nodes comprise an entity node, a message node, an intent node, a service node or a script node based on the one or more shared definitions.
18. A non-transitory computer readable medium having stored thereon instructions comprising executable code which when executed by one or more processors, causes the one or more processors to:
receive one or more tags corresponding to a scene within a designer view of a designer tool, implemented using a computing system, wherein the one or more tags further comprise one or more tags of one or more utterances of the scene as requiring a service call configured to link to an external computing system;
provide, in a shared database between the designer tool and a developer tool, one or more shared definitions corresponding to the scene, wherein the one or more shared definitions are defined as a database schema that includes database entities used to: define a plurality of attributes corresponding to a conversation within the scene, and create one or more nodes within a dialog task based on the conversation; and
create automatically the dialog task in a developer view of the developer tool using the one or more shared definitions from the shared database corresponding to the scene wherein the one or more shared definitions comprise the one or more tags that are associated with one or more service nodes configured to link to an external computing system, the dialog task being implemented using the computing system and comprising the one or more nodes corresponding to the scene.
19. The non-transitory computer readable medium of claim 18 , wherein the one or more shared definitions shared within the shared database are used to create both the developer view and the designer view.
20. The non-transitory computer readable medium of claim 18 , wherein the shared database further comprises records that are used to output instructions to create part of the designer view or the developer view.
21. The non-transitory computer readable medium of claim 18 , wherein two or more of the database entities comprise a one-to-one, a one-to-many, or a many-to-one relationship with each other, and wherein values of the plurality of attributes of the two or more of the database entities are populated in real-time when the scene is created.
22. The non-transitory computer readable medium of claim 18 , wherein the at least one of the attributes is used to create a visualization of the designer view and the developer view.
23. The non-transitory computer readable medium of claim 18 , wherein the scene includes an entity and an entity tag, and a change of the entity tag in the scene automatically reflects as a change in an entity type in the dialog task using the one or more shared definitions.
24. The non-transitory computer readable medium of claim 18 , wherein the one or more nodes comprise an entity node, a message node, an intent node, a service node or a script node based on the one or more shared definitions.