This documentation was authored by secure AI tools.  Please review this content carefully before integrating it with other processes.

Set All Sites and Products InActive

Path: File > Companies > open a customer > Extended menu > Set All Sites and Products InActive

Purpose

Use this command when a customer is being deactivated and you need Q360 to inactivate that customer’s sites, products, and put service contracts into a non‑active status in one pass. This helps prevent new service activity and billing against the account while preserving history.

What happens when you run it

• Sets Customer status to INACTIVE.
• Sets all Sites to INACTIVE.
• Sets all Products/Machines to INACTIVE.
• Closes any open Recurring Dispatches by setting the end date to today and Renewal Type to NONE.
• Updates Service Contracts to a non‑active status (per SCSTATUS configuration; see How the Status is Determined below) and sets Renewal Type to NONE.

Note: This action does not delete records. It changes status/active flags so the records stop appearing in “active only” views and cannot be used for new transactions.

How the Status is Determined

Service Contracts (configurable)

Admin > General Code > SCSTATUS

• Ensure the status you want applied by this routine is Active = Y and State/Flag ≠ ACTIVE.
• Option A (recommended): Create/enable a code value INACTIVE and place it where you like in the list. The routine will pick this explicitly.
• Option B: If you prefer a different code (e.g., HOLD), give that code the lowest Sequence among your non‑ACTIVE statuses.

The action prefers an INACTIVE code; otherwise it uses the first non‑ACTIVE status by Sequence in SCSTATUS.

Sites & Products (not configurable)

• Sites: status is set to INACTIVE.
• Products/Machines: status is set to INACTIVE.
• Recurring Dispatches: end date is set to today and Renewal Type is set to NONE.

These changes are applied directly by the routine; there is no separate code list that determines alternative statuses for sites or products.

Prerequisites & Permissions

• Requires CUSTOMER_EDIT permission (checked automatically when you run the action).
• You must have permission to edit Customer, Site, Product, and Service Contract records.
• Verify no users are actively editing the customer or its contracts to avoid record locks.