Release Date: 2026-04-01
Release Channel: Current
Version: 26.03.1.0.12
Trinity Asset Version: 1.0.12
Support Requests Resolved
Support Requests Resolved-
NPFRBT-1254: Studio was extremely slow for projects with large configurations (3,000+ custom codes). Custom code loading could exceed 5 minutes. Resolved by optimizing the database query used to load branch configurations.
-
NPFRBT-1174: Switching branches in Development did not bring up the cases and tasks already assigned to the user. Resolved by adding a fallback to the main branch case definition when a branch-specific definition is not found. This is now enabled by default via the
FALLBACK_TO_MAIN_CASEDEFfeature flag. -
NPFRBT-1173: Database SSL certificate content (
DB_SSL_CERT_CONTENT) was not propagated to config-service, case-service, and gts, causing connection failures for deployments using SSL certificates for database access. -
NPFRBT-1161: Change tracking diff was slow on PRs and commits. Diffs now load significantly faster, especially for projects with large configurations.
-
NPFRBT-1162: Change tracking diff loader was stuck and not loading when opening a PR or commit.
-
NPFRBT-1158: Sync Case Delegate Time migration for existing tasks failed after 1.0.7 migration with an internal server error.
-
NPFRBT-1157: Inbox column added via Global Custom Code (Inbox Projection) disappeared after refreshing the browser. The mapping now persists correctly across page reloads.
-
NPFRBT-1142: Case count mismatch after reassignment. Inbox parameter initialization was not awaited, causing the count and filter state to go out of sync.
-
NPFRBT-1210: Case status filter in Case Manager was not applied correctly. The filter change handler has been fixed to await initialization before applying filter values.
-
NPFRBT-1258: Fixed inability to rearrange page order in a process. Pages can now be reordered as expected.
New Features
New FeaturesBranch-Aware Case Definition Fallback
When working on a branch with change tracking enabled, cases and tasks that don’t have a branch-specific case definition now fall back to the main branch definition instead of showing an error. This means switching branches no longer causes assigned cases and tasks to disappear.
- Enabled by default via the
FALLBACK_TO_MAIN_CASEDEFfeature flag
Case Comments Edit and Delete
Case comments in Case Manager now support editing and deleting. Deleted comments use soft delete and are no longer visible to users but are retained in the database.
Copy CSS Selector
The page editor in Studio no longer auto-generates CSS rules when components are placed via drag-and-drop or copy-paste. Instead, a new Copy CSS Selector button (curly braces icon) is available in the attribute panel’s ID section, allowing you to copy the component’s CSS selector for manual styling.
Enhancements
Enhancements-
Table Config Data Source Mapping: Table configuration now supports additional schema types — data source mapping displays a dropdown with autocomplete for known types and a free-text input for others.
-
Dropdown Editability: Dropdown components in mapping type configuration are now editable.
-
Custom Code Usage Tracking: Custom code usage is now correctly reflected in the main branch after merging from a feature branch. The Usage link also now works correctly when Studio is deployed on a non-default base path.
-
Saving Multiple Custom Codes: Saving multiple custom codes at once is now faster (batched into a single operation instead of saving one at a time).
Bug Fixes
Bug FixesStudio
- Fixed false “Custom code is empty” validation errors appearing in the page editor when custom codes were valid but still loading.
- Fixed editable dropdown typed text not being visible when the dropdown is inside a float label.
Case Management
- Fixed task deallocation failing when the process instance was not yet available.
- Fixed task re-attempt failing with a 500 error despite tasks being properly configured. The case instance request was missing required query parameters.
Inbox & Filters
- Fixed date format configured in Studio for Group Tasks not being applied in Case Manager.
- Fixed inbox column format control not being applied when a column format was specified in the configuration.
Admin
- Fixed duplicate users appearing in the bulk assignment popup when users belonged to multiple groups.
- Fixed set-reportees API returning an empty reportees array on the manager object despite successful assignment (circular JSON reference).
- Fixed remove-manager API returning the username instead of an appropriate response when the user had no manager assigned.
- Fixed duplicate error toast messages appearing on the Enquiry page when no filter values were applied.
Configuration
Configurationmarketplace-headless Template Integration
marketplace-headless environment variables have been moved from service-level envs: blocks into the deployment template. This reduces duplication and ensures consistency across environments.
Template-derived env vars:
| Variable | Source |
|---|---|
CLIENT_ID |
features.ids.clientId |
CLIENT_SECRET |
features.ids.clientSecret |
OIDC_ISSUER |
features.ids.url |
DB_PORT |
features.database.port (default: 5432) |
APP_NAME |
Hardcoded: marketplace-headless |
DEPLOYED_ON_PREM |
Hardcoded: true |
DISABLE_S3 |
Hardcoded: true |
NODE_ENV |
Hardcoded: production |
ON_PREM_ENV |
Derived from features.devMode |
New optional features.marketPlace override keys (not in default-values.yaml — set only if you need to override):
| Key | Default |
|---|---|
centralMarketPlaceUrl |
https://marketplace.neutrinos-apps.com/marketplace-headless |
cmClientId |
FYqh5ZhdbIp2SrQPGZYMe |
cmClientSecret |
(empty) |
cmIdsIssuerUrl |
https://marketplace.neutrinos-apps.com |
configFileSizeLimit |
2 |
MARKETPLACE_URL (for alpha-module-service and alpha-config-service) now uses cluster DNS: http://marketplace-headless.{namespace}.svc.cluster.local:8080/marketplace-onprem/api
Credential deduplication: features.marketPlace.clientId, clientSecret, ids, and url have been removed. MARKETPLACE_CLIENT_ID, MARKETPLACE_CLIENT_SECRET, and MARKETPLACE_IDS_URL now use features.ids.clientId, features.ids.clientSecret, and features.ids.url respectively. MARKETPLACE_URL is now constructed as a cluster DNS URL (see above).
NODE_TLS_REJECT_UNAUTHORIZED Global Toggle
New features.nodeTlsRejectUnauthorized toggle sets the NODE_TLS_REJECT_UNAUTHORIZED env var globally for all backends and adapters. Only emitted when the value is explicitly set (non-empty). Use "0" to disable TLS certificate verification. Per-service override via envs.NODE_TLS_REJECT_UNAUTHORIZED takes precedence.
features:
nodeTlsRejectUnauthorized: "0" # Disable TLS verification
Breaking Changes
Breaking ChangesRemoved features.marketPlace keys
The following keys have been removed from features.marketPlace. If your values file sets any of these, remove them:
| Removed Key | Replacement |
|---|---|
clientId |
Use features.ids.clientId (now shared) |
clientSecret |
Use features.ids.clientSecret (now shared) |
ids |
Use features.ids.url (now shared) |
url |
Removed — MARKETPLACE_URL is now auto-constructed as cluster DNS |
marketplace-headless envs removed from template defaults
The following env vars are no longer expected in services.backends.marketplace-headless.envs — they are now template-generated. Remove them from your values files to avoid duplication:
APP_NAME, CLIENT_ID, CLIENT_SECRET, OIDC_ISSUER, DB_PORT, DEPLOYED_ON_PREM, DISABLE_S3, NODE_ENV, ON_PREM_ENV, NODE_TLS_REJECT_UNAUTHORIZED, CENTRAL_MARKET_PLACE_URL, CM_CLIENT_ID, CM_CLIENT_SECRET, CM_IDS_ISSUER_URL, CONFIG_FILE_SIZE_LIMIT
Service-level envs overrides still work if explicitly needed.
Feature Flags
Feature Flags| Feature Flag | Description | Default |
|---|---|---|
FALLBACK_TO_MAIN_CASEDEF |
Enables fallback to main branch case definitions when branch-specific definition is not found | true |
Migrations
MigrationsDatabase Migrations
DB Schema migrations are automated for all trinity asset releases.
Docker Images
Docker Images| Category | Service Name | Image Repository | Image Version |
|---|---|---|---|
| backends | neutrinos-cm-bpm | neutrinos.azurecr.io/alpha/neutrinos-cm-bpm |
1.0.0 |
| backends | alpha-case-service | neutrinos.azurecr.io/alpha/alpha-case-service |
26.03.1.0.12-0e1704de0b09 |
| backends | alpha-request-service | neutrinos.azurecr.io/alpha/alpha-request-service |
26.03.1.0.12-0e1704de0b09 |
| backends | alpha-delta-service | neutrinos.azurecr.io/alpha/alpha-delta-service |
26.03.1.0.12-0e1704de0b09 |
| backends | admin | neutrinos.azurecr.io/alpha/admin |
26.03.1.0.12-0e1704de0b09 |
| backends | alpha-auth-service | neutrinos.azurecr.io/alpha/alpha-auth-service |
26.03.1.0.12-0e1704de0b09 |
| backends | alpha-config-service | neutrinos.azurecr.io/alpha/alpha-config-service |
26.03.1.0.12-0e1704de0b09 |
| backends | alpha-module-service | neutrinos.azurecr.io/alpha/alpha-module-service |
26.03.1.0.12-0e1704de0b09 |
| backends | alpha-dashboard-service | neutrinos.azurecr.io/alpha/alpha-dashboard-service |
26.03.1.0.12-0e1704de0b09 |
| backends | marketplace-headless | neutrinos.azurecr.io/alpha/marketplace-headless |
25.11.0.0.0-49d5909-current |
| backends | alpha-archival | neutrinos.azurecr.io/alpha/alpha-archival |
26.03.1.0.12-0e1704de0b09 |
| frontends | alpha-admin-ui | neutrinos.azurecr.io/alpha/alpha-admin-ui |
26.03.1.0.12-0e1704de0b09 |
| frontends | alpha-case-manager-ui | neutrinos.azurecr.io/alpha/alpha-case-manager-ui |
26.03.1.0.12-0e1704de0b09 |
| frontends | alpha-workflow-studio | neutrinos.azurecr.io/alpha/alpha-workflow-studio |
26.03.1.0.12-0e1704de0b09 |
| frontends | alpha-delta-ui | neutrinos.azurecr.io/alpha/alpha-delta-ui |
26.03.1.0.12-0e1704de0b09 |
| adapters | alpha-jbpm-service | neutrinos.azurecr.io/alpha/alpha-jbpm-service |
26.03.1.0.12-0e1704de0b09 |
| cron | alpha-task-distributor | neutrinos.azurecr.io/alpha/alpha-task-distributor |
26.03.1.0.12-0e1704de0b09 |
| cron | gts | neutrinos.azurecr.io/alpha/gts |
26.03.1.0.12-0e1704de0b09 |
Support & Resources
Support & Resources- Documentation: Alpha Platform Documentation
- Bug Reports: Jira Service Desk
- Community: Neutrinos Community Forum