Call Studio - Red X Indicator – No 'Unskip' Option Available

[ln33147]

Hello,

Can anyone advise what the red X means in the screenshot below? There is no 'unskip' option available in the properties of this specific element.

Thanks in advance.

[bill.king1]

What type of node is it and what version of Call Studio are you using?

[ln33147]

Here it is a Decision element, there are many other Voice Elements as well showing the same red X.

The script was developed initially in Call Studio 11.6 but here I'm opening it on Call Studio 12.5 and I used to the same when doing upgrades with no issues.

[piyush aghera]

Do you have all the variables available that you are evaluating or using in that Decision element? Were you using any Custom Elements in 11.6 that are not migrated over to 12.5?

You may see error details in Call Studio Problems console of the Call Studio.

[bill.king1]

So if you drag a new Decision element to the workspace, you see it there too? Or this only happens with migrated projects?

Are you sure it is the native Decision element for instance, vs. something native?
Do you want to share the screenshots of the details of that decision element?

[janinegraves]

If you copy a Studio application from one Studio system to another and an
Element displays in RED, it usually means that Studio can’t find the definition of this
component.

The compiled java class or jar file was probably in the common directory on the original system, and
must be copied to your system:
C:/Cisco/CallStudio/eclipse/plugins/com.audiumcorp.studio.library.common_x.y.z./

A red X like that indicates that Call Studio can't find the code for the element.
This usually happens if the element was written using custom java.

Go back to your previous VXMLServer (before upgrading) and look in Cisco/CVP/VXMLServer/common/lib (and also common/classes).

If there's anything in VXMLServer/common/classes then it is CUSTOM CODE - and will all need to be copied intact (maintaining its full directory structure which might look like com/myCompanyName/myCode.class) to
C:/Cisco/CallStudio/eclipse/plugins/com.audiumcorp.studio.library.common/classes

And check the VXMLServer/common/lib directory for anything that isn't Cisco standard code (Cisco has elements.jar, sayitsmart.jar, etc). You'll be looking for something with a custom name or different Creation Date on it.

You'll need to copy custom code from common/lib/filename.jar to your Call Studio system and place it into
C:/Cisco/CallStudio/eclipse/plugins/com.audiumcorp.studio.library.common/lib

Then restart Call Studio and see if it fixes your issue.

If so, you'll copy the custom code to 2 more places:
C:/Cisco/CallStudio/eclipse/plugins/com.audiumcorp.studio.debug.runtime/AUDIUM_HOME/common/lib or classes (for use with Studio Debugger)
CVP/VXMLServer/common/lib or classes (for runtime)

HTH

[janinegraves]

BTW, be very careful copying the files/folders. There are a LOT of directories named 'common' and you have to follow the instructions above to the letter. Be sure it works for Call Studio to display the element before you try copying it to VXMLServer. 

Report back if you have problems or questions

Janine

[ln33147]

Thanks @janinegraves , I'll have a session with the customer tomorrow to check and will update the thread accordingly.