BookmarkSubscribeRSS Feed
agesser
Obsidian | Level 7

Hi all,

We will appreciate your help with the issue:

We have a flow with many scenarios.

Now we would like to change parameters at one of scenarios.

After this we should publish this with new version. (any other options?)

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.

What is the correct solution for this situation?

 

e.g for the scenario:

during the last 7 days the sum of all transaction for account is greater than 1000 USD

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.

Thanks,

Alex.

1 REPLY 1
_austin_
SAS Employee

Hi Alex,

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.

Best regards,

Austin

hackathon24-white-horiz.png

The 2025 SAS Hackathon Kicks Off on June 11!

Watch the live Hackathon Kickoff to get all the essential information about the SAS Hackathon—including how to join, how to participate, and expert tips for success.

YouTube LinkedIn

Discussion stats
  • 1 reply
  • 1379 views
  • 0 likes
  • 2 in conversation