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.
august 3rd
adoption
| Undo now restores canvas edges Deleting a relationship edge on the migration canvas and then undoing that action now correctly restores the edge, instead of leaving it removed. | |
| Provisioning forms updated with new contact fields Default forms created during tenant provisioning now include the new Phones, Addresses, and Emails fields. |
automation
| Tags for automations Users can now add and remove tags on automations, making them easier to organize and find. | |
| New generic HTTP actions — PUT, PATCH, DELETE Three new generic REST API actions have been added to the automation builder, alongside the existing GET/POST actions, expanding what automations can do against external systems. | |
| Send Email action can pull from a template Users can select an email template — with project or lead information merged in — and use it directly in the Send Email automation action. | |
| Natural-language CRON Expression Builder for time-based Starting Rules When creating a time-based starting rule, users can set up a CRON schedule using natural language. (Note: this same item was already published in the Week 31 - 2026 release notes; it's listed again in this week's source page, so flagging in case it's an unintended repeat.) |
communications
| Per-channel contact preferences for Email, Fax, and SMS Sending a communication now uses the specific phone number or email address a contact has designated for that channel, instead of a single "primary" value for everything. The contact-level fax number field has also been replaced by a dedicated fax preference. | |
| SMS consent (opt-in / opt-out) SMS can now only be sent to contacts with active consent. Consent is tracked as Unknown (no record — the default for existing/imported contacts), Pending (awaiting double opt-in confirmation), Opt-in (active, SMS allowed), or Opt-out (revoked, SMS blocked). | |
| Add a new contact inline Users can create a new contact directly from the "To" field when sending an email, fax, or SMS — and create new attendees or locations directly from the Calendar. | |
| Context is preserved when emailing from a Microsoft account When an email is sent from a Microsoft account with a project or lead selected, that context is now kept instead of being overridden by association rules. | |
| Fax details UI improvements General usability improvements to how fax details are displayed. | |
| SMS project-assignment icon always visible The icon used to assign a project or lead to a message is now always visible, making it easier to spot SMS messages that still need to be assigned. |
core
| Programmatic webhook subscription management Partners can now create, list, update, and delete webhook subscriptions programmatically via API (through a new Svix proxy), removing the need to manage them manually through the UI. All endpoints are authenticated and documented. | |
| Permissions tab for Integration Users Admins can now view the permissions assigned to an Integration User directly from its detail page, using the same permissions view already available for regular users. | |
| Contact data now reflects the canonical communications model Contact tables and the user email endpoint now read phone, email, and address data from the updated canonical data structure, ensuring information continues to display and resolve correctly following the communications data migration. | |
| Merge Contacts field names back in sync Fixed a bug where field names shown on the Merge Contacts screen were out of sync with the backend, causing inconsistencies during a merge. |
customization
| Lookup Fields Administrators can add a new field type to any form that pulls a value from a related record in context — controlling where the value comes from, whether it's visible, its label, and how it drives the form's conditional logic, all without code. Users working on a record can then see that related-record value directly inside the form without switching screens. | |
| Key system field for merge fields Every record now gets an automatically assigned, system-generated Key (UUID) at creation, which administrators can reference in merge field expressions to build consistent, unique, auto-generated names — including using short segments of the key as memorable identifiers. | |
| Communication-specific field types via selector Phone, email, and address fields now support communication-specific types (e.g. Primary, Fax, Texting) through selector-based configuration, without needing new field types. | |
| Responsive card layout Cards in views now adapt automatically to available width, showing two or three per row instead of always one, so users see more information without any extra configuration. | |
| Schema conflict feedback in the object builder Conflicts such as duplicated field labels are now surfaced directly on the affected fields, on the tabs containing them, and on the save button, instead of silently blocking the save. | |
| Document relationship fields open the right screen Clicking a document referenced in a relationship field inside a form now opens the document's metadata drawer (with a dedicated icon to open the full single view in a new tab), instead of incorrectly opening the Document Custom Fields form. | |
| Project Groups configurable by project type Project Groups can now be enabled per project type in Control Center, with propagation rules centralized at the object level instead of being configured inconsistently per group. | |
| Disable submit on fully read-only forms Forms where every field is read-only now automatically disable the submit button, instead of leaving it active with nothing to submit. | |
| Leaving a Project Group no longer requires a manual refresh Old group data is now cleared automatically when a user leaves a project group. | |
| Warning when a primary project isn't selected Project Groups now show a warning if a primary project hasn't been designated. |
explore
| Report results now show field labels instead of API field names Report results previously displayed raw API field names, making them hard to interpret for users unfamiliar with internal naming conventions. Reports now show the user-friendly field label instead. | |
| Hierarchical field selection for report filters Instead of searching across every field on every related object at once, users can now drill into a specific related object first and then browse or search only within its fields — much easier to navigate as data models grow. | |
| Date-part filtering in Advanced Search & Reports Date fields can now be filtered by an individual component of the date (e.g. month, regardless of year) — useful for recurring scenarios like birthdays, anniversaries, or renewal months — while existing relative-date filtering (Created At, Updated At) is preserved. | |
| Quick Searchable configuration is now respected Disabling a field's "Quick Searchable" option now actually removes it from Quick Search, instead of leaving it searchable. | |
| Unsupported field types can no longer be marked Quick Searchable Field types that don't provide meaningful search value (e.g. booleans) can no longer be configured as Quick Searchable, reducing irrelevant results and configuration errors. | |
| Internal system objects hidden from Search & Reporting Object selectors in Explore and Reporting no longer expose internal system collections, so users only see business-relevant objects. | |
| Save an execution as a report from the visualizer Users can revisit, tweak, and re-run executions created from unsaved reports directly from the execution visualizer, then convert a refined iteration into a saved report once it's right — without needing to save multiple temporary versions along the way. |
finance
| Delete draft invoices Finance users can delete a draft invoice before it's finalized; its line items automatically return to the uninvoiced list for future invoicing. Every deletion is auto-numbered, logged in the activity history, and preserved read-only in a dedicated Deleted Drafts tab for a complete audit trail. | |
| Void sent invoices Users can void a sent invoice that needs to be invalidated (e.g. due to an error or billing change). Voiding is permanent and requires a reason; line items are released back to the uninvoiced pool, the original invoice is preserved read-only with its invoice number retained, and the action is logged to the invoice's activity history. | |
| Fixed charges on projects Case workers can add fixed charges to a project (e.g. filing fees, document requests) pulled from the product catalog with rates pre-filled; saved charges appear as Unbilled and ready for the accounting team to invoice. | |
| Download and send invoices as PDF Invoices can now be generated and downloaded as a finalized, non-editable PDF, with a preview step before download. Once downloaded, the invoice status automatically updates to "Sent" and locks from further editing to keep the shared PDF consistent with the recorded invoice. |