go to post Ben Spead · Mar 4, 2021 There are different kernels but other than that you should be able to run the same ObjectScript code on both platforms and it will behalf identically. If you are going to be doing file interactions, then I suggest using the %File library class which will make your code portable between Windows and UNIX file systems. Likewise if you are calling out to other executables, you will need to instrument your code to call out appropriately based on your platform.
go to post Ben Spead · Feb 18, 2021 I am assuming you want to create a tag-based CSP page as a quick and dirty way to through up some data in a table? If so, the basic steps would be: Load a JS library like https://www.tablefilter.com/ to make your filtering easy Write out your <table> and <th> tags Create a <script language='cache' runat='server'> block to hold your ObjectScript which will fetch your result set Use %SQL.Statement to create and run the query and fetch the data Iterate over the resultset, and write out a row of HTML for each row in the resultset using &html<> End your </script> tag and then end your </table> tag Hope that gets you rolling!
go to post Ben Spead · Jan 5, 2021 This is definitely possible, although it will be very painful :) You can use Studio to edit any sort of flat files on the OS, and Studio has been used for years to edit .js and .css files. You can use Studio to edit the source files for your React or Angular app, but you will then need to use the CLI in order to build your app for testing (you could also roll your own server side source control hooks to do this). So if your organization is currently locked into Studio, this can be done but you'll need to do extra work to make it work. If you have the flexibility, I would strongly recommend that you leverage VSCode rather than Studio for this.
go to post Ben Spead · Dec 31, 2020 please share the doc link you are referring to. ZF calls are still supported and we use them for our source control integration within InterSystems. The zf(-1) has been deprecated and replaced with zf(-100) and you can certainly use that to do the same thing but may need to change your zf input slightly to use 100.
go to post Ben Spead · Dec 15, 2020 No, no - *please* don't encourage the the use of eXecute ... that can make maintenance so very difficult :( Most ObjectScript coding standards I have seen strictly forbid the use of this :)
go to post Ben Spead · Dec 11, 2020 @Rich Taylor - John is correct, server-side source control models are fully supported and that is the dominant model for many (including internal apps at ISC, and our implementations in the field). I did a presentation at Virtual Summit on how to choose between Private / Shared Dev servers and Client-side vs Server-side source control and what the IDE options are for each. Tim Leavitt also did a session on the topic of server-side source control with VSCode. Here are the links: https://learning.intersystems.com/course/view.php?id=1638 https://learning.intersystems.com/course/view.php?id=1615 My team has been very active in the VS Code plug-in testing and development to ensure that it will be fully functional for our serverside source control based workflows.
go to post Ben Spead · Dec 3, 2020 The new UI is now live for all users! Feel free to leave any questions or comments.
go to post Ben Spead · Nov 21, 2020 Unfortunately not - AppS.REST is only supported for InterSystems IRIS as it relies on enhanced JSON support that exists there but not Caché.
go to post Ben Spead · Nov 19, 2020 Thanks for the update George - note, this really isn't a CCR-related question.
go to post Ben Spead · Nov 19, 2020 Sorry @Jeffrey England - I only just saw this now (feel free to use an @ mention in the future). This control doesn't currently include any sort of dropdown. It was based on the System lookup in the old UI where people could just drop in their SysCode to drive navigation. Adding a dropdown of some sort is on the roadmap, but it's not trivial as some people have access to hundreds of Systems (so it's not a simple dropdown - it will eventually be a combination typeahead dropdown which pulls from all Orgs a user has access to). We will be moving live an update to this component soon which makes it more clear that SystemCode is optional (but it will still be a text field). Hope that helps explain things! Ben
go to post Ben Spead · Oct 28, 2020 In that case I can't see how a 1.4 sec query could trigger any sort of timeout from a CSPGateway perspective. I think you have something else going on - maybe an uncaught error in your code?
go to post Ben Spead · Oct 28, 2020 Phuc, Assuming the SQL is being run synchronously from within the CSP page, then the page will not be able to send it's response to the client while it waits for the SQL to complete. Are you saying that the average response time of the query is 1.4 minutes? If so then I think you need to see if you can speed up your query, call for the data asynchronously, or change your CSPGateway configuration so it has a longer timeout.
go to post Ben Spead · Oct 22, 2020 @ZengSheng Niu - do you have a Support contract? If you think you should have access and do not, I suggest you call Support to get your account enabled: https://www.intersystems.com/support-learning/support/
go to post Ben Spead · Oct 5, 2020 You can get a Community Edition of InterSystems IRIS as Evgeny suggested, or if you need a new developer license for your Caché instance you should work with your Account Manager to get one. If you are not sure who your account manager is, contact the WRC who should be able to help direct you.
go to post Ben Spead · Sep 21, 2020 I agree with both Tim and Evgeny. In addition, I will add that we also store our unit tests in a different location, which has a top level of /internal for all of our in-house applications. We store unit tests and test data in /internal so our integration scripts can explicitly ignore changes in those branches when we're porting things to our LIVE branch. This ensures that no testing code or testing data ever make it into production.
go to post Ben Spead · Sep 15, 2020 @Perla Escarcega - that is one of the ways to do a Refresh, yes. You need to first populate all files in your Source Workspace, and then the Refresh will walk the directory contents and load everything in. More details can be found on slides 43-45 of ICC520: ftp://ftp.intersystems.com/isc/customers/ccrtraining/ICC520(Presentation)%20CCR%20Tier%201%20-%20Baselining%20Source%20Code.pdf
go to post Ben Spead · Sep 14, 2020 @Perla Escarcega - taking a closer look at this, I think we had an issue with a historical file clean-up routine which was a little too overeager to reclaim space. All of your source is safe and available but you may need to create a fresh ItemSet to push this source. Note - you should always be making fresh ItemSets anyway because the head revision may be newer than what is in your historical ItemSet, and you don't want to get an older revision of something which breaks when interacting with a newer revision of other items. So simply create a new ItemSet for BASE and deploy it and you should be all set. P.S. This does raise the question of why you are initializing a new Secondary BASE environment from old ItemSets as opposed to just grabbing the head revision of the BASE source and running Refresh to pull it all into the Namespace? I am afraid your approach may be significantly more risky than the recommended approach.
go to post Ben Spead · Sep 14, 2020 Actually - I take back my statement now that I looked at the error more closely. It appears as though it's trying to fetch an ItemSet by ID that doesn't actually exist. What is the CCR in question?
