Send a proposal's row on the consolidated capex plan for approval.
Send a proposal’s row on the consolidated capex plan for approval. Needs finance.capex_consolidation.edit.
A row goes to the first level of its planning workflow by itself when its proposal is approved, and its approvers plan it there; this sends one that no request holds — one no workflow held then, one already on the plan before your organisation published its workflow, or one whose request was withdrawn or could not be carried out. The row must be planned first: refused with PLANNING_INCOMPLETE, naming what is missing in detail.missing, while any of the six mandatory fields is empty, a carry forward lacks its carried cashflow, or the twelve months do not add up to py1_outflow. It is raised in the name of the person who created the proposal. APPROVAL_REQUIRED in error_code means it is waiting on its approvers; when the last level approves, the proposal is PLAN_APPROVED, and a rejection at any level makes it PLAN_REJECTED. Where no workflow applies it is approved at once and proposal_status is PLAN_APPROVED. Refused with PLANNING_DECIDED once the plan is approved or rejected, and ALREADY_SUBMITTED while it is with its approvers.
Headers
Preference
params=single-object Body
Send a proposal's row on the consolidated capex plan for approval. Needs finance.capex_consolidation.edit.
A row goes to the first level of its planning workflow by itself when its proposal is approved, and its approvers plan it there; this sends one that no request holds — one no workflow held then, one already on the plan before your organisation published its workflow, or one whose request was withdrawn or could not be carried out. The row must be planned first: refused with PLANNING_INCOMPLETE, naming what is missing in detail.missing, while any of the six mandatory fields is empty, a carry forward lacks its carried cashflow, or the twelve months do not add up to py1_outflow. It is raised in the name of the person who created the proposal. APPROVAL_REQUIRED in error_code means it is waiting on its approvers; when the last level approves, the proposal is PLAN_APPROVED, and a rejection at any level makes it PLAN_REJECTED. Where no workflow applies it is approved at once and proposal_status is PLAN_APPROVED. Refused with PLANNING_DECIDED once the plan is approved or rejected, and ALREADY_SUBMITTED while it is with its approvers.
Response
OK

