SCEM Extension Manager Now Minifies and Obfuscates Extension JavaScript by Default

Starting with version 2026.1.0 of the SuiteCommerce Extension Management (SCEM) bundle, a new preference called SCEM Enable Code Optimization automatically processes extension JavaScript each time you activate an extension. This is enabled by default.

What Changed

The new code optimization pipeline runs at activation time and applies two transformations to extension JavaScript:

• Minification — strips whitespace, comments, and unnecessary characters to reduce file size and improve browser download/parse times.
• Obfuscation — rewrites code to make it harder to read and reverse-engineer, adding a layer of IP protection for extension source.

The optimization scope covers:

• All JavaScript files within the extension being activated.
• Shared files such as ssp_libraries_ext.js, which is used across all domains within an SSP application. This means activating a single extension can trigger reprocessing of shared assets that affect other domains.

The preference is located at Setup > Company > General Preferences > Custom Preferences.

What to Watch Out For

• Debugging will be harder. Obfuscated and minified output in the browser makes client-side debugging significantly more difficult. If you rely on reading compiled extension output in browser DevTools, you will need to disable this preference during development.
• Shared file reprocessing. Because ssp_libraries_ext.js is shared across domains within an SSP application, activating an extension on one domain may change the optimized output of that shared file for all domains. Plan activations accordingly, especially in multi-domain setups.
• Activation time may increase. The additional minification and obfuscation step runs during every activation. For extensions with large JavaScript footprints, expect longer activation processing times.
• Source specifics are unclear. Oracle does not document which obfuscation technique or tool is used, whether source maps are generated, or whether the optimization can be toggled per-extension vs. globally only. The preference appears to be an all-or-nothing global toggle.

What to Do

1. Verify your SCEM bundle version. Go to Customization > SuiteBundler > Search & Install Bundles > List and confirm you are on SCEM bundle version 2026.1.0 or later. The preference only exists on this version and above.
2. Check the default. Navigate to Setup > Company > General Preferences > Custom Preferences and confirm SCEM Enable Code Optimization is checked (it is enabled by default).
3. Disable for development/debugging. If you are actively developing or debugging extensions, clear the checkbox before activating. Re-enable it before activating for production.
4. Test existing extensions. Re-activate your extensions in a Sandbox account with optimization enabled and verify no runtime errors are introduced by the minification/obfuscation pass — particularly for code that uses dynamic property access, eval, or relies on function/variable naming conventions at runtime.
5. Coordinate multi-domain activations. Since shared files like ssp_libraries_ext.js are reprocessed on activation, coordinate activation schedules across domains to avoid unexpected changes to shared assets during peak traffic.

Other Notes

The remainder of this page is reference documentation for the Extension Manager itself (activating/deactivating themes and extensions, script deployment requirements, role permissions). These are not new to 2026.1 — the only net-new feature on this page is the SCEM Enable Code Optimization preference described above.

As a reminder: the SCEM bundle still requires the Administrator role for activation operations (bundle version 2019.1+). Non-admin roles require explicit Script Deployment configuration.