go to post John Murray · Oct 13, 2017 Vineeth, please help the community by accepting the answer that helped you. The animation in this article shows you how to do that.
go to post John Murray · Oct 13, 2017 Maybe use this as your launch URL:http://localhost:57774/csp/sys/%25CSP.Portal.Home.zen?$NAMESPACE=EXPERT
go to post John Murray · Oct 13, 2017 [@Thembelani Mlalazi] - to add a linked mention of another DC member you need to use this syntax.I posted the above example as an image so the DC software doesn't transform it.If unsure, try the Preview button before posting.As a moderator I have edited your first comment to make the mention work as I think you intended.
go to post John Murray · Oct 12, 2017 Assuming your Ensemble is running on Windows, you can probably use Caché Activate.
go to post John Murray · Oct 12, 2017 Do you really mean MAPI, which is a Microsoft proprietary protocol for interacting with an Exchange server?Or perhaps you mean IMAP.
go to post John Murray · Oct 10, 2017 In support of Nicole's answer, it should "just work". The server-side source control class that's part of our Deltanji product, and the associated Studio add-ins, function in Atelier pretty much the same as they do in Studio.
go to post John Murray · Oct 6, 2017 When you searched the Ensemble doc for "email" did you see this article?http://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=...
go to post John Murray · Oct 6, 2017 You don't have control of this. It's done automatically. More info in this post:https://community.intersystems.com/post/september-2017-dc-release
go to post John Murray · Oct 6, 2017 Possibly answered in comments. I am posting this as an answer so the question no longer lists as "no answer", and so the OP can mark it as answered if desired (thus removing it from the "unanswered" view).
go to post John Murray · Oct 6, 2017 Another recommendation (for all types of post, not just questions) is to try and make the "teaser" portion of the body useful.The teaser is the first part of the body, the part that displays under the title on the list of posts that appear on the home page, for example. Sometimes the DC software doesn't make the best job of deciding how much of the body to put into the teaser. For example:orYou can help by using this button on the editor to insert the "teaser break" into your text:The "Preview" button next to the "Save" one is a handy way of checking if a teaser break might be needed. Or, go back to your post and edit it afterwards.
go to post John Murray · Oct 6, 2017 Here's my understanding of the feature:For each DC member who clicks the green "thumb up" at the foot of your post, its rating increases by 1. And for each DC member who clicks the red "thumb down", the post's rating decreases by 1.I'm going to click the "thumb up" on your question because I think it's a good one. So you should see its rating increase from 0 to 1.
go to post John Murray · Oct 5, 2017 Randall, my understanding is that it wasn't removed. But some of the syntax that was introduced in 2016.1 in connection with it was subsequently dropped, meaning that code of yours which worked in 2016.1 has to be amended for 2016.2 and later. The links above should help.
go to post John Murray · Oct 3, 2017 Another reason to limit your reliance on the webserver that InterSystems ship and install is that it will only receive security patches when you apply a maintenance update to your Cache/Ensemble/HealthShare instance. In comparison, you can (and should) take responsibility for keeping a standalone instance of webserver software (e.g. IIS, Apache) up to date with security fixes.
go to post John Murray · Oct 3, 2017 Any update on when 2017.2 will release? The most recent build we outside ISC have access to is 740, dated 24th August.
go to post John Murray · Oct 2, 2017 Interesting observation Ian.Can anyone at InterSystems confirm that this should (or should not) be necessary to redo after each upgrade?
go to post John Murray · Sep 29, 2017 Prepare() is for dynamic SQL, but in your case it's a class query you want to run. So change your rs.Prepare call to be an rs.Execute one. Or use the following as a quick verification:%SYS>d ##class(%ResultSet).RunQuery("Config.MapGlobals","List","HSEDGEREST","*")
