PIM 6.1.5 – Release notes

The new release of PIM improves the stability, compatibility and security of your solution, and is recommended for all installations.

If you upgrade from a version before PIM 6.1.4 follow the manual steps need for 6.1.4: PIM 6.1.4 Release notes

Bugfixes

PIM-1575 Issue with filter.PIPFilter untouches attributes before everything has been saved

The filter filter.PIPFilter would untouch attributes before we got an OK from PIP. This could cause issues (depending on configuration) when you get an error from PIP and then try to send again it would send nothing and be unclear that this happened. Now it will instead only untouch the attributes after we got an OK from PIP so you can resend after an error from PIP. Issue resolved.

PIM-1581 Internal Server Error during session timeout

PIM 6.1.4 introduced an issue where you could get an internal server error in the web when a session timeout. Issue resolved.

PIM-1587 Missing DN for suser in logout audit log

PIM 6.1.4 introduced an issue where the DN was missing for the suser in the logout audit logs. Issue resolved.

PIM-1596 Issue with text wrapping for check boxes, static string and radio buttons

Different display scaling could cause the check boxes, static strings and radio buttons to wrap which could make it unreadable. These controls will now set the width equal to the length if set or the length of the content if not set to prevent the wrapping to happen. Issue resolved.

PIM-1599 Control se.nordicedge.controls.password.ManagePasswordCC is not validating “showed” password

The validation would always be done for the hidden password and if you showed the password and made changes then it would still use the old hidden value. Now the version that is chosen will be validated. Issue resolved.

PIM-1600 Control se.nordicedge.controls.date.DateGeneralizedTime end up in bad state

The control could end up in a bad state after an error from PIP which would then display a java exception message when retrying to resend the data to PIP. Issue resoled.

Improvements

Upgrade tomcat to latest 9.0.x version

Upgraded tomcat from version 9.0.100 to to 9.0.115.

Upgrade JRE to latest 17.0.x version

Upgraded the java runtime environment (JRE) from version 17.0.3 to 17.0.18.