How to Add a Personalization Script to an M3 H5 Panel

Add a personalization script to an H5 panel

1. 1Confirm you have Application Administrator (or equivalent personalization) rights in H5 - regular end users can personalize layout but not attach scripts.
2. 2Open the target program and navigate to the exact panel where the behavior should apply; scripts attach at the panel level, not the whole program.
3. 3Enter Personalization mode from the H5 toolbar/gear icon and open the scripting option for that panel.
4. 4Write the script against the MForms client API, using panel-load and field-change event hooks rather than polling the DOM directly.
5. 5Reference fields by their panel field name (visible in the panel's field properties, not the on-screen label) so the script keeps working if the label is later translated or renamed.
6. 6Test the script in a non-production environment first, exercising both the normal path and edge cases (empty field, invalid value) before saving.
7. 7Save the script against the panel and decide the deployment scope - all users, a specific role, or a specific user - matching how narrowly the behavior should apply.
8. 8Document what the script does and why in a change log outside H5 itself, since personalization scripts do not show up in standard M3 program documentation or upgrade impact reports.

Working with the MForms API

// Simplified pattern - actual MForms API calls vary by H5 version
MForms.onFieldChange("WHLO", function(value) {
  if (value === "CENTRAL") {
    MForms.setFieldValue("TEDL", "DEFAULT-ROUTE");
  }
});

Common pitfalls

• !Using a personalization script to enforce a business rule that really needs to apply everywhere, including batch jobs and API calls, which the script will never see.
• !Referencing a field by its on-screen label instead of its panel field name, breaking the script when the label is translated or edited.
• !Polling the DOM continuously instead of hooking MForms field-change and panel-load events, which hurts performance and behaves inconsistently across panel states.
• !Not testing add mode, change mode, and different role-based field visibility before deploying a script broadly.
• !Losing track of which panels have scripts attached, since H5 has no single central inventory view most administrators check regularly.
• !Skipping personalization scripts during upgrade or update testing because they are not part of the core program.