go to post Ben Spead · Nov 20, 2024 @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)
go to post Ben Spead · Nov 20, 2024 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.
go to post Ben Spead · Nov 6, 2024 most likely yes. Support should be able to help you sort this out.
go to post Ben Spead · Nov 1, 2024 @Yuhong Snyder - the following should be helpful to you: https://github.com/intersystems/git-source-control/tree/main/docs https://community.intersystems.com/post/video-git-gitlab-shared-development-environments (also the article prior and following) https://community.intersystems.com/post/git-source-control-launches-release-240-new-basic-mode Also, in the future we plan to create a new #EmbeddedGit tag to make it easier to follow news and Q&A for these tools
go to post Ben Spead · Oct 30, 2024 that is correct ... Artifactory will be supported with this release.
go to post Ben Spead · Oct 28, 2024 @Scott Roth - are you sure that you re-exported the source after /exportversion was set in the system exporting the code that would be imported into 2022.1? If you are certain of this, then please reach out to Support because I am not sure why that would not work
go to post Ben Spead · Oct 28, 2024 @Scott Roth - best practice in cases like this is to set the /exportversion qualifier in the DEV environment (or whatever is exporting the source) until all of your pipeline is on the newer version. E.g. w $system.OBJ.SetQualifiers("/exportversion=iris2022.1") This should prevent any newer attributes from being included in the exported XML which would prevent import on an earlier version. ref: https://docs.intersystems.com/iris20242/csp/docbook/Doc.View.cls?KEY=RCOS_vsystem_flags_qualifiers
go to post Ben Spead · Oct 22, 2024 Yes indeed! It was a great new challenge for me to reach new personal records on my walkstation :)
go to post Ben Spead · Oct 22, 2024 Terrific and major enhancement! Thank you all who contributed! Looking forward to hearing feedback as this starts getting traction in the field.
go to post Ben Spead · Oct 17, 2024 you will need to discuss with your IT administrators and get it categorized appropriately within your organization
go to post Ben Spead · Oct 11, 2024 @Timothy Leavitt - great work on continuing to move this critical piece of our tech ecosystem forward!!
go to post Ben Spead · Oct 2, 2024 Thank you to everyone who provided feedback directly through the app. We have addressed the few concerns that there were, and @Matthew Giesmann will be disabling the old UI in the near future.
go to post Ben Spead · Oct 1, 2024 I am so very excited! This should be a lot of fun, even if it's just to see how long it takes me to walk that distance.
go to post Ben Spead · Sep 30, 2024 well done everyone, and thank you for the contributions to the Community!!
go to post Ben Spead · Sep 30, 2024 Great news!! Looking forward to those InterSystems socks again!!! ;) Bravo G.M. team :)
go to post Ben Spead · Sep 27, 2024 @Colin Brough - values for Cache Server manager are stored in the registry. If these servers are using CCR, you can actually download registry keys directly from you CCR System page (above Environments select Export > Studio) and load it onto a developers desktop in order to have the Environments automatically show up in the Caché Server Manager. If these are not CCR-controlled, then you can create a .reg file similar to the following in order to pull them in (this was generated by CCR for an internal System and I have modified a few fields; the last two entries change Studio to have a red background on LIVE to make it easier to see where you are located): Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\InterSystems\Cache\Servers\ISCU-Demo-BASE] "Address"="base.demo.iscdemo.com" "AuthenticationMethod"="0" "Comment"="This has been created by the CCR system export." "ConnectionSecurityLevel"="" "LastNamespace"="" "Port"="51773" "ServerType"="" "ServerPrincipalName"="" "Telnet"="22" "WebServerAddress"="" "WebServerInstanceName"="" "WebServerPort"="443" "HTTPS"="1" [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\InterSystems\Cache\Servers\ISCU-Demo-BASE] "Address"="base.demo.iscdemo.com" "AuthenticationMethod"="0" "Comment"="This has been created by the CCR system export." "ConnectionSecurityLevel"="" "LastNamespace"="" "Port"="51773" "ServerType"="" "ServerPrincipalName"="" "Telnet"="22" "WebServerAddress"="" "WebServerInstanceName"="" "WebServerPort"="443" "HTTPS"="1" [HKEY_LOCAL_MACHINE\SOFTWARE\InterSystems\Cache\Servers\LIVE-ISCU-Demo] "Address"="monitor.iscdemo.com" "AuthenticationMethod"="0" "Comment"="This has been created by the CCR system export." "ConnectionSecurityLevel"="" "LastNamespace"="" "Port"="51773" "ServerType"="" "ServerPrincipalName"="" "Telnet"="22" "WebServerAddress"="" "WebServerInstanceName"="" "WebServerPort"="443" "HTTPS"="1" [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\InterSystems\Cache\Servers\LIVE-ISCU-Demo] "Address"="monitor.iscdemo.com" "AuthenticationMethod"="0" "Comment"="This has been created by the CCR system export." "ConnectionSecurityLevel"="" "LastNamespace"="" "Port"="51773" "ServerType"="" "ServerPrincipalName"="" "Telnet"="22" "WebServerAddress"="" "WebServerInstanceName"="" "WebServerPort"="443" "HTTPS"="1" [HKEY_CURRENT_USER\Software\InterSystems\Cache Studio\Editor\Server Background Color] "LIVE-ISCU-Demo"=dword:00a0a0ff [HKEY_CURRENT_USER\Software\InterSystems\Cache Studio\Editor\Status Bar Color] "LIVE-ISCU-Demo"=dword:005757ff Hope this helps! Ben
