From fbced36d3d0fc8e52b082af36f59c1b91fb90d1f Mon Sep 17 00:00:00 2001 From: julieschwartz18 <91824591+julieschwartz18@users.noreply.github.com> Date: Thu, 7 Nov 2024 11:17:48 +0200 Subject: [PATCH 1/2] Update mirroring.md minor update based on Richard's review --- docs/integrations/mirroring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/mirroring.md b/docs/integrations/mirroring.md index 6972dcac9..28d78baba 100644 --- a/docs/integrations/mirroring.md +++ b/docs/integrations/mirroring.md @@ -235,7 +235,7 @@ def get_mapping_fields_command(): ``` ## Classification and Mapping with Mirroring -When incoming mirroring happens, the incident goes through both the classifier and the mapper. The classifier sets a specific value for the incident type, and the mapper updates the incident with this value, ensuring that the incident type matches what the classifier determined. +When incoming mirroring occurs, the incident is classified and the mapped. The classifier sets a specific value for the incident type, and the mapper updates the incident with this value, ensuring that the incident type matches what the classifier determined. To prevent the incident type from changing during mirroring: 1. If your integration instance does not fetch incidents, do not set a default incident type, and remove the classifier. 2. Set up a second integration instance without classification that uses the same mapper. From 64a0542f56da066f6c28c02327f5cc6ce581281a Mon Sep 17 00:00:00 2001 From: julieschwartz18 <91824591+julieschwartz18@users.noreply.github.com> Date: Thu, 28 Nov 2024 09:49:24 +0200 Subject: [PATCH 2/2] Update mirroring.md tiny correction --- docs/integrations/mirroring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/mirroring.md b/docs/integrations/mirroring.md index 28d78baba..8409e78f7 100644 --- a/docs/integrations/mirroring.md +++ b/docs/integrations/mirroring.md @@ -235,7 +235,7 @@ def get_mapping_fields_command(): ``` ## Classification and Mapping with Mirroring -When incoming mirroring occurs, the incident is classified and the mapped. The classifier sets a specific value for the incident type, and the mapper updates the incident with this value, ensuring that the incident type matches what the classifier determined. +When incoming mirroring occurs, the incident is classified and then mapped. The classifier sets a specific value for the incident type, and the mapper updates the incident with this value, ensuring that the incident type matches what the classifier determined. To prevent the incident type from changing during mirroring: 1. If your integration instance does not fetch incidents, do not set a default incident type, and remove the classifier. 2. Set up a second integration instance without classification that uses the same mapper.