All
Accepted answers
Ben Spead · Jan 21, 2025 go to post

Robert - you rock!  Congrats to you and thank you to everyone contributing :)

Ben Spead · Jan 17, 2025 go to post

@Sean Brady - per "The push to use vscode over studio is there but the processes have not been migrated so we are still having to fall back to studio for deployments." ... FYI, when you use Embedded Git (or any Serverside Source Control toolset) you can use either VS Code and Studio (or both!).  The IDE triggers the behavior on the server so either should kick off the same behavior.

I am sorry but I can't answer your question about deployment manager as I have always relied on source control and automation tools based on that (I have been spoiled by that ;) ). 

If you are hitting merge conflicts I am going to go out on a limb and guess that these are in the Production Class?  If so then I highly recommend that you look at using Production Decomposition which solves this issue by allowing Embedded Git to manage PTDs rather than the Production Class as a whole - https://github.com/intersystems/git-source-control/discussions/519. 

We also have a standing weekly meeting for Embedded Git users to provide updates on features and 'office hours' for questions.  DM @Pravin Barton if you want to get an invite.  

Ben Spead · Jan 17, 2025 go to post

@Sean Brady - welcome to the D.C.!  Great question and you should get a lot of help here.

First, definitely watch the video linked by @Oliver Wilms in the earlier response.  It will help you understand how the InterSystems-based healthcare platforms tend to work best with the embedded source control paradigm due to how changes are made in the Management Portal and not just in VS Code.  

As you try to get Git set up, can you please confirm that you using the Embedded Git package?  https://community.intersystems.com/tags/embedded-git

You said you are having issues working with Git - could you please provide more details?

If you haven't, you should review the Branching Strategy doc on GitHub for Embedded Git (https://github.com/intersystems/git-source-control/blob/main/docs/hcc.md#general).  While it is in the HealthConnect Cloud section, @Pravin Barton has assured me it is generally applicable.

While you are working towards getting a proper Git-based progression in place, you can use Deployment Manager in the Portal (but you should stop using this once you have Embedded Git working).  This is the easiest way to grab things in bulk and move them between environments.  

Please note that HealthShare Registries are not yet covered by Source Control / Change Control hooks, so you will need to move those by hand or via custom scripting.  Those will come later this year - see the Global Summit presentation on the topic here: https://www.intersystems.com/change-control-for-healthshare-intersystems/

Hopefully this is enough to get you rolling.  Let us know what questions you may have!
 

Ben Spead · Jan 17, 2025 go to post

I was talking to someone about the VS Code Workspace enhancement and I don't have a local instance to check.  Can anyone provide a screenshot or more detail on where to find this new feature? (I didn't notice it in the GitHub release notes either)

Ben Spead · Jan 17, 2025 go to post

this is very helpful video ;)

Thanks for the callout!  @Sean Brady - welcome to the D.C.!  This would be the right place for you to start.  

Ben Spead · Jan 15, 2025 go to post

I believe the API were first included in 2016.2 but there were issues so 2017.1 or later is recommended.

To connect to 2016.1, your only option is to use InterSystems Studio.  If you don't have access, reach out to a support who can supply you with a kit.

Ben Spead · Jan 7, 2025 go to post

@Ben Schlanger - thanks for catching that! Not sure if I have time to chase down all of these updates, but if you have alternative URLs I can point to for the above DM me or post them here

and I will update anything that you find.  Thanks!

Ben Spead · Jan 3, 2025 go to post

Bravo to those who participated and especially to those who completed!!

Ben Spead · Jan 2, 2025 go to post

This is a *really* useful utility and I want to make sure people have this on their radar.  @Matthew Giesmann / @Evan Gabhart - this is the work I want to make available to our customers who are moving to using CCR Tier 1 for their integration instances.  
 

Ben Spead · Jan 1, 2025 go to post

Congratulations everyone on the great set of content created by this community in the past 3 months!  Happy New Year everyone!

Ben Spead · Dec 26, 2024 go to post

thanks all for a great year!  Here's to great things in 2025 :)

Ben Spead · Dec 23, 2024 go to post

very well deserved - congratulations @Alberto Fuentes and thank yoi for everything that you contribute to the Developer Community and to InterSystems!!!

Ben Spead · Dec 23, 2024 go to post

Congratulations to the winners and thank you to everyone who participated! It is great to see such creative solutions being made available in the Open Exchange:-)

Ben Spead · Dec 3, 2024 go to post

agreed!!  the Kindle is an awesome option.  I use mine pretty much daily :)

Ben Spead · Nov 20, 2024 go to post

Does it fail in any browser other than Edge?  I can't get Edge to fail (nor Chrome not Chrome incognito).  

Just trying to figure out what might be different for you.

Ben Spead · Nov 20, 2024 go to post

@Scott Roth - what browser are you using?   Can you try in an incognito browser to bypass any cookies or settings which could be impacting behavior? (I am not able to replicate your results)

Ben Spead · Nov 20, 2024 go to post

There is no rollback mechanism built into the installer (unless there is an issue in the middle of the installation in which case it will back out the installation).  If you are using a VM the best practice is to snapshot your VM prior to upgrade and roll back to the snapshot if something goes wrong.  This should be done with care because any data changed post upgrade will be lost when you restore the snapshot.