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.
july 6th
adoption
| Reorganized field mappings Multi-object field mappings can now be organized more clearly, reducing confusion when working with large or complex mapping canvases. | |
| Resend welcome email for password reset Supports migrating users ahead of go-live and activating them only when the customer is ready. | |
| Fixed a data conditional import issue affecting Persons and Organizations. |
automations
| Support for attachments in the Send Email automation action Automated emails can now include file attachments. | |
| Generic (REST API) HTTP actions Two new automation actions let users call external GET and POST endpoints directly from a workflow. |
communications
Fax capabilities expanded:
| |
| Notifications panel expand button A new button lets users expand the Notifications panel to view notification details more easily. | |
| Fixed an error that appeared when accessing the calendar view from a lead's context. | |
| Fixed an issue where switching from SMS to fax did not reload the sender's phone number. | |
| Fixed a UI issue where the "from" address dropdown in Quick Add Email overflowed the window when scrolling. | |
| Fixed an issue where calendar events were not visible to all tenant attendees. | |
| Fixed date/time validation so an end date/time can no longer be set earlier than the start; underlying datetime format standardized to ISO. | |
| Fixed an issue where reopening a message thread did not redirect the user to it while staying in the Messages view. |
core
| Contact Merge action Users with merge permissions can now merge duplicate Contact records into a single master record. Conflicting field values are surfaced for manual review — nothing is overwritten automatically — and all sub-objects, relationships, communications, and notes from both contacts carry over to the master. Contacts linked to platform users can't be merged this way, and once confirmed, a merge can't be undone. | |
| SSO auto-provisioning Users logging in for the first time via SSO are now automatically provisioned an account, removing the need for manual pre-registration, and are assigned to a default group with a controlled, limited-access permission baseline. | |
| Tag-based permissions enforced on Contacts and Documents Access to Contacts and Documents is now strictly governed by tag permissions configured by administrators — covering list views, direct API updates/deletes, and object-specific permission scopes (e.g., Own/Related/Any) — so end users only interact with records they're authorized to see or edit. |
customization
System field indicators Fields created by the system are now visually flagged in the object builder, giving administrators immediate clarity on which fields they can safely modify or delete. | |
| Bidirectional relationships Administrators can now configure, create, synchronize, and disable bidirectional relationships between records at the schema level, keeping related records in sync on both sides and improving navigation across connected entities. | |
| Global Objects support type-based forms Administrators can now assign specific forms to each Global Object type so the correct form displays automatically based on the record's type. | |
| Auto-hide fields linked to inactive objects Relationship fields tied to a deactivated object are now automatically hidden, preventing end users from hitting errors or missing data. | |
| Views and Components restricted to active fields Archived or hidden fields can no longer be selected when configuring a view or component, preventing broken or empty columns. | |
| Fixed relationship data not synchronizing correctly when a bidirectional relationship was created on top of an existing relationship. | |
| Fixed an issue that allowed a Global Object record to be modified from any project when it should have been restricted to one record per Global Object. | |
| Fixed an issue preventing a field group from being created after the first transaction. | |
| Fixed a server error when filtering Components by type (Button, Chart, Table, Card) in Schema > Views. | |
| Fixed an issue where deleting one side of a bidirectional-linked field also deleted the entire linked object instead of just the field. | |
| Fixed the Global Item form appearing empty when opened from a relationship field. | |
| Fixed Global Objects not saving their configured display options (card, search, table). | |
| Fixed an error rendering a view after adding a numeric calculation field. | |
| Fixed the ADD_DAYS calculation function not working correctly. | |
| Fixed calculated field conditions not triggering the correct output for text fields. | |
| Fixed conditional expressions in calculated fields not evaluating decimal values correctly. | |
| Fixed Global Object deletion not working properly. | |
| Fixed required fields missing from the form's conditional logic builder. | |
| Fixed the Name row not respecting its configured position in table components. | |
| Fixed the percentage field type displaying incorrect values in Projects merge fields and object grids. | |
| Fixed a List field only displaying the first saved instance in the grid. |
documents
| Tag and document type assignment on upload: A new modal in the document upload flow lets users assign tags and a document type at the time of upload, reducing post-upload classification work. | |
| PDF Forms now generate an envelope: Generating a document from a PDF Template now creates an envelope (instead of a standalone signing session), defining signers on that envelope and sending Signature Request emails through the same consistent workflow used elsewhere. | |
| Faster fact editing: Clicking directly on a Fact's text now jumps straight into the editable field, removing the extra step of navigating to the Edit tab. | |
| Templates can be opened in SharePoint: Templates now support the same SharePoint editing experience already available for Documents. | |
| Click-through from Facts to source documents: Clicking a Fact in the grid now redirects users to its associated document. | |
| Removed the Signature tabs from Docs grids and detail panels. | |
| Fixed envelope content progress resetting when switching between documents in a signing session. | |
| Fixed signer form labels rendering incorrectly after a registered contact was deleted. | |
| Fixed the Submit button remaining enabled after removing a required signature or initials field during signing. |
workflows
| Fixed get_next_available_task_for_user so it now respects the requesting user's assignee scope and returns tasks in the correct (highest-priority-first) order, instead of ignoring scope and reversing priority. |
july 2nd and 3rd
ai
| AI Search Bracket Notation and Operator Support AI search now supports bracket notation and all operators when searching for persons and organizations. |
core
| Apply permissions on Non-Contextual Documents Admins can now control access to non-contextual Documents (documents not linked to any project or lead) through the standard permission set. View, Create, Edit, Delete, and Share permissions each independently govern what users can see and do within the Documents section of the Cases workspace — including visibility of the menu itself, available actions, and editable fields. | |
| Tag-based permissions not enforced for Edit/Delete: Fixed an issue where users could still edit or delete documents with a tag-based permission explicitly set to deny Edit/Delete access. | |
| Documents permissions wrapper fails (View/Create/Edit): Fixed a conflict where enabling full Document permissions at the Project level would override more restrictive Control Center permission settings, incorrectly allowing users to View, Create, and Edit documents they shouldn't have access to. |
customization
| Unable to load view error on custom object in organization: Fixed an error that prevented users from opening custom objects (e.g., the Engagements object) from an Organization record, which occurred even when using a newly created form. |