# Infor M3 H5 Script Checklist: Review Before You Deploy Client Customisations > Source: https://netray.co/tools/infor-m3-h5-script-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A review checklist for H5 Client scripts covering design, coding, security, testing and upgrade risk. ## Category infor-cloudsuite ## Erp Infor M3 ## Audience - M3 developer - M3 technical consultant - Solution architect ## Tool **Kind:** checklist **Groups:** #### Design **Items:** **Text:** Business requirement is written and cannot be met by configuration, a personalisation or a standard setting **Critical:** true Script is scoped to named programs and panels, not global Owner and support contact are recorded in the script header Alternatives such as a web service or Infor OS app were considered Data needed from M3 is available through a documented MI call or panel field Roles and users who will receive the script are defined #### Coding **Items:** **Text:** Script uses documented H5 scripting interfaces only, not internal DOM structures **Critical:** true **Text:** Panel and field lookups handle missing elements without throwing errors **Critical:** true Event handlers are removed on dispose to avoid duplicates after panel changes Asynchronous MI calls have error callbacks and timeouts No hardcoded company, division, facility or warehouse values Messages shown to users are clear and translatable Debug logging is removed or switchable Code is formatted, commented and under version control #### Security and data **Items:** **Text:** No credentials, tokens or keys are in the script **Critical:** true MI calls run with the privileges of the end user, and the user role has needed access Script does not write data that bypasses M3 validation No personal data is written to browser storage or logs External calls are to approved domains only #### Testing **Items:** **Text:** Tested in the target H5 Client version and supported browsers **Critical:** true Tested with a normal user role, not only an administrator Tested with empty, long and special-character values Tested with several panel sequences and with F-key and bookmark navigation Tested on tablet or mobile if users work there Tested with slow network and failed MI call Regression test of the standard program flow without the script #### Deployment and upgrade **Items:** **Text:** Script is deployed through the controlled promotion process from test to production **Critical:** true Rollback step is written and tested Script is listed in the customisation register with program, panel and purpose **Text:** Upgrade impact review is scheduled for each M3 and H5 update **Critical:** true Users and support desk have short documentation Script usage is reviewed yearly and retired when not needed **Scoring Note:** Every critical item should be checked before production. Below 80 percent overall, hold the deployment and fix the unchecked items first. ## Content **Intro:** H5 scripts are quick to write and expensive to forget about. This checklist covers what to confirm before a script goes live and what to schedule for later upgrades, so a small change does not become a hidden support burden. **Sections:** #### How to use the checklist **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is an H5 script in Infor M3? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms M3 H5 script, H5 client scripting checklist, Infor M3 H5 customization, M3 H5 script review, M3 H5 script best practices, M3 script upgrade impact, M3 H5 JavaScript --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json