Workflow Problem When Adding a Condition Criteria (Doc ID 747674.1)

Last updated on AUGUST 17, 2016

Applies to:

Siebel Workflow - Version 8.0.0.2 SIA [20412] and later
Information in this document applies to any platform.
** Checked for relevance on 28 March 2012**
** Checked for relevance on 16 March 2015**



Symptoms

In Workflow Editor, when trying to create a new condition in a connector an error occurs: Error processing your request. Please consult a Siebel administrator.

In the logs the following error messages and codes may be found:

SBL-DEV-61159: No valid Expression Builder could be found for the field Process Name on business component Repository Workflow Process

SBL-DEV-62300: A condition criteria that is based on a process property has an empty value for the Property Name field.

SBL-DAT-00225: The value entered in field Operation of buscomp Repository WF Branch Criteria does not match any value in the bounded pick list Repostiory WF Branch Criteria Include.

This issue is reproduced in 8.0.0.2 SEA/SIA and beyond.

These are the steps to reproduce.

1) Create a new workflow process:

Start > Decision Point > End step

2) Create a new process property AAA.

3) On the connector from Decision Point to End step, right click to compose condition criteria:

Compare To: Process Property
Operation: None Can Match or None Can Match (Ignore Case)
Object: AAA
Values: AAA (Click New button to add the value)

4) Click Add button and then OK button and obtain error message:

Error processing your request. Please consult a Siebel administrator

5) Try to save and close the workflow process and then edit it again.

6) Try to Select the select the condition created. Choose all again:

Compare To: Process Property
Operation: None Can Match or None Can Match (Ignore Case)
Object: AAA
Values: AAA (Click New button to add the value)

7) Click on Update this time (since the condition was already created).

8) Click on OK and obtain error message:

Error processing your request. Please consult a Siebel administrator

Note1: This is not repro on Sample, so it must be tested in an 8.0.0.2 or 8.0.0.3 SEA/SIA server environment.

Note2: The symptoms seems to be similar to the one described in: "Workflow Editor condition step (Doc ID 731247.1)". However in this case the workaround (close editor, save and then try to edit the condition in the connector again) will not work.

Note3: The workaround provided in Doc ID 731247.1 may work when the condition used is ‘One Must Match’ and ‘All Must Match’. But it does not work when other conditions are used.

Cause

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