Hi developers!

Do you know a CRM that is built with InterSystems IRIS or Caché or Ensemble on a backend?

Has anyone been able to successfully implement a business service to pull files from Azure Blob storage?

Hello everybody...

Hi everybody!

Many developers prefer a dark version of applications. Not surprisingly, @Guillaume Rongier posted an idea of making a dark version for the Developer Community.

So we look forward to hearing from you.

Please send us your feedback by using this Poll on the Ideas Portal, and by voting and commenting on the relevant idea.

Thank you in advance for your votes and have a good day!

Hello community,

First of all thanks for reading this post:

Because of you are more experienced, pragmatic, and have a lot of knowledge and good know-how; please consider to read and answer some question, if you would like:

Why did you choose to become a software engineer / developer?

How and when did you start to generate a "flow state of mind" during your career?

Images for other languages are often build using multistage build process.

What about InterSystems IRIS?

Consider this Dockerfile:

FROM irishealth-community:2020.4.0.524.0 AS builder

# Load code into USER and compile
# Adjust settings, etc.

FROM irishealth-community:2020.4.0.524.0

# replace in standard kit with what we modified in first stage

COPY --from=builder /usr/irissys/iris.cpf /usr/irissys/.
COPY --from=builder /usr/irissys/mgr/IRIS.DAT /usr/irissys/mgr/.
COPY --from=builder /usr/irissys/mgr/user/IRIS.DAT /usr/irissys/mgr/user/.

The advantage of this approach is the image size.
The disadvantage is that on a final stage developer must know/remember all the modified places in the builder image.

But otherwise is this approach OK for InterSystems IRIS?
Have anyone tried to build IRIS images this way?

Hi All,

I am preparing for InterSystems IRIS Core Solutions Developer Specialist Certification. I have completed the desired syllabus. Does anyone have any questions dumps. I have already completed the practice paper on Intersystems website.

For standalone installations I always recommended to use custom namespaces and not the USER namespace.

However, what about Docker?

In many Dockerfiles I see the creation of additional namespace, but why, if only one namespace is required?

What do you think?

It's been a while (and everyone is well-rested after Advent Of Code!) so let's run another round of Code Golf.

Your task is navigating in a grid-like labyrinth in a clockwise spiral pattern. As it traverses the matrix, it collects characters, revealing a secret message.
Your challenge: find the shortest, most elegant code to decode this spiral cipher.
Input:
1. A multidimensional string array with comma separated characters (n x n)
2. Starting coordinates X and Y

Output:
The decoded message as a single string

Such most popular nowadays CI platforms as GitHub and Gitlab, offers the ability to run any docker image as a service, mostly useful for integration tests.

And I could define a GitHub workflow like this for instance, for some of my Python project which, requires the connection to IRIS

What does everyone think about submitting an issue in a repository and then submitting a pull request to fix that issue. Is it an unnecessary step or does it give extra context and logging for the issue? I ask this because when I find a bug in an Open Exchange app, I always submit the Issue and then often submit a Pull Request to fix the issue.

I think that if the repository owner doesn't like your suggested fix, it is helpful to have the issue around so that they can deny the pull request and potentially implement their own change for the issue.

Work Queue Manager (WQM) is a feature of InterSystems IRIS that enables you to improve performance by distributing work to multiple concurrent processes programmatically. The idea is that you split the work into chunks, and WQM distributes the chunks across worker processes and can provide the info that the work is done.

However, recently, I got an interesting question: there's a large logical transaction composed of ~1,000,000 individual objects and SQL inserts and updates. Some updates are CPU-intensive, so the original idea was to use WQM to split an update into chunks to speed things up.

But, here's a catch: if one of the individual 1,000,000 changes fails (there's a variety of application-level checks so that it can fail, and that's not even that abnormal a behavior), the entire transaction must be rolled back. That creates a problem: each chunk must report success before committing their individual transactions, and someone must get all these reports and decide if we are committing or not.

Unfortunately, it looks like WQM does not have a bidirectional communication between workers and manager, so I suggested an approach using events:

1. Start jobs.
2. Wait for all jobs to report success using $System.Event.WaitMsg().
3. Send Commit or Rollback using the $System.Event.Signal().

I usually receive complains from our customers about the BPL and DTL web pages automatic refreshes, it's a common problem among newbies users but for veteran developers too, they forget to save the changes regularly and automatically the web page is reloaded, losing all the work done.

Maybe an autosave would fix this problem that produces a deep feeling of hate and resentment against InterSystems technology among our customers. I've added an idea in our portal, so feel free to vote it!

Documentation here explains how IRIS Portal can be launched in a tab in the VS Code editing area from Server Manager. One limitation though is that if you then perform an action in Portal which needs to invoke a modal message box in the browser (e.g. window.alert() or window.confirm()) this doesn't work.