New post

Find

Digest
· Aug 9, 2024

Participate in the sweepstakes by sharing how DC AI helped you!

Dear Community Member,

We're super excited to invite you to participate in our very first Developer Community Sweepstakes!

Your task is super simple: Share in the comments to this post how Developer Community AI helped you with your question (don't forget to add a link to the answer). At the end of summer, we will use random.org to choose one lucky winner out of everyone who commented (and followed the guidelines) — a maximum of 5 entries per person.

Good luck!

Announcement
· Aug 9, 2024

[Video] Preparando seus dados para uso com IA Generativa

Olá, Comunidade!

Como você pode preparar seus dados para aplicações de IA generativas? Obtenha algumas dicas importantes de um especialista da InterSystems:

Preparing Your Data for Use with Generative AI

Neste vídeo, @Jeff Fried, Diretor de Estratégia de Plataforma da InterSystems, explica como preparar seus dados e garantir que eles sejam governados, seguros, justos, enriquecidos e precisos.

Continue sua jornada com o Noções básicas do caminho de aprendizagem da IA ​​Generativa (2h 45m).

Discussion (0)1
Log in or sign up to continue
Article
· Aug 9, 2024 1m read

VS Code ObjectScript extension 2.12.6 and later can optionally display server documents read-only if source control class reports them as such

A nice feature that we recently added to version 2.12.6 of the VS Code ObjectScript extension is controlled by this new setting:

objectscript.serverSourceControl.respectEditableStatus

When set true in JSON, or checked in the Settings Editor, a server-side file will be read-only if the source control class for the namespace reports that it is not editable.

This option may be of particular interest to users of our Deltanji source control product, particularly when used in combination with the Deltanji extension for VS Code. Once set, managed documents have to be explicitly checked out via the context menu option Deltanji adds, instead of the checkout being triggered implicitly by the first edit. Operating this way combines well with Deltanji's concept of a "favorite" change request, which streamlines the checkout procedure but until now tended to lead to accidental checkouts that the user would then need to cancel.

Discussion (0)1
Log in or sign up to continue
Announcement
· Aug 9, 2024

[Vidéo] SQL on FHIR au service de la logistique hospitalière

Salut la Communauté!

Profitez de regarder la nouvelle vidéo sur la chaîne Youtube d'InterSystems France :

📺 SQL on FHIR au service de la logistique hospitalière

Intervenants : 
🗣 Luc Chatty, CEO, Fyrstain
🗣 @Guillaume Rongier, Ingénieur Commercial, InterSystems

Découvrez un cas d'usage de SQL avec FHIR pour la gestion des déplacements des ambulances autour d'un hôpital ainsi que l'affichage des informations sur une carte interactive.

Abonnez-vous à notre chaîne youtube pour plus de vidéos et restez à l'écoute !

Discussion (0)0
Log in or sign up to continue
Article
· Aug 9, 2024 2m read

WebTerminal is broken on IRIS 2024.2

I'm posting this for the benefit of WebTerminal users who have upgraded to the recently-released IRIS 2024.2 -- (Build 247U) Tue Jul 16 2024 09:52:30 EDT -- or are considering doing so.

That version of 2024.2 contains a change (DP-432503) which requires that the user under which the Web Gateway initially connects to IRIS (usually CSPSystem) must have READ permission on the database hosting the dispatch class of the REST web application.

For cases where that is not true an error is raised, but this returns an HTTP 404 status to the caller instead of the expected HTTP 401.

Apparently the problem will be fixed in 2024.3, reference DP-432898 / ALI048 : REST Login endpoints to return 401 HTTP error instead of 404, but as a Continuous Delivery (CD) release 2024.2 won't get a maintenance release correction.

Workaround is to arrange for CSPSystem to have READ permission on the database of the namespace you installed WebTerminal in.

Here's how I did it:

  1. Create a new security resource %DB_WEBTERMINAL and set the WEBTERMINAL database to use this instead of %DB_%DEFAULT.
  2. Create a role %DB_WEBTERMINAL that gives the role-holder RW access to the %DB_WEBTERMINAL resource.
  3. Create another role (I called mine DBread_WEBTERMINAL) that gives the role-holder only R access to that resource.
  4. Give the CSPSystem user the DBread_WEBTERMINAL role. This works around the 2024.2 bug.
  5. Edit the /terminalsocket web application and add %DB_WEBTERMINAL to the Application Roles tab. This step is necessary because WebTerminal initially runs its websocket process as UnknownUser and needs to update state information in its database even before it switches to run as the authenticated user.

An easier but less secure technique would be:

  1. Create a new security resource %DB_WEBTERMINAL with RW public privileges, then set the WEBTERMINAL database to use this instead of %DB_%DEFAULT.

More details at https://github.com/intersystems-community/webterminal/issues/155

2 Comments
Discussion (2)2
Log in or sign up to continue