EPM Vitals Book 20-min demo
Guide Chapters

Product support / Chapter 10

10. Tools Workspace

Use the Tools workspace for configuration utilities, automation support, run evidence, and licensing.

The Tools workspace contains supporting utilities for configuration management, automation, run evidence, upgrade migration, and licensing.

10.1 Configuration

Use Configuration to compare config versions and manage reusable templates.

Config Compare Result
Config Compare Result

Config Compare workflow:

  1. Upload the first configuration workbook.
  2. Upload the second configuration workbook.
  3. Click Run Config Compare.
  4. Review differences.
  5. Download the compare result.

Template Library workflow:

  1. Open the Template Library area.
  2. Review saved configs and sample configs.
  3. Download a sample config if needed.
  4. Reuse validated templates in Validation, Convertor, Configure Wizard, or readiness workflows.
Template Library
Template Library

Typical use cases:

  • Compare two config versions.
  • Freeze a reviewed config before delivery.
  • Reuse an effective config across repeated runs.

10.2 Automation

Use Automation to generate local command or BAT scripts for repeatable runs.

Automation Command Generator
Automation Command Generator

Inputs:

  • Module type.
  • File paths.
  • Config path.
  • Output path.
  • Module-specific options.

Recommended workflow:

  1. Select the module or workflow type.
  2. Enter local file paths.
  3. Generate the command or BAT script.
  4. Download the script.
  5. Review the paths before running it locally.

Notes:

  • Generated scripts run on the user's machine.
  • Local paths must remain valid.
  • Automation does not change the rule that production data should not be sent to support.

10.3 Run History

Use Run History to find previous runs, open outputs, export history, and clean up records.

Run History List
Run History List

Filters:

  • Module.
  • Status.
  • Show count.

Key buttons:

  • Open Folder
  • Open Result
  • Open Summary
  • Delete
  • Download CSV
  • Download Excel

Recommended workflow:

  1. Filter by module and status.
  2. Select the run you want to inspect.
  3. Open the result, summary, or run folder.
  4. Export history if you need a project evidence list.
  5. Delete obsolete run records only when the project no longer needs them.
Run History Detail
Run History Detail

Outputs:

  • CSV history export.
  • Excel history export.
  • Access to local result files and run folders.

10.4 Upgrade Assistant

Use Upgrade Assistant when you have installed or extracted a new EPM Vitals package and want to carry forward selected local assets from an older package.

The assistant generates a Windows BAT script. It does not run the migration inside EPM Vitals, and it does not activate a license, rebuild indexes, or reprocess business files.

Typical assets:

  • License: copies license.dat and the package-local time guard sidecar if it exists.
  • Application Profiles: copies initialized application profiles, including profile-owned internal workbooks and derived indexes, while excluding background job and staging folders.
  • Template Library: copies reusable configuration templates.
  • Run History: optional; copies the history CSV for reference.
  • Run Outputs: optional; copies historical run folders and can be large.
  • Generated Configs: optional; copies generated configuration workbooks for manual reference.

Recommended workflow:

  1. Open Tools > Upgrade Assistant.
  2. Select the old package root. You may select either the release folder or its app folder.
  3. Select the new package root. You may select either the release folder or its app folder.
  4. Review the selected assets. The default selection is License, Application Profiles, and Template Library.
  5. Optionally click Run Preflight to check source existence, target collisions, estimated file count, and estimated copy size.
  6. Click Generate Migration BAT.
  7. Download the BAT file.
  8. Close the new EPM Vitals package.
  9. Run the BAT locally from Windows.
  10. Start the new EPM Vitals package and confirm that copied assets are available.

Important notes:

  • The generated BAT writes a migration log under the new package app folder.
  • If a selected target asset already exists, the BAT backs it up under _upgrade_backup_<timestamp> in the new package app folder before copying.
  • Run Preflight is optional. It is a dry run only and does not copy files.
  • Keep the old package available until you have confirmed that the new package can read the migrated assets.
  • If the copied license is not valid for the current machine or product version, the normal License Activation page will report that status.