# Hello World with Pro Config

{% hint style="info" %}
Key Concepts In This Chapter:\
\- Render Types\
\- Inputs/Outputs
{% endhint %}

### "Hello World" Example

We start by building a simple bot that can render and output “Hello World” with Pro Config. Here is what the config looks like:

{% hint style="info" %}
For better readability of this code block, you could copy and paste this into any code editor app like [VS Code](https://code.visualstudio.org) and select JSON as its format.&#x20;
{% endhint %}

{% code lineNumbers="true" %}
```json
{
  "type": "automata",
  "id": "hello_demo",
  "initial": "home_page_state",
  "inputs": {},
  "outputs": {},
  "transitions": {},
  "states": {
    "home_page_state": {
      "inputs": {},
      "tasks": [],
      "outputs": {},
      "render": {
        "text": "Hello World! Welcome to this demo. Click 'Start' to chat!",
        "buttons": [
          {
            "content": "Start",
            "description": "Click to Start.",
            "on_click": "start_demo"
          }
        ]
      },
      "transitions": {
        "start_demo": "home_page_state"
      }
    }
  }
}
```
{% endcode %}

Above is the syntax with all the available fields for a Pro Config JSON file. Using the code above should allow you to do the following interaction with your bot.

<figure><img src="https://2005308380-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSXDXcSB3MMwWmh9UaOI6%2Fuploads%2FZL0X77MvdcFKUKvDozCv%2Fimage.png?alt=media&#x26;token=39214b2e-c04e-48c8-a88a-47e3f9b1ebc2" alt=""><figcaption><p>Hello world using pro config</p></figcaption></figure>

In Pro Config, each `Automata` can be defined using a JSON file. An `Automata`has a unified `id` and several states as its children. In the simple example above, the `Automata`has only one state called `home_page_state` which simply outputs an intro message. It also has a button called `Start` which can jump to  `home_page_state` itself like an iteration (we will get to more complicated transitions in the future.)

### Automata and Atomic States

#### AtomicState

An atomic state is a state executing real tasks, which usually are small functional modules, such as LLM module and TTS module.

These are usually embedded as a part of a bigger automata.

#### Automata

`Automata` shares many fields with `AtomicState`. They differ by the following:

* `AtomicState` has the lack of `properties.is_chat_allowed` and `tasks` fields.
* The different special events it can handle.
* `initial` , `states` and `context` fields.

Put in simpler words, one `Automata` can contain different `AtomicState`. Your Pro Config should be of the type `Automata` and tasks should be `AtomicState`.

For more information about the difference between AtomicState and Automata, please refer to the [dev doc](https://docs.myshell.ai/product-manual/create/pro-config-mode-beta/basic/automata).

### Defining Inputs/Outputs

The states of an `Automata`is a dictionary of `AtomicState`.  An `AtomicState` take inputs from the user, process some tasks, return outputs, and render some content (such as text/image/button). In the example above, we rendered a text message and a button. \
\
We will now demonstrate how to add `inputs` and `outputs` to an `Automata`

<pre class="language-json" data-line-numbers><code class="lang-json"><strong>{
</strong>  "type": "automata",
  "id": "hello_demo",
  "initial": "home_page_state",
  "states": {
    "home_page_state": {
      "inputs": {
        "intro_message": {
          "type": "text",
          "user_input": true,
          "default_value": "Hi, this is your Pro Config Tutorial Bot"
        },
        "tts_widget_url": {
          "type": "text",
          "user_input": true,
          "default_value": "https://app.myshell.ai/widget/mEjUNr"
        }
      },
      "outputs": {
        "intro_message": "{{intro_message}}",
        "voice_id": "{{tts_widget_url}}"
      },
      "render": {
        "text": "Hello Word! Welcome to this demo. Click 'Start' to chat!",
        "buttons": [
          {
            "content": "Start",
            "description": "Click to Start.",
            "on_click": "start_demo"
          }
        ]
      },
      "transitions": {
        "start_demo": "home_page_state"
      }
    }
  }
}
</code></pre>

In the example above, we are doing the following:

*   **Lines 7-18:** Gathering inputs `intro_message` and `tts_widget_url` from the user. The type is `text` which means that the user will be prompted to input data (unlike `IM` where user needs to type in the chat to provide an input). If the `user_input` property is `false`, the user will not be prompted to input via a form, and a new variable with the value of `default_value` will be automatically generated.\


    <figure><img src="https://2005308380-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSXDXcSB3MMwWmh9UaOI6%2Fuploads%2FKEItANvwzRTj0QXxS3aq%2Fimage.png?alt=media&#x26;token=31bc1f3c-39b5-4a0f-bfc2-3f192e7891e0" alt=""><figcaption><p>Input fields prompted to user when input type <code>text</code> is used.</p></figcaption></figure>
* **Lines 19-22:** The `output` section in pro config runs after all the tasks are completed for the automata or atomic state. In this section, you can create or manipulate variables. This is also the place you can manipulate any variables you create in `context`. If you want to store output for the task performed, this is the way. We use an expression wrapped by double curly braces `{{expression}}` to assign the value of an output variable. The expression should be written in [JavaScript](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide), adhering to the [ECMAScript 5.1](https://262.ecma-international.org/5.1/) standard, as we currently support only this version. In the example, we are using this section to save the inputs to variables.

Now, you have learned how to build a basic app with inputs and outputs. In the next chapter, we will learn how to build a workflow to achieve more complicated functionalities empowered by AI Modules.

