Docs

Templates provide expected dimensions, measures, property hints, security notes, and base files for common visualization patterns. They are intended as governed starting points, not as a promise that every public chart example can be copied directly into Qlik.

• ECharts-style templates for polished standard and advanced chart patterns.
• D3-style adapter templates for bespoke SVG, canvas, or geometry-heavy visual ideas.
• Chart.js-style templates for lightweight canvas chart requests.
• Picasso and nebula-style templates for Qlik-native extension patterns.
• Every generated extension should still pass functional review, security review, and acceptance testing before production use.

The agent should translate the source object's data contract into Qlik dimensions, measures, and extension properties before packaging.

• Marks and labels become dimensions.
• Position, size, radius, width, color intensity, or ranking usually become measures.
• Interactivity should use Qlik selections for selectable marks where the extension supports it; local-only zoom, drill-down, or hover should be documented clearly.
• Remote assets should be bundled or removed unless the user explicitly accepts CSP changes.
• Generated extensions should include enough metadata for later inspection without turning one-off visuals into permanent product templates.