Edit assets
Phase 1 preview — pages render fixture data only; no changes are saved.
Selected
1
Eligible
1
Blocked / skipped
0
Would change
0
Would stay as is
1
- Batch rule: every asset is processed on its own; one failing doesn't undo the others.
- Assets are updated one by one with no transaction: a failure on one leaves the earlier ones saved (a partial result).
- Each saved asset gets an ordinary `update` activity row with an old/new diff; there are no bulk-specific log types.
- Legacy applies the update with only the class-level permission (no per-asset or company check on the web path); the Go rule should check each asset.
Selected assets (1)
| Asset | Current state | Verdict | Reason / note | Would become | Actions |
|---|---|---|---|---|---|
| TC-00018 Hypervisor 01
| Deployed · Checked out to London HQ – Server Room (location) | Would proceed | — | No change |