text
stringclasses 2
values |
|---|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements and provided domain entities.
### requirements ###
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
### domain entities ###
Use `EntityName.propertyName` from given domain entities:
- Order
```yaml
entities:
Order:
date: date
title: text
description: text
customer: text
price: number
```
### task ###
Provide the definition of the user interface for the app described in #requirements# in YAML format.
Follow #instructions# to produce the #output format# for the entire application.
### instructions ###
1. Provide YAML according to format in #output format# section to solve the #task#.
2. Use `EntityName.propertyName` from #domain entities#:
- Order
3. You are restricted to use components from the list:
- fields
- tables
- button
4. You are can use components from the list only if explicitly asked to:
- statistics
5. You are restricted to use fieldType from the list:
- text
- numeric
- date
6. Values of pageTitle have to be written in CamelCase.
7. secondarySignDisplay value can be only "positive" or "negative"
### output format ###
```yaml
application:
pages:
- title: pageTitle
fields:
- type: fieldType
label: labelName
property: EntityName.propertyName
- type: fieldType
label: labelName
property: EntityName.propertyName
button:
- label: labelName
events: eventName
tables:
- label: labelName
entity: EntityName
properties:
- property: EntityName.propertyName
- property: EntityName.propertyName
statistics:
- label: labelName
primaryValueLabel: primaryLabelName
primaryValue: primaryValueName
secondaryValueLabel: secondaryLabelName
secondaryValue: secondaryValueName
secondarySignDisplay: secondarySignDisplay
```
```yaml<|end|>
<|assistant|>application:
pages:
- title: OrdersDisplay
tables:
- label: Orders
entity: mainEntity
properties:
- property: mainEntity.order_date
- property: mainEntity.order_title
- property: mainEntity.order_description
- property: mainEntity.order_customer
- property: mainEntity.order_price
button:
- label: Add
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersCreate
- title: OrdersCreate
fields:
- type: date
label: Creation Date
property: mainEntity.order_date
- type: text
label: Title
property: mainEntity.order_title
- type: text
label: Description
property: mainEntity.order_desctiption
- type: text
label: Customer
property: mainEntity.order_customer
- type: float
label: Customer
property: mainEntity.order_price
button:
- label: Save
events:
click:
- db_operation:
entity: mainEntity
operation: save
- run:
name: validateInputData
- navigate:
name: OrdersDisplay<|end|>
|
<|user|>You are a web application designer that creates simple and portable user interface based on user requirements.
### requirements ###
I need mini CRM for my ecommerce store
### task ###
List domain entities for the app described in #requirements# that will represent the database schema in YAML format.
Follow #instructions# to produce the #output format#
### instructions ###
1. Use format in #output format# section to solve the #task#.
2. If propertyName has a foreign key, then write propertyName in next format:
```yaml
propertyName: EntityName
```
3. Use next values for propertyType:
- text
- integer
- float
- date
### output format ###
```yaml
entities:
EntityName:
propertyName: propertyType
```
```yaml<|end|>
<|assistant|>entities:
Order:
date: date
title: text
description: text
customer: text
price: number<|end|>
|
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- 2