1. Using Pipeline Designer
  2. Managing Threshold Sets
  3. About Threshold Simulator
  4. Edit Simulator Conditions

Edit Simulator Conditions

You can edit Simulator Conditions using the Threshold Manager.

To edit existing simulator conditions for a threshold set, follow these steps:
  1. In the All Thresholds page, select the check box corresponding to the threshold set you want to edit.
  2. Click Simulation History Simulation History icon. The Simulation Details for this threshold set opens as a new tab.
  3. Select the check box corresponding to the Simulation Run ID for the simulation you want to edit.
  4. Click Edit Edit icon. The Edit Simulator Conditions pop-up window displays.
    Alternatively, you can access the Edit Simulator Conditions window by clicking Edit & Simulate in the View Simulator Conditions window.
  5. To make modifications to these conditions, update the following values:
    1. Select one or more Jurisdictions for this threshold set using the drop-down list. Jurisdiction refers to the division of data in the database based on criteria such as geographical boundaries, legal entities, and so on.
    2. Enter the Lookback Period for this threshold set. Lookback period refers to the number of seconds, minutes, hours, or days to lookback from the current date or time to create a time window which is used to consider cases for correlation.
    3. Enter the Frequency Period for this threshold set. Frequency period refers to how frequently the scenario should be run.
    4. Enter the threshold values you want this threshold set to be updated with in the New Value field. Select the Batch Date as the date for the data you want to test the thresholds against. This can be the current date or a past date.
    5. Enter the Data Origin.
  6. Click Save & Simulate to run the modified simulation. After running a simulation, the Simulator History window displays the result with the number of event matches and details of each event. You can view the following details:
    • Simulation ID: ID for this simulation run.
    • Data Origin: Data Origin of the data set the simulated scenario conditions are run against.
    • Jurisdiction: Jurisdiction the simulated scenario conditions are run for.
    • Batch Date: Date the simulated scenario conditions are run for.
    • Results: Number of event matches generated by the simulated scenario conditions during the run.
    • Event Details: Details for each event generated by the simulated scenario conditions during the run.
      • Event ID
      • Focus Name
      • Focus Type
      • Highlights