You can open the BPL graphical editor in Atelier by opening the class code, right-clicking anywhere on the code in the Editor and selecting "Open diagram editor".

As Joyce mentioned, there will also be a Developer Community post coming soon about the way to view the DTL/BPL graphical editors in the current version of Atelier.

You can copy a whole package of classes or routines to an Atelier project. In the Server Explorer, right-click the package under the Classes or Routines tree and select Copy To Project. Pick the Atelier Project to copy to and on the next page of the wizard you should see a list of all of the classes or routines that will be copied over.

Development did a code review and determined that this is a bug with the cached query generation code in Caché 2014.1. As far as I know we've only seen this for queries executed via xDBC.

There is a place in the cached query generation code where an error may not be properly trapped. In this case the cached query routines are not created properly, but no error is reported back. Then when Caché tries to use that cached query code to execute the query the expected methods do not exist.

The possible solutions we've come up with:

1. Create a task to purge cached queries in your application namespace - Pick a task frequency that means it will run more often than you have seen errors occur. This way you aren't stuck manually purging cached queries whenever an error pops up.

2. Get a development patch containing some fixes for your version of Caché - For this you will need to contact either your InterSystems Sales team or Support to file a WRC case. Note that our development patches do not go through our standard QD testing process. If you apply this patch you will be working with a version of our code that has not gone into any released product.

3. Upgrade your instance - This is the only long-term solution. Our cached query generation code has been rewritten in later versions of the product and this is no longer a problem.

You can use the Outline view in Atelier for information about the current class' properties, parameters, class methods, etc:

There is an enhancement request to show inherited members in the Outline view which is currently planned for Atelier 1.1.

Atelier's code completion, which can be accessed by hitting ctrl+space, is also a good tool here. For example you can use code completion to quickly check the possible options for an index's keywords (with documentation):

When you generate an HTML Zen Report that request is served through the web server. It looks like on your system: in the case of the IIS web server using the alias name rather than the IP address and IE 8+, some of the static files are not being served properly. I think this would be best investigated by Support in a WRC case. You can open up a new case by emailing a brief description to, or by calling the Support line at (617) 621-0700.

Agreed, that could be confusing. I filed an enhancement request to retain error messages in the Server Connection Configuration dialog as long as the problem persists.

When you try to start Atelier with the wrong version or bitness of Java installed, you will see that error pop up. There are a few things you can check when this occurs:

1. In an OS command prompt, enter “java –version” to display something like:

java version "1.8.0_51"

Java(TM) SE Runtime Environment (build 1.8.0_51-b16)

Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

This shows the version and the bitness of the Java version installed on your machine. So this can help make sure you are meeting a couple of requirements:

A. You need the Java JDK or JRE version 1.8 (JDK for Mac, JRE for other platforms)

B. The bitness of Java must match the bitness of your Atelier client. I’ve seen that a 64-bit install indicates that it is 64-bit in the "java –version” output. But for a 32-bit version of Java, no bitness is listed in the "java –version” output.

2. Check your JAVA_HOME environment variable. Make sure that if this is set that it is pointing to your Java JDK/JRE with the correct version and bitness.

On a Mac,  you can check the location of your Java 1.8 home directory with the Terminal command: /usr/libexec/java_home -v 1.8. On a Windows machine, you can enter this in a Command Prompt: where java.