Infor M3 Smart Office to H5 Script Migration Checklist
This checklist plans the move of Infor Smart Office scripts, mashups, shortcuts and personalizations to the M3 H5 client. It is for migration; for reviewing the code of a single H5 script before deployment, use the H5 script review checklist.
0 of 27 items complete
7 critical items still open - these are the highest-risk gaps.
Inventory
Classify
Rewrite
Test
Deploy
Critical items prevent the two typical failures: scripts migrated without source or owner, and Smart Office left running indefinitely beside H5. Do not decommission Smart Office until every critical item is checked.
Get your Smart Office script inventory classified
Send us your script list with programs and purposes and we will suggest which to retire, replace or rewrite in H5.
Optional. The tool and every export work without this. No spam.
How to use it
Start with Inventory and do not skip it: most migrations fail because nobody knows which scripts exist or who depends on them. Classify each item before writing any code. A good share of Smart Office scripts can be retired or replaced by a personalization, a shortcut or a standard setting, and that is cheaper than a rewrite. Use Rewrite and Test per script, and Deploy per user group. Export the list with your inventory as the migration plan, then rerun the Deploy group before decommissioning Smart Office for each group.
What changes between Smart Office and H5
Smart Office is a .NET desktop client and its scripts are JScript.NET with access to WPF elements, typically through controller.RenderEngine.Content and ScriptUtil.FindChild. H5 runs in the browser, and scripts are JavaScript, usually written in TypeScript against the H5 script SDK. An H5 script is a class with a static Init method that receives script arguments: the instance controller, a log object and the argument string. MI calls use MIRequest objects executed through MIService.Current.executeRequest, which returns a promise. Smart Office mashups are XAML and have no direct H5 equivalent, so each needs a separate decision.
- Smart Office: JScript.NET, WPF, desktop
- H5: TypeScript or JavaScript, browser DOM
- MI calls: MIRequest plus MIService.Current.executeRequest
- Mashups: decide case by case
Worked example
A Smart Office script on OIS100 panel A fills a default order type from the customer and warns if a credit limit is near. In H5 the developer writes a TypeScript class with a static Init, reads the customer field through the H5 controller, calls a customer MI transaction with MIRequest and MIService.Current.executeRequest, and shows a message on the panel. Logging goes through args.log and only appears in the browser console, so the support team is shown how to read it. The script is uploaded in the H5 administration tools, attached to OIS100, tested in English and Swedish and released to the order desk.
Gotchas
Do not port field access line by line: controller.FieldMap from older H5 examples is not available in the new H5 UI, and Smart Office element lookups do not exist in the browser. Keyboard behaviour differs, and users notice missing F-key shortcuts before anything else. Autocomplete and field prompts in H5 behave differently from Smart Office, so test data entry speed with real users. Scripts that wrote local files or launched desktop programs need another design, usually a server-side integration.
Frequently Asked Questions
What is Infor Smart Office?
Infor Smart Office (formerly Lawson Smart Office) is the .NET desktop client for M3, supporting JScript.NET scripts, XAML mashups, shortcuts and personalizations. Many M3 sites have moved users to the browser-based H5 client, which needs those scripts rewritten in JavaScript or TypeScript.
Can Smart Office scripts run in H5?
No. Smart Office scripts are JScript.NET running against WPF elements in a desktop client. H5 runs in the browser and uses its own script API. Each script must be rewritten, replaced by a personalization or standard setting, moved to an integration, or retired.
How does autocomplete work in M3 H5?
H5 provides its own field prompting and suggestion behaviour, which is different from Smart Office. Scripts that filled fields or offered suggestions in Smart Office should be retested against H5 behaviour first; often the standard H5 behaviour is enough and the script can be retired.
Do Smart Office shortcuts need a script in H5?
Usually not. Many Smart Office shortcut scripts only opened another M3 program with a few values filled in, and H5 has its own shortcuts and personalizations for that. Rebuild those as H5 shortcuts first and keep scripting for cases that need logic, such as validation or MI calls. Check the H5 user guide for your release for the shortcut options.
If you want order desk users to ask M3 questions in plain English instead of adding more panel scripts, we can set that up on your own servers.
Related Tools
Infor M3 H5 Script Review Checklist
A review checklist for H5 Client scripts covering design, coding, security, testing and upgrade risk.
Infor M3 & CloudSuiteInfor M3 13.x On-Premises Upgrade Readiness Assessment
Score how ready your on-prem Infor M3 environment is for an upgrade to a newer 13.x release, across modifications, client scripts, integrations, infrastructure and testing.
Infor M3 & CloudSuiteInfor M3 LCM Fix and Cumulative Update Checklist
Checklist for applying M3 Business Engine fixes and cumulative updates on an on-prem M3 13.x system through Lifecycle Manager, including MAK retrofit and regression checks.
Infor M3 & CloudSuiteInfor M3 MI API and ION API Gateway Security Checklist
Security checklist for on-prem M3 13.x integrations using MI programs over REST and the ION API gateway: accounts, authorization, transport, monitoring and lifecycle.
More Infor M3 & CloudSuite tools
See all- Infor M3 Program Reference (MMS001, OIS100, PMS100)
- Infor M3 MI API Transaction Call Generator
- Infor M3 Customer Order Status Tracking Worksheet
- Infor M3 Item Master Upload Worksheet
- Infor M3 MEC Mapping Design Template
- Infor M3 Upgrade Test Checklist
- Infor M3 Facility and Warehouse Structure Worksheet
- Infor M3 Fit-Gap Analysis Worksheet
- Infor M3 Interface and Integration Inventory Worksheet
Keep exploring
Free tools
- Infor M3 H5 Script Review ChecklistA review checklist for H5 Client scripts covering design, coding, security, testing and upgrade risk.
- Infor M3 H5 Hot Keys and Function Keys ReferenceKeyboard shortcuts for M3 programs in the H5 client: function keys, list options, paging, and the Mac setting that makes them work.
- Infor M3 H5 Script TypeScript Template GeneratorGenerate a starting H5 script class that reads a field on an M3 panel, calls an MI transaction and shows the answer on the panel, on load or before Enter.
ERP fixes and how-tos
- Infor M3 Export to Excel: Lists, Report Output and the API RouteHow to export Infor M3 list and panel data and report output to Excel using the client export, the Excel add-in or the MI API, plus common limits and pitfalls.
- How to Add a Personalization Script to an M3 H5 PanelAdd a JavaScript personalization script to an M3 H5 panel using the MForms API: setup, panel/field events, save and deploy, and common scripting mistakes.
- Infor M3 Business Engine upgrade checklist: customizations and integrationsPractical checklist for an Infor M3 Business Engine upgrade: inventory customizations, integrations, H5 personalizations, reports and a regression test plan.
Guides
- Infor M3 H5 Client Personalization and Scripting GuideWhat the Infor M3 H5 client is and how to tailor it: personalization layers, JavaScript scripts, bookmarks and deployment, without touching the Business Engine.
- Infor M3 Technical Architecture Explained Layer by LayerInfor M3 technical architecture explained: M3 Business Engine, Infor Grid, database tables, H5 client, and integration layers for on-prem and CloudSuite teams.
- Infor M3 Upgrade and CloudSuite Migration PlanningInfor M3 upgrade and CloudSuite migration guide: modification inventory, extensibility rework, data strategy, testing waves, and 9 to 18 month timelines.