Batch Update Monte Carlo Settings

put

/api/restapi/monteCarloSettings/batch

Send a request to this endpoint to update one or more Monte Carlo settings. For each JSON object provided in the request body, an application object with a matching ID value 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<ApiEntityMonteCarloSettingsInput>
Type: array
Title: List<ApiEntityMonteCarloSettingsInput>
Show Source
Nested Schema : ApiEntityMonteCarloSettingsInput
Type: object
Title: ApiEntityMonteCarloSettingsInput
Show Source
  • Allowed Values: [ "PROJECT_ONLY", "MILESTONE_LOE", "ALL" ]
    Determines the activities that are included in the risk analysis results. Selecting all the activities will increase the risk analysis time.
  • The number of iterations for which the mean plan finish date must remain constant to be considered converged.
  • The maximum percentage deviation at which analysis results are considered converged.
  • Controls whether the risk analysis includes risks with a status of Proposed.
  • The number of iterations run during the risk analysis.
  • The unique identifier of a set of Monte Carlo settings.
  • The value (0% to 100%) to be used to calculate optimistic percentiles.
  • The value (0% to 100%) to be used to calculate pessimistic percentiles.
  • Minimum Length: 1
    Maximum Length: 60
    The unique identifier for a project set by the user who created the project.
  • The unique identifier of a project.
  • Defines the number to be used to set the starting point for the random number generator.
  • Read Only: true
    Deprecated. As of 23.6, replaced by 'scheduleCost'.
    Select this option to run a risk analysis where activity costs vary for each iteration. This will increase the risk analysis time. If this option is not selected, the activity costs will remain fixed for each iteration.
  • Allowed Values: [ "PRE_MITIGATED", "POST_MITIGATED", "BOTH" ]
    The type of risk analysis run on a project.
    • PRE_MITIGATED : A quantitative risk analysis that doesn't take into account the impact of defined risk response plans.
    • POST_MITIGATED : A quantitative risk analysis that takes into account the impact of defined risk response plans.
    • BOTH : A quantitative risk analysis that uses both pre and post mitigated contexts.
  • Read Only: true
    Deprecated. As of 23.10.
    Setting to tell the monte carlo job to run mean impacts.
  • Select this option to run a risk removal impact analysis on the project. A risk removal impact analysis measures and ranks the potential impact of each risk on the cost and completion date of the entire project.
  • Read Only: true
    Allowed Values: [ "UNIFORM", "TRIANGLE", "SINGLE_POINT" ]
    Deprecated. As of 23.10.
    Acts as a placeholder for type of distribution , Triangle , Uniform etc in case the schedule or cost impacts don't have their own distribution defined.
  • Select this option to run a risk analysis where activity costs vary for each iteration. This will increase the risk analysis time. If this option is not selected, the activity costs will remain fixed for each iteration.
  • Read Only: true
    Deprecated. As of 23.10.
    Date when the record was last updated.
  • Controls whether convergence is used to automatically determine when enough iterations have been run during the risk analysis. As a risk analysis is performed, the results begin to converge to such an extent that there is no point running the analysis any further because the results are only changing by a small percentage. At this point, the analysis has converged and is automatically stopped. If this option is selected, the analysis is run until the convergence criteria that have been set up are met.
  • Minimum Length: 0
    Maximum Length: 60
    The user-specified identifier of a workspace.
Back to Top

Response

204 Response

Successful operation with no content.

400 Response

Invalid input for the Monte Carlo Settings service. Verify the request contains valid data, then resubmit the request.
Back to Top