All
Accepted answers
John Murray · Mar 9, 2023 go to post

By doing a second install using Normal level security, then comparing webapp settings, I have tracked down the cause of my problem.

My install was a Minimal security one, after which I changed the settings of the /csp/sys web app and its sub-apps /csp/sys/* by clearing the Unauthenticated checkbox and setting the Password one.

But it seems that unless I do the same for the /api/interop-editors webapp I get a Rule Editor authentication page which I am unable to get past, not even by entering the credentials of the same %All-role user I logged into /csp/sys (i.e. Portal) with.

As soon as I made the change to /api/interop-editors I was able to get into the new Rule Editor, seeing only a brief flash of its authentication paged.

Here are the tweaked Minimal-security settings that work for me (i.e. authentication required to access Portal, from where I can move without challenge into the new Rule Editor):

John Murray · Mar 9, 2023 go to post

The technique I have seen used is to run a JS timer which will run for, say, 120 seconds less than the session timeout. Restart the timer each time something happens that will cause the server-side session timeout to restart. When the JS timer expires, display the "2 minutes before timeout" message, perhaps with a countdown run by another 1-second JS timer.

John Murray · Mar 8, 2023 go to post

This seems to include a new Rule Editor, but I'm unable to get past the authentication page it displays after I use my usual pathway from Portal (Interoperability > Build > Business Rules).

I have logged WRC 972106 about this (though WRC Online doesn't yet offer 2023.1 as a version choice).

John Murray · Feb 26, 2023 go to post

Can you help us understand why you want each routine exported into its own separate file? 

John Murray · Feb 24, 2023 go to post

Third choice could be phrased better:

I suggest "Doesn't matter, I will use Community regardless of interface color."

John Murray · Feb 11, 2023 go to post

Thanks Semion. I added that, and I have now set up an online demo and linked to it from OpenExchange. Please add this bonus.

John Murray · Feb 10, 2023 go to post

@Henrique Dias as a minimum please put that gif below the teaser break, so it doesn't show on the home page. People who have a physiological sensitivity to fast-moving images risk being made to feel physically sick when they visit DC to see what's new.
 

John Murray · Feb 7, 2023 go to post

In VS Code the "editor.insertSpaces" boolean setting governs whether or not pressing Tab will insert a tab character or a number of space characters (specified in the "editor.tabSize" setting).

"editor.insertSpaces" is one of the settings which can be specified per-language. The command "Preferences: Configure Language Specific Settings..." gives you a language picker, then seeds the Settings Editor filter so you can easily set a language-specific value. Below is a screenshot showing how I can make the Tab key enter the tab character when in a document set to the objectscript-class language.

You make a good point about how Python-coded methods must be space-indented. VS Code can't help you with this, as it sees the entire .cls document as being objectscript-class language. So I suggest you leave "editor.insertSpaces" at its default (checked / true). The ObjectScript-coded methods won't mind being space-indented.

John Murray · Jan 26, 2023 go to post

Presumably those problems are only affecting the Community container build, seeing as Online Distribution is offering an ARM64 of the non-Community variant:

John Murray · Jan 25, 2023 go to post

NOTE: ARM Community containers are not available for this Developer Preview #6.

Why is this? The same happened for Preview #5.

John Murray · Jan 24, 2023 go to post

Today ICR no longer offers build 589 of Community. It has been replaced by 599. I know this is preview, but I do wish InterSystems wouldn't delete the old build immediately they upload a later build. Those of us using dev containers or CI/CD workflows will suddenly find things broken until we update our scripts. And if we're only watching this DC post to learn about the new version we won't even have been notified yet.

Plus, still no arm64 build...

John Murray · Jan 23, 2023 go to post

Still no ARM64 version of the Community Edition of this build?

(Asking for a friend; my employer hasn't bought me an M1 / M2 machine yet sad)