Now the Classes/Rutines/DeepSee files will be automatically exported to the working directory after saving or compiling and files will be automatically deleted .

https://www.youtube.com/embed/B1pmqAQqd4M
[This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]

Installation

To install isc-dev , you just need to download and import the file isc-dev.xml from last release.
Some ways to import isc-dev .xml file:

• Go to Management Portal -> System Explorer -> Classes -> Import and select the XML file.
• Drag the file over Studio.
• Terminal command:

NS>do $system.OBJ.Load("yourpath/isc-dev.xml","ck")

• Get it from Package Manager Client:

NS>zpm
zpm: NS>install isc-dev

How to enable this feature:

• After importing the class in the target namespace, run the following method to set up the working directory:

NS>do ##class(dev.code).workdir("/path/to/your/working/directory/src/")

• Go to Management Portal -> System Administration -> Configuration -> Additional Settings -> Source Control.
• Select the target namespace and set the dev.FileManExtension class as the main one and save it.
• Try to create a new class in the studio and save/compile it
• Enjoy!

Framing refers to the characters that mark the start and end of an HL7 message (or other types of framed messages). Most HL7 services and operations have a Framing setting that allows the user to define this framing. The most common choices are available as defaults, but with the AsciiMM/NN setting, components can be configured to recognize any framing characters.

InterSystems is pleased to announce the release of Caché, Ensemble, and HealthShare Health Connect v15.03

Some highlights for Caché and Ensemble are:

Hi developers!

If you missed our presentation at the InterSystems UK&I Summit and our demo during the Source Control roundtable, but you still want to find out more about source control for Interoperability Productions... there’s another chance to see it at our User Group Session next Thursday, November 3rd at 3pm (GMT). 

The new driver enables highly granular management of Interoperability Productions with tight integration into the InterSystems IRIS management management portal. 

Sign up via eventbrite here >> https://bit.ly/3yqzfvS

You might have encountered this and not known how to prevent it, or perhaps not even noticed it...

Olá pessoal,

Compartilho material de um curso desenvolvido por mim, espero que possa ajudar a comunidade.

English:

Hi folks,

I share material from a course developed by me, I hope it can help the community. The material is in Portuguese.

Link: https://www.linkedin.com/posts/cristianojs_material-te%C3%B3rico-activity-6608421528906285056-sr8E

InterSystems FAQ rubric

Countermeasures against SQL injection have been published on various websites, but we believe that it is possible to prevent SQL injection in applications using InterSystems SQL as well as other RDBMS by implementing these countermeasures appropriately. In addition, InterSystems Data Platform (hereinafter referred to as IRIS) incorporates several measures that make SQL injection more difficult than general RDBMS.

InterSystems FAQ rubric

If you do not specify the option to remove the mirror attribute of the mirror database when deleting the mirror configuration, the database cannot be restored to a normal state and will be mounted read-only the next time it is mounted. To restore the database to a read-write state, you must remove the mirror attribute using the system routine ^MIRROR.

The procedure is as follows (execute in the %SYS namespace):

InterSystems is happy to announce the availability of our newest Data Platforms release: Caché and Ensemble 2016.2

The highlights of 2016.2 are:

A sophisticated alerting solution lets you solve problems quickly and proactively. Watch the recorded webinar: Proactive Alerting: Advanced Approaches for Alerting Solutions webinar presented by Michael Brady, InterSystems Technical Trainer, to learn how to make the most out of your alerting solution.

If you work with interoperability productions of InterSystems IRIS or Ensemble, no doubt you are familiar with the Message Viewer page. The page supports filtering messages according to filter criteria you enter in the Basic and/or Extended Criteria sections. Extended Criteria conditions are specified as property-operator-value triples. Once you click Search button, such triples become WHERE clause conditions of a generated SQL query executed against message header/body tables.

InterSystems FAQ rubric

When executing OS commands, use $ZF(-100).

Hi ObjectScript developers!

InterSystems ObjectScript is perhaps the best language on the planet to deal with globals - and it is an interpretable language.

Yes, it has a compiler. But even the compiler can compile some lines in ObjectScript which will then fire as bugs during the runtime.

There are some technics on how to avoid that such as unit testing, coding guidelines and your coding experience, of course ;)

Here I want to present to you the yet another approach to how you can reduce the number of errors in your ObjectScript runtime and enforce coding guidelines - it's an ObjectScript Quality tool developed by Lite Solutions, InterSystems solution partner.

See the details below.

EnsLib.HL7.Message.cls provides many API methods for manipulating an HL7 message. RemoveSegmentAt(), for example, can be used to remove a segment by path or index, but only one segment at a time. There may be times that you'll need to remove all segments within a group or even many groups of segments from the HL7 message. Surely you can iterate through each segment in each group and remove them one by one, but there's a much easier way.

With just one command, like below, you can remove all OBX segments in an ORU_R01 message (msg):