#Atelier

Greetings.

I'm trying to do some experiments using the Atelier REST API, but I noticed a bug that I simply can't bypass.

When requesting the Atelier server asking for an array of docs, it seems to fail when using it with multiple formats.
Like: [ "RCWWW015.int", "Class.cls" ]

While this method does return the class's source code, it fails when fetching the routine.
Like this:

I have 2 projects in atelier, A and B which map to namespace A and B on the same server.

Namespace B has some classes mapped from namespace A.

I then edit a mapped class in project A and save it(I can see the changes in cache studio as well).

atelier A:

studio:

However in project B the class does not change, even if I click the "syncronize all files with associated namespace " button.

atelier B:

How to cancel the remembered password after studio remembers it

Hi,

I just updated Atelier to 1.01.263 and now many of the Atelier icons/images are blurry and the spacing in the Atelier Explorer doesn't look right. This is on Windows 10. Is this a known issue? Are there any settings I need to adjust?

I have previously setup an Atelier project and it was running. I recently received the 1.3 release. Now, I am unable to click on the previously established connection to my Cache server (as seen in the Serve Explorer. I see the connection and the little arrow (implying that there is a hierarchy of items underneath). But, clicking that arrow opens nothing. Ultimately, I was trying to access files on the server so that I could add some new ones to my existing Atelier Project.

I'm just getting started with Atelier and HealthShare. I created a persistent class, then realized I didn't want it. There is information in help about resetting storage definitions, where you use 'delete' in Studio. I tried that in Atelier. It deleted the class but not the storage. I can't delete the table directly because I didn't set it to allow DDL. This was done in a development environment and there is no data in the table. So, two questions:

In Atelier when resolving conflicts with the server the screen shows the Local copy and Server copy and the differences, but depending on where the difference is you cannot tell what what the document is, you need to scroll to the top to see what it is before deciding what to do. It should indicate the class or routine name beside "Conflicting Server documents"

Upgraded IRIS/Connect to 2022.1 and /api/atelier no longer works through a Web/CSPGateway. Also upgraded the Web/CSPGateway to version WebGateway-2022.1.0.152.0 on Ubuntu and HTTPD Server version: Apache/2.4.29 (Ubuntu) with no luck as well.

It doesnt seem to matter if I add /api/atelier or /api/monitor to the enabled applications list, these routes do not make it back to the instance, however /csp, /csp/sys still does.

Is it possible to exclude certain folders from validating (i.e. generating errors/warnings in the Problems tab)? For example, I have *.js files from ckeditor and jquery libraries that are generating multiple errors that I'd like to suppress.

Some thins I have noticed, which I am not sure are bugs or features to come.

1.) Go to type declaration (F3 or ctrl+click on a class/variable/method)

It doesn not work on object variables and methods

Where it does work, it opens the related class but it is not editable.

2. )There is no code indentation correction/ctrl+L ?

Is this planned?

I would very much prefer to have formatting even if it means loosing some COS "functionalty".

Good day, this is just question from beginner, but I often use Atelier export to export my file as XML for Caché Unit Testing and I didn't find solution for my problem.

I just used Help\Check for Updates and updated my Atelier from 1.0.158 to 1.0.165. Is there any information published about what's new/fixed in this compared to previous public builds? Having that information might help us target our testing and so increase the value of our feedback to you.

Atelier is not translating the indentation spaces used to format XDATA sections in Cache Studio. Lack of these spaces makes the XDATA difficult to read. The styling (coloring) of the code is working just fine. Also, it appears that other class code indentation works fine.

Is anyone else seeing this issue? Has there been any discussion when this issue might be addressed by InterSystems? How shall I get some attention to this issue?

Is there anyway in either Atelier Server Explorer and Atelier Explorer to change the order of the Routine list so that it shows the software in both using Date Last Modified Order rather than alphabetically?