Product knowledge

Docs

Docs
Controlled business updates
View Markdown

Writeback and workflows

Capture approved business updates, comments and decisions through stored Gateway actions, with a separate plan for Qlik refresh.

On this page

Configure the action before the interface

Writeback connects a business form or workflow to an approved Gateway action. Common applications include planning inputs, comments, status updates, approvals and saved scenarios. Each application needs a defined form, target, action policy, access model and validation; enabling the module does not create a finished planning application.

Administrators configure the target and keep its credentials in Gateway state. Database execution and managed schema migrations currently support PostgreSQL, with verified TLS. Other action targets include the local audit store, approved HTTP endpoints and Qlik Cloud automations. Each target has its own platform and access requirements.

Approve and test the stored contract

Use DBA-approved existing tables or an explicitly approved schema managed through Gateway migrations. PostgreSQL statements and structured atomic transactions have separate inspection, approval and execution checks. Saving a target, approving a statement or validating a form does not activate every related action or execute a business update.

  1. Confirm the database, schema, allowed relations, service-role privileges and business keys.
  2. Configure and test the target; inspect the schema policy and any proposed migration.
  3. Review the exact statement or atomic contract, complete required live preflight and approve its current revision.
  4. Configure the action's allowed users, form constraints and lifecycle state.
  5. Test an authorized submission outside the browser, then inspect its execution history and database result.
  6. Connect the reviewed action to the Qlik form or extension and test it as the intended user.

Check the write and the refresh separately

Written records appear in Qlik only through the app's configured load path. Partial reload requires a suitable script and data connection; other apps may need a full reload. On Qlik Sense on Windows, an action can start an approved QMC reload task after submission. Qlik Cloud atomic refresh uses an explicit administrator-approved binding to a fixed app and execution identity.

A successful database write and a completed Qlik reload are separate outcomes. Retain the original execution ID and reload reference. If the Gateway reports outcome_unknown, review authoritative downstream evidence and reconcile that execution. Repeating the request with a new key can create a duplicate and does not resolve the original result.

Define workflow states and responsibilities

Workflow definitions control transitions, assignments, sign-offs and permitted actions. Configure the states, owners, reminders and escalation policy before opening the process to users. The Gateway records transition history and supports monitoring of pending work. Approved InsightOps targets can carry notifications.

Scenario grids, spread-back rules, attachments and specialist approval screens are application design choices. Confirm the action contract, storage and interface needed for each requirement during implementation. Validate the workflow with business owners, including rejection, timeout and recovery paths.

Previous

InsightOps

Next

Custom Qlik extensions