WorkPoint 365 Version 3.9.2

These notes contain both the new features and improvements of WorkPoint 365 version 3.9.2, which was released to Release Candidate the 1st of February 2021.

WorkPoint 365 version 3.9.2. is being released for general availability on the 18th of February 2021 at 19:00 CET.

New Features

Template Management

Managing templates for documents and other items is an important aspect of well-structured data- and document management.

Using Template Management in WorkPoint it is possible to create multiple template lists and libraries for different types of content. Examples of these could be template lists for task templates, folder structures which can be imported into libraries, and custom document template libraries.

These template lists and libraries are stored in the root site collection of the solution.

With the use of templates, administrators can define templates for these various types of content, which users can then add to entities using a Wizard.

You can read more about this feature in this article.

Task Management - Batch updating items across sites

Batch Update is a feature which makes it possible to update multiple items across multiple sites in the same action.

One use case for this feature could be in a project management solution, where a set of task has been assigned to specific person. This person leaves the company and needs to be replaced in the system. All task assigned to this users needs to be reassigned to a new employee.

Another use case could be that every year, all tasks of a specific type on a solution needs to be completed the 1st of April. This year this deadline is moved. Therefore, a WorkPoint user needs to find all tasks of the specific type across sites and update the date.

This feature can be used from the Advanced Search webpart or the WorkPoint Express panel once configured.

You can read more about this feature in this article.

Extensions to Copy Entity

Copying entities can have various purposes under different scenarios when working in WorkPoint. WorkPoint now features a set of settings which can be set at business module level, which allows administrators to modify aspects of the copy operation of entities by e.g. introducing time displacement on various fields.

With this addition of copy entity settings, WorkPoint makes it possible to create copies of existing entities while simultaneously setting specific data fields. One example of this could be creating a copy of a Case entity on a Case Management solution. when creating the copy of the case, the completion date can be automatically set in relation to the original case, e.g. by displacing the original completion date and using that date for the copy.

A typical use case for this feature could be accountants making annual accounts for clients. Each year becomes a case with it's own set of tasks that needs to be completed. Every year, the case from the previous year could be copied using this feature along with all tasks, and deadlines can then be displaced by e.g. a year.

Another use case could be related to Project Management where a new project a new project similar to a previous project needs to be created. In that case, the previous project can be copied along with e.g. task- and risk lists. A deadline for the new project can then be set, and sub-deadlines for e.g tasks can then be displaced accordingly.

You can read more about this feature in this article.


  • The Task Overview webpart has been updated to Support Microsoft Lists. Several other improvements to the webpart has also been released. You can read more about the Task Overview webpart in the article
  • The Relations webpart have been improved with options to hide the buttons to edit the relation, delete the relation, and edit the entity.
  • The Advanced Search webpart has been improved to allow users to select a height between 300 and 2000 pixels. If the options is left blank, the webpart will dynamically resize to fit the window it is displayed in.
  • When updating an entity through integrations/WebAPI the system now checks if any data from the input fields are used for triggering jobs in the system. If not, the job is not triggered. An example could be if a security job uses a specific field as activation condition, and this field is not an input field for the entity update through the WebAPI, the security job is not run.
  • Performance has been optimized when getting template info wizard step
  • An option to skip last step in the settings for the Copy Entity wizard has been added.
  • The WorkPoint Embed webpart now supports user fields to be used as properties in the URL. This allows e.g. the current user e-mail or department to be used as parameter for reports and other scenarios.
  • Include [entity property] in search settings
  • Search Setting base queries now supports entity parameters such as wpProjectType.
  • Support both month and days in template management field mappings
Have more questions? Submit a request