Capex plans with what was asked for, what survived, and what is holding them up. awaiting_instance_id is the approval…
Capex plans with what was asked for, what survived, and what is holding them up. awaiting_instance_id is the approval request a submitted plan is waiting on; my_task_id is the step of it waiting on you in your own name, which is what api.reject_capex_plan acts on; awaiting_apply is true between the last approval and the moment it is carried out, when the plan can no longer be taken back. heads_opened counts finally approved schemes with a budget head, and schemes_awaiting_heads the finally approved schemes that api.open_capex_plan_budgets would still open one for. The proposals_ columns count the plan’s schemes by where each stands as a proposal: draft, in approval, approved for the consolidation plan, rejected, under revision, Capex Plan approved and Capex Plan rejected; a scheme copied into a division plan by the earlier whole-plan process is counted there instead, and proposals_consolidated says how many. A plan turned down by its approvers is back in DRAFT with decided_at and decision_reason saying when and why, until it is submitted again. description is formatted markup; description_text is the same description as words, for a report or an export. invite_subject is the subject its stakeholder invite carries, or null where it takes the template’s. custom_fields holds the answers to your own fields on the plan. fiscal_year_start_month is the month the plan’s calendar starts its financial year in, so fiscal_year 2027 on a calendar starting in April is April 2026 to March 2027. window_opens_on and window_closes_on are the dates a unit plan for this year may be entered between, and entry_open says whether today is one of them; a year with no window, and every division plan, is always open, and so is a draft its approvers turned down, which may be corrected and submitted again after the window has closed. proposal_approval is true where your organisation approves each scheme on its own, in its own workflow, rather than sending whole plans for approval. phasing is true where your organisation phases each scheme’s cashflow month by month; where it is false no scheme is asked for a phasing, and the plan’s checks do not ask for one. correction is true where the approver a scheme is waiting on may correct it in its form before signing (api.amend_capex_proposal); where it is false they change only the fields their own level of the workflow names.
Headers
Limiting and Pagination
Limiting and Pagination
Preference
count=none Query Parameters
Filtering Columns
Ordering
Limiting and Pagination
Limiting and Pagination
Response
OK
Note: This is a Primary Key.
Note:
This is a Foreign Key to business_units.id.
60Note:
This is a Foreign Key to depreciation_packs.company_id.
20060Note:
This is a Foreign Key to capex_plans.id.
3Note:
This is a Foreign Key to asset_cost_to_keep.currency_id.
Note:
This is a Foreign Key to department_settings.id.
200200Note:
This is a Foreign Key to capex_calendars.id.
120Note: This is a Primary Key.
20010200200Note:
This is a Foreign Key to capex_invite_candidates.id.
Note:
This is a Foreign Key to entry_currencies.for_site_id.
20012200Note:
This is a Foreign Key to capex_invite_candidates.id.

