@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
@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
Yes indeed! It was a great new challenge for me to reach new personal records on my walkstation :)
Terrific and major enhancement! Thank you all who contributed! Looking forward to hearing feedback as this starts getting traction in the field.
you will need to discuss with your IT administrators and get it categorized appropriately within your organization
@Timothy Leavitt - great work on continuing to move this critical piece of our tech ecosystem forward!!
So excited! Welcome back :)
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.
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.
Thank you to all who contribute to this community!!
well done everyone, and thank you for the contributions to the Community!!
most welcome!
Great news!! Looking forward to those InterSystems socks again!!!
;)
Bravo G.M. team :)
@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
Great!
@G. Mar - as mentioned above Evaluation Licenses are only shown for those who are associated with a Support Customer organization. Looking at your profile this is not the case for your InterSystems Login user. Can you please reach out to your Account Manager and request that they provide an Evaluation Key, or get you properly tied to your Organization in the WRC (which would then give you the option of getting an Evaluation Key yourself). Thanks!
@G. Mar - Yes you can! See the details on the InterSystems Evaluation Service here - https://community.intersystems.com/post/intersystems-evaluation-service
Current customers can log into https://evaluation.InterSystems.com and request a key for themselves.
Prospects can ask their Account Rep who can use the Evaluation Service to pull a key on their behalf.
Hope that gets you what you need!
@Rajendra Chandracant - to reach InterSystems Support, please email support@InterSystems.com (you are on the Developer Community and not an official InterSystems support channel)
To get an IRIS key for testing purposes, please see the details about the Evaluation Service which customers can use to request an IRIS key: https://community.intersystems.com/post/intersystems-evaluation-service
@Benjamin De Boe - congrats and well deserved!! I have to also echo my eager anticipation of the return of G.M. and new socks options ;)
Thank you, we did change it as a stopgap, but we're more wondering about a more secure way to handle this situation. Benjamin's answer above is exactly what we needed, and he confirmed it was intended behavior which is very helpful
Awesome - thank you @Benjamin De Boe! Just what we needed to know :)
I want to highlight the fact that the account expiration was several months long (so the connection being up for many months with no reconnecting) resulted in the account expiring.
The other question (besides workarounds) is whether this is expected / desired behavior at the product level, or perhaps the account inactivity logic should take into account ongoing activity?
Another option (my preferred one) - ensure that source control is used for all namespaces in your instance and simply do the search in your source repository. Then you not only find the strings you are looking for but also you can easily find the history related to each of those parts of code.
thank you for making us aware. I have escalated this internally and I hope it can be corrected quickly.
We are using this to implement a reusable comprehensive email templating module to prevent our having to hand-craft HTML emails out of many different IRIS applications. So far the approach looks very promising! (and members of the community will eventually be able to directly see the results as we're first using this to implement a Welcome Email framework which can be used by any of our externally facing applications which use InterSystems Login accounts - https://community.intersystems.com/post/leveraging-your-intersystems-lo…)
My pleasure @Dean Andrews - I couldn't do any of it were it not for the awesome team you have supporting the D.C. :)
@Evgeny Shvarov - I feel the same way about you and your contribution! It's great striving together to make this place better for everyone learning our technologies :)
Umm ... that sounds a little scary, but thanks all the same ;)
thanks Raj!