My Oracle Support Banner

Users Are Not Filtered in the Android Unifier App When Workflow Assigness Set Dynamic Assignees (Doc ID 2520810.1)

Last updated on SEPTEMBER 09, 2019

Applies to:

Primavera Unifier - Version 18.8.3.0 to 18.8.8.0 [Release 18.8]
Primavera Unifier Cloud Service - Version 18.8.3.0 to 19.2 [Release 18.8 to 19.2]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR

In any given workflow schema, for any given step where the Assignees setting is defined as; 1) dynamic, 'match step <stepname>', 2) the Step Revisiting setting is defined as Include only previous action takers, and 3) the 'stepname' for match step has more than one assignee, the following occurs: When the record is sent to the next step in the workflow, the list of assignees are not filtered to the previous action taker; instead all users are listed in the Android app (the user is correctly filtered through the web application).

EXPECTED BEHAVIOR

The task assign should be auto populated dynamically for the match step creation user.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.