Atelier 1.1 Beta Update

December 2017

Here's an account of what has changed in Atelier 1.1.391, available now from the beta update channel.


  • UI freeze during UDL file processing — A problem with the UI freezing or becoming unresponsive when UDL file indexing is taking place has been fixed.
  • Problem with connection passwords fixed — A problem with workspace initialization that caused server connection login failure has been fixed.

Other Enhancements & Fixes

  • Debugger — Fixed problem with disconnect button being disabled when it should be enabled. This behavior is supported in server versions 2017.2.0 and later, and depends on fixes available in 2017.2 maintenance releases.
  • Synchronization — Skip copy of deployed files when copying from the Server Explorer.
  • Wizards
    • The connection Wizard now handles the presence of underscore in a connection name gracefully.
    • File Search no longer causes Java null pointer exception when used immediately after using Atelier Search.
  • XML and RTN File Support
    • Syntax checking has been enabled.
    • File encodings other than UTF-8 are now supported
    • The Windows-specific problem of a file system exception being thrown when you delete a project that includes an XML or RTN class has been fixed.
    • Compile Project now compiles XML and RTN files in the project.
    • The XML and RTN file editor displays the correct background color for read-only files.
  • Performance — The XML Import/Export wizard now can handle large files when listing classes and routines.
  • InterSystems IRIS — Copyright comment in the syntax checker and legacy XML import wizard is supported.

Known Issues:

  • If you open an RTN file and introduce a syntax error during editing, the file content is destroyed when you attempt to save the file.
  • Breakpoint setting fails for XML and RTN files opened in an Atelier editor.
  • Code completion fails in XML and RTN files opened in an Atelier editor.
  • Open declaration fails from XML and RTN files opened in an Atelier editor.
  • An exception is thrown when an Atelier project is deleted that contains a class or routine file in XML format.

Previous Features and Improvements


DescriptionBuild number

XML and RTN editor — If you have been using source control by exporting classes and routines to individual XML or RTN files from Studio, you can now modify those files without first converting them to the UDL format. These files will be presented in an Atelier editor as if they were UDL files.

Use the File System import wizard to Import XML or RTN files and add them to an Atelier project. Open these files in an Atelier editor by double-clicking in the Atelier Explorer view. Double-clicking in the Project Explorer opens the file in the default XML editor according to your user preferences. Note that XML files containing more than one class or routine are not supported by the XML and RTN editor. You must convert these files to UDL using the Legacy XML import wizard as you did previously.

Known bugs:
  • code completion fails in XML files opened in an Atelier editor
  • open declaration fails from XML files opened in an Atelier editor
  • breakpoint setting fails for XML files opened in an Atelier editor
  • Exception thrown when Atelier project is deleted that contains a class or routine file in XML format

CSP as a debugging entry point — Create debug configurations that use a CSP page as an entry point.

Create a project mapped to the namespace where the CSP application is located. Open the Debug Configurations dialog by selecting Run > Debug Configurations.... Create a new Atelier Application launch configuration. When completing the form, select the CSP entry point radio button. In the URL field specify the path to the CSP page starting with the CSP application. For example, /csp/samples/lotteryjoin.csp. Files must be compiled for debugging to work as expected.

Note that breakpoints and stepping through CSP pages are not supported at this time, but are planned future work. You can set breakpoints in code called from a CSP page.

Also note that, like many Eclipse menu items, Run > Debug Configurations... is context dependent. For example, it is not available if an editor has focus while editing a CSP file.


Configure any Eclipse project as an Atelier project — Easily migrate your existing code base to be used with Atelier.

Import your code base from source control using the appropriate wizard contributed by the source control plugin you have installed. You can also import existing Eclipse projects using the Existing Projects into Workspace import wizard. Select the imported project and right-click to open the context menu. Select Configure > Configure Atelier. Complete the dialog that pops up by selecting a connection and namespace for this project and press the OK button.

Note that projects that are not configured to work with Atelier might be filtered from your Atelier Explorer view. You can:

  • open the Project Explorer view
  • open the Atelier Explorer filters from the view's menu to verify if this is the case

Open Declaration support for macros — Easily unpack macros by jumping directly to their definition.

Select the macro in an Atelier editor and invoke Open Declaration with the key binding (F3 by default) or by selecting it from the editor context menu (right-click in the editor). In order for this feature to work, the server connection associated with a given file (inherited from its project) must be accessible when you invoke Open Declaration.

Server-side text search is available in projects with connections to servers 2017.2 and higher (available in the Field Test Portal). This feature enables you to discover declarations and references for any pattern. Searches take place on the server in a given a namespace. The scope definition can include system and/or generated items. To use this feature, configure a connection, then open the Atelier Search tab from the Search dialog. 351
Code completion for Macros is available in projects with connections to servers 2017.2 and higher. This feature provides assistance for completing macro references. To use this feature, open any file where $$$ syntax is legal in the Atelier editor. The server must be accessible. Invoke code assist with CTRL+Space after $$$ syntax. Note that only macros with an associated description are listed. 351
The Atelier editor automatically closes parentheses and double quotes. The editor also automatically closes curly braces and indents the cursor. These features speed up code writing by predicting characters and formatting. 351
Server credentials are required when you create new server connections or edit existing ones. This restriction supports the license management requirement for valid credentials. 351
Secure server connections using Transport Layer Security (TLS) are supported. This feature enhances security. To use this feature the server must be correctly configured according to documentation. 351
BPL is supported for the Ubuntu platform. Please note that some related server fixes are only available from 2018.1.0 310
You can open the Management Portal from the Server Explorer view context menu 291
You can compare local and server file versions using the Compare With > Server’s Copy command on the Atelier Explorer context menu 291
XML import and export no longer require an active server connection; in addition, the import wizard is more robust and can handle large XML files 291
Support for Feature Tracker, which is a safe and trustworthy approach for InterSystems to periodically collect information about feature use while maintaining the integrity of our relationship with our clients. For Atelier, only compilation times are collected to get a sense of the number of active Atelier users. See documentation for details. 291
The Atelier editor copies indentation of the previous line when you add a new line after a comment 291
Based on Eclipse Oxygen (4.7) 291


DescriptionBuild number

Server text search — The ability to perform text search on the server was introduced in 1.1.351, enhanced in the new beta release. A known bug is that doing a File Search immediately after doing an Atelier Search throws a NullPointerException


Typing preferences — Beta release 1.1.351 added automatic closing of strings, parentheses, and method bodies. This release adds a Typing preference page, which lets you enable or disable autocompletion of these elements.

Use the Typing preference page, Preferences > Atelier > Editor > Typing, to configure these preference. Your changes are immediately enabled in all Atelier editors: classes, routines, CSP files. A known bug is that double quote closing does not handle copy and paste well, and often introduces a syntax error.


License usage is improved for users who reboot Atelier often, especially those with low user licenses. Atelier now closes any active CSP sessions when shutting down. Close CSP session on Atelier shutdown


Syntax checking and coloring coverage has been expanded, especially for $z components and for methods in Basic.


Code completion bugs have been fixed, especially related to routine support and macros.


Debugger has been made more robust.


Error logging has been improved, especially for synchronization from the graphical editor and the debugger.


The XML import/export wizard now ignores irrelevant types (Global, Checksum, Document, OBJ).


Several miscellaneous UI improvements.


A bug introduced in 1.1.351 that caused CSP files to disappear from the Server Explorer view has been fixed.

Completion fixes — the file must be opened in Atelier editor. $System completion in routines fixed. Labels are proposed after .. in routines. 351
Syntax checking fixes — the file must be opened in Atelier editor. Support for methods with the keyword CodeMode = call. Support for classes with keyword [ CompileAfter = ]. Support for quoted ForeignKey properties. 351
Code templates have been updated. These templates completely replace the Studio wizards that performed the same tasks. To use this feature, open the file in the Atelier editor, then invoke code assist with CTRL+Space. 351
The Atelier Logo has been updated to reflect InterSystems branding. 351
Files without timestamps are now supported. 351
It is now possible to create a launch configuration from an inherited class method. 351
The parser generates fewer false negatives, especially for $functions. 351
UI has been updated, especially XML and RTN file support for non-Windows operating systems. 351
Syntax checking has been fixed for additional functions ($zjob, $zobjref) 310
The SQL parser has been significantly enhanced including performance improvements 310
The JavaScript parser has been simplified for performance improvements. The "File is too large to parse properly" issue has been fixed. 310
Miscellaneous UI fixes 310
Improved support for Studio features 291
Expanded support for syntax checking 291
Improved Performance 291