go to post Evgeny Shvarov · Jan 4, 2020 Robert! Is it wrong or it's incomplete? Wrong is a fake, incomplete - its another 'not enough information', which should be stated on the site of course. Some companies just don't share their contracts and partnership at all so I'm curious if any "enlyft" can show accurate information.
go to post Evgeny Shvarov · Jan 4, 2020 Yes, I agree that it's not clear where they got the information. Is there any disclaimer on the site? Some information is accurate some are at least 'not sufficient".
go to post Evgeny Shvarov · Jan 4, 2020 @Mark Bolinsky - your article is the most viewed this year! Not surprised ) @Henry Pereira - congrats on the most voted article - everybody agrees that unit tests are 'the must' but not everybody is using it ;) And voting for this is almost using this! :) @Henrique Dias - and yours the most discussed, perhaps the monitoring is the hottest topic! Wish we add it to ZPM to make the installation instant. Thank you, gentlemen! And thanks all for contributing such great articles this year!
go to post Evgeny Shvarov · Jan 4, 2020 Thanks, Ponnumany, interesting! Pretty much no code libraries. This is what InterSystems Open Exchange and ObjectScript Package Manager for.
go to post Evgeny Shvarov · Jan 4, 2020 Sander! Could you also share it on Github and submit to Open Exchange, please? Even better with ZPM module?
go to post Evgeny Shvarov · Dec 30, 2019 Hi Peter! Thanks for the question. It makes a lot of sense to test your package before publishing it on ZPM-registry. You can test it via 'load' and 'publish' commands of ZPM-client. Suppose, you have IRIS with ZPM client installed and you have the repo folder locally with module.xml in the root. Then you can use following command to test the module.xml loading: USER:zpm>load /yourfolder/withrepo/ or with -v with more details: USER:zpm>load -v /yourfolder/withrepo/ It shows the log and if module.xml is not correct you'll see errors in the log. This is the test of resources description. Then you can test the publisher with 'publish' command. Call: USER:zpm>packagename publish or with -v with more details: USER:zpm>packagename publish -v This will try to execute all the tests, run web-app settings and call invoke methods locally. This will then refuse to publish cause you don't have the registry locally - which is OK, because you don't want to publish locally, right? All other errors will tell you if something is wrong with your module.xml package. HTH
go to post Evgeny Shvarov · Dec 27, 2019 True. Fabian! Could you please publish this Graph util as standalone app on Open Exchange?
go to post Evgeny Shvarov · Dec 26, 2019 If it says "Computing Axis" in Analyzer this is most probably the case of MDX Query performance. You can run the MDX Query you use in this pivot against any of the tools @Peter Steiwer mentioned above and share the results here or/and with WRC Support.
go to post Evgeny Shvarov · Dec 26, 2019 I saw it but didn't get what it does. Could you please share how is it helpful?
go to post Evgeny Shvarov · Dec 26, 2019 Hi Lawrence! Does your issue relates to DeepSee Dashboards UI or to the MDX query performance?
go to post Evgeny Shvarov · Dec 25, 2019 And you are able to redeem the voucher for certification attempt with GM points! See the announcement.
go to post Evgeny Shvarov · Dec 23, 2019 QEWD is. But it looks like you have two more products related to QEWD, right?
go to post Evgeny Shvarov · Dec 22, 2019 Hi @Rob Tweed! Do you want to list your QEWD products on Open Exchange? This will definitely bring more attention to your solutions.
go to post Evgeny Shvarov · Dec 20, 2019 Hi Nikita! Do you want the ZPM exception for the Webterminal only or for all your InterSystems solutions? )
go to post Evgeny Shvarov · Dec 19, 2019 Hi Neerav! Use REST-API with data in JSON format - this is server-side type consumable by almost any modern web or mobile frontend.
