Hello and welcome to the next InterSystems technical article writing competition!

🐍 InterSystems Tech Article Contest: Python Edition 🐍

Write an article on any topic related to the usage of Python with InterSystems technologies from June 20 to July 20 July 31– extended!

🎁 Prizes for everyone: A special prize pack for each author who takes part in the competition!

🏆 Main Prizes: AirPods Max; Apple Watch SE; Apple HomePod mini / Apple Pencil

I am writing documentation in VS Code, using markdown, and am including some COS snippets in it, e.g.:

```objectscript
[Some COS snippet]
```

The IRIS language server (etc.) is enabled, and classes in the repository this documentation is in, are syntax highlighted properly. However, the code fragment in the documentation isn't. Syntax highlighting for e.g. XML does work.

Am I doing something wrong, or is this not supported?

Following this GitHub we will see how the FIX protocol can be implemented easily using IRIS and Python.

If you don't have much time focus on the Send a Quote before the Order part near the end, as it will, in a matter of minute, tell you how to send a Quote Request followed by an Order Request and show you the result from the server, and that in no more than five clicks.

Hi everyone!

Just wanted to share here a quick post about my project for the Grand Prix :)

An interesting pattern around unique indices came up recently (in internal discussion re: isc.rest) and I'd like to highlight it for the community.

As a motivating use case: suppose you have a class representing a tree, where each node also has a name, and we want nodes to be unique by name and parent node. We want each root node to have a unique name too. A natural implementation would be:

In this article, I would like to talk about the spec-first approach to REST API development.

While traditional code-first REST API development goes like this:

• Writing code
• REST-enabling it
• Documenting it (as a REST API)

Spec-first follows the same steps but reverse. We start with a spec, also doubling as documentation, generate a boilerplate REST app from that and finally write some business logic.

This is advantageous because:

• You always have relevant and useful documentation for external or frontend developers who want to use your REST API
• Specification created in OAS (Swagger) can be imported into a variety of tools allowing editing, client generation, API Management, Unit Testing and automation or simplification of many other tasks
• Improved API architecture. In code-first approach, API is developed method by method so a developer can easily lose track of the overall API architecture, however with the spec-first developer is forced to interact with an API from the position if API consumer which usually helps with designing cleaner API architecture
• Faster development - as all boilerplate code is automatically generated you won't have to write it, all that's left is developing business logic.
• Faster feedback loops - consumers can get a view of the API immediately and they can easier offer suggestions simply by modifying the spec

Let's develop our API in a spec-first approach!

I have a project that needs to get DSTU2 resources ultimately to CSV files. My thought was if I could get there Resources to R4 I could use the FHIR SQL builder to help map the data. Anyone have ideas? Maybe DSTU2 to SDA to R4...

Hi:

Had an issue after upgrading to 2021.1 where search bar for interoability will bring up "INVALID ACTION".

On upgrading to 2022.1 this still occurs.

It did not occur on another environement that was upgraded from 2017.2 straight to 2022.1

Is there any solution? Loads up SYS in url rather than customnamespacename

Issue is the url for instance brings through ip/csp/sys/EnsPortal.DTLEditor.zen?$NAMESPACE=X

We have a downstream application that cannot accept more than 500 messages at a time. They want to restrict the number of messages being sent to them at a time.

I would say it is a post of pain after years of using InterrSystems IRIS Docker images in many projects.

And I hope InterSystems will hear me and do something with it.

We have a lot of issues with Docker images, but I see no progress in solving them.

• containers.intersystems.com - any new releases substitute previous versions, makes build useless
  • ARM64 images have separate names, and it makes a pain to use them
• flags in iris-main, appears and disappears from version to version, which may fail the start the container
• healthcheck does not work as expected

Hi Community,

Let's meet together at the online meetup with the winners of the InterSystems Full Stack contest – a great opportunity to have a discussion with InterSystems Experts team as well as our contestants. Winners' demo included!

Date & Time: Friday, July 22 – 12:00 PM EDT

https://www.youtube.com/embed/m6GnLVJD23o
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Hello,

I found another question on how to change the language for Studio (but it would've been nice to have my actual language used - Ukrainian, since it's available, or was available). Still, I can't seem to figure out how to get rid of gibberish in the menu without changing the Windows settings:

Hi all,

I've just update the version of WebTerminal using the link, but now it doesn't work.

When call to /terminal is displaying the following error:

How do I access items and their settings of production by using Objectscript? I have already tried making SQL queries to Ens_Config.Production table and using methods in Ens.Director and EnsPortal.Utils classes but I just can't get a hang of it.