Version: 2025.1.1

🏴‍ Known Issues

This list includes all pending known issues not yet resolved.

[4 - Low] Async react-select options are positioned wrong on Screens < ~450px​

Description​

Internal: see TFS [#51342]
Async react-select options are positioned wrong on Screens < ~450px. In combination with position: auto the select options need at least 450px Screen size to calculate correctly.

Workaround​

Internal: see TFS [#51342]
This is a known issue from react-select, that won't be fixed. No workaround possible.

[2 - High] Rules are not evaluated correctly when using DocAttributes​

Description​

Internal: see TFS [#51840]
inPoint.Web archives a file without checking the rules before. Then the server just rejects the upload.

Workaround​

Internal: see TFS [#51840]
No workaround available

[3 - Medium] inPoint.Web.IdentityServer/Windows Server 2012 R2: ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY​

Description​

Internal: see TFS [#54678]
Installed on Windows 2012 R2 the ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY error message is displayed even if the "Urls": "allowUnsafeSslProtocols" has been set in the appsettings.json.

Workaround​

Internal: see TFS [#54678]
Add the following section to the appsettings: 
"Host": \{
    "EndpointDefaults": \{
      "Protocols": "Http1"
    \}
\},

[4 - Low] Broken WorkflowProvider will slow down Folder Classification​

Description​

Internal: see OTRS [2021032201000037]
Internal: see TFS [#56685]
If there is a misconfigured Workflow Provider, it will take a significant longer time to load any FolderClassification.

Workaround​

Internal: see TFS [#56685]
Fix your Workflow Provider configuration.

[4 - Low] Win 8.1: the Web Sharing API CommandAction does not work​

Description​

Internal: see TFS [#58394]
Due to limitations on the implementation of Web Sharing API in Win 8.1. This won't be fixed.

Workaround​

Internal: see TFS [#58394]
Please fall back to the inPoint.Web Share dialog, if you need to provide a sharing feature.

[4 - Low] Localization from custom ActionPanel Categories and ItemActions is not applied​

Description​

Internal: see OTRS [2021040801000035]
Internal: see TFS [#59430]
It is currently not possible to translate custom ActionPanel Categories and ItemActions. 

Workaround​

Internal: see TFS [#59430]
Currently no workaround available. We are working on a Feature to enable translation on all customizations

react-select can overflow DocModal​

Internal: see TFS [#68288]
react-select will always use the available with for the input to render the options
This will be fixed, when react-select allows popper.js to handle the positioning.

Note: Currently no workaround is available

[3 - Medium] DocAttributes lose create and read timestamp info on uploaded files​

Description​

Internal: see TFS [#75877]

Plugin DocAttribute lose timestamp information of the original file. Specifically, the following properties are not functioning as expected: File creation time local or UTC and File last access time local or UTC

Workaround​

Internal: see TFS [#75877]
This is a browser API limitation without a workaround. If this changes in the future, we will revisit this issue.
  • [#76889] [3 - Medium] Sorting direction only change for second click for searchResult_form CommandActions

[3 - Medium] inPoint.Core: Swagger ignores fields in CreateDocument​

Description​

Internal: see TFS [#79759]
The swagger page using "POST /api/v2/docs upload a new Document" sends the "fields" parameter so that it's not recognized on the server side. All the parameters must be in one "multipart/form-data" content called fields.

Workaround​

Internal: see TFS [#79759]
As a workaround it's possible to add a comment into the json body which will force "swagger" to use one "multipart-/form-data" content without splitting it.

Example:
Creating a document and setting two properties, "Type" and "State".
Image

The resulting request will have a body similar to this, the body contains all properties in "fields".
Image

Without the workaround, the request will look like this. The properties are added as own form-data entry.
(and not inside a property called "fields")
Image