go to post John Murray · Aug 10, 2018 I can get that error message from Atelier's connection setup dialog if I intentionally point to a web server that doesn't offer the /api/atelier REST interface to a Cache/Ensemble 2016.2+ serverFrom your original posting it's not clear to me that you're connecting to a suitable web server.
go to post John Murray · Jul 30, 2018 No sign yet of the updated release notes in the downloadable zip.
go to post John Murray · Jul 27, 2018 Did you consider creating a Studio Project containing everything you need? Then you can export the project to XML in a way that includes all the members of the project as well as the project definition.It's also worth knowing that if you go to the Namespace tab of the Workspace pane, then expand Classes, you can right-click on a package and add the package to your current project. This may be better that adding individual classes to your project, because by adding the package you ensure that any classes added later to the package will be exported too.
go to post John Murray · Jul 24, 2018 It looks like this class is intended to be created in the %SYS namespace so it can use the Security.System class.Also, be aware that classes you create in %SYS typically don't survive a Cache / Ensemble / HealthShare upgrade.
go to post John Murray · Jul 19, 2018 This section of the 2017.1.2 release notes looks relevant. I guess the problem occurs for all server-side source control classes, not just the Deltanji oneCategory: DeepSee.User InterfacePlatforms: AllDevKey: DTB633Version: 2017.1.2Summary: Ensure widgets can be edited when namespace uses source controlDescription:If source control is enabled in a namespace, privileged users could not edit dashboards. This change corrects this problem.
go to post John Murray · Jul 18, 2018 Dave, please tell us which bit(s) of the documentation you're referencing. Ideally, hyperlink to the copy rooted at https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls
go to post John Murray · Jul 18, 2018 What version(s) of Ensemble / HealthShare suffer from this bug? In what version did it get fixed?
go to post John Murray · Jul 17, 2018 Could you use the SQL Gateway feature to make your tables accessible there?
go to post John Murray · Jul 17, 2018 Connect Studio to your namespace.File\New Project. Your Studio titlebar will refer to Project1.prj.Project\Add Item...File\Save Project As... and give your project a meaningful name.
go to post John Murray · Jul 17, 2018 Your SetPersistentValue calls refer to LastModified, but your query refers to LastUpdated. Is this a typo in your post?If you use Portal (Explorer, SQL) to run a query that reports LastUpdated values, what do they look like? More technically, what datatype are they?
go to post John Murray · Jul 17, 2018 You can create a Studio project interactively from within Studio. There are a few hints in the Studio doc here.Or if you want to create/amend Studio projects programmatically, use the %Studio.Project class.
go to post John Murray · Jul 12, 2018 Not a direct answer to your question, but did you consider using the Size query of the %SYS.GlobalQuery class, as shown by this DC comment from @David Loveluck on another DC post?https://community.intersystems.com/post/database-table-size#comment-12401
go to post John Murray · Jul 11, 2018 Though it now seems that 1.3 is the end of the Atelier road, right?https://community.intersystems.com/post/atelier-and-studio
go to post John Murray · Jul 11, 2018 There's a table at http://georgejames.com/deltanjiEditionsThe free Solo edition is intended for, well, solo situations, with one developer wanting straightforward checkout/checkin source versioning for their namespaces on their local Cache / Ensemble instance.In your context the Team or Enterprise editions are more likely to be appropriate, particularly since the comparison table shows LUTs not being supported by Solo.Deltanji is capable of a lot more than simple code versioning. Please contact me via the George James Software website if you'd like to evaluate Team or Enterprise editions, or if the capabilities of the Deploy edition are of interest to you.
go to post John Murray · Jul 10, 2018 Since you're using Ensemble, you may also like to know that Deltanji integrates with the Portal-based editors and with Studio, as well as with Atelier. It is server-side source control, so has no problem with scenarios where multiple developers work as a team in a single namespace.
go to post John Murray · Jul 10, 2018 Yes, Deltanji handles LUT and HL7 components natively. And yes, it's a paid product, though there is a free Solo edition.
go to post John Murray · Jul 10, 2018 Manish, I highly recommend you use the normal support channel for this, i.e. contact WRC.
go to post John Murray · Jul 10, 2018 IMO your best chance of getting this issue addressed by InterSystems is to engage with them through WRC (Worldwide Response Center).
go to post John Murray · Jul 10, 2018 Are you "committed" to using GIT as your source control? If not, maybe take a look at Deltanji from George James Software (my employer).
