Page 1 of 1

selected on destinations for forwardRoutes

Posted: 02 Dec 2018 11:42
by ssteiner
It seems there's some discrepancy between the documentation on the sandbox (https://o2g-shared-sandbox.ale-aapp.com ... ml#mth0096) and what is being returned in OnRoutingStateChanged.

Here's an example where 1033 programs an immediate forward to 1025:

{
"eventName": "OnRoutingStateChanged",
"loginName": "oxe1033",
"routingState": {
"activableProfiles": [],
"presentationRoutes": [{
"destinations": [{
"type": "OFFICE",
"selected": true
}]
}],
"forwardRoutes": [{
"destinations": [{
"type": "NUMBER",
"number": "1025"
}]
}],
"overflowRoutes": []
}
}

As per the example in the documentation (link above), for an active forward, the destination should have the selected flag set to true. However, as you can see by the actual example, there's no selected attribute. Looking at the definition of the Destination element, there's no selected either.

So.. what is wrong now.. the object description or the example?

On OTMS, the selected property is there and to set a destination, selected has to be set to true.

Re: selected on destinations for forwardRoutes

Posted: 03 Dec 2018 10:43
by yblanchard
The "selected" attribute is only used in O2G in one context: to activate/deactivate the remote Extension in the presentationRoute.
So this attribute should be removed in the forwardRoute example

==> DOCUMENTATION TO BE FIXED