Find

Announcement
· Nov 6

InterSystems "Bringing Ideas to Reality" Contest 2025

Hi Developers,

Following the resounding success of last year's new contest, we decided to repeat it. Please welcome 

🏆 Bringing Ideas to Reality Contest 🏆

Submit an application that implements an idea from the InterSystems Ideas Portal that has status Community Opportunity or Future Consideration, created before the publication of this announcement, and requires doing the actual programming 😉

Duration: November 17 - December 7, 2025 December 14, 2025 (the submission period extended until December 7)

Prize pool: $12,000


The topic

In this contest, we expect applications that implement any idea from the InterSystems Ideas Portal with a status of Community Opportunity or Future Consideration that was created before the publication of this announcement.

General Requirements:

  1. The application or library must be fully functional and original. It cannot be a simple import or direct interface to an existing library in another language (with the exception of C++, where creating an IRIS interface requires significant work). It must not be a copy-paste of an existing project, nor include any proprietary code. It can't use the results of reverse engineering of InterSystems or any other company's products. Read more about it here.
  2. Only new applications are accepted
  3. The application should work either on IRIS Community Edition or IRIS for Health Community Edition. Both could be downloaded as host (Mac, Windows) versions from the Evaluation site, or can be used in the form of containers pulled from InterSystems Container Registry or Community Containers: intersystemsdc/iris-community:latest or intersystemsdc/irishealth-community:latest .  
  4. The application should be Open Source and published on GitHub or GitLab.  
  5. The README file for 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.
  6. Only three submissions from one developer are allowed.
  7. Different applications that implement the same idea from different programmers/teams are accepted.

NB. Our experts will have the final say on whether the application is approved for the contest, based on the criteria of complexity and usefulness. Their decision is final and not subject to appeal.

Prizes

1. Experts Nomination - a specially selected jury will determine winners:

🥇 1st place - $5,000 
🥈 2nd place - $2,500 
🥉 3rd place - $1,000
🏅 4th place - $500
🏅 5th place - $300
🌟 6-10th places - $100

2. Community winners - applications that will receive the most votes in total:

🥇 1st place - $1,000 
🥈 2nd place - $600 
🥉 3rd place - $300
🏅 4th place - $200
🏅 5th place - $100

❗ If several participants score the same number of votes, they are all considered winners, and the prize money is shared among the winners.
❗ Cash prizes are awarded only to those who can verify their identity. If there are any doubts, organizers will reach out and request additional information about the participant(s).

Who can participate?

Any Developer Community member, except for InterSystems employees (ISC contractors allowed). Create an account!

Developers can team up to create a collaborative application. 2 to 5 developers are allowed in one team.

Do not forget to highlight your team members in the README of your application – DC user profiles.

Important Deadlines:

🛠 Application development and registration phase:

  • November 17, 2025 (00:00 EST): Contest begins.
  • December 7, 2025 (23:59 EST): Deadline for submissions.

 Voting period:

  • December  8, 2025 (00:00 EST): Voting begins.
  • December  14, 2025 (23:59 EST): Voting ends.

Note: Developers can improve their apps throughout the entire registration and voting period.

Helpful resources

✓ Example applications:

✓ Templates we suggest starting from:

✓ For beginners with IRIS and Python:

✓ For beginners with IRIS and ObjectScript:

✓ For beginners with ObjectScript Package Manager (IPM):

✓ How to submit your app to the contest:

Need Help?

Join the contest channel on InterSystems' Discord server or talk with us in the comments section of 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. 

 
4 new Comments
Discussion (24)6
Log in or sign up to continue
Question
· Nov 6

How to use underscores in an expression in Analytics Architect.

Hi community

I have a persistent data class where there are some properties that contain underscores in their names, for example:
Property "client_name" As %String(MAXLEN = 250) [ SqlFieldName = client_name ];

In Architect, I would like to use this property in an expression, in this field:

But I can't figure it out. If I use %source.client_name, it gives a compilation error. If I use %source."client_name", it treats it as the string "client_name" instead of getting the value from the field. Any suggestions on how to do this?

9 Comments
Discussion (9)4
Log in or sign up to continue
Announcement
· Nov 6

Celebrating 1,000 Certifications

Hi, Community!

Join us in celebrating a milestone: InterSystems Certification is celebrating 1,000 certifications that showcase the knowledge and expertise of InterSystems professionals. Meet our team, see how the program has evolved, and get a discount on your next certification!

Celebrating 1,000 Certifications

👩‍🎓Join our growing community: Learn more about the InterSystems Certification program.

Use promo code InterSystems1000Certs for 30% off your next certification exam! (Offer ends 12/31/25.)

1 Comment
Discussion (1)2
Log in or sign up to continue
Article
· Nov 6 2m read

About exporting mapped globals

InterSystems FAQ rubric

When exporting using the Export() method of the %Library.Global class, if the export format (fourth argument: OutputFormat) is set to 7, "Block format/Caché block format (%GOF)," mapped globals cannot be exported (only globals in the default global database of the namespace are exported). To export mapped globals in "Block format/Caché block format (%GOF)," specify the database directory to which you want to map them in the first parameter of %Library.Global.Export().

An example of execution is shown below. 

 set DB = "^^c:\InterSystems\Cache\Mgr\Test\"  ; "^^\<path to database folder>\"
 set sc = ##class(%Library.Global).Export(DB,"TESTGBL.gbl",FULLPATH,7,,"")

If you specify the export format as 5 (default), "ISM/ObjectScript format (ISM/Cache format) (*)," you can also export mapped globals, but the output file will be larger than if you set the export format (fourth argument: OutputFormat) to 7, "Block format/Caché block format (%GOF).

Also, if binary data is recorded in the global, that data will not be output correctly.

For more information, see the following documentation.
Class Reference: %Library.Global.Export() [IRIS]
Class Reference: %Library.Global.Export()

[Note]
Globals that contain $LIST format or control characters cannot be exported correctly with the default export format of 5 (ISM/ObjectScript format (ISM/Cache format) (*)). In this case, you must export on a database-by-database basis with the export format (fourth argument: OutputFormat) set to 7 (Block format/Caché block format (%GOF)).

* Sequential file format

Discussion (0)1
Log in or sign up to continue
Discussion (3)2
Log in or sign up to continue