What is the suggestion for property tables? | | At the outset, the table scheme should be decided based on the requirements. Our suggestion is as follows: - Create a property type table to define the property items.
- Create a property type description table to provide further details about the property items.
Also, create your own tables to relate with property items. For example, you can create a settings menu if you want to manage settings dynamically.
This sample was prepared for the settings menu, and property items were created for the related settings menu. Please note that you have numerous options to use this feature in your projects or solution packs.
|
|
Lets start to create a database | | The creation of a database is the first step in the dynamic form scenario. The database name can be different from the sample, and there are no specific rules regarding its usage
|
|
Creating the table for definition of property | | The table schema for management is not limited to a specific list, and users can create their own schema according to their needs. Moreover, property types within the same table can be reused for other items, which can be configured using this option.
|
|
How to create property type table? | | This table allows you to specify the types of fields that can be used for the property feature.
|
|
How can i design the property type fields? | | Please note that at least one field must be set as the identifier for the property type. You are free to choose the name of the identifier field according to your preference.
|
|
Creating a table output for property type table | | To use in the form management in the future, we should add a unique identifier to the table output list.
|
|
Creating a description table for property type items | | This step is optional. If you wish to provide your users with additional details on how to use the current feature, we recommend creating a descriptive table.
|
|
Creating description fields for the table of property type description | | You need to add fields to the description table as shown in the sample screen. The only critical point is to ensure that the field names used in the description table match those used in the property type table.
|
|
Creating a table input for description table | | The table input is being added to the list due to the field defined in the property type table. This means that the value of the defined field will be transferred to the related field in the current table.
|
|
Example : Creating a table for settings menu | | This is an example of a settings menu. It is optional, and users can create their own designs instead of using 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 indicates the related content that will be listed in the tool.
- defaultValue: This field is optional. If you want to set a default value when no data is entered in the table, and the value is null or empty, the default value will be automatically inserted into the related field.
- designLabelTiID: This is the label tool for the form. Aigap will provide an option to select a tool from the current tool list.
- designTiID: This is the value entry tool for the form. Aigap will provide an option to select a tool from the current tool list.
- designToolTypeID: You must select a component from this option. This option specifies the type of related tool and sets the item as a collectible object.
- injectionID: This is the unique identifier for the current table. The field name is not static, and users can rename this item as desired. This item will be assigned to the dynamic form afterwards.
- inputAlias: This field is optional. If you have a content and any choice from the list, and you want to use the collected data in future elements, you can enter the name of the value from this option.
- propertyTypeID: This field contains transferred data from the property type table.
- setMenuID: This field contains transferred data from the settings menu table.
- sortID: This field defines the order number of the list.
- valueText4claimID: If you have this type of model in your table and want to store the name in this field along with the related ID, the content name will be stored in this field along with the contentID (claimID).
- valueText4designLabelTiID: This field contains the name of the design tool for the label. The same description is applicable for valueText4claimID.
- valueText4designTiID: This field contains the name of the design tool for the value. The same description is applicable for valueText4claimID.
- valueText4designToolTypeID: This field contains the name of the component. The same description is applicable for valueText4claimID.
|
|
Property injection - table inputs | | |
|
Property injection - table output | | |
|
How to create the table of property injection value? | | This table is used for storing the values entered for prepared injections. The table type is set as a partition table because the data will be stored in a separate table based on the network owner. However, this is optional, and dreamers can use a standard table type if they designed their project capabilities accordingly.
|
|
What is the fields for property injection value? | | These are the details of the fields in the table: - injectionID: This is the ID that comes from the injection table created beforehand.
- isID: This is the image server ID. It is mandatory if the dreamer wants to have an image or movie storing option in the table. The field name must be defined as "isID," and it is a static name.
- smpivID: This is the unique ID for this table.
- value: This is the value of the chosen item. The name is static and must be defined as "value."
- valueText: This is the name of the value if there is a list, and injection has content in it. The name is static and must 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. |
|
