pgkiln 0.51.0 → 0.52.0

package/db/migrations/123_workflow_outcomes.sql

@@ -0,0 +1,407 @@
+-- =====================================================================
+-- 123: workflows and approvals (APEX 26.1 / 26.2): custom task outcomes,
+-- task events and notifications, draft steps, migrating running instances
+--
+-- Task definitions:
+--   outcomes       [{"name": "YES", "label": "Yes", "colour": "success"}, …]: the buttons of the
+--                  task and the outcomes a task may end with (stored lower case in meta.task.outcome);
+--                  empty or null: the type's own (approval: approved / rejected, action: completed).
+--                  Colours: default, primary, success, danger, warning.
+--   events         [{"on": "complete" | "expire" | "fail", "type": "sql" | "mail" | "workflow", …}]:
+--                  actions when a task is completed, expires, or its completion SQL fails
+--                  (src/task-events.ts runs them as the application's role).
+--   fail_recovery  after a failing completion SQL: reopen (the decision is undone; the default) or
+--                  complete (the decision stands without the SQL's effect).
+--   notifications  {"create": "TEMPLATE", "complete": "TEMPLATE", "expire": "TEMPLATE"}: built-in
+--                  e-mails from the application's e-mail templates (meta.send_mail_template) to the
+--                  potential owners (create) or the initiator (complete; expire: both).
+-- All are columns of meta.task_definition: they travel with export/import as they are.
+--
+-- meta.task_hook: the outbox of task events and notifications (create, complete, expire), filled
+-- by a trigger in the task's transaction and worked off by the server after the commit. Runtime
+-- data like the tasks themselves (no application foreign key: not exported, kept on replace).
+--
+-- Workflows:
+--   a "draft" step type, a placeholder while modelling: allowed in a development version only
+--   (a check on the active steps; activation refuses it);
+--   a "send_mail" step (src/workflow.ts) through meta.send_mail / meta.send_mail_template;
+--   meta.migrate_workflows(): running instances move to a newer version of their definition,
+--   each current step mapped to a step of that version, in one transaction, logged in
+--   meta.workflow_event ("migrated") and meta.workflow_migration (installation data).
+-- =====================================================================
+
+-- ---------------------------------------------------------------- outcomes
+/** Why a task definition's outcomes are not valid, or null. */
+create function meta.task_outcomes_problem(p jsonb) returns text
+language plpgsql immutable set search_path = pg_catalog as $$
+declare
+  e      jsonb;
+  v_seen text[] := '{}';
+  v_name text;
+begin
+  if p is null or p = '[]'::jsonb then
+    return null;
+  end if;
+  if jsonb_typeof(p) <> 'array' then
+    return 'Outcomes are a JSON array.';
+  end if;
+  if jsonb_array_length(p) > 10 then
+    return 'At most 10 outcomes.';
+  end if;
+  for e in select * from jsonb_array_elements(p) loop
+    if jsonb_typeof(e) <> 'object' then
+      return 'Each outcome is an object {"name": …, "label": …, "colour": …}.';
+    end if;
+    v_name := lower(e->>'name');
+    if v_name is null or v_name !~ '^[a-z][a-z0-9_]{0,29}$' then
+      return format('Outcome name %s: letters, digits and underscores (at most 30), e.g. YES.', coalesce(e->>'name', '(none)'));
+    end if;
+    if v_name in ('cancelled', 'expired', 'default') then
+      return format('Outcome name %s is reserved.', e->>'name');
+    end if;
+    if v_name = any (v_seen) then
+      return format('Outcome %s is listed twice.', e->>'name');
+    end if;
+    v_seen := v_seen || v_name;
+    if e ? 'label' and (jsonb_typeof(e->'label') <> 'string' or length(btrim(e->>'label')) not between 1 and 60) then
+      return format('Outcome %s: the label is text of 1 to 60 characters.', e->>'name');
+    end if;
+    if e ? 'colour' and coalesce(e->>'colour', '') not in ('default', 'primary', 'success', 'danger', 'warning') then
+      return format('Outcome %s: the colour is default, primary, success, danger or warning.', e->>'name');
+    end if;
+  end loop;
+  return null;
+end
+$$;
+
+alter table meta.task_definition
+  add column outcomes jsonb constraint task_definition_outcomes_check check (meta.task_outcomes_problem(outcomes) is null),
+  add column events jsonb check (events is null or (jsonb_typeof(events) = 'array' and jsonb_array_length(events) <= 20)),
+  add column fail_recovery text check (fail_recovery in ('reopen', 'complete')),
+  add column notifications jsonb check (notifications is null or (jsonb_typeof(notifications) = 'object'
+    and notifications - 'create' - 'complete' - 'expire' = '{}'::jsonb));
+comment on column meta.task_definition.outcomes is 'Custom outcomes (123): [{"name", "label", "colour"}]; empty: the type''s own.';
+comment on column meta.task_definition.events is 'Task events (123): [{"on": complete|expire|fail, "type": sql|mail|workflow, …}].';
+comment on column meta.task_definition.notifications is 'Built-in notifications (123): {"create"|"complete"|"expire": e-mail template name}.';
+
+/** The outcomes a task of this definition may end with (lower case). */
+create function meta.task_outcome_names(d meta.task_definition) returns text[]
+language sql immutable set search_path = pg_catalog as $$
+  select case when d.outcomes is not null and jsonb_array_length(d.outcomes) > 0
+              then array(select lower(e->>'name') from jsonb_array_elements(d.outcomes) e)
+              when d.type = 'approval' then array['approved', 'rejected']
+              else array['completed'] end
+$$;
+
+alter table meta.task drop constraint task_outcome_check;
+alter table meta.task add constraint task_outcome_check check (outcome ~ '^[a-z][a-z0-9_]{0,29}$');
+alter table meta.task_event drop constraint task_event_event_check;
+alter table meta.task_event add constraint task_event_event_check
+  check (event in ('created', 'claimed', 'released', 'delegated', 'approved', 'rejected', 'completed', 'cancelled', 'commented', 'closed',
+                   'expired', 'renewed', 'escalated', 'failed'));
+
+-- Same as 021, plus: the outcomes of the definition (custom ones too). A custom outcome is logged as
+-- "completed" with its label. Returns also the outcome, its label, the fail events and the recovery.
+create or replace function meta.complete_task(p_id bigint, p_outcome text, p_comment text default null) returns jsonb
+language plpgsql security definer set search_path = meta, pg_catalog as $$
+declare
+  t       meta.task;
+  d       meta.task_definition;
+  v_out   text := lower(btrim(coalesce(p_outcome, '')));
+  v_label text;
+begin
+  t := meta.task_load(p_id, 'act');
+  select * into d from task_definition where id = t.definition_id;
+  if not v_out = any (meta.task_outcome_names(d)) then
+    raise exception 'A task of % cannot end as %.', d.name, left(coalesce(p_outcome, '(none)'), 60);
+  end if;
+  select e->>'label' into v_label from jsonb_array_elements(coalesce(d.outcomes, '[]')) e where lower(e->>'name') = v_out;
+  update task set state = 'completed', outcome = v_out, completed_at = now(), completed_by = meta.app_user(),
+                  actual_owner = coalesce(actual_owner, meta.app_user())
+   where id = p_id;
+  if v_out in ('approved', 'rejected', 'completed') then
+    perform meta.task_log(p_id, v_out, p_comment);
+  else
+    perform meta.task_log(p_id, 'completed', coalesce(v_label, upper(v_out)) || coalesce(': ' || nullif(btrim(p_comment), ''), ''));
+  end if;
+  return jsonb_build_object('action_code', d.action_code, 'detail_pk', t.detail_pk, 'params', t.params, 'initiator', t.initiator,
+                            'outcome', v_out, 'label', coalesce(v_label, v_out), 'subject', t.subject, 'definition', d.name,
+                            'fail_events', coalesce((select jsonb_agg(e) from jsonb_array_elements(coalesce(d.events, '[]')) e where e->>'on' = 'fail'), '[]'),
+                            'fail_recovery', coalesce(d.fail_recovery, 'reopen'));
+end
+$$;
+
+-- Same as 021, plus: a custom outcome of the definition.
+create or replace function meta.close_tasks(p_name text, p_detail_pk text, p_outcome text default null) returns int
+language plpgsql security definer set search_path = meta, pg_catalog as $$
+declare
+  v_n   int := 0;
+  v_id  bigint;
+  d     meta.task_definition;
+begin
+  select * into d from task_definition where app_id = meta.app_id() and name = upper(p_name);
+  if p_outcome is not null and not (found and lower(p_outcome) = any (meta.task_outcome_names(d))) then
+    raise exception 'Invalid outcome %.', left(p_outcome, 60);
+  end if;
+  for v_id in
+    update task t set state = case when p_outcome is null then 'cancelled' else 'completed' end,
+                      outcome = lower(p_outcome), completed_at = now(), completed_by = meta.app_user()
+     where t.definition_id = d.id and t.detail_pk = p_detail_pk and t.state in ('unassigned', 'assigned')
+    returning t.id
+  loop
+    perform meta.task_log(v_id, 'closed', p_outcome);
+    v_n := v_n + 1;
+  end loop;
+  return v_n;
+end
+$$;
+
+-- The completion SQL of a task failed and its fail events ran (the task list, as the acting user).
+create function meta.log_task_failure(p_id bigint, p_detail text) returns void
+language plpgsql security definer set search_path = meta, pg_catalog as $$
+declare
+  t meta.task;
+begin
+  select * into t from task where id = p_id and app_id = meta.app_id();
+  if not found or not ((meta.task_rights(t)).may_act or (t.state = 'completed' and lower(t.completed_by) = lower(meta.app_user()))) then
+    raise exception 'Task % not found.', p_id;
+  end if;
+  perform meta.task_log(p_id, 'failed', left(p_detail, 4000));
+end
+$$;
+revoke all on function meta.log_task_failure(bigint, text) from public;
+grant execute on function meta.log_task_failure(bigint, text) to public;
+
+-- ---------------------------------------------------------------- events and notifications: the outbox
+create table meta.task_hook (
+  id         bigserial primary key,
+  task_id    bigint not null references meta.task on delete cascade,
+  event      text not null check (event in ('create', 'complete', 'expire')),
+  created_at timestamptz not null default now(),
+  attempts   int not null default 0,
+  done_at    timestamptz,
+  error      text check (length(error) <= 2000)
+);
+create index task_hook_pending on meta.task_hook (id) where done_at is null;
+revoke all on meta.task_hook from public;
+comment on table meta.task_hook is 'Task events and notifications to run after the commit (123); runtime data, not exported.';
+
+create function meta.task_hook_enqueue() returns trigger
+language plpgsql security definer set search_path = meta, pg_catalog as $$
+declare
+  d       meta.task_definition;
+  v_event text := case when tg_op = 'INSERT' then 'create' when new.state = 'completed' then 'complete' when new.state = 'expired' then 'expire' end;
+begin
+  if v_event is null then
+    return new;
+  end if;
+  select * into d from task_definition where id = new.definition_id;
+  if coalesce(d.notifications ? v_event, false)
+     or exists (select 1 from jsonb_array_elements(coalesce(d.events, '[]')) e where e->>'on' = v_event) then
+    insert into task_hook (task_id, event) values (new.id, v_event);
+    perform pg_notify('pgkiln_workflow', 'task');
+  end if;
+  return new;
+end
+$$;
+create trigger task_hook_create after insert on meta.task for each row execute function meta.task_hook_enqueue();
+create trigger task_hook_state after update of state on meta.task
+  for each row when (old.state is distinct from new.state and new.state in ('completed', 'expired')) execute function meta.task_hook_enqueue();
+
+/**
+ * The e-mail addresses of a task's people (accounts with an address): its potential owners (named users,
+ * the actual owner, the application's users with one of its owner roles) and/or its initiator.
+ */
+create function meta.task_addresses(p_task_id bigint, p_owners boolean, p_initiator boolean) returns text[]
+language sql stable security definer set search_path = meta, pg_catalog as $$
+  select coalesce(array_agg(distinct ac.email order by ac.email), '{}')
+    from task t
+    join account ac on ac.active and ac.email is not null
+   where t.id = p_task_id
+     and ((p_initiator and lower(ac.username) = lower(t.initiator))
+       or (p_owners and (lower(ac.username) = any (select lower(u) from unnest(t.owner_users) u)
+                         or lower(ac.username) = lower(t.actual_owner)
+                         or exists (select 1 from app_access aa
+                                     where aa.app_id = t.app_id and aa.account_id = ac.id
+                                       and exists (select 1 from unnest(aa.roles) r where lower(r) = any (select lower(x) from unnest(t.owner_roles) x))))))
+$$;
+revoke all on function meta.task_addresses(bigint, boolean, boolean) from public;
+
+-- ---------------------------------------------------------------- draft steps
+alter table meta.workflow_definition add constraint workflow_definition_no_draft
+  check (not jsonb_path_exists(steps, '$[*] ? (@.type == "draft")'));
+
+-- Same as 027, plus: a version with draft steps is not activated.
+create or replace function meta.activate_workflow_version(p_definition_id int) returns text
+language plpgsql set search_path = meta, pg_catalog as $$
+declare
+  d meta.workflow_definition;
+  v_drafts text;
+begin
+  select * into d from workflow_definition where id = p_definition_id for update;
+  if not found then
+    raise exception 'Workflow definition % does not exist.', p_definition_id;
+  end if;
+  if d.dev_version is null then
+    raise exception 'Workflow % has no version in development.', d.name;
+  end if;
+  if jsonb_array_length(d.dev_steps) = 0 then
+    raise exception 'Version % of workflow % has no steps.', d.dev_version, d.name;
+  end if;
+  select string_agg(s->>'name', ', ') into v_drafts from jsonb_array_elements(d.dev_steps) s where s->>'type' = 'draft';
+  if v_drafts is not null then
+    raise exception 'Version % of workflow % has draft steps (%): replace them before activating it.', d.dev_version, d.name, v_drafts;
+  end if;
+  update workflow_definition
+     set inactive_versions = inactive_versions || jsonb_build_array(jsonb_build_object(
+           'version', version, 'steps', steps, 'activated_at', activated_at, 'deactivated_at', now())),
+         version = dev_version, steps = dev_steps, activated_at = now(),
+         dev_version = null, dev_steps = null
+   where id = d.id;
+  return d.dev_version;
+end
+$$;
+revoke all on function meta.activate_workflow_version(int) from public;
+
+-- ---------------------------------------------------------------- migrating running instances
+alter table meta.workflow_event drop constraint workflow_event_event_check;
+alter table meta.workflow_event add constraint workflow_event_event_check
+  check (event in ('started', 'step', 'task', 'waiting', 'resumed', 'completed', 'terminated', 'faulted', 'retried', 'split', 'joined', 'cancelled', 'migrated'));
+
+create table meta.workflow_migration (
+  id              bigserial primary key,
+  app_id          int  not null references meta.app on delete cascade,
+  definition_name text not null,
+  to_version      text not null,
+  -- current step → step of the new version
+  mapping         jsonb not null,
+  workflow_ids    bigint[] not null,
+  -- per instance: {"id", "from_version", "from_step", "to_step"}
+  detail          jsonb not null default '[]',
+  migrated_by     text not null,
+  migrated_at     timestamptz not null default now()
+);
+create index on meta.workflow_migration (app_id, migrated_at);
+revoke all on meta.workflow_migration from public;
+comment on table meta.workflow_migration is 'Log of migrations of running workflow instances to a newer version (123); installation data, not exported.';
+
+/**
+ * Move running instances (p_ids) of a definition to a newer version (p_to_version: the active version or a
+ * later inactive one), each at the step p_map gives for its current step. Returns one row per instance with
+ * the problem that stops it (null: it can move). With p_apply, nothing changes unless every instance can
+ * move; then all move in this transaction, with a "migrated" event each and a row in meta.workflow_migration.
+ */
+create function meta.migrate_workflows(p_definition_id int, p_to_version text, p_ids bigint[], p_map jsonb, p_apply boolean, p_by text)
+returns table (workflow_id bigint, from_version text, from_step text, to_step text, problem text)
+language plpgsql set search_path = meta, pg_catalog as $$
+declare
+  d        meta.workflow_definition;
+  v_order  text[];
+  v_target int;
+  v_steps  jsonb;
+  v_to     jsonb;
+  v_from   jsonb;
+  w        record;
+  v_rows   jsonb := '[]';
+  v_bad    text[] := '{}';
+  v_id     bigint;
+  r        jsonb;
+begin
+  select * into d from workflow_definition where id = p_definition_id;
+  if not found then
+    raise exception 'Workflow definition % does not exist.', p_definition_id;
+  end if;
+  if coalesce(cardinality(p_ids), 0) = 0 then
+    raise exception 'Choose the instances to migrate.';
+  end if;
+  if jsonb_typeof(coalesce(p_map, '{}')) <> 'object' then
+    raise exception 'The step mapping is a JSON object.';
+  end if;
+  -- versions from the oldest to the active one
+  v_order := array(select x->>'version' from jsonb_array_elements(d.inactive_versions) with ordinality o(x, i) order by i) || d.version;
+  v_target := array_position(v_order, p_to_version);
+  if v_target is null then
+    raise exception 'Workflow % has no version % to migrate to (the active version or an inactive one).', d.name, p_to_version;
+  end if;
+  v_steps := case when p_to_version = d.version then d.steps
+                  else (select x->'steps' from jsonb_array_elements(d.inactive_versions) x where x->>'version' = p_to_version limit 1) end;
+
+  foreach v_id in array (select array_agg(distinct x order by x) from unnest(p_ids) x) loop
+    select wf.id, wf.app_id, wf.definition_id, coalesce(wf.version, '1') as version, wf.state, wf.current_step, wf.steps, wf.waiting_task, wf.wait_until,
+           (select td.name from task tk join task_definition td on td.id = tk.definition_id where tk.id = wf.waiting_task) as task_name,
+           exists (select 1 from workflow_branch b where b.workflow_id = wf.id and b.state in ('active', 'waiting', 'faulted')) as branches
+      into w from workflow wf where wf.id = v_id for update;
+    workflow_id := v_id;
+    from_version := w.version;
+    from_step := w.current_step;
+    to_step := case when w.current_step is not null then p_map->>w.current_step end;
+    problem := null;
+    v_to := (select s from jsonb_array_elements(v_steps) s where s->>'name' = to_step limit 1);
+    v_from := (select s from jsonb_array_elements(w.steps) s where s->>'name' = w.current_step limit 1);
+    if w.id is null or w.definition_id is distinct from d.id or w.app_id <> d.app_id then
+      problem := 'not an instance of this workflow';
+      from_version := null;
+      from_step := null;
+      to_step := null;
+    elsif w.state not in ('active', 'waiting', 'faulted') then
+      problem := format('is %s', w.state);
+    elsif coalesce(array_position(v_order, w.version), 0) >= v_target then
+      problem := format('runs version %s, which is not older than %s', w.version, p_to_version);
+    elsif w.branches then
+      problem := 'runs parallel branches: let them reach their join first';
+    elsif to_step is null or to_step = '' then
+      problem := format('no step of version %s is mapped to %s', p_to_version, coalesce(w.current_step, '(none)'));
+    elsif v_to is null then
+      problem := format('version %s has no step %s', p_to_version, to_step);
+    elsif v_to->>'type' = 'draft' then
+      problem := format('%s is a draft step', to_step);
+    elsif w.waiting_task is not null and v_to->>'type' <> 'task' then
+      problem := format('waits for a task: %s must be a task step', to_step);
+    elsif w.waiting_task is not null and upper(v_to->>'task') is distinct from w.task_name then
+      problem := format('waits for a task of %s, but %s creates %s', w.task_name, to_step, coalesce(v_to->>'task', '(none)'));
+    elsif w.state = 'waiting' and w.waiting_task is null and v_from->>'type' = 'invoke_api' then
+      problem := 'is calling a web service: try again when the call is done';
+    elsif w.state = 'waiting' and w.waiting_task is null and v_from->>'type' = 'wait' and v_to->>'type' <> 'wait' then
+      problem := format('waits at a wait step: %s must be a wait step', to_step);
+    elsif w.state = 'waiting' and w.waiting_task is null and v_from->>'type' = 'join' and v_to->>'type' <> 'join' then
+      problem := format('waits at a join: %s must be a join step', to_step);
+    end if;
+    if problem is not null then
+      v_bad := v_bad || format('%s %s', v_id, problem);
+    end if;
+    v_rows := v_rows || jsonb_build_object('id', v_id, 'from_version', from_version, 'from_step', from_step, 'to_step', to_step);
+    return next;
+  end loop;
+
+  if not p_apply then
+    return;
+  end if;
+  if cardinality(v_bad) > 0 then
+    raise exception 'Nothing was migrated: instance %.', array_to_string(v_bad, '; instance ');
+  end if;
+  for r in select * from jsonb_array_elements(v_rows) loop
+    update workflow set steps = v_steps, version = p_to_version, current_step = r->>'to_step', updated_at = now()
+     where id = (r->>'id')::bigint;
+    perform meta.workflow_log((r->>'id')::bigint, r->>'to_step', 'migrated',
+      format('version %s → %s: %s → %s (by %s)', r->>'from_version', p_to_version, r->>'from_step', r->>'to_step', p_by));
+  end loop;
+  insert into workflow_migration (app_id, definition_name, to_version, mapping, workflow_ids, detail, migrated_by)
+  values (d.app_id, d.name, p_to_version, coalesce(p_map, '{}'), array(select (x->>'id')::bigint from jsonb_array_elements(v_rows) x), v_rows, p_by);
+  -- active ones go on with their new step
+  perform pg_notify('pgkiln_workflow', 'migrated');
+end
+$$;
+revoke all on function meta.migrate_workflows(int, text, bigint[], jsonb, boolean, text) from public;
+
+-- Same as 072, plus the definition's custom outcomes (the task list's buttons).
+create or replace view meta.tasks with (security_barrier) as
+  select t.id, t.app_id, d.name as definition, d.type, t.subject, t.detail_pk, t.params, t.state, t.outcome,
+         t.priority, t.initiator, t.actual_owner, t.owner_users, t.owner_roles, t.created_at, t.due_at,
+         t.completed_at, t.completed_by, d.details_page, d.details_item,
+         t.due_at is not null and t.due_at < now() and t.state in ('unassigned', 'assigned') as overdue,
+         (r).is_initiator, (r).is_owner, (r).is_admin, (r).may_act, (r).may_claim, (r).may_release, (r).may_delegate, (r).may_cancel,
+         t.tenant_id, d.outcomes
+    from (select t, meta.task_rights(t) as r from meta.task t where t.app_id = meta.app_id()) x
+    cross join lateral (select (x.t).*) t
+    join meta.task_definition d on d.id = t.definition_id
+   where (x.r).may_see;

package/db/migrations/124_component_details.sql

@@ -0,0 +1,51 @@
+-- =====================================================================
+-- 124: component details of APEX 26.1 (sprint 115, WS-11)
+--
+-- Dynamic actions:
+--   * event "menu_entry" (APEX: Menu entry chosen): a menu button's entry
+--     {"label": "…", "action": "NAME"} runs the dynamic actions of event
+--     menu_entry whose trigger names the entry (NAME) or the menu button
+--     (any of its entries; the entry's name is the value a client-side
+--     condition tests).
+--   * actions "wait_popup" and "remove_wait_popup" (APEX: Show / Remove
+--     Wait Popup): a modal "please wait" overlay (Message is its text)
+--     until remove_wait_popup or the next page; e.g. before_submit →
+--     wait_popup around a long process, or wait_popup, execute_sql,
+--     remove_wait_popup around an Ajax callback.
+-- Menu entries: exactly one of "page", "request" or "action" (new).
+-- No new tables or columns: the button's menu jsonb and the dynamic
+-- action's event/action travel with export_app / import_app unchanged.
+-- =====================================================================
+
+alter table meta.dynamic_action drop constraint dynamic_action_event_check;
+alter table meta.dynamic_action add constraint dynamic_action_event_check check (event in (
+  'change', 'click', 'load', 'dialog_closed', 'after_refresh', 'selection_change', 'focus', 'blur', 'key_release', 'before_submit', 'custom',
+  'menu_entry'));
+
+alter table meta.dynamic_action drop constraint dynamic_action_action_check;
+alter table meta.dynamic_action add constraint dynamic_action_action_check check (action in (
+  'show', 'hide', 'enable', 'disable', 'set_value', 'execute_sql', 'refresh_region', 'refresh_item', 'alert', 'submit',
+  'set_focus', 'add_class', 'remove_class', 'show_success', 'show_error', 'clear_errors', 'ai_generate', 'execute_javascript', 'plugin',
+  'push_subscribe', 'confirm', 'close_dialog', 'cancel_dialog', 'clear', 'open_region', 'close_region', 'download', 'print',
+  'current_position', 'share', 'wait_popup', 'remove_wait_popup'));
+
+-- A menu entry: {"label": "…", "page": 3, "items": {"P3_ID": "&P2_ID."}} (a link),
+-- {"label": "…", "request": "ARCHIVE"} (submits the page with that request) or
+-- {"label": "…", "action": "EXPORT"} (runs the dynamic actions of event menu_entry);
+-- optional "confirm", "authz" and "icon". At most 20 entries.
+create or replace function meta.button_menu_ok(p_menu jsonb) returns boolean
+language sql immutable set search_path = meta, pg_catalog as $$
+  select jsonb_typeof(p_menu) = 'array' and jsonb_array_length(p_menu) <= 20
+     and not exists (
+       select 1 from jsonb_array_elements(p_menu) e
+        where jsonb_typeof(e) <> 'object'
+           or jsonb_typeof(e->'label') is distinct from 'string' or length(e->>'label') not between 1 and 100
+           or (e ? 'page')::int + (e ? 'request')::int + (e ? 'action')::int <> 1
+           or (e ? 'page' and (jsonb_typeof(e->'page') <> 'number' or (e->>'page')::numeric <= 0 or (e->>'page')::numeric <> floor((e->>'page')::numeric)))
+           or (e ? 'request' and coalesce(e->>'request', '') !~ '^[A-Z][A-Z0-9_]*$')
+           or (e ? 'action' and (jsonb_typeof(e->'action') <> 'string' or e->>'action' !~ '^[A-Z][A-Z0-9_]{0,59}$'))
+           or (e ? 'items' and jsonb_typeof(e->'items') <> 'object')
+           or (e ? 'confirm' and jsonb_typeof(e->'confirm') <> 'string')
+           or (e ? 'icon' and coalesce(e->>'icon', '') !~ '^[a-z][a-z0-9-]{0,40}$')
+           or (e ? 'authz' and coalesce(e->>'authz', '') !~ '^!?[A-Z][A-Z0-9_]*$'))
+$$;

package/docs/apex-feature-parity.md

@@ -7,23 +7,23 @@ open item and open an issue or pull request; see [CONTRIBUTING.md](../CONTRIBUTI
 Legend: ✅ available · 🟡 partial (see notes) · ❌ not yet · ➖ not planned (a deliberate choice,
 or better served by the PostgreSQL ecosystem; see the notes and [extensions](guide/15-extensions.md))
 
-Last reviewed: 2026-10-19 (sprint 110: Data Reporter as a workspace tool with datasets, reporting applications, editors and viewers, published reports with stable URLs and pins; sprint 109: the Workspace home above the App Builder and SQL Workshop, with a summary, top applications, users and developers, and an optional release check; sprint 108: the code editor's syntax colours in the builder's light and dark themes, read-only SQL highlighted, the Data Modeler in dark mode; sprint 107: a transaction mode in the SQL Worksheet with Commit and Rollback; DA-18: JavaScript (MLE) not planned, plv8 where installed; sprint 106: the change log of DDL change sets with Flyway, Liquibase and SQL downloads; sprint 104: RESTful Services modules, templates and handlers with PL/pgSQL and media handlers, privileges, OpenAPI and Try it; sprint 103: Schema Export / Import with pg_dump and pg_restore; sprint 102: the SQL Monitor with live sessions, Top SQL and a statement's plan; sprint 101: Scheduling of pg_cron jobs with a schedule builder, run now and run history; sprint 100: RESTful Services, tables and views published as REST endpoints with paging, filters, keys and OpenAPI; sprint 99: Administration → Database Users for PostgreSQL roles; sprint 98: the Data Modeler with relational diagrams, DDL and a data dictionary; sprint 97: charts of a query in the worksheet, saved charts and their dashboard; sprint 96: the SQL Workshop's Launchpad with pins and tool groups, the builder's search with Ctrl+K; sprint 95: Table Properties: create, edit or copy a table in a form with a DDL preview and Apply in one transaction; sprint 94: an object's menu with Open in a panel, Quick DDL, Add index / trigger / policy and Drop with dependents; sprint 93: worksheets saved as SQL Scripts with tabs and a Files list, Format, Convert case, find and replace, bind and substitution variables; sprint 92: the worksheet's Query Result with sort, value dialog, copy and downloads, plans as a tree with the slowest step and misestimates, SQL History with status, search and run again; sprint 91: the SQL Worksheet like Database Actions' SQL: navigator, Run Statement at the cursor and Run Script with a log per statement, Explain Plan, Autotrace, notices, history, Run as an application role; sprint 90: Comment Out in the page designer, gallery labels in title case; sprint 89: the Object Browser's schema, one row of tabs, blank NULLs, Modify column; sprint 88: home cards with colour bands and round icons, the hero on the page background, a page footer with the version and Back to top; sprint 87: the Create Application wizard reloads the page list for a schema, RLS badges, the alias from the name; sprint 86: the page designer by page number, HTML error pages in the builder; sprint 85: the Form Designer, beyond APEX; sprint 84: the date picker, facet menus; sprint 83: Component Settings and Component Groups; sprint 82: Report Queries; sprint 81: Application Computations and Shortcuts in Shared Components; sprint 80: the master grid's first row selected when the page opens and after a search; grid cells as text with their format mask until edited, with cell navigation by arrow keys, Enter, F2 and Escape; sprint 79: generated dashboards with sums, donuts and lines, leaving out charts that say nothing; applications open in their own light or dark mode until the user chooses, per application; a user menu with Appearance and Sign in when signed out; the developer toolbar's App and Page texts and debug state; the report search's column scope in the magnifier; sprint 78: generated faceted search reports with one column per foreign key, the faceted search's total row count, Show all and Yes/No values, one search field, friendly headings and number formats in generated grids and master-detail pages, friendly names in the Create Application wizard's page list; sprint 77: the Page Designer's layout and tree by display position, button positions, the tree's context menu with Duplicate and Copy to other page, Show Common / Show All, Go to group and the Template Options dialog; display positions, button positions and side-column page templates at runtime; sprint 76: the interactive report's menus and pagination, date items in the date format; sprint 75: the SQL Workshop's Object Browser and tabs; sprint 74: the builder's information architecture: Shared Components grid, Settings tabs, application home search and tasks; sprint 73: the Create Application wizard on one page with page types and features; sprint 72: the runtime chrome compared with APEX 26.2's: the developer toolbar, the Iris look, the navigation bar's Help menu and Install button; sprint 71: generated applications compared with APEX 26.2's: labels, foreign key names in reports, file columns, format masks, the Home page and the dashboard; sprint 70: treemap, sunburst and timeline charts; sprint 69: dragging tasks on a Gantt chart; sprint 68: the Data Reporter's welcome page, Find my workspace; sprint 67: REST source catalogs from OpenAPI documents, a workspace's export and import (two rows added); sprint 66: a blueprint from an existing application; sprint 65: facet charts; sprint 64: approval vacation rules and expiration policies; sprint 63: range, box plot and stock charts; sprint 62: workspace preferences (SQL Workshop and RESTful services per workspace), extension links, Manage backups across applications, SQL Workshop utilities with object reports, About Database and a database monitor; sprint 61: the builder's screens compared with APEX 26.1: the workspace sign-in page, the Administration menu with workspace message, environment banner and utilization, the SQL Workshop home, the App Gallery, application groups and cross application reports (four rows added); sprint 60: isolated workspaces with their own database logins, row-level security on pgkiln's tables and workspace database roles, workspace administrators; sprint 59: the Page Designer's help pane, Quick edit from the developer toolbar; sprint 58: page groups; sprint 57: region templates hero, title bar, buttons container, inline dialog and drawer, wizard with wizard progress, the carousel; sprint 56: Generate DDL and Schema Comparison in the SQL Workshop, `pgkiln ddl` and `pgkiln compare`; sprint 55: an editable login page with a Login region and the Minimal page template, Forgot password through the application's mail service; sprint 54: interactive grid views, the single row view, group by and chart; sprint 53: application settings, user preferences and items kept per user, dynamic translations, `meta.data_export` and data export downloads, display image and geocoded address items; sprint 52: every dynamic action event and action, Ajax callbacks, an error handling function, the session timeout warning; sprint 51: checked imports, application backups, availability and Run only, feedback, type-specific attribute help; sprint 50: lost update detection, warn on unsaved changes, the URL and search regions with search configurations, the developer toolbar with a session state viewer, and e-mail through SMTP with OAuth2, Microsoft Graph, Amazon SES and HTTP APIs; import checks, application availability, property help and e-mail compared again; 2026-10-06: pgkiln 0.31.0, in progress: static application files and the Execute JavaScript dynamic action; region, item, dynamic action and process plug-ins; conditional and dynamic theme styles; XML and Excel in `meta.parse_data`, zips in SQL, `meta.v_boolean`; file items in S3-compatible object storage; map layers by the visible area and as vector tiles; a graphical query builder; tenants for workflows and tasks; application files as YAML and region static IDs; Lucide icons and icon modifiers; PWA push notifications; 0.30.0: 136 icons and an icon picker; an axe-core accessibility audit; cropping pictures; session sharing between applications; twenty-two built-in languages; 0.29.0: workspaces; the Iris base style; drawers; built-in template components including the metric card; Theme Roller dark-mode colours, live preview and template options on items and report columns; report selection across pages; instance settings; fourteen built-in languages; 0.28.0: AI with Claude and OpenAI; 0.27.0: Data Reporter; sample data generator; create application from several sheets, pasted data or existing tables; 0.26.0: working copies with a three-way merge; theme, library and boilerplate applications with subscriptions; 0.25.0: Gantt, pyramid and polar charts; map layers, clustering and server-side spatial filters; REST data sources that write back from forms and grids and synchronise into tables, OAuth2 password and refresh-token grants; debug messages per request and an install/upgrade log; `meta.web_request()` and `meta.parse_data()`; Theme Roller style variants and template options; 0.24.0: automations with several actions, error handling per row and runs from SQL; invoke-API workflow steps; Unload Data in the Data Workshop; create page wizards for cards, calendar, chart, map, faceted search, form and master-detail; create an application from a file; 0.23.0: interactive grid aggregates, frozen/moved/resized columns, layouts and saved grid reports, master-detail, row actions and copy/paste; download processes, execution chains in the background, workflow processes, branches to a function's URL or another app, the Dialog Closed event; number format masks, automatic time zone, runtime messages in German, French and Spanish; SQL scripts, Quick SQL, a query builder, XML loading and data load definitions; custom authentication, lists, page and application locks with developer comments, supporting objects; 0.22.0: keyset paging, report PDFs and REST collections streamed from a cursor, database-account authentication; 0.21.0: HTTP-header authentication behind a reverse proxy; 0.20.0: a popup list of values with server-side search; 0.19.0: row-range pagination, maximum row counts and row limits, lazy loading and caching of regions, streamed CSV/Excel downloads; 0.18.0: calendar week/day/list views with drag and drop, bubble/gauge/funnel/radar charts and drill-down, smart filters, a region display selector and more facet types, computations, conditional branches, build options, menu buttons, REST data sources and web credentials, rich text/Markdown, rating, combobox, date range and QR code items; 0.17.0: an App Builder home, workspace dashboard and utilities like APEX's; 0.16.0: a Page Designer with drag-and-drop layout, a code editor with autocomplete, template components and plug-ins, parallel branches and versions of workflows, the `pgkiln` command line with one file per component; 0.15.0: drop and paste files, heat maps, filtering a report by the map area; 0.14.0: stacked, combo, scatter and pie charts, several files per upload item; 0.13.0: map and tree regions; 0.12.0: REST modules in the builder; 0.11.0: workflows and Progressive Web Apps; 0.10.0: LDAP, SAML, "Keep me signed in", document templates, JSON loading, approvals and the task list; pgkiln installs no application, HR is an example).
+Last reviewed: 2026-10-19 (sprint 115: popup LOVs that load on scroll, Wait Popup dynamic actions and dynamic actions on menu entries; sprint 114: Workflow 26.2 with custom task outcomes, task events and notifications, Send E-Mail and draft steps, migrating running instances and the diagram as SVG / PNG; sprint 113: Team Development with issues, labels, milestones, templates, a board and a set-up wizard; sprint 112: AI interactive reports with chips, Undo, computed columns and a phrase parser that needs no AI service; sprint 111: AI Agents with tools as a shared component, a Navigate tool with checksummed URLs, Gemini and OpenAI-compatible services; sprint 110: Data Reporter as a workspace tool with datasets, reporting applications, editors and viewers, published reports with stable URLs and pins; sprint 109: the Workspace home above the App Builder and SQL Workshop, with a summary, top applications, users and developers, and an optional release check; sprint 108: the code editor's syntax colours in the builder's light and dark themes, read-only SQL highlighted, the Data Modeler in dark mode; sprint 107: a transaction mode in the SQL Worksheet with Commit and Rollback; DA-18: JavaScript (MLE) not planned, plv8 where installed; sprint 106: the change log of DDL change sets with Flyway, Liquibase and SQL downloads; sprint 104: RESTful Services modules, templates and handlers with PL/pgSQL and media handlers, privileges, OpenAPI and Try it; sprint 103: Schema Export / Import with pg_dump and pg_restore; sprint 102: the SQL Monitor with live sessions, Top SQL and a statement's plan; sprint 101: Scheduling of pg_cron jobs with a schedule builder, run now and run history; sprint 100: RESTful Services, tables and views published as REST endpoints with paging, filters, keys and OpenAPI; sprint 99: Administration → Database Users for PostgreSQL roles; sprint 98: the Data Modeler with relational diagrams, DDL and a data dictionary; sprint 97: charts of a query in the worksheet, saved charts and their dashboard; sprint 96: the SQL Workshop's Launchpad with pins and tool groups, the builder's search with Ctrl+K; sprint 95: Table Properties: create, edit or copy a table in a form with a DDL preview and Apply in one transaction; sprint 94: an object's menu with Open in a panel, Quick DDL, Add index / trigger / policy and Drop with dependents; sprint 93: worksheets saved as SQL Scripts with tabs and a Files list, Format, Convert case, find and replace, bind and substitution variables; sprint 92: the worksheet's Query Result with sort, value dialog, copy and downloads, plans as a tree with the slowest step and misestimates, SQL History with status, search and run again; sprint 91: the SQL Worksheet like Database Actions' SQL: navigator, Run Statement at the cursor and Run Script with a log per statement, Explain Plan, Autotrace, notices, history, Run as an application role; sprint 90: Comment Out in the page designer, gallery labels in title case; sprint 89: the Object Browser's schema, one row of tabs, blank NULLs, Modify column; sprint 88: home cards with colour bands and round icons, the hero on the page background, a page footer with the version and Back to top; sprint 87: the Create Application wizard reloads the page list for a schema, RLS badges, the alias from the name; sprint 86: the page designer by page number, HTML error pages in the builder; sprint 85: the Form Designer, beyond APEX; sprint 84: the date picker, facet menus; sprint 83: Component Settings and Component Groups; sprint 82: Report Queries; sprint 81: Application Computations and Shortcuts in Shared Components; sprint 80: the master grid's first row selected when the page opens and after a search; grid cells as text with their format mask until edited, with cell navigation by arrow keys, Enter, F2 and Escape; sprint 79: generated dashboards with sums, donuts and lines, leaving out charts that say nothing; applications open in their own light or dark mode until the user chooses, per application; a user menu with Appearance and Sign in when signed out; the developer toolbar's App and Page texts and debug state; the report search's column scope in the magnifier; sprint 78: generated faceted search reports with one column per foreign key, the faceted search's total row count, Show all and Yes/No values, one search field, friendly headings and number formats in generated grids and master-detail pages, friendly names in the Create Application wizard's page list; sprint 77: the Page Designer's layout and tree by display position, button positions, the tree's context menu with Duplicate and Copy to other page, Show Common / Show All, Go to group and the Template Options dialog; display positions, button positions and side-column page templates at runtime; sprint 76: the interactive report's menus and pagination, date items in the date format; sprint 75: the SQL Workshop's Object Browser and tabs; sprint 74: the builder's information architecture: Shared Components grid, Settings tabs, application home search and tasks; sprint 73: the Create Application wizard on one page with page types and features; sprint 72: the runtime chrome compared with APEX 26.2's: the developer toolbar, the Iris look, the navigation bar's Help menu and Install button; sprint 71: generated applications compared with APEX 26.2's: labels, foreign key names in reports, file columns, format masks, the Home page and the dashboard; sprint 70: treemap, sunburst and timeline charts; sprint 69: dragging tasks on a Gantt chart; sprint 68: the Data Reporter's welcome page, Find my workspace; sprint 67: REST source catalogs from OpenAPI documents, a workspace's export and import (two rows added); sprint 66: a blueprint from an existing application; sprint 65: facet charts; sprint 64: approval vacation rules and expiration policies; sprint 63: range, box plot and stock charts; sprint 62: workspace preferences (SQL Workshop and RESTful services per workspace), extension links, Manage backups across applications, SQL Workshop utilities with object reports, About Database and a database monitor; sprint 61: the builder's screens compared with APEX 26.1: the workspace sign-in page, the Administration menu with workspace message, environment banner and utilization, the SQL Workshop home, the App Gallery, application groups and cross application reports (four rows added); sprint 60: isolated workspaces with their own database logins, row-level security on pgkiln's tables and workspace database roles, workspace administrators; sprint 59: the Page Designer's help pane, Quick edit from the developer toolbar; sprint 58: page groups; sprint 57: region templates hero, title bar, buttons container, inline dialog and drawer, wizard with wizard progress, the carousel; sprint 56: Generate DDL and Schema Comparison in the SQL Workshop, `pgkiln ddl` and `pgkiln compare`; sprint 55: an editable login page with a Login region and the Minimal page template, Forgot password through the application's mail service; sprint 54: interactive grid views, the single row view, group by and chart; sprint 53: application settings, user preferences and items kept per user, dynamic translations, `meta.data_export` and data export downloads, display image and geocoded address items; sprint 52: every dynamic action event and action, Ajax callbacks, an error handling function, the session timeout warning; sprint 51: checked imports, application backups, availability and Run only, feedback, type-specific attribute help; sprint 50: lost update detection, warn on unsaved changes, the URL and search regions with search configurations, the developer toolbar with a session state viewer, and e-mail through SMTP with OAuth2, Microsoft Graph, Amazon SES and HTTP APIs; import checks, application availability, property help and e-mail compared again; 2026-10-06: pgkiln 0.31.0, in progress: static application files and the Execute JavaScript dynamic action; region, item, dynamic action and process plug-ins; conditional and dynamic theme styles; XML and Excel in `meta.parse_data`, zips in SQL, `meta.v_boolean`; file items in S3-compatible object storage; map layers by the visible area and as vector tiles; a graphical query builder; tenants for workflows and tasks; application files as YAML and region static IDs; Lucide icons and icon modifiers; PWA push notifications; 0.30.0: 136 icons and an icon picker; an axe-core accessibility audit; cropping pictures; session sharing between applications; twenty-two built-in languages; 0.29.0: workspaces; the Iris base style; drawers; built-in template components including the metric card; Theme Roller dark-mode colours, live preview and template options on items and report columns; report selection across pages; instance settings; fourteen built-in languages; 0.28.0: AI with Claude and OpenAI; 0.27.0: Data Reporter; sample data generator; create application from several sheets, pasted data or existing tables; 0.26.0: working copies with a three-way merge; theme, library and boilerplate applications with subscriptions; 0.25.0: Gantt, pyramid and polar charts; map layers, clustering and server-side spatial filters; REST data sources that write back from forms and grids and synchronise into tables, OAuth2 password and refresh-token grants; debug messages per request and an install/upgrade log; `meta.web_request()` and `meta.parse_data()`; Theme Roller style variants and template options; 0.24.0: automations with several actions, error handling per row and runs from SQL; invoke-API workflow steps; Unload Data in the Data Workshop; create page wizards for cards, calendar, chart, map, faceted search, form and master-detail; create an application from a file; 0.23.0: interactive grid aggregates, frozen/moved/resized columns, layouts and saved grid reports, master-detail, row actions and copy/paste; download processes, execution chains in the background, workflow processes, branches to a function's URL or another app, the Dialog Closed event; number format masks, automatic time zone, runtime messages in German, French and Spanish; SQL scripts, Quick SQL, a query builder, XML loading and data load definitions; custom authentication, lists, page and application locks with developer comments, supporting objects; 0.22.0: keyset paging, report PDFs and REST collections streamed from a cursor, database-account authentication; 0.21.0: HTTP-header authentication behind a reverse proxy; 0.20.0: a popup list of values with server-side search; 0.19.0: row-range pagination, maximum row counts and row limits, lazy loading and caching of regions, streamed CSV/Excel downloads; 0.18.0: calendar week/day/list views with drag and drop, bubble/gauge/funnel/radar charts and drill-down, smart filters, a region display selector and more facet types, computations, conditional branches, build options, menu buttons, REST data sources and web credentials, rich text/Markdown, rating, combobox, date range and QR code items; 0.17.0: an App Builder home, workspace dashboard and utilities like APEX's; 0.16.0: a Page Designer with drag-and-drop layout, a code editor with autocomplete, template components and plug-ins, parallel branches and versions of workflows, the `pgkiln` command line with one file per component; 0.15.0: drop and paste files, heat maps, filtering a report by the map area; 0.14.0: stacked, combo, scatter and pie charts, several files per upload item; 0.13.0: map and tree regions; 0.12.0: REST modules in the builder; 0.11.0: workflows and Progressive Web Apps; 0.10.0: LDAP, SAML, "Keep me signed in", document templates, JSON loading, approvals and the task list; pgkiln installs no application, HR is an example).
 
 ## At a glance
 
 | Area | ✅ | 🟡 | ❌ | ➖ | In short |
 |---|---:|---:|---:|---:|---|
-| App Builder and development | 20 | 0 | 0 | 0 | Page Designer with drag-and-drop and a code editor, wizards, search, where used, an Advisor, a CLI with one file per component, page locks and comments, supporting objects, working copies with a three-way merge, theme/library/boilerplate apps with subscriptions; App Builder AI (pages, SQL and table descriptions) |
+| App Builder and development | 21 | 0 | 0 | 0 | Page Designer with drag-and-drop and a code editor, wizards, search, where used, an Advisor, a CLI with one file per component, page locks and comments, supporting objects, working copies with a three-way merge, theme/library/boilerplate apps with subscriptions; App Builder AI (pages, SQL and table descriptions) |
 | Regions | 23 | 0 | 0 | 0 | All everyday regions, a search region over search configurations and a URL region; twenty-two chart types with drill-down; calendars with week/day/list views and drag and drop; faceted search, smart filters and a region display selector; interactive reports with breaks, aggregates, highlights, compute, group by, pivot, chart view and saved reports; interactive grids with single row, group by and chart views; maps (with vector tiles) and trees; template components; row ranges, lazy loading and region caching for large tables |
 | Items | 13 | 0 | 0 | 0 | All common items, file upload (several files per item), rich text and Markdown editors, star rating, combobox, date range, QR code, password reveal, display image and geocoded address |
-| Logic and processing | 17 | 0 | 0 | 1 | User preferences and application settings; all dynamic action events and actions, Ajax callbacks and an error handling function; Core APEX model complete with computations, conditional branches, build options and menu buttons, download, chain and workflow processes; JavaScript from static application files in dynamic actions; region, item, dynamic action and process plug-ins |
+| Logic and processing | 18 | 0 | 0 | 1 | User preferences and application settings; all dynamic action events and actions, Ajax callbacks and an error handling function; Core APEX model complete with computations, conditional branches, build options and menu buttons, download, chain and workflow processes; JavaScript from static application files in dynamic actions; region, item, dynamic action and process plug-ins |
 | Security | 22 | 0 | 0 | 0 | An editable login page and Forgot password; a session timeout warning; On par or stricter (CSP without `unsafe-inline`); OIDC, SAML and LDAP; header authentication behind a proxy; database accounts; custom authentication |
 | User interface | 12 | 0 | 0 | 0 | Region templates incl. hero, inline dialog and drawer, wizard and carousel; Universal Theme-like and responsive; a Theme Roller with style variants and conditional, dynamic styles; about 1,700 icons with Font APEX-like modifiers |
 | Globalization | 6 | 0 | 0 | 0 | One translated app like 26.1 with dynamic translations of table values; number format masks and automatic time zone; twenty-two built-in languages |
 | Data and integration | 13 | 0 | 0 | 2 | REST source catalogs from OpenAPI documents; Generate DDL and schema comparison; `meta.data_export` and data export downloads (CSV, JSON, XML, HTML, Excel, PDF); e-mail through SMTP (password or OAuth2), Microsoft Graph, Amazon SES and HTTP APIs; REST APIs via PostgREST, REST data sources that write back and synchronise, web credentials with OAuth2 grants, CSV/XLSX/JSON/XML loading with saved definitions and unloading, SQL scripts and Quick SQL, report PDFs and document templates |
 | Workflow, automation and AI | 6 | 0 | 0 | 0 | Scheduled automations with several actions and runs from SQL, approvals, a task list and workflows with parallel branches, versions and invoke-API steps; AI with Claude or OpenAI: *Generate text with AI*, an assistant region with tools, natural-language report filters and blueprints |
 | Administration | 12 | 0 | 0 | 0 | An APEX-like sign-in with a workspace and a Workspace home; a workspace's components exported and imported as one file; workspace message, environment banner and utilization; isolated workspaces with their own database logins and roles, and workspace administrators; application availability and Run only, automatic backups, user feedback; a developer toolbar with a session state viewer and debug per session; Top SQL per app; debug messages per request; an install/upgrade log |
-| **Total** | **144** | **0** | **0** | **3** | 147 APEX features compared: 98% available, none partial or missing |
+| **Total** | **146** | **0** | **0** | **3** | 149 APEX features compared: 98% available, none partial or missing |
 
 (Counts are of the rows in the tables below. A review on 2026-10-06 added 18 rows for APEX features that were
 not compared before, one on 2026-10-12 added two more (property help, application availability), and one on
@@ -43,6 +43,7 @@ two, REST source catalogs and the workspace export, with their features.)
 | Export / import | ✅ | `meta.export_app()` / `meta.import_app()`: portable JSON, also in the builder (new applications; `pgkiln import --replace` and the MCP `import_app` update one in place, live for every user at the commit). (sprint 51) **Checked imports**: `pgkiln import --check` (`--dry-run`, `--force`), the MCP import (by default) and the builder's import run the Advisor inside the import's transaction (SQL planned as the application's role: missing tables, columns, functions, types, grants; references) and refuse on errors, so nothing changes; APEX doesn't check. The version an import replaces is [backed up](guide/03-builder.md#backups) first ([chapter 18](guide/18-cli.md#checking-before-an-import)) |
 | APEXlang: human-readable, diffable app files; static IDs (26.1) | ✅ | `pgkiln export --format dir`: one JSON file per component with sorted keys, SQL and HTML in sibling files, references by static id instead of database ids; `pgkiln import --replace` updates an app in place, `pgkiln diff` compares ([chapter 18](guide/18-cli.md)). (0.31) **`--format text`**: the same files as YAML (a strict subset any YAML tool reads) with the SQL and templates inline, read back losslessly ([text files](guide/18-cli.md#text-files-apexlang)); regions have a stored **Static ID** (exported as their key, rendered as `data-static-id`), other components are named by their stored names. The syntax is YAML rather than APEXlang's own, so APEXlang files don't import |
 | Working copies, merge, team development | ✅ | **Working copies** of an application ([chapter 3](guide/03-builder.md#working-copies)): a second app on the same schema and data, compared three ways per component (settings, each shared component, page, region, item, …) with the main app as it was when copied; changes on one side merge, conflicts are chosen per component with a line diff; merge into the main app or refresh the copy, keeping users, sessions, saved reports, secrets and automation switches; locks respected. Conflicts are resolved per component, not per property |
+| Team Development: issues, labels, milestones, templates, feedback | ✅ | (sprint 113) Builder → **Team Development** ([chapter 3](guide/03-builder.md#team-development)): issues per workspace with labels in groups, milestones, assignees, application and page links, Markdown comments with in-app @mentions and a history; a filtered list with saved views and a board by label group or milestone (no JavaScript needed); a set-up wizard installs sample labels, templates, canned responses and milestones. Users' feedback and developer comments become issues; open issues show in the Page Designer, on App Home and on the Workspace home; issues travel in the workspace export. Not included: e-mail notifications, GitHub sync |
 | Application lock (26.1), page locks, comments | ✅ | Page and application locks, enforced on the server for every builder change; the owner or an administrator unlocks, and an administrator breaking a lock is logged. Developer comments per page and per app ([chapter 3](guide/03-builder.md)) |
 | Static application files | ✅ | Shared Components → **Static application files** ([chapter 3](guide/03-builder.md#static-application-files)): JavaScript, CSS, JSON, images and fonts uploaded or written in the builder, served at `/a/<alias>/static/<name>` with long caching per version, loaded by every page or by one page (APEX's *JavaScript/CSS File URLs*), exported with the application (as files in a directory export). No HTML; the CSP stays `script-src 'self'` |
 | Supporting objects (install scripts) | ✅ | Install, upgrade and deinstall scripts travel with the export (JSON and directory formats), never run on import; reviewed and run from the builder as the app's role, in one transaction, with a result per statement ([chapter 3](guide/03-builder.md#supporting-objects)) |
@@ -91,7 +92,7 @@ two, REST source catalogs and the workspace export, with their features.)
 | Text field, textarea, number, date picker, password, hidden, display only | ✅ | Native inputs, with the right phone keyboard (`inputmode`) |
 | Select list, radio group, checkbox, switch | ✅ | |
 | Checkbox group, shuttle / multi-select | ✅ | Colon-separated values, as in APEX |
-| Popup LOV | ✅ | `popup_lov`: a dialog with server-side search (paged, at most 100 rows a page) of the item's own shared, static or SQL list of values, extra display columns, return vs display value; the posted value is checked against the list; a select list without JavaScript ([chapter 5](guide/05-items.md)) |
+| Popup LOV | ✅ | `popup_lov`: a dialog with server-side search (loaded page after page as the dialog scrolls, at most 100 rows a request; ‹ / More without IntersectionObserver) of the item's own shared, static or SQL list of values, extra display columns, return vs display value; the posted value is checked against the list; a select list without JavaScript ([chapter 5](guide/05-items.md)) |
 | Cascading, shared and static lists of values | ✅ | `cascade_parents`, `LOV:NAME`, `STATIC:` |
 | E-mail, phone, URL, colour picker | ✅ | Typed inputs |
 | Read-only condition, required, help text, default | ✅ | |
@@ -120,7 +121,8 @@ two, REST source catalogs and the workspace export, with their features.)
 | Error handling function | ✅ | (sprint 52) `schema.function(jsonb) returns jsonb` (Settings → Errors and sessions): every message users see (raised, constraint, unexpected with its reference) can be rewritten, as the app's role with a time limit ([chapter 6](guide/06-processing.md#error-handling)) |
 | User preferences, application settings (`APEX_UTIL.SET_PREFERENCE`, `APEX_APP_SETTING`) | ✅ | (sprint 53) `meta.get/set/remove_preference`, and items with `{"persist": "user"}` keep their value per user across sessions; application settings with valid values and *required*, `meta.get/set_app_setting`, exported with the application and kept on upgrade |
 | APEX PL/SQL APIs | ✅ | `meta.app_user()`, `meta.has_role()`, `meta.v()`, `meta.page_url()`, `meta.message()`, `meta.html_escape()`, password functions, `meta.debug()`; **`meta.web_request()` / `meta.web_request_source()` + `meta.web_response()`** (APEX_WEB_SERVICE: queued and made by the server, right after the page process that queued it or by the scheduler after commit, through the allow-list/SSRF checks and the app's web credentials; responses kept 24 h) and **`meta.parse_data()` / `meta.parse_data_columns()`** (APEX_DATA_PARSER for CSV/TSV and JSON in SQL, same names and types as the data loader) ([chapter 9](guide/09-reference.md)). (070) **XML and Excel** in `meta.parse_data` (as the data loader reads them; Excel files that pgkiln received: uploads and web responses), **APEX_ZIP** (`meta.zip_add`/`zip_finish`/`zip_agg` build zips in SQL, `meta.zip_entries`/`zip_entry` read them), **BOOLEAN** state (`meta.v_boolean`), and a mapping from APEX_JSON to PostgreSQL's JSON functions ([chapter 9](guide/09-reference.md#zip-files-in-sql)). A synchronous HTTP call inside one statement needs the `http` extension ([chapter 15](guide/15-extensions.md)); `meta.web_request` is queued by design |
-| Declarative menu buttons, button badges (26.1) | ✅ | Menu buttons with links and submit requests (a hidden button can't be reached through a menu), works without JavaScript; badges as text with `&ITEM.` or from SQL ([chapter 6](guide/06-processing.md#menu-buttons-and-badges)) |
+| Declarative menu buttons, button badges (26.1) | ✅ | Menu buttons with links, submit requests and (sprint 115) dynamic actions (event *Menu entry chosen*, `menu_entry`) (a hidden button can't be reached through a menu), works without JavaScript except action entries; badges as text with `&ITEM.` or from SQL ([chapter 6](guide/06-processing.md#menu-buttons-and-badges)) |
+| Wait Popup (26.1) | ✅ | (sprint 115) `wait_popup` / `remove_wait_popup` dynamic actions: a modal dialog with a status message (aria-busy, Escape-proof), shown until removed or the next page; `pgkiln.waitPopup()` in JavaScript ([chapter 7](guide/07-dynamic-actions.md#wait-popup)) |
 | Plug-ins | ✅ | **Region, item, dynamic action and process plug-ins** with their own code ([chapter 4](guide/04-pages-and-regions.md#plug-ins-with-their-own-code)): one `pgkiln-plugin/2` file with custom attributes, JavaScript and CSS (static application files, registered with `pgkiln.plugins.register`; the CSP stays strict), a template component for regions, a PL/pgSQL function for processes and install SQL that a developer reviews and runs; Shared Components → Plug-ins, `pgkiln plugin build|install`, four examples. Template component plug-ins (`pgkiln-plugin/1`) as before. Authentication and authorization plug-ins: custom authentication and SQL authorization schemes cover them |
 | Build options | ✅ | Include / exclude (and `!NAME` for the reverse) on pages, regions, items, buttons, dynamic actions, validations, processes, computations, branches, navigation entries and application processes; fail closed; *Used in*, Advisor and export ([chapter 6](guide/06-processing.md#build-options)) |
 | Collections (`APEX_COLLECTION`) | ➖ | Temporary or unlogged tables, or `jsonb` in session state |
@@ -204,10 +206,10 @@ two, REST source catalogs and the workspace export, with their features.)
 
 | APEX | pgkiln | Notes |
 |---|---|---|
-| Approvals and task list | ✅ | Task definitions (approval / action, owner roles and users, business administrators, priority, due date, details page), `meta.create_task` from application SQL, a task list region (claim, approve/reject/complete with comment, release, delegate, cancel, history), completion SQL in the same transaction. (sprint 64) **Vacation rules** (a stand-in acts on a user's tasks while the rule is active, checked on every request) and **expiration policies** (expire, renew up to N times, escalate to a role once; a waiting workflow goes on with the outcome `expired`). **Missing:** built-in e-mail notifications (send them with `meta.send_mail` from the completion SQL or an automation) |
-| Workflow (26.1: parallel flows, multi-tenancy) | ✅ | Workflow definitions of task, SQL, switch, wait, **invoke API** (a REST data source or URL through the invoke-API code, response values and the HTTP status into variables, retryable faults, no transaction open during the call) and end steps with variables, started from application SQL, run by the server (NOTIFY + polling) as the app's role; console region (terminate, retry a faulted step); diagram in the builder. **Parallel branches** (split, then a join that waits for all or for the first branch) and **versions** (development, active, inactive; running instances keep theirs) ([chapter 6](guide/06-processing.md#workflows)). (0.31) **Tenants**: `meta.set_tenant()` (APEX: `APEX_SESSION.SET_TENANT_ID`); workflows, their tasks, background chains, the task list, the console and every action follow the session's tenant ([chapter 6](guide/06-processing.md#tenants)). No *Send E-Mail* activity: send mail with `meta.send_mail` from an SQL step |
+| Approvals and task list | ✅ | Task definitions (approval / action, owner roles and users, business administrators, priority, due date, details page), `meta.create_task` from application SQL, a task list region (claim, approve/reject/complete with comment, release, delegate, cancel, history), completion SQL in the same transaction. (sprint 64) **Vacation rules** (a stand-in acts on a user's tasks while the rule is active, checked on every request) and **expiration policies** (expire, renew up to N times, escalate to a role once; a waiting workflow goes on with the outcome `expired`). (sprint 114) **custom outcomes** with labels and colours (Yes / No / Undecided), **task events** on complete, expire and a failed completion SQL (SQL, e-mail or start a workflow; reopen or keep the task) and **notifications** from e-mail templates on create, complete and expire ([chapter 6](guide/06-processing.md#custom-outcomes)) |
+| Workflow (26.1: parallel flows, multi-tenancy) | ✅ | Workflow definitions of task, SQL, switch, wait, **invoke API** (a REST data source or URL through the invoke-API code, response values and the HTTP status into variables, retryable faults, no transaction open during the call) and end steps with variables, started from application SQL, run by the server (NOTIFY + polling) as the app's role; console region (terminate, retry a faulted step); diagram in the builder. **Parallel branches** (split, then a join that waits for all or for the first branch) and **versions** (development, active, inactive; running instances keep theirs) ([chapter 6](guide/06-processing.md#workflows)). (0.31) **Tenants**: `meta.set_tenant()` (APEX: `APEX_SESSION.SET_TENANT_ID`); workflows, their tasks, background chains, the task list, the console and every action follow the session's tenant ([chapter 6](guide/06-processing.md#tenants)). (sprint 114, 26.1 / 26.2) **Send E-Mail** steps (a template or subject and body), **draft** steps allowed only in development versions, branching on custom task outcomes, **migrating running instances** to a newer version (step mapping, preview, one transaction, a log; not yet for instances inside open parallel branches: [chapter 6](guide/06-processing.md#migrating-instances)) and the diagram as **SVG / PNG** |
 | Automations (scheduled) | ✅ | Shared Components → Automations: cron schedules with time zones, once or per row of a query, **several ordered actions** with their own conditions, **error handling** (stop, skip the row and continue, or disable; row errors in the run history), roles, run history and Run now, **on-demand runs from SQL** with `meta.run_automation()` (like `APEX_AUTOMATION.EXECUTE`, synchronous in the caller's transaction), safe with several servers ([chapter 6](guide/06-processing.md#automations)) |
-| AI assistant, natural-language reports (NL2IR), AI agents and tools (26.1) | ✅ | Region type **AI assistant**: a conversation per session, context queries (RAG over developer queries, run as the app's role, read-only), and **tools** the model may call: SQL with bound arguments checked against declared parameters (read-only unless marked as writing, row limit, timeout) and REST data sources, each optionally behind an authorization scheme. **Natural-language report filters**: an "Ask in your own words" box turns a question into the report's normal filters, search and sort, limited to its visible columns ([chapter 4](guide/04-pages-and-regions.md)). Agents are defined per region (not as shared components); answers are not streamed. `pgvector` covers semantic search on the data side |
+| AI assistant, natural-language reports (NL2IR), AI agents and tools (26.1) | ✅ | Region type **AI assistant**: a conversation per session, context queries (RAG over developer queries, run as the app's role, read-only), and **tools** the model may call: SQL with bound arguments checked against declared parameters (read-only unless marked as writing, row limit, timeout) and REST data sources, each optionally behind an authorization scheme. **AI Interactive Reports** (sprint 112; 26.1 / 26.2): an "Ask in your own words" box turns a question into the report's own settings (filters, highlights, search, sort, control break, totals, group by, pivot, chart and computed columns such as "bonus is 10% of salary"), never SQL, limited to its shown columns; each setting is a chip with Edit and Remove, plus Undo. Without an AI service a built-in phrase parser (English, Dutch, German) answers ([chapter 4](guide/04-pages-and-regions.md#ask-in-your-own-words-ai-interactive-reports)). Not yet: phrases mapped to faceted search and smart filter values. (sprint 111) **AI Agents** as a shared component (26.1 / 26.2): an AI service, system prompt, reasoning effort (low / medium / high, mapped per provider), approved tools, max steps and tokens and an authorization scheme; an assistant region names one. **AI Tools**: SQL (read-only transaction, the app role through RLS, timeout), PL/pgSQL function, REST data source, JavaScript action (a registered action or custom-event dynamic action), and **Navigate**: pgkiln builds the checksummed URL, only to pages the user may open. Every tool call is logged with its arguments (debug and Activity → AI usage). Providers add Gemini and OpenAI-compatible endpoints (Ollama, vLLM, Azure OpenAI). Answers are not streamed; no OCI provider. `pgvector` covers semantic search on the data side |
 | *Generate Text with AI* process, structured outputs (26.1) | ✅ | **AI services** (Workspace utilities, administrators): Claude through `@anthropic-ai/sdk` or OpenAI through `openai`, encrypted write-only keys (or `ANTHROPIC_API_KEY` / `OPENAI_API_KEY`), per-app access with daily request and token limits, a usage log. Page process `ai_generate` (text into an item, or structured output into several items with a schema built from the items or your own) and a dynamic action that runs it without a page submit; `meta.ai_generate` / `ai_result` / `ai_available` from SQL ([chapter 6](guide/06-processing.md)). Prompts, item values included, go to the chosen provider |
 | Blueprints, spec-driven development (26.1) | ✅ | Create → **From a blueprint**: a JSON spec of tables (types, required, unique, allowed values, references), pages, navigation and sample data; optionally drafted by AI from a description; always reviewed (problems, SQL, pages, menu) before the application is created in one transaction; saved blueprints; (sprint 66) **a blueprint from an existing application** (its tables, pages, menu and optionally sample rows, with notes on what didn't carry over) |
 
@@ -333,7 +335,7 @@ Sources: [APEX 26.1 new features](https://docs.oracle.com/en/database/oracle/ape
 | Workflows, Task Definitions, Automations | The same names |
 | Text Messages, Translate, Dynamic Translations, Globalization Attributes | Translations and Text Messages, Dynamic Translations, Settings → Globalization |
 | Map Backgrounds | ➖ Not planned per application: the installation's map tile server (`MAP_TILE_URL`) is every map's background |
-| AI Attributes, AI Services, AI Agents | AI Services; AI agents ➖ not planned |
+| AI Attributes, AI Services, AI Agents | AI Services; AI Agents and AI Tools (sprint 111) |
 
 ## Database Actions (SQL Developer Web) and the SQL Workshop