We have same problem on our iOS channel that is routing through a mid-sourcing sever. Any help would be greatly appriciated

Hi Sachin, The offer status is a logical thing and it should correspond to your offer lifecycle. The names are pretty much self-explanatory. To integrate offers you can use ether javascript: https://experienceleague.adobe.com/docs/campaign-classic/using/managing-offers/unitary-interactions/integration-via-javascript--client-side-.html?lang=en#html-mode Or SOAP https://experienceleague.adobe.com/docs/campaign-classic/using/managing-offers/unitary-interactions/integration-via-soap--server-si...

You mean how to set existing statuses? That will depend on your offer engine set up and your offer proposition lifecycle. You might not even need all of them. In a nutshell, if you wish to change status of existing offer, you can always do it via SOAP function, but you will need something to call it. You also can use some technicall wotkflow to do the same. Why do you need to use all of existing statuses?

Hi Sachin, This is simple. Find the schema where the enumeration is defined. Extend the schema and add enumeration with the same name to it. Add extra statuses and make sure the status id is not overlapping with existing one. Restart the Adobe client and you should be able to see new statuses.

Hi supratim320, thanks for the response. Unfortunately, that is not the answer I was looking for. I'm aware I can specify keys, but they must be exact keys. In the case of the sequence number, that does not work, because the previous sequence number is unknown. Instead, the record should be updated if new sequence number is greater than previous, so the request should look something like this: xtk.session.WriteCollection( ) Obviously, that is not the right syntax, so I'm looking for a corre...