Default package update behavior for additional package files

When installing a new version of a package, the current additional package files are overwritten by the automatic running of a Windows installer package—MSI—file during the upgrade process. Starting with version 4.0, when updating from a previous major version, any current additional files that would be overwritten are moved to the folder C:\ProgramData\MDM_MSIBackup before the new additional files are installed.

You can view the MSI file on the Edit Package page.

The default file paths within the Work Tasks application folder for each of the additional file categories are:

• CSS files: ...\Web\BPMUITemplates\Default\NextGenForms\css\custom

• Label text files:

  • Configuration text files: ...\Locales\en-US\Forms2

  • Text files for run time: ...\Locales\en-US\Forms2\Standard

• JavaScript files: ...\Web\BPMUITemplates\Default\NextGenForms\js\custom

• SVG and PNG files: ...\Web\BPMUITemplates\Default\Themes\MDMTHEME\IMAGES\MDM

• Web widget files: ...\Web\BPMUITemplates\Default\NextGenForms\custom\Widgets, then a subfolder for each widget

• Help files: ....\Web\BPMUITemplates\Default\NextGenForms\MDMHELP, then a subfolder for each form's help

The additional package files are also included separately in the Additional Files folder of the MES model-driven application content installation files, if needed.

Additional Files and Custom Content Packages

The MES model-driven application content packages have been enabled to allow you to use them as a template for your own custom content packages. However, note that additional package files are not versioned. It is recommended that you do not change these files as they are overwritten as part of the package upgrade process.

If custom changes are required, you should create your own custom version of the new files using different file names (which will not be overwritten during the upgrade). Or, before upgrading the package, make a backup of the existing custom files to preserve your modifications for future use, if needed. If you do add or modify any additional files after the package upgrade, make sure you reset IIS and clear web browser cache to see your changes reflected.