Infor M3 H5 Development Guide: Version 10.3.1, 10.4.0 Published January 2018

Infor M3 H5 Development Guide
Version 10.3.1, 10.4.0

Published January 2018
Copyright © 2019 Infor
Important Notices
The material contained in this publication (including any supplementary information) constitutes and
contains confidential and proprietary information of Infor.
By gaining access to the attached, you acknowledge and agree that the material (including any
modification, translation or adaptation of the material) and all copyright, trade secrets and all other
right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or
interest in the material (including any modification, translation or adaptation of the material) by virtue
of your review thereof other than the non-exclusive right to use the material solely in connection with
and the furtherance of your license and use of software made available to your company from Infor
pursuant to a separate agreement, the terms of which separate agreement shall govern your use of
this material and all supplemental related materials ("Purpose").
In addition, by accessing the enclosed material, you acknowledge and agree that you are required to
maintain such material in strict confidence and that your use of such material is limited to the
Purpose described above. Although Infor has taken due care to ensure that the material included in
this publication is accurate and complete, Infor cannot warrant that the information contained in this
publication is complete, does not contain typographical or other errors, or will meet your specific
requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or
otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or
omissions in this publication (including any supplementary information), whether such errors or
omissions result from negligence, accident or any other cause.
Without limitation, U.S. export control laws and other applicable export and import laws govern your
use of this material and you will neither export or re-export, directly or indirectly, this material nor any
related materials or supplemental information in violation of such laws, or use such materials for any
purpose prohibited by such laws.
Trademark Acknowledgements
The word and design marks set forth herein are trademarks and/or registered trademarks of Infor
and/or related affiliates and subsidiaries. All rights reserved. All other company, product, trade or
service names referenced may be registered trademarks or trademarks of their respective owners.
Publication Information
Release: Infor M3 H5 10.3.1.0, 10.4.0
Publication date: < January 25, 2019 >
Contents
About this guide ................................................................................................................................. 11

Related documents ........................................................................................................................ 11
Contacting Infor.............................................................................................................................. 11
The H5 Scripting Blog .................................................................................................................... 12
Chapter 1 Introduction .................................................................................................................. 13

Scripting overview .......................................................................................................................... 13
Resources ...................................................................................................................................... 13
Creating a script in M3 H5 ............................................................................................................. 14
Contents of a script file .................................................................................................................. 14
Example Script......................................................................................................................... 14
Init method ............................................................................................................................... 14
Element parameter .................................................................................................................. 15
Args parameter ........................................................................................................................ 15
Controller parameter................................................................................................................ 15
Log parameter ......................................................................................................................... 15
Debug parameter (deprecated) ............................................................................................... 15
M3 H5 limitations ........................................................................................................................... 16
M3 H5 script minification................................................................................................................ 16
Chapter 2 Developing scripts ....................................................................................................... 17

Development environment ............................................................................................................. 17
Prerequisites ............................................................................................................................ 17
Using Visual Studio ................................................................................................................. 17
Configuring the project ...................................................................................................... 17
Running Samples .............................................................................................................. 18
Debugging ......................................................................................................................... 18
Adding a new script to the solution ................................................................................... 19
Using VS Code and Node.js .................................................................................................... 19
Infor M3 H5 Development Guide | 3

Contents
Opening project in VS Code.............................................................................................. 19

Running Samples on a Node.js server ............................................................................. 19
Adding a new script to the project ..................................................................................... 20
Debugging in browsers ............................................................................................................ 20
MForms Panel Layout.................................................................................................................... 20
Adding Content to a Form ....................................................................................................... 21
Element layout ......................................................................................................................... 21
Events ...................................................................................................................................... 21
Example ................................................................................................................................... 21
Chapter 3 Deploying scripts ......................................................................................................... 23

Deploying a customized script in M3 H5 ....................................................................................... 23
Chapter 4 Adding scripts to a form.............................................................................................. 25

Adding a personalized script to a form .......................................................................................... 25
Adding a script shortcut ................................................................................................................. 25
Chapter 5 Public APIs.................................................................................................................... 27

API Overview ................................................................................................................................. 27
InstanceController .......................................................................................................................... 27
Properties ................................................................................................................................ 27
ParentWindow: JQuery ............................................................................................... 27
RenderEngine: RenderEngine .................................................................................. 28
Requesting: InstanceEvent .................................................................................... 28
Requested: InstanceEvent ...................................................................................... 28
RequestCompleted: InstanceEvent ....................................................................... 28
Response: ResponseElement .................................................................................... 28
Functions ................................................................................................................................. 28
GetContent() ...................................................................................................................... 28
GetContentElement() ........................................................................................................ 28
GetElement() ..................................................................................................................... 29
GetGrid()............................................................................................................................ 29
GetInstanceId().................................................................................................................. 29
GetMode() ......................................................................................................................... 29
GetPanelName() ............................................................................................................... 30
GetProgramName() ........................................................................................................... 30
GetSortingOrder().............................................................................................................. 30
GetValue() ......................................................................................................................... 30
4 | Infor M3 H5 Development Guide

Contents
GetView()........................................................................................................................... 31
ListOption() ........................................................................................................................ 31
PageDown()....................................................................................................................... 31
PressKey() ......................................................................................................................... 31
SetValue().......................................................................................................................... 31
ShowMessage() ................................................................................................................ 32
ShowMessageInStatusBar() ............................................................................................. 32
Request Event Arguments ............................................................................................................. 32
RequestEventArgs .............................................................................................................. 32
CancelRequestEventArgs ................................................................................................. 33
RenderEngine ................................................................................................................................ 33
Properties ................................................................................................................................ 33
Content: ContentElement ........................................................................................ 33
Functions ................................................................................................................................. 33
ShowMessage() ................................................................................................................ 33
ListControl ...................................................................................................................................... 33
Properties ................................................................................................................................ 34
ListView ......................................................................................................................... 34
Functions ................................................................................................................................. 34
Columns() .......................................................................................................................... 34
GetColumnIndexByName() ............................................................................................... 34
GetPositionFieldValue() .................................................................................................... 34
Headers()........................................................................................................................... 35
ListView .......................................................................................................................................... 35
Functions ................................................................................................................................. 35
GetValueByColumnIndex() ............................................................................................... 35
GetValueByColumnName() ............................................................................................... 35
SelectedItem() ................................................................................................................... 36
SetValueByColumnIndex() ................................................................................................ 36
SetValueByColumnName() ............................................................................................... 36
ScriptDebugConsole (deprecated) ................................................................................................ 37
Functions ................................................................................................................................. 37
WriteLine() ......................................................................................................................... 37
Clear()................................................................................................................................ 37
ScriptLog ........................................................................................................................................ 37
Functions ................................................................................................................................. 38
Error() ................................................................................................................................ 38

Contents
Warning() ........................................................................................................................... 38
Info() .................................................................................................................................. 38
Debug().............................................................................................................................. 38
Trace() ............................................................................................................................... 39
SetDefault() ....................................................................................................................... 39
SetDebug() ........................................................................................................................ 39
SetTrace().......................................................................................................................... 39
ScriptUtil ......................................................................................................................................... 40
Functions ................................................................................................................................. 40
AddEventHandler() ............................................................................................................ 40
ApiRequest() (deprecated) ................................................................................................ 41
DoEnterpriseSearch()........................................................................................................ 41
FindChild() ......................................................................................................................... 41
GetFieldValue() ................................................................................................................. 42
GetUserContext() .............................................................................................................. 42
Launch() ............................................................................................................................ 42
LoadScript() ....................................................................................................................... 43
OpenMenu() ...................................................................................................................... 43
RemoveEventHandler() ..................................................................................................... 43
SetFieldValue().................................................................................................................. 44
SessionCache ................................................................................................................................ 44
Functions ................................................................................................................................. 44
Add() .................................................................................................................................. 44
ContainsKey() .................................................................................................................... 45
Get() .................................................................................................................................. 45
Remove() ........................................................................................................................... 45
InstanceCache ............................................................................................................................... 46
Functions ................................................................................................................................. 46
Add() .................................................................................................................................. 46
ContainsKey() .................................................................................................................... 46
Get() .................................................................................................................................. 47
Remove() ........................................................................................................................... 47
ConfirmDialog ................................................................................................................................ 47
Functions ................................................................................................................................. 48
ShowMessageDialog() ...................................................................................................... 48
ContentElement ............................................................................................................................. 49
Properties ................................................................................................................................ 49

Contents
Children: any[] .......................................................................................................... 49

ContentPanel: JQuery ............................................................................................... 49
Host: JQuery................................................................................................................. 49
Functions ................................................................................................................................. 49
Add() .................................................................................................................................. 49
AddElement() .................................................................................................................... 50
CreateElement() ................................................................................................................ 50
GetContentBody() ............................................................................................................. 51
GetElement() ..................................................................................................................... 51
GetPrevContainer() ........................................................................................................... 51
OnUnload() ........................................................................................................................ 51
Unload() ............................................................................................................................. 52
MFormsAutomation ....................................................................................................................... 52
Functions ................................................................................................................................. 52
addStep() ........................................................................................................................... 52
addField() .......................................................................................................................... 53
setFocus().......................................................................................................................... 53
toEncodedURI()................................................................................................................. 53
MIService ....................................................................................................................................... 54
Functions ................................................................................................................................. 54
executeRequest() .............................................................................................................. 54
execute()............................................................................................................................ 54
IonApiService (For MUA 10.4 only) ............................................................................................... 55
Functions ................................................................................................................................. 55
execute()............................................................................................................................ 55
getBaseUrl() ...................................................................................................................... 56
Chapter 6 MForms Automation .................................................................................................... 57

What is MForms Automation? ....................................................................................................... 57
Automation Sequences.................................................................................................................. 57
Automation Steps .................................................................................................................... 58
Automation Fields .................................................................................................................... 58
Example............................................................................................................................. 59
Automation XML ...................................................................................................................... 59
Examples ........................................................................................................................... 59
Starting Automations in M3 H5................................................................................................ 60
URI Format ........................................................................................................................ 60
Example............................................................................................................................. 60

Contents
Helper Class ............................................................................................................................ 60
Chapter 7 MI Service...................................................................................................................... 61
MIRequest...................................................................................................................................... 61
Example ......................................................................................................................................... 62
Chapter 8 Drillback ........................................................................................................................ 63

Invoking a drillback ........................................................................................................................ 63
infor.companyon.client.sendPrepareDrillbackMessage() ....................................................... 63
Drillback parameters ...................................................................................................................... 63
Examples ................................................................................................................................. 64
Chapter 9 ION API (For MUA 10.4 only) ....................................................................................... 67

Prerequisites .................................................................................................................................. 67
IonApiService ................................................................................................................................. 67
OAuth access token ................................................................................................................ 67
IonApiRequest ......................................................................................................................... 68
IonApiResponse ...................................................................................................................... 68
Development environment ............................................................................................................. 69
Acquire an OAuth token string ................................................................................................ 69
Set the token as a script argument ......................................................................................... 69
Chapter 10 Best practices ............................................................................................................... 71

Use H5 functions and properties that are documented ................................................................. 71
Use recommended API functions .................................................................................................. 71
Use proper logging utility ............................................................................................................... 72
Use TypeScript .............................................................................................................................. 72
Be wary of using ES6/ES2016 features ........................................................................................ 72
Minify scripts .................................................................................................................................. 72
Chapter 11 Script examples ............................................................................................................ 73

H5SampleHelloWorld.ts................................................................................................................. 73
H5SampleUserDetails.ts................................................................................................................ 74
H5SampleShowXml.ts ................................................................................................................... 75
H5SampleAddElements.ts ............................................................................................................. 76
H5SampleOptionButton.ts ............................................................................................................. 79
H5SamplePreviewListHeader.ts .................................................................................................... 81

Contents
H5SampleShowOnMap.ts ............................................................................................................. 83
H5SampleMFormsAutomation.ts................................................................................................... 84
H5SampleRegexValidator.ts ......................................................................................................... 86
H5SampleRequestTracer.ts .......................................................................................................... 89
H5SampleCancelRequest.ts ......................................................................................................... 90
H5SampleOpenFieldHelp.ts .......................................................................................................... 92
H5SampleCustomColumns.ts ....................................................................................................... 92
H5SampleMIService.ts .................................................................................................................. 94
H5SampleImageFromList.ts .......................................................................................................... 97
H5SampleDrillback.ts .................................................................................................................... 99
H5SampleIonApiService.ts .......................................................................................................... 101
Chapter 12 Appendix ..................................................................................................................... 105

Node.js ......................................................................................................................................... 105
Install Node.js ........................................................................................................................ 105
Verify the Node package manager ........................................................................................ 105
Verify the Node executable ................................................................................................... 106
TypeScript .................................................................................................................................... 106

About this guide
The M3 H5 Development Guide provides conceptual and how-to information for developing,
deploying and adding scripts to MForms. It also contains information about the public APIs and script
examples that the user can use as a guide in scripting.
This guide is for developers who want to create and deploy scripts for M3 H5.
Related documents
You can find the documents in the product documentation section of the Infor Xtreme Support portal,
as described in the following section.
M3 UI Adapter Installation Guide for LifeCycle Manager 9.x
M3 UI Adapter Installation Guide for LifeCycle Manager 10.x
M3 Core Administration Guide - Windows
Infor M3 H5 User and Administration Guide
Contacting Infor
If you have questions about Infor products, go to the Infor Xtreme Support portal at
www.infor.com/inforxtreme.
If we update this document after the product release, we will post the new version on this Web site.
We recommend that you check this Web site periodically for updated documentation.
If you have comments about Infor documentation, contact documentation@infor.com.

Introduction
The H5 Scripting Blog
We recommend visiting the H5 scripting blog for information, feedback, and questions.
https://smartofficeblog.com/h5-scripting/

Chapter 1 Introduction
1
Scripting overview
You can use one or more scripts that can be connected to a form to extend the functionality of M3
forms in H5. By adding a script to a form, the script has access to the form, and can add and modify
content.
These scripts are a type of personalization and are deployed to a server as JavaScript files using an
administration tool. It will have access to public classes exposed by the M3 H5 framework.
Scripts can be developed using JavaScript or TypeScript but the latter is preferred for it adds typing,
compilation and refactoring support. More information on developing with TypeScript is provided in
the next chapter.
Scripts can also use jQuery, a fast, small, and feature-rich JavaScript library that makes tasks, such
as HTML document traversal and manipulation, event handling, animation, and Ajax, much simpler
with an easy-to-use API that works across a multitude of browsers.
Resources
Following is a list of resources to develop scripts:
For information about URL

jQuery API Documentation http://api.jquery.com/
TypeScript http://www.typescriptlang.org/docs/tutorial.html
Template and Samples (KB 1909067) https://www.inforxtreme.com/espublic/EN/answerlinkdot
net/SoHo/Solutions/SoHoViewSolution.aspx?SolutionID
=1909067

Introduction
Creating a script in M3 H5
Scripts can be created using a Web development IDE or an external text editor as these are client-
side scripts only. The development setup and script debugging are detailed in the next chapter.
Contents of a script file

A script file must follow certain rules to be used by the H5 framework. If the script does not follow
these rules, it will not be executed.
• The script class name must match the script file name (excluding the file extension).
• The script must have a public function called Init with a specific signature.
Important: If there is a mismatch between the script class and the script file name, the script will not
work when it is deployed to the server.
Example Script
var test = new function{
this.Init = function(scriptArgs){
var controller = scriptArgs.controller;
var args = scriptsArgs.args;
var element = scriptArgs
var log = scriptArgs.log;
/* Write code here */

}
}
The following method and parameters describe the content of the script file.
Init method
The script must have a public function called Init with this signature:
/* Write code here */
}
The scriptArgs parameter of the Init method contains JSON object that can be used to access
elements or objects from the framework. These parameters are detailed in the following sections.

Introduction
Element parameter
The element parameter is the control to which the script is connected. The argument is null if the
script is not connected to a specific element. The element parameter can be a TextBox, ComboBox,
CheckBox, and so on, depending on which element the script is attached to. To access the element:
var element = scriptArgs.elem;
}
Args parameter
The args parameter contains the script arguments string. The value is null if no arguments were
specified. To access args:
var args = scriptArgs.args;
}
Controller parameter
The controller is the InstanceController for the current program. This is used to access the
content of an M3 form. To access the controller:
var controller = scriptArgs.controller;
}
Log parameter
The log parameter is an instance of ScriptLog and can be used for logging to the browser
console. To access log:
var log = scriptArgs.log;
}
Debug parameter (deprecated)

The debug parameter is an instance of the class ScriptDebugConsole. This has been deprecated
in favor of the log propery. To access debug:

Introduction
var debug = scriptArgs.debug;
}
M3 H5 limitations
The H5 scripts have more limitations compared to MForms JScript in SmartOffice, mostly due to the
web platform and not specific to H5. Some examples of the limitations are as follows:
• No access to file system or applications
• Cross domain calls are not allowed by default
• Browser restrictions for window/iframe access
M3 H5 script minification
The H5 script files should be minified before they are deployed in a production environment. When
files are minified, there is less data to download, code comments are removed, and code is
obfuscated. There are also several open source script minifiers that are available and one of them
can be found at http://yui.github.io/yuicompressor/ .

Chapter 2 Developing scripts
2
This chapter describes how to set up the development environment, run the Samples project, and
add content to an H5 form via script written in TypeScript.
All the code examples from here on are written in TypeScript. The typing files are available for the
H5 APIs, jQuery and other frameworks.
Development environment
Prerequisites
To develop and test scripts, you will need an editor for the source files, and a web server for hosting
the files. Tools such as Visual Studio have a source code editor, debugger, and built-in web server,
while some only have a source code editor and a support for running command line tools.
The following is a selection of the tools that can be used for developing scripts:
• Visual Studio Professional or Enterprise
o Requires a license
o Minimum version is Visual Studio 2013 with update 4
• Visual Studio Community
o Free version of Visual Studio with limited functionality
• Visual Studio Code + Node.js web server
o Visual Studio Code is free and runs on Windows, macOS and Linux
Using Visual Studio
Configuring the project

1 Open the H5 Script samples solution (Samples.sln).
2 Right click Samples tree item.

Developing scripts
3 Select Properties menu item.

4 Select Web tab.
5 Select Start URL radio button.
6 Set Start URL.
Here, the localScript parameter points to a single local script. The scriptCache parameter
disables script caching for development.
a URL templates
i) <H5 URL>?localScript=<IIS Express URL>/<Script name>
ii) <H5 URL>?scriptCache=false&localScript=<IIS Express URL>/<Script name>
b Example URLs:
i) https://server.infor.com:23008/mne/?localScript=http://localhost:49482/H5SampleHelloWorld.
js
ii) https://server.infor.com:23008/mne/?scriptCache=false&localScript=http://localhost:49482/H
5SampleHelloWorld.js
7 Save.
Running Samples
1 Open the H5 Script samples solution (Samples.sln).
2 Make sure that the project has been properly configured, as described in the previous section.
3 Modify the script name in the Start URL if needed.
4 Debug the project with F5 or run with Ctrl+F5. The M3 H5 application will be opened.
Debugging
Note: When running in Chrome, the same origin policy needs to be disabled.
1 Set a breakpoint in a script file.
2 To start debugging, press F5.
3 Log on to H5.
4 Start the M3 program where the script should be tested.
5 Select Tools menu item.
6 Select Scripts… menu item under Personalize.
7 Type in the edit box the script name and optional arguments.
8 Click Add.

Developing scripts
9 Click Save.
10 Refresh the panel with the Refresh button in the toolbar or press F5.
11 The breakpoint should be hit in Visual Studio.
Adding a new script to the solution

Alternatively, you can use the H5ScriptsProjectTemplate solution that is included in the SDK.
1 In the solution, right click on the project tree item.
2 Click Add > New Item.
3 Select Web > TypeScript File.
4 Enter Name.
5 Click Add.
Using VS Code and Node.js
Opening project in VS Code

1 Open Folder
2 Select H5ScriptSDK/Samples/Samples
This is the directory that contains the tsconfig.json file.
Running Samples on a Node.js server

1 To use a Node.js server, follow the instructions in the Appendix and make sure they are correctly
installed before trying to run the samples.
2 Double-click InstallWebServer.cmd and wait for the installation to complete.
3 Double-click StartWebServer.cmd after the web server installation. Open this file in a text editor
to modify the port number.
4 Open a browser and navigate to http://localhost:8080 to verify that the server is up.
If the default port (8080) is available, the web server will be started. If the server does not start,
check that the port is available. If the port is not available, try to start the server on another port
by editing StartWebServer.cmd in a text editor. If there are other issues with the installation,
check that NPM and Node.js is installed according to the information in the Appendix.
5 Navigate to the following URL:
<H5 URL>?scriptCache=false&localScript=<Node.js server URL>/<Script name>

Developing scripts
• Example:
https://server.infor.com:23007/mne/?localScript=http://localhost:8080/H5SampleHelloWorld.js
• To verify that the script is accessible, navigate to <Node.js server URL>/<Script name>.
Example:
http://localhost:8080/H5SampleHelloWorld.js
6 Log on to H5.
7 Start the M3 program where the script should be tested.
8 Select Tools menu item.
9 Select Scripts… menu item under Personalize.
10 Type in the edit box the script name and optional arguments.
11 Click Add.
12 Click Save.
13 Refresh the panel with the Refresh button in the toolbar or press F5.
Adding a new script to the project

1 File > New File
2 Enter file name with .ts extension, e.g., H5Test.ts.
3 Ctrl + S to save. This automatically transpiles the script to JavaScript, e.g., H5Test.js.
4 To manually compile files, Ctrl + Shift + B.
Debugging in browsers
Internet Explorer 11 and Chrome have good developer tools. To open the tools in both browsers,
press F12.
TypeScript can also be debugged in IE and Chrome using debugger map files.
MForms Panel Layout

The form that shows the content of an M3 program is located between the command bar and the
status bar. This is the form that can have its content modified by scripts. The layout of the contents
of a form is displayed based on the computed positioning of each element passed from an M3
program.

Developing scripts
Adding Content to a Form

The form elements can be accessed through the ContentElement, which can be retrieved from
the InstanceController. To add content to the panel, call the ContentElement.AddElement
function.
Element layout
The standard content is positioned on the form using the Top, Left, Width, and Height properties
of the PositionElement class. When you add custom elements to a form, the elements should
always be positioned using these properties.
Events
Because M3 H5 is a web-based application, script developers can utilize the default events of the
browser for the elements. For button elements, the commonly used event is the click event, which
can be used to perform additional validation and to properly handle the data to be submitted or
passed.
Events must also be properly handled. This means that some events may need to be unsubscribed
or turned off after usage to prevent memory leaks or multiple calls to the same script of different
instances. Data that is used inside the event must also be passed properly to avoid having
anonymous functions, which also causes memory leak.
Example
class H5Sample {
public static Init(args: IScriptArgs): void {
const buttonElement = new ButtonElement();
buttonElement.Name = "btnFoo";
buttonElement.Value = "Foo";
buttonElement.Position = new PositionElement();
buttonElement.Position.Top = 3;
buttonElement.Position.Left = 1;
buttonElement.Position.Width = 5;
const contentElement = args.controller.GetContentElement();

const button = contentElement.AddElement(buttonElement);
button.click({}, () => {
args.log.Info("Foo was clicked.");
});

Developing scripts
}
}
This TypeScript example transpiles to the following JavaScript code:
var H5Sample = (function () {
function H5Sample() {
}
H5Sample.Init = function (args) {
var buttonElement = new ButtonElement();
buttonElement.Name = "btnFoo";
buttonElement.Value = "Foo";
var contentElement = args.controller.GetContentElement();
var button = contentElement.AddElement(buttonElement);
button.click({}, function () {
args.log.Info("Foo was clicked.");
});
};
return H5Sample;
}());

Chapter 3 Deploying scripts
3
Deploying a customized script in M3 H5

When a script has been developed and tested, it must be uploaded to M3 H5 in order to be available
to other users.
To upload an H5 script:
1 Go to Administration Tools.
2 Go to Data files tab.
3 Select H5 Script as file type in dropdown.
4 Click Import and locate script file.
Note: For scripts developed in TypeScript, make sure to upload the transpiled JavaScript (.js) file,
not the TypeScript (.ts) file.

Chapter 4 Adding scripts to a form
4
Adding a personalized script to a form

Scripts can be added to an M3 H5 form as a personalization. A script personalization can be created
by one user and then deployed to many users using global or role personalizations.
The Personalized Scripts dialog can be used to connect scripts to elements on a form.
In the form:
1 Select Tools > Personalization > Scripts
2 Select a Target element from the list. The selected element will be connected and passed as an
argument to the script. Select the blank option if there is no target element.
3 Input the name of the name of Script. This should match the name of the uploaded script.
4 Specify the script Arguments. This is optional.
5 Click Add.
6 Click Save.
7 Refresh the form for the script to take effect.
Note: If no other steps are taken, the script becomes active only for the user who created the
personalization. Scripts can be associated with roles or assigned to run globally.
Adding a script shortcut

Scripts can also be connected to shortcuts.
In the form:
1 Open the Shortcuts dialog.
a Expand Toolbox at the right side of the panel.
b Click the Shortcuts icon.
2 Expand the Advanced area.

Adding scripts to a form
3 Specify the Name and Value of the shortcut. These are the texts that will be displayed in the
toolbox.
4 Select the Script name from the list.
5 Specify the script Arguments. This is optional.
6 Click Add.
7 Click Save.

Chapter 5 Public APIs
5
API Overview
There are many public classes, methods, and properties in M3 H5 but only a number of these are
allowed for use by scripts. Many classes are public for technical reasons but should only be used
internally by the M3 H5 framework.
In scripts, use only public classes that are documented. This ensures that scripts will not break when
updated version of M3 H5 are installed.
This chapter provides the methods and properties of classes that are allowed to be used from
scripts. There are code examples on how to use them in the TypeScript syntax. The colon (:) is used
to denote variable type. Some code use arrow functions (=>), which capture the this where the
function is created rather than where it is invoked. For more information, please see the TypeScript
Handbook. The following examples are not complete and are mainly used to show the syntax.
InstanceController
Each running M3 program has one controller object. The controller provides access to the content of
a panel through the RenderEngine property and makes it possible to trigger the function keys and
list options from script code.
Properties
ParentWindow: JQuery
The current panel

Public APIs
RenderEngine: RenderEngine
Holds controls in a panel. See RenderEngine.
Requesting: InstanceEvent
This is a cancelable event that is raised when H5 is about to make a server request. It can be used
to validate the panel before a request is started and cancel the event if the validation fails. See
Request Event Arguments.
Requested: InstanceEvent
This event is raised just before each call to the server and can be used to unsubscribe to events on
a panel and clean up other resources. See Request Event Arguments.
RequestCompleted: InstanceEvent
This event is raised when a server request is done. See Request Event Arguments.
Response: ResponseElement
The response for the M3 programs.
Functions
GetContent()
Gets the content panel
Returns: JQuery – A content panel
Example:
let myContent = this.controller.GetContent();
GetContentElement()
Gets the content element
Returns: ContentElement
Example:

Public APIs
let myContentElement = this.controller.GetContentElement();
GetElement()
Gets a named child element on the panel
Returns: JQuery – The element
Example:
let myElement = this.controller.GetElement();
GetGrid()
Gets the current data grid
Returns: A data grid or null if there is no grid on the current panel
Example:
let myGrid = this.controller.GetGrid();
GetInstanceId()
Gets the ID for the current program instance
Returns: string - An instance id
Example:
let myIid = this.controller.GetInstanceId();
GetMode()
Gets the current panel mode
Returns: string
The panel mode on a detail panel will be one of:
“1” – Create
“2” – Change
“3” – Copy
“4” – Delete
“5” – Display
“” – The panel mode will be blank on list panels and in other cases when the detail panel modes
do not apply

Public APIs
Example:
let myMode = this.controller.GetMode();
GetPanelName()
Gets the current panel name
Returns: string
Example:
let myPanelName = this.controller.GetPanelName();
GetProgramName()
Gets the current program name
Returns: string
Example:
let myProgramName = this.controller.GetProgramName();
GetSortingOrder()
Gets the current sorting order
Returns: string
Example:
let mySortingOrder = this.controller.GetSortingOrder();
GetValue()
Gets the value of a field on the current panel
Parameter:
name: string – Name of the element
Returns: string – A value or null
Example:
let myValue = this.controller.GetValue(“elemName”);

Public APIs
GetView()
Gets the current view
Returns: string – A view or null if no view exists
Example:
let myView = this.controller.GetView();
ListOption()
Executes a list option request
Parameter:
option: string – The option to execute, 1-99
Returns: void
Example:
this.controller.ListOption(“5”);
PageDown()
Executes a page down request
Returns: void
Example:
this.controller.PageDown();
PressKey()
Executes a key request
Parameter:
key: string – The key to press, F1-F24 or ENTER
Returns: void
Example:
this.controller.PressKey(“F5”);
SetValue()
Sets the value of a field on the current panel
Parameters:

Public APIs
name: string – The element name

val: any – The element value to set
Returns: void
Example:
this.controller.SetValue(“elemName”, “elemValue”);
ShowMessage()
Shows a message in the status bar or in a message box depending on the settings for the current
user
Parameter:
message: string – The message to show
Returns: void
Example:
this.controller.ShowMessage(“This is a validation message”);
ShowMessageInStatusBar()
Shows a message in the status bar
Parameter:
message: string – The message to show
Returns: void
Example:
this.controller.ShowMessageInStatusBar(“This is a validation message”);
Request Event Arguments

These are the event arguments for the Requesting, Requested and RequestCompleted
events. For an example on how to cancel a request, see the Script examples chapter.
RequestEventArgs
Provides data for a request event.

Public APIs
CancelRequestEventArgs
Provides data for a cancelable request.
RenderEngine
The RenderEngine class generates the controls on a panel and can be used to update or add
content to a panel from scripts.
Properties
Content: ContentElement
Provides access to the content panel of an M3 panel. See ContentElement.
Functions
ShowMessage()
Shows a message in the status bar or in a dialog depending on the user settings.
This function is identical to InstanceController’s ShowMessage().
Parameter:
msg: string – The message to be displayed
Returns: void
Example:
this.controller.ShowMessage(“The order number must be entered.”);
ListControl
ListControl is a wrapper object for the list that provides access to the actual ListView control and
other data related to the list

Public APIs
Properties
ListView
Sub-class for the actual control of the list. See ListView API.
Functions
Columns()
Provides the column name(s) of the current displayed list
Returns: string[] – An array containing the four-character column name(s) of the list. This will
return an empty array if there is no column or if there is no list available.
GetColumnIndexByName()
Provides the zero-based index of a specified column name
Parameter:
colName: string – The four-character name of the column
Returns: number
Example:
let myIndex = ListControl.GetColumnIndexByName(“ITNO”);
GetPositionFieldValue()
Gets the value of the position field of a specified column
Parameter:
colName: string – The name of the column field
Returns: string – This will return an empty string if the column is not found, or the column does
not have a position field.
Example:
let myPosFieldVal = ListControl.GetPositionFieldValue(“MMITNO”);

Public APIs
Headers()
Returns the original text for each column header(s)
Column headers can be modified using the Label personalization therefore the returned value(s)
using this method may be different from the actual displayed header text(s).
Returns: string[] – An array containing the text for each column header(s). This will return an
empty array if there is no column or if there is no list available.
Example:
let myHeaders = ListControl.Headers();
ListView
Functions
GetValueByColumnIndex()
Collects all the selected item(s) then gets the values relative to the specified column index
Parameter:
colIdx: number - The column index from which the value will be retrieved
Returns: string[] – An array of value(s) of the provided column index of the selected item(s).
This will return an empty array if there is no selected item or if there is no list available. null will be
returned if column index in not found.
Example:
//Get values of the first column for the selected list rows
let result = ListControl.ListView.GetValueByColumnIndex(0);
GetValueByColumnName()
Collects all the selected item(s) then gets the values relative to the specified column name
Parameter:
colName: string – The column name from which the value will be retrieved
Returns: string[] – An array of value(s) of the provided column name of the selected item(s).
This will return an empty array if there is no selected item or if there is no list available. null will be
returned if column index in not found

Public APIs
Example:
//Get values of the ITNO column for the selected list rows
let result = ListControl.ListView.GetValueByColumnName(“ITNO”);
SelectedItem()
Gets the selected rows in the list
Returns: number[] – A sorted array of zero-based row number(s) of the selected item(s). This will
return an empty array if there is no selected item or if there is no list available.
Example:
let selected = ListControl.ListView.SelectedItem();
SetValueByColumnIndex()
Sets the value of a column of an editable list corresponding to the index
The value will be set to the first item of the list if there is no selected item. If there are selected items,
the value will be set to the first selected item.
Parameters:
colIdx: number – The zero-based column index to which the value will be set
value: string – The value to set
Returns: void
Example:
ListControl.ListView.SetValueByColumnIndex(0, “newValue”);
SetValueByColumnName()
Sets the value of a column of an editable list corresponding to the name
The value will be set to the first item of the list if there is no selected item. If there are selected items,
the value will be set to the first selected item.
Parameters:
colName: string – The column name to which the value will be set
value: string – The value to set
Returns: void
Example:

Public APIs
ListControl.ListView.SetValueByColumnIndex(0, “newValue”);
ScriptDebugConsole (deprecated)
The ScriptDebugConsole class can be used to write debug trace messages during the development
of a script. This class is now deprecated starting from version 10.3.0.0 of M3 H5. Consider using the
ScriptLog API instead.
Functions
WriteLine()
Writes a string and a new line character to the browser console.
Parameters:
text: string – The string to display
Returns: void
Example:
ScriptDebugConsole.WriteLine(“testValue”);
Clear()
Clears all text written to the console.
Returns: void
Example:
ScriptDebugConsole.Clear();
ScriptLog
The ScriptLog is used in place of the ScriptDebugConsole starting from version 10.3.0 of M3 H5.

Public APIs
Functions
Error()
Logs an error.
Parameters:
message: string – The message to be logged
Returns: void
Example:
let log = scriptArgs.log;
log.Error(“errorMessage”);
Warning()
Logs a warning message that might warn of potential problems.
Parameters:
Returns: void
Example:
log.Warning(“warningMessage”);
Info()
Logs a message about an information at the log files.
Parameters:
Returns: void
Example:
log.Info(“infoMessage”);
Debug()
Logs debug messages that is of main use for developers.

Public APIs
Parameters:
Returns: void
Example:
log.Debug(“debugMessage”);
Trace()
Logs messages that are very detailed and are intended only for development.
Parameters:
Returns: void
Example:
log.Trace(“traceMessage”);
SetDefault()
The SetDefault method makes the log level the same as Info().
Returns: void
Example:
log.SetDefault();
SetDebug()
The SetDebug method makes the log level the same as Debug().
Returns: void
Example:
log.SetDebug();
SetTrace()
The SetTrace method makes the log level the same as Trace().

Public APIs
Returns: void
Example:
log.SetTrace();
ScriptUtil
The ScriptUtil class contains utility methods scripts can use.
Functions
AddEventHandler()
Attaches an event handler to an element
You can also include a namespace for the event handler that you want to attach by adding the (.)
character plus the namespace that you want to the eventType parameter. The namespace can be
used to remove just the event handler that you attached when you use the
ScriptUtil.RemoveEventHandler method.
Parameters:
element: jQuery – The element to which the event handler will be attached
eventType: string – The event type to which the handler will respond. Examples of event
type are “click”, “mousedown ”, “mousemove”, etc. The eventType parameter can also
include the namespace for the event handler. Examples are “click.myClick” and
“mouseDown.myMousedown”.
callback: function(e: Event) – The callback method to execute when the event occurs.
The callback method receives the Event object as a parameter.
paramData (optional): any – Holds parameters to be passed the callback method. This will
become the paramData property of the Event object of the callback parameter.
Returns: void
Example:
let eventParam = { field1: “myField1”, field2: “myField2” };
ScriptUtil.AddEventHandler(button, "click", (event) => {
//Do something
});
ScriptUtil.AddEventHandler(myButton, " click.myClickEvent", function(event){
//Do something

Public APIs
}, eventParam);
ApiRequest() (deprecated)
Executes an M3 API call to the server. This function has been deprecated in favor of MIService.
Parameters:
URL: string – The request URL to the M3 API
onSuccess (optional): function(result : Object) – The function to execute if the
request is successful; accepts the result Object from the server response as parameter
onFail (optional): function(e : Object, msg : string) – The method to execute if
there is an error in the request; accepts the error Object and the error message as parameters.
Use null as value for onSuccess to pass an onFail parameter only.
Returns: void
Example:
ScriptUtil.ApiRequest(url,
(result) => {
this.onSuccess(result)
}, (e, msg) => {
this.onError(e, msg)
});
DoEnterpriseSearch()
Sets value in the search input and execute the search functionality
This method can be used to execute a search query in the list of an M3 panel.
Parameter:
query: string – The string to search for
controller (optional): InstanceController – The instance controller; uses the active
controller by default
Returns: void
Example:
ScriptUtil.DoEnterpriseSearch(“myQuery”);
FindChild()
Finds an element in the panel
Parameters:

Public APIs
parent: jQuery – The parent node of the element to find

elementName: string – The name of the element to find
Returns: jQuery
Example:
ScriptUtil.FindChild(parent, “myChild”);
GetFieldValue()
Gets the value of a specified field
Parameter:
fieldName: string – The name of the field whose value will be retrieved
Returns: string – The value of the field, or null if the field cannot be found.
Example:
ScriptUtil.GetFieldValue(myTextbox.attr("id"));
GetUserContext()
Gets user context data that contains login information of the user
Parameter:
contextProp (optional): string – The name of the context property to get
Returns: string – The value of the specified user context property. This will return null if the
property is not found. If no parameter is passed, the whole user context data object will be returned
Example:
let myCompany = ScriptUtil.GetUserContext("CurrentCompany"); //”136”
let myContext = ScriptUtil.GetUserContext();
this.log.Info(myCompany === myContext.CurrentCompany); //true
Launch()
Launches a program, file or a URL.
The default handler of the operation is used to find the program for the files or URLs.
Parameter:
task: string – A program name, file name or URL to execute

Public APIs
Returns: void
Example:
let uri = 'https://www.google.com/maps/dir/' + encodeURI(address);
ScriptUtil.Launch(uri);
LoadScript()
Loads an external script file from the script repository
The script file must contain a class with the same name as the file.
Parameters:
URL: script – The location of the script file to be loaded
callback: function(data: string)– A callback method to execute after the script has
been loaded. The callback method receives the string content of the loaded script file.
Returns: void
Example:
ScriptUtil.LoadScript("scripts/SampleExternalScript.js", data => { });
OpenMenu()
Displays a menu located in the menu bar
Parameter:
menuName: string – The name of the menu to open
Returns: void
Example:
ScriptUtil.OpenMenu(menuName);
RemoveEventHandler()
A utility method for removing event handlers that are attached to an element
If you attached the event handler using ScriptUtil.AddEventHandler method and included a
namespace for the event handler, you will be able to remove only that specific handler.
Parameters:
element: jQuery – The element from which the event handler will be removed

Public APIs
eventType: string – The event type for which the handler will be removed. Examples of
event type are click, mousedown, mousemove, etc. The eventType parameter can also use
a namespace associated to the event handler by adding a (.) character plus the namespace of
the handler. Examples are click.myClick and mouseDown.myMousedown. This will allow
you to remove only the event type under that namespace.
Returns: void
Example:
ScriptUtil.RemoveEventHandler(buttonElement, “click”);
ScriptUtil.RemoveEventHandler(buttonElement. “click.myClickEvent”);
SetFieldValue()
Sets the value of a specified field
Parameters:
fieldName: string – The name of the field whose value will be set
value: string – The value to set. This accepts true and false for a checkbox field
Returns: void
Example:
let field = ScriptUtil.GetFieldValue(myTextbox.attr("id")).toUpperCase();
ScriptUtil.SetFieldValue(field, “myValue”);
SessionCache
The SessionCache is a helper class for scripts to cache items in the MForms session. Make sure to
use unique key names to avoid conflicts with other scripts when you add content to the cache.
Functions
Add()
Adds value to the cache.
If a value with the same key exists, it will be overwritten.

Public APIs
Parameters:
key: string – The key of the value to add
value: any – The value to add
Returns: void
Example:
SessionCache.Add(“progName”, “MMS001”);
ContainsKey()
Checks if a key exists in the session cache
Parameters:
key: string – The key to check
Returns: boolean - true if the key exists, false otherwise.
Example:
if(SessionCache.ContainsKey(“myKey”)) {
//Do something
}
Get()
Gets a value from the session cache
Parameter:
key: string – The key of the value to get
Returns: any – The cached value. This will return null if key is not found.
Example:
let myCachedProgram = SessionCache.Get(“myProgram”);
Remove()
Removes a value from the session cache
Parameter:
key: string – The key of the value to remove
Returns: boolean – true if the key existed, false otherwise.
Example:
if(SessionCache.Remove(“myKey”) {

Public APIs
this.log.Info(“myKey was removed”);

}
InstanceCache
The InstanceCache is a helper class for scripts to cache items for a specific MForms instance. Make
sure to use unique key names to avoid conflicts with other scripts when adding content to the cache.
Functions
Add()
Adds a value to the instance cache
If a value with the same key exists, it will be overwritten.
Parameters:
controller: InstanceController – The controller for the instance
key: string – The key of the value to add
value: any – The value to add
Returns: void
Example:
InstanceCache.Add(this.controller, “myKey”, true);
ContainsKey()
Checks if a key exists in the instance cache
Parameters:
key: string – The key to check
Returns: boolean - true if the key exists, false otherwise.
Example:
const key = this.scriptName;
if (InstanceCache.ContainsKey(this.controller, key)) {

Public APIs
// The key exists in cache

}
Get()
Gets a value from the instance cache
Parameter:
key: string – The key of the value to get
Returns: any – The cached object. This will return null if key is not found.
Example:
let myCachedValue = InstanceCache.Get(this.controller, “myKey”);
Remove()
Removes a value from the instance cache
Parameter:
key: string – The key of the value to remove
Returns: boolean – true if the key existed, false otherwise.
Example:
if(InstanceCache.Remove(this.controller, “myKey”) {
this.log.Info(“myKey was removed”);
}
ConfirmDialog
The ConfirmDialog class contains a method for showing the kinds of dialogs that conform to the
design system of M3 H5.

Public APIs
Functions
ShowMessageDialog()
The ShowMessageDialog takes in an JSON object that can be used to define what type of Message
Dialog to be displayed.
Parameters:
options: Object – A JSON object that contains the options that is available for configuring
the Message Dialog to be shown.
options.dialogType (optional): string – Determines what type of dialog to be
displayed. It can be “Question”, “Information”, “Warning” or “Error”. Default value would be
“Information”. “Warning” would be used if it is not a valid type.
options.header: string – The dialog header.
options.message: string – More detailed message to be displayed in the dialog.
options.id: string – Only required for Warning and Question dialogs.
options.withCancelButton (optional): boolean – Optional property that flags if a
cancel button should be displayed or not.
options.isCancelDefault (optional): boolean – Optional property that flags if the
cancel button is the default button or not.
Returns: void
Example 1:
let headerMsg = “Test Header”;
let msg = “This is a Sample Message Dialog”;
let options = {
dialogType: “Information”,
header: headerMsg,
message: msg,
id: “testScript”
};
ConfirmDialog.ShowMessageDialog(options);
Example 2:
//Retrieving the user response in a Question dialog
ConfirmDialog.ShowMessageDialog({
header: “My Question”,
message: “Are you?”,
dialogType: “Question”,
closed: (ret) => {

Public APIs
//If user selects Ok, ret.ok is True and ret.cancel is False

this.log.Info("Ok: " + ret.ok + " Cancel: " + ret.cancel);
}
});
ContentElement
The ContentElement object provides access to the content panel of an M3 panel.
Properties
Children: any[]
List of the created data elements, e.g, [TextBoxElement, ButtonElement..]
ContentPanel: JQuery
The panel that contains the elements inside an M3 panel
Host: JQuery
The parent panel of an M3 panel
Functions
Add()
Adds an element to the content panel
The exact width and position of the element in pixels must be specified to properly add an element
using this method.
Parameters:
element: any – The HTML element to be added
Returns: void

Public APIs
Example:
let $list = $(“<div>”,{“class”:”inforDataGrid”});
let contentElement = this.controller.GetContentElement();
contentElement.Add($list);
AddElement()
Creates an HTML element based on the provided element data object and adds it to the content
panel
The element data can be an instance of the following: ButtonElement, CheckBoxElement,
ComboBoxElement, TextBoxElement, etc. This is an alternative to ContentElement.Add()
method.
Parameters:
elementData: any – The data object regarding the element to be created
Returns: any – An HTML element. The created and added element, null if no element is
created.
Example:
let buttonElement = new ButtonElement();
contentElement.AddElement(buttonElement);
CreateElement()
Creates an element based on the provided data
The element data can be an instance of the following: ButtonElement, CheckBoxElement,
ComboBoxElement, TextBoxElement, etc.
Parameters:
elementData: any – The data object regarding the element to be created
Returns: JQuery – The element based on the provided Object data, null if no element is
created.
Example:
let buttonElement = new ButtonElement();
contentElement.CreateElement(buttonElement);

Public APIs
GetContentBody()
Retrieves the contentBody element of the panel
Returns: JQuery – An HTML element; null if not found.
Example:
let contentBody = this.controller.GetContentBody();
GetElement()
Gets an element in an M3 panel
Parameters:
elementName: string – The name of the element to get
Returns: JQuery – An HTML element. The element corresponding to the provided element name,
null if no element is found.
Example:
let $field = contentElement.GetElement(“ITNO”);
GetPrevContainer()
Finds the immediate element container to the left of a given element container of a field
Element containers are those HTML elements with “elementContainer” class.
Parameters:
elementContainer: JQuery – The element container of a field, the one with
“elementContainer” class.
Returns: JQuery – An HTML element. The immediate element container to the left of the given
element container.
Example:
let $host = this.controller.ParentWindow;
let $firstLabel = $host.find(“.someLabelClass”).eq(0);
let $elem =
contentElement.GetPrevContainer($firstLabel.closest(“.elementContainer”));
OnUnload()
Provides a way to add callback method to execute when the content panel unloads its content
Parameters:

Public APIs
callback: function() – The function to execute when the content panel unloads.
Returns: void
Example:
let content = this.controller.GetContentElement();
content.OnUnload(function(){
//Code here
});
Unload()
Triggers the callback method(s) added using ContentElement.OnUnload()
This method does not remove the contents added to the content panel.
Returns: void
Example:
let content = this.controller.GetContentElement();
content.Unload();
MFormsAutomation
This is a helper class to create an automation XML and its equivalent URI, which can be used to
launch an M3 program in H5. The MForms Automation chapter discusses the feature in detail.
Functions
addStep()
Adds a step to the automation sequence.
Parameters:
action: string – The command for the automation step. The available values are: Run, Key,
ListOption, Set. Use the ActionType enum to specify the value.
parameter: string – The command value.
expected: string (optional) – The expected value.
Returns: void

Public APIs
Example:
cont auto = new MFormsAutomation();
auto.addStep(ActionType.Run, “MNS150”);
auto.addStep(ActionType.Key, “ENTER”);
addField()
Adds a field to the current step.
Parameters:
name: string – The name of the field.
value: string – The value for the field.
Returns: void
Example:
auto.addField(“W1USID”, ScriptUtil.GetUserContext(“USID”));
setFocus()
Adds a field that sets focus.
Parameters:
name: string – The name of the field.
Returns: void
Example:
auto.setFocus(“WWQTTP”);
toEncodedURI()
Converts the automation to a URI string.
Returns: string
Example:
auto.addStep(ActionType.Run, “MNS150”);
const uri = auto.toEncodedUri();

Public APIs
MIService
This is a helper class for calling M3 MI programs and reading the response. See the MIService
chapter for more information.
Functions
executeRequest()
Executes an MI transaction using the request object
Parameter:
request: MIRequest – Contains input and information about the request. It contains the
parameters for program, transaction, record or output fields. This is detailed in the MIService
chapter.
Returns: Promise – A promise that will resolve an MIResponse. If the promise is rejected, the
response will contain the error information.
Example:
const myRequest = new MIRequest();
MIService.Current.executeRequest(myRequest).then((response: IMIResponse)=>{
//Read results here
}).catch((response: IMIResponse)=>{
//Handle errors here
});
execute()
Executes an MI transaction
Parameter:
program: string – The program involved in the request.
transaction: string – The method to be used.
record: any (optional) – An object that contains records of the data involved.
outputfields: string array (optional) – Corresponding output fields.
timeout: number (optional) – How long would it take for the timeout.
Returns: Promise – A promise that will resolve an MIResponse. If the promise is rejected, the
response will contain the error information.
Example:

Public APIs
const program = “MNS150MI”;

const transaction = “GetUserData”;
const record = { USID: this.usid };
const outputFields = [“USID”, “CONO”, “DIVI”, “DTFM”];
MIService.Current.execute(program, transaction, record,

outputfields).then((response: IMIResponse)=>{
//Read results here
}).catch((response: IMIResponse)=>{
});
IonApiService (For MUA 10.4 only)

This is a helper class for calling ION API’s. See the ION API chapter for more information.
Functions
execute()
Executes an ION API request
Parameter:
request: IonApiRequest – Contains input and information about the request. It contains the
parameters for program, transaction, record or output fields. This is detailed in the ION API
chapter.
Returns: Promise – A promise that will resolve an IonApiResponse.
Example:
const request: IonApiRequest = {
url: `/M3/m3api-rest/execute/MNS150MI/GetUserData/`,
method: "GET",
record: {
USID: ScriptUtil.GetUserContext("USID")
}
}
IonApiService.Current.execute(request).then((response: IonApiResponse) => {
//Read response here
}).catch((response: IonApiResponse) => {
});

Public APIs
getBaseUrl()
Returns the ION API base URL
Returns: string
Example:
let baseUrl = IonApiService.Current.getBaseUrl();

Chapter 6 MForms Automation
6
What is MForms Automation?

MForms automation makes it possible to start M3 programs and perform single automated steps on
M3 UI Adapter (MUA) server before returning the result and control to the user. The steps in the
automation sequence can set values, press keys, execute lists options and set focus, etc.
Automation data can be sent to the MNE server as a small XML document that contains the
definition of the automation Automations can be started from both Infor Smart Office and Workplace.
The automation functionality has some limitations and is not a complete replacement for LWS/BCI
scripts. It can however be a more lightweight solution for many scenarios.
One important limitation is that the automation will only work if the program starts on the panel it was
defined for (A/B etc). If the user has set a different start panel for a program the automation will not
work, it will simply stop at the start panel.
Automation Sequences
An automation sequence consists of the exact same actions that a user would do when running an
M3 BE program. The user can basically enter data on a panel and make requests to the server by
using enter, function keys and list options. The automation sequence will contain one step for each
request and each step can set values on the panel.
Note that in some cases it might be necessary to first set values for sorting order and panel version
and pressing enter before assuming that specific fields are available.
A typical automation could be to start a program, select an item and open an E-panel in change
mode. The user would do the following steps to achieve that:
• Start the program (for example MMS001)
• Select sorting order. Changing sorting order in the UI will automatically trigger the ENTER key.
• Enter an item number in the first position field, change the panel sequence and press ENTER.
• Select the first row in the list and choose the change list option.
The E-panel is displayed.

MForms Automation
These user actions must be mapped to steps in the automation sequence. An automation sequence
can contain 1-n steps.
Automation Steps
Each automation step must have a command, a value and 0-n fields. The available commands and
values are listed in the table below.
Command Values Description
RUN M3 BE program name Starts an M3 BE program.The short

program name is used as value, for
example MMS001.
The RUN command cannot set field
values, fields will be ignored if they are
added to the RUN command.
KEY ENTER, F1-F24 Press a key. The next button is the
same as ENTER and the back button is
the same as F12.
LSTOPT 1-99, -1 Executes a list option. The default is to
set the option on the first visible list row,
unless selected rows are specified
using the SELROWS parameter. Note
that -1 must be used for option create, 1
is used for option select.
AUTOSET N/A This command can set field values but
do not make a request to the server.
The command can be used to enter
data on the last panel.
Automation Fields
Fields are used to enter data on a panel and for sending other special data such as focus. A field
has a name and a value.
You can locate the name of a field on an H5 panel in the field help window. To open the field help
window, set the focus on a control in the panel and press F1.

MForms Automation
Example
Field name = “WWITNO” Field value = “ITEM001”
• Focus
o It can be set on a specific field by using the special field name FCS.
o Example
▪ Field name = “FCS” Field value = “WWITNO”
• Selected List Rows
o When using the list option command the default is to select the first row in the list. It
is possible to select other list rows using the special field name SELROWS. The
value is a comma-separated list of row names. The name for a row is on the format
R<1-based list index>.
o Example
▪ Field name = “SELROWS” Field value = “R1,R2,R3”
Automation XML
An automation sequence is described in the form of a small XML document. The XML document can
be generated in runtime or created using XML templates.
Examples
• Empty automation XML
<?xml version=”1.0” encoding=”utf-8”?>
<sequence>
<step command=”” value=”” />
<step command=”” value=””>
<field name=””></field>
</step>
<step command=”” value=””>
</step>
</sequence>
• Automation XML with values

<?xml version=”1.0” encoding=”utf-8”?>
<sequence>
<step command=”RUN” value=”MMS001” />
<step command=”KEY” value=”ENTER”>

MForms Automation
<field name=”WWQTTP”>1</field>
</step>
<step command=”KEY” value=”ENTER”>
<field name=”W1ITNO”>TESTITEM</field>
<field name=”WWPSEQ”>E</field>
</step>
<step command=”LSTOPT” value=”2” />
</sequence>
Starting Automations in M3 H5
Automations can be started in M3 H5 using a URI with the host _automation and the automation
XML in the data parameter. The automation XML value should be URL encoded.
URI Format
mforms://_automation/?data=<AUTOMATION XML>
Example
mforms://_automation?data=%3c%3fxml+version%3d%221.0%22+encoding%3d%22utf-
8%22%3f%3e%3csequence%3e%3cstep+command%3d%22RUN%22+value%3d%22MMS001%22+%2f%
3e%3c%2fsequence%3e
Helper Class
There is a helper class that can be used to generate automation XML from code. From the
generated automation XML, it creates a URI to launch an M3 program in H5. See the API chapter
and an example of it for reference.

Chapter 7 MI Service
7
The M3 framework has support for calling M3 MI programs using the REST endpoint on the BE
server. The MIService is a helper class that can be used to call transactions to M3 MI programs. It
builds the request URL from the set of request parameters, executes the request, and parses the MI
response values.
Use the MIService.Current instance to avoid creating objects every time. See the API chapter
for the available functions, and the Sample scripts chapter for an example.
MIRequest
The executeRequest() accepts an MIRequest object with the following properties:
Properties Values Description
program M3 BE program name The BE program to be requested from.

Example: MNS150MI
transaction Transaction name Example: GetUserData
outputFields String array The names of the output fields to return
from a transaction.
Use this property to limit the amount of

data to transfer from the server. Only
specify the names of the fields that will
actually be used since that will approve
the performance.
Example: [“CONO”, “DIVI”]
record JSON The input data to the transaction. This
property is not required for transactions
without mandatory input fields.
Example: { USID: “myID” }

MI Service
includeMetadata true/false Indicates if metadata should be included

as part of the reply. Default is false.
typedOutput true/false Indicates if output should be converted
to numbers and dates according to the
meta data definition for the MI
transaction. This implicitly turns on
includeMetadata in the options to load
the meta data information. Default is
false.
maxReturnedRecords number Indicates the maximum number of
records to return. Default is 33.
timeout number Indicates the timeout value for the
HTTP request in milliseconds. Default is
55000.
Example
myRequest.program = "MNS150MI";
myRequest.transaction = "GetUserData";
myRequest.outputFields = ["CONO", "DIVI", "DTFM"];
myRequest.record = { USID: “USERFOO” };
myRequest.includeMetadata = true;
myRequest.typedOutput = true;
myRequest.maxReturnedRecords = 10;
myRequest.timeout = 60000;
MIService.Current.executeRequest(myRequest).then((response: IMIResponse) => {
//Success
}, (response: IMIResponse) => {
//Error
}
});
MIService builds this request into the following URL:
execute/MNS150MI/GetUserData;metadata=true;maxrecs=10;excludempty=false;cono=760;divi=AA
A;returncols=CONO,DIVI,DTFM?&USID=USERFOO?&_rid=YEBDH7IISB564BFJ

Chapter 8 Drillback
8
This chapter describes how to use standard Ming.le drillback links to launch M3 bookmarks in H5.
Invoking a drillback
Drill backs can be invoked by calling the Infor Ming.le JavaScript API to fire the drillback message. A
script is provided in the examples chapter.
infor.companyon.client.sendPrepareDrillbackMessage()
Returns: void
Example:
let myDrillback = “?LogicalId=lid://infor.m3.1&AccountingEntity=136_AAA…”;
infor.companyon.client.sendPrepareDrillbackMessage(myDrillback);
Drillback parameters
Name Description
LogicalId Used to determine which ERP to forward the drillback request to

Must start with lid://
AccountingEntity If blank or missing, CONO and DIVI must be part of ID1-ID7
ID1-ID7 Used to provide bookmark key values

Drillback
Name Description
ViewId Used to provide metadata about an M3 bookmark

Key-value-pairs separated by semi colon (;) and the key and value
separated by equals (=)
Keys are case-insensitive
Key Description
Program
TableName
Option
Panel
PanelSequence Optional
KeyNames The bookmark key names
Keys Consists of bookmark key names and
value keys separated by comma (,)
Has priority over KeyNames
CombinedElementSeparator Optional
The separator character for the
AccountingEntity parameter
The default value is underscore (_)
CombinedElementsAccountingEntity Optional
A comma separated list of key names
for the AccountingEntity parameter
The default value is CONO,DIVI
Examples
• Using KeyNames
o Company and division will be automatically retrieved from the AccountingEntity
parameter
o Additional bookmark keys are retrieved from ID1-ID7
?LogicalId=lid://infor.m3.1&AccountingEntity=136_AAA&ViewId=Program=CRS610
;TableName=OCUSMA;Option=5;Panel=E;KeyNames=OKCONO,OKCUNO&ID1=MANGO
• Using Keys
o The value key can be CONO, DIVI or ID1-ID7
o CONO is retrieved from the AccountingEntity

Drillback
?LogicalId=lid://infor.m3.1&AccountingEntity=136_AAA&ViewId=Progr
am=CRS610;TableName=OCUSMA;Option=5;Panel=E;Keys=OKCONO,CONO,OKCU
NO,ID1&ID1=MANGO
o CONO is specified using the ID1-parameter
?LogicalId=lid://infor.m3.1&AccountingEntity=136_AAA&ViewId=Progr
am=CRS610;TableName=OCUSMA;Option=5;Panel=E;Keys=OKCONO,ID1,OKCUN
O,ID2&ID1=136&ID2=MANGO
• Using CombinedElementsAccountingEntity
?LogicalId=lid://infor.m3.1&AccountingEntity=136_AAA&ViewId=CombinedElemen
tSeparator=_;CombinedElementsAccountingEntity=CONO,DIVI;Program=CRS610;Tab
leName=OCUSMA;Option=5;Panel=E;Keys=OKCONO,ID1,OKCUNO,ID2&ID1=136&ID2=MANG
O

Chapter 9 ION API (For MUA 10.4 only)
9
The ION API uses OAuth as authentication mechanism. OAuth essentially allows access tokens to
be issued to third-party clients by an authorization server, with the approval of the resource owner.
The client then uses the access token to access the protected resources hosted by the resource
server. The OAuth access token must be set as a request header. This means that all access to a
URL must be done in code to manually update the header before making the request.
Prerequisites
1 MUA version 10.4, due to Grid server restrictions for OAuth resource
2 Application API deployed in ION API server in that environment
3 Access to Ming.le and H5 in that environment
IonApiService
The IonApiService is a helper class for retrieving the OAuth token and consuming ION APIs from
H5 scripts. Use the IonApiService.Current instance to avoid creating objects every time. See
the API chapter for the available functions.
OAuth access token

The IonApiService handles the retrieval of the token and updates the request authorization
header before executing the ION API requests. When the token timeouts and an API call returns a
401 Unauthorized error, it requests for a new token and retries the API call once with this newly
acquired token.

ION API (For MUA 10.4 only)
IonApiRequest
The execute() function accepts and IonApiRequest object with the following properties:
url Request URL If relative, ION API base URL will be

prepended
If absolute, will be executed as it is
method HTTP method
Default: GET
responseType (optional) Depends on API; Default: JSON
usually JSON or XML
record (optional) JSON The input data. This property is not required
for APIs without mandatory input fields.
On execution, values will be parsed and
appended to request URL
data (optional) Depends on API Data to be sent
cache (optional) true/false Default: false
headers(optional) Array of key-value pairs Authorization header will always be added
first, followed by these headers
IonApiResponse
The execute() function resolves an IonApiResponse object with the following properties:
data Response data Depends on API

status (optional)
statusText
message (optional)

ION API (For MUA 10.4 only)
Development environment
The H5SampleIonApiService script shows how to connect to the Ming.le and M3 APIs. If the
script is uploaded thru Admin Tools, skip the following steps and it should run as intended
provided that the ION API prerequisites are satisfied. The following steps are a workaround
when working on a development environment with no access to an authorization server, like
localhost.
Acquire an OAuth token string

1 Log on to Ming.le
2 Locate the server that H5 is running on within Ming.le. You will need to check the server and port
for H5 and apply it to the template below:
o Open the browser developer tools (how depends on browser)
o Use the element inspector and click the top bar in H5. Look for an iframe element
with a context root called /mne
3 Open a new tab in the same browser and navigate to the Grid SAML Session Provider OAuth
resource
Template: https://{h5server}:{h5port}/grid/rest/security/sessions/oauth
4 Copy the OAuth token string from the browser window
Set the token as a script argument

Set the copied token as an argument when adding the script in the Tools > Personalize > Scripts
dialog.
When this OAuth token times out, you must acquire a new token and update the script argument.

Chapter 10 Best practices
10
This chapter provides suggestions to improve the quality and maintainability of your scripts.
Use H5 functions and properties that are

documented
Although there are many accessible functions, it is recommended to use those that are listed in the
public API. This ensures that the scripts will not break when H5 is updated.
Use recommended API functions

Here are some of the more commonly-used functionalities:
1 InstanceController.ParentWindow
Use this property to get the current panel, instead of using CSS class selectors, i.e.,
$(".lawsonHost:visible") and $(".visible-tab-host").
2 ContentElement.AddElement()
Consider using this function to add elements and easily align them in the panel row, as opposed
to ContentElement.Add() which requires the exact position in pixels and ControlFactory
which is not part of the public API.
3 MIService
Use this utility for M3 API requests, instead of the now deprecated
ScriptUtil.ApiRequest().

Best practices
Use proper logging utility

The problem with logging using console.log()is that you have no way to turn it off. Use the log
object from the script arguments and use the log levels provided.
Use TypeScript
TypeScript allows writing safer code. Although optional, it is best to include the data type,
avoiding any as much as possible, when declaring a variable to take advantage of its type-checking.
It also allows usage of some ES6 features by transpiling them to ES5-compliant code. It is
recommended to utilize these features such as:
1 const and let
These allow definition of block-scoped variables, as opposed to the function-scoped var
declarations. Use these instead of var whenever possible. Use const to make a variable
immutable.
2 for…of and for…in
These constructs eliminate potential index bugs in the for loop. Note that for…of iterates over
the elements of an array, while for…in iterates over the keys of an object.
3 Arrow functions (=>)
The fat arrow captures this from the surrounding context as opposed to an ordinary function
that tends to lose the meaning of this when it is passed around. It is recommended to use this
in callback functions.
Be wary of using ES6/ES2016 features

As of this writing, some browsers, like Internet Explorer, do not fully support ES6/ES2016 features.
Verify that the functions and properties you use are supported in the browsers that you target your
scripts to run in. Note that the TypeScript compiler can convert some, not all, code to be ES5-
compliant.
Minify scripts
Consider minifying large scripts to improve load time. More information on minification in the
Overview chapter.

Chapter 11 Script examples
11
This chapter contains examples of scripts written in TypeScript. The scripts are complete and can be
copied from this document to a new TypeScript file. The transpiled JavaScript file can then be
deployed to M3 H5.
H5SampleHelloWorld.ts
This script shows a message dialog information about the connected element and script arguments.
class H5SampleHelloWorld {
/**
* Script initialization function.
*/
let message: string;
const element = args.elem;

if (element) {
message = "Connected element: " + element.Name;
} else {
message = "No element connected.";
}
const argumentString = args.args;

if (argumentString != null) {
message = message + " Arguments: " + argumentString;
} else {
message = message + " No arguments.";
}
// Show an information message dialog.

ConfirmDialog.Show({
header: "H5SampleHelloWorld",
message: message,
dialogType: "Information"

Script examples
});
}
}
H5SampleUserDetails.ts
This script adds a custom ButtonElement on the panel. When the button is clicked, a message
dialog shows M3-related data about the logged on user.
class H5SampleUserDetails {
private controller: IInstanceController;
private log: IScriptLog;
private args: string;
constructor(scriptArgs: IScriptArgs) {
this.controller = scriptArgs.controller;
this.log = scriptArgs.log;
this.args = scriptArgs.args;
}
/**
*/
new H5SampleUserDetails(args).run();
}
private run(): void {

this.addButton();
}
private addButton(): void {

buttonElement.Name = "showUserDetails";
buttonElement.Value = "Show User Details";
const contentElement = this.controller.GetContentElement();

const button = contentElement.AddElement(buttonElement);
button.click(() => {
this.showDetails();

Script examples
});
}
private showDetails(): void {

const userContext = ScriptUtil.GetUserContext();
const header = "USER DETAILS";
const message = [];
for (let key in userContext) {

message.push(key + ": " + userContext[key]);
}
const opts = {
dialogType: "Information",
header: header,
message: message.join("<br/>"),
id: "msgDetails",
withCancelButton: true,
isCancelDefault: false
}
ConfirmDialog.ShowMessageDialog(opts);
}
}
H5SampleShowXml.ts
This example displays the raw XML content of an MForm from the View Definitions file. The script
retrieves the XML file, and converts text symbols to HTML codes to properly display the text symbols
in a Message Dialog.
class H5SampleShowXml{
private static charMap = {
'<': '<',
'>': '>',
'&': '&',
'"': '"',
"'": ''',
'!': '!',
'[': '[',
']': ']'
};

Script examples
constructor(args: IScriptArgs) {
this.controller = args.controller;
this.log = args.log;
this.args = args.args;
}

new H5SampleShowXml(args).run();
}

const xml = this.controller.Response.RawContent;
const strXml = (new XMLSerializer()).serializeToString(xml);
const finalStr = this.escapeChar(strXml);
dialogType: "Information",
header: "XML Response",
message: finalStr
});
}
private escapeChar(xml: string): string {

return xml.replace(/[<>&"'!]/g, (ch) => {
return H5SampleShowXml.charMap[ch];
});
}
}
H5SampleAddElements.ts
This script show how to add label, textbox, combobox, checkbox, and button elements to a panel.
On button click, it toggles the checkbox and prints the textbox and combobox values on the console.
class H5SampleAddElements {
private contentElement: IContentElement;

Script examples

new H5SampleAddElements(args).run();
}

this.contentElement = this.controller.GetContentElement();
this.addLabel();
this.addTextBox();
this.addComboBox();
this.addCheckbox();
this.addButton();
}
private addLabel(): void {

const labelElement = new LabelElement();
labelElement.Name = "testLabel";
labelElement.Value = "Test Elements";
labelElement.Position = new PositionElement();
labelElement.Position.Top = 4;
labelElement.Position.Left = 6;
this.contentElement.AddElement(labelElement);
}
private addTextBox(): void {

const textElement = new TextBoxElement();
textElement.Name = "testTextBox";
textElement.Value = "Test";
textElement.Position = new PositionElement();
textElement.Position.Top = 4;
textElement.Position.Left = 14;
textElement.Position.Width = 5;
this.contentElement.AddElement(textElement);
}
private addComboBox(): void {

const items = [
{ key: '1', value: 'One', selected: true },
{ key: '2', value: 'Two', selected: false },
{ key: '3', value: 'Three', selected: false },
{ key: '4', value: 'Four', selected: false },
{ key: '5', value: 'Five', selected: false },
];

Script examples
const comboBox = new ComboBoxElement();

comboBox.Name = "testComboBox";
comboBox.Position = new PositionElement();
comboBox.Position.Top = 4;
comboBox.Position.Left = 18;
comboBox.Position.Width = 8;
for(let item of items) {

const cboxItem = new ComboBoxItemElement();
cboxItem.Value = item.key;
cboxItem.Text = item.value;
if(item.selected) {
cboxItem.IsSelected = true;
}
comboBox.Items.push(cboxItem);
}
this.contentElement.AddElement(comboBox);
}
private addCheckbox(): void {

const cbElement = new CheckBoxElement();
cbElement.Name = "testCheckBox";
cbElement.Position = new PositionElement();
cbElement.Position.Top = 4;
cbElement.Position.Left = 26;
cbElement.IsChecked = false;
this.contentElement.AddElement(cbElement);
}

buttonElement.Name = "testButton";
buttonElement.Value = "Print and Toggle";
const $button = this.contentElement.AddElement(buttonElement);

$button.click({}, () => {
const $textBox = $("#testTextBox");
const $selected = $("#testComboBox").find('option:selected');
const $cbox = $('#testCheckBox');
this.log.Info(`Text value: ${$textBox.val()}`);

Script examples
this.log.Info(`Selected option: ${$selected.val()}

(${$selected.text()})`);
$cbox.toggleChecked();
});
}
}
H5SampleOptionButton.ts
Adds one or more option buttons that executes a list option when clicked.
class H5SampleOptionButton {
private buttons: IButtonInfo[];
}
private parseArgs(args: string): boolean {

try {
// The argument string should be either an array of IButtonInfo
or a single IButtonInfo object on JSON format.
const json: any = JSON.parse(args);
let buttons: IButtonInfo[];
if (json.length > 0) {
// Assume it's an array of buttons
buttons = json;
} else {
// Assume it's a single buttons object
buttons = [json];
}
// Validate that all mandatory properties are set.

for (let button of buttons) {
if (!button.text || !button.option) {
this.log.Error("Invalid argument string " + args);
return false;
}
}

Script examples
this.buttons = buttons;
} catch (ex) {
this.log.Error("Failed to parse argument string " + args, ex);
return false;
}
return true;
}
private addButton(buttonInfo: IButtonInfo): void {

buttonElement.Value = buttonInfo.text;
const button = ControlFactory.CreateButton(buttonElement);

button.click({}, () => {
this.controller.ListOption(buttonInfo.option);
});
button.Position = {
Width: buttonInfo.width || "100",
Top: buttonInfo.top || "0",
Left: buttonInfo.left || "0"
};

contentElement.Add(button);
}
public run(): void {

// Parse the script argument string and return if the arguments are
invalid.
if (!this.parseArgs(this.args)) {
return;
}
this.log.Info("Running...");
// Add the option buttons to the panel.

for (let button of this.buttons) {
this.addButton(button);
}
}
/**
*/
new H5SampleOptionButton(args).run();

Script examples
}
}
H5SamplePreviewListHeader.ts
This example is a program-specific script loaded from the MNEAI element of an H5 panel. This script
searches for two specific elements that contain the headers and the row content to be displayed in a
table. When this script is loaded in CRS020/F, a table with one row of data is displayed.
class H5SamplePreviewListHeader {
}
/**
*/
new H5SamplePreviewListHeader(args).run();
}

//Check panel
if (this.controller.GetPanelName() !== "CRA020F0") {
this.log.Error("Script should run in CRS020/F.");
return;
}
this.buildGrid();
}
private buildGrid(): void {

let options, grid;
const content = this.controller.GetContentElement();
const header = this.getHeader();
const columns = this.getColumns(header);
const data = this.getData(columns);
const $list: IList = $("<div>", {

Script examples
"class": "inforDataGrid",
"id": "crs020FGrid",
"width": "auto",
"height": "500px"
});
$list.Position = new PositionElement();
$list.Position.Width = "97%";
$list.Position.Top = "250";
$list.Position.Left = "10";
content.Add($list);
options = Configuration.Current.ListConfig('id', columns, data);

options["forceFitColumns"] = true;
options["autoHeight"] = true;
grid = $("#crs020FGrid").inforDataGrid(options);
grid.render();
}
private getHeader(): string[] {

const wwsfhl = this.controller.GetElement("WWSFHL");
//Split on capital letters
return wwsfhl[0].textContent.split(/(?=[A-Z])/);
}
private getColumns(headers: string[]): any[] {

const columns = [];
for (let header of headers) {
let column = {
id: "C" + (columns.length + 1),
name: header,
field: header
};
columns.push(column);
}
return columns;
}
private getData(columns: any[]): any[] {

const rows = [];
const wwsfll = this.controller.GetElement("WWSFLL");
const data = wwsfll[0].value.split(" ");
const row = { id: "R1" };
for (let i = 0; i < columns.length; i++) {

row[columns[i]["field"]] = data[i];
}

Script examples
rows.push(row);
return rows;
}
}
H5SampleShowOnMap.ts
This is a program-specific script for OIS002/F. It adds a custom button element in the panel that
opens a location in Google Maps depending on the latitude, longitude, and zoom values specified in
the text fields.
class H5SampleShowOnMap {
private $host: JQuery;
}
/**
*/
new H5SampleShowOnMap(args).run();
}

this.$host = this.controller.ParentWindow;
this.addButton();
}

buttonElement.Name = "showMap";
buttonElement.Value = "Show Map";

const button = contentElement.CreateElement(buttonElement);
const geoX = ScriptUtil.FindChild(this.$host, "WFGEOX");

Script examples
button.attr("style", "margin-left: 5px");

geoX.after(button);
button.click(() => {
this.showMap();
});
}
private showMap(): void {

const lat = ScriptUtil.GetFieldValue("WFGEOX", this.controller);
const lng = ScriptUtil.GetFieldValue("WFGEOY", this.controller);
const zoom = ScriptUtil.GetFieldValue("WFGEOZ", this.controller);
if (!(lat && lng)) {

this.log.Info("Coordinates required.");
return;
}
let x = lat.replace(",", ".");

let y = lng.replace(",", ".");
let z = zoom ? zoom : 15;
if (x.indexOf("-") > -1) {

x = x.replace("-", "");
x = "-" + x;
}
if (y.indexOf("-") > -1) {

y = y.replace("-", "");
y = "-" + y;
}
const url = "https://maps.google.com/maps?z=" + z + "&t=m&q=loc:" + x

+ "+" + y + "&output=embed";
ScriptUtil.Launch(url);
}
}
H5SampleMFormsAutomation.ts
This example retrieves the user ID from the user context, creates an automation that starts MNS150,
and opens the user in change mode.
class H5SampleMFormsAutomation {

Script examples

}
/**
*/
new H5SampleMFormsAutomation(args).run();
}

if (this.controller.GetProgramName() === "MNS150") {
this.log.Error("Adding this script will cause an infinite loop.
Try adding it to a different program.");
return;
}
this.addButton();
}

const run = new ButtonElement();
run.Name = "run";
run.Value = "Run Automation";
run.Position = new PositionElement();
run.Position.Top = 3;
run.Position.Left = 1;
run.Position.Width = 5;

const $run = contentElement.AddElement(run);
$run.click({}, () => {
const auto = new MFormsAutomation();
auto.addStep(ActionType.Run, "MNS150");
auto.addStep(ActionType.Key, "ENTER");
auto.addField("W1USID", ScriptUtil.GetUserContext("USID"));
auto.addStep(ActionType.ListOption, "2");
const uri = auto.toEncodedUri();

ScriptUtil.Launch(uri);
});
}

Script examples
H5SampleRegexValidator.ts
This script validates the content of the configured fields on a panel and shows a validation message
for the first validation that fails. Validation runs on Enter or Next, and on failure, the request will be
cancelled and the user will not be able to continue until the validation errors have been addressed.
/**
* Configuration example:
* Validate that the WRYREF field is not blank on the CRS610/E panel.
* Note that the backslash character has been escaped with an additional
backslash character.
*
* { "names": ["WRYREF"], "regex": "^$|\\s+", "message": "Your ref 1 may not
be blank" }
*/
class H5SampleRegexValidator {
private scriptName = "H5SampleRegexValidator";

private detachRequesting: Function;
private detachRequested: Function;
private validations: IValidationInfo[];
}
private parseArgs(args: string): boolean {

try {
// The argument string should be either an array of
IValidationInfo or a single IValidationInfo object on JSON format.
const json: any = JSON.parse(args);
let validations: IValidationInfo[];
if (json.length > 0) {
// Assume it's an array of validations
validations = json;
} else {
// Assume it's a single validation object
validations = [json];

Script examples
// Validate that all mandatory properties are set.

for (let validation of validations) {
if (!validation.regex || !validation.message ||
!validation.names) {
this.log.Error("Invalid argument string " + args);
return false;
}
}
this.validations = validations;
} catch (ex) {
this.log.Error("Failed to parse argument string " + args, ex);
return false;
}
return true;
}
private validateFields(): boolean {

try {
for (var validation of this.validations) {
const regExp = new RegExp(validation.regex);
for (var name of validation.names) {
const value = this.controller.GetValue(name);
if (value === null || value === undefined) {
// Skip fields that does not exist on the current
panel.
this.log.Debug("The field " + name + " does not
exist on the panel.");
continue;
}
if (regExp.test(value)) {
this.controller.ShowMessage(validation.message);
return false;
}
}
}
return true;
} catch (ex) {
this.log.Error("Failed to validate fields", ex);
// Return true if the script crashes to avoid getting stuck on

a panel.
return true;
}
}

Script examples
private logEvent(eventName: string, args: RequestEventArgs): void {

this.log.Info("Event: " + eventName + " Command type: " +
args.commandType + " Command value: " + args.commandValue);
}
private detachEvents(): void {

this.detachRequesting();
this.detachRequested();
}
private attachEvents(controller: IInstanceController): void {

this.detachRequesting = controller.Requesting.On((e) => {
this.onRequesting(e);
});
this.detachRequested = controller.Requested.On((e) => {
this.onRequested(e);
});
}
private onRequesting(args: CancelRequestEventArgs): void {

// Only validate for the enter key (next button).
if (args.commandType === "KEY" && args.commandValue === "ENTER") {
if (!this.validateFields()) {
args.cancel = true;
}
}
}
private onRequested(args: RequestEventArgs): void {

this.detachEvents();
}

if (!this.parseArgs(this.args)) {
return;
}
// Attach events.
this.attachEvents(this.controller);
}
/**
*/
new H5SampleRegexValidator(args).run();

Script examples
}
}
H5SampleRequestTracer.ts
This script logs the command type and command value for the Requesting, Requested and
RequestCompleted events on a panel. It uses the InstanceCache to ensure that the script is
attached only once for a program instance.
class H5SampleRequestTracer {
private scriptName = "H5SampleRequestTracer";

}
private logEvent(eventName: string, args: RequestEventArgs): void {

this.log.Info("Event: " + eventName + " Command type: " +
args.commandType + " Command value: " + args.commandValue);
}
private attachEvents(controller: IInstanceController): void {

controller.Requesting.On((e) => {
});
controller.Requested.On((e) => {
});
controller.RequestCompleted.On((e) => {
this.onRequestCompleted(e);
});
}

this.logEvent("Requesting", args);
}

this.logEvent("Requested", args);
}

Script examples
private onRequestCompleted(args: RequestEventArgs): void {

this.logEvent("RequestCompleted", args);
}

const controller = this.controller;
const key = this.scriptName;
const cache = InstanceCache;
// Check the instace cache to see if this script has already

attached to this program instance.
if (cache.ContainsKey(controller, key)) {
// The script is already attached to this instance.
return;
}
// Add a key to the instance cache to prevent other instances of

this script on the same program instance.
cache.Add(controller, key, true);
// Attach events.
this.attachEvents(controller);
}
/**
*/
new H5SampleRequestTracer(args).run();
}
}
H5SampleCancelRequest.ts
This example shows how to cancel a server request and is built for the E-panel in POS015. The
script subscribes to the Requesting event and when that event is raised it checks the name of the
project leader. If the name is invalid, it cancels the request and shows an error message.
class H5SampleCancelRequest {
private unsubscribeRequesting;
private unsubscribeRequested;

Script examples
}
/**
*/
new H5SampleCancelRequest(args).run();
}

this.unsubscribeRequesting = this.controller.Requesting.On((e) => {
});
this.unsubscribeRequested = this.controller.Requested.On((e) => {
});
}

this.log.Info("onRequesting");
if (args.commandType === "KEY" && args.commandValue === "F12") {
return; // The user should be allowed to go back
}
const $host = this.controller.ParentWindow;

const fullName = ScriptUtil.GetFieldValue("WWTX40");
if (fullName && fullName.indexOf("Infor") >= 0) {

this.controller.ShowMessage(fullName + " is not a valid project
leader.");
args.cancel = true;
}
}

this.log.Info("onRequested");
this.unsubscribeRequested();
this.unsubscribeRequesting();
}
}

Script examples
H5SampleOpenFieldHelp.ts
This example displays through a dialog box the field help of the corresponding element argument
attached to it. The script adds a click event to the attached element which opens the field help of the
element based on the argument supplied. When there is no argument, the script will use the element
name where it is attached.
class H5SampleOpenFieldHelp {
const element = args.elem;
const controller = args.controller;
const fieldHelp = args.args;
const response = controller.Response;
const $host = controller.ParentWindow;
if (element) {
let $elem = ScriptUtil.FindChild($host, element.Name);
if ($elem.length > 0) {
ScriptUtil.AddEventHandler($elem, "click", (event) => {
const helpElement = $("#" + (fieldHelp || element.Name));
controller.RenderEngine.OpenFieldHelp(response, $host,
controller, helpElement);
});
}
}
else {
dialogType: "Error",
header: "H5 Sample Field Help Button",
message: "No element connected"
});
}
}
}
H5SampleCustomColumns.ts
This script adds a column to the grid and populates the new column with dummy data.
class H5SampleCustomColumns {
private unsubscribeReqCompleted;

Script examples
/**
*/
new H5SampleCustomColumns(args).run();
}

const list = this.controller.GetGrid();
const customColumnNum = list.getColumns().length + 1;
this.appendColumn(list, customColumnNum);
this.populateData(list, customColumnNum);
this.attachEvents(this.controller, list, customColumnNum);
}
private appendColumn(list: IActiveGrid, columnNum: number) {

const columnId = "C" + columnNum;
let columns = list.getColumns();

let newColumn = {
id: columnId,
field: columnId,
name: "Custom Column " + columnNum,
width: 100
}
if (columns.length < columnNum) {
columns.push(newColumn);
}
list.setColumns(columns);
}
private populateData(list: IActiveGrid, columnNum: number) {

const columnId = "C" + columnNum;
for (let i = 0; i < list.getData().getLength(); i++) {
let newData = {};
newData[columnId] = "Dummy Data" + i;
newData["id_" + columnId] = "R" + (i + 1) + columnId;
$.extend(list.getData().getItem(i), newData);
}
let columns = list.getColumns();
list.setColumns(columns);
}
private attachEvents(controller: IInstanceController, list: IActiveGrid,

columnNum: number) {

Script examples
this.unsubscribeReqCompleted = controller.RequestCompleted.On((e) =>

{
//Populate additional data on scroll
if (e.commandType === "PAGE" && e.commandValue === "DOWN") {
this.populateData(list, columnNum);
} else {
this.detachEvents();
}
});
}
private detachEvents() {
this.unsubscribeReqCompleted();
}
}
H5SampleMIService.ts
This script executes M3 API calls to retrieve user data using the MIService utility.
Caution:
Some minifiers report an error on the occurrence of Promise.catch as catch is a reserved word. To
work around this, you can pass the catch function as the second parameter to the then function
instead.
class H5SampleMIService {
private usid: string;
}
/**
*/
new H5SampleMIService(args).run();
}

Script examples

this.usid = ScriptUtil.GetUserContext("USID");
this.addButton();
}

run.Name = "run";
run.Value = "Execute MI calls";

$run.click({}, () => {
this.executeByRequest();
this.executeByTransaction();
this.executeWithOptionalArgs();
this.executeMultiple();
});
}
private executeByRequest(): void {

//Fields that should be returned by the transaction
myRequest.outputFields = ["CONO", "DIVI", "DTFM"];
//Input to the transaction
myRequest.record = { USID: this.usid };
MIService.Current.executeRequest(myRequest).then(
(response: IMIResponse) => {
//Read results here
for (let item of response.items) {
this.log.Info(`1: Company: ${item.CONO}`);
}
}).catch((response: IMIResponse) => {
this.log.Error(response.errorMessage);
});
}
private executeByTransaction(): void {

const program = "MNS150MI";
const transaction = "GetUserData";

Script examples
const record = { USID: this.usid };

const outputFields = ["USID", "CONO", "DIVI", "DTFM"];
MIService.Current.execute(program, transaction, record,

outputFields).then(
//Read results here
for (let item of response.items) {
this.log.Info(`2: Division: ${item.DIVI}`);
}
});
}
private executeWithOptionalArgs(): void {

myRequest.includeMetadata = true;
//Convert data to number and date as defined in the metadata; default
is false
myRequest.typedOutput = true;
//Default is 33
myRequest.maxReturnedRecords = 10;
//Default is 55000
myRequest.timeout = 60000;
MIService.Current.executeRequest(myRequest).then(
//Since CONO is numeric based on the metadata, this will read
"999 is a number"
//If request.typedOutput = false, everything will be a string
and this will read "999 is a string"
this.log.Info(`3: ${response.item.CONO} is a ${typeof
response.item.CONO}`);
//Read metadata
const metadata = response.metadata;
for (let field in metadata) {
let info: IMIMetadataInfo = metadata[field];
this.log.Info(`3: ${field}: ${info.description}
(${MIDataType[info.type]})`);
}
}, (response: IMIResponse) => {
//Alternatively, pass a second function to then instead of
using catch

Script examples
});
}
private executeMultiple(): void {

const myRequest1 = new MIRequest();
myRequest1.program = "MNS150MI";
myRequest1.transaction = "GetUserData";
myRequest1.outputFields = ["CONO", "DIVI", "DTFM"];
//Input to the transaction
myRequest1.record = { USID: this.usid };
const myRequest2 = new MIRequest();

myRequest2.program = "MNS150MI";
myRequest2.transaction = "LstUserData";
myRequest2.outputFields = ["USID", "TX40", "USTP"];
myRequest2.maxReturnedRecords = 5;
const myPromise1 = MIService.Current.executeRequest(myRequest1);

const myPromise2 = MIService.Current.executeRequest(myRequest2);
Promise.all([myPromise1, myPromise2]).then(
response => {
//Read results here
const response1 = response[0];
const response2 = response[1];
for (let item of response1["items"]) {
this.log.Info(`4: DTFM: ${item.DTFM}`);
}
for (let item of response2["items"]) {
this.log.Info(`4: USID: ${item.USID}`);
}
});
}
}
H5SampleImageFromList.ts
This script shows an image when a list row is selected, it gets the text in the first column to build a
URL to an image. The image is loaded and displayed next to the list. The base URL to the images

Script examples
are retrieved from the script arguments. For the script to work properly, there must be images in the
folder of the URL whose names (not including the file extension) match the values of the first column
in the list.
class H5SampleImageFromList {
private imgLink = "";

private content: IContentElement;
this.imgLink = scriptArgs.args;
this.content = this.controller.GetContentElement();
}

new H5SampleImageFromList(args).run();
}

if (!this.imgLink) {
dialogType: "Error",
header: "No Argument",
message: "Please provide url of the location of the images.
Example: http://server/images/"
});
return;
}
//Add eventhandlers
const list = this.controller.GetGrid();
const handler = (e, args) => { this.onSelectionChanged(e, args); };
list.onSelectedRowsChanged.subscribe(handler);
}
private addImage(src: string): void {

const contentBody = this.content.GetContentBody();
const height = contentBody.height();
const width = contentBody.width()/2 - 20;
const style = `z-index:2000;
display: block;
max-width:${width}px;
overflow: hidden;
position:absolute;
left:50%;
max-height:${height}px;

Script examples
top:0px;`;
const $image = $(`<div id='newImg' style='${style}'><img
style='width:100%;' src='${src}'></img></div>`);
contentBody.append($image);
}
private updateImage(src: string): void {

const newImg = this.content.GetContentBody().find("#newImg");
if (newImg) {
newImg.remove();
}
this.addImage(src);
}
private onSelectionChanged(e: any, args: any): void {

const grid = args.grid;
const selected = grid.getSelectedRows();
if (selected.length < 1) {
// No row was selected
return;
}
// Get the index of the first selected row

const rowIndex = selected[0];
// Get item number of selected row

const imageName = ListControl.ListView.GetValueByColumnIndex(0);
//Show Image
this.updateImage(this.imgLink + imageName + ".jpg");
}
}
H5SampleDrillback.ts
This script takes a customer ID from the script arguments and launches CRS610/E for this customer
using a standard Ming.le drillback URL. The drillback is invoked using the Infor Ming.le CE
JavaScript API.
class H5SampleDrillback {

Script examples
private content: IContentElement;

private customer: string;
this.customer = scriptArgs.args;
}
/**
*/
new H5SampleDrillback(args).run();
}

if (!this.customer) {
this.log.Error("Enter a customer ID in the script arguments.");
return;
}
this.content = this.controller.GetContentElement();
this.addButton();
}
private invokeDrillback() {
const userContext = ScriptUtil.GetUserContext();
const acctEntity =
`${userContext.CurrentCompany}_${userContext.CurrentDivision}`;
const viewId =
`Program=CRS610;TableName=OCUSMA;Option=5;Panel=E;KeyNames=OKCONO,OKCUNO`;
const drillback =
`?LogicalId=lid://infor.m3.1&AccountingEntity=${acctEntity}&ViewId=${encodeUR
IComponent(viewId)}&ID1=${this.customer}`;
//Fire the drillback message using the Infor Ming.le CE JavaScript

API
infor.companyon.client.sendPrepareDrillbackMessage(drillback);
}

run.Name = "run";
run.Value = "Invoke Drillback";

Script examples
const $run = this.content.AddElement(run);

$run.click(() => {
this.invokeDrillback();
});
}
}
H5SampleIonApiService.ts
This script retrieves the user GUID and email from the Mingle and M3 ION APIs. You may need to
set the OAuth token manually to run the script in your development environment. Please see the
ION API chapter for more details.
/**
* Executes requests to Ming.le and M3 ION APIs.
* For MUA 10.4 only.
*
* No setup needed if script will be uploaded thru Admin Tools
* During development, to run this script in any instance where an
authorization server is not available,
* you will need to set the OAuth token manually:
* - Acquire an OAuth token string.
* + Log on to Ming.le.
* + Open a new tab in the same browser and navigate to the Grid SAML
Session Provider OAuth resource.
* + The Grid must be version 2.0 or later with a SAML Session Provider
configured for the same IFS as Ming.le.
Example:
https://yourservernameandport/grid/rest/security/sessions/oauth
* - Copy the token to the script arguments.
* - When the token times out, you must acquire a new token and update the
script arguments.
*/
class H5SampleIonApiService {
private args: any;
private readonly mingleEndpoint = "Mingle";

private readonly m3Endpoint = "M3/m3api-rest/execute";

Script examples
this.args = args.args;
}
/**
*/
new H5SampleIonApiService(args).run();
}

this.addMingleButton();
this.addM3Button();
/* For development purposes only

Make sure to add a valid access token as the script argument.
See comments above or the development guide for details.
*/
// IonApiService.Current.setToken(this.args);
}
private addMingleButton(): void {

run.Name = "run";
run.Value = "Get user GUID";

$run.click(() => {
url:
`${IonApiService.Current.getBaseUrl()}/${this.mingleEndpoint}/SocialService.S
vc/User/Detail`,
method: "GET"
}
IonApiService.Current.execute(request).then((response:
IonApiResponse) => {
if(!response.data.ErrorList) {
this.controller.ShowMessage(response.data["UserDetailList"][0].UserGUID);
}
else {

Script examples
for(const error of response.data.ErrorList) {

this.log.Error(error.Message);
}
}
this.log.Error(response.message);
});
});
}
private addM3Button() {
run.Name = "run";
run.Value = "Get M3 user email";

$run.click(() => {
url: `/${this.m3Endpoint}/MNS150MI/GetUserData/`,
method: "GET",
record: {
USID: ScriptUtil.GetUserContext("USID")
}
}
IonApiService.Current.execute(request).then((response:
IonApiResponse) => {
const responseData = MIService.Current.parseResponse({},
response.data);
if(responseData.item) {
this.controller.ShowMessage(responseData.item.EMAL);
}
if(responseData.errorMessage) {
this.controller.ShowMessage(responseData.errorMessage);
}
this.log.Error(response.message);
});
});
}
}

Chapter 12 Appendix
12
Node.js
Node.js should be installed to be able to use the web server included in the SDK samples in
developing scripts. You can skip this section if you have a working Node.js installation or if you do
not want to use the web server.
Install Node.js
Download and install Node.js from http://nodejs.org/
When the installation is complete you can follow the steps in the next two sections to verify that
installations works. Note that the instructions are for Microsoft Windows operating systems only.
Refer to the Node.js documentation for other operating systems.
Verify the Node package manager

Follow these steps to verify that the Node package manager works.
1 Verify that the following folder exists and create it manually if not.
• C:\Users\<userid>\AppData\Roaming\npm
• You need to show Hidden items in Windows Explorer to be able to see the AppData folder.
2 Open a Windows Command Prompt window.
3 Run the following command.
• npm -version
4 Verify that a version number is printed, such as 2.15.8.
• If the command fails, verify that the npm directory has been created. See previous step, and
create it if necessary.
• When the directory has been created, retry the “npm –version” command.

Appendix
• On some operating systems, the command might complete even if the npm folder is missing.
In these cases, the installation of the node packages will fail. This can be solved by manually
creating the npm folder.
• On some operating systems, you might have to restart the computer after adding the npm
folder.
Verify the Node executable

Follow these steps to verify that Node executable works.
2 Run the following command.
• node -v
3 Verify that a version number is printed, such as v4.4.7.
• If the command fails, it could be that the node directory is not on the Windows path.
• Add the following directory to the Windows System Path.
o C:\Program Files\nodejs
• Close the command Window, start a new one and test node –v again.
o The command should succeed this time.
• To apply the new Windows path, the computer might have to be restarted.
TypeScript
Follow these steps to install the TypeScript compiler. If you choose to use Visual Studio, you can
skip this part as the IDE already includes a compiler plugin.
2 Run the following command:
• npm install -g typescript@2.2
3 Verify installation. A version number should be printed when you run the following command:
• npm typescript -version

Infor M3 H5 Development Guide: Version 10.3.1, 10.4.0 Published January 2018

Uploaded by

Copyright:

Available Formats

Infor M3 H5 Development Guide: Version 10.3.1, 10.4.0 Published January 2018

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Infor M3 H5 Development Guide: Version 10.3.1, 10.4.0 Published January 2018

Uploaded by

Copyright:

Available Formats

Infor M3 H5 Development Guide

Version 10.3.1, 10.4.0

About this guide ................................................................................................................................. 11

Chapter 1 Introduction .................................................................................................................. 13

Chapter 2 Developing scripts ....................................................................................................... 17

Infor M3 H5 Development Guide | 3

Opening project in VS Code.............................................................................................. 19

Chapter 3 Deploying scripts ......................................................................................................... 23

Chapter 4 Adding scripts to a form.............................................................................................. 25

Chapter 5 Public APIs.................................................................................................................... 27

4 | Infor M3 H5 Development Guide

Infor M3 H5 Development Guide | 5

6 | Infor M3 H5 Development Guide

Children: any[] .......................................................................................................... 49

Chapter 6 MForms Automation .................................................................................................... 57

Infor M3 H5 Development Guide | 7

Helper Class ............................................................................................................................ 60

Chapter 8 Drillback ........................................................................................................................ 63

Chapter 9 ION API (For MUA 10.4 only) ....................................................................................... 67

Chapter 10 Best practices ............................................................................................................... 71

Chapter 11 Script examples ............................................................................................................ 73

8 | Infor M3 H5 Development Guide

Chapter 12 Appendix ..................................................................................................................... 105

Infor M3 H5 Development Guide | 9

Infor M3 H5 Development Guide | 11

The H5 Scripting Blog

12 | Infor M3 H5 Development Guide

For information about URL

Infor M3 H5 Development Guide | 13

Contents of a script file

/* Write code here */

14 | Infor M3 H5 Development Guide

Debug parameter (deprecated)

Infor M3 H5 Development Guide | 15

16 | Infor M3 H5 Development Guide

Using Visual Studio

Configuring the project

Infor M3 H5 Development Guide | 17

3 Select Properties menu item.

18 | Infor M3 H5 Development Guide

Adding a new script to the solution

Using VS Code and Node.js

Opening project in VS Code

Running Samples on a Node.js server

Infor M3 H5 Development Guide | 19

Adding a new script to the project

MForms Panel Layout

20 | Infor M3 H5 Development Guide

Adding Content to a Form

const contentElement = args.controller.GetContentElement();

Infor M3 H5 Development Guide | 21

22 | Infor M3 H5 Development Guide

Deploying a customized script in M3 H5

Infor M3 H5 Development Guide | 23

Adding a personalized script to a form

Adding a script shortcut

Infor M3 H5 Development Guide | 25

26 | Infor M3 H5 Development Guide

Infor M3 H5 Development Guide | 27