Data-Driven Editor
You can add this widget to your workflow as a step to embed the Data-Driven Editor. The editor allows users to fill out a pre-configured form, thereby modifying the design according to the required data.

General Info
- type:
data-driven-editor
Params
The widget parameters are organized into sections and specified under the params.config object.
{
"widgets": [
{
"name": "dde",
"type": "data-driven-editor",
"params": {
"config": {
"access": { ... },
"design": { ... },
"api": { ... },
"settings": { ... },
"renderer": { ... },
"translation": { ... },
"userInfo": { ... }
}
}
}
]
}
Let's review them in detail.
Access section
Describes access information:
tenantId-string, tenant identifier.userId-string, user identifier.token-string, access token.
Design section
Descries the design the editor will work with:
designId-string, design ID in Asset Storage.dataSetId-string, dataset ID in Asset Storage.isPrivateDesign-boolean, flag for private design, used for returning to editing.designPath-string, path to the design file in Asset Storage. Used for debugging. If an error occurs, it is displayed to the user.mockup-object, describes the applied mockup. This configuration is optional.down-string, ID of the image from Asset Storage used as the substrate mockup. Optional.up-string, ID of the image from Asset Storage used as the overlay mockup. Optional.location-object, describes the design position relative to the mockup. Optional. Default:{ x: 0, y: 0 }.
API section
Describes the URLs of the services the editor will interact with:
designAtoms-string, URL of the Design Atoms service.assetProcessor-string, URL of the Asset Processor service.assetStorage-string, URL of the Asset Storage service.
Settings section
Describes the appearance, features, and settings of the editor:
lang-string, language used in the editor. Default:en.symbols-string[], list of symbols available for insertion. Default:["•", "○", "¤", "♥", "♦", "♣", "♠", "↑", "↓", "→", "←", "▲", "▼", "►", "◄", "©", "