I completely love the "Live Data Update" option for objects, one of my fav features to be added in Creatio. However, there are many cases where I want to be able to override that behavior and not have the live data update message sent to the UI. For example, if I am doing hundreds of adds/updates in a process, I likely don't want all those updates to go to the UI since that sort of thing can cause a lot of "flickering" and lag for the user that triggered the process as each message is received and the UI loads the data. Another case is where I am loading in a large amount of data from an external source via OData, the user context that the OData connection is using will receive the messages for all the adds/updates. The same for Excel imports, these should have Live Data Update off by default. There are many cases where the Live Data Update feature could cause a negative impact on the system and is unnecessary since it's not something that is for the user.

Please provide a way that the Live Data Update feature can be bypassed/disabled for single (or batch of) transactions for scenarios such as:

1. OData connections
2. Entity object adds/updates
3. Processes - Ideally, as an option for a single Add Data or Modify Data element, or at least as an option for the entire process
4. Excel imports (should be bypassed/disabled by default for these)

Thank you.

Ryan

It would be very useful in having good, consistent reporting to extend the current date macros available for doing so. Currently, if I want to filter to only include the rolling year's values, I have to put in a filter like Date >= Previous days <365> (and another for Date <= Today, if dates can be in the future) but this is quite clunky and not always the most clear (from memory, Previous Days does not include today's date, hence the greater than or equal to).

Even worse is that there is no real way (without doing something like creating a custom date object & maintaining the lookups to it for all objects with a date) to put a filter on to say "show me the last x complete months", with the partial workaround being similar to the above one, but this does not fulfil the "complete months" aspect of the filter.

I would propose the following would be very useful additions to the filtering setup used in folder config, BP read data steps, chart/metric config, list filtering config & other areas that filtering can be set up throughout Creatio:

High priority:

• Previous x for each of the dropdown's sections, so week, month, quarter, except for "Every year"
• Following x for each of the dropdown's sections as above

Nice to have:

• A checkbox/similar on Previous/Following macros to select whether the current day/week/month etc should be included, to both remove the slight ambiguity and give users more control without needing 2 date filters