Search

).test() ClassMethod test() { do ..%KillExtent() for len = 100, $$$MaxStringLength - 1, $$$MaxStringLength, $$$MaxStringLength+1, $$$MaxStringLength *2 { set sc = ..save

(community.objectscript.PersistentClass).CreateRecord() Second: SetToTheGlobal of community.objectscript.ClassExample class and passes two parameters: 42 and "Test Data", which is equivalent to the call: do

be used for testing 2. installation steps ① Establish rest Service New web application → configure dispatch class → configure permission

Often when debugging COS code you get an error message such as '<UNDEFINED>test^routine *test' so the first thing you want to do is to take a look at this code and see what

, and explicitly. TEST>set currentLocalTime = $ZDateTime($Horolog,3,,3) TEST>set currentGeneralTime = $ZDateTime($ZTimeStamp,3,,3) TEST>write currentLocalTime 2018-09-20 10:46

version of HealthShare on docker, very useful to do test and build edge on the fly. If you have a license key and a HealthShare Unified Care Record kit, you can run "do ##class

windows server; and the following command is run by the runner irissession IRISHEALTH -U TEST "##class(isc.git.GitLab).load()" we get the following "error" <NOTOPEN>> I do

I produce my monthly Review Report on OEX packages now for 18 months.These are a view figures and some comments: Total packages checked = 669 Packages tested and reviewed

\test) in the SQL Gateway connection However, as the error message suggests, IRIS is trying to connect with PROD\svc_mist, rather than PROD\test configured above

for x86-64) 2016.2 (Build 605U) Thu Feb 25 2016 19:24:57 EST and is not working as well. I have tested with Atelier 1.0.122 (unreleased) and it worked. What's the $ZV of your cloud

option when using Ensemble but I suggest you follow the link above. As Daniel has said.Plus, you might want to unit test them, in which case you need to create an instance of your web

can be automatically pushed downstream to build and test environments; the use of open source Git hooks, %Installer, and Atelier, with Jenkins and automated Unit Tests

The following code snippet is a REGEX that validates characters that are not in English, as well as English characters. The class method "test" takes an email address

have a certain development methodology that either produces less bugs, catches them at a unit test level, or makes tracking them down much easier. Here are my tips... 1. Write

symbols.We can do a simple echo test to prove some of this, this is a pre 2016 CSP page...Class Foo.Hex Extends %CSP.Page{ClassMethod OnPage() As %Status [ ServerOnly = 1 ]{ set