Product knowledge
Docs
Custom Qlik extensions
Build a reviewable Qlik extension from a packaged template, publish it through approved Qlik access and verify it in the target app.
On this page
Use an extension for a defined requirement
Start by checking whether a native Qlik visualization meets the requirement. For a custom visual or action interface, discover the Gateway's packaged extension templates and inspect the chosen template's dimensions, measures, properties and security notes. Templates are starting points that still require implementation and testing.
The Gateway supports packaging, extension inspection, publication to Qlik Cloud or QSEoW and creation of extension-backed sheet objects. These are separate operations, subject to the connected user's permissions and available tools. A packaged ZIP or a stored source file does not establish that the extension is installed or working in Qlik.
Build, publish and verify
An existing extension name may affect multiple apps. Review the impact of an update before replacing it, and retain an approved recovery package. Use the returned publication outcome and readback evidence when a network interruption makes the result uncertain.
- Confirm the target platform, app and sheet, intended behavior and exact data fields.
- Choose an approved template and map dimensions, measures, selections and formatting.
- Review the generated JavaScript, manifest and other assets. Bundle dependencies where permitted and check their licences.
- Package the extension, review validation warnings and inspect its embedded Raptor manifest.
- Publish through the approved Qlik administration path; use the staged upload workflow where appropriate.
- Read back the published extension, create or inspect its sheet object, then test rendering and interaction in Qlik.
Review code and business behavior
Gateway packaging enforces archive, file-count and uncompressed-size limits and rejects unsafe paths and disallowed payloads. These checks do not replace code review. External scripts, remote assets and CSP changes need administrator review; public chart examples may also have redistribution restrictions.
Test data size, nulls, negative values, responsive layout, selections, keyboard access and the Qlik versions used by the customer. For action extensions, keep database credentials and service tokens in the Gateway. The browser submits an approved action and displays its result; administrators configure the backing action separately.
Related guides
Previous
Writeback and workflows
Next