Service History
Read the immutable record of everything that happened to a service, so a status change, a price edit or a switch the client flipped can be traced to the account behind it and the minute it happened.
Reaching the Screen
History is one of the tabs of a service record, so it opens with the service: {admin}/services/detail?id={service}&content=history
Panel menu: Orders › Services, then the service, then History. Every service record carries it, whatever it sells and whatever state it is in. The rows travel down with the page, so the tab is filled when you open it.
What Is on the Screen
Two things: the controls above the list, and the list itself. Nothing here changes the service; the tab only reads what the other tabs, the client's panel and the automation wrote.
The controls above the list
The Date Range box sits above the table. Click it to open a calendar and pick a first and a last day; the list keeps the entries between them, both days included. A single day filters that day, and the clear button inside the box brings the whole list back. The button beside it decides how the dates are read: Equals keeps what falls inside the range, Exclude Date what falls outside it, and On or After, After, On or Before and Before use one edge as a boundary.
On the table's own top edge: Show Records sets how many rows a page holds, the search box matches the text of the rows so a status, a staff name or an address finds its entries, and the download icon saves the list as a file. Search and the date range stack, and the counter under the table reports how many survived both; with nothing left it says No data available in table. The date range works on the entries the page already holds.
The list
Four columns, newest entry at the top. Only Date can be re-sorted; the other three are there to be read, because a name or an address is something you search for. Sorting happens in the browser, on the entries the page already holds.
The sentence in Description is assembled when you open the tab, not when the change happened: the event supplies the wording and the stored values are dropped in, which is why an old entry still reads in today's panel language. Values are translated on the way, so a status returns as its badge, a currency as its code and a switch as Enabled or Disabled. An event with no sentence of its own falls back to its raw event name, a technical string rather than a broken row.
Fields
The four columns
Who an entry belongs to
The left column names an account and labels it. The label follows the account type at the moment you read the list, not when the entry was written.
What gets recorded
Creating a service writes no entry of its own, so the first line a new record carries is usually the status change that activated it. DNS records, nameservers, DNSSEC entries, WHOIS contacts, forwarding rules, requirement answers and additional information blocks are saved without writing an entry here, and reading or exporting the tab records nothing.
| Entry | Written when | Recorded against |
|---|---|---|
| Status changed | The service moves between Pending Approval, In Progress, Active, Suspended, Expired, Cancelled and Completed, from any screen or from automation | Staff, Client or System |
| Service field changed | A Details tab field is saved with a new value: name, admin note, module, payment method, subscription, any date, cycle, amount, currency, quantity, discount, pricing type, billing profile, blocked access, skipped renewal invoice, automatic payment or the Auth (EPP) code. Each gets its own entry | Staff |
| Client, product or server changed | The service moves to another client, its linked product is replaced or cleared, or it moves to another server | Staff |
| Quick action, preference or module tool | The service is reinstalled, its access password changed or a licence reissued; Management tab preferences are saved; a module tool is run here | Staff |
| Add-on written | An add-on row is created or deleted, its status or a field changes, a paid upgrade rewrites it, or a plan change carries it onto the new cycle | Staff or System |
| Upgrade or downgrade applied | A plan change finishes, naming the old and the new product with their cycles | System |
| Cancellation request accepted or removed | The client's cancellation request is approved or deleted | Staff |
| Ownership or licence transfer | An ownership transfer is started, cancelled, rejected, approved or removed, or a licence transfer is started, cancelled or completed | Client, Staff or System |
| Subscription changed | A payment subscription is cancelled, its recurring amount is synced to current prices, or the service leaves one | Staff or System |
| Renewal paid | A renewal payment extends the term, or a domain renewal is confirmed with the years it bought | System |
| Client-panel switch or automatic metric disable | The client turns auto-renew, the transfer lock, WHOIS privacy or a metered feature on or off, or a metered feature is switched off because its usage invoice went unpaid past its due date | Client or System |
Tasks
Trace who changed something
- Open the service from Orders › Services and select the History tab.
- Type what you are after into the search box at the top right of the table: a status, a staff name or an address.
- Read the row: Description names the change with the values it carried, By the account it is recorded against, IP Address where it came from.
Narrow the list to a date range
- Click the Date Range box above the table and pick the first and the last day.
- Leave the operator button on Equals to keep the days inside the range, or switch it to a boundary option to keep everything before or after one edge.
- The list keeps only the matching entries and the counter under the table follows. The clear button inside the box brings the rest back.
Download the log
- Press the download icon at the right edge of the control strip above the table.
- Choose CSV, JSON or XML from the menu that opens.
- The file arrives with the whole filtered list rather than the page on screen, in the same four columns. A date range picked above the table does not reach it, and the search is re-run against the stored record, not the sentence on screen.
Things to Watch
The tab carries no action at all: an entry cannot be edited, removed or hidden. A mistake made on another tab is not undone here, it is followed by the entry that corrects it.
An entry recorded against a client can be what the client did or what the product did on their behalf. Read the sentence before the name: Staff Member is the only label that means a person in the panel acted.
It carries the addresses changes came from, the names of the staff who made them, old and new prices, discounts and notes. That is what makes it useful in a review and a document to keep inside the company.
Required Privileges
The tab opens with the service record and needs the same rights: SERVICES_LOOK or SERVICES_OPERATION, either one on its own is enough. Staff holding neither never reach the record, so the tab is out of reach with it.
The download icon is separate and follows the panel-wide table export permission. Without it the icon is not drawn and the export cannot be reached by other means, while the list stays readable.
Related Articles
Vielen Dank für Ihre Rückmeldung!
Unser Support-Team ist rund um die Uhr für Sie da, wenn Sie oben nicht fündig werden.