Siebel Workflow: Siebel Operation Step Not Running Query On Null Attributes
(Doc ID 2441816.1)
Last updated on AUGUST 30, 2018
Applies to:Siebel CRM - Version 220.127.116.11 SIA and later
Information in this document applies to any platform.
We have used siebel operation step in one workflow process to query based on process property. We use Siebel Operation Query step with one field in business component and Value as process property in 'Field Input Arguments' tab.
Field Input Arguments:
Field Name: BuscompFieldName
Type: Process Property
Property Name: ProcessPropertyName
While executing query using this workflow process its not returning proper results where process property value is null (Default String is blank). For example, here is extracted from the workflow process input:
If we are querying for some field value as null then we expect to see the following in SQL where clause:
(BuscompFieldNameColumnName IS NULL)
But Siebel Operation does not have it and is ignoring that field. The improper query result is all records in the queried business component table are returned.
However, when the process property value is not null (Default String is not blank) and has some value:
then it works correctly and we see the column in SQL where clause with bind variable substitution for 123.
We are aware if we use 'Search Spec Input Arguments' tab instead with a Search Specification for blank Default String for the process property, i.e., ProcessPropertyName0*, it works correctly and we see (BuscompFieldNameColumnName IS NULL) in SQL where clause for returning correct results:
Search Spec Input Arguments
Expression Business Component: business component name
Filter Business Component: business component name
Search Specification: "[BuscompFieldName] = '"+[&ProcessPropertyName]+"'"
Currently we are using 'Field Input Arguments' tab and not 'Search Spec Input Arguments' tab. To use 'Search Spec Input Arguments' tab it means we need to revisit design of all the workflow processes to change to use 'Search Spec Input Arguments' tab.
How to configure a Siebel Operation step to query on null attributes?
We are unable to understand the behavior and constantly asking that is it the expected behavior or this is related to some bug as this behavior is not documented anywhere.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document