go to post Ben Spead · Aug 25 You could gift some points to some well deserving InterSystems interns ... or get socks for everyone on your Christmas list this year ;)
go to post Ben Spead · Aug 25 Went to the sea or a lake Yes Hiked/enjoyed nature Yes Traveled somewhere new Yes Attended a concert or festival Yes Watched a movie or series Yes Read a book Yes Earned points and redeemed a reward on Global Masters 🏆 Earned points (but didn't redeem yet ... am saving them up ;) ) Joined READY 2025 🎉 YES!!! Spent time with family or friends Yes I also had the opportunity to introduce our interns to Global Masters and see them have fun with the gamification challenges :) Thank you Global Masters team for all of your great contributions to the Community!!
go to post Ben Spead · Aug 20 its been a pleasure working with you and learning from you all of these John!!
go to post Ben Spead · Aug 19 @Yuri Marx - thank you for time you spent pulling together this article ... well done :)
go to post Ben Spead · Aug 18 @David McCaldon - exciting news, thank you for the work on getting this released!
go to post Ben Spead · Aug 12 "all these discussions are mostly useless. " - we have implemented linting as part of server-side source control hooks. See https://openexchange.intersystems.com/package/isc-codetidy
go to post Ben Spead · Aug 4 got it - I reached out to the Docs team to better understand why the button isn't there
go to post Ben Spead · Aug 4 I completely agree! Doc offers a direct channel to them for feedback, and they are very responsive to that. Every documentation page has a Feedback button on the right, which will capture the page from which the feedback originates, making it even faster for the Docs team to know where a tweak is needed:
go to post Ben Spead · Aug 1 @Vachan C Rannore - The DC answer is right. You may log in at login.intersystems.com and go to Options > Change Email. You will need to input a code to verify your new email and a notification gets sent to the old email. (credit for answer @Pravin Barton )
go to post Ben Spead · Jul 11 This is coming from the Source Control class set up in this Namespace. If you search for "Source Control" in the SMP, and look at the settings for that Namespace you will see that a class is selected. Change to None if you don't wish to have Serverside (embedded) Source Control active. If you do wish to use embedded source control, then you will need to provided item type mappings in the ^Sources global in order for it to work (at least to allow the one you currently have active to work - different hooks work differently in terms of configuration)
go to post Ben Spead · Jun 26 I really like that idea, having them close together is extremely helpful. We always use the created and updated properties as well, with %OnAddToSaveSet() triggers for both
