Every change to a capex plan, a row per field, in the shape of capex_proposal_change_logs: changed_by, changed_at…
Every change to a capex plan, a row per field, in the shape of capex_proposal_change_logs: changed_by, changed_at, field_name, old_value, new_value and remarks. Its header, the teams and people its invite is sent to (a team or a person added is a row with new_value, one taken off a row with old_value), your organisation’s own questions on it and the files under Supporting documents. The plan’s creation is a row per field it was started with and its removal a row of its own; activity says which, CREATED, EDITED or DELETED. Where the plan is approved as a whole, that approval is activity APPROVAL. Each row names its plan by capex_plan_id, request_id (the plan’s code) and proposal_name (the plan’s name); the plan’s proposals are in capex_proposal_change_logs. Listed to you if you hold finance.capex_change_log.view and may view capex plans, for the 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

