While we have the ability to use GIT within VSCode, there are a lot of folks out there that are depenant on using the Management Portal and the Editors within the Management Portal to do their coding. While it is not intunitve to add some kind of Change Management/Source Control, guidence within the Management Portal would be appreciated to have an automatic way that once someone edits within an Editor in the Management Portal that it is uploaded into GIT or the Change Management SW of your choosing.
Jan 26, 2023
Thank you for posting the idea. According to information from experts, this functionality already exists.
I would suggest to build a general audit utility that can be used with any % or non-% global.
We have built such solutions for auditing over the years, in different projects, but a more "generic" and robust tool that can be used internally by the SMP to keep track of every change might be supper useful in my opinion.
https://github.com/intersystems/git-source-control handles the management portal editors nicely. It’s a bit clunky at points but ultimately it does all it needs to.
Isn't it great when your ideas come to life so quickly... Check out our last few posts on the Developer Community, where we have been discussing our new Production component driver for Deltanji source control - a solution for your winning entry!
Great minds think alike @Scott Roth, congratulations on winning the contest.
Link to most recent post here: https://community.intersystems.com/post/source-control-interoperability-...
I really like this suggestion. There are many places in the management portal that don't fit neatly into the existing tools. Some ability to know what's changed and the ability to export those changes into an idempotent file that can be checked in, loaded into new environments, etc would be helpful.
@John Murray, the description on Open Exchange still lead me to believe this is being done in Studio and VS Code. What I am looking for is something within the Management Portal that can be setup that when ever a data lookup, DTL, Business Process, etc... is touched that it is automatically set to GIT or some other change management by design. This has been our struggle since the beginning as we have just told folks to make sure they backup the code prior to making the change in the Production environment since there was nothing native. With VS Code we just started using GIT but there is still an issue with keeping it in sync with those that use outside of VS Code.
@Scott There is a question about your idea. Please answer, it will attract more attention to it.
Did you look at https://openexchange.intersystems.com/package/Git-for-Shared-Development-Environments already? And if you're not wedded to Git there's Deltanji, for which we at George James Software are getting ready to add a major upgrade to how it can manage the building blocks of interoperability productions.