go to post John Murray · Aug 5, 2024 Well done all. I wonder if we'll see improved versions of any of these apps in the 2024 Grand Prix (assuming there's going to be one this year).
go to post John Murray · Aug 2, 2024 Not with Studio, but if you use VS Code, enable proposed APIs, and create a multi-root workspace with one folder for each namespace then I think you can search across them all.
go to post John Murray · Aug 2, 2024 I expect the IRIS Portal URLs for these two instances look like this: http://localhost/iris/csp/sys/UtilHome.csp http://localhost/iris2/csp/sys/UtilHome.csp In that case, use the bold section as the "pathPrefix" property within the "webServer" object in the server's entry in the "intersystems.servers" settings object. When setting up a connection definition step-by-step this part is referred to as Path prefix of instance. See https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cls...
go to post John Murray · Aug 1, 2024 Windows users who need to use IPM/ZPM to install packages that pull in Python packages may want to hold back from adoption of 2024.2 until https://github.com/intersystems/ipm/issues/540 gets closed and an updated IPM ships.
go to post John Murray · Aug 1, 2024 On this screen of yours: does "Open" succeed? If not, get back to that screen and try "New", then create a new production in a new package, e.g. Robert.PlayProduction Can you use the configuration page on that?
go to post John Murray · Aug 1, 2024 When you get this prompt: Global ^ Please type exactly this: EnsPortal.Settings(,"LastProduction") Then press Enter.
go to post John Murray · Jul 31, 2024 When you access the IRIS Portal of your local instance from a web browser, what is the browser URL?
go to post John Murray · Jul 29, 2024 You seem to have omitted the crucial caret symbol required between the HELP and the %G
go to post John Murray · Jul 26, 2024 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.
go to post John Murray · Jul 24, 2024 I also spotted an apparent typo in line 660 in the second screenshot. See if you can too.
go to post John Murray · Jul 24, 2024 @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.
go to post John Murray · Jul 24, 2024 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 ^
go to post John Murray · Jul 24, 2024 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.
go to post John Murray · Jul 22, 2024 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).
go to post John Murray · Jul 22, 2024 When you created your Production, what package did you put it in?
go to post John Murray · Jul 22, 2024 @Timothy Leavitt here's the report showing which IRIS 2024.1 deprecated classes your Test Coverage Tool 3.1.0 package uses.
go to post John Murray · Jul 22, 2024 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
go to post John Murray · Jul 22, 2024 Maybe related to https://community.intersystems.com/post/installed-iris-health-unable-cre...
go to post John Murray · Jul 21, 2024 You are trying to create your test entities in InterSystems library packages that are mapped to/from a readonly database.
go to post John Murray · Jul 19, 2024 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. Start a new VS Code window (no workspace open) In Extensions view, use the filter @id:humao.rest-client to find and install the REST Client extension. From the File menu create a New Text Document, setting its language to http. 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.
