Release date: 3rd of April 2025 at approx. 19:00 CET.
This release introduces a major enhancement with the integration of Microsoft Purview Information Protection, enabling organizations to apply sensitivity labels automatically based on metadata. This feature helps enforce compliance and secure content across documents, sites, and Microsoft 365 groups.
In addition, as per usual we are committed to further enhance the stability and performance of WorkPoint 365 by addressing existing issues in the product.
New features
Information protection rules
WorkPoint 365 now supports the use of Microsoft Purview sensitivity labels through information protection rules. This enables organizations to classify and protect data across documents, sites, and Microsoft 365 groups based on sensitivity. Labels can be applied automatically based on defined rules and activation conditions based on metadata, helping ensure compliance with internal governance policies and external regulations. Once applied, sensitivity labels enforce policies such as encryption, access restrictions, and sharing limitations.
Information protection rules are set up on the security settings pages for each business module in WorkPoint 365. Administrators can define information protection rules to apply sensitivity labels to sites in WorkPoint, Office 365 groups, and default sensitivity labels for document libraries on entity sites (which will be inherited to documents in affected libraries). These rules can be applied in every scenario, or based on activation conditions.
For more information about information protection rules, please visit this article.
Copy Entity Content
A new step has been introduced to WorkPoint Automate: Copy entity content.
This step can be used to specify a source entity, and select which content, including relations and list contents, to copy to a specified target entity. You can read an example of use of the step in this article, and technical information about the step in this article.
Improvements
- Several improvements have been made to how WorkPoint Automate processes are displayed on mobile devices, ensuring a better and more consistent experience across both desktop and mobile platforms such as smartphones and tablets.
- Minor improvement in installer to support changes from Microsoft (https://devblogs.microsoft.com/microsoft365dev/changes-on-sharepoint-framework-spfx-permission-grants-in-microsoft-entra-id/)
- Optimizations have been made to the ConvertToPDF API endpoint which would fail when trying to convert a large number of documents in one operation.
- Field references in typed in or inserted into fields in steps in the process builder will now display icons, depending on the method with which they were inserted. Icons are displayed as follows:
In the examples in the picture, "Selected Items" has been selected from the list of options in the Step Input field, while "Entity.ID" has been selected from the process context. In the Show details panel field "No" has been typed manually into the field. In the Description field, which uses rich text, a custom text has been inserted, along with "string(Entity)", which comes from an adaptive expression inserted into the field.
- When new business modules are created, they will now have the WorkPoint provided standard processes set to be used for various purposes. These can be changed before starting the business module provisioning, or afterwards in the general settings of the business module.
- When calling the WorkPoint API endpoints, the header "WorkPointJobQueue" can be used to specify which job queue the job should be sent to for processing. Examples could be "Integration" or "Management". Here's an example from Postman where we are using the API to create an entity, and where we are sending the job to the Integration queue:
Here's a link to the WorkPoint API Postman project, where you can create your own fork and try out calling the WorkPoint API: https://www.postman.com/workpoint365/workpoint365/collection/nj8uwbm/workpoint-api
Bug fixes
- Entity Creation Fix: Resolved an issue with retrieving wpParent during entity creation.
- Job Initialization Issue: Fixed a bug that prevented jobs from starting as intended.
- Signal R Exception On Entity Copying: Resolved System.InvalidOperationException during the entity copying job.
- Relations Webpart Date Issue: Fixed an issue where the Relations webpart displayed dates using the incorrect time zone.
- Navigation View Sorting: Fixed an issue where business module views displayed from a business module in the WorkPoint Home menu were not sorted alphabetically.
- Recycle Bin Threshold Error: Resolved error related to list view threshold when deleting sites from the recycle bin.
- Missing Business Module Site Link: Fixed the issue where the site link was missing in the Business Module list.
- Digital Post Notification Messages Switched: Corrected an issue where notification- and additional notification messages were being interchanged incorrectly.
- List View Webpart Document Opening: Addressed an issue where documents were not opening as per the "open in the client application" setting.
- Copy Entity Performance: Improved performance for copying entities.
- Document Extension Display: Rectified an issue where the Item Form sometimes displayed the wrong document extension when receiving metadata from a template.
- Leading White Spaces in Entity Title: Fixed site creation failures due to leading white spaces in entity title.
- Option Values Cut Off: Fixed an issue where items with a long name selected in a Process form would get cut off. Max value width is now 500 pixels in desktop mode, and 300 pixels on mobile views.
- SynchronizeGroups Server Exception: Resolved an issue where site collection replication of security groups failed if entity contained tailing white spaces.
- Mandatory Field Check on Stage Change: Fixed a bug where content type fields were not checked for requirements upon stage change.
- Single Buffer Site Creation Job Duplication: Prevented requeuing of already existing Single Buffer Site Creation jobs in the dispatcher.
- Security Rule Deletion Issue: Corrected an error where deleting one security rule would mistakenly remove another due to duplicate IDs.
- Different Number Formats in Merge Fields: Standardized number formats in merge fields between Process and Wizard usage.
- Security Replication for deleted user: Fixed an issue where running a security replication on a multi-user field would fail if encountering a deleted user, and not set security for subsequent users in the field. An alert can now be set up to catch the warning produced by security replication hitting a deleted user.
- License Information Page Error: Resolved an error where the License Information page would fail to load if a customer changed contact information.
- Batch Loading Users: Fixed an issue where loading a large number of users in a field was not properly done in batches.
- Select Solution Template Removal: Removed the option to select a solution template in the WorkPoint installer, as solution templates have been deprecated.
- Aggregation Last Activity Date: Fixed an issue where aggregating the Last Activity date did not work properly.
- People Picker Data Length: Resolved a data length issue in the people picker field within the process builder, which made it impossible to focus a field to select more people.
- System Process Context Preservation: Ensured the _before values in system process context are preserved after the first step.
- Deletion Handling for Entity Sites: Fixed the marking of entity sites for deletion when related site collections are no-script sites.
- Missing Template Library Command Set: Fixed an issue where solutions created on a No-script site got created without the proper Command Sets on the default Template Library.
- Blank Entity Form in Automate Process: Addressed an issue causing Entity Forms to appear blank in WorkPoint Automate process if business module contained more than 5000 items and more than 14 lookup fields.
- Custom Document Set Creation Failure: Resolved an issue where custom document sets failed to create on entity sites.
- Lookup Fields Not Returning Results: Fixed an issue where Lookup fields did not return any results when looking in a business module list with a large number of entities.
- Stage Model Changes and User Process: Fixed an issue where changing stage models in an Entity Form did not properly update the fields displayed.
Comments
0 comments
Article is closed for comments.