Call Studio, Skipped element expected behavior

[agaliano]

Hello all,

We have encountered applications running on 11.6 that are using an audio element to set session values, and then they are marked as 'skipped' in call studio.
The call servers are no honoring the 'skipped' tags it appears, as the session values are still being set according to the element configuration.

The applications weren't coded with an application modifier element to set session values, which is interesting, but this skipped behavior is even more strange as 'it shouldn't work'.

Has anyone encountered this behavior?

[janinegraves · Accepted solution]

Hi Audra,

Some people use 'skipped' elements to set SessionData, instead of using an App Modifier or some other innocuous element for its Data tab. Not my favorite, but...

When you skip an element, it becomes a temporary Data tab - where it (you) can assign variables and values. Even though the element won't execute its real function (like Audio), it'll still create variables.

That is how the skipped function has always been, and how it was intended to execute.
The idea is that if you have an element (like a DB or WebSvc) that isn't currently functional, you can 'skip and exit as done' and use its Data tab to 'simulate' the Element or Session Data that the 'unskipped' element would create...so you can test the remainder of the program.

Hope that helps.

[agaliano · Accepted solution]

Thanks for the feedback Janine.