查找 | InterSystems Developer Community

お知らせ

Irène Mykhailova · 2026年1月22日

Salut le Communauté,

Nous sommes ravis de vous inviter à participer à la conception de la prochaine génération d'outils de développement pour ObjectScript. Nous travaillons sur un assistant de codage ObjectScript basé sur l'IA, spécialement conçu pour les développeurs IRIS. Il ne s'agit pas d'une IA générique adaptée à ObjectScript, mais d'une solution entièrement nouvelle, capable de comprendre les spécificités d'ObjectScript, les API IRIS, les exigences d'interopérabilité et les flux de travail réels des développeurs.

Pour créer un outil vraiment utile, nous avons besoin de votre avis.

👉 Sondage pour développeurs sur l'Assistant de codage pour ObjectScript 👈

Ce sondage ne prend que 5 minutes et aborde les points suivants :

Votre rôle et votre niveau d'expérience
Vos difficultés et flux de travail actuels
Les fonctionnalités les plus importantes pour vous (génération de code, débogage, aide à l'apprentissage, etc.)
Où et comment vous souhaiteriez utiliser cet outil

Ce sondage est ouvert aux développeurs de tous niveaux d'expérience d'ObjectScript.

Et ensuite ?

Les résultats agrégés seront partagés avec la communauté.
Les participants intéressés pourront recevoir une invitation à la bêta anticipée.
Des mises à jour régulières sur l'avancement du développement seront fournies.

Vos commentaires influenceront directement nos priorités de développement et le fonctionnement de l'outil.

Pour toute question, n'hésitez pas à laisser un commentaire ci-dessous ou à nous contacter directement à l'adresse thomas.dyar@intersystems.com.

Merci de nous aider à créer de meilleurs outils pour la communauté d'ObjectScript. Nous avons hâte de recevoir vos suggestions !

ディスカッション (0)1

続けるにはログインするか新規登録を行ってください

記事

Toshihiko Minamoto · 2026年1月21日 4m read

Open Exchange

#CSS #ObjectScript #Python #ビジネスオペレーション #相互運用性 #InterSystems IRIS #Open Exchange

メール送信は、統合シナリオでは一般的な要件です。クライアントへのリマインダー、自動レポート、トランザクション確認などに使用されます。固定メッセージは、管理やパーソナライズが難しくなりがちです。そこで登場するのが templated_email モジュールです。InterSystems IRIS InteroperabilityをJinja2テンプレートの機能を組み合わせます。

メール作成でJinja2を選ぶ理由

Jinja2はPythonエコシステムで人気のあるテンプレートエンジンで、完全に動的なコンテンツ生成を可能にします。次をサポートします：

変数 — 統合メッセージや外部ソースから動的にデータを取り込みます
条件（if/else）— ランタイムデータに基づいてコンテンツを変更します
ループ（for）— テーブル、項目リスト、反復セクションを生成します
フィルターとマクロ — 日付や数字のフォーマット、テンプレートブロックを再利用します

簡単なメール本文テンプレートの例：

ディスカッション (0)0

続けるにはログインするか新規登録を行ってください

記事

Peter Steiwer · 2026年1月21日 2m read

#分析 #互換性 #キューブ #Internal Tech Article Contest

Starting with InterSystems IRIS 2025.1, the way dependent cubes are handled in cube builds and cube synchronizes was changed.

This change may require modifying custom build/synchronize methods. If you are using the Cube Manager, these changes are already considered and handled, which means no action is needed.

Prior to this change, cubes were required to be built and synchronized in the proper order and account for any cube relationships/dependencies. With this change, dependent cubes are automatically updated as needed when using the %BuildCube or %SynchronizeCube APIs.

The negative symptom you may see if you have a custom build method would be that your dependent cubes may be built multiple times. This should not cause any errors, but it may mean your builds take considerably longer depending on how many dependent cubes you have.

The biggest consideration in modifying your custom build/synchronize methods is that the first parameter of %BuildCube and %SynchronizeCube now accept a list of cube names. Dependencies in this list will be resolved so they are not built multiple times.

Example using old logic:

do ##class(%DeepSee.Utils).%BuildCube("relatedcubes/cities")
do ##class(%DeepSee.Utils).%BuildCube("relatedcubes/doctors")
do ##class(%DeepSee.Utils).%BuildCube("relatedcubes/patients")
do ##class(%DeepSee.Utils).%BuildCube("relatedcubes/cityrainfall")
do ##class(%DeepSee.Utils).%BuildCube("relatedcubes/allergies")

Calling the cube builds like this will trigger dependent builds multiple times. This results in the following cube builds happening:

Building cube [RELATEDCUBES/CITIES]
Building cube [RELATEDCUBES/CITYRAINFALL]
Building cube [RELATEDCUBES/DOCTORS]
Building cube [RELATEDCUBES/PATIENTS]
Building cube [RELATEDCUBES/ALLERGIES]
Building cube [RELATEDCUBES/DOCTORS]
Building cube [RELATEDCUBES/PATIENTS]
Building cube [RELATEDCUBES/ALLERGIES]
Building cube [RELATEDCUBES/PATIENTS]
Building cube [RELATEDCUBES/ALLERGIES]
Building cube [RELATEDCUBES/CITYRAINFALL]
Building cube [RELATEDCUBES/ALLERGIES]

Example using updated logic:

do ##class(%DeepSee.Utils).%BuildCube($LB("relatedcubes/cities","relatedcubes/doctors","relatedcubes/patients","relatedcubes/cityrainfall","relatedcubes/allergies"))

This will simply build the cubes in a dependency-compliant order:

Building cube [RELATEDCUBES/CITIES]
Building cube [RELATEDCUBES/CITYRAINFALL]
Building cube [RELATEDCUBES/DOCTORS]
Building cube [RELATEDCUBES/PATIENTS]
Building cube [RELATEDCUBES/ALLERGIES]

The documentation’s “Upgrade Considerations” page references this compatibility change: https://docs.intersystems.com/iris20251/csp/docbook/DocBook.UI.Page.cls?KEY=GUPE_upgrade#GUPE_upgrade_buildcube

ディスカッション (0)1

続けるにはログインするか新規登録を行ってください

お知らせ

Anastasia Dyubaylo · 2026年1月21日

#Artificial Intelligence (AI) #ビデオ #その他

Hey Community!

We're happy to share the next video in the "Code to Care" series on our InterSystems Developers YouTube:

⏯ How Big Research Bets Are Made Without a Crystal Ball

Learn how research organizations set priorities without relying on precise future predictions, about the concept of “inevitable futures” as a way to ground long-term research decisions in real-world trends, with examples drawn from healthcare and demographic change. Hear about a structured framework for balancing short-term problem solving, long-term exploration, disruptive innovation, and sustained improvement across multiple domains.

Presenters:
🗣 @Don Woodlock, Head of Global Healthcare Solutions, InterSystems
🗣 Dr. Peter Lee, President, Microsoft Research

Enjoy watching, and subscribe for more videos! 👍

ディスカッション (0)1

続けるにはログインするか新規登録を行ってください

記事

Heloisa Paiva · 2026年1月21日 3m read

#FHIR #OAuth2 #InterSystems IRIS #InterSystems IRIS for Health

Olá, agora gostaria de continuar com o tópico que discutimos anteriormente

Usando o Postman para testar o OAuth2.0 do repositório InterSystems FHIR - Parte 1

Pergunta 1: De onde vêm meu client_id e meu client_secret?

Resposta curta: Do Servidor de Autenticação.

Se você não possui um Servidor de Autenticação, pode configurar um da seguinte forma:

Forneça o hostname (o host deve suportar Https), pelo menos 1 tipo de concessão (escolhemos client credential aqui) e a configuração SSL/TLS

Insira os escopos (aqui inserimos user/.read e user/.write, que são baseados no suporte de escopo do servidor FHIR (servidor de recursos)). Caso haja algum escopo que esquecemos, marque "Allow unsupported scope".

Na configuração de JWT, escolha RS256 (este é apenas um exemplo, você pode escolher o que melhor se adapta à sua arquitetura)

Altere a Generate token class para %OAuth2.Server.JWT. E atualize o namespace se necessário.

Salve a configuração

Pergunta 2: Como verificar o client_id e o client_secret vindos do Servidor de Autenticação?

Resposta curta: Configure um Cliente OAuth2.0 (se não tiver um) e crie um cliente

Abaixo estão as etapas para configurar um Cliente OAuth 2.0.

Clique em Create Server Description

Insira o Issuer end point e a configuração SSL/TLS aqui

e clique em Discover and Save

Você pode encontrar as informações relacionadas na página de configuração do Servidor OAuth2.0

Após o Discover and Save, você verá algo semelhante ao abaixo. Podemos precisar dar uma olhada no token endpoint, que precisaremos para solicitar um token

Após a configuração acima, agora é hora de criarmos um cliente chamado Postman 😁

Clique no botão OAuth 2.0 Client

Clique em Client Configurations

Clique em Create Client Configuration

Insira o Application name e o Client name, escolha o Client type confidential, insira o Hostname for the Client redirect URL e escolha o Required grant types como Client credentials

Clique em Dynamic Registration and Save

Você verá algo semelhante ao seguinte.

Agora, é hora de verificar nosso client_id e client_secret😁😁

Clique na aba Client Credential

Você pode copiar seu client_id e client_secret aqui 😉

Pergunta 3: Como adicionar meu servidor FHIR como um servidor de recursos e relacioná-lo ao Servidor de Autenticação?

Resposta curta: Configure um Cliente OAuth2.0 (se não tiver) e crie um servidor de recursos. Em seguida, aplique o servidor de recursos à configuração do servidor FHIR

Para criar um servidor de recursos

Clique em Client Configurations