Unable to save categories when adding or updating users

The problems seems to be caused by checking the actionRequest for a parameter named assetCategoryNames.

if (actionRequest.getParameter("assetCategoryNames") == null ) {

The actionRequest only contains actionCategoryIds. But changing the assetCategoryNames to assetCategoryIds in the above code is not enough because there may be several actionCategoryId parameters for different vocabularies.

This step seems to be unnecessary because the actionRequestIds will already be in the ServiceContext. Removing the whole block appears to work correctly.

Although the Asset Tags are working, the code checking the ActionRequest for the assetTagNames also seems unnecessary because the Service Context should already have that information.

Sergio, can you please take a look when you get some time. It looks to me like the Service Context will always have the Asset Category Ids and Asset Category Tags so there doesn't seem to be a need to try and get them from the Action Request, which was what was failing for the Asset Categories.

Need to make sure the solution to LPS-29781 doesn't break the solution to LPS-25410.

Tested the steps described in LPS-25410 and verified that the proposed solution works for Categories and Tags.

Committed on:
Portal 6.2.x GIT ID: b56d564614fd5969f0ffad11e63c2ef03c95795e.

PASSED Manual Testing following the steps in the description.

Reproduced on:
Tomcat 7.0 + MySQL 5. Portal 6.1.20 EE GA2.

When I click save, the category can not be saved.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: 7963ca2938e9bcc0167ad92f9c98b90143edccf6.
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 9e92fd3ee490fb55da4898292881195ee5f8d5a4.

When I click save, I can save the category successfully.

Is this included in one of the EE patches/fixes?

Peter Mesotten Yes, this fix will be included in the upcoming fixpacks for 6.1 GA2