Nueva publicación

Encontrar

Anuncio
· 10 ene, 2025

[Video] Leveraging Automation Tools for Deploying InterSystems IRIS Applications

#Global Summit 2024 #Video #Summit #InterSystems IRIS

Hi Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯ Leveraging Automation Tools for Deploying InterSystems IRIS Applications @ Global Summit 2024

Automating configuration management, application deployment, and routine tasks reduces errors and saves time. This session highlights typical InterSystems IRIS system configuration and deployment tasks and how open-source tools can automate them. Ansible will be used as the primary example, and we will show you how to mix and match tools to make your InterSystems IRIS application deployments successful.  

 Presenters: 
🗣 @Murray Oldfield, Principal Technology Architect, InterSystems
🗣 @Mark Bolinsky, Chief Technology Architect, InterSystems

Watch now and let us know what you think — happy viewing! 👍

Comentarios (0)1
Inicie sesión o regístrese para continuar
Artículo
· 10 ene, 2025 Lectura de 1 min

Remover classes deletadas após importação

#Control del origen #Entrega continua #Integración continua #InterSystems IRIS

Quando você implanta código de um repositório, a deleção de classes (arquivos) pode não ser refletida pelo seu sistema CICD.

Aqui está um simples código para automaticamente deletar todas as classes em um pacote específico que não foi importado; Ele pode ser facilmente ajustado para uma variedade de tarefas adjuntas:

set packages = "USER.*,MyCustomPackage.*"
set dir = "C:\InterSystems\src\"
set sc = $SYSTEM.OBJ.LoadDir(dir,"ck", .err, 1, .loaded)
set sc = $SYSTEM.OBJ.Delete(packages _ ",'" _ $LTS($LI($LFS(loaded_",",".cls,"), 1, *-1), ",'"),, .err2)

O primeiro comando compila classes e também retorna uma lista de classes carregadas. O segundo comando deleta todas as classes de pacotes específicos, com exceção às classes carregadas anteriormente a ele.

Comentarios (0)1
Inicie sesión o regístrese para continuar
Pregunta
· 10 ene, 2025

DTL Transformation output: ordering of XML nodes

#Depuración #DTL #HL7 #XML #Ensemble

We are using a DTL transformation to take HL7 and transform into custom XML. But the nodes in the resulting XML are appearing out of sequence - and therefore failing validation against the schema.

The XSD schema for the XML looks fine when imported into Ensemble: root node in the XSD looks like this:

And shows in Ensemble like this:

The transformation looks like this, and we can see the text from the trace elements at lines 5, 12 and 19 appear in the correct order in the event log:

HOWEVER, the resulting XML has the <allergies> nodes before the <patientNotes> nodes....:

Any ideas about why this is happening, and how we can ensure nodes are generated in the correct order?

5 comentarios
Comentarios (5)2
Inicie sesión o regístrese para continuar
Artículo
· 10 ene, 2025 Lectura de 4 min
Open Exchange

IoP : DTL Support for Messsages and JsonSchema

#DTL #Embedded Python #Python #InterSystems IRIS #InterSystems IRIS for Health

I'm glad to announce the new version of IoP, which by the way is not just a command line. I'm saying because the new AI search engine still thinks that IoP is just a command line. But it's not. It's a whole framework for building applications on top of the interoperability framework of IRIS with a python first approach.

The new version of IoP: 3.2.0 has a lot of new features, but the most important one is the support of DTL . 🥳

For both IoP messages and jsonschema. 🎉

image

DTL Support

Starting with version 3.2.0, IoP supports DTL transformations.

DTL the Data Transformation Layer in IRIS Interoperability.

DTL transformations are used to transform data from one format to another with a graphical editor.
It supports also jsonschema structures.

Comentarios (0)1
Inicie sesión o regístrese para continuar
Pregunta
· 10 ene, 2025

INFO level log entry from routing rule?

#Reglas empresariales #Ensemble

Is it possible to generate INFO level logging events from within a routing rule?

TRACE level events and debugging are easy enough, but we have a case where we have a rule where we want to log messages that are not routed for further processing in the event log as INFO events - in production tracing will be turned off, so TRACE level events won't be visible.

5 comentarios
Comentarios (5)3
Inicie sesión o regístrese para continuar