EventAnalytics Time Correlation Rules

Hi,

Trying to write an EventAnalytics rule using TimeCorrelation (in M3 cloud) to limit the BODs generated. However, facing issues of in-consistent behavior (in terms of time delay) when events are released for processing. Writing these rules for both CREATE and UPDATE operation of the same M3 table. Noticed that there are no std BODs available using TimeCorrelation for CREATE operation. Hence,

1) Is there any limitation for using TimeCorrelation for CREATE operation?

2) In cloud is there any default time taken by the system overriding the time we have defined in the rule?

TIA!

Find more posts tagged with

Accepted answers

All comments

Maxime Richard

Hello,

1) You can use it with CREATE operation but it has non sense as a record creation happens once

2) Default time = 2 minutes window. M3 does not take into account parameter "delayTime" in your EA rule (compared to on-premise)

Legacy Contributor

Hi,

Thanks for the reply! However, I've noticed that events also get released before the 2 minutes window sometimes. Also, doesn't it reset the time counter ? (often it doesn't)

Wichtige Hinweise zur PROFILE Donglelizenzierung.pdf

Maxime Richard

I think it's a window, not a timer. It means that you may wait up to 2 minutes before your event is released. But it can be released before 2 minutes, if your event is triggered in a middle of a window.

Legacy Contributor

Oh! that makes sense In this case I guess all events having TimeCorrelation is released together for processing. Is it possible to know or monitor this window or is it in sync with any timezone?

Thanks a lot!

Copyright © 2025 Infor. All rights reserved.