Version: 2020.3.2

🏴‍ Known Issues

Client freeze, when switching between mysite and globalsite if doclist is sorted and paging is used​

Description​

Internal: see TFS [#40038]

If an folder is selected, which have paging enabled and is sorted by any column, and then the user switches to the mysite or the globalsite it can happend that the client freezes and stops working!

Workaround​

Internal: see TFS [#40038]
If the Client was freezed, restart it!
Try to avoid switching between my and global site when paging is enabled on the currently selected folder. Select a different folder first (which does not have paging enabled) and then change the site.

inPoint.SetupCommon: installation is not working if "service pw" contains special characters​

Internal: see OTRS [2020081301000038]

Description​

Internal: see TFS [#42012]
The characters ";" and ":" cannot be used for the service password.

Workaround​

Internal: see TFS [#42012]
Please install the setup with an empty service user-password and change the password manually after the installation has finished successful.

Unpin inPoint folders from windows explorer "Quick access" is not possible​

Internal: see OTRS [2019102901000033]

Description​

Internal: see TFS [#49496]
If any inPoint folder is D&D into the windows "Quick access", it is automatically pinned.
Then this folder cannot be unpinned, because the contextmenu entry for "Unpin from Quick access" is missing on all virtual inPoint folders. 
This is a Windows Bug, because this happens also for some other applications!

Workaround​

Internal: see TFS [#49496]
  1. Add any windows explorer folder to the pinned "Quick access".
  2. Select "Quick access"
  3. On the right side: "Frequent folders", hold down CTRL and select all inPoint folders and this one additionally added windows folder
  4. Right click on the windows folder and select "Unpin from Quick access"
All selected inPoint folders are "unpinned"

Axon.ivy Engine Cockpit AD Ldap Browser Expand Node does sometimes not work​

Description​

Internal: see TFS [#53718]
In the Axon.ivy Version 8.0.9 Engine Cockpit Security System "Microsoft Active Directory", the "Ldap Browser" does have an issue that expanding Nodes does not work.
"Error, An unexpected error has occured: javax.el.ELException: java.lang.NullPointerException" is shown.

Workaround​

Internal: see TFS [#53718]
Use any other Ldap Browser Application (e.g. ADExplorer), search for the Context you want to import and then Copy&Paste the Ldap Path into the field in Axon.ivy.

AD sync: Inconsistency may occur between the inPoint user name and the AD user name, because of local security authority (LSA) cache update delay in Windows​

Description​

Internal: see TFS [#53804]
When the user name has been changed on a domain controller, the AD synchronization is not recognizing this change immediately.
In this scenario, the AD synchronization may return the old user name instead of the new user name.

The local security authority (LSA) caches the mapping between the SID and the user name in a local cache on the domain member computer. The cached user name isn't synchronized with domain controllers. The LSA on the domain member computer first queries the local SID cache. If an existing mapping is already in the local SID cache, the LSA returns the cached user name information instead of querying the domain controllers. This behavior is by design and is intended to improve performance.

The cache entries do time out, however chances are that recurring queries by applications keep the existing cache entry alive for the maximum lifetime of the cache entry.

Workaround​

Internal: see TFS [#53804]

The upgrade from 2020.2 fresh install to 2020.x shows a warning dialog, asking the user to manually execute the 001_00_UpdateLASTMODIFIEDIDandNAME.ps1 PowerShell script​

Description​

Internal: see TFS [#54102]
The upgrade from 2020.2 fresh install to 2020.x shows a warning dialog, asking the user to manually execute the 001_00_UpdateLASTMODIFIEDIDandNAME.ps1 PowerShell script.
This script is mainly setting the user id in the following fields 'DOCCREATORID','DOCLASTMODIFIEDID', 'CONCREATORID','CONLASTMODIFIEDID', 'EXTLASTMODIFIEDID' in the archive units for all tenants. These fields are already created and correctly filled in the 2020.2 version. There is no reason to execute the 001_00_UpdateLASTMODIFIEDIDandNAME.ps1 PowerShell script in this case.
This warning dialog will be not displayed anymore in further updates.

Workaround​

Internal: see TFS [#54102]
Ignore the first warning dialog, asking the user to manually execute the 001_00_UpdateLASTMODIFIEDIDandNAME.ps1 PowerShell script when upgrading from 2020.2 fresh install to 2020.x.
This warning dialog will be not displayed anymore in further updates.