Group element Issue while migrating call studion project from version 8 to 10.5

[Vikash Chandra]

Hi Team,

Recently I have encountered an issue with Group Elements When I open the code which has been developed in 8.0 Call Studio in 10.5 Call Studio, all the connections which are present in Group Elements are missing ..

So I have added all the connections, save it & trying to validate it ,Even after that all the connections are getting disconnected & Validate is failing.

What can be a solution for this ?

It would be great If I can get some insight about the solution.

Thanks,

[janinegraves]

I don't have Studio 8.0 but I do have 9.0 and I was able to import the

app into Studio 11 with the Grouped elements not causing any problems.

Can you be more specific about what connections are missing? Are all

the elements' exit states inside the Group missing?

The big differences now are that

1) if you had Page Entry elements with the same name as another element

(which used to be allowed) it causes problems. I guess now Page Entry

and Page Connector elements are considered 'elements'

2) Subdialog Return (to go back to ICM) became the CVP Subdialog Return

element (I think that was before 8.0 though). And a new (different)

element named Subdialog Return was added but not to be used to return to

ICM - very unfortunate naming.

3) I assume that you're aware that elements in a Group that must connect

to something on the outside of the group will display inside the group

without their exit states, right?

[Vikash Chandra]

Hi Janine,

Thanks for your response. As I said we are migrating call studio application from version 8 to 10.5. We have already applied ES 5, 6 and 7 patches for call studio 10.5.

We are not facing issue with all group element but few. For example in one of application we are grouping 6 custom decision element that is the first group element and all exit state are going to another group element where we are grouping around 15 audio elements. In this first group element does not having any issue but in second group element all exit connection to audio element are disconnected while migrating. Even we manually connects all exit state for second group element and saving the application does not reflect. When we validate the application it is again showing "Orphan element" error message. After saving application when we close the project and open it then again all exit state are showing disconnected.

We are facing this issue with multiple application with group element of different elements like group of mix element (action and decision element). One similarity I observed that when application is having 2 consecutive group element in call flow then first group element does not have any issue but second group element showing disconnection.

Regards,

Vikash

[janinegraves]

I can't help verify (as I don't have studio 8 anymore) and I'm not with

Cisco.

But, as a workaround, if this only occurs when you have 2 Groups

connected, then in Studio 8 connect the first Group to an AppModifier

element (which requires no config'n), and then connect the AppModifier

element to the 2nd Group. Perhaps then it would import correctly.

In either case, this sounds like a bug.