PAM -CM-0179: managed is not a valid parameter.

Document ID : KB000116261
Last Modified Date : 01/02/2019
Show Technical Document Details
While trying to use multiple filters under Discovery Jobs, CA PAM fails with an error "PAM -CM-0179: managed is not a valid parameter." You cannot use the "managed" filter with any other filter. 
PAM 3.2
The problem is with DiscoveredAccountService when building the JPA queries.
The column 'managed' on persistent instance 'DiscoveredAccount' is a transient column and not a persistent one. So, the column should be avoided when building the JPA Query which otherwise will lead to IllegalArgumentException thus leading to 400 BAD_REQUEST.
DiscoveredAccountService only handled the case of filterColumn being specified as 'managed'. Thus it only works when managed specified alone. When its included along with other filters, it's leading to a situation where 'managed' column is included in Query thus 400 BAD_REQUEST. 
Fix has been applied on PAM 3.2.3 and master PAM 3.3 releases. 
Downloadable PAM 3.3 link will be provided after the release date. 

PAM 3.2.3 downloadable link: