Skip to main content

WorkPoint 365 Update - 26/8 2026

  • Reading time: —

Release candidate date: 26th of August, 2026 at approx. 19:30 CET.

This release introduces several improvements to WorkPoint Automate, including the new Run AI Prompt step for integrating Azure AI capabilities into automated processes and the Adaptive Expression Helper for easier expression creation and troubleshooting. The release also adds a new Export/Import pre-check feature that helps identify common configuration issues before importing a WorkPoint solution. In addition, a number of fixes and stability improvements have been made across the WorkPoint 365 product.

We recommend reviewing the new features and bug fixes described below before upgrading.

New Features and improvements

WorkPoint Automate - Run AI Prompt step

The Run AI prompt step enables WorkPoint Automate processes to interact with Azure AI models directly from within a workflow. By providing instructions and input data, the step can generate structured AI responses that can be used in subsequent process steps, making it possible to automate tasks such as information extraction, classification, summarization, and metadata generation.

The step also supports schema-based output validation to ensure consistent and predictable results.

You can read more about the Run AI Prompt step in this article. An example of use can be found in this article.

WorkPoint Automate - Adaptive Expression Helper

The new Expressions Helper in WorkPoint Automate makes it easier to build and troubleshoot expressions when designing processes. It provides guidance on expression syntax, helps identify common issues, and supports users in creating more advanced logic with greater confidence, reducing the time spent testing and correcting expressions.

You can read more about the Adaptive Expression helper in this article.

Export/Import Pre-check

A new pre-check feature has been added to the Export/Import page in WorkPoint Administration. The pre-check helps identify issues that could prevent a WorkPoint solution from being imported successfully, allowing administrators to resolve them before starting the import process.

Examples include missing Entra ID groups referenced in security rules, missing term sets used by Managed Metadata fields, or required WorkPoint Automate service users that have not been configured on the target environment. By detecting potential issues upfront, administrators can avoid lengthy failed import attempts and reduce troubleshooting efforts.

Documentation on how to use the Export/Import Pre-checker will be released soon.

Bug Fixes

Zendesk ticket IDs in parenthesis

  • Fixed an issue where it was not possible to synchronize the "Open in a new tab" setting for Quick Navigation elements using Master site synchronization (#60451)
  • Improved the WorkPoint 365 Power Automate trigger so dynamic content is now exposed correctly (#61037)
  • Improved master site synchronization so rules based on calculated fields now apply more reliably during entity updates and site creation (#61278)
  • Fixed an issue where it was not possible to use the ChangeStage API endpoint using from a daemon application (#61535)
  • Fixed an issue where the Advanced Search webpart would crash and disappear from pages if trying to display a column group containing a number field (#62645)
  • Fixed an issue that could result in duplicate sites being created for the same entity when automatic site provisioning and manual site creation were triggered concurrently (#62793)
  • Fixed an issue where stage changes could not be initiated from the stage ribbon in the details pane, ensuring consistent stage transition behavior across the user interface (#62883)
  • Fixed an issue where master site synchronization folder rules did not consistently respect configured conditions, which could result in folders being created unexpectedly (#61245)
  • Fixed an issue where Excel to PDF conversion always used en-US locale (#62444)
  • Fixed an issue where copying or moving multiple PDF documents could result in duplicate documents being created when using the Send To functionality (#62529)
  • Resolved an issue where Managed Metadata fields only displayed up to 20 terms, even when the underlying term set contained more entries. This caused some values to be hidden unless users searched manually (#60668)
  • Added WorkPoint Automate settings to hide disabled users and option to create a custom filter that is applied globally in Automate people/user pickers (#61404)
  • Fixed an issue where Sub processes sometimes showed "Completed" text while it is still running and should not yet be closed (#61888)
  • Fixed a styling issue causing "days callout" to overlap with the "month callout" when opening the calendar in a datepicker in WorkPoint Automate forms (#62223)
  • Fixed an issue where the "Search for item in list" process step could not correctly match values in rich text multi-line fields, causing searches to return unexpected results (#62495)
  • Fixed an issue where number fields in Automate form did not correctly take locale into account (#62239)
  • Fixed an issue where WorkPoint Automate Custom Form note fields could display raw HTML from rich text SharePoint columns instead of readable content (#62818)
  • Fixed an issue where the Relation type dropdown on the first relation card in WorkPoint Automate could not be selected until an extra relation card was added and removed (#63543)
Was this article helpful?
0 out of 0 found this helpful

Related articles

Comments

0 comments

Please sign in to leave a comment.