Joget DX 8 Stable Released
The stable release for Joget DX 8 is now available, with a focus on UX and Governance.
Name | Description |
---|---|
Select File | Extensions supported are:-
|
Import Mode | This would allow you to manage existing records. Choices are:-
|
Validate data? | When checked, value from source will be validated against the specific form element's validator that it is mapped to in the "Column Mappings" property. |
Figure 2: Post submission result in Userview
Figure 3: Import Menu Properties
Name | Description | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Custom ID | Item link slug. Optional field.
| |||||||||||
Label | Menu label. | |||||||||||
Form | Specify on where to store the data by choosing a target form.
| |||||||||||
Column Mapping |
| |||||||||||
Key Column Number | Define column number that defines the record id. Column number starts from zero. | |||||||||||
Start From Row Number | Define which row number to start processing. Row number starts from zero. |
Figure 4: Import Menu Properties - Actions
Name | Description |
---|---|
Confirmation Message | Confirmation Message. |
Message shown when error occur | Message shown when error occur. |
Message shown after data imported | Message shown after data imported. |
Redirection (Hyperlink) | URL to redirect. |
Figure 5: Import Menu Properties - UI
Name | Description |
---|---|
Custom Header | Custom Header in HTML. |
Custom Footer | Custom Footer in HTML. |
Figure 6: Import Menu Properties - Advanced
Name | Description |
---|---|
Userview Key Name | Corresponding element ID in the form set above to be mapped to (same like the mapping in "Column Mapping" above). When defined, the Userview Key value will be saved into the field defined here. |
UTF-8 Encoding Checking? | When checked, it will check the uploaded file if it is a valid UTF-8 encoded file. |
Example:
With the configurations above, we will attempt to import the following data in the screenshot below.
Figure 7: Source data highlighting data that will be imported into the target form's database table (master)
Figure 8: Data written into the form table (master)
Figure 9: Source data highlighting data that will be imported into the target form's subform's database table (child)
Run Time Option | Description |
---|---|
Import new record only | Import only if the import data id value does not exist (match) in the form tabledatabase, i.e. new records only. |
Import new record or update existing record | Import into form table database all records in import data. |
Delete record | Delete record records in form table database if the imported import data id value exist (match) in form tabledatabase. |