Skip to content

RivetIT 26.10.81

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 03 Nov 02:53
· 295 commits to production since this release

Integration release of the issue #30-#36, #43, #52 / #55 work, #37 (docs) and #29 (docs and tests). Database 2.6.211 to 2.6.231 (21 additive, idempotent steps; take a database dump first, then Administration > Update > Update Database, or php scripts/update_cli.php --update_db). Nothing risky is switched on by this release; several parts are verified against local mocks only and are marked UNVERIFIED LIVE.

  • Service catalog, issue #30: categories, computed risk and routing, parallel approvals, delegation and timeouts, repeating tables, catalog report (database 2.6.211 and 2.6.212). Everything is additive and off by default; existing catalog items behave exactly as before.

    • Category tiles. New Categories list on Administration > Service Catalog (name, description, icon, order); pick one per item. Request Something (agent and portal) shows a row of category tiles with request counts above the item tiles and filters when one is clicked. Items without a category are listed under Other.
    • Computed risk score and risk-based routing. An item's score is now a base plus risk rules (an answer equals / is one of / is answered / is at least / is at most a value: plus or minus points, kept between 0 and 100). The computed score and its breakdown are stored on the request and shown on the ticket page; it decides the auto-approve test and which approval steps apply (every step has a risk band, default 0 to 100), so a high-risk request can need an extra approver.
    • Parallel approval steps. Tick Parallel on a step to decide at the same time as the step above it; the next stage starts when every parallel step is satisfied. One rejection ends the request; one person in two parallel steps decides once.
    • Out of office, reminders, escalation, timeouts. Agents can hand their approvals to a colleague for a period (Approvals page). Each item can set a reminder interval, an escalation time (the active administrators are added and can decide the stage) and a timeout (the request is rejected and its ticket closed), in hours (0 = off). The new worker cron/catalog_approvals.php (required from cron/cron.php) does the work and stays off until an administrator ticks Approval worker on the Service Catalog admin page (settings.config_catalog_approval_cron).
    • Repeating table questions and multi-condition show/hide. A new Table question type (columns Heading|text|number|date, up to 8 columns and 25 rows, every cell validated on the server, shown as a table on the ticket and approval pages) and up to three conditions per question combined with all/any.
    • Report. Reports > Service Catalog Requests: request volume, approved / rejected / waiting, rejection rate and approval turnaround per item, category and day, department scoped, CSV export, saveable and schedulable.
    • API. GET /api/v1/service_catalog.php now also returns categories, each item's category_id, a table question's columns and compound show_if rules; POST is unchanged for existing clients and now runs through ServiceCatalogService::createRequest(), the entry point for chat integrations (issue #36). An older mobile app does not know the table question type.
      Deploy notes: take a database dump first, then run the database update. Two additive, idempotent steps (2.6.210 -> 2.6.211 -> 2.6.212). Reminders, escalation and timeouts only run after the Approval worker is switched on.
  • Employee lifecycle automation (issue #31)

    • Role-change and department-transfer workflow templates, with employee.role_changed and employee.transferred events and start rules.
    • The Microsoft and Google directory syncs now raise hire / departure / role-change / transfer events (only when "Start workflows automatically" is on).
    • Onboarding form (questions asked when a workflow starts, usable as {{var.name}}) and conditional tasks (department, job title, employee type, form answer); the dry run shows what is left out.
    • Delayed tasks ("archive the record 30 days after the end date"): scheduled status, run now / skip, released by cron/workflow_cron.php.
    • New actions: assign / collect devices, archive the record, Microsoft 365 licences, mailbox automatic reply, Odoo create / archive (off by default, own setting), identity-system connectors (stubs).
    • Bulk start for many people (email list / CSV, and from the People import); built-in presets and starter templates.
    • Database 2.6.213 and 2.6.214.
    • Unverified on real systems: Entra licence / mailbox actions, Odoo actions, identity connectors, directory-sync events (see docs/EMPLOYEE-LIFECYCLE-WORKFLOWS.md).
  • Employee portal (issue #32): announcements (new Settings > Portal announcements page; all departments or one; schedule, expiry, pin, plain text) shown at the top of the employee home and in a new notification feed with an unread badge.

  • Help articles (popular this month, new and updated) on the employee home; portal article reads are counted.

  • My devices shows a card per device with OS, last seen, warranty and restart-needed.

  • Employee API: /api/v1/portal_auth, portal_home, portal_devices, portal_checklist, portal_announcements, portal_notifications with their own hashed tokens (not usable on the staff API). Not yet verified against a live install.

  • The employee home no longer shows the stat tiles (department administrators keep the original page). Two new home sections, announcements and kb, are added to existing installs that had chosen their sections.

  • Database 2.6.215-2.6.218 (new tables portal_announcements, kb_article_views, portal_api_tokens, portal_feed_state; settings column default).

  • Automation engine, issue #33: more triggers, more actions, an API and a retryable run log (database 2.6.219 - 2.6.222). Nothing risky is switched on by this change.

    • New events for event rules: employee.created, employee.disabled (needs Employee workflows auto-start, and only raised while a rule or webhook names them), employee.offboarded (an offboarding workflow completed), asset.assigned (every assignment path), and, raised by cron only for events something listens to and once each, asset.offline, asset.online, certificate.expiring (at the configured number of days, then 7, 1, 0), credential.rotation_due (never carries the username, password, OTP seed, note or URL) and schedule.hourly|daily|weekly|monthly clock ticks (conditions on hour, weekday, day_of_month make "every Monday at 8").
    • Conditions beyond payload keys: rules can now test department, location_name, asset_type, asset_status, user_group, user_role, job_title, employment_status and more; they are looked up from the ids in the event before matching (never overwriting what the event carries) and also fill {placeholders}.
    • New rule actions: Run an RMM script (OFF until Allow rules to run RMM scripts is switched on; the job is created as a named technician through the RMM module, so permissions, platform checks and second-person approval apply; the script and parameters are fixed in the rule), Entra: disable the person's account and Entra: add the person to groups (the workflow actions, reused: write switch OFF by default, department check, never deletes), Send a chat message (calls a pluggable ChatNotifier; no Slack/Teams sender ships here, issue #36 plugs in) and Create an Odoo user (switched OFF and no Odoo write connection ships: contract and tests only; production Odoo is never written).
    • Run log: each try of the job queue shows as try N of 3 (and gave up); a failed run keeps its event so an administrator can Run again from the History drawer or the Run log tab (refused when it already succeeded on a retry, so nothing is done twice; audited).
    • Legacy ticket rules: Automation > Ticket rules lists which of them have an event-rule equivalent (asset online/offline + notify) and imports a switched-off copy on request; the old rules are untouched and keep running. The rest are listed with the reason they stay a separate engine.
    • API: GET/POST /automation_rules, GET/PUT/PATCH/DELETE /automation_rules/{id}, GET /automation_rules/runs[/{id}], POST /automation_rules/retry/{run_id}, GET /automation_rules/meta (administrators, user token only; documented in openapi.yaml and docs/API.md).
    • Not proven live: running a script on a real device, the Entra actions against a real tenant, chat delivery and anything in Odoo; see docs/AUTOMATION.md, "What is not proven live".
      Deploy notes: take a database dump first, then run the database update. Four additive, idempotent steps: automation_rules (five new action_type values, source_legacy_id unique), automation_rule_runs (context_json, attempt, trigger_source, retry_of_run_id), new table automation_emit_marks, and three settings.config_automation_* columns (both risky-action switches default 0).
  • Reporting and dashboards, completed (issue #34; database 2.6.223 and 2.6.224). Everything below is additive; existing reports, saved views and schedules behave as before. Nothing is switched on by this change.

    • PDF reports. Every catalogued report now has Download PDF in its toolbar (?export=pdf) next to Export CSV and Print. The PDF is made on the server with the TCPDF already bundled in plugins/TCPDF (no browser, no extra program) from the same tables as the CSV, so the three always agree; it states the date range and the filters used. A new schedule delivery, PDF attached to the email, sends the PDF as a real attachment: the mail queue can now carry attachments (email_queue_attachments, removed as soon as the message is sent or its queue row is deleted).
    • Quarterly schedules. A new Quarterly frequency (due again 3 months after the last send) for every schedule type, including the original headline summaries.
    • Reports hub headline row. Open Tickets, Mean Resolution Time (30 days), SLA Compliance (30 days), Tickets This Month and User Satisfaction (30 days, when CSAT is on), then Unassigned and Opened Today. All respect the viewer's department restriction.
    • Universal report filters. Service Desk and SLA, Tickets, Tickets: Day by Day, Time by Technician, Technician Performance and Customer Satisfaction (and the new SLA and backlog reports) now filter by department, location, technician, category, priority, status and asset. The Filters button in the report toolbar opens the panel; the filters are saved in saved views, replayed by schedules and shown on printed and PDF output. Values are validated against fixed lists or whole numbers, and combine with (never widen) a user's department restriction.
    • New reports. SLA Breach and Aging (response and resolution breaches in a date range, compliance, breaches by priority, technician and department, how long open tickets have been overdue, the breached tickets), Ticket Backlog (open tickets by age, status, priority, technician and department, a weekly backlog trend, the oldest open tickets) and Asset Lifecycle and Warranty (warranty expired or expiring, device age, replacement candidates, by type and department). Each is in the hub, the side menu, saved views, schedules, CSV and PDF.
    • Recipient groups and per-group views. On Scheduled Reports, create recipient groups (for example Executives, Service desk) and let one schedule send a different saved view to each group. Addresses must be active agents or administrator-approved recipients, checked when the group is saved and again each time cron sends. A failing group is named in the schedule's status without resending the groups that succeeded.
    • Tests. Six new test files under tests/i34_*: migrations (fresh vs upgraded SHOW CREATE TABLE), filters and PDF, report queries on fixture data, the existing report helpers with filters on, the scheduler with recorders, and a real SMTP hand-off to a throwaway local listener proving the PDF arrives byte for byte.
      Deploy notes: take a database dump first, then run the database update. Two additive, idempotent steps: 2.6.223 (email_queue_attachments) and 2.6.224 (report_recipient_groups, report_schedule_targets). No new settings, cron entries or permissions. Verify on the live mail setup that one PDF schedule arrives with its attachment (a real mailbox is the only thing the tests could not reach).
  • Entra ID / Intune sync, scheduled and incremental (issue #35, DB 2.6.225 to 2.6.226)
    Everything new is off by default and read-only towards Microsoft. Mock-tested only (tests/mock/graph_mock.php); UNVERIFIED LIVE, see the live checklist in docs/ENTRA_INTUNE_SETUP.md.

    • Scheduled Entra directory sync from cron (opt-in, every 1 h to daily) beside the Intune device sync.
    • Incremental sync with Graph delta queries. The first run saves a delta token; later runs read only changed users; users deleted in Entra are archived like disabled ones; an invalid token (410) falls back to a full read by itself. New microsoft_directory_users link table (Entra user id to contact): a renamed mailbox now updates its contact instead of creating a second one.
    • Previews (dry run) for the directory sync, Intune device sync, groups, licenses and Intune details: the real counts, inside a rolled-back transaction, logged separately and ignored by the sync watch.
    • Entra groups and members, license SKUs (purchased/consumed, who holds what) and Intune compliance policy states and detected apps per device (shown on the asset page).
    • Client-secret expiry: date field plus an optional lookup in Entra; alerts at 30 days, 7 days and on expiry (event integration.secret_expiring).
    • Stalled / failing sync watch now covers the scheduled directory sync and the new syncs; Admin > Update > Checks and Server status show the secret expiry and sync health.
    • Entra / Intune sync status page (/admin/entra_status.php): per sync last run, counts, classified error, next due, run and preview buttons; license, group and Intune-detail summaries.
    • Test Connection now probes groups and licenses when they are switched on. New migrations: 2.6.225 (columns on microsoft_integrations, sync logs, microsoft_directory_users), 2.6.226 (entra_sync_log, entra_groups, entra_group_members, entra_licenses, entra_user_licenses, intune_device_compliance, intune_device_apps, asset_intune_links.details_synced_at).
  • Slack and Microsoft Teams chat (issue #36), all off by default: Slack Events API (two-way ticket threads, direct messages and mentions to the virtual agent), /ticket slash command, ticket modal and message shortcut, status / priority / reply and approve / deny actions, explicit identity links with an optional email fallback, KB and service-catalog virtual agent, ChatActions / ChatNotifier services for other modules, Slack app manifest and Teams app package generators (Administration > Settings > Chat), and a Teams Bot Framework endpoint with JWT validation. Database 2.6.227 to 2.6.229. Proven against local mocks only; Teams and all Slack parts are unverified live (docs/CHAT_LIVE_VERIFICATION.md).

  • Quality module: the integration with the separate quality management system (issues #52 and #55; database 2.6.230 and 2.6.231). Everything is off until an administrator turns it on. RivetIT does not become a QMS: it shows each person their own items from the QMS, sends it changes, and signs people in to it.

    • Administration > Quality (new): the module switch (also under Settings > Modules), the QMS address (https only, checked against SSRF when saved and before every call, connection pinned to the vetted address, no redirects), client id and secret (sealed, write-only), Test connection, two signing secrets (shown once), the departments and the features that are enabled, timeouts and sync intervals, Sync health (ok / degraded / failing, with reasons), Run sync now, Queue full resync, the outbound and inbound event lists with Replay for dead-lettered events, and the integration error log (no secrets or personal data; the same correlation id the QMS logs).
    • Department portal: a Quality tab with My tasks, Corrective actions, Documents, Training, Notifications and History, plus a Department view for managers (overview, corrective actions, overdue tasks, training compliance, pending acknowledgments). Items are read live for the signed-in person and shown with the time they were read; when the QMS cannot be reached the page says so with a reference and shows nothing rather than stale data. Acknowledging a document or answering a corrective action asks for the password again unless the sign-in is fresh. Kiosk: counts, required training and document acknowledgment with the PIN; corrective actions never appear on a shared screen.
    • QMS client with a per-user context: OAuth 2.0 client credentials; every request for a person's items also carries a 60 second signed context (ES256, the SSO provider's key) naming that person, their department and role; the client refuses a person's request without one, and the QMS must authorize per person. Bounded retries with backoff, timeouts, a 1 MiB response cap and correlation ids.
    • Events: signed (HMAC-SHA256, 5 minute window), versioned, deterministic ids. RivetIT queues lms.assignment.*, lms.completion.*, employee.updated, employee.deactivated and department.updated (identifiers only, only for the enabled departments) with retry, dead letter, replay, a daily reconciliation window and a manual full resync. New inbound endpoint POST /api/v1/integrations/qms/events (scope quality:events, also signed, replay-protected) stores the QMS's own ids for people and departments (never matched by name) and lets the QMS ask for a resync.
    • Single sign-on (#55): the Quality module switch and the department list now gate the OpenID Connect provider (module_disabled, department_not_enabled); the portal "Open Quality system" button and the administrator menu entry follow. The seed row of oidc_provider_settings is now in db.sql (a fresh install could not switch the provider on).
    • Docs and tests: docs/QUALITY_CONTRACT.md is the exact contract the QMS must implement; docs/integrations/qms-configuration.md and qms-troubleshooting.md are new; OpenAPI and docs/API.md list the new endpoint. tests/quality_module.php (mock QMS in tests/support/mock_qms.php) and tests/quality_ssrf.php.
      Deploy notes: take a database dump first, then Update Database. Two additive, idempotent steps (2.6.229 -> 2.6.230 -> 2.6.231): settings.config_module_enable_quality (0), quality_settings, quality_features, quality_departments, quality_error_log, quality_outbox, quality_inbound_events, quality_sync_state, quality_id_map. Nothing is switched on. New cron entry cron/quality_worker.php (every 5 minutes, written by deploy/install.sh; exits at once while the module is off); on an existing server add it to the cron file or re-run the installer's cron step. Not verified against the real QMS (Datum): see the go-live checklist in docs/integrations/qms-configuration.md.
  • Training kiosk: pick tablets, one Web Clip profile per iPad (issue #43)

    • Fleet links > Per-device URLs and profiles now lists the department's tablets with a usable serial. Tick the ones you want, then download a CSV (device name, serial, type, start URL) or a ZIP with one .mobileconfig Web Clip per iPad (its own serial in the URL, Full Screen, not removable, kiosk icon embedded, stable PayloadUUIDs per device). Limit 300 tablets per ZIP; foreign-department, archived, non-device and unusable-serial assets are ignored. Needs the Training kiosk permission at level 3 plus Assets view, and the once-shown link token.
    • New API action fleet_device_profiles (Training kiosk admin API); each download is audited (training.kiosk_fleet_profiles).
    • No database change (the fleet-link schema is DB 2.6.151). Docs: docs/training-kiosk-setup.md. Tests: tests/kiosk_fleet_links.php.

Docs: added COMPETITOR_RESEARCH_FRESHSERVICE_JSM.md (Freshservice and Jira Service Management feature matrix, sourced 2026-11-01, prioritized gaps) and refreshed ROADMAP section 3.6 and open question 4. No code or database changes.

  • Security and permissions (issue #29)
    • New installs now give the built-in Technician role Knowledge Base Modify access (browser installer and setup_cli.php). Reporting stays an explicit administrator grant. Existing installs are unchanged; no database change.
    • Re-verified the 22 security/permission items from the user-guide findings against current code; most were already fixed. docs/user-guide/tools/app-findings.md now carries a status table and tests/security_findings_i29.php pins the guards.