User Key's are used to uniquely identify a record while you insert/update/delete records using Integration Objects.
We can ignore defining User Key's if w are using Query/Query Page operations.
The idea of ignoring user key's to create duplicate records could be misleading but we might have some requirements like below.
Example: Create a Service Request record in Siebel from an external application where the user submits the Error description in a form and hits submit.
No matter how many times the user puts the same description and hits submit, it should create multiple Service Requests in Siebel.
In other way, all Insert operations should never error out, but can create multiple duplicate records.
Solution:
Create an Integration Component User key with the Integration Component Field as "Id".
"Id" is a system field and the value will be generated by siebel irrespective of whatever value you send as input.
instead of sending "NULL" value to the "Id" Integration component field, we can map the Workflow Process Instance Id property to this "Id" field.
Now Siebel will always create records without erroring out.
We can ignore defining User Key's if w are using Query/Query Page operations.
The idea of ignoring user key's to create duplicate records could be misleading but we might have some requirements like below.
Example: Create a Service Request record in Siebel from an external application where the user submits the Error description in a form and hits submit.
No matter how many times the user puts the same description and hits submit, it should create multiple Service Requests in Siebel.
In other way, all Insert operations should never error out, but can create multiple duplicate records.
Solution:
Create an Integration Component User key with the Integration Component Field as "Id".
"Id" is a system field and the value will be generated by siebel irrespective of whatever value you send as input.
instead of sending "NULL" value to the "Id" Integration component field, we can map the Workflow Process Instance Id property to this "Id" field.
Now Siebel will always create records without erroring out.
