Skip to main content

​
Testing/Running your assistant

Once you have completed building your assistant you can test it is working correctly by clicking the Run button at the top right This will run the workflow and your assistant should spring to life and prompt you to ask them a question From here you can interact with the assistant as you would any other person. And the assistant in term will respond in turn. Now that you have tested and checked it is working as expected its time to get it published so that you and others can start using it in a production setting

​
Publishing your assistant

To begin the publishing process you can click the top right Publish button. This will prompt us to enter a deployment message into the text box and click the Confirm button to action the publishing process Importantly the system validates that nothing is unconnected before publishing And so if you have forgotten to connect u all your components the system will throw up an error and tell you to go back and fix the problem, which ensures that only validated assistants make it to production. Once we fix any errors we can try again as if all is well we will see the assistant being published After this process is completed we can see that the assistant is now online and that the version number has been incremented Congratulations, your assistant has been successfully deployed and now you and others will always have an assistant to help you with this specific task.

​
Taking your assistant offline

Sometimes you may want to take an assistant offline, for example to do maintanance, etc. This process is easy, simply hitt the toggle and the system will deactive the assistant after which your assisant will now be offline.

​
A note on versions

Importantly any changes you have made which are visible in the current state of the canvas below are always considered a draft version. That means the current canvas, i.e. your current draft of the assistant is the thing which will be deployed when you click publish. Deploying this draft will automatically version the new assistant as v2 (or v5 if v4 was the last version, etc) The currently deployed version is clearly indicated with the live label. Showing you which version of the assistant is currently live and answering questions. You may be wondering what happens to the old v1 assistant when a new version is deployed, does it dissapear? No, certainly not, it gets archived in history. And you are able to see all of the versions of your assistants in the version section above the canvas as previously shown. This means that at any point in time If you can roll-back and re-deploy an older version of the assistant. all you need to do is click the older version you wish to re-deploy and click the preview button next to the version info. This will cause a preview section to appear at the top of the canvas. Clicking the “Replace draft with this version”, will prompt you to confirm that you want to overwrite the canvas i.e. your current unpublished changes and that you want to roll back to the older version. Doing so will show a message and confirm that your canvas has been changed back to v1 You will note however that v2 is still the version that is online. That is because, as we mentioned before, the canvas is our current draft. All we did was replace our current canvas with v1. In order for the changes to take effect, i.e. in order to fully roll back v1 we must now publish our draft/the current canvas using the usual process Lets give it a roll back comment, and confirm. And thats it. We have successfully rolled back to v1 and it is now live in production. Note however that this is now v3. i.e. v1 and v3 are the same. And that as always we can see the full deployment history of all version v1,v2,v3, and our current draft.

​
What’s Next?

Interact with Your Assistant

Learn how to use and manage your deployed assistant
⌘I