v5.6 breaks this query

I have a query in a content view which looks like this:

(ecm:mixinType = 'HiddenInNavigation' AND ecm:isCheckedInVersion = 0 AND ecm:currentLifeCycleState != 'deleted') AND ecm:parentId=? AND (ecm:primaryType =? OR ecm:currentLifeCycleState ='Pause')

with query parameters:

“#{currentDocument.id}” “#{currentDocument.currentLifeCycleState}”

Which worked fine in v5.5. Yeah I know its 'fragile' to use the currentLifeCycleState of a document as a search parameter of ecm:primaryType and I know the document types need coordinated with the lifecycle state. However this query did work in v5.5 and as the parent document moved through the lifecycle it would show only the document type which had the same name as the lifecycle state.

I need to know if this is a bug or a change in the underlying code which will not be changed and therefore I need to find a different way to only display a child document based on the parent's lifecycle.

Here is the error I get!

0 votes

1 answers

923 views

ANSWER



I found data type inconsistency with a Java action I have written. Fixing that fixed the problem.

0 votes