go to post Evgeny Shvarov · Jul 1, 2020 Robert! If Copy-n-Paste works for you? For me it doesn't. Possible to add? Added to issues.
go to post Evgeny Shvarov · Jun 29, 2020 But are you sure that method which does the thing was invoked? Is there a matter of Namespace (just a guess)? And what is the status then?
go to post Evgeny Shvarov · Jun 29, 2020 Hi Henrique! what is the problem do you have? any error or what?
go to post Evgeny Shvarov · Jun 28, 2020 Not sure what doesn't work for you. Could you please share an example? Or elaborate the problem?
go to post Evgeny Shvarov · Jun 28, 2020 Oh. Or make a small program, which does the thing - multiline editor for terminal. very simple. Just to have an option copy-paste several lines of code and run it in terminal
go to post Evgeny Shvarov · Jun 23, 2020 Because this is how we work, Robert :) Only this way ;) Thanks @Anastasia Dyubaylo!
go to post Evgeny Shvarov · Jun 23, 2020 Thanks, @Klaus Richarz! Ping @Luca Ravazzolo and @Steven LeBlanc on the issues with IRIS Docker image.
go to post Evgeny Shvarov · Jun 19, 2020 Thanks, Lucas! If you have issues with DSW, please submit it here!
go to post Evgeny Shvarov · Jun 19, 2020 Hi Lucas! Could you confirm that DSW export to PDF doesn't work for you here? What do you have as the result with PDF?
go to post Evgeny Shvarov · Jun 18, 2020 In a new 0.2.3 version of ZPM you can return back to the public repository with the following command: zpm:USER>repo -n registry -r -url https://pm.community.intersystems.com
go to post Evgeny Shvarov · Jun 16, 2020 Updated images: And we released images with IRIS 2020.1 and 2020.2 and ZPM 0.2.3. the tags are: intersystemsdc/iris-community:2020.1.0.215.0-zpm intersystemsdc/iris-community:2020.2.0.204.0-zpm intersystemsdc/irishealth-community:2020.1.0.215.0-zpm intersystemsdc/irishealth-community:2020.2.0.204.0-zpm intersystemsdc/iris-aa-community:2020.3.0AA.331.0-zpm And to launch IRIS do: docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/iris-community:2020.1.0.215.0-zpm docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/iris-community:2020.2.0.204.0-zpm docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/irishealth-community:2020.1.0.215.0-zpm docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/irishealth-community:2020.2.0.204.0-zpm docker run --name my-iris -d --publish 9091:51773 --publish 9092:52773 intersystemsdc/iris-aa-community:2020.3.0AA.331.0-zpm And for terminal do: docker exec -it my-iris iris session IRIS and for control panel: http://localhost:9092/csp/sys/UtilHome.csp Happy coding!
go to post Evgeny Shvarov · Jun 11, 2020 Neat! Rob, do you want to publish the sample on Open Exchange?
go to post Evgeny Shvarov · Jun 11, 2020 So this thread is an attempt to agree within the community on the modules naming
go to post Evgeny Shvarov · Jun 11, 2020 1. Sure 2. it’s not a rule, it’s a recommendation. It’s an attempt to answer the question,If you develop the module which will live with other modules, what the name should be to minimize possible package conflicts
go to post Evgeny Shvarov · Jun 9, 2020 Hi Daniel! Another option is to have several SQL commands in a file, e.g. script.sql and run it one by one with: do $System.SQL.DDLImport("IRIS",$Username,"/path/script.sql") Learn more in documentation.
