go to post John Murray · Mar 21, 2016 Thanks all. I enjoyed taking part, and am looking forward to Global Summit.
go to post John Murray · Mar 18, 2016 What's the $ZV of your cloud server?When I tested debugging from Atelier 1.0.116 onto a local 2016.2FT Build 605 earlier today it wasn't working for me. So I upgraded the server to the latest build they're publishing (613) and that seems to have fixed the issue.
go to post John Murray · Mar 18, 2016 Excellent. Don't forget to get the 2016.1 FT section removed from https://wrc.intersystems.com/wrc/BetaPortal.csp
go to post John Murray · Mar 18, 2016 If I'd realized that I wonder if I could've used it to boost my score in the competition that just ended
go to post John Murray · Mar 18, 2016 I haven't tried this myself, but maybe use the Terminate method of %SYSTEM.Process
go to post John Murray · Mar 18, 2016 You mean we used to be able to post an article into more than one group? From my recollection of the previous UI it certainly wasn't obvious, but perhaps the list was multiselect. Either way it's now irrelevant since you've replaced that list with radiobuttons.
go to post John Murray · Mar 17, 2016 It happens to me too. For example, these four are showing on the enigmatic "My collaborations" page for me:
go to post John Murray · Mar 17, 2016 Adding to this, I'm not 100% clear on the relationship between Communities/Groups and Tags. Some tags seem to correspond to communities/groups, other tags don't. When I look at an arbitrary post and want to know what Community/Group it belongs to, how do I tell? Look for a tag that is also a community? What if more than one tag qualifies?
go to post John Murray · Mar 17, 2016 Good suggestion, though you somehow managed to post it in the Developer Community Feedback community/group rather than the Atelier one. There's still room for improvement in the DC's user interface.I think you can edit your post and change what's selected in the Group list, setting it to "Atelier" instead of "Developer Community Feedback".
go to post John Murray · Mar 17, 2016 How about adding a DC version identifier somewhere? Perhaps in the page footer?
go to post John Murray · Mar 17, 2016 Checking for myself whether this is corrected. If after adding this comment the post date still displays correctly then it is.
go to post John Murray · Mar 17, 2016 I've been told that they're intending to offer Atelier as a plugin to an existing Eclipse IDE as well as giving us the standalone Atelier IDE. Just wondering how close that day is.
go to post John Murray · Mar 16, 2016 How realtime is the leaderboard? My post from earlier today hasn't turned up there yet. Wondering if yesterday's DC update could have affected the data feed to it.
go to post John Murray · Mar 16, 2016 It'd be useful if "My Content" entries also showed info about number of answers, comments etc. in the usual place (highlighted below):
go to post John Murray · Mar 16, 2016 Interesting that my browsers (FF and Chrome) stack the two "Related Topic" fields vertically:Maybe your screenshot is from a newer version of DC?
go to post John Murray · Mar 16, 2016 That's certainly a useful tip. I wonder if it would have helped in a situation we assisted an Ensemble site with last year. They'd upgraded their DEV and QA environments from 2013.1 to 2015.1 but their LIVE was still on 2013.1. Then they amended an HL7 schema in DEV, exported it, imported it to QA, verified it worked, and finally loaded it to LIVE, where it broke the production.The cause turned out to be a change made in 2014.1 and documented in a bullet point here. Yes, they had been unwise not to retain a QA or pre-live staging environment on the exact Ensemble version that LIVE was running.
go to post John Murray · Mar 16, 2016 I take your point about keeping up with the technology curve, but it's no good the next release of your app using all the whizzy new features of the latest Caché version if you're not able to deploy it to your customers until they can be coaxed to upgrade. Yes, you can use the new features as a carrot to entice them to upgrade, but meanwhile you probably have support commitments to them that mean occasionally patching the app release they're currently using.
go to post John Murray · Mar 16, 2016 I'm not advocating making your live environment the first one you upgrade. Upgrade a QA environment initially, and do enough testing there to be confident that your app works.
