Infor M3 H5 Script Checklist (Review and Test)

0%

0 of 32 items complete

7 critical items still open - these are the highest-risk gaps.

Download checklist:

Design

Business requirement is written and cannot be met by configuration, a personalisation or a standard settingCRITICALScript is scoped to named programs and panels, not globalOwner and support contact are recorded in the script headerAlternatives such as a web service or Infor OS app were consideredData needed from M3 is available through a documented MI call or panel fieldRoles and users who will receive the script are defined

Coding

Script uses documented H5 scripting interfaces only, not internal DOM structuresCRITICALPanel and field lookups handle missing elements without throwing errorsCRITICALEvent handlers are removed on dispose to avoid duplicates after panel changesAsynchronous MI calls have error callbacks and timeoutsNo hardcoded company, division, facility or warehouse valuesMessages shown to users are clear and translatableDebug logging is removed or switchableCode is formatted, commented and under version control

Security and data

No credentials, tokens or keys are in the scriptCRITICALMI calls run with the privileges of the end user, and the user role has needed accessScript does not write data that bypasses M3 validationNo personal data is written to browser storage or logsExternal calls are to approved domains only

Testing

Tested in the target H5 Client version and supported browsersCRITICALTested with a normal user role, not only an administratorTested with empty, long and special-character valuesTested with several panel sequences and with F-key and bookmark navigationTested on tablet or mobile if users work thereTested with slow network and failed MI callRegression test of the standard program flow without the script

Deployment and upgrade

Script is deployed through the controlled promotion process from test to productionCRITICALRollback step is written and testedScript is listed in the customisation register with program, panel and purposeUpgrade impact review is scheduled for each M3 and H5 updateCRITICALUsers and support desk have short documentationScript usage is reviewed yearly and retired when not needed

Every critical item should be checked before production. Below 80 percent overall, hold the deployment and fix the unchecked items first.

Customisation register starter

Optional: a starter layout for tracking M3 scripts and extensions with owner, purpose and upgrade risk.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Tick items as you verify them, in review with another developer if possible. Items marked critical block deployment when unchecked. Export the result as PDF or Excel and attach it to the change record. Repeat the review when the script changes materially or after an upgrade of the H5 Client.

What H5 scripts are for

H5 Client scripts are JavaScript that runs in the browser client and can read and change panel fields, react to events and call M3 interfaces. They suit small usability changes, defaults, validations and links between programs. They are not a place for heavy business logic, which belongs in M3 settings, extensions or an integration layer where it can be tested and monitored.

Common mistakes

The most expensive mistakes are scripts that rely on undocumented page structure and break after an update, scripts with no owner, and logic that duplicates what a standard setting could do. A script register with owner, purpose and last test date prevents most of these. Keep scripts small, one purpose each, and retire them when the standard product catches up.

Frequently Asked Questions

What is an H5 script in Infor M3?

It is a JavaScript customisation attached to a program in the M3 H5 Client. It can change how panels behave, set defaults, validate input and call interfaces, without changing M3 application code on the server.

Do H5 scripts survive upgrades?

Not automatically. Scripts that use documented interfaces usually keep working, but any script should be retested after every update. Scripts that depend on undocumented structure are the ones most likely to break.

When should I not use an H5 script?

Do not use one when a configuration setting, personalisation or standard feature meets the need, or when the logic must apply to all channels such as API and EDI. Server-side or integration solutions apply to every channel, client scripts only to the screen.

How often should scripts be reviewed?

At least after each M3 or H5 Client update and once a year for the register as a whole. Remove scripts that nobody uses or that the standard product has replaced.

Netray can help inventory your existing M3 customisations and flag the ones at risk in an upgrade, so your team can focus its review time.

Talk to an Expert Explore More Free Tools

Related Tools

Infor M3 & CloudSuite

More Infor M3 & CloudSuite tools

See all

Infor M3 H5 Script Checklist: Review Before You Deploy Client Customisations