Onify Hub API 2.51.2
1 day ago by Robert Lundsten
Changelog from version 2.50.1 to 2.51.2
2.51.2
- fix: Reject compromised eMudhra (emSign) certificate chains in outgoing connections, including Git resource synchronisation
- improve: Require Node.js 24.22.1 or later for installations that manage their own Node.js runtime
2.51.1
- fix: Improve reliability when adding or removing user roles during concurrent updates
2.51.0
- fix: Preserve numeric identifiers as text during SSO field mapping to prevent errors when creating or updating users
- fix: Only allow the
valueof system settings to be changed through the API; changes to other fields return HTTP 400. Visibility and role restrictions are managed by system configuration - fix: Record successful internal and SSO logins in the audit log so login statistics have data
- fix: Allow the
citizen_prefix for custom strings as well as custom settings - fix: Correct search results when combining multiple filters with OR in workspaces using
{{term}} - feat: Add a
publicflag to make settings available without authentication throughGET /public/settings. Role-restricted settings require authentication and cannot also be public. The existingpublictag remains supported - fix: Allow bulletins to receive more than 1,000 acknowledgements
- feat: Add cursor pagination to
GET /tools/logs; existing scroll pagination remains the default - feat: Add
GET /admin/audit/aggregatefor unique user counts and daily, weekly or monthly audit activity statistics - feat: Add
GET /admin/items/aggregatefor distinct value counts and daily, weekly or monthly item statistics - feat: Add
GET /admin/processes/aggregatefor average execution time of completed processes - feat: Add the
admin_dashboard_settingssystem setting for configuring dashboard KPIs - improve: Remove legacy API statistics and the
api_statssettings - fix: Update dependencies to address security vulnerabilities
2.50.4
- improve: Support sorting bulletins by start date in ascending or descending order
- fix: Correct error logging and preserve additional log details in
POST /tools/logs
2.50.2
- fix: Handle invalid database provider configuration with a warning and fallback to Elasticsearch
2.50.1
- fix: Preserve workflow schedules and history retention settings when resource files are temporarily inaccessible
- fix: Prevent forced resource synchronisation from unexpectedly clearing workflow schedules when many resources are present

