go to post Ben Spead · Jan 29 Always love seeing the stars :). Thank you to all those who asked and those who answered!!
go to post Ben Spead · Jan 28 @Armin Gayl - can you please confirm you are using Embedded Git to manage your server-side source control? https://community.intersystems.com/tags/embedded-git
go to post Ben Spead · Jan 26 One possibility is that you don't have the appropriate Service enabled to allow for this connection. This is pretty easy to check, from the SMP go to:System Administration > Security > Auditing If auditing isn't enabled then Enable it and run your test again, then go into View Audit Database and see if there is an access error logged. It is quite possible that you don't have the Call-in service enabled (I don't think it is by default in Normal or Locked Down instances). From the first .Net documentation link you provided: [quote] If InterSystems IRIS has been installed with security option 2, open the Management Portal and go to System Administration > Security > Services, select %Service_CallIn, and make sure the Service Enabled box is checked. If you installed InterSystems IRIS with security option 1 (minimal) it should already be checked. [/quote] Check that out and report back if it solved your issue.
go to post Ben Spead · Jan 21 Robert - you rock! Congrats to you and thank you to everyone contributing :)
go to post Ben Spead · Jan 17 P.S. There is also a newly released Learning Services Online Course which covers use of Embedded Git in our HealthConnect Cloud platform, but the principles covered are generally applicable - https://learning.intersystems.com/course/view.php?name=HCCSourceControlC...
go to post Ben Spead · Jan 17 @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.
go to post Ben Spead · Jan 17 @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!
go to post Ben Spead · Jan 17 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)
go to post Ben Spead · Jan 17 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.
go to post Ben Spead · Jan 15 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.
go to post Ben Spead · Jan 10 FYI .... This material was presented at Global Summit, and the recording can be found (for now) here: https://www.intersystems.com/creating-an-intersystems-iris-cross-functio... I assume that eventually it will be moved to the InterSystems YouTube channel as well.
go to post Ben Spead · Jan 7 @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!
go to post Ben Spead · Jan 7 @Oliver(Take2IT).Wilms - current versions of IRIS do not include IPM out of the gate. You can side load it very easily - see https://community.intersystems.com/post/install-zpm-one-line. At some point in the future, IRIS should include IPM.
