We have an ERP system that runs on hundreds of ZEN pages, and we still love it. We just recognize that at some point, we're probably going to have to do some things to maintain it ourselves. I'd love to see it come back if that was an option.

ObjectScript doesn't allow you to overload method definitions. If the method name is the same, the arguments and return types have to match too.

You can define methods that have a variable number of arguments, but you'd have to name yours something else, like New instead of %New.

I'm a big fan of try/catch, but I'm an even bigger fan of "if it ain't broke, don't fix it." This is one of those things that will sound simple, but you'll end up finding out that there are multiple different ztraps at different stack levels and an occasional etrap here and there, and then you end up rewriting way more code than you thought.

If you are accessing them through IIS now (i.e. using port 80) then you just need to get the SSL certificate set up in IIS and you'll be able to access those URLs using HTTPS. Keep in mind that HTTPS by default uses port 443, so you may have to make a firewall change accordingly.

You may also want to consider setting up a URL rewrite so that requests that come in as HTTP are redirected to their new HTTPS versions.

Are you using a CSP or a Zen page? In one of your comments you mentioned Zen.

That's also not the correct syntax for calling a class method. It would be:

#server(##class(MyOrders.WO).retGetWO(wo))#;

That's assuming this is all in the class MyOrders.WO.

I don't think there is a really good way to do exactly this through JDBC, but you can handle this using the JDBC URL if you do a little setup beforehand.

First, in the SMP, System Administration, Configuration, System Configuration, Namespaces, click on Create New Namespace. Give it a name - let's say "SAMPLE" and have it copy from your original namespace (probably USER).

Second, go into a terminal, switch to the new namespace and use the command:

w $SYSTEM.SQL.Schema.SetDefault("SAMPLE",.oldval,1)

You should get a 1 confirming that the change was made successfully.

At this point, when you make your JDBC connection, connecting to either namespace will work on the same database, but connecting to the SAMPLE namespace will use the sample schema, and the USER namespace will use the SQLUser schema.

@Cristiano Silva, Rochdi is using Ensemble 2018. Does that version automatically configure IIS if you install it after IIS? I could be wrong, but I thought that automatic configuration was only in more recent versions of IRIS.
 

If that's the issue, you could also try the following, and it will post to that location using the parameters you specified with InsertFormData:

set AuthToken = "/B2C_1A_client_credentials_signIn/oauth2/v2.0/token"
set tSc = AuthToken.Post()

You can use the if $i to do some stuff within loops too. For example, if you enter the following to commands in a terminal:

set a = 5
for{if $i(a,-1){w a,!}else{quit}}

This will subtract 1 from a and write its value until it reaches 0, then quit the loop. Of course you could just as easily use for a=4:-1:1 {w a,!} to produce the same output a little more nicely, so you don't see that as much.

You can create a text input and write a method that sets the maxRows property based on what the user puts into that input that fires in the input's onchange.

The document's original source file name is the name the file had when it was received. %f is a shorthand for using that in the file name. If you wanted them all to be named "myfile" with the timestamp on the end, you'd change the Filename property to myfile_%Q%!+(_a)

In SQL, you can use the following query:

select * from %dictionary.compiledclass where primarysuper like '%abc.test.cls%'

Queries to linked tables will fail if there is an issue with the connection, but when it's up, you've got the current data. Copying it over would help with potential connection issues, though you would still have a problem if the connection can't be established when you're trying to copy the data over. But if you're doing that once a day, your data is going to be a day old at times. I think the question you need to be asking is, for your specific application, how important is it that the data you're getting from the external database is current?

Your login request technically is an unauthenticated request, which means it uses the account UnknownUser. Since the web application /api/atelier requires user permission on the %Development resource, the request is failing. You could address this by either removing that restriction from the web app or by assigning the %Developer role to UnknownUser. In my opinion, though, neither of those is really ideal.

I've seen this before when the browser has something cached from the old version. Have you cleared your browser's cached files?