Every change to a capex proposal, a row per field: who changed it (changed_by), when (changed_at), which field…
Every change to a capex proposal, a row per field: who changed it (changed_by), when (changed_at), which field (field_name, and field, the column it was), what it was (old_value) and what it became (new_value). A proposal’s creation is a row per field it was raised with, its phasing is a row per month changed, and its removal is a row of its own; activity says which, CREATED, EDITED or DELETED. The proposal’s journey through its approval is here too, as activity APPROVAL: field approval_status for the request, with the request’s status (PENDING when raised, then APPROVED, REJECTED, REVISION, WITHDRAWN), and approval_step for each level, with field_name the level’s name, the level’s status (PENDING when reached or asked again, then APPROVED, REJECTED, SKIPPED, or ROLLBACK and REVISION where it sent the request back to the level before it or to its creator) and remarks what the approver wrote. request_id and proposal_name say which proposal each row is about. A reference is given as the name of what it points at; dates and amounts as stored. Listed to you if you hold finance.capex_change_log.view, for the proposals on capex plans you can read.
Headers
Limiting and Pagination
Limiting and Pagination
Preference
count=none Query Parameters
Filtering Columns
Ordering
Limiting and Pagination
Limiting and Pagination
Response
OK

