These release notes summarize the new features, latest updates, and bug fixes from this month in Neostella platform.
For detailed information of product-specific changes, please visit our Help Center articles.
september 1st
adoption
| Standard Mapping date fields now use ISO format The created_at and updated_at fields on customizable objects now return dates in ISO format instead of raw timestamp, keeping date values consistent, readable, and correctly formatted across the platform after migration. | |
| Leads relationship fields and dual context on schema import The schema adapter now correctly creates relationship fields for Leads objects and assigns dual context to Intake objects during schema import. | |
| Switch import source even with inconsistencies Specialists can now switch the import source from the mapping canvas even when inconsistencies exist, with those inconsistencies surfaced directly in the UI for review — removing the previous hard block that prevented any progress. | |
| Same email allowed as owner across multiple tenants The same email address can now be used as the owner in multiple tenants, enabling shared accounts and service users to manage more than one tenant environment without conflicts. | |
| +1 country code prepended to migrated phone numbers Migrated phone numbers in the Contacts entity now include a +1 country code prefix so every number is complete and ready to use after migration. | |
| Load Date and Last Updated Date shown in Import Import and mapping lists now display creation and last-updated dates, are sorted from newest to oldest by default, and include a select-all option within an import. | |
| Inline field search when drawing connection lines Specialists can now search for the target field directly when drawing a connection line from a source field (and vice versa), instead of scrolling through long field lists manually. | |
| Share maps across imports with data contract validation Maps can now be reused and shared across different imports without rebuilding them from scratch, saving time across clients and executions. The system also validates data contract structure consistency before any execution runs, preventing structural mismatches. | |
| Clearer error detail in execution failures When a migration execution fails, users can now see exactly what went wrong at each step — including the object, field, error type, and operator involved — directly in the failure modal, without needing to contact engineering or read raw logs. |
automations
| Partner Apps connectors usable as Automation actions Users can create Connectors to external or internal endpoints through partner apps in the Control Center. These Connectors can now be converted into reusable actions for Automations, allowing users to call configured endpoints without manually entering the URL or credentials each time. |
communications
| Granular admin permissions for the Control Center Admin access can now be controlled with separate permissions for Activity Feed, Provider Set-up, and Templates, instead of a single broad admin permission. |
core
| Standard fields backfilled across all tenants Standard Person, Organization, and User fields are now consistently available across all tenants. Existing tenants missing these fields receive them via a backfill migration, and newly provisioned tenants include the full standard field set by default — no manual intervention required. | |
| "Main Office" flag at the tenant level Tenant administrators can now designate one office as the Main Office from General Settings. This gives the system a single time zone reference used by Automation for task scheduling. Only one Main Office can be active at a time — selecting a new one automatically replaces the previous designation. | |
| User GET endpoints return updated contact data structure The User GET and GET list endpoints now retrieve phone, email, and address data from the updated canonical data structure, ensuring accurate responses following the communications data migration. | |
| Rule Builder condition editor preserves display format The rule condition editor now preserves the user's chosen display format after saving, preventing unexpected syntax changes. Complex or long expressions are also better accommodated through an auto-expanding text box or modal view. | |
| Audit log and event flagging for contact merges Contact merge actions are now recorded in the audit log, showing who performed the merge and which contacts were involved. Merge-triggered events are also flagged with metadata so downstream systems and webhook consumers can identify and handle them appropriately. | |
| Field Tag Builder supports sub-contextual objects The Field Tag Builder now supports sub-objects, allowing users to create tags that reference fields on dependent objects in addition to top-level ones. |
customization
| Object aggregation across project groups ("Receive from Secondary") A new Receive from Secondary attribute lets the primary project in a project group act as an aggregator, displaying its own records alongside shared-object records (e.g. Incident Data) from all secondary projects in one consolidated view. | |
| Relationship fields auto-sync when a new context is added When a new context is added to an object, all relationship fields pointing to that object are now automatically synchronized to include the new context, instead of requiring administrators to update each one manually. | |
| Substring extraction for calculated fields Calculated fields that output text now support FIRST and LAST substring extraction functions, letting administrators pull a specific portion of a string (e.g. the last 4 digits of an SSN) without a manual workaround. | |
| Dedicated Org Name field for Organizations Organizations now have a required Org Name field as the primary identifier, with the merge field updated to use it. Legal Name remains available as an optional secondary field for formal or contractual use. | |
| Edition drawer resolves full record context before rendering The edition drawer now always resolves the full record context — object type, schema, fields, and configurations — before rendering, fixing cases where it displayed incorrectly or incompletely, and improving performance. | |
| Open full contact record from the relationship field drawer A new button at the top of the contact relationship field drawer opens the full contact record in a new browser tab, giving users access to custom objects and full contact information without losing their current project context. | |
| Confirmation before leaving a form with unsaved changes Users who try to navigate away from a form with unsaved changes are now prompted to confirm before leaving, preventing accidental data loss. | |
| Faster, non-blocking schema changes Object creation operations (collection creation, graph updates, index creation) now run asynchronously via a Kafka-based flow instead of synchronously in the request path, avoiding timeouts and slow responses as schemas grow. | |
| Import completion notifications Administrators are now notified as soon as an import completes, both via a floating panel and platform notifications, with a downloadable report detailing anything that was skipped or failed. | |
| Immediate feedback on invalid import files Uploaded import files are now validated immediately, so administrators get clear feedback on structural problems right away instead of waiting for the import to run. | |
| Partial form import when some fields are missing Importing a form into a destination tenant that's missing some referenced fields or components no longer blocks the whole import — the system brings in what it can and clearly reports what was left out. | |
| Import an object with its forms and type assignments Administrators can import an object schema — including its forms and form assignments — into a destination tenant without overwriting existing configuration, whether the object is new or already exists there. | |
| Export an object with its forms Administrators can export one or more object schemas, including all associated forms, as a single JSON file directly from the schema module, for moving validated configuration between environments. |
explore
| Chart configuration separated from the Data Table Chart configuration controls now live in the Data Visualization section, separate from the Data Table, for a clearer distinction between visualization and table functionality. | |
| Hidden fields excluded from Reporting Fields configured with the Hidden limitation are no longer available when building reports. | |
| Hidden fields excluded from Advanced Search Fields configured with the Hidden limitation are no longer available to end users when building Advanced Search queries. |
finance
| Bulk invoice generation across projects Finance users can generate invoices for all pending items across multiple projects at once instead of going project by project. Selected items are automatically grouped by project into one draft invoice per project, with the same fields, behavior, and capabilities as any manually created invoice. |
workflows
| Timers stop automatically on bulk reassignment When users reassign or unassign a group of tasks at once, any running timers on those tasks now stop automatically the moment each change succeeds, keeping recorded time accurate. | |
| Task timers synced with Finance Task timers are now synced with Finance so time tracked on a task is visible to billing and vice versa. Finance becomes the single system of record for timers — tasks remain a place to start and pause a timer, but both surfaces show the same record. | |
| Inherited assignment now traverses intermediate nodes Inherited assignment now correctly resolves an owner even when a delay or automation node sits between a task and its assignment source, instead of leaving the task unassigned and requiring manual intervention. |
bug fixes
| Favorite status no longer stuck loading (Executions) Adding or removing an Execution from Favorites now reflects the updated status immediately, instead of leaving the UI stuck in a loading state until the user navigates away and back. | |
| Favorites actions failing for Reports and Scheduled Reports/Runs Adding or removing a Report from Favorites no longer returns a 500 error, and the same action on a Scheduled Report or Run no longer leaves the page loading indefinitely. | |
| Quick Search now returns exact email matches Searching by a complete email address now correctly surfaces the record with that exact email, instead of returning unrelated partial matches. | |
| Selected columns stay marked as selected Columns already added to a report now remain visually marked as selected when reopening the "+ Columns" panel. | |
| Phones and Addresses fields available again in Explore The Phones and Addresses fields are available again in the field selector for filters and report columns when using Persons as the data source. |