#Studio

Introduction

Preface: our small, but very ambitious company called “Black Mushroom Studio” came up with an idea for an e-commerce project and a mobile app that would let users pay for certain goods/services via a payment aggregator.

What we had initially: an Android app skeleton that, of course, liked communicating via HTTP and JSON, and a payment system with an API – web services with SOAP content.

Goal: make it all work together.

Happy new year! I’m Raj Singh, InterSystems’ product manager for Developer Experience and I’d love your feedback on how you use IDEs today and your thoughts for the future.

As you have probably noticed, online product documentation has advanced tremendously in the last few years. Among numerous improvements under the hood, documentation has become easier to read and navigate. And we now have a powerful search engine that gets you to what you need more accurately than we could ever do with the old system of shipping documentation in the product. While most of you have probably had nothing but positive impacts on your workflows, it has come to my attention that some of you may be having a slight problem accessing custom class documentation.

I wanted to share a little tidbit which is in the Studio documentation (http://docs.intersystems.com/cache20152/csp/docbook/DocBook.UI.Page.cls?...) but many people who have been using the InterSystems Studio for a long time missed the addition of this *very* useful feature, and every time I mention this to an audience I see at least one face light up because of how excited they are to learn about it!

Within Studio, the Output pane (View -> Output) is actually misnamed. It is actually an Input/Output window which can be used to run Caché ObjectScript commands!

As first announced in May, and after many presentations and robust discussions at Global Summit 2023, we are continuing with the plans to deprecate InterSystems Studio (deprecated designates a feature or technology that InterSystems no longer actively develops, and for which better options exist).

As the announcement of Studio's deprecation has been made, users may be wondering about making a smooth transition to VS Code.

George James Software has extensive experience in VS Code, through regularly contributing to VS Code itself and building and maintaining a number of Extensions. This, combined with our expert knowledge of InterSystems technologies, gives us an in-depth understanding of what the process involves and means we have the unique capabilities to ensure a smooth migration from InterSystems Studio to VS Code.

We offer bespoke consultation, with recommendations that are tailored to your organization's specific needs. Alternatively, we will be hosting a monthly public webinar that is designed specifically for users migrating from Studio to VS Code.

If you're ready to make the switch and would like to find out more, please come and speak to us at the Global Summit next week - you'll be able to find George James Software in the Partner Pavilion. Our team will be happy to chat with you about how you can ensure your migration is seamless.

Alternatively, you can send me a direct message here on the Developer Community, or email us at info@georgejames.com.

Creating and working with the new SDA extensions for storage of custom data elements

In HSCore 15.01, there is a new way to store custom data elements. HealthShare now had the ability to use custom extensions on many SDA elements.

This article will:

1. Show how to set up your system to use SDA extensions
2. Create a new SDA extension property
3. Use the new SDA extension property in HL7 transactions
4. Interact with the new data
5. Show new SDA extension used in a customization of Patient Summary Report

For those of you who still use the Studio IDE for ObjectScript programming and are going through the process of migrating to VS Code, did you know there's a section in the VS Code documentation just for you? Have a look at the Migrating from Studio chapter. It covers:

Atelier has reached a threshold of feature completeness. Atelier 1.3 which is currently in flight will mainly focus on supporting the latest release of Eclipse Photon. After release, Atelier and Studio will continue to receive critical software corrections.

Hi,
It can now be programmed with different development enviroments in Cache / Iris.
The question arises which is the primary IDE Intersystems prefers when it comes to new features.
We are working in a small team, should we use Atelier or VSCode in addition to Studio?

What do you use, and why?

The one question that some of you might have is:

How do I change my login information for Cache Studio if I clicked the checkbox to automatically save my login info so I do not have to enter my username/password every time I open Studio?

Well.....excellent question!!!!!!

Here's the answer:

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!

Everything you need to know about VS Code for InterSystems technologies.

With the announcement of the deprecation of Studio, George James Software are here to make moving to VS Code as smooth as possible. Our expertise in InterSystems technologies and active contributions to the development of VS Code itself, as well as creating and maintaining a range of VS Code extensions, provide us with comprehensive knowledge and experience to guide you step-by-step so you're set up and ready to work in VS Code.