#Open Exchange

Hi Community!

Good news! We have a new release of InterSystems Open Exchange.

This release comes with some better options to expose your solutions and tools.

What's new?

✓ Embedded videos;
✓ Screenshots;
✓ Download stats.

See the details below.

Hello Gentlemen,

As you can read on the title, my question is to know how to retranslate the hl7 message into a string and so to remove the '\E' that are inside. A example/picture worth more than a thousand word.

OBX|1|RP|ECG||CARDIO ECG^APPLICATION^PDF^^\E\\E\sitehopital.org\E\files\E\cardio\E\022018\E\GE274583.PDF|

Hi Everyone!

We have a good tidings for you! Recently, we launched a new block on Developer Community Site called "APP OF THE WEEK" (you can see it through all website pages on the right).

And now you have a great opportunity to promote your project!

Redeem a new reward that available for Global Master advocates only: "Open Exchange project promotion on Developer Community"

What benefits will it give you? See the details below.

Hi guys!

Suppose you developed a tool, framework, library on InterSystems ObjectScript for InterSystems Data Platform, share it via Open Exchange and want people to install it.

What is the best strategy if it is a library and supposed to be called from different namespaces?

Here are the following thoughts:

1. Tool's developer should be able to use globals to read/store data the tool needs.

2. Tool's consumer should be confident, that the thing he/she installs will not harm the application's data.

3. A tool should be callable from any application's namespace.

4. Tool's installation(in general) should not request manual security changes (e.g. grant the write access to IRISLIB) and %YourClass is not an option.

5. It's easy to uninstall the tool - just delete the namespace/database (maybe delete some web-apps too).

I'm pleased to announce the latest version of the renewed for ObjectScript, which is now available with a lot of new features.

This new extension is a fork of previously developed extension in different repository originally started by @Oleg Dmitrovich.

Did you know that Caché (and now InterSystems IRIS) has available parser for ObjectScript ?

Well, technically, lexer. It hides under the name of %SyntaxColor class. This class provides API to the DLL used by Studio to do syntax highlighting. As a result if works only under Windows.

Hi Community!

Here is the digest of what has happened on the InterSystems Open Exchange in October 2018.

Application Releases

We had 12 releases in October:

Design Pattern in Caché Object Script v.1.0

Ideal ObjectScript v.2018.1

Caché Simple Rule Engine Example v.2017.1

Adding tools in Studio Caché Intersystems v.1.2

Execute Server Commands from Caché / Ensemble / IRIS v.1.1

IRIS API EXPLORER v.1.0.0

String Datatype - Regular Expression v.1.0

Debug Stack v.1.0

Ethereum Interoperability Adapter v.2018.2.2

Yape v.1.0.0

Hi, Community!

I'm pleased to announce that InterSystems Open Exchange is now operating and available for everyone!

Greetings, InterSystems community!

I am pleased to announce that the web terminal project, Caché WebTerminal version 4 gets its release! After long period of enhancing this web application from 2013, it came to the version 4, which features major stability and security improvements, intelligent autocomplete and syntax highlighting, convenient SQL mode and a lot of other useful features.

The goal of this article is to spread the knowledge about this project over the InterSystems community.