Part 2

The second in a three part series that describes Alan Studio and how to start with the Alan Platform. If you haven’t read the first part, we highly recommend that you do so here! 

Customizing Scripts

Let’s continue our work with the Food Ordering demo by asking, “What is this application?”. This intent matches with line 89 of our code. The system should respond with, “This is an example Food Ordering App for ordering pizza, street food, drinks, and desserts”. This response is located on line 90 where we can easily edit the response.

The original response is:

reply(“(This is|It’s a) (just|simple) Food Ordering application for ordering pizzas, street food, drinks, and desserts”));

But we are going to edit it to look like:

reply(“(This is|It’s) (just|simple) Food Ordering example application for (food delivery service|pizza ordering)”));

Once you have made your changes, let’s look at version control.

Version Control

Now that we have customized our scripts, let’s save this script as a separate version.

At the top of the scripting window, you can click the button that says, “Save as New Version” and name this specific version whatever you would like. For this tutorial, we are going to name this version, “v1”, and click save. 

In this window, we have an option to “Run on Production”. This means that this version of code will be in our production server, so we can push it out to any app. If we create edits after this, they will stay on either the development or testing stage, so that our production server is always running the last stable version.

Development Stages

• Development: This stage is where you will create your scripts.
• Testing: The Testing environment is ideal for sending out to QA to ensure our code is being properly tested without being sent to our production unit.
• Production: The version we save on our Production Environment will be sent to our production server for live use within your application.

Logs

At the bottom of the screen, you will also see a bar for logs and other analytics. This will show you all the user interactions so you can see the user commands and responses as well as the unrecognized inputs from Alan.

You have now learned about customizing scripts, version control, development stages, and logs. In our next and final blog post, we will begin embedding our script into a live iOS application with Xcode.