Handwritten Signature
Description
| Item | Content |
|---|---|
| Category | Control |
| Storage Type | TableSignature |
| Sortable | No |
| Filterable | No |
Settings
| Setting | Description |
|---|---|
| Allow Empty | Set whether the field is required |
| Allow Multiple Signatures | When enabled, multiple signatures can be uploaded. Changing this will change the storage type of the field |
| Signature Color | Can set the color of the signature stroke |
| Signature Display - Width (pixels) | Can set the display width of the signature image, range: 32~10240 |
| Signature Display - Height (pixels) | Can set the display height of the signature image, range: 32~10240 |
Notes
Because the storage types for single signature and multiple signatures are different, enabling/disabling "Allow Multiple Signatures" may result in partial data loss. Please operate with caution.
Storage Format in Database
| Field Type | Description |
|---|---|
| jsonb | Stores JSON format data, JSON structure see below |
In the data table, handwritten signature field data is stored in JSON format. If multiple signatures are allowed, it is stored as a JSON array. The JSON structure is as follows:
interface TableSignature {
id: string; //ID
accountId: string; //Account ID
accountName: string; //Account Name
uploadTime: Date; //Upload Time
path: string; //Path
}Example 1: Data stored when multiple signatures are not allowed (single selection)
{
"accountId": "skydu2",
"accountName": "skydu2",
"id": "vyu0art5s0reflpad09v7.jpg",
"path": "otxlyqyjacgnx/sr7gnmk90asb2/vyu0art5s0reflpad09v7.jpg",
"uploadTime": 1721359223688
}Example 2: Data stored when multiple signatures are allowed (multiple selection)
[
{
"accountId": "skydu2",
"accountName": "skydu2",
"id": "or3yjjhn0bf98f5uy6j6n.jpg",
"path": "otxlyqyjacgnx/ffr7s7spbxb76/or3yjjhn0bf98f5uy6j6n.jpg",
"uploadTime": 1721295355794
},
{
"accountId": "skydu2",
"accountName": "skydu2",
"id": "ng326htx6ob2ci2c8e7zv.jpg",
"path": "otxlyqyjacgnx/ffr7s7spbxb76/ng326htx6ob2ci2c8e7zv.jpg",
"uploadTime": 1721295370334
}
]File Storage Method
After a handwritten signature is uploaded, it is saved using the shared storage service. The system creates folders for different fields based on the application, data table, and field. The folder naming rules are as follows:
companyId/appId/tableId/fieldIdcompanyIdTeam IDappIdApplication IDtableIdData Table IDfieldIdField ID
Note
The above IDs are all internally generated system IDs, not identifiers.
Access Path
The access path rules for handwritten signature images are as follows. A user token needs to be passed.
Access via handwritten signature path
https://host:port/web${cluster}/file/field/${appId}/${path}?token=${token}Access via handwritten signature ID
https://host:port/web${cluster}/file/field/${appId}/${tableId}/${fieldId}/${fileId}?token=${token}Access via module, field identifier, and handwritten signature ID
https://host:port/web${cluster}/file/fieldkey/${appId}/${tableKey}/${fieldKey}/${fileId}?token=${token}Display Effect


