| Feature | Summary |
| Module Designer > Proximity Search > Multi-Location Records | Fixed proximity search filtering for modules configured with multiple GeoCode fields (e.g., Physician Directory with 4 office locations). Previously, records with multiple locations were
incorrectly filtered using only the primary location's distance for all WHERE clause conditions. Now each location is correctly evaluated against its own calculated distance. Behavioral change:
Modules using ResultsProximityFieldCount > 1 will now return different results — records previously excluded because their primary location was outside the search radius will now appear if any
secondary location is within range. |
| CAD Files Viewer | Previously, a CAD drawing that couldn't be shown rendered as a blank screen with no explanation. The viewer now detects the drawing's status and shows a brief message explaining why: it's still processing, it couldn't be loaded right now, or the source file failed to convert. Every message includes a Copy link button so a visitor can forward the page to their website administrator, and the conversion-failure message adds an administrator note with the underlying error and steps to re-publish the file. This behavior applies automatically and requires no configuration or setup changes. |
| Module Details > Email a Friend > Multiple Recipients | The Email a Friend feature on module details views now supports sending to multiple recipients in a single submission. A new AllowMultipleRecipients attribute has been added to the Generic
Enhanced module under the Details Email tab. When enabled, the recipient field label updates to "Recipient Email(s)" with a hint to separate addresses with commas. Users can enter multiple email addresses
separated by commas or semicolons, and all recipients receive the email in one send. Duplicate addresses are automatically removed, and the confirmation message displays the count of recipients when more
than one address is entered. |
| Design > Script Generator > Page Assistant > Use Knowledge Base (RAG) | In the Design > Script Generator module, records whose Script attribute is set to Page Assistant gain AI knowledge-base (vector search) grounding, driven by a new Use Knowledge Base (RAG) attribute. When enabled, the Page Assistant can answer end-user questions using AI-indexed module records - the "knowledge base" - in addition to the content of the current page, bringing the same meaning-based search that powers the Knowledge Assistant to the public-facing Page Assistant.
The new attributes appear on a Page Assistant script when Show Chat is enabled:Use Knowledge Base (RAG) - off by default; turn on to let the assistant search AI-indexed module records. Turning it on reveals the options below.Use Page Content - on by default; keep the current page as the primary source, or turn it off to make the assistant answer purely from the knowledge base (an on-page Knowledge Assistant).Knowledge Base Modules - choose which AI-indexed modules to search, or leave it on All Vector Modules. The list shows one entry per module using its display alias.Knowledge Base Results (Top N) and Knowledge Base Similarity Threshold - tune how many records are retrieved and how closely they must match.Show References - show or hide the list of source records used in an answer.References Template (Template mode only) - customize how each reference renders.
When the knowledge base is on, the assistant answers from the page first and supplements with indexed records only when the page falls short, citing the records it used. A References list appears beneath each reply; when the site's public URL is configured, each reference links to the source record's page. Retrieval respects all standard content security - a visitor only sees records permitted by their audience, roles, publish dates, and enabled status. The assistant also remembers the conversation per page: returning to the page reloads the prior chat and its references, and long conversations stay responsive because older turns drop out of the AI's working context while the full history is retained.
Only modules enrolled in AI Vector Indexing (Development > AI Indexing) are searchable. |
| Console > Data Transfer > Field Map Scripting > OcrZone (OCR) | OCR text extraction is now available in Data Transfer through a new OcrZone CpScript. Added to a field map, it reads the text from a scanned image and writes it to the destination column, turning scanned documents into structured, searchable content instead of flat image files. This feature supports extracting the whole page or just a fixed area of it, such as an invoice number or a date that always sits in the same spot on a form. Recognition runs entirely on a local engine, so no image data leaves the server, and common formats are supported including PNG, JPG, BMP, GIF, and single- or multi-page TIFF. Optional settings are available to clean up, format, and validate each value before it is saved. Full setup details are in the Script Builder help for OcrZone. |
| Data Transfer > Clicks Destination | The data transfer that imports activity into the legacy Clicks area has been hardened so that it can no longer stall and hold database locks that make the rest of the site unresponsive. Each batch is now written through a safe staging step and committed as a single unit, so the Clicks and Clicks Log records always land together. A time limit on database waits ensures a blocked write fails quickly instead of waiting indefinitely. Behavior is otherwise unchanged: the same records are imported, and if a batch fails it is logged and the transfer continues.
|
| Master > Process Monitor | The live Process Monitor now shows each running process's Id as the first column, rendered as a link. Clicking the Id opens that process directly in the Process Log, where its full step-by-step history is shown. Previously there was no way to jump from a running process to its log entry. The Process Log search now also includes a Process Id field, so a specific process can be looked up by its Id. |
| File Upload > Supported Extensions | Added support for .upg and .cli file extensions to the allowed upload list. These extensions are used by Ericsson network equipment for firmware upgrade packages (.upg) and CLI configuration scripts (.cli). Both extensions are restricted to authenticated users only and are not available for anonymous uploads. |
| Console > CMS > IAM Connector > OIDC B2C PKCE Authentication | A new OIDC B2C authentication option has been added to the IAM Connector module for Azure AD B2C single sign-on. This enables PKCE (Proof Key for Code Exchange) authentication flow, which is
more secure for browser-based logins and does not require a client secret. When enabled, the module generates a login button using the OidcB2CLoginButton CpScript. The authentication flow supports:
- PKCE code challenge/verifier for secure token exchange
- B2C custom extension attributes (e.g., extension_email)
- Proper B2C session logout via the IdP logout endpoint
- Username fallback chain: email → display name → first/last name → subject ID
- Force fresh login with prompt=login to prevent stale session issues
Configure the B2C settings under the Solenis B2C section in the IAM Connector record, including Client ID, Authorize URL, Token URL, and Logout URL. |
| Data Cleaner > Rule Priority Ordering | The Priority attribute is now visible on Keyword Generator, Taxonomy Generator, and Attribute Generator rules in the Data Cleaner module. It was previously available only on HTML Cleaner, Attribute HTML Cleaner, Data Triage, and SQL Query.
Rules within each of these three types now execute in ascending Priority order, with Title as the tiebreaker. Important: Priority orders rules within their type. All Keyword Generator rules execute in priority order, then all Taxonomy Generator rules, then Attribute Generator rules. Priority does not interleave across rule types.
New help text on the Priority field describes this ordering contract directly in the form, so admins setting priorities see the rules of the road inline.
This is useful for tiered/multi-pass classification scenarios. For example, with Taxonomy Generator set to single-select, a low-priority rule can serve as a specific match (e.g. "kidney transplant" -> Nephrology / Transplant) and a higher-priority rule can serve as a broader fallback (e.g. "kidney" -> Nephrology / General). The most specific match wins because it fires first. |
| Master > Utilities > Database Maintenance on Selected Site(s) | Database Maintenance has been improved for both the manual Database Maintenance on Selected Site(s) task in Master > Utilities and the automatic maintenance that runs on a schedule. Two issues from the previous release were addressed:
- Large transaction log files that previously stayed oversized are now reduced. The routine makes several passes so that even multi-gigabyte logs are brought down toward 1 GB.
- Error notifications are no longer raised for logs that have already shrunk to their healthy minimum. Previously a notification was sent whenever a log settled slightly above 1 GB even though shrinking had succeeded. A notification is now only sent when a log genuinely remains oversized after maintenance completes.
Sites running full recovery with recent log backups continue to be left untouched so externally managed backup chains are preserved. |