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.
october 28th to november 4th
adoption
Target field already mapped in another map is flagged: When saving a map, migration users are warned if a target field is already mapped in another map, and the validation popup names that map, so duplicate target mappings are caught before an execution.
Remove the "Data source" when a new mapping is being created: The redundant Data source step is removed when creating a mapping, saving users a repeated selection.
Standardize SmartAdvocate Data Migration Process: Stabilizes the SQL-based SmartAdvocate migration process so it runs without manual data adaptation, documented in a guide and published to the migrations repository.
Flexible Primary Field Selection for Multiple Contact Fields: Migration specialists can designate which phone, email or address entry is primary directly from the mapping canvas, without a separate value alignment step.
Person Addresses field not migrating despite correct mapping: This is the resolution for the client support.
automations
Send an in-app notification from an automation step: An automation step can send an in-app notification so the right people know right away that something ran, failed or changed, with a link that takes them straight to the affected record.
communications
Allow to assign context when there is unknown contact: Staff can assign an SMS, fax, call or Contact Center interaction to the right project or lead even when the sender isn't a known contact, without first identifying or creating the contact.
Align auto-match rules across SMS, Fax, and Calls: SMS messages, faxes and calls are automatically linked to the right contacts and cases using the same rules for every channel. Numbers shared by several contacts link to all of them, communications link to a project or lead only when the matched contacts have exactly one active one, and any contact or project already selected by the user is kept. The rules apply to new communications going forward.
core
BREAKING CHANGE
Remove the read-only lock on converted Leads: Converted leads can now be edited. Action item for admins: define who can edit converted leads by setting "Leads" conditional permission sets based on the leads statuses.
Create "BASIC" Sandbox: Admins can create a Basic Sandbox, a safe copy of the main tenant's structure (forms, workflows and configurations, but not Projects, Leads or Documents) to configure and experiment before promoting changes. A tenant can have up to five at a time, each shows a banner with its name, domain and type, and a sandbox cannot be deleted while it is still being created.
customization
Allow inactivate/reactivate components: Admins can inactivate and reactivate components, inactive components are hidden from views, and the component context stays locked after creation.
Allow table component to filter by object type: Table components in views can be filtered by one or more object types so each table shows only the record types that matter.
Render a Global Table in Insights: Users can browse global views from a side menu in Insights, review paginated tables of records, open any row in a read-only drawer, and jump to the full record in a new tab.
Enable document generation buttons before the record is saved: Document generation buttons are enabled from the start on a new section record; clicking one saves the record first and then generates the document.
Configure a Global Table component: Admins can build a table component for global views by choosing the data source, columns, filters and detail form.
Clear button for Radio Button fields: A small clear button on radio button fields in forms lets users remove a selected value without changing the field type.
Expand heading and text style options in Forms to match Custom Views: Form heading and text style options now match Custom Views (H1–H6, Sub-Titles, Captions, Body 1 and Body 2).
TextLarge field auto-expand and outlined variant: TextLarge fields get an auto-expand option configurable at the field level, and multiline fields use the outlined variant.
explore
Quick Search – Implement Tier-Based Search Execution: Quick Search prioritizes frequently used objects and shows results progressively as searches complete.
Support Tags in Explore Reporting V2: Full Tags support is restored in Explore Reporting V2, so users can report and filter by tags consistently across supported objects.
Refactor Schema Light GET to Include Native Data Type: Explore receives a standardized native data type for fields, so new field types can be supported more consistently.
Audit Log Reporting: Audit Log data becomes a reporting source in Explore, supporting filtering, reporting and exporting for organization-wide audit reporting and investigations of specific records.
Reporting – Unable to Expand Attorney Relationship in By Object Column Selector: Users can expand the Attorney relationship in the Reporting column selector and add related Attorney fields to reports.
Advanced Search – Records are clickable when an object has no Form configured: Records of objects without a configured Form are no longer clickable in Advanced Search, matching Reporting.
Explore Missing Master Fire Relationship Field in Project Columns: Addresses the missing Master Fire relationship field in Explore project columns; a configuration fix is pending validation.
finance
Doc Gen ensure invoice Field population: All invoice fields and their data are reviewed, validated and made available in Doc Gen, so firms can populate any invoice-related field when generating documents.
Payment Account Selection on Invoices: With the partner integration active, Support Staff select a payment account on each invoice to ensure payments made through the partner's payment link go to the correct account. This selection is required before sending the invoice, can be modified while the invoice is in draft status, and becomes locked once the invoice is issued.
partner apps
Validate object dependencies when adding an automation to a partner app: When a partner adds an automation to an app, the app builder checks that every object it references is also in the app and lists any that are missing.
Lock Objects on Install: Objects included in an installed partner app are automatically locked so the client cannot modify them, while the client's own objects stay fully editable.
Release Center: enforce the "Sandbox - Release Center" permissions: Administrators can grant Release Center access independently through the dedicated Sandbox - Release Center permission group, without opening Partner Hub or Marketplace access; existing permissions keep working as before.
Token Prefix is required for credentials when installing an app and should be optional: Clients can install apps whose connection does not use a token prefix; the install form no longer blocks on it.
workflows
Completion Code Dropdown Loads Outcome Codes by Page: The completion code selection on an outcome node loads outcome codes one page at a time and supports typing to search, so it opens quickly however large the catalog grows.
Task Assignment Includes Users With Access Through Permissions: Tasks can be assigned to anyone with access to the record a workflow runs on, whether through a role or through permissions.
Recompute Task Candidate Pool on Group Composition Changes: Tasks assigned through groups stay in sync with group membership: when someone joins or leaves, or a user or group is deactivated, open tasks are reassigned or returned to the Available list, and a task with no eligible person is flagged as blocked until someone qualifies.
Recompute Task Candidate Pool on Role Membership Changes: Tasks assigned through a role stay in step with who currently holds the role, updating when someone gains the role, loses it, or is deactivated.
Now as a Comparison Value for Date Time Fields: The Rule Builder offers "Now" as a comparison reference point so a condition can compare a field against the current moment, available only with the "Less than" and "Greater than" operators.
Button click fails to trigger workflow with error: A button inside the form of a child record now starts its workflow instead of failing with a server error.
Task due date shows a different day in the task list than in the task sidebar: Task due dates show the same calendar day everywhere a task appears.
Task Grids Group Tasks Under the Opposite Priority: Grouping tasks by priority puts each task under the heading that matches its real priority.
Normalize_changed_fields reads the wrong keys from change events: Rules that react to a changed field see the real old and new values, so automations and communications triggered by field changes fire when they should.