Version: Next

✨ What's New

This list includes all new major features implemented.

WebDAV moved from IIS into inPoint.Core

Internal: see TFS [#75158]
The implementation of WebDAV is no longer hosted inside of IIS but moved into the inPoint.Core service.

The root handler of WebDAV is no longer needed (it was  directly in C:\inetpub\wwwroot) The setup will remove the library and the config file used.  In case the config file  'C:\inetpub\wwwroot\web.config' was modified by the user there will be a warning during the setup and the file will be added to the backup folder.

The URL on which WebDAV operates is now the inPoint.Core URL  with 'webdav' appended (e.g. https://testServer.domain.local:5443/webdav)
    • The setting 'pamWebDavUrl'  in web.config is no longer needed and will be commented out by the setup.
    • The setting in inPoint.Identity to allow Office Form Based Authentication will be update by the setup if the setting is configured.
    • In case of a Proxy additional steps may be needed to configure the URL changes.

inPoint.Archive: use gRCP connection to HybridStore

Internal: see TFS [#75458]
On a machine of  Windows Server 2022 or higher the inPoint.Wizard will automatically configure inPoint to use the gRPC-interface when connecting to inPoint.Hybridstore.

  • inPoint.HybridStore
    • sets the certificate (selected during installation)
    • add a URL with HTTPS and the port 823)
      e.g. "https://%COMPUTERNAMEFQDN%:823/HybridStore"
  • inPoint.Archive.Config
    • set HybridStoreUrl to use prefix grpcs instead of http(s) or net.tcp
      e.g. HybridStoreUrl="grpcs://server.domain.local:823/HybridStore"

inPoint.Core migrated from HTTP.sys to Kestrel

Internal: see TFS [#75466]
inPoint.Core was migrated from HTTP.sys to Kestrel.

See the documentation inPoint.Core Configuration · inPoint.Enterprise for the needed changes in the inPoint.Core configuration.

Filtering and sorting for user fields in the document list

Internal: see TFS [#76352]

Filtering and sorting by "Created by" and "Modified by" is now available in:

  • the document list
  • shared documents

HierarchyProvider: Disable Offline and Ping when used inPoint.Web

Internal: see TFS [#76937]
A new optional parameter supportOfflineMode was added to the constructor of the HierarchyProvider.

When not specified supportOfflineMode is true and the behavior is the same like before.

inPoint.Web initializes the HierarchyProvider with supportOfflineMode=false to disable the offline mode and the connection-pings.

Added gRPC client to HierarchyProvider

Internal: see TFS [#77482]
The HierarchyProvider was extended by an gRPC client
It is enabled when:
  • Only for the .net 8.0 build
  • CoreUrl is set and not using HTTP (HTTPS is required)
  • IdentityUrl is set
else it uses the old WCF client.

You can enforce the mode by a setting in the registry:
  • Key \\HKLM\Software\Wow6432Node\HS Europe\inPoint\Environment\{environment\}
    • ForceClientMode=gRPC  - enforces the gRPC client, fails when gRPC is not available
    • ForceClientMode=WCF - enforces the WCF client

HierarchyProvider refactoring

Internal: see TFS [#77614]
Some changes were made to the HierarchyProvider for a better performance with inPoint.Web
  • Caching can be controlled by the caller
  • State handling was improved (especially for many parallel instances/users)
  • Still work in progress!

Improved performance for recycled documents

Internal: see TFS [#77629]
Accessing the recycled documents is now faster.

Cursor pagination for GetUserResources (⏳ Pending) (💩 Missing Documentation)

Internal: see TFS [#77889]

Pending detailed information!

Improved folder tree performance

Internal: see TFS [#77917]
The folder tree now loads and responds more quickly, speeding up navigation and document access.
Note: As a side effect, the child count in inPoint.Web is no longer displayed when hovering over a folder.

Notes-Reply enabled when no text was entered

Internal: see TFS [#78749]
A small fix in the Reply button for Notes: The button is now always enabled but a message box appears when text field was empty.

Performance improvements for managing the Shares

Internal: see TFS [#79065]
Sorting / filtering for shares is now done at server side.

Raise Infragistics.WPF to 25.1.117

Internal: see TFS [#79326]
There is a new Infragistics.WPF (25.1.117) instead of the currently used 23.2.94.
This new release should solve some/all pending issues with inPoint.Standalone and Thai.

But there are some breaking changes which are not solved yet. So, this upgrade is postponed - inPoint stays at 23.2.94!

ExtraAttribute: Search for display value instead of key value

Internal: see OTRS [2024092701000011]
Internal: see TFS [#79357]
When creating a search form for fulltext search, it's possible to use a lookup for a field to translate from a display value shown by ExtraAttributes to the key value stored in the item field. The lookup of values supports all string operators (Contains, Equals, Starts With,...) and will use them to search for values using the lookup and then uses the found key values in the resulting fulltext search.

In the form designer, choose a lookup and then select the columns used for the key value and for the display value.

Image

The search result will still return the original data from the search with the exception of the search-as-you-type feature when using the "Choose from existing".

When translating a display value to a key value, it is possible that the translation finds more then 5,000 possible candidates in the lookup. In this case an error is returned that the search found too many intermediate results.

Image


Attach Image to #81038 and remove HTML-Tag/Markdown from description!

Sort jobs logs by time descending by default

Internal: see TFS [#80386]
in inPoint,Admin when showing the Job-Logs, the result is now by default sorted by time descending.

Custom-Plugins add LoaderExceptions details (⏳ Pending) (💩 Missing Documentation)

Internal: see OTRS [2025122201000076]
Internal: see TFS [#80732]

Pending detailed information!

HierarchyProvider instances in PowerShell scripts must now be created using the PowerShellHelper class

Internal: see TFS [#81394]
HierarchyProvider instances must now be created exclusively via the CreateProvider method of the PowerShellHelper class.