This release will be available as "Release Candidate" from Thursday, 1 March 2018 and will go live on 6 March 2018.
This minor release has been scheduled in order to release improvements that we deemed too important to wait for the major release (scheduled for Q2 2018).
It includes some important improvements to the security management features as well as performance improvements.
Also it includes the Dynamic Site Creation that was scheduled for our release in December 2017 but failed the quality test.
Changed security management
With this release we have changed the feature "incremental security replication" and made it optional. By default it is not available, but can be activated in case it is needed. The reason for this move is that the feature is very rarely needed. In those specific cases where it is still needed it can be activated by contacting WorkPoint A/S.
Another change affects full security replication. This feature is now only available to schedule as a one-off job, i.e. it cannot be scheduled to run on intervals. Experience has shown that it requires a lot of SharePoint resources to run and often slows down the system as it is used incorrect or when it is not necessary. This feature should only be used to correct things when the security settings for some reason gets out of sync.
Improved performance on event receivers
To increase performance we have made the following changes: WorkPoint365 settings is now cached serversite. This improves performance as the system makes fewer requests to SharePoint.
Also we have optimised the event receivers. More tasks have been moved away from event receivers and are run as jobs instead.
Expansion of web API - support for SharePoint managed metadata
This release also includes an expansion of our web API used for integration with other systems. We are now able to update SharePoint managed metadata fields using the API.
Until now elements in WorkPoint modules have been designed either with or without sites. In some cases you could manually create a site. Now, with the dynamic site creation, it is possible to manage when a site should be created. For example you can now have sites created based on the entity stage, and if the stage changes, the entity will get a site.
Also you can import data first and then create sites later on, making data import much faster.
Information on how to use dynamic site creation is here.
wpStage Field does not get a value when item is created from quick edit (#18316)
wpStage field not set when creating new items using the releations feature (#18680)
Aggregation type count with filtering does not trigger update in event receiver (#18676)
Scheduled aggregation job cannot be stopped
Check for existing site collection in provisioning uses wrong id
Site collection provisioning does not exclude content types from HUB
Fixed bug in security where users with read only rights could delete