Version: 2019.4.2

🏴‍ Known Issues

  • [#37342] Pam.Loader: support "vowel mutations" in the table names when importing a pco

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.
  • [#46798] inPoint.Admin: Error retrieving StorageSchemeSettings for archive unit ArchiveUnitID

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"
  • [#49516] inPoint.Core should not require IdentityAuthority web.config setting

add note to the known issues that the form templates needs to be regenerated and published by the ExchangeFormWizard tool at mail customers​

Internal: see OTRS [2019121801000051]
Internal: see TFS [#50022]
Old MAM emails with the old forms cannot be opened.

This problem is caused by the Windows Defender (or maybe other anti-virus software as well), which does not want to execute the obj.shell.run script.
As soon as the Windows Defender is stopped, the old MAMEE mails can be restored.

The old MAMEE form templates needs to be regenerated and published by the ExchangeFormWizard tool at mail customers having old MAMEE mails.

ElasticSearch 7.4.2 does not support radius queries for areas​

Internal: see TFS [#50168]
Due to a bug in ElasticSearch 7.4.2 it's not possible to search for an area by using a point and a radius.
In the search form it's called: "Areas intersecting with a radius" and "Areas intersecting within a radius".

Support DefaultValue for Dependent Lookups​

Internal: see OTRS [2019110801000081]
Internal: see TFS [#50361]
When you configure dependent lookups in the ExtraAttributes plugin you can now specify default values for new elements.
Now, also the filtering works when default values are selecting entries in the parent lookup.

NOTE: Having lookups with non distinct values is not supported any may not work as expected when using as default values.

ExtraAttributes DateEditorControl new format "Times" (MERGE 2019.4)​

ExtraAttributes DateEditorControl now with Dates & Times (MERGE 2019.4)​

Internal: see TFS [#50808]
The Date-Editor in the ExtraAttributes is now named "Date and Time" and has a new configuration: In "Editor Parameters" you can select the formats for the control (date, time or date and time)

ExtraAttributes DateEditorControl with Times - Documentation​

Internal: see TFS [#50808]
ExtraAttributes.2020.1.docx erstellen und Änderungen eingepflegt.

Selected Editor:


Editor settings:


Rendered Editor:


Office 2010 Open Excel files does not work if path>218 characters​

Internal: see OTRS [2020021801000085]

Description​

Internal: see TFS [#50847]
Only if AlternateMirrorForLongPathNames is set to true and Office 2010 is used!
It is not possible to open any Excel file from the client if the complete filepath exceeds 218.

Workaround​

Internal: see TFS [#50847]
Configure to use Webdav for the affected Excel fileextensions.

Elastic Search 7.4 does not start if used memory is multiple of 8GB​

Internal: see TFS [#51710]
If the memory of the machine is 16 GB or Elasticsearch is configured to use 8 GB using the "Xmx" setting it's possible that the service does not start with the message  "Exception in thread "main" java.lang.OutOfMemoryError: Direct buffer memory".

To avoid this, set the direct buffer memory manually as advised in the fulltext search troubleshooting guide.

  • [#52600] HS.inPoint.Plugins 2020.1.3.1.nupkg has wrong reference to HS.Infragistic.resources (Merge 2020.1)

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]

Pam.PamArgumentException: The unicode string value for parameter '@WEBDAVNAME' is longer than allowed (allowed: 78, actual: 79)! (MERGE 2020.3)​

Internal: see OTRS [2020111301000077]

Description​

Internal: see TFS [#54374]
The mail archive ('inPoint CSE' or inPoint CSD) cannot archive mails from folders where the name is longer than 78 characters.
The error includes this message:
"Pam.PamArgumentException: The unicode string value for parameter '@WEBDAVNAME' is longer than allowed (allowed: 78, actual: 79)!"

Workaround​

Internal: see TFS [#54374]
Ensure that in web.config (default: C:\Program Files (x86)\H&S Heilig und Schubert Software AG\Pam.Storage\Web\web.config) the setting "ReinitializeTempTablesOnStartup" is configured to "false". (the default value).

Execute this statement to make the server believe that the column is larger (replace '_TABLE_OWNER' with the correct database scheme):
update _TABLE_OWNER_.PAM_TMP_ALL_TAB_COLUMNS
  set DATA_PRECISION = 255, DATA_LENGTH = 255
where COLUMN_NAME = 'WEBDAVNAME'
  and TABLE_NAME like '%_MAIL_DESC'
  and (DATA_PRECISION < 255 OR DATA_LENGTH < 255)
Restart Pam.Web afterwards!

Execute these steps, if upgrading to a newer version until its fixed.