Skip to content

Releases

RivetIT 26.10.88

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 17 Nov 02:55

Onboarding/offboarding as tickets (switch off by default; portal New hire / Leaver items), worksheet on ticket templates, Clone for ticket/workflow/worksheet templates and automation rules, Workflows list page, New from workflow on Tickets, Employee Workflow editor redesign, blank-page fix when adding a preset. Needs database update 2.6.236 (Administration > Update; set a backup passphrase first). See CHANGELOG.md.

RivetIT 26.10.87

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 16 Nov 20:21

Rolls up 26.10.86 and 26.10.87: ticket list/status redesign, Counts-as-closed ticket status flag, ticket time zone fix and DB repair (2.6.234/235), credentials TOTP widget, asset details card fix, new asset types (Server Room, Rack, UPS/Power, Storage/NAS), Employee Workflow editor redesign. Database updates run from Administration > Update. See CHANGELOG.md.

RivetIT 26.10.85

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 13 Nov 15:46

Requires RivetCore 1.0.0-rc.60 (CSS/JS and agent fixes; its migration 0049, the "managed by another RMM" installer column, is not used by RivetIT yet and is applied by the database step that adopts the feature).

  • No underline on hover, anywhere. One last rule in the shared design CSS overrides Tabler's hover underline and every per-page copy of it (asset names, interface links, report, training and webhook links, kanban task titles).
  • Assets list: no sliver above the sticky table header. Collapsed borders painted the sticky header about a pixel low, so scrolled rows showed through above it.
  • RMM Assets: advanced filters. Search, integration, status, department (including "none assigned"), last seen (within an hour to 30 days, or not seen for 7 or 30+ days), operating system, manufacturer and model, remote agent, asset record and rows per page; health checks (needs reboot, patches pending, maintenance mode, disk, CPU or memory 85% or more); removable filter chips, sortable columns, paging, status pills, disk-usage bars and reboot/patch badges, tiles for reboot and patches.
  • Fix: "N of N could not be assigned" on RMM Assets. Assigning a department (single or bulk) failed with "No integration configured" when no default RMM integration was set; it needs none. The dialog now also says why a bulk assignment failed.
  • Hypervisor host page redesigned (Proxmox/Hyper-V): at-a-glance tiles, a clear banner when the collector reports a problem or the host is stale, aligned cluster/storage/VM cards with usage bars, the VM filter in the card header. A Proxmox host with ceph-common but no Ceph cluster no longer shows "ceph: /usr/bin/ceph exited with status 1" (server drops it from reports of older agents; new agents do not send it).
  • API: POST /api/v1/tickets accepts asset_id (must belong to client_id).
  • Alerts: the Critical + error open tile is highlighted only when both its filters are active. Asset edit modal: the Details grid shows only while its tab is active.
  • Tickets: a ticket in a Resolved or Closed status is no longer counted or listed as unresolved. The open/closed split also looks at the status name, so tickets moved to Resolved by the API, the Kanban board or an older version leave the Unresolved tile, the Open count and the open list.
  • Ticket status pills use a light tint of the status colour with a darker shade for the text (deep tint, light text in dark mode), so neon, near-black and pastel status colours stay readable.
  • Empty ticket lists say why. The empty state names the applied filters (including a saved default view) and offers "Show all open tickets", "Include closed" or "Clear filters".

RivetIT 26.10.84

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 06 Nov 16:35
  • Production branch renamed. The production release channel now follows the git branch production (it was main). New installs and the setup script use it. A server already on the Production channel needs one step after this release: git fetch origin && git branch -m main production && git branch -u origin/production production. Servers on Beta are not affected.
  • Settings. Tiles for Compliance framework, Security and trust, and Reporting / Power BI on the settings hub.
  • Telemetry page removed. RivetIT sends nothing anywhere; the Settings > Telemetry page and its installation-ID display are gone (the ID is still used internally to sign calendar-feed links).
  • Funding. .github/FUNDING.yml (GitHub Sponsors).

RivetIT 26.10.83

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 05 Nov 02:11

Release candidate 2 on top of 26.10.81: issue #29 leftovers, #31/#33 lifecycle follow-ups, #36 Teams/Slack buttons, #30 risk score display, plus test, accessibility and API-doc work. Database 2.6.231 to 2.6.233 (2 additive, idempotent steps; take a database dump first, then Administration > Update > Update Database).

Reversed decisions: in docs/FINDINGS-DECISIONS.md, item 11 (company-wide vendors stay Financial-only) is superseded by item 13, and item 12's "no UI moves a person to another department" row is superseded by item 14 (Move department).

Added

  • Move department (issue #29 leftovers): People row menu. Moves a person to another active department (needs Departments at Modify and access to both). Their devices and licence seats in the old department are unassigned by default (a box keeps them), the location is kept only if the new department can use it, the primary-contact flag is cleared, the move is audited, and employee.transferred is raised through the existing lifecycle detection when Employee workflows auto-start is on. Web only, no API equivalent.
  • Users export has an Include archived users box; archived agents are then listed with the status Archived.
  • HR requests from the employee portal (issue #31): managers and department administrators can ask HR to start an onboarding, offboarding or role-change workflow (portal menu HR requests, off until Administration > Settings > Employee portal > "Allow HR requests from the portal" is ticked, DB 2.6.232). The request waits for an HR agent (Service desk > HR requests, also GET/POST /api/v1/hr_requests); nothing starts and no record changes until it is approved, and rejecting or withdrawing starts nothing. Department scoped (a manager can name only their reports), audited, in-app notification to eligible HR agents. Approving picks the template and starts the run through the normal workflow code.
  • Okta workflow actions (issue #31): create a user (staged, no password, no activation email), suspend a user and clear their sessions (never delete), and add a user to groups, as workflow tasks. Off by default (Administration > Employee Workflow Templates > Okta actions; domain, encrypted API token and the "Allow workflows to change Okta" switch, DB 2.6.233). Department check, idempotent, token never in messages, logs or audit. Tested against a mock only; not verified against a real Okta org.
  • Legacy ticket rules in the Event rules tab (issue #33): every older ticket rule is listed read-only with its state; a rule that has an event-rule equivalent has Convert to event rule (a switched-off copy, the legacy rule keeps running) and then Switch over (copy on, legacy off, one confirmed step). Rules with no equivalent stay as they are, with the reason.
  • Workflow approval tasks reach approvers in Slack / Teams through the existing chat layer (ChatNotifier::approvalRequested); covered by a new end-to-end test. No new chat code.
  • Teams ticket buttons via a relay (issue #36). A Microsoft Teams webhook destination with an interactive-action token (Edit webhook > Generate) posts Acknowledge and Assign to me (Action.Submit) next to Open ticket. A relay flow you own forwards each click to /teams_interactive.php, authenticated with that per-destination token (constant-time compare, never in the card), a 5 minute timestamp and single use; the clicker is matched to exactly one active agent by email with the same role and department rights as Slack. No migration. Loopback-tested only, never a real Teams tenant. See docs/SLACK_TEAMS_SETUP.md.
  • Service catalog risk score is visible (issue #30). The admin-set risk score shows as a banded Risk n (Low / Medium / High) badge in the admin catalog list, the agent Request Something tiles, the ticket's Request details block, and the agent and portal approval inboxes. No migration.
  • One-click catalog request in chat (issue #36). With "actions from chat" on, catalog results from the Slack and Teams virtual agent show a Request this / Request button that raises the request for the linked user (same rules as request <id>: required questions go to the portal, approval items wait for approval). Tested with signed Slack simulators and a mocked Teams connector only.

Changed

  • Company-wide vendors (reverses the earlier decision that they stay Financial-only): a role with Tickets, assets & docs can list and open them (Read) and add, edit, archive and restore them (Modify). The account number, Delete and the vendor CSV stay Financial-only; without Financial the account number is hidden from the list, search, details and forms and is never changed by that role's edits.
  • Deleting an RMM check policy now asks the RMM to remove the checks it already pushed to agents. If any cannot be removed the policy is kept, those deployments are marked remove_failed, and Delete anyway (which writes the device names and check ids left on agents to the audit log) is offered.
  • The Waiting on Employee dashboard tile also counts open tickets in any status flagged "waiting on someone else" (pauses the SLA clock), not only the two names.
  • Mobile API: a catalog table answer now accepts JSON null for an empty cell (it was a 422). docs/MOBILE_API.md documents answering table questions with an example and the limits, and the new /hr_requests endpoint.

Fixed

  • Users CSV listed Department Portal logins; it is now agents only (what the Users list shows).
  • Bulk department email mailed the contacts of an archived department when it was selected.
  • Licence seat links: a forged asset or person id from another department was linked on add or edit; only the licence's own department can be linked now.
  • Departments date range: a custom range with only a From (or only a To) date showed ... - Dec 31, 2099 (or 1970) after the page reloaded; it now reads From Jan 15, 2026 / Up to ....
  • deploy/restore.sh refused a backup whose inner manifest is encrypted although it already requires --passphrase-file; it now decrypts the manifest with that file.

Tests, accessibility and API docs

  • API: api/v1/openapi.yaml now documents the endpoint agent's agent_changes, agent_logs, agent_transfer, agent_software and agent_linux_file, the local build host protocol /build_host/{action}, and the RivetPanel device API (panel_enroll, panel_me, panel_categories, panel_tickets, panel_ticket_chat), with the new panelAuth and buildHostAuth security schemes.
  • scripts/check_openapi_drift.sh forces LC_ALL=C so comm sees byte-sorted input (it reported false drift for hyphenated resource names under a UTF-8 locale); it now exits 0.
  • Accessibility: portal and announcement pages no longer skip heading levels; the amber "not verified" badge, amber device status text on portal cards on Chat settings, outline buttons in dark mode and urgent portal announcements in dark mode now meet WCAG AA contrast.
  • Tests: the browser suites take their scratch database from RIVETIT_TEST_DB_NAME / RIVETIT_TEST_DB_USER; the portal seed wipes safely on an install that already holds demo data; tests/reporting_views.php sets a UTC company first and can load time zone tables into a private throwaway MariaDB without Docker; tests/a11y_new_pages.js is a repeatable accessibility probe; tests/browser/lib (the CDP driver and harness the browser suite needs) is tracked again. Status of every top-level test is in docs/TEST_STATUS.md.

Notes

  • New tests: tests/i29_leftovers.php, tests/browser/i29_leftovers_seed.php, tests/browser/i29_leftovers_smoke.mjs. Findings status tables are final in docs/user-guide/tools/app-findings.md and docs/FINDINGS-STATUS.md; decisions 13 and 14 in docs/FINDINGS-DECISIONS.md supersede 11 and 12.
  • Database: 2.6.232 (hr_workflow_requests, settings.config_portal_hr_requests) and 2.6.233 (settings.config_lifecycle_okta_*). Everything new is off by default.

RivetIT 26.10.82

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 04 Nov 00:36
  • Every-page UI pass. Fixes and one user-facing improvement per area: collapsible Ticket Views rail, "Their other tickets" on the ticket page, similar-ticket hints in New Ticket, hidden-tab validation that opens the offending tab (about 95 dialogs), Health column on Departments and expiry chips on domains/certificates/software, project health chips, quote status pipeline, answer-first headlines on 12 reports, a device-status band on the asset page, training overdue banner and compliance matrix, admin jump bars on long settings pages (one shared look), grouped Ticket settings, status badges for SSO/mail/identity, retry-all on the job queue, and a 24-hour health banner on webhook deliveries.
  • Command palette. Ctrl/Cmd+K jumps to any page or record (RivetCore rc.58).
  • Portal. "How can we help?" box suggests knowledge-base articles and catalog requests before a ticket is raised; clearer no-access banner, ticket-detail summary, status tabs; tables stack as cards on phones.
  • Fixes. Table badges and buttons no longer break mid-word, mailbox and credentials tables fit at 1366 wide, readable amber text, org chart Location column, panel_deploy 500 without a department.
  • Requires RivetCore 1.0.0-rc.58 (CSS/JS only; no migration).

RivetIT 26.10.81

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 03 Nov 02:53

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, includ...
Read more

RivetIT 26.10.80

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 01 Nov 06:53
  • Administration > Update: the check for generated vendor/composer files that differ from the repository is now a Note, not a warning (those files are regenerated by composer install). The RMM data store tile shows the short PostgreSQL version; the full version string is on hover.

  • Project tasks, phase 1: priority, description, labels, colour, and a task detail pop-up (database 2.6.207). Every project task can now carry a priority (none, low, medium, high, urgent), a description, labels (global ones, or ones that belong to one project) and a card colour. The Kanban card shows the priority as a coloured left edge plus a badge with its name (never colour alone), the labels as chips, an icon when there is a description, an Overdue due date, a progress bar and the assignee, and is more compact so more cards fit on a phone. The board has a Sort (manual order or priority) and filters by priority, label and assignee; these only change what you see, never the saved order. Click a card title or the expand icon for the task detail pop-up with every field editable; New Task and Edit Task have the new fields too, and the project's task list shows the priority marker and label chips.

  • Task actions: Delete (asks first; needs the same Service Desk level as before, removes the task's labels links), Duplicate (copies fields and labels, not completion) and Move to another project are in the detail pop-up, and a small per-card menu (Edit, Create ticket, Mark complete, Duplicate, Delete). The old Delete link in the task list now also applies the client-access check to project-only tasks (it only checked ticket tasks before).

  • Kanban drag fix. The hamburger drag handle (which overlapped the ticket and edit icons on phones) is gone. Grab a card anywhere to drag it: with a mouse it drags at once; on a touch screen press and hold for about a quarter of a second, then drag, so a quick swipe still scrolls the board. Moving cards between lanes and the saved order work exactly as before.

  • API: GET/POST /tasks, GET/PATCH/PUT/DELETE /tasks/{id} (new; scopes api:tasks:read / write / delete, role level 1 / 2 / 3, department scope), and priority, priority_name, description, color, labels on every task (including in GET /projects/{id}). Existing fields and clients are unchanged. See docs/API.md and api/v1/openapi.yaml.
    Deploy notes: take a database dump first, then Update Database (Administration > Update, or php scripts/update_cli.php --update_db). One additive, idempotent step (2.6.206 -> 2.6.207): tasks.task_priority (default 0), tasks.task_description, tasks.task_color, and the new task_labels / task_label_links tables. Nothing is back-filled. New code on a database that has not been updated yet keeps working (the new fields simply do not show).

  • Project tasks, phase 2: checklists, subtasks and comments (database 2.6.208). The task pop-up has a Checklist (add, tick, edit, delete, move up / down; the card shows 3/5), Subtasks (add, tick to complete, make a regular task again; the card shows 2/3; a subtask is a full task in the same project, one level deep, and shows in its parent's pop-up rather than as a card of its own) and Comments (add, edit your own, delete your own; administrators can delete any; shows author and time; the card shows a count). These save as you click, without leaving the pop-up. Deleting a task deletes its checklist and comments but never its subtasks: they stay in the project as ordinary tasks. Duplicate copies the checklist (unticked) and the subtasks. Moving a parent moves its subtasks; a subtask cannot be moved on its own.

  • Project tasks, phase 3: several assignees, files, reminders, repeating tasks (database 2.6.209). Several people can be on a task (the "Assigned To" person stays the primary, so older screens and apps keep working; the card shows avatars and the assignee filter matches anyone on the task; existing assignees are carried over). Files can be attached in the pop-up (scripts, web pages and installers are refused; downloads need the same department access as the task and are always sent as a download). A task can have a reminder (a date and time, or relative to the due date); the cron job (cron/task_reminders.php, run by the main cron) sends an in-app / push notification to everyone on the task once (administrators when nobody is assigned; no email). A task can repeat every N days / weeks / months / years: completing it (drag to Done, Mark complete, the pop-up, the API) creates the next occurrence once, with the due and start dates moved on (a task finished late gets a due date of today or later, month ends are clamped, not skipped), checklist unticked, same people, labels and reminder offset; comments and files are not copied.

  • API: every task gains parent_id, assignees, checklist, subtasks, comment_count, attachment_count, reminder_at, reminder_sent_at, repeat; parent_id, assignee_ids, reminder_at, repeat are writable; new sub-resources /tasks/{id}/checklist, /subtasks, /comments, /attachments. Existing fields and clients are unchanged. See docs/API.md and api/v1/openapi.yaml.
    Deploy notes (phases 2 and 3): take a database dump first, then Update Database. Two additive, idempotent steps: 2.6.208 (tasks.task_parent_id, task_checklist_items, task_comments) and 2.6.209 (tasks.task_reminder_at / task_reminder_sent_at / task_repeat_interval / task_repeat_unit / task_repeat_spawned_at, task_assignees with a one-time back-fill from tasks.task_assigned_to, task_attachments). Attachments are stored in uploads/task_attachments/ (created on first upload; the web server user must be able to write to uploads/; this folder is under /uploads/, so keep the nginx rule that stops scripts running there). New code on a database that has not been updated yet keeps working (the new panels and fields simply do not show).

  • RivetCore parity pass (Core 1.0.0-rc.55; database 2.6.210). Everything RivetCore's edition prompts ask for that RivetIT did not have yet. Nothing is switched on by this change.

    • Compliance frameworks (RivetCore #92 phase 4). New page Administration > Compliance framework: select a built-in or custom framework, copy one, edit it (every save is a new version, a stale edit is refused, restore any older version), archive, delete (only a never-selected one), export and import (JSON, 64 KiB, hostile files change nothing), and record a restore test. Once a framework is selected its requirements (backup age, off-site copy, encryption, restore-test age, retention minimums, log presets) are checked on the Compliance status page and recorded in snapshots, its retention minimums are refused below in the RMM settings and raised in the audit-trail cleanup, and every change is audited. With no framework selected nothing differs from before.
    • Backup facts. Each backup run now records which stores it really contained, whether it was encrypted and how long its writer keeps sets (backup_runs.run_stores, run_encrypted, run_retention_days; filled by the in-app backup and by deploy/backup.sh). The compliance checks judge those facts and the backup file's header, not configuration. The in-app backup now includes the RMM PostgreSQL store (rmm-postgres.dump, through RivetCore's BackupHook, password through a 0600 PGPASSFILE only) when that store is in use; a dump that is expected and fails fails the whole run (no zip is written, the run is recorded as failed).
    • Reporting / Power BI (RivetCore #91 phase 4). New page Administration > Reporting / Power BI and RivetIT's own views rpt_clients, rpt_sites, rpt_assets, rpt_tickets, rpt_alert_tickets, rpt_sla (allow-listed columns, no free text, client_id on every row, frozen by a fixture). Create, rotate and drop a dedicated read-only database account (MariaDB/MySQL, and a PostgreSQL role when the RMM store is PostgreSQL) with a generated password shown once and an administrator login that is used once and never kept; test the connection as that account; copy Power Query for this install; computed warnings. Timestamps in the RivetIT views are converted to UTC from the company time zone by zone name (daylight saving time proven on MariaDB 10.11); on a server without time zone tables the views are created unconverted and the page says so.
    • Security baseline. docs/security/EDITION_BASELINE.json states honestly, per RivetCore control, what RivetIT enforces (3 enforced, 15 partial, 2 gap), checked by scripts/edition-baseline-check.php (new CI job security baseline). New Security and trust page, public at /trust.php and an administrator copy with per-control detail; it uses only RivetCore's approved wording and a test fails the build if it ever says "SOC 2 compliant" and the like. The staff password minimum can no longer be set or stored below RivetCore's floor of 12.
    • RMM. An asset that moves department (asset edit, inline edit) now takes its RMM device with it through DeviceService::transfer(): jobs, open alerts and the stored log/change history follow, and a PostgreSQL store that is down repeats the history move later. The device-type rule of EndpointAssets::createForDevice now applies RivetCore's pre-rc.29 OS rule when a caller sends no type (the Core conformance kit pins it).
    • Tests. Three stale conformance tests repaired (API keys became integration clients, https-only webhooks, the asset types RivetIT really has); new tests for backup facts (Core kit plus the edition rules), the in-app PostgreSQL backup, frameworks, reporting views/page/PostgreSQL role, the trust page and the baseline check.
      Deploy notes: take a database dump first, then run the database update (Administration > Update, or `php scripts/updat...
Read more

RivetIT 26.10.49 - RivetCore 1.0.0-rc.19 (first Windows run: eight defects fixed)

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 14 Oct 22:37

Deploy notes: back up the database, pull this tag, composer install --no-dev (RivetCore 1.0.0-rc.19). No database change (DB stays 2.6.172; rc.19 has no Core migration) and no cron change. After the update: publish the agent 0.7.1 from the Agent page and rebuild the MSI template with it, then install the starter pack's update (pack 1.0.1) from the Starter pack page.

  • Alerting tab: thresholds for policy checks. The threshold endpoints (GET/PUT endpoint_devices/{id}/checks/{key}/thresholds) answered 404 for every check a policy delivers (the whole starter pack), so the asset page Alerting tab showed no editor for them and an override could not be saved. Core now also looks in the device's effective policy; the editor renders and an override saves for a policy-defined check.
  • Starter pack 1.0.1. battery-report, defender-status, defender-update-signatures and disk-health print unknown / n/a / a note instead of Windows sentinel values (71582788 minutes, 65535 days, a bare /).
  • Agent 0.7.1 (Windows), found by running the agent on a real Windows 11 machine: a junction inside an allowed file-transfer folder could reach files outside it (fixed; update agents 0.6.0 and older if file transfer is on, it is off by default); scripts that call ping, whoami, w32tm and similar failed or reported success with empty sections (the job environment lacked PATHEXT, COMPUTERNAME, ComSpec); PowerShell error output arrived as #< CLIXML XML; proc_kill reported success before the process ended; service checks failed with "Access is denied" on Dnscache and mpssvc; the av check now accepts a third-party antivirus Windows Security Center lists as on. Full evidence: RivetCore docs/rmm/WINDOWS_VERIFICATION.md.
  • Tests: tests/rmm_ui_p23_c_alerting.php (a policy with a thresholds check assigned to a device through the real handler: the thresholds API answers, the Alerting tab renders the editor, an override saves, shows and clears; a check no list or policy defines, and a device the policy does not reach, are still refused). The test fails on rc.18 and passes on rc.19.

RivetIT 26.10.48: the Remote button finds the device (MeshCentral node ids)

Choose a tag to compare

@TheTractorHacker TheTractorHacker released this 14 Oct 19:20

[26.10.48] RivetIT — the Remote button finds the device (MeshCentral node ids)

Deploy notes: back up the database, pull this tag, composer install --no-dev (RivetCore 1.0.0-rc.18), then run the database update (Administration > Updates or php scripts/update_cli.php --update_db). DB 2.6.172: Core migration 0027_rmm_mesh_node_ids rewrites the stored MeshCentral node ids to one form (data only, no schema change, idempotent). No cron change.

  • Bug fixed: Remote opened the MeshCentral home page instead of the device. MeshCentral finds a device by its 64-character id (...?viewmode=11&gotonode=<64 characters>), but the agent reports the same 48 bytes as 96 hex characters and the link carried node//<hex>. The link is now <mesh>/?login=<token>&gotonode=<64 characters>&viewmode=11&hide=31; every stored form (hex, 64 characters, node// either) is converted when the link is built, so it works even before the database update.
  • Paste whatever you have. The MeshCentral node field (Remote card, legacy device page) accepts the address bar of the device in MeshCentral, node//..., the 64 characters after gotonode=, or 96 hex characters, and shows node// plus 64 characters. Help text: "In MeshCentral open the device and copy the address bar, or paste the node id."
  • Same node, one mapping. An agent that reports the node in hex and a hand-typed 64-character id are the same node: conflict detection compares them as such.
  • Not verified on a live MeshCentral with this exact link; the shape is the one MeshCentral shows in its own address bar. See RivetCore's docs/rmm/REMOTE_AND_LOGS.md.
  • Tests: tests/rmm_ui_p68_remote.php (the launch URL carries the 64-character form for a device whose stored id was hex, on every view; a pasted address is saved canonical), tests/rmm_ui.php (field help), tests/endpoint_agent_migration.php (DB 2.6.172 step), tests/browser/rmm_rc17_remote_smoke.mjs extended.