CXDev Toolbox Questions and Comments

The new Windows-store based CXDev Toolbox (v3) has launched. We recommend upgrading to the new version. See for installation details. For help with the new toolbox (v3), please post your questions on this new thread:

If you are experiencing technical issues with the legacy CXDev Toolbox, encounter a bug, or have a feature suggestion, please let us know by posting a comment to this discussion thread.


Hi Andy/Jack,

First of all, great work which will help budding RNT Developers like me to scale new heights. I referred this site to 22 of my RNT CX colleagues and they will also share their feedback soon.

Starting with me, I downloaded this in my Work environment but since we access RNT via Proxy, I am unable to connect to my site WSDL. Anywhere I need to bypass/enter Proxy details?


Hi Suresh,

There isn't an application specific proxy for this tool. You should be able to specify your proxy in your Internet Options (accessed either through IE or though Settings - and it will be applied to your connection through the toolkit. Also make sure that you're trying to connect to the SOAP endpoint and not the WSDL. The URL should be similar to: https://[site][interface].cfg/services/soap if you have ?wsdl on the end of the URL it won't work.

Thanks for trying out the app, please let us know of any issues you encounter or features you'd like to see added.


Hi Jack,

I am also facing the same issue, i am getting Login Fail error, I have tested the same login on another machine with in the same network able to login CXDev with my credentials. But I am not ale to in the my machine. I have tested with and with out Proxy.
I have used site as https://[site][interface].cfg/services/soap and cx console credentials.

Wow, this looks like a nifty tool. I've thought about writing something like this myself. I'd use yours but I think connecting a closed source tool to our API would be a pretty insane idea. Let me know if you ever release the source. I might contribute. As is, this is far too risky to use.

Hi Charlie,
Thanks for the feedback. We are going to keep the core tool's source private. In the future we plan to release an SDK for custom extensibility as a mechanism for community involvement but that doesn't really address your concern. You want to be certain that by entering your U/P and Endpoint into the tool your credentials won't be hijacked and used later to access loads of personal information.

The issue comes down to trust. Any software you install on your computer is going to have some sort of risk for abuse. Fiddler is a great example of this. It can decrypt HTTPS traffic which can lead to all sorts of bad things, yet people install it without access to the code because it has a long history, a credible developer, and good reports from users which has lead to a position of trust. Browser plugins such as AdBlock are another example. These plugins have incredible access to your web browser interactions, but they are trusted because of similar reasons.

Our tool is also at the mercy of user trust. You have to decide that you trust our Company and the Software, and that is a personal decision. Certain factors can help; signed code being one of them. We are in the process of getting an Authenticode compatible Code Signing Certificate. With this in place we will start gaining reputation with the Windows SmartScreen system (and eventually the install warnings will go away). Even without the code cert our app is still part of that system and being passively evaluated every time it is installed.

Another factor is that the tool is developed by a credible business. and the CXDev Toolbox ( are owned and operated by 45 North Solutions, a consulting organization of RightNow CX expert engineers and architects out of Bozeman Montana. Our business is completely dependent upon our reputation; we are very enthusiastic about the tool and associate our business name to it whenever possible.

Because this is such a small community, many of the users of the Toolbox know Ben, Jack or myself personally from our work at RightNow Technologies, Oracle, or subsequently through 45 North Solutions. This personal connection helps strengthen the trust for these users. That doesn't help your trust decision necessarily, but you may know someone who knows us and will vouch for our integrity.

Additionally, we wrote the Toolbox as a Windows Application instead of a web app because security was important. With the Windows Application there is a direct connection between the Toolbox and your CX site. There is no web app proxying calls. You can open up a HTTP Debugger/Proxy (i.e. Fiddler) and see every network request sent through the tool. No network calls are made except directly to your CX site. Note: In the future we will be adding some use counters to help justify our time investment, but these will be opt-in and easily distinguishable.

The purpose of this long reply is not to necessarily convince you that you should trust us. Instead I think this is a good topic to discuss as too many people install tools without knowing the risks for malicious activity (ie, Fiddler, Browser plugins, etc). Open source code helps (if you are an engineer), but often it comes down to a trust decision. I've discussed some of the factors I consider when trusting an application and would be curious to know the evaluation process that others use.

Thanks for checking it out and thanks again for the feedback.

This is a great initiative! Those are indeed the tools that lots of people have written in a quick and dirty way to get something done, and it is great to see that you guys bundle this in a nice package!
I would consider the upload of Cats / Prods / Dispositions to be part of the tool as this is always a hassle with new sites and seems like a great fit for this package.
Keep up the good work!


Is this coming through now? Messages I post simply do not come through on this site..

Anyway, great initiative. It is good to see that there is a common place with information and now even a real useful app!
Having the ability to upload prod / cats / dispositions from a csv would be a great one too!

thanks for all the effort,

This spam checker is seriously uncool. I just posted a message wondering why suddenly my friday post is here as well, suggesting you can remove any post of mine to keep the thread clean. That posted nicely, then I edited to remove a stupid spelling mistake and then I got the message that it was under review.

Maybe the spamchecker detects a very similar message in a short time when you edit it and then marks it for review. that is what happened to my previous message as well..

Hi Bastiaan,
Thanks for the feedback. I like the idea of a prod/cat/disposition migrator. We'll add it to the list and try to get it out there. As for the spam checker, we are working on make it a bit less aggressive.


+1 for prod/cat migration.

A login field check on account importer would also be swell -- to avoid creating dupes on import (yes, I realize this makes me lazy ;)).


Hi team,

First of all congrats on the launch of this tool really appreciable.

Second thing am not able to log in into this tool. What will be the URL username and Password.

Am giving the URL as the one what we have enter during the installation of RNT console, Username password is My account Username and Password.

Thanks and Regards
Gurpreet Singh
| Oracle RightNow Cloud CX Techno – Functional Consultant |Mob: +91 9958895608 |

Once downloaded, will the toolkit automatically update with new utilities (introduced in future) next time (internet is ON) ?

Could anyone please provide environment requirements to run this tool? My computer is windows server R2, but its layout is overlap somehow.

Thanks in advance,

Make sure your font scaling is at 100%. We've seen some problems when it's set higher

Hi Andy, thanks for your response. My OS font scaling is at 100%. I think it may be language supporting problem as my OS language is simple Chinese (zh-cn). I installed anther Windows 7 OS which language was English in virtual machine. It was OK. So I want to make sure whether it is language setting problem. Thanks.

Hi andy,
I have created a stub file for one of my site using the CXDev tool. And I have followed the steps that you mentioned in the article to get the potential matches while coding. So for me, it was not working. Then I went through the the stub file. There I find a class named 'Interface'. Since 'Interface' is a keyword, I think we cannot declare a class like 'Class Interface'. So I just removed that particular class from the stub file. Then I got everything working fine. I dont know whether it is a bug or something. I just want to put this solution for the developers who use the stub stuff. Thank You.

Hi Aneesh. What version are you seeing this on?
I did some tests on the sites I have available to me and I don't see a class named "Interface".

I do see a class named 'InterfaceValue' which wouldn't cause the problem you described.

The CXDev Toolbox version is

Sorry. I meant which OSC site version? Does the site happen to have a Custom Object named "Interface"?

CX Cloud Service February 2014
RightNow Customer Portal 3.2.1

I just checked it with a latest OSC site. Then I cannot see that class. This time the stub file is fine.

I just installed the CXDev tools, in the hope that i can use it to create a stub for my eclipse IDE.

My problem is that the password field is not visible, so I can't authenticate. I am guessing that my problem is because I use 'medium' (125%) sized fonts in Windows 7, so I will log out and try again, but wanted to pass along the feedback.

Mark Ahrens
Keysight Technologies



But thanks to markahrens, it worked when I changed from the default 125% to the "Smaller" 100% setting. I guess I'll just get more use out of my reading glasses...

I deleted the Country ID = 1 US. After that, I can not import new accounts. Is this a problem or I did something wrong?

Thank you for creating this free tool.

It is not a game killer for me, but I have been having issues connecting to Service Cloud interfaces that are on versions equal to or greater than May 2016.

I have other tools that I can use to play with ROQL, but I am kind of bummed to have to uninstall the CX Dev Toolbox. Are there any things I can do to fix the tool so that it can be used with these newer versions of Service Cloud?

Kind Regards,

Hi Rajan,
I did a quick test on a February 2017 (Build 258, CP 346) SP1 site and it connected without issue. I did a simple tabular ROQL query of 'Select * from Account' and it returned the expected results.

I haven't heard of any other issues, so perhaps it is a set-up issue with your site or network?



The error I am getting is "Login Failed" with the error saying "Failed to log in. Please verify your information and try again".

I thought I was testing this against February 2017, but I was mistaken.

I have tested with an upgrade and test interface (both May 2016) that use the same credentials as the production interface (May 2015). I can connect to the main interface but not the test and upgrade interfaces.

I have also tested this on a few different networks without any changes in results.

I can connect to all of these via the REST API using the same credentials.

Is it possible that this issue might be unique to version May 2016? I have been trying to get another test site with February 2017, but haven't been that successful.

Not sure if it is helpful, but I am using version of the CX Dev Toolbox.

I tested on a client site (a TST site actually) that uses May 2016 (Build 254) SP6. I was able to connect without issue and run queries. I'm using version 2.1 ( but I don't remember the older versions having any issues with May 16.

Are you able to retrieve the WSDL for the site? Are you able to generate a client and make SOAP calls? All the toolbox is doing is connecting to the SOAP API and doing fancy stuff.

I am not too familiar with the SOAP API, but I followed the first link specified in the SOAP documentation for the WSDL Retrieval (

I can access the this on all 3 interfaces; I ran the WSDL's for 2 of the sites through a diff checker. The results can be found here:

The major thing that I could see standing out was that the WSDL version is slightly newer on the newer interfaces. Otherwise there are a few differences between the WDSL.

I will try to hack together a quick client to test out the SOAP API and see if I can trigger a call. If I can't, then I imagine there is probably some configuration setting that is messing things up.

As a shortcut, I'd perhaps look at SOAP UI. It's not a tool that I use a lot, but others do. It is probably a quicker way to poke at the API vs generating a client in code.

I think I figured out the issue.

I used the .NET contact creation example for the SOAP API and modified it a little. I was able to get it to work on my production instance but could not get the same code to work with the upgrade interface.

When I run the .NET code for the upgrade site, it generates the following error:
Exception thrown: 'System.ServiceModel.Security.SecurityNegotiationException' in mscorlib.dll

It looks like it is an SSL error with RightNow and not a CX Dev Toolbox issue. I have the correct version of the .NET framework (4.6.2) for the newer version of RightNow (May 2016); do you know if there is some sort of configuration change that has occurred with the newer versions of RightNow that may be contributing to this issue?

I don't know of any problems and I was able to connect with the post-May 2016 versions.
At some point during that time they made a new setting a default. This setting changed the way that data could be accessed via the SOAP API. Instead of having full access to the data model (previous default), the permissions came from the profile of the user that authenticated to the SOAP API. So if your profile didn't have Incident read permissions, you could read the incident... etc.

Maybe that setting got activated on the upgrade site?

The account has all of the necessary account rights set; the C# code works in production but does not work on the upgrade site unless I add a line of code that specifies to use TLS v1.1 or v1.2 ...

I used the following stackoverflow link to get the SOAP code working:

Is there some update that I can make to machine that will default to use a newer TLS protocol? I have upgraded my .NET Framework to 4.7 and changed my windows Registry, but I can't seem to get the C#/SOAP API call to work with the upgrade console, I keep getting SSL errors...

What windows version are you running? Win 7? What is the earliest .NET framework version that is installed?. Also, did you try this using the v2 of the toolbox?

I am using Windows 7.

Earliest .NET Framework installed is 2.0.50727.5420 (at least that is what I see from checking the Windows Registry).

I will look into trying out the V2 of the toolbox; my thought is that there is either an issue with my computer or that there needs to be a line that needs to be added in applications that use the SOAP API to explicitly use the TLS 1.1 or 1.2 protocol.

Thank you for your help, Andy.

I downloaded v2 of the toolbox and it worked with out any issues with the upgrade site. There must be something different between the two versions...

I believe we targeted different minimum .NET versions between v1 and v2. I'd say this likely explains the issue.

I am able to connect to a prod site but not a tst site. I was notified by Oracle that in this case the TLS 1.0 was disabled for the tst site.

Do you have a version of CXDev Toolkit that supports TLS 1.1 or 1.2?

Thank you,


Yep. Here:


I used to be able to run a query with CSV output, and then copy and paste the returned values into excel, with the column names intact.

It was great when I needed to quickly review data, but didn't want to create a report on Right Now.

Newer versions of CX Dev tools still allows me to copy the values, but no longer brings across the headings. Is there a way to enable this?


I've added this functionality back to the toolbox (v2.4.1.0). Thanks for pointing it out.

I am not able to login with REST api. I am using latest Oracle Service Cloud which supports REST, if i provide soap getting error as "login failed"

Zircon - This is a contributing Drupal Theme
Design by WeebPal.