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 30th to october 6th
adoption
| Ignore Conflicts on Existing Base Object Fields During Schema Import: This update includes internal improvements that do not impact the user experience. | |
| Create Internal Schema Import Endpoint: This update includes internal improvements that do not impact the user experience. | |
| Integrate Lambdas inside the Provisioning Step Function: This update includes internal improvements that do not impact the user experience. | |
| Clean up leads with non-Lead type records: Minor bug fixes and internal improvements. | |
| DNS records are not being created correctly in tenant provisioning: Minor bug fixes and internal improvements. | |
| Strip Document ID from title and move to custom metadata field: This is the resolution for the client support. | |
| Organization names with slashes incorrectly doubled as backslash-slash: This is the resolution for the client support. | |
| User Creation Step Function Broken Due to Permission: Minor bug fixes and internal improvements. |
communications
| BREAKING CHANGE Create Activity Feed events based on configured rules: Admins can now configure rules that control which object events show up in the Activity Feed, rather than surfacing every event by default. This keeps the feed focused on what actually matters for a case or project, cutting down on noise for users reviewing activity. | |
| Filter the interaction list: Narrow the list to what needs attention, such as unknown callers, interactions without a project or lead, or a specific project or lead. | |
| Assign an interaction to the right context: Place any interaction on the right project or lead, or move it later, so it shows up for everyone working that matter. | |
| Open an interaction to see the full story: Open any interaction to see the whole conversation in one place, with every call, message, email, and chat in order, most recent first. | |
| See interactions in the Contact Center tab (Workspace and Project | Lead): A new Contact Center tab in Communications lists your interactions, both across your workspace and on each project or lead. |
core
| Persist Outcome Code and reason on Lead stage change: When a Lead changes stage or is converted and the stage requires a reason, the Outcome Code and optional comment users enter are now saved with the stage change, and the Outcome Code keeps the name it had at that moment even if it is renamed later. | |
| Click on Stage's label on headers: Users can click directly on the current stage label in the header of a project or lead to open the list of stages and change the stage, instead of only using the small icon next to the label. | |
| Enable DeletedBy details in recycle Bin: The Recycle Bin now shows who deleted each item, making it easier to follow up on deletions and restore items with more confidence. | |
| View, access, and permission-gate Conflict Checks across the platform: Staff get one place to see every Conflict Check across the firm, split into Active and Completed, so they can find their work without digging through individual records. Access is controlled by a single permission. | |
| Generate and attach the Conflict Check PDF report: Firms can generate a PDF report of a Conflict Check and have it saved automatically to the related record's Documents, giving them a permanent, shareable proof that the check was performed for audits. | |
| Run a Conflict Check end-to-end — search, evaluate parties, and complete: Case Intake Specialists can run a Conflict Check from start to finish inside the platform, with the outcome calculated automatically and the record permanently locked on completion. | |
| Customize Header – Support composed fields: Customize Header now supports composed fields, meaning fields that are built from several other fields, such as an Address made up of street, city and other parts. |
customization
| BREAKING CHANGE Contact Field Validation — Warn Instead of Block: Invalid phone numbers and email addresses no longer block lead and contact creation entirely; the record can be saved regardless of validity, with a clear warning so users can identify and correct the issue. | |
| Hover on relationship fields displayed on grids: Adds a hover preview that displays the configured display card for the linked record, giving users immediate context without leaving the grid. | |
| Deprecated Field: Allows system admins to mark a field as deprecated so it is hidden on records with no data and shown as read only on records where it already has a value. | |
| Lead deletion and restoration within Lead Groups: When a secondary lead is deleted, its relationship to the Lead Group and shared records is handled cleanly; on restore, the lead rejoins the group with its original relationships intact. | |
| Convert a Lead Group to a Project Group: Introduces a conversion modal triggered by a stage change, with three conversion options determining whether a Project Group is created and which leads are included. | |
| Governance: permissions and post-conversion restrictions: Ensures access control is applied consistently and that converted Lead Groups cannot be modified in ways that would break data integrity. | |
| Lead Group List View: Introduces a dedicated Lead Group Management screen where users can browse, filter, and access all Lead Groups from a single place. | |
| Create and manage a Lead Group: Lets intake specialists create a Lead Group, designate a primary lead, configure shared objects, and manage the group throughout intake. | |
| Configure Lead Group availability by lead type: Allows administrators to control which lead types can participate in Lead Groups. | |
| Share, propagate, and manage shared records between leads in a group: Defines how shared object records flow between leads in a group, covering all propagation scenarios and the Receive from Secondary behavior. |
documents
| BREAKING CHANGE Add "Export Package" button: Users can trigger a Fact Export for an entire package directly from the UI, covering all facts across every document in the package. | |
| BREAKING CHANGE Add "Create Document Record" Toggle on Fact Export: Users can choose whether Fact Export creates a record document: a single record PDF when enabled, or a ZIP with a separate facts PDF and Table of Contents when disabled. | |
| BREAKING CHANGE Allow users to upload a document directly from a Fact Packet: Users can now upload a document directly from a Fact Packet through an Upload Document option, instead of having to bring documents in another way. | |
| BREAKING CHANGE Generate two documents when exporting Facts: Adds a standalone Table of Contents PDF and packages the export as a ZIP containing both the merged PDF and the Table of Contents. | |
| Redirect user to the Fact Packet after successful creation: Users are now taken straight to a new Fact Packet once it's saved, instead of staying on the Fact Packets grid. | |
| Support Conditionals from Multi-value objects: Users can now build Conditionals (and Tables) using fields that belong to repeatable, multi-record objects, picking one specific record when inserting such a field. | |
| Named List Variables for Multi Object Fields: Users can insert the same multi-object field (for example, Parties) more than once in a template with different selections, by naming each list insertion as its own variable, and each named list is displayed distinctly when the template is reopened. | |
| Include sending SMS with Replace Signer: When replacing a signer on an envelope, the sender can now also choose to send the envelope link to the new signer by SMS, in addition to the email that is always sent. |
explore
| Attach Scheduled Report to Email Notification: Enables users to receive scheduled report results directly as an Excel or CSV attachment in the email notification. | |
| QuickSearch Does Not Return User Results When Searching by Email: This is the resolution for the client support. | |
| Grouped Reports Fail When Related Group Dimensions Share the Same Relationship Path: Users are unable to generate reports when grouped fields share the same relationship path. | |
| Report date fields not displaying US format MM/DD/YYYY: This is the resolution for the client support. | |
| Grouped reports fail when date fields contain mixed data types: Mixed date data types could cause grouped reports to fail. | |
| "At Least" relative date operator returns the incorrect date range: The operator did not return the expected date range and its wording was unclear. | |
| Report Object Changes from Persons/Organizations to Contacts When Favoriting, Causing 400 Error During Run or Scheduling: Minor bug fixes and internal improvements. | |
| Report Execution Breaks When Grouping by Project Name: Grouping an already-generated report execution by Project Name no longer breaks the report page. | |
| Report fails to generate after successful creation confirmation: This is the resolution for the client support. | |
| Chart throws an error when a Category field contains null values: Charts can now be built and modified even when the selected category field is not populated for every record. |
finance
| Time entries default sort should be date descending not name: Time entries are now sorted by date in descending order by default across all views. | |
| Time Entry PUT for other users: Time entries can now be updated from Confido or by other users. |
partner apps
| Form Versioning: This allows for new versions of apps to be created that have new versions of forms to be included. |
workflows
| Is Empty Operators for Number, Date, and Boolean Fields: Rules will be able to check whether a relationship, number, date, or true/false field has any value at all, the same way this already works for text and dropdown fields. | |
| Display an ad hoc task and its documents in the task Drawer: A task created from the simplified form shows everything that was set on it, and the documents attached at creation are reachable from the task itself. | |
| Simplify ad hoc task creation with defaults and a More Options accordion: The form asks only for a name and a due date, fills every other field with a defined default, and keeps the advanced fields behind a single expandable section. |