We love hearing from our users. Tell us what you want to see next and upvote ideas from the community. * Bugs and troubleshooting should as usual go through InterSystems support.
Lookup tables provide a much needed configuration ability that allows us to use different values for different namespaces. However they are not audited so there is no way to track who changed what and when. Please audit them so we can see the chan...
Stella Ticker
almost 2 years ago
in InterSystems IRIS
0
Future consideration
Ukrainian translation is also quite horrendous. In some places you can see placeholders instead of words, so it's not even remotely clear what is going on and what is or needs to be done. Studio suffers the most.
Iryna Mykhailova
about 2 years ago
in InterSystems IRIS
0
Future consideration
Hi, as a Developer it is very challenging to troubleshoot a code issues when the documentation provided does not include potential or common error scenarios and examples of code to use to resolve those issues. For other vendors like Microsoft, I a...
Carmelita Resh
about 2 years ago
in Documentation
0
Future consideration
The current spanish translation of IRIS products is...horrible, it's so literal that the most of the time you don't understand the functionality. A lot of concepts used in IRIS are perfectly in english and is not necessary a translation, for examp...
Luis Angel Pérez Ramos
about 2 years ago
in InterSystems Products
0
Future consideration
For community articles, let admins (and possibly article authors) pin particular comments to the top
Sometimes, particular comments on a DC article offer crucial insight that people should. Allowing authors or DC admins to be able to pin this to be the first comment after the article (or perhaps even above it?) so that they make sure that people ...
Jonathan Sue-Ho
about 2 years ago
in Community
1
Future consideration
Add address standardization to Normalization (using Project US@ standards)
Standardizing the address fields would improve autolinking and save time spent on manual review. By using the US@ standards, it would improve interoperability and data sharing. Minutes from the April 2021 meeting are attached. See ONC for further ...
Add the option to call class parameters in Embedded Python
Currently, class parameters can be called in ObjectScript in the following way: write ..#ParameterName The same construction in Embedded Python looks like this: import irisprint(iris.cls('ClassName')._GetParameter("ParameterName") Could it be simp...
Evgeny Shvarov
about 2 years ago
in InterSystems IRIS
0
Future consideration
A Dynamic Cheat Sheet to lookup for Common Core Functions for Reusability
When developing Region or site level codes, sometimes we tend to create our own functions to complete it; But what if there is a core function which does the same thing and you didn't know of. Below advantages can be achieved if the common core fu...
Shareek Ahamed
about 2 years ago
in InterSystems IRIS
3
Future consideration
Adapting tools for people with special needs and/or disabilities 🌐🔰🦽🦼♿
Blind people, people with reduced mobility, people with color blindness, autistic people, people with Asperger's syndrome, human beings with Parkinson's disease, or missing a hand and/or fingers.
Can Intersystems tools be adapted to them? Do you ...
Where a system is using user based licensing the allocation is first come first served. If there are dynamic connections, such as web based applications, it would be useful to reserve a license for a specific license ID to ensure availability. Thi...
David Underhill
about 2 years ago
in InterSystems IRIS
0
Future consideration