Skip to main content
Version: 5.0 🚧

Report default settings

Overview​

Use the Report default settings page to define the default number of events and processes included when PowerManage generates reports.

Use this page when you need to:

  • Increase report detail for high-volume systems.
  • Keep report size consistent across operators and scheduled jobs.
  • Set safe defaults that operators can override per report when needed.

This page solves a common reporting problem where fixed limits exclude relevant history.

Before you begin​

Required permissions​

  • You must have permission to edit Resolve category settings in Server Settings.
info

Access to Report default settings is controlled by permissions for the Resolve settings category.

Preconditions​

  • You can open the Settings page in the Web GUI.
  • You know the expected report volume for your environment.

Dependencies​

  • Report output volume depends on both default limits configured here and any per-report override selected during report creation.
  • System performance constraints enforce an upper limit of 255 for both fields.

Important limitations​

warning
  • Values above 255 are not supported.
  • Higher limits can increase report generation time and output size.
  • These values are defaults. Operators can still set custom values per report when creating or scheduling reports.

Page layout​

Edit report default settings dialog​

Edit report default settings dialog (light) Edit report default settings dialog (dark)
CalloutUI elementDescriptionWhen to use
1Default max eventsSets the default maximum number of panel events included in generated reports. Includes event types such as alarms, arm/disarm, troubles, and restorals. Default is 20. Accepted range is 1-255.Use when report consumers need more or fewer event records by default.
2Default max processesSets the default maximum number of process records included in generated reports. Includes processes such as discovery, configuration upload/download, RRI, firmware upgrade, set state, and VOD requests. Default is 20. Accepted range is 1-255.Use when operational workflows require more or fewer process records in each report.
3Cancel buttonCloses the dialog and discards unsaved changes.Use when you need to exit without applying edits.
4Save buttonSaves current values and applies them dynamically to subsequent report generation.Use after validating values and confirming impact.

How to use this page​

Configure global report defaults​

Goal:

  • Set standard event and process limits for all newly generated reports.

Steps:

  1. Open Settings.
  2. Go to Report default settings in the Resolve category.
  3. Select the edit icon.
  4. Enter a value for Default max events.
  5. Enter a value for Default max processes.
  6. Select Save.

Expected result:

  • The system saves both default limits.
  • Any newly generated or scheduled report uses these defaults unless an operator sets custom per-report values.

Increase limits for high-activity environments​

Goal:

  • Include more history in each generated report for environments with high event or process volume.

Steps:

  1. Open the Edit report default settings dialog.
  2. Increase Default max events and/or Default max processes.
  3. Keep each value at or below 255.
  4. Select Save.
  5. Generate a test report to validate output size and generation time.

Expected result:

  • New reports include more records by default.
  • Report generation uses updated limits immediately for subsequent reports.
note

If the generated output is too large for your workflow, reduce one or both limits and test again.

Revert to baseline defaults​

Goal:

  • Restore conservative default limits that match legacy behavior.

Steps:

  1. Open the Edit report default settings dialog.
  2. Set Default max events to 20.
  3. Set Default max processes to 20.
  4. Select Save.

Expected result:

  • New reports return to baseline defaults.
  • Operators can still override values per report if needed.

Tips​

tip
  • Start with 20 and increase gradually based on actual reporting needs.
  • Keep higher values for environments that need longer event or process history in each report.
  • Use per-report overrides for exceptional cases instead of permanently increasing global defaults.

Troubleshooting​

Save does not apply changes​

Possible causes

  • One or both values are outside the accepted range.

What to do

  1. Verify both fields are within 1-256.
  2. Confirm your role can access Resolve settings.
  3. Re-enter values and select Save again.

Reports still show fewer records than expected​

Possible causes

  • The report was generated before the new defaults were saved.
  • A per-report custom limit overrides the system default.
  • Source data contains fewer records than the configured maximum.

What to do

  1. Confirm that Save completed successfully.
  2. Generate a new report after the change.
  3. Check report creation settings for a custom Event/Process quantity.
  4. Confirm that enough source events or processes exist.
Was this page helpful?