My votes

This is in reference to the settings that are stored on the production class and cannot be put in default settings. These are Pool Size, Enabled, Log Trace Events As an example, there are many business hosts that are enabled on Live regarding aler...

This protocol is the more efficien through HTTP than any other mechanism and it's appearing in conversations very often and also as a requirement in some interoperability projects in industrial sectors.

Provide an option in LOAD DATA to indicate a date/datetime format other than 'yyyy-mm-dd hh:mm:ss' i.e : LOAD DATA .../...USING{ "from": { "file": { "dateformat": "DD/MM/YYYY" } }}

As we are expanding to use HealthShare Provider Directory within our Environment, I do not see a tag within the Developer Community that could be used to tag posts within the Developer Community. Sort of like HealthShare, Health Connect, IRIS for ...

The integration of Developer Community AI (in different name) into the InterSystems IRIS documentation would enhance search efficiency and ease of access to relevant information, while also providing exposure to the Developer Community AI / Develo...

As we move some of our Provider build from a homegrown application to Health Share Provider Directory, there are some questions on how to handle data tags. Within our Provider build we had built a way to categorize "Conditions Treated" as a way to...

Within the Management Portal, you can explore classes, routines, and global and see when the last time a file had been touched. It would be nice if we could see this for Data Lookup (LUT) tables as well. Sometimes we start a project and testing go...

GM has no badge for writer of 100/150/200/250/300/400/500 articles, so it is important create it.

Currently, table tuning data is part of a class definition. Many of us are splitting routines and globals into different databases to keep the data and the code separate. This causes a problem because we have many situations where we want the same...

It would be much better if documentation would use some existing popular documentation framework not based on IRIS. Documentation does not need IRIS for running at all. Use normal search engine instead of useless irrelevant non-prerdictable search...