Add the impacted area

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 1 min. de leitura

    • Add an impacted area or an object to the operational vulnerability record in the Operational Resilience Workspace.

    Antes de Iniciar

    Role required: sn_oper_res.manager

    Por Que e Quando Desempenhar Esta Tarefa

    When an impacted area is added for the vulnerability, its state is updated to New (In progress) as shown on the Overview tab of the vulnerability record.

    Beginning with Release 20.1.x, the Operational Resilience application supports the latest Common Service Data Model (CSDM). The enhanced functionality supports the roll up of the dependencies.

    Procedimento

    1. Navigate to Workspaces > Operational Resilience Workspace > All Operational Vulnerabilities.
    2. Open the vulnerability for which you want to add an impacted area.
    3. Select New.
    4. On the Impacted area form, fill in the fields.
      To view more information on the fields, see the Impacted area form.
    5. Select Save.

      When you add the primary origin of the operational vulnerability, its impacted areas with upstream entities are updated on the Impacted areas tab.

      Impacted areas with upstream entities.

      When the scheduled job is executed, the updated impacted areas and the overall operational vulnerability count are reflected in the dashboard.

      Count 0.

      For example, when the impacted areas in the operational vulnerability are updated, the operational vulnerability count on the overview page of SO1 remains at 0 before the scheduled job runs.

      Count 1.

      After running the scheduled job, the operational vulnerability count on the overview page of SO1 is updated to 1. This ensures that the updated data is promptly reflected on the Operational Resilience dashboard.