What is the suggestion for property tables?

At the beginning, the table scheme has to be decided by necessities.

* Our suggestion is like below;

* Create a property type table to define the property items.

* Create a property type description table to give further details for property items.

Also create your own tables what you want to relate with property items. E.g. you can settings menu if you want to manage settings dynamically.

This sample was prepared for settings menu and was created property items to the related settings menu. Please keep in mind that you have lots of options if you want to use that feature in your projects or solution packs.

Lets start to create a database
The database creation is the first part of the dynamic form scenario. The database name can be the different from the sample and no any rule to use. 

Creating the table for definition of property

The list is not a pattern and dreamers can create their own table scheme for the management. Also take into consider that the property types in the same table can be used for another item which can be set by this option.

How to create property type table?
With this table, you can determine which type of fields can be used for property feature.

How can i design the property type fields?

You should consider that at least one of the field has to be set as an identifier of property type. The name description to use is completely free.

Creating a table output for property type table

In order to use in future in the form management, we should add the unique identifier to the table output list.

Creating a description table for property type items

This is optional. If you want to give further details to your users to have and idea how to use the current feature, being advised to create the table.

Creating description fields for the table of property type description
You need to add fields to the description table as it is in the sample screen. The only critical point is that to have the same field which was used in the property type table.

Creating a table input for description table

The table input is being added to the list because of the field which was defined in the property type table. This adding means is that the value of defined field will be transferred to the related field in the current table.

Example : Creating a table for settings menu

This is the example of settings menu. This is an optional and users can create their own design instead of this one.

Setting menu - table fields

Settings menu - table outputs

How to create the table of property injection?
This is the connection table between property types and related object to have parameter options. 

What is the property injection fields?

The injection fields are explained below;

* claimID : This field expresses the related content which is going to be list in the tool

* defaultValue : This is optional and if you want to set a default value when any data to the table, and the value is null or empty, the default value will be inserted to the related field automatically.

* designLabelTiID : This is the label tool of the form. Aigap will give an option to pick a tool from the current tool list.

* designTiID : This is the value entry tool of the form. Aigap will give an option to pick a tool from the current tool list.

* designToolTypeID : You have to pick a component on this option. This option declares the type of related tool and sets the item as collectible object.

* injectionID : This is the unique identifier for the current table. The field name is not static and dreamer can rename this item whatever they want. This item will be assigned to the dynamic form afterwards.

* inputAlias : This is optional. If you have a content and any choice from the list and if you want to use the collected data in the future elements, you can enter the name of value from this option.

* propertyTypeID : This is the transferred data from property type table.

* setMenuID : This is the transferred data from settings menu table.

* sortID: Defines the order number of the list

* valueText4claimID : If you have this type of model in your table, you want to store the name in this field with the related ID. In this part: The content name will be stored in this field along with the contentID (claimID)

* valueText4designLabelTiID : Contains the name of design tool for label. Same description is available with valueText4claimID. 

* valueText4designTiID : Contains the name of design tool for value. Same description is available with valueText4claimID.

* valueText4designToolTypeID : Contains the name of component. Same description is available with valueText4claimID.

Property injection - table inputs

Property injection - table output

How to create the table of property injection value?

This is the table of storing the entered value for prepared injections. The table type is picked as partition table because of the data will be stored in a separated table of network owner based. This is optional and dreamers can use standard table type if they designed their project capabilities.

What is the fields for property injection value?

Those are the details of fields;

* injectionID : This is the ID which comes from the injection table which is created beforehand.

* isID : This is the image server ID. This is mandatory if dreamer wants to have a image or movie storing option in the table. The field name has to define as this name and it is static.

* smpivID : This is the unique ID for this table.

* value : This is the value of the chosen item. The name is static and has to be defined as 'value'

* valueText : This is the name of value if there is a list and injection has content in it. The name is static and has to be defined as 'valueText'

Property injection value - table inputs

Property injection value - table outputs

Property injection value - table partition

This form is the definition form for if they want to split the data to different dynamic tables.

About Us
Contact Us
Terms and Conditions
©2022, all right reserved
  • Hi there, i am here to help you
Hi there, i am here to help you
We use cookies to improve your browsing experience and personalize content.
You can manage your preferences in our Privacy Policy.