Platform is where you find out whether the installation is well, and where you act when it is not.

Where to find these pages

Utilities › System
Update WBAMS, System Health, Automation Status, Mail Check, Database Status, System Cleanup and PHP Info.
Utilities › Logs
Activity Log, Admin Log, Email Log, Module Log and Mail Import Log. The Gateway Log is under Billing.
The wrench menu
At the top right: System Settings, Management Levels, Apps & Integrations, Manage Admins, Default Admin Theme, System Health, System Logs, Get Help and License Information.
System Settings
Every setup page, searchable, in categories. People & Organization holds Management Levels and, while those levels are on, Membership Types, Membership Policy, Pay Items, Payroll Tax and Employer Policy. System also lists Mail Check and Default Admin Theme. The progress badge at the top opens the setup tasks.
Content Manager › Media Library
Opens the media library to upload, rename and delete the pictures and videos used across WBAMS.

System Health

System Health rates the installation and lists what needs attention: runtime and extension problems, directory permissions, default paths that could be moved, the license state, and whether the automation has completed in the last 24 hours.

The cron warning means what it says.

“The system cron does not appear to have completed successfully within the last 24 hours” is not a false positive to be dismissed. It clears only after a successful run.

Updates

Releases come from your license server. WBAMS checks the channel you are on, verifies the package it downloads against the checksum the server publishes, backs up every file it replaces, and applies the database migration afterwards.

  1. Back up the database and the application files together, before anything else.
  2. Read the release notes for manual steps. Some releases have them; they are always listed first.
  3. Apply the update and let the database migration run to completion.
  4. Sign in and open one page from each area before declaring it done.

License

The license page shows the license state and lets you change the key. License checks are made against the license server and cover the deployment and domain your order permits. A failed check has a grace period; it is not indefinite.

Database

Every table with its row count and on-disk size. Optimize tables after large deletions, and download a backup before upgrades. The largest tables on a mature installation are usually the logs, which is what the cleanup tools are for.

Cleanup

Cleanup removes historical data that has stopped being useful: old log entries, expired sessions, orphaned records. Read what each option will delete before running it. Cleanup is not reversible and does not ask twice.

Activity and administrator logs

The activity log records what the system did; the administrator log records what people did. Both are filterable by date, wording, administrator and IP address. When something changed and nobody knows why, the administrator log is the first place to look, and it only helps if administrators have individual accounts.

Email, mail and module logs

Email log
Messages the product generated, and whether sending succeeded.
Mail import log
What the mail import brought in, and what it rejected. Empty until the scheduler is set up, which is new in 1.5.0.
Module log
Requests to and responses from provisioning and gateway modules. This is the log that answers “the gateway says it worked, so why didn’t we?”
Gateway log
Payment callbacks as received. Check here before contacting a payment provider.

Troubleshooting module problems

  1. Reproduce the action and read the module log entry it produced, request and response together.
  2. Confirm the credentials the module holds are for the environment you think it is talking to.
  3. Check the server can reach the remote endpoint at all, then whether it is being refused.
  4. Only then change configuration. A module that never logged a request has a connectivity or credentials problem, not a settings problem.

PHP version compatibility assessment

The assessment reads the installation — including extensions and customizations — and reports what would break on a newer PHP version. Run it before changing the PHP version, not after. It reports findings by severity; treat anything it calls fatal as a blocker rather than a warning.

PHP information

Everything PHP reports about the server: version, loaded extensions, configuration directives and environment. Use it to confirm what is actually loaded rather than what is believed to be loaded. If phpinfo() is unavailable the page says so; that is a hosting restriction, not a fault.

Scheduler

The scheduler page reports when the automation last ran and what it did. It also provides a web trigger, which requires the $cron_key from settings.php and answers 404 without it.