All
Accepted answers
John Murray · Mar 16, 2024 go to post

At Step 3, if you already use Studio you can take advantage of an option on the ... menu to import your existing server definitions. 

John Murray · Feb 23, 2024 go to post

I agree that source control is a good way of tackling the "who changed it, when, and why?" questions.

If you haven't already, please take a look at Deltanji from my company, George James Software. LUTs are treated the same way as Classes, Routines, Schemas and many more component types. Deltanji operates natively inside all InterSystems platforms, including HealthConnect, dealing with deployment as well as versioning.

John Murray · Feb 21, 2024 go to post

So I'm confused that none of the GIFs posted in response to this seem to have a play/pause button. 😕

John Murray · Feb 14, 2024 go to post

I'm guessing you are using the client-side editing paradigm, creating a new Foo/Bar.cls file (probably in the src subfolder of the folder you opened in VS Code), defining Foo.Bar as a subclass of %Persistent. Then when you save it VS Code imports the class into the namespace of the server your configuration connects to. When it compiles this for the first time the server adds the storage definition. VS Code should automatically reload the updated class definition into your local file.

When you begin a debugging session VS Code by default saves modified documents before launching server-side execution of your code.

None of this should produce the symptoms you reported. I recommend moving the investigation to the extension's Issues section in its GitHub repository. A good way of opening an issue there is to begin at the Report Issue option from VS Code's Help menu. This will automatically include version information in the report. You can't paste screenshots or animated GIFs into that dialog but it's easy to edit the issue description on the GitHub page that opens after the dialog closes.

John Murray · Feb 9, 2024 go to post

It looks like you used VS Code to directly open the folder (C:\InterSystems\IRIS\CSP\goerke\) which your (local desktop instance) IRIS created for the /csp/goerke webapp it configured when you added a GOERKE namespace using IRIS Portal.

I think this is going to get confusing for you, particularly if you try to use documentation or training material.

Here's what I recommend you do:

1. Close your the folder in VS Code.

2. Copy your C:\InterSystems\IRIS\CSP\goerke into a folder where you will edit your source files, and perhaps in future source-control them with Git. For example, copy it to c:\MyProjects

3. Open the newly-created folder in VS Code (e.g. c:\MyProjects\goerke)

4. Reconfigure your /csp/goerke webapp in IRIS Portal so it points again to C:\InterSystems\IRIS\CSP\goerke

5. Delete all contents of C:\InterSystems\IRIS\CSP\goerke (files and folders), since you already have a copy of these in c:\MyProjects\goerke

Now when you edit a CSP file in VS Code and save it under c:\MyProjects\goerke\src a copy of it will appear in C:\InterSystems\IRIS\CSP\goerke and the /csp/goerke webapp will use this.

When you edit a CLS file in VS Code, saving this writes the class into the GOERKE namespace but doesn't create a file under C:\InterSystems\IRIS\CSP\goerke because IRIS classes live in IRIS databases, not in host OS files.

John Murray · Feb 9, 2024 go to post

Did you put your files in a src subfolder of the folder you opened in VS Code? If not, please close the files in VS Code, create a src subfolder, drag your CSP files into it, then open one and try saving it.

John Murray · Jan 18, 2024 go to post

I'm guessing that Brett is testing on a non-Windows platform. By replicating Mathew's setup on Windows I can reproduce the issue.

Mathew, please try using backslash in the "folder" property of your "objectscript.export" settings object:

      "folder": "src\\database",
John Murray · Dec 21, 2023 go to post

Package definition can already be exported to a file using $system.OBJ.Export("Foo.Bar.pkg",filename)

Yes, it's XML format rather than prettier UDL, but it can still be used to manage the definition in file-based source control.

John Murray · Nov 22, 2023 go to post

I find the borders too narrow (1.5px) to show me the colour. Maybe also use different values for border-radius, e.g. 5% for staff, 30% for mods.

John Murray · Nov 9, 2023 go to post

This is a good reason for implementing the server-centric paradigm for code editing and for source control. We at George James Software have a growing number of sites that use our mature and powerful Deltanji tool, which handles deployment as well as versioning, is hugely flexible and configurable, and now has a unique ability to manage the individual configuration items of an interoperability production. Deltanji runs within the InterSystems platforms, handling your code where it is runnable instead of constantly having to export and reimport it. Deltanji can also handle code artifacts that live outside the InterSystems platform, such as images, scripts and stylesheets.

John Murray · Nov 7, 2023 go to post

If the existing (large) application consists of a lot of ObjectScript artifacts (routines, globals, and maybe some classes) did you consider using Deltanji, an ObjectScript-native source code management solution? No Git involved, so none of the export/import that approach requires.

As well as versioning the code it handles the whole workflow, making it easy to promote changes from dev namespaces via test ones to production / packaging ones.

John Murray · Oct 20, 2023 go to post

Use this section:

There's also a useful "Help" link in the upper right of that page (not shown in my screenshot above).

John Murray · Oct 11, 2023 go to post

Starting with v2.10.3 of the InterSystems ObjectScript extension, if you launch the Server Actions menu (e.g. by clicking on the extension's status bar panel) you should get an option to "Open Studio Add-in...", and from there a list that includes the SOAP Wizard.

John Murray · Oct 9, 2023 go to post

They are independent passwords. Changing the password for CSPSystem user in IRIS Portal doesn't affect the password you authenticate with when you access the Web Gateway Management page even though the username is the same. 

John Murray · Oct 5, 2023 go to post

Are you using VS Code for your debugging? Or Studio? Or the command line?

John Murray · Sep 14, 2023 go to post

They got back to me. Clearing browser cookies from isccloud.io did the trick, after which I was offered "demo" rather than "micro".

John Murray · Sep 12, 2023 go to post

I guess you are looking for a way to launch the XML Schema Wizard add-in that Studio offers.

Try adapting the advice at https://docs.intersystems.com/components/csp/docbook/DocBook.UI.Page.cl… for adding a custom entry to the Server Actions menu. In this case the entry in the "links" object within "objectscript.conn" should be:

"Open XML Schema Wizard": "${serverUrl}/isc/studio/templates/%25ZEN.Template.AddInWizard.XMLSchemaWizard.cls?$NAMESPACE=${ns}"