Skip to main content

Release Notes 2025.4.0

Updated

DB-Migration

This version contains a DB-Migration which changes all existing SharePoint Activity configurations targeting a SharePoint Online using Basic authentication. This was done to update activity configurations used in long running workflows which otherwise won’t get udpated and will cause an error after Basic authentication will be turned off end of April/beginning of May.

This also affects activities of older process versions and we are aware that this also means approved processes will be changed. If your company never used SharePoint Activities that targeted SharePoint Online using Basic Authentication, nothing will be changed.

The migration uses the SharePoint Online OAuth client marked as default for the migration. If your system contains at least one Activity configuration that targets a SharePoint Online and uses Basic authentication, a SharePoint Online OAuth client is mandatory otherwise the migration will fail and the FireStart Server won’t start.

You can configure a SharePointOnline OAuth client using the FireStart Config Wizard. This is also where you can select a default client now which is used for this migration and also as default selection value for new SharePointOnline activities.

If you do not have an Azure App registration regarding SharePointOnline yet, please check the 2025.0.0 Feature Docs which should have been provided to you. You can also reach out to our support team which will provide you with the needed documentation and can help you out otherwise as well.

There is no way of using multiple clients for different workflows.

Keep in mind once this migration is executed there is no way back (other than restoring a database backup or snapshot) so please make sure to use a working SharePoint Online OAuth client for the migration!

If you have any questions regarding this or are unsure whether or not your company is affected by this migration, feel free to reach out to our support team!

Improvements

  • Added an additional output option for the people picker form builder control ‘DisplayName’. This was done to mitigate any confusion when the ‘Name’ property was used that could differ from the shown value as the shown value is the ‘DisplayName’ and not the ‘Name’. We also added a new category for people picker search results ‘External/Guest’ to properly mark guest or external users in the search.

  • Added an option to mark a SharePointOnline OAuth Client entry as the default entry that will automatically be selected for new SharePoint Activities targeting SharePoint Online. This can be configured using the FireStart ConfigWizard. Only one entry can be marked as default.

BugFixes

  • Resolved an issue that would cause an error when using SharePoint dates in a non en-US culture environment.

  • Resolved an issue that would ignore SharePointOnline hidden fields and not fetch their values if such fields have been mapped.

  • Resolved an issue that would cause an error when a Person field was renamed in SharePoint and the FireStart Server was restarted afterwards.

2025.4.1 (Patch)

  • Updated a previous database migration to now also use the newly introduced ‘IsDefault’ option for SharePointOnline Azure Apps. This only affects your system if you are updating from a version prior to 2025.3.0. If you have any SharePoint Activities that use the now deprecated ‘DefaultClientId’ option, the migration replaces all occurences in your database of it with the ‘IsDefault’ selected SharePoint Online Azure app.

  • Resolved an issue that would prevent using the SharePoint-MoveFile Activity to copy folders or folder contents to any target.

2025.4.2 (Patch)

  • Resolved an issue that would break BE-Links in Task Forms when saving processes as new Versions.

  • Resolved an issue that would cause an error when either the filename or the folder name contained special characters (‘%' and '#') which are used as url-escaping characters.

  • Fixed a minor UI issue that appeared when opening a People-Picker configration which was configured before 2025.4.0 causing the ‘Domain’ field to show up twice.

2025.4.4 (Patch)

  • Fixed a culture related issue that would cause numbers to be written in the wrong culture to SharePoint.

  • Resolved an issue that would either cause an exception or simply write wrong or incomplete values to SharePoint lists when adding a new item using either the SP-AddItem-Activity or the Add-BE-Activity. The following field types were affected and have been resolved:

    • Link/Hyperlink

    • Location

    • ManagedMetadata (Taxonomy)

    • ManagedMetadataMulti (Taxonomy-Multi)

  • Resolved an error that caused BE-Field values to be empty when the connected list contained user fields with ‘Email’ as display property.

  • Resolved an issue that caused an exception when the system field ‘Title (link to item)’ was used as the Lookup display property. It now uses the ‘Title’ instead.

  • Resolved an issue that caused a Select-BE Activity to not return any items when a User or Lookup field was used in the selection condition.

2025.4.5 (Patch)

Improvements

  • Improved user search behaviour when trying to add or update a user field in SharePoint. It should now be possible to add/update a user field with either Name, LoginName, Email, UPN (UserPrincipalName) regardless of the configured SharePoint display property.

BugFixes

  • Resolved an issue that caused taxonomy fields to be resolved incorrectly.

  • Resolved an issue that caused some system fields in rare cases to be empty and not correctly fetched.

  • Resolved an issue that caused events not being resolved correctly for User or Lookup SharePoint Online fields.