Search

The 24th contest was dominated by already well know winners+ 3 new winning contributors GROWTH: 8,6%Participation by my 5 regions: as: 1, br: 4, eu: 4+1new, us: 1+2new, ru: 5, total:18 With is distribution: Prizes USD Region Prz 8 9200 ru 37.4% 7 6200 eu 25.2% 7 4700 br 19.1% 2 3500 as 14.2% 5 1000 us 4.1% This results over all 24 contests into: Prizes USD Region Prz 95 72870 br 40.3% 48 51625 ru 28.6% 34 25900 eu 14.3% 15 19325 as 10.7% 14 11000 us 6.1% The Top 6 performing winners: And all winner's profiles over 24 contests: The related package is updated on OEX and ODS. GitHub Just curious, how do you count me, since I've moved to UAE, a few contests ago You are still counted with RU as at beginning of the contests.I didn't split your identity. I had rumors that you are contracted in UAR.

Hey Community, We're thrilled to invite you to the next "InterSystems Iberia Summit 2022", which will be held in-person once again. Registration is already open! Join us in this important event where we'll bring together InterSystems customers and partners and also employees and members of the Developer Community - to learn, inspire and share innovation challenges with each other: ➡️ InterSystems Iberia Summit 2022 🗓 November 16 – 17, 2022 📍Valencia. The Westin Valencia hotel At the InterSystems Iberia Summit, you will be able to share challenges and priorities. And you will learn how InterSystems technology is making the digital transformation a reality while allowing and boosting innovation. We'll publish the agenda with prominent speakers, topics, and workshops soon. And there will be great surprises at the Developer Community Corner. See you in Valencia! ➡️ Registration is open at: www.intersystems.com/es/iberia-summit-2022 worth to go! I wish I would go

Hey Community, We're very pleased to present to you our brand new About Us pages! Please welcome: 📍 Our Team 📍 InterSystems Developer Ecosystem Overview So... Let's meet the Team! These are the people that make the magic happen ✨ Please feel free to contact us – we are here to make the Community a better place for developers! In addition, don't miss your chance to get to know all our regional teams: ES DC team PT DC team JP DC team CN DC team FR DC team And... 🤩 Let's meet our InterSystems Developer Ecosystem overview page! Here you can see a clear and simple overview of our related portals and resources where you can find lots of exciting and helpful stuff: How to find these pages? Go to the "About Us" section from the top menu: Hope you enjoy our brand new pages! Feel free to share your feedback in the comments ;)

Hi Community, Watch this video to learn the basics of how to use the InterSystems® command line interface to execute commands, including starting the Terminal, executing methods and routines, and exiting the Terminal. ⏯ Using the InterSystems Terminal Subscribe to InterSystems Developers YouTube to stay up to date!

Hi Community, Enjoy watching the new video on InterSystems Developers YouTube: ⏯ Introduction to InterSystems Products Get an introduction to the InterSystems IRIS data platform and InterSystems IRIS for Health, InterSystems Caché and Ensemble, the HealthShare family of products, and InterSystems TrakCare. See what each product has to offer and how they relate to each other. Enjoy the video and stay tuned for more! 👍

SCOPE OF SERVICES: The Database Developer’s responsibilities will include, but are not limited to:• To perform support and maintenance of existing Cache code• Analysis and migration of existing Cache code to Microsoft SQL; and Web Services (SOA) REQUIRED SKILLS/EXPERIENCE: A minimum of 5 proven years of experience in computer applications development planning, design, troubleshooting, integration, maintenance, and enhancement of Cache Database applications. Related required skills:• Object Script• Cache Routines, Queries, Class Methods• SQL• Globals• RedHat Linux Excellent communication skills and experience in handling confidential information US Citizenship only: Yes Job Type: Contractor Hybrid Position. 4 Days in the Kew Gardens NY office and one day remote. $$$: DOE ($60-$70/hour) Work hours: 9AM to 5PM (~35 hours weekly). Email consideration to with Resume (must have) to pbrown@cybercodemasters.com

InterSystems team is heading to MIT's largest hackathon this weekend where we will introduce a tech challenge for hackers.We offer hackers to use IntegratedML or InterSystems Supply Chain Orchestrator in their projects in order to compete for some really cool prizes! If you are in Boston and would be interested to be an InterSystems mentor at the event - drop me a line. UPDATE: We have our amazing winners! Check out these projects: First Place – Fluxus Description | GitHub Second Place – Carta Description | GitHubThird Place – Manifest Description | GitHub Thanks to everyone who took part in InterSystems Challenge!Don't forget to join our Discord Server to stay in touch and receive notifications on upcoming InterSystems programming contests! We are looking forward to seeing new creative projects! Stay tuned for the winners announcement on September 18. Learn more about this hackathon at HackMIT official website. Looking forward to seeing who the winners of the InterSystems awards are 😀 Thank you, Sylvain!We now have the 3 winning teams! I updated the post with links to their projects 🤩

Hello Community, Welcome to our first InterSystems Ideas News! The most important piece of news is the result of our very first and very successful Idea-A-Thon Contest. We've received 75 new interesting ideas. Some general stats of the Ideas Portal: ✓ 42 new ideas published last month✓ 147 new users joined last month✓ 142 ideas posted all time✓ 273 users joined all time The top 5 most voted for ideas of the month: IRIS and ZPM(Open Exchange) integration Move users, roles, resources, user tasks, Mappings (etc) to a seperate Database, other than %SYS, so these items can be mirrored RPMShare - Database solution for remote patient monitoring (RPM) datasets of high density vitals Create front-end package based on CSS and JS to be used in NodeJS and Angular projects PM platform And to round up this newsletter, here is a list of all ideas posted last month Add IRIS as a supported database for Apache Superset For community articles, let admins (and possibly article authors) pin particular comments to the top Add address standardization to Normalization (using Project US@ standards) PM platform Tool to convert legacy dot syntax code to use bracket syntax TTTC PDF reports for IRIS BI Sample code share opportunity Add basic tutorial of Docker or point to a Docker tutorial in Documentation The ability to export current settings to a %Installer Manifest Move users, roles, resources, user tasks, Mappings (etc) to a seperate Database, other than %SYS, so these items can be mirrored Common Data Modelling CI/CD support String format to numeric values in ZEN.proxyObject Patient Initiated Follow Up - Adding a document to an ROPWL I service Flags Linking I service to JIRA system Linux: iris session [command line] get commands from a file Journal file analysis/visualization Add the option to call class parameters in Embedded Python Create query builder Colour Background on Ward / Clinical Areas Floorplans A Dynamic Cheat Sheet to lookup for Common Core Functions for Reusability Version History for Classes Add wizard to create class with its properties RPMShare - Database solution for remote patient monitoring (RPM) datasets of high density vitals Better handle whitespace in Management Portal Text entry IRIS and ZPM(Open Exchange) integration Visual programming language Backup button before importing Adapting tools for people with special needs and/or disabilities 🌐🔰🦽🦼♿ Reserve licenses Interoperability Wizard Improve journal display in IRIS admin portal Create front-end package based on CSS and JS to be used in NodeJS and Angular projects Mirror Async Member Time Delay in Applying Journals Cache Journal Switch Schedule Monitoring and Programatic way of Starting/Stoping Gateways Embedded Python: Add a built-in variable to represent class LDAP Authentication method by default on Web Applications Please add google oauth authorization to login to the management portal Data Analyzer That's it for now. Visit our InterSystems Ideas portal, suggest your ideas and vote for the existing ones! Look out for the next announcement!

Hi Developers, We're pleased to announce that InterSystems is hosting its partner days in Germany – InterSystems Partnertage DACH 2022! During this time you will be able to exchange product innovations and practical tips and tricks between InterSystems experts and your colleagues in Darmstadt. And of course, a lot of networking, because there is a lot to catch up on! 🗓 Dates: November 23-24, 2022 📍 Venue: Wissenschafts- und Kongresszentrum darmstadtium in Herzen DarmstadtsSchloßgraben 1, 64283 Darmstadt The agenda of the two-day partner days consists of a mix of keynotes, informative sessions, and masterclasses. Read on for more details. The agenda at a glance: November 23 (focus on healthcare): Innovations in healthcare Transferring innovative ideas into concrete projects – with InterSystems technology Outlook on the next development steps for InterSystems HealthShare and InterSystems IRIS for Health Masterclass sessions with our Sales Engineering team (InterSystems SAM, Embedded Python for ObjectScript developers) November 24: Keynotes on the successful cross-industry use of InterSystems technologies Our innovative data management concept „Smart Data Fabric“ – what is it all about? Round Table „migration on InterSystems IRIS“ – our partners share their experiences Presentations and live demos focusing on the following key topics: Columnar Storage, IntegratedML, Container-Support, InterSystems Reports Masterclass sessions on „social selling“ ✅ REGISTER HERE We look forward to seeing you in Darmstadt!

We're electrified to invite all our clients, partners, developers, and community members to our in-person InterSystems Global Summit 2023! Our Global Summit user conference is your opportunity to connect with trailblazing product developers, fellow users pushing our technology into new frontiers, and the people whose out-of-box thinking is rocking our universities and board rooms. All in the same space. And registration is now open! ➡️ InterSystems Global Summit 2023 🗓 Dates: June 4-7, 2023 📍 Location: The Diplomat Beach Resort, Hollywood, Florida, USA Join us this year for content on how customers like you use our technology for innovation and what trends affect our future innovations, including new and enhanced products and product offerings. Here is a short glimpse at the agenda. Sunday, June 4 Golf Outing or Morning Social ActivitiesBadge Pick-upTechnology BootcampCertification ExamsWomen's MeetupWelcome Reception Monday, June 5 Welcome and KeynotesBreakout SessionsHealthcare Leadership ConferencePartner Pavilion 1:1 MeetingsCertification ExamsFocus GroupsTech ExchangeAffinity SessionsEvening Drinks & Demos Tuesday, June 6 KeynotesBreakout SessionsPartner Pavilion 1:1 Meetings Certification Exams Focus GroupsTech ExchangeAffinity SessionsEvening Social Event Wednesday, June 7 Keynotes Breakout Sessions Partner Pavilion 1:1 Meetings Certification ExamsFocus Groups Tech Exchange Farewell Reception For more information on the agenda please visit this page. We look forward to seeing you at the InterSystems Global Summit 2023!

Hi folks! Those who actively use unittests with ObjectScript know that they are methods of instance but not classmethods. Sometimes this is not very convenient. What I do now if I face that some test method fails I COPY(!) this method somewhere else as classmethod and run/debug it. Is there a handy way to call the particular unittest method in terminal? And what is more important, a handy way to debug the test method? Why do we have unittest methods as instance methods? VSCode has a way to help with running tests, but it requires implementing from our side A handy way to call UnitTest Case method in a terminal Do ##class(%UnitTest.Manager).DebugRunTestCase("", "[ClassName]", "", "[MethodName]") Run all Test methods for a TestCase: Do ##class(%UnitTest.Manager).DebugRunTestCase("", "[ClassName]", "", "") Placing a "break" line within a method can be useful when iterating creating the test. See the variables. Run other code and then type "g"+ [Enter] to continue. The instance gives context to current test run, when raising assertions and other functionality. Thanks, Dima! Is there a listed related issue? Thanks Alex. See the following: USER>Do ##class(%UnitTest.Manager).DebugRunTestCase("", "dc.irisbi.unittests.TestBI", "", "TestPivots") (root) begins ...LogStateStatus:0:Finding directories: ERROR #5007: Directory name '/usr/irissys/mgr/user/u:/internal/testing/unit_tests/' is invalid <<==== **FAILED** (root):: In fact there is a handy way to run all the tests via: zpm "test module-name" But, I'd love to see debugging of it @Alex.Woodhead , do you know by a chance why unittest methods are instance methods but not classmethods? Could it be converted to classmethods or provided the option to do that? Hi Evgeny, The global ^UnitTestRoot needs to be set to a real directory to satisfy the CORE UnitTest Runner. As the first argument "Suite" is not specified, then no sub-directories are needed. Set ^UnitTestRoot="\tmp\" ... may be sufficient for your purposes. It is common to need to run unit tests for other modules that have overlapping / breaking functionality. This is where the value of loading and running multiple TestSuites comes into its own. There are no reasons for them to be ClassMethods, UnitTests is quite a complex thing, and it's there are use-cases where it needs to be this way. with zpm you can use additional parameter for it zpm "test module-name -only -D UnitTest.Case=Test.PM.Unit.CLI:TestParser" Use class name only to run all tests there, or add Method name to test only that method in the class Thanks! this is helpful. @Evgeny.Shvarov I have a detailed writeup here (although Dmitry already hit the important point re: IPM): https://community.intersystems.com/post/unit-tests-and-test-coverage-objectscript-package-manager A few other notes: Unit test class instances have a property (..Manager) that refers to the %UnitTest.Manager instance, and may be helpful for referencing the folder from which unit tests were loaded (e.g., to load additional supporting data or do file comparisons without assuming an absolute path) or "user parameters" / "user fields" that were passed in the call to run tests (e.g., to support running a subset of tests defined in unit test code). Sure, you could do the same thing with PPGs or % variables, but using OO features is much better. I'll also often write unit tests that do setup in OnBeforeAllTests and cleanup in %OnClose, so that even if something goes very horribly wrong it'll have the best chance of actually running. Properties of the unit test are useful to store state relevant to this setup - the initial $TLevel (although that should always be 0), device settings, global configuration flags, etc. Thanks Tim! How do you debug a particular unit test in VSCode? Unit testing from within VS Code is now possible. Please see https://community.intersystems.com/post/intersystems-testing-manager-new-vs-code-extension-unittest-framework thanks, @John.Murray ! Will give it a try! Why are unit test methods instance methods? Since a running unit test is an instantiated object (%RegisteredObject), the unit test class itself can have custom properties, and the instance methods can use those properties as a way to share information. For example, initialize the properties in %OnBeforeAllTests(), and then access/change the properties in the test methods. 💡 This question is considered a Key Question. More details here. @Evgeny.Shvarov my hacky way of doing this is to create an untracked mac file with ROUTINE debug defined. I just swap in the suite or method I want to run per Alex's instructions, set my breakpoints in VS code and make sure the debug configuration is in my VSCode settings: "launch": { "version": "0.2.0", "configurations": [ { "type": "objectscript", "request": "launch", "name": "debugRoutine", "program": "^debug" } ] } That's indeed hacky! Thanks @Michael.Davidovich! Thanks @Joel.Solon! But all this could be achieved without instance methods, right? Anyway, I'm struggling to find an easy way to debug a failed unittest. @Michael.Davidovich suggested the closest way to achieve it but I still want to find something really handy, e.g. an additional "clickable button" in VSCode above the test method that invites "debug this test method". Similar what we have for class methods now - debug this classmethod and copy invocation. That'd be ideal. That's one of the things the new extension is designed to achieve. I am utilizing properties on class methods to good effect. I would not use a classmethod only approach for normal development. There is nothing stopping a community parallel UnitTest.Manager re-implementation that follows a ClassMethod pattern. Some have reimplemented UnitTest.Manager: 1) Without Deleteing the test classes at end of run (With Run instead of DebugRun) 2) Not needed ^UnitTestRoot to be defined. Looking forward! Anything can be achieved without instance methods. The point here is that instance methods exist in object-oriented systems because they are considered a good, straightforward way to achieve certain things. In the case of unit tests sharing information using properties, that approach saves you from having to pass info around as method arguments, or declaring a list of public variables. I understand the argumentation, makes sense. Just curious how do you debug those unittests that fail?

Hi Developers! Welcome to the 5th issue of the InterSystems Ideas News! This time you can read about: ​​​​✓ Hall of Fame - a new page on the Ideas Portal ✓ Integration with Global Masters - get points for your ideas ✓ List of ideas that are planned for implementation 11 developers have already implemented ideas from the Ideas Portal. We created a new dedicated page on InterSystems Ideas to pay tribute to these heroes. The Hall of Fame lists: names of implemented ideas, developers who implemented ideas, implementation names with links to more information. You can implement one of Community Opportunity ideas and your name will be in the Hall of Fame! About a month ago, developers who submitted product ideas started getting points for these ideas. We would like to share that since 22 February, the authors have received a total of 18,200 Global Masters points for the following ideas 15 product ideas that were posted, promoted, or implemented: Cross-production Interoperability Messages, Service and Operation by @Stefan.Cronje1399 Additional Data Types for ISC Products by @Stefan.Cronje1399 Change data capture from IRIS to kafka using SQL commands by @Yuri.Gomes Allow graphical editing of Interoperability components BPL, DTL and Business Rules in VS Code by @Steve.Pisani Examples to work with IRIS from Django by @Evgeny.Shvarov Install python and java libraries from ZPM and Installation Manifest (%Installer) by @Yuri.Gomes Set password through environment variable by @Dmitry.Maslennikov Add a project that helps to generate unittests for an ObjectScript class by @Evgeny.Shvarov Create a UI for convenient and easy transfer of projects (classes, globals, applications, users, roles, privileges, grants, namespace mapping, SQLgateways, libraries, etc.) to other system instances for fast deployment. by @MikhailenkoSergey Add a wizard similar to the SOAP wizard to generate a REST client from OpenAPI specification by @Jaime.Lerga Public API for access to shared memory by @Alexey.Maslov Fold code on loops and If's on studio by @Heloisa.Paiva Chat bot to help with TrakCare customization/settings by Sumana Gopinath Iterative build of TrakCare configuration/code tables utilising FHIR and HL7 Messaging. by Linda McKay BPL, DTL, Business Rule Editor in VSCode by @Cristiano.Silva Post your great ideas and get points for them! And to round up this newsletter, here is the list of ideas that are planned for implementation Publish the InterSystems IRIS Native SDK for Node.js on npm by @John.Murray Move users, roles, resources, user tasks, Mappings (etc) to a seperate Database, other than %SYS, so these items can be mirrored by @Sean.O'Connor1391 Please add google oauth authorization to login to the management portal by @Aleksandr.Kolesov InterSystems Ideas - Long Term by @Vinay.Purohit3109 BPL, DTL, Business Rule Editor in VSCode by @Sawyer.Butterfield Add Favorites in GM by @Irène.Mykhailova LIMIT OFFSET support for IRIS SQL by @Dmitry.Maslennikov Introduce WITH into IRIS SQL engine by @Evgeny.Shvarov Security settings for mirror configurations by @Evgeny.Shvarov A modern management portal to manage InterSystems IRIS by @Evgeny.Shvarov copy/sync system configurations and user accounts between IRIS instances by @Evgeny.Shvarov Jupyter Notebook by Guest Stay creative, post your great ideas on InterSystems Ideas, vote and comment on existing ideas! Hi Community! I want to say special thanks to the developers who implemented the ideas from InterSystems Ideas: @Lorenzo.Scalese@Robert.Cemper1003 @MikhailenkoSergey @Dmitry.Maslennikov @Evgeniy.Potapov @henry @Henrique @José.Pereira @Yuri.Gomes @Evgeny.Shvarov @Guillaume.Rongier7183 Your names are on the special Hall of Fame page!  Many thanks

When IRIS 2023.2 reaches general availability, we’ll be making some improvements to how we tag and distribute IRIS & IRIS for Health containers. IRIS containers have been tagged using the full build number format, for example 2023.1.0.235.1. Customers have been asking for more stable tags, so they don’t need to change their dockerfiles/Kubernetes files every time a new release is made. With that in mind, we’re making the following changes to how we tag container images. Major.Minor Tags: Containers will be tagged with the year and release, but not the rest of the full build number. For example, where an image is accessed currently as containers.intersystems.com/intersystems/iris:2023.2.0.606.0 Will now be accessed as containers.intersystems.com/intersystems/iris:2023.2 latest-em and latest-cd Tags: The most recent extended-maintenance and continuous-delivery releases will be tagged with latest-em and latest-cd, respectively. This provides a shorthand notation that can be used in documentation, examples, and development environments. We do not advise using these tags for production environments. Preview: Developer preview releases will all be clearly tagged with -preview so you can easily separate out pre-release containers from production-ready containers. The most recent preview release will helpfully be tagged with latest-preview. If you’re looking for the full build number for an InterSystems container, that’s available as a label, which you can view with the docker inspect command. For example: docker inspect --format '{{ index .Config.Labels "com.intersystems.platform-version"}}' containers.intersystems.com/intersystems/iris:2023.1.0.235.1 Containers will no longer be distributed via the WRC download site. If you’re one of the few customers downloading containers from the WRC download site, now’s the time to switch to the InterSystems Container Registry (docs). While we’re here, as a reminder that we have been publishing multi-architecture manifests for IRIS containers. This means that pulling the IRIS container tagged 2022.3 will download the right container for your machine’s CPU architecture (Intel/AMD or ARM). If you need to pull a container for a specific CPU architecture, tags are available for architecture-specific containers. For example, 2022.3-linux-amd64 will pull the Intel/AMD container and 2022.3-linux-arm64v8 will pull the ARM container. We’ll stop posting to the iris-arm64 repositories soon since multi-architecture streamlines the process of getting the right containers on the right machines. If you have questions or concerns, please reach out to the WRC. Hi Bob, That's good news and I like new names much more than old ones. I hope old tags for old releases will still be available? A couple of entries from my container tagging wishlist (one can dream, you know) - provide :latest tag for all containers, but especially for community ones, which will just pull the latest working release without having to rebuild dockerfiles every year when license expires - provide 2023.1.x tag which will follow the latest minor version 🎉, great news ! I join Sergei on latest tag in addition of latest-cd and latest-em. Awesome! Please add latest too. Great improvements! Looking forward to it, Bob. - provide 2023.1.x tag which will follow the latest minor version It's not clear to me whether or not this is already the plan for the new Major.Minor tags. For instance, when IRIS 2024.1.1 is released, will it be at containers.intersystems.com/intersystems/iris:2024.1 (where IRIS 2024.1.0 images would likely have existed previously) or containers.intersystems.com/intersystems/iris:2024.1.1? @Robert.Kuszewski can you please clarify? The plan for new IRIS containers is to use YYYY.R format only. Let's walk through an example of a few releases for a hypothetical IRIS 2024.1 release. Release Old Tag New Tag Initial GA 2024.1.0.123.0 2024.1 First maintenance 2024.1.1.234.0 2024.1 Security Fix 2024.1.1.234.1 2024.1 This new scheme greatly simplifies your work to keep up with whatever mix of maintenance and security releases we provide. All you need to do is reference iris:2024.1 and you'll pick up the latest bug and security fixes without making any changes to your code. As for the latest tag, we like the idea so much that we're giving you two. One that lets you get the latest release (iris:latest-cd) and one that lets you get the latest long-term-support release (iris:latest-em). You also can use intersystemsdc/iris-community:latest or just intersystemsdc/iris-community for the latest InterSystems IRIS Community Edition release. And intersystemsdc/iris-community:preview for the latest preview build. intersystemsdc/irishealth-community and intersystemsdc/irishealth-community:preview for InterSystems IRIS For Health Community Edition Well you gave me two so I should have one spare wish :) Make iris:latest-cd just iris:latest, this way we can just skip the "latest" bit altogether and just use iris without any tag at all. Already some time since the last post...I appreciate the way of dealing with the tags although I'm used to the way this is done i.E. in docker hub where every provided image is listed with its actual build-number so you can see, which image exactly is "latest" or which version is delivered when you only ask for a mayor-release-tag. If there is a bug in a certain minor-version I cannot see easily if there is a never minor version provided with a docker image. Therefore I have to search through the release notes to see if / when an image of the new version is released or I have to pull the last image of the mayor-version (some GB!) and inspect it.Perhaps this scenario seems a little "constructed"? We just had to deal with it . In short: With only mayor-version-tags we have to rely in Intersystems that 1. there is always the latest release of an application provided as docker image as well and 2. that there are no new bugs in a newer version (because we can't stick to a certain build). For production environments with high availability I recommend to use a private registry for Iris etc. and tag the images so we can determine when to upgrade. How do other deal with this (or am I just paranoid?) I recently got an answer from the WRC confirming that In the YYYY.R docker image is always the latest release of the given version. So we only have to lookup which is the latest release of a version to know which exact version to expect when pulling an image. With these changes, to have just latest, latest-preview, it's hard to get how old the the image on InterSystems Containers Registry It would be nice to see the date of the image is uploaded and have somewhere sorting by date Hi, Pulling the irishealth:latest-em fails with dangling manifests (looks like). docker pull containers.intersystems.com/intersystems/irishealth:latest-emlatest-em: Pulling from intersystems/irishealtha271f97708e3: Pull complete6d17179b85a7: Downloading [==================================================>] 272.8MB/272.8MB0a3eeb0be045: Waitingae9eda793928: Waitingcda3cca218dc: Waiting7858487e277f: Waitingunexpected EOF Did any get this error? Thanks, JB

Hello Community! Welcome to the new edition of the InterSystems Ideas News! Learn what we've been up to this past couple of weeks. Curious about what is going on with all the great ideas you've been submitting to our InterSystems Ideas Portal? Here is the current status breakdown: ✓ 58 ideas are being triaged by InterSystems Product Managers. ✓ 43 ideas can be implemented by Developer Community members. ✓ 11 ideas are being implemented by InterSystems. ✓ 2 ideas are already implemented by InterSystems. ✓ 9 ideas are implemented by Developer Community members. To make it clearer what stages your ideas are going through here is the diagram: And to round up this newsletter, here is a list of ideas posted after Idea-A-Thon Improve Ukrainian translation in IRIS Code example Full Code Debugger Promote video contest Create a tool for IRIS BI to test all the pivots and dashboards if they still work after changes made Improve Spanish translation in IRIS Add IRIS as a supported database for Apache Superset For community articles, let admins (and possibly article authors) pin particular comments to the top Add address standardization to Normalization (using Project US@ standards) A tiny reminder, you can filter ideas by status, post new ideas for public discussion, vote for existing ideas, and comment on them on our InterSystems Ideas Portal! Stay tuned for the next InterSystems Ideas news bulletin and get creative in the meantime! Hello Community! Several users have asked me why the number of ideas in some statuses they see in the InterSystems Ideas is different from the number I mentioned in the news bulletin.I will try to explain it in this comment. Experts analyze your ideas daily. Thus, the status of analyzed or implemented ideas changes. In general, the number of ideas in the "Needs review" status is decreasing. And the number of ideas implemented by InterSystems and ideas that can be implemented by members of the Developer Community is increasing. Have a nice day. Vadim. Hello Community! I want to inform you that InterSystems Ideas now has a Portal Guide. The Portal Guide contains: information about the Ideas Portal goal, a complete list of ideas statuses, some links related to the portal. Please share your thoughts here or @Vadim.Aniskin about what else we can add there. Have a nice day, Vadim.

Hey Developers, We'd like to invite you to join our next contest dedicated to creating useful tools to make your fellow developers' lives easier: 🏆 InterSystems Developer Tools Contest 🏆 Submit an application that helps to develop faster, contributes more qualitative code, and helps in testing, deployment, support, or monitoring of your solution with InterSystems IRIS. Duration: January 23 - February 12, 2023 Prize pool: $13,500 The topic 💡 InterSystems IRIS developer tools 💡 In this contest, we expect applications that improve developer experience with IRIS, help to develop faster, contribute more qualitative code, help to test, deploy, support, or monitor your solution with InterSystems IRIS. General Requirements: Accepted applications: new to Open Exchange apps or existing ones, but with a significant improvement. Our team will review all applications before approving them for the contest. The application should work on InterSystems IRIS Community Edition. Types of applications that match: UI-frameworks, IDE, Database management, monitoring, deployment tools, etc. The application should be an Open Source application and published on GitHub. The README file to the application should be in English, contain the installation steps, and contain either the video demo or/and a description of how the application works. One developer can enter the competition with a maximum of 3 applications. Prizes 1. Experts Nomination - a specially selected jury will determine the winners: 🥇 1st place - $5,000 🥈 2nd place - $3,000 🥉 3rd place - $1,500 🏅 4th place - $750 🏅 5th place - $500 🌟 6-10th places - $100 2. Community winners - an application that will receive the most votes in total: 🥇 1st place - $1000 🥈 2nd place - $750 🥉 3rd place - $500 If several participants score the same amount of votes, they all are considered winners, and the money prize is shared among the winners. Important Deadlines: 🛠 Application development and registration phase: January 23, 2023 (00:00 EST): Contest begins. February 5, 2023 (23:59 EST): Deadline for submissions. ✅ Voting period: February 6, 2023 (00:00 EST): Voting begins. February 12, 2023 (23:59 EST): Voting ends. Note: Developers can improve their apps throughout the entire registration and voting period. Who can participate? Any Developer Community member, except for InterSystems employees. Create an account! 👥 Developers can team up to create a collaborative application. Allowed from 2 to 5 developers in one team. Do not forget to highlight your team members in the README of your application – DC user profiles. Helpful resources ✓ Example applications: iris-rad-studio - RAD for UI cmPurgeBackup - backup tool errors-global-analytics - errors visualization objectscript-openapi-definition - open API generator Test Coverage Tool - test coverage helper and many more. ✓ Templates we suggest to start from: iris-dev-template rest-api-contest-template native-api-contest-template iris-fhir-template iris-fullstack-template iris-interoperability-template iris-analytics-template ✓ For beginners with IRIS: Build a Server-Side Application with InterSystems IRIS Learning Path for beginners ✓ For beginners with ObjectScript Package Manager (ZPM): How to Build, Test and Publish ZPM Package with REST Application for InterSystems IRIS Package First Development Approach with InterSystems IRIS and ZPM ✓ How to submit your app to the contest: How to publish an application on Open Exchange How to submit an application for the contest Need Help? Join the contest channel on InterSystems' Discord server or talk with us in the comment to this post. We can't wait to see your projects! Good luck 👍 By participating in this contest, you agree to the competition terms laid out here. Please read them carefully before proceeding. What a contest! It'd be great if someone could implement the tool to export Interoperability components into a local folder with every changes saved in the interoperability UI? Currently git-source-control can do the job, but it is not complete. Some Interoperability components (e.g. business rules) are not being exported. And lookup tables are exported in an not importable format. I published and idea regarding it. For your inspiration see also the ideas with the "Community Opportunity" status on the Ideas Portal. Here're more ideas for your inspiration by @Guillaume.Rongier7183: https://community.intersystems.com/post/kick-webinar-intersystems-developer-tools-contest#comment-212426 @Evgeny.Shvarov as we've covered in GitHub issues, the business rule issue is a product-level issue (in the new Angular rule editor only, not the old Zen rule editor). I clarified https://github.com/intersystems/git-source-control/issues/225 re: the importable format. The non-"wrapped" XML export format is importable by git-source-control and, I believe, IPM itself, although not by $System.OBJ.Load. It's just a matter of preference/readability. In a package manager context being loadable by $System.OBJ.Load isn't as important, and while the enclosing <Export> and <Document> tags aren't as annoying for XML files as for XML-exported classes/routines/etc., they're still annoying and distract from the true content of the document. Also - git-source-control 2.1.0 fixes issues with import of its own export format. You should try it out. ;) nice job Tim! Thank you for continuing to improve this :) Hey Developers, Watch the recording of the Kick-off Webinar on InterSystems Developers YouTube: ⏯ [Kick-off Webinar] InterSystems Developer Tools Contest Community! There are 5 apps that have been added to the contest already! GlobalStreams-to-SQL by @Robert.Cemper1003 helper-for-objectscript-language-extensions by @Robert.Cemper1003 gateway-sql by @MikhailenkoSergeyxml-to-udl by @Tommy.Heyding iris-persistent-class-audit by @Stefan.Cronje1399 Who's the application going to be next?! Dear Developers! Please use technology bonuses to collect more votes and get closer to victory. 🥳 Happy coding!✌ I am now in the running with DX Jetpack for VS Code Hi Evgeny, The ompare tool has a Schedule option that happily exports classes, routines, productions, lookup tables, HL7 schemas. It can be configured to traverse multiple namespaces in a single run, generating an export file for each namespace. Wonder if this is useful for your case. A periodic export / snapshot of some components. Cheers, Alex Devs! Four more applications have been uploaded to the contest! DX Jetpack for VS Code by @John.Murray JSONfile-to-Global by @Robert.Cemper1003 apptools-admin by @MikhailenkoSergey irissqlcli by @Dmitry.Maslennikov Check them out! I just uploaded my app... It is the first time that I participate in one of the programming contests... I hope you like it. my helper was eliminated today by censorshelper-for-objectscript-language-extensionsTag version: 0.0.3 Released: 2023-01-26 22:33:33