Why is the H5 Script version different on Cloud environments?

Hello,

I have a general question, we have 2 cloud environments (CE) and we need to use an H5 Script on both.

At first I thought all CE uses ScriptUtil.version >= 2.0 but on one CE I found out that it was lower than 2.0 because when I run the ScriptUtil.version code I get "undefined" in return.

Is there a way to verify which H5 Script version we are using without code and if we can upgrade it to >=2.0 ?

Thanks

Find more posts tagged with

M3 Development

Accepted answers

Legacy Contributor

CE has two UIs Classic and the New UI. Classic UI will return ScriptUtil.version = undefined while the New UI returns ScriptUtil.version = 2.0. The new UI uses Angular JS, has a different framework, and will require other methods to do the same tasks. Within a program in M3, you can select Tools > User Settings > Enable Classic UI, and uncheck if you want to use the New UI. Currently, our company is in transition to the New UI but will have users in the Classic UI for a while still during the transition. To minimize issues during our transition we have been writing code to work with both UIs.

Legacy Contributor

As stated above, Both UIs will have minor differences and scripts will have to be written for one or the other. In our case, we opted to have scripts written for Both UIs. I like to add the following to the beginning of my scripts during the initial declarations. I've included 3 examples below of the initial check, all are the same just formatted differently.

// Example 1: Initial UI Check, Save Variable

if (ScriptUtil.version >= 2.0) {

this.uiVersion = 2; // New UI

} else {

this.uiVersion = 1; // Classic UI

};

// Example 2: Javascript ignores spaces and linebreaks, this can be shortened to one line...

if(ScriptUtil.version >= 2.0){this.uiVersion = 2/**New UI*/}else{this.uiVersion = 1/**Classic UI */};

// Example 3: UI Check can be condensed further...

ScriptUtil.version >= 2.0 ? this.uiVersion = 2 : this.uiVersion = 1;

this saves the variable which can be later used to determine UI Version.

// Initial Declaration example:

var SCRIPTNAME = (function(){

function SCRIPTNAME(scriptArgs){

this.controller = scriptArgs.controller;

this.elem = scriptArgs.elem;

this.args = scriptArgs.args;

this.log = scriptArgs.log;

this.scriptName = 'SCRIPTNAME';

ScriptUtil.version >= 2.0 ? this.uiVersion = 2 : this.uiVersion = 1;

}

I later use a switch case for solutions that are different between the Classic and New UI. Example below:

// Switch Case Example for determining which code to use based on UI...

switch (this.uiVersion) {

case 2:

//New UI Code Here

break;

case 1:

//Classic UI Code Here

break;

};

All comments

Legacy Contributor

antonio-caria

If used "The new UI" many of the scripts will not run...

Rene Bottern

There are minor differences in 'New UI' scripting, and you will have to add this to your code where applicable to make it compatible with 'Old' & 'New' as per below.

if (this.version >= 2.0) {
...
}
else {
...
}

Legacy Contributor

// Example 1: Initial UI Check, Save Variable

if (ScriptUtil.version >= 2.0) {

this.uiVersion = 2; // New UI

} else {

this.uiVersion = 1; // Classic UI

};

// Example 2: Javascript ignores spaces and linebreaks, this can be shortened to one line...

if(ScriptUtil.version >= 2.0){this.uiVersion = 2/**New UI*/}else{this.uiVersion = 1/**Classic UI */};

// Example 3: UI Check can be condensed further...

ScriptUtil.version >= 2.0 ? this.uiVersion = 2 : this.uiVersion = 1;

this saves the variable which can be later used to determine UI Version.

// Initial Declaration example:

var SCRIPTNAME = (function(){

function SCRIPTNAME(scriptArgs){

this.controller = scriptArgs.controller;

this.elem = scriptArgs.elem;

this.args = scriptArgs.args;

this.log = scriptArgs.log;

this.scriptName = 'SCRIPTNAME';

ScriptUtil.version >= 2.0 ? this.uiVersion = 2 : this.uiVersion = 1;

}

I later use a switch case for solutions that are different between the Classic and New UI. Example below:

// Switch Case Example for determining which code to use based on UI...

switch (this.uiVersion) {

case 2:

//New UI Code Here

break;

case 1:

//Classic UI Code Here

break;

};

David Tollet

Very interesting post and replies. Thanks all for this.

In addition, does anyone have listed the changes we should do in a Classic version compatible script versus the new UI ? This will be very helpful to facilitate script migrations that we should do anyway due to the Portal v2 coming very soon.

Many thanks for sharing.

Copyright © 2025 Infor. All rights reserved.