---
title: Steps to Implement Neuro Solution
slug: neuro-en/steps-to-implement-neuro-solution
description: This document provides valuable insights into the design, configuration, and development process of building a Neuro application. It highlights the significance of accurately designing the application's needs and requirements, incorporating entity models 
docTags: 
createdAt: 2021-10-27T21:51:17.000Z
---



![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/gttG6ErtpIGOo5jl8pxy5_image.png "Figure 1 - Create Neuro Application")

![](https://api.archbee.com/api/optimize/pu5VMc-2TW3GQX4ly5Xp7/Rvmh83s0PWz8_STi8_FVu_image.png "Figure 2 - Business Objects")

:::hint{type="warning"}
**ATTENTION:**

The steps can be found in the CITSmart documentation (docs.citsmart.com).
:::

## Design App

For better development of Neuro applications, it is good practice a previous&#x20;**design of needs and requirements that the application will meet**, also&#x20;include the **entities model** of the data that will travel through the&#x20;application.

A research of the **desired interfaces** and, if the Neuro will be the option to&#x20;use data for services, the **design of the services** that will be automated.

## Neuro Configuration

After Designs, the Application gathering the information regarding the data&#x20;entities of your Neuro Application you will:

1. Create your *DATABASE CONNECTION* and your *NEURO APPLICATION* entry;
2. Verify if you will be going to use any common *DOMAIN* for your installation   &#x20;and create if it is necessary;
3. You will, also, verify the *BUSINESS RULES* for the registration, update or   &#x20;deletion of records in the data entity… you will link those to the Business   &#x20;Object;
4. If you will have forms that will use multiple languages you will create the
   *INTERNATIONALIZATION KEYS*, labels that will be used for all fields in your   &#x20;forms.

## Neuro Development

The configuration step will make us ready to develop the application:

1. Create the *BUSINESS OBJECTS*, containing the data structure of the entity,   &#x20;at this step, you will be able to create the columns, PK's and FK's (assign   &#x20;relationships), link Business rules and Domains you will be able to create   &#x20;CRUD forms and other features;
2. Create *FORMS* related to your Business.

## CITSmart Experience Connection

After you have your Business Objects and Forms created you can:

1. *LINK THE FORM TO A SERVICE* as needed, or
2. *LINK THE FORM TO CITSmart Experience MENU OR TO AN EXPERIENCE CENTER*, this will make you   &#x20;able to maintain tables and additional data that will be not used on a ticket opening.

