This content has been marked as final. Show 2 replies
Actually the first Siebel Operation step is part of a solution which is designed to avoid the duplicate transaction.
Due to one unique index the first SO will fail, then in the second SO I insert the same record with status as Error. It means only 1 columns value will change.
But it seems the context of the first BC still persists.
I tried below options today, but no use.
1) After 1st SO, used SO without passing any search spec, so expect to refresh the BC with null query.But instead of triggering null query the SQL generated has all the values used in first SO, in WHERE clause. I don't from from where these values are being taken.
2) Created new WF, which consists only 1 SO to insert the second record. And called it from current workflow, passing all the values through process properties. But still the values are being used in this sub process are old values (same context).
Is there any other way to fix this.