Batch Update Budget Planning Scenario Status

post

/api/restapi/budgetPlanningScenario/batchUpdateScenarioStatus

Send a request to this endpoint to update status of Budget Planning Scenarios. An application object with an ID value that matches the ID value provided in the JSON object in the request body will be updated to reflect the JSON contents.

Request

There are no request parameters for this operation.

Supported Media Types
Request Body - application/json ()
Root Schema : List<ApiEntityScenarioStatus>
Type: array
Title: List<ApiEntityScenarioStatus>
Show Source
  • ApiEntityScenarioStatus
    Title: ApiEntityScenarioStatus
    This entity represents a ScenarioStatus object, a unique ScenarioStatus object can be identified by the following combinations of the fields.
    • scenarioId
    • scenarioName,planPeriod,portfolioId
    • scenarioName,planPeriod,portfolioName,workspaceCode
Nested Schema : ApiEntityScenarioStatus
Type: object
Title: ApiEntityScenarioStatus
This entity represents a ScenarioStatus object, a unique ScenarioStatus object can be identified by the following combinations of the fields.
  • scenarioId
  • scenarioName,planPeriod,portfolioId
  • scenarioName,planPeriod,portfolioName,workspaceCode
Show Source
  • The period during which budget is allocated to projects within the plan.
    This value determines the year in which budget planning timescales start.
    You can set the planning period to either the current or following year. For example, if the year is 2020 the latest planning period you can set is 2021.
    After the planning period for a budget plan has been set it cannot be changed.
  • The system-generated identifier of the Capital Portfolio.
  • Minimum Length: 1
    Maximum Length: 255
    The name of the portfolio.
  • The system-generated identifier of the Budget Plan Scenario.
  • Maximum Length: 255
    The name of Budget Plan Scenario.
  • Allowed Values: [ "APPROVED", "UNDER_REVIEW", "IN_PLANNING", "UNDER_APPROVAL", "RETIRED", "SHARED", "PENDING_APPROVAL", "PENDING_SHARED", "PENDING_IN_PLANNING" ]
    The status of Budget Plan Scenario.
  • Maximum Length: 60
    The user-specified identifier of a workspace.
Examples

Back to Top

Response

Supported Media Types

200 Response

Successful operation
Body ()
Root Schema : List<ApiEntityScenarioStatus>
Type: array
Title: List<ApiEntityScenarioStatus>
Show Source
  • ApiEntityScenarioStatus
    Title: ApiEntityScenarioStatus
    This entity represents a ScenarioStatus object, a unique ScenarioStatus object can be identified by the following combinations of the fields.
    • scenarioId
    • scenarioName,planPeriod,portfolioId
    • scenarioName,planPeriod,portfolioName,workspaceCode
Nested Schema : ApiEntityScenarioStatus
Type: object
Title: ApiEntityScenarioStatus
This entity represents a ScenarioStatus object, a unique ScenarioStatus object can be identified by the following combinations of the fields.
  • scenarioId
  • scenarioName,planPeriod,portfolioId
  • scenarioName,planPeriod,portfolioName,workspaceCode
Show Source
  • The period during which budget is allocated to projects within the plan.
    This value determines the year in which budget planning timescales start.
    You can set the planning period to either the current or following year. For example, if the year is 2020 the latest planning period you can set is 2021.
    After the planning period for a budget plan has been set it cannot be changed.
  • The system-generated identifier of the Capital Portfolio.
  • Minimum Length: 1
    Maximum Length: 255
    The name of the portfolio.
  • The system-generated identifier of the Budget Plan Scenario.
  • Maximum Length: 255
    The name of Budget Plan Scenario.
  • Allowed Values: [ "APPROVED", "UNDER_REVIEW", "IN_PLANNING", "UNDER_APPROVAL", "RETIRED", "SHARED", "PENDING_APPROVAL", "PENDING_SHARED", "PENDING_IN_PLANNING" ]
    The status of Budget Plan Scenario.
  • Maximum Length: 60
    The user-specified identifier of a workspace.

400 Response

Invalid input for the Budget Planning Scenario service. Verify the request contains valid data, then resubmit the request.
Back to Top