2025R2 Release Notes

What’s improved:

The AI Approver Review feature now evaluates all changes in a revision by comparing the revision solution to its base solution (the parent solution) in an approval workflow. It lists all cumulative modifications made since the solution was created. This improvement highlights key differences more effectively, replacing the earlier method where comparisons were made only against the immediately preceding version.

For more information:

• AI Approver Review

Benefits:

The approvers can now see and understand how a solution has evolved by displaying all cumulative changes at once. With the differences highlighted in one place, the approvers can move through the review process faster and make informed decisions more easily. This update enhances accuracy and clarity in the review process.

What's improved:

You can now add an optional comment when you resolve a comment using the Knowledge Updated and Other resolution categories in addition to the existing mandatory comment for Answer to Question.

What it means:

You now have the option to include a comment when resolving feedback, enabling you to provide valuable context whenever needed. This is especially helpful for categories like Other and Knowledge Updated, where previously there was no option to post a comment.

Whether you are a Self Service user, Support Agent, or Solution Manager user, you will now see an optional comment box appear when you select Other or Knowledge Updated as the resolution category. You can add a comment to explain your resolution, but it is not mandatory. If you add a comment, it will be posted in the thread and marked as resolved. Upon comment resolution, the user who posted the original comment thread will be automatically notified by email. Comment remains mandatory for the Answer to Question category.

Our API (POST /comments/resolve/{commentID}) now fully supports submitting comments for all three resolution categories: Answer to Question (required), Knowledge Updated (optional), and Other (optional).

To improve clarity, we have also updated the descriptions for each resolution category.

For more information:

• Resolve or unresolve a comment

Benefits:

This enhancement allows you to add helpful context when resolving or unresolving comments, making feedback clearer, more informative, and easier for others to understand why the comment was resolved or unresolved.

What’s improved:

Users can now quickly access the official RightAnswers product documentation directly through the Help icon across all platforms - Self Service and Support Agent portals, Solution Manager, and the Administrator Console. This enhancement ensures every user has a consistent, reliable source of guidance at their fingertips, reducing the need to search multiple locations for answers. With centralized and up-to-date documentation readily available, teams can more efficiently learn features, resolve issues, and make the most of their RightAnswers experience.

For more information

• Help

Benefits:

This feature ensures the users always have quick access to the latest documentation, improving efficiency, accuracy, and the overall user experience.

What's improved:

We have significantly redesigned and simplified the Administrator Console home page exclusively for the Super Admins. This page is now rebranded as the Application Status page and serves as the landing page for the Super Admins. It will be a single point of entry for managing the health and performance of your pplication.

The core of the new design is the Overview tab, which provides a comprehensive, 24-hour snapshot of the application's current health and status. This tab centralizes vital information across key areas: detailed Solr connection health and the status of Solr Queue (pending and completed indexing requests); Database health, performance, and connection statistics; and Tomcat server status, uptime, and resource utilization, including a convenient Clear Cache button.

In addition to the Overview, all critical maintenance and diagnostic tools have been consolidated onto the new Application Status page for easy access. This includes dedicated tabs for: Reindex Log (history of Solr reindexing), Solr Exceptions (listing errors generated by Solr), Solr Circuit Breaker (monitoring Solr client limits), Server Logs (for troubleshooting), and Index Maintenance (for optimizing search indexes). A new Solr Queue tab has also been added, allowing you to filter and view pending indexing tasks across various time frames (5 minutes, 30 minutes, or 24 hours). This consolidated approach ensures that all necessary performance monitoring and diagnostic tools are available to Super Admins from a single, intuitive location.

For more information:

• Home Page for Super Administrator

Benefits:

The redesigned experience provides a centralized, real-time view of system health and activity, helping Super Admins quickly assess performance and identify issues across critical components. By consolidating key operational insights and tools into a single, streamlined interface, it improves efficiency, reduces navigation time, and enhances overall system oversight.

What’s Improved:

You can now create personalized email notification templates for comments using the new variables we have introduced. Two new variables have been added to the Comment variable in the email templates under the Administrator Console > Content > Email templates:

• $(RecipientFirstName) - the first name of the recipient of the email notification.

• $(ResolverFirstName) - the first name of the user who resolved the comment.

For more information:

• Email Templates

Benefits:

This enhancement allows you to deliver more personalized and engaging email notifications, making messages feel more relevant and user-specific.

What's improved:

We have introduced an important update to how Super Admin accounts are accessed and tracked to improve security and auditability across the Admin Portal.

Direct Super Admin Login can now be restricted

To enhance accountability and meet enterprise audit standards, system administrators can now disable direct logins for the Super Admin account using a system parameter, restrictSuperadminLogin, in web.xml.

• When enabled (restrictSuperadminLogin = true):

  • Direct login via the Super Admin username is blocked.

  • Users will see this message: "SuperAdmin login restricted. Contact Systems Administrator."

  • Super Admin access is still possible, but only via impersonation using the Support Agent portal.

  • Access will be limited to the Admin Portal only.

• When disabled (restrictSuperadminLogin = false): Direct login as Super Admin works as before.

• Super Admin access is only allowed via impersonation

For more information:

• Restrict Super Administrator access

• Impersonate user

Benefits:

This update enhances security by restricting direct Super Admin logins through authenticated impersonation. It also strengthens auditability through detailed logging and controlled navigation, providing full traceability and reducing the risk of unauthorized or untracked administrative actions.

What's improved:

We have made some enhancements to improve transparency and auditability for administrators managing users in bulk.

Available reports:

• Audit Trail Logging: Whenever users are activated or deactivated in bulk, these bulk actions will be recorded in the Admin Audit Trail. This provides clear visibility into who made the changes and when.

• Detailed History Tracking: Bulk user activate/deactivate actions will be logged as individual records in the user history database tables..

Why This Matters:

These changes make it easier to:

• Monitor administrative actions at scale

• Track user status changes more accurately

• Ensures traceability, compliance and accountability across the system

For more information:

• Activate users

• Deactivate users

Benefits:

Bulk activation and deactivation of users are now thoroughly tracked to enhance visibility and accountability. Each user’s status change is individually recorded, ensuring accurate auditing and a clear historical record. This ensures that all user changes are tracked at the individual level for better auditing and historical context.

What's improved:

We have enhanced the 'API Account' checkbox on the Users page with a new tooltip to provide more context.

Now, the following tooltip will be displayed when you hover over the checkbox: “Skips password expiry. Does not control API access permission.”

This update helps ensure you understand exactly what the setting does, making account management more transparent and user-friendly.

For more information:

• Add User

Benefits:

This update clarifies the purpose and functionality of the API Account checkbox, helping prevent confusion and configuration errors during user setup.

What's Improved:

We have enhanced the embedding process to handle large solutions more effectively. Previously, when a solution exceeded the AI model's token limit, the embedding process failed. With this update, the system automatically chunks solutions that exceed the defined token limit, ensuring the embedding process completes successfully without losing essential context.  You can configure the maximum token limit for content using the new Max Context Tokens field under the Solr Administration > Embedding Services UI in the Administrator Console. If this field is set to '0', content will not be chunked.

For more information:

• Create a Solr embedding

Benefits:

This enhancement ensures that even large or complex solutions can be reliably embedded by automatically chunking content that exceeds token limits, preventing failures and preserving essential context. It also gives you greater control over embedding behavior by allowing you to define token limits, resulting in more consistent and reliable AI-driven search performance.

What's improved:

The default value of the following settings has been updated:

• AIAddToKbInstructionRequest - default value has been updated to include double quotes. This setting is accessible only to Super Administrators.

• AllowedidleMinutes - default value has been changed to 60 minutes. This Super Admin setting controls how long the Administrator Console can remain idle. Its default value was previously 10 minutes.

For more information:

• Configure AI Solution Creation prompt

• Configure session timeout duration

Benefits:

The update to AIAddToKbInstructionRequest helps distinguish conversational text from other values in the AI prompt. Increasing the default time each session can stay idle for 60 minutes in AllowedidleMinutes helps keep sessions stable by preventing unnecessary disconnects.

What’s improved:

We have enhanced the GET Solution API to now return rich-text field responses in Markdown or HTML. A new boolean query parameter fieldContentMarkdownto be added in the GET Solution API.

• If fieldContentMarkdownto=true, all rich text fields (for example, Description, Symptoms, Resolution) are returned in Markdown format.

• If fieldContentMarkdownto is set to false or not present, the content is returned in HTML format. This is the default value.

The API continues to return data in JSON format, with field values changing based on the value of the fieldContentMarkdownto parameter. It is compatible with CommonMark and GitHub variants of Markdown.

Additional updates:

• The Markdown response is compatible with HTML elements produced by the Rich Text editor (TinyMCE) in Solution Manager and includes support for strikethrough, underline and code samples.

• The Markdown response does not support the conversion of audio, iframe, embed tags, styles and scripts.

• Nested tables and PNG image formats may not be rendered correctly.

• Video Tags will be converted to clickable links.

For more information:

• Application Programming Interface Reference

Benefits:

The enhanced GET Solution API now allows developers to optionally retrieve rich text fields in Markdown format, simplifying the integration of knowledgebase content into modern applications and interfaces that natively support Markdown rendering.

What’s improved:

We have enhanced the SolutionByLMD API to provide results sorted by modified date in ascending order (oldest solutions first).

Additionally, three new optional parameters have been introduced to offer greater flexibility:

• max: Specifies the maximum number of solutions to return. If not provided, the API continues to return all solutions within the specified date range. When used, the API returns up to the specified number of solutions, starting from the oldest.

• statuses: Filters the results based on solution status. Accepts a comma-separated list from the following: approved, noapproved, draft, archived, deleted, review. If left empty, the API returns solutions of all statuses, maintaining current behavior.

• responseFields: Controls which fields are included in the response, helping reduce payload size. Accepts a comma-separated list of fields such as solutionID, submittedBy, author, lastmod, lastMajorMod, templateSolutionID, status, templateName, id, collections, taxonomy. If not specified, all fields will be included as before.

Additional updates:

• The response now includes the solution’s collections and taxonomy.

• The linkToken JWT for images no longer expires, ensuring continued access without time-based restrictions.

For more information:

• Application Programming Interface Reference

Benefits:

The enhanced SolutionByLMD API significantly improves data retrieval efficiency by offering results sorted by modified date, and introduces new parameters that allow users to further refine the results.

What’s improved:

We have updated the Get Solution by ID API to return the list of images present in the solution.

A new field called images is now part of the Get a Solution by ID REST API response when retrieving a solution by its ID. This field returns an array of image filenames that are actively used in the solution’s template editor fields. It indicates the number of images (on the RA-hosted server) associated with the solution.

• Only images hosted by RightAnswers are returned

• This feature focuses on images used in template editor fields

• Document type solution images are not included

• Duplicate image filenames are also returned.

• Links or external URLs are not returned

• The KPakMediaPath application setting is used to identify and retrieve image filenames for RA solutions.

For more information:

• Application Programming Interface Reference

Benefits:

The API now directly provides a list of image filenames associated with a solution, making it easier and efficient to The benefit is that developers can now easily and reliably retrieve the exact image filenames used in a solution, which greatly simplifies the accurate rendering and integration of the solution's images into external applications during integrations.

What’s improved:

We have enhanced the RightAnswers API to give you more control and transparency over your comment workflows.

• Support for all resolution category:
  You can now use all three resolution categories with the POST /comments/resolve/{commentID} API, not just "Answer to Question" and "Other." The API now supports the following resolution types:

  • Answer to Question

  • Knowledge Updated

  • Other
    
    This gives you a more precise way to track how a comment was resolved, whether it led to an update in your knowledge base or was handled in another way.

• Add a comment with any resolution type:
  You can now include a comment with any resolution type, not just Answer to Question. This update ensures consistency between API and UI behavior—and gives your users full flexibility to explain resolutions.

• Richer Metadata in Comments API response:
  We have updated the GET /comments/ endpoint to provide more detail on resolved comments. You will now receive a richer set of metadata for each comment, including:

  • isResolved: A boolean value indicating if the comment is resolved.

  • resolvedBy: The username or email of the person who resolved the comment.

  • resolvedDate: The exact date and time the comment was resolved.

  • resolutionCategory: The specific category used to resolve the comment.

  • resolvedFrom: The interface from which the comment was resolved (e.g., SA, SS, SM).
    This new information makes it easier to track the lifecycle of a comment and build automations based on its status.

• Automated Notifications:
  To improve transparency, we have enabled automated email notifications. When a comment is resolved, an email is now automatically sent to the original commenter, the person who resolved the comment, and the solution author. This ensures that all relevant parties are immediately notified, closing the feedback loop and keeping everyone informed.

For more information:

• Application Programming Interface Reference

Benefits:

These enhancements improve transparency, automate user feedback workflows, and ensure all stakeholders are notified about comment resolutions.

What’s improved:

We have enhanced the RightAnswers API to give you more control and transparency over your comment workflows.

• Support for all resolution category:
  You can now use all three resolution categories with the POST /comments/resolve/{commentID} API, not just "Answer to Question" and "Other." The API now supports the following resolution types:

  • Answer to Question

  • Knowledge Updated

  • Other
    
    This gives you a more precise way to track how a comment was resolved, whether it led to an update in your knowledge base or was handled in another way.

• Add a comment with any resolution type:
  You can now include a comment with any resolution type, not just Answer to Question. This update ensures consistency between API and UI behavior—and gives your users full flexibility to explain resolutions.

• Richer Metadata in Comments API response:
  We have updated the GET /comments/ endpoint to provide more detail on resolved comments. You will now receive a richer set of metadata for each comment, including:

  • isResolved: A boolean value indicating if the comment is resolved.

  • resolvedBy: The username or email of the person who resolved the comment.

  • resolvedDate: The exact date and time the comment was resolved.

  • resolutionCategory: The specific category used to resolve the comment.

  • resolvedFrom: The interface from which the comment was resolved (e.g., SA, SS, SM).
    This new information makes it easier to track the lifecycle of a comment and build automations based on its status.

• Automated Notifications:
  To improve transparency, we have enabled automated email notifications. When a comment is resolved, an email is now automatically sent to the original commenter, the person who resolved the comment, and the solution author. This ensures that all relevant parties are immediately notified, closing the feedback loop and keeping everyone informed.

For more information:

• Application Programming Interface Reference

Benefits:

These enhancements improve transparency, automate user feedback workflows, and ensure all stakeholders are notified about comment resolutions.

What’s improved:

A new optional filter parameter, templateSolutionIDs, is added to the Search API endpoint. This parameter will accept a comma-separated list of template solution IDs to filter search results matching the template ID.

The API will return only those solutions whose template solution ID exactly matches one of the provided IDs. Solutions that merely reference the ID in comments, body text, or metadata will not be included.

For more information:

• Application Programming Interface Reference

Benefits:

This enhancement enables the API to return exact matches and gives you greater control over the search results.