BP Picker in 'Additional conditions to filter assignees' Setting Causing Generic System Alert To Be Thrown At Runtime
Last updated on APRIL 05, 2017
Applies to:Primavera Unifier - Version 18.104.22.168 to 22.214.171.124 [Release 16.2]
Primavera Unifier Cloud Service - Version 126.96.36.199 to 188.8.131.52 [Release 16.2]
Information in this document applies to any platform.
On Unifier : version 184.108.40.206
Expected Result: When the setting for 'Additional conditions to filter assignees' in the workflow BP workflow schema contains a BP Picker it should be working as expected at run-time to filter out a list of users to assign the record to.
Actual Result: At run-time the following Unifier Notification is being returned: The system could not process your request. Logging in again may help in some cases. Contact your System Administrator if you are still having problems.
Excerpt written to the Unifier log files:
...[[ACTIVE] ExecuteThread: '2' for queue:
'weblogic.kernel.Default (self-tuning)'] ERROR Target.Exception
~ unifier:/studio/workflow/api/task/ace throws an exception at file:///studio/workflow/api.xml:579: ~
file:///studio/workflow/api.xml:579: java.sql.SQLSyntaxErrorException: ORA-01722: invalid number at com.skire.form.taskdefs.QueryUtilTask.execute(QueryUtilTask.java:214)
To reproduce, define the conditions for the setting in the workflow schema so that it contains a BP Picker type Data Element and then route the record accordingly at run-time. Note the Unifier Notification that is returned when the user clicks on the 'Send' button.
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 hundreds of Community platforms