Hi everyone, hope all fine out there; I’m facing a quite tricky scenario, so I would like to ask you if it can be possible the udate of a value is getting lost between strategies (IRD 7.5, URS 7.5) using a call subroutine block, followed by a play&exit app that sends the interaction on a default return dn loaded with strategy.
So:
Interaction enters
A strategy with play&continue apps is used
A call subroutine block is used
A strategy treats the interaction, fills some Update values, then exits
The interaction turns back on main strategy
A play&exit is used
The strategy loaded on the default return is engaged
The “check if this udata = something” fails.
Can be?
Best regards.
Tried an attach data block to retrieve, in the final strategy, with an UDAta[‘’] function, but no way… the value arrives empty in the final strategy.
_I_I_009c028479ec9e92 [09:04] ASSIGN: DESTABB(LOCAL) <- STRING:
Really I don’t know how to look, since I use this method regularly, with no issue.
EDIT
InteractionData does not work too.
Can you post a screenshot of your IRD? Is the call still live when reached that point?
TServer logs for that call would be great
Here we are.
log files (URS/TServer): http://web.tiscali.it/modifiche/logs.zip
.zcf strat. files: http://web.tiscali.it/modifiche/strategies.zip
009c028479eccf9e - non working call.
009c028479eccf4c - working call
Both have a similar call flow:
-. Call enters in the main strategy (loaded on a genesys routing point)
-. Main strategy calls subroutine (OnCallAbandoned is declared, subroutine is not loaded on a routing point)
-. Subroutine exits (exit block in strategy)
-. Main stategy uses a play&exit GVP app to generate an eventabandoned
-. Call falls in the OnCallAbandoned declared strategy
-. Some UpdateData is written, then an exit block sends the call on the default destination (set in the Avaya Cm3 VDN)
-. Call arrives to the default dest. routing point in which a strategy is loaded
-. Strategy on default destination reads the udata written during the oncallabandoned strategy to decide if the call should be routed or dropped
-. The call reaches its destination (routed on vq/ag through a SelectDN, or dropped by a RouteCall on a Avaya VDN that executes a disconnection)
Usually all works fine, but in the non working case seems that when the eventabandoned is sent from inside the subroutine, with no turn back on the main strategy, causes a sistem inability to write the updatedata (or interactiondata too) on the oncallabandoned strategy, and when the call reaches the last strategy (on default return destination), the udata is empty.