<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Visual Investigator alerts reopening after workflow execution in Fraud, AML and Security Intelligence</title>
    <link>https://communities.sas.com/t5/Fraud-AML-and-Security/Visual-Investigator-alerts-reopening-after-workflow-execution/m-p/759419#M767</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm using Visual Investigator 10.7 and whenever I close an alert it got active again after the flow execution. In other queues I got it solved (the action of move an alert from one queue to another after flow execution) with priority of strategies and queue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've noticed that when I close it manually by the disposition on PGAdmin it shows alert_status_id = 'CLOSED' and queue_id equals to the queue the alert was before I close it. But everytime flow runs it gets active.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone have any suggestion?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Aug 2021 17:43:03 GMT</pubDate>
    <dc:creator>masiqmoselli</dc:creator>
    <dc:date>2021-08-04T17:43:03Z</dc:date>
    <item>
      <title>Visual Investigator alerts reopening after workflow execution</title>
      <link>https://communities.sas.com/t5/Fraud-AML-and-Security/Visual-Investigator-alerts-reopening-after-workflow-execution/m-p/759419#M767</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm using Visual Investigator 10.7 and whenever I close an alert it got active again after the flow execution. In other queues I got it solved (the action of move an alert from one queue to another after flow execution) with priority of strategies and queue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've noticed that when I close it manually by the disposition on PGAdmin it shows alert_status_id = 'CLOSED' and queue_id equals to the queue the alert was before I close it. But everytime flow runs it gets active.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Anyone have any suggestion?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Aug 2021 17:43:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Fraud-AML-and-Security/Visual-Investigator-alerts-reopening-after-workflow-execution/m-p/759419#M767</guid>
      <dc:creator>masiqmoselli</dc:creator>
      <dc:date>2021-08-04T17:43:03Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Investigator alerts reopening after workflow execution</title>
      <link>https://communities.sas.com/t5/Fraud-AML-and-Security/Visual-Investigator-alerts-reopening-after-workflow-execution/m-p/759453#M768</link>
      <description>&lt;P&gt;So it sounds like your flow is creating a new alert.&amp;nbsp; If you don't think that should be happening you might start checking a few areas.&amp;nbsp; Check your alert score aggregation policy to make sure it represents what you are trying to enable.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN&gt;When the&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="xisDoc-windowItem"&gt;Do not compute a score from the provided activity&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;or&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="xisDoc-windowItem"&gt;Compute the score from the activity in the current alerting event&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;score aggregation policy is selected, the scorecard displays only the scenario-fired events in the current alerting event.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;When the&amp;nbsp;&lt;SPAN class="xisDoc-windowItem"&gt;Compute the score from the unique alerting activity in all the alerting events&lt;/SPAN&gt;&amp;nbsp;score aggregation policy is selected, the scorecard displays all the scenario-fired events in the current alerting event as well as all the unique scenario-fired events in prior alerting events for this alert version.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN&gt;When the&amp;nbsp;&lt;SPAN class="xisDoc-windowItem"&gt;Compute the score from all the activity in all the alerting events&lt;/SPAN&gt;&amp;nbsp;score aggregation policy is selected, the scorecard displays all the scenario-fired events in the current alerting event as well as all the events in prior alerting events for this alert version.&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;From what you said it sounds like the system is finding "new" activity&amp;nbsp;and alerting on it.&amp;nbsp; &amp;nbsp;Example: An alert comes up for Joe Smith and a user dispositions it.&amp;nbsp; That disposition creates a case and closes the alert.&amp;nbsp; That alert only stays closed until new activity that meets the alerting threshold criteria comes into the system.&amp;nbsp; If that isn't what you are wanting in terms of behavior you could look at the alert disposition&amp;nbsp;option to keep the alert suppressed until the score in creases by % or X amount.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3 id="n1fiuqu6nim706n1n0j83o46reas" class="xisDoc-title" tabindex="-1"&gt;Reactivate after a Score Increase&lt;/H3&gt;
&lt;P class="xisDoc-paragraph"&gt;Suppresses the alert and keeps it suppressed unless its score changes. You can specify whether the score must increase by a percentage or by an exact amount. You can indicate that the alert should be reactivated if the score goes above a specified value.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Aug 2021 19:17:19 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Fraud-AML-and-Security/Visual-Investigator-alerts-reopening-after-workflow-execution/m-p/759453#M768</guid>
      <dc:creator>MBergeron</dc:creator>
      <dc:date>2021-08-04T19:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Investigator alerts reopening after workflow execution</title>
      <link>https://communities.sas.com/t5/Fraud-AML-and-Security/Visual-Investigator-alerts-reopening-after-workflow-execution/m-p/759491#M769</link>
      <description>I've tried use the Reactivate after a Score Increase, and even used some high percentages like 100%, but it still Activing alerts that was closed.&lt;BR /&gt;&lt;BR /&gt;About the agregation scenarios, I'm not using it. I'm using the Scenario in row level (think that in english is that way), and I don't have any of the options.</description>
      <pubDate>Wed, 04 Aug 2021 20:12:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Fraud-AML-and-Security/Visual-Investigator-alerts-reopening-after-workflow-execution/m-p/759491#M769</guid>
      <dc:creator>masiqmoselli</dc:creator>
      <dc:date>2021-08-04T20:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: Visual Investigator alerts reopening after workflow execution</title>
      <link>https://communities.sas.com/t5/Fraud-AML-and-Security/Visual-Investigator-alerts-reopening-after-workflow-execution/m-p/759523#M770</link>
      <description>&lt;P&gt;Close Alert and Reactivate After an Increase are separate and distinct disposition actions.&amp;nbsp; If you have Close Alert checked it will invalidate your reactivate option completely.&amp;nbsp; &amp;nbsp;I'd unchecked the Close option if that is the case and try again with the Reactivate and whatever % threshold you felt was appropriate.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Aug 2021 21:26:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Fraud-AML-and-Security/Visual-Investigator-alerts-reopening-after-workflow-execution/m-p/759523#M770</guid>
      <dc:creator>MBergeron</dc:creator>
      <dc:date>2021-08-04T21:26:00Z</dc:date>
    </item>
  </channel>
</rss>

