nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

REST and tasks with candidateOrAssigned parameter

martin_grunberg

Hi,

The user guide states that it should be possible to use candidateOrAssigned parameter with tasks. However the the parameter is not applied-all tasks are returned.

For example runtime/tasks?candidateOrAssigned=kermit yields the same results as runtime/tasks?candidateOrAssigned=fozzy.
Looking at the code I cannot see the candidateOrAssigned parameter option in TaskCollectionResource.getTasks()

Am I missing something or is it a bug?

Br.
Martin

Find more posts tagged with

Comments

martin_grofcik

Hi Martin,

Which version do you use?

I have found

<br>&hellip;<br>&nbsp;&nbsp;&nbsp; if(names.contains("candidateOrAssigned")) {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; request.setCandidateOrAssigned(getQueryParameter("candidateOrAssigned", query));<br>&nbsp;&nbsp;&nbsp; }<br>&hellip;<br>

in 5.16 (I am using snapshot version so may be I am missing something)

Regards
Martin

martin_grunberg

I 'm using 5.15.1.
It looks like it is fixed in 5.17 that is in repo. So case closed

Martin