Page 1 of 1

RequstId in OnRoutingStateChanged

Posted: 02 Dec 2018 14:41
by ssteiner
As per the object model, OnRoutingStateChanged contains a requestId string which is used to correlate requests and responses.

However, the object model of SetRoutesRequest, SetOverflowRoutesrequest and SetForwardRoutesRequest does not contain such a requestId parameter.

So, what's the point of requestId in OnRoutingStateChanged? I hope it's an oversight in the Set* models as this was a very useful thing that I was making use of quite frequently on OTMS.

Re: RequstId in OnRoutingStateChanged

Posted: 03 Dec 2018 10:45
by yblanchard
It's a documentation bug(not cleaned from OT): requestId is not supported on O2G. There is no secured mean to make a correlation between the CMIS event received from OXE and a previous request.

==> to be removed from the documentation

Re: RequstId in OnRoutingStateChanged

Posted: 04 Dec 2018 09:21
by ssteiner
Snif… would have made my life a LOT easier having that.

Re: RequstId in OnRoutingStateChanged

Posted: 05 Dec 2018 10:32
by ssteiner
could it be that this feature is also broken on OTMS? I have a scenario where I could use it, yet, despite sending a requestId for every of my routing request, nothing is ever returned in OnRoutingStateChanged

Re: RequstId in OnRoutingStateChanged

Posted: 06 Dec 2018 04:01
by yblanchard
a case should be opened on OTMS to determine if this feature is really broken on OTMS or if it's a local issue