<?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 Re: VI 10.8 generating alerts after a new version of flow in Fraud, AML and Security Intelligence</title>
    <link>https://communities.sas.com/t5/Fraud-AML-and-Security/VI-10-8-generating-alerts-after-a-new-version-of-flow/m-p/953770#M1069</link>
    <description>&lt;P&gt;Hi Alex,&lt;/P&gt;
&lt;P&gt;We do not have a way to prevent that situation today. We have discussed letting users choose whether the change they are saving is a "minor" change, which would not invalidate history, or a "major" change, which would act like the system does today - resetting the deduplication process. I don't have a timeline for that feature though.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Austin&lt;/P&gt;</description>
    <pubDate>Mon, 16 Dec 2024 23:21:10 GMT</pubDate>
    <dc:creator>_austin_</dc:creator>
    <dc:date>2024-12-16T23:21:10Z</dc:date>
    <item>
      <title>VI 10.8 generating alerts after a new version of flow</title>
      <link>https://communities.sas.com/t5/Fraud-AML-and-Security/VI-10-8-generating-alerts-after-a-new-version-of-flow/m-p/953407#M1065</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;
&lt;P&gt;We will appreciate your help with the issue:&lt;/P&gt;
&lt;P&gt;We have a flow with many scenarios.&lt;/P&gt;
&lt;P&gt;Now we would like to change parameters at one of scenarios.&lt;/P&gt;
&lt;P&gt;After this we should publish this with new version. (any other options?)&lt;/P&gt;
&lt;P&gt;And it means that the alerts will jump again as change of version generate the same alert we are running even the message is the same.&lt;/P&gt;
&lt;P&gt;What is the correct solution for this situation?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;e.g for the scenario:&lt;/P&gt;
&lt;P&gt;during the last 7 days the sum of all transaction for account is greater than 1000 USD&lt;/P&gt;
&lt;P&gt;so today we checked this and generated alert, tomorrow this is tomorrow and 7 days back giving the same result , same message - so no alert. with the version changed it will raise alert again and we want to prevent this situation.&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Alex.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Dec 2024 16:25:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Fraud-AML-and-Security/VI-10-8-generating-alerts-after-a-new-version-of-flow/m-p/953407#M1065</guid>
      <dc:creator>agesser</dc:creator>
      <dc:date>2024-12-12T16:25:43Z</dc:date>
    </item>
    <item>
      <title>Re: VI 10.8 generating alerts after a new version of flow</title>
      <link>https://communities.sas.com/t5/Fraud-AML-and-Security/VI-10-8-generating-alerts-after-a-new-version-of-flow/m-p/953770#M1069</link>
      <description>&lt;P&gt;Hi Alex,&lt;/P&gt;
&lt;P&gt;We do not have a way to prevent that situation today. We have discussed letting users choose whether the change they are saving is a "minor" change, which would not invalidate history, or a "major" change, which would act like the system does today - resetting the deduplication process. I don't have a timeline for that feature though.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Austin&lt;/P&gt;</description>
      <pubDate>Mon, 16 Dec 2024 23:21:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Fraud-AML-and-Security/VI-10-8-generating-alerts-after-a-new-version-of-flow/m-p/953770#M1069</guid>
      <dc:creator>_austin_</dc:creator>
      <dc:date>2024-12-16T23:21:10Z</dc:date>
    </item>
  </channel>
</rss>

