You seem to have omitted the crucial caret symbol required between the HELP and the %G

This is caused by how version 2.12.0 and above of the ObjectScript extension depends on the Server Manager extension, which hasn't yet been made compatible with VS Code in the browser.

I have created https://github.com/intersystems-community/intersystems-servermanager/iss...

Workaround is to use the gearwheel on the extension's detail page, then choose to install the latest pre-2.12 version.

@Ben Spead sometime we'd love to show your Internal Apps team the kind of codebase insights Yuzinji can provide. Please DM me if you are interested.
 

Maybe the page is trying to display details of a previously-opened prodclass that is giving it a problem.

I suggest you use the %G utility in an IRIS Terminal in your namespace (INTERFACES?) to see what this lists:

INTERFACES>d ^%G
 
Device:
Right margin: 80 =>
Screen size for paging (0=nopaging)? 24 =>
For help on global specifications DO HELP^%G
Global ^EnsPortal.Settings(,"LastProduction")
^EnsPortal.Settings("XXX","LastProduction")="Foo.Bar"
 
Global ^

Other answers here cover exporting the application definition.

To transfer the application files it may be simplest to copy the files from the host OS path that the application definition points to.

Another option is to create a Studio project, add the webapp to the project, then export the project.

But your earlier screenshots show you trying to create entities in the INFORMATION.SCHEMA package and in the %Api package. These are always mapped to the IRISLIB database (see the error dialogs), which is always readonly.

You should enter a non-percent package name of your own (e.g. Robert).

When you created your Production, what package did you put it in?

@Timothy Leavitt here's the report showing which IRIS 2024.1 deprecated classes your Test Coverage Tool 3.1.0 package uses.

I came up with a better technique for using Yuzinji and Structure101g Studio to reveal which deprecated classes an app's codebase uses. Here's a screenshot showing the results for the Web Terminal 4.9.6 package on IRIS 2024.1

I adapted the tagging technique to identify the use of deprecated methods in non-deprecated classes. In the case of the Web Terminal codebase, no such usage was found.

If anyone reading this is interested in trying this on your own codebase please contact me through DC's DM facility, or email info@georgejames.com

Maybe related to https://community.intersystems.com/post/installed-iris-health-unable-cre...

Here's one way to verify from VS Code (but independent of the InterSystems ObjectScript extension) that the /api/atelier REST APIs are available on that server.

1. Start a new VS Code window (no workspace open)
2. In Extensions view, use the filter @id:humao.rest-client to find and install the REST Client extension.
3. From the File menu create a New Text Document, setting its language to http.
4. Paste this content:

GET http://localhost/api/atelier/v1/%25SYS HTTP/1.1
Authorization: Basic _system:SYS

Now click on the "Send Request" codelens that appears above the first line.

Maybe the trace facility on the Web Gateway Management page will yield clues. 

I'm guessing you need to add a `pathPrefix` property. See https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cls...

When you access IRIS Portal in your browser what is the url? 

TIP: if you are in a hurry, use the YouTube option to play this at 2x speed and you'll get through it in half the time.

It is often the case with large applications that developers would like to or need to work on unrelated parts of an application simultaneously. It is a limitation of the Git for Shared Development Environments application from the InterSystems Open Exchange that you cannot do this in a single namespace. That's because it is built on git, where you can only have a single branch checked out to a working folder at any one time.

Our InterSystems-native source control and integrated deployment solution Deltanji allows developers to create multiple separate branches within the same namespace.  Because Deltanji has finer granularity it can handle concurrent non-overlapping sets of changes in a single namespace, enabling users to check code entities out onto separate Change Requests, then promote these independently.

Even with a team as small as one person it is common for Deltanji-controlled development to take place this way. Use of QA and/or Staging environments ensures that unforeseen dependencies created in the Development environment between supposedly independent Change Requests will be detected before they can impact the Production environment.