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

It would be a very useful feature for both developers and users in list views to be able to see the underlying field name (and path to the field, in cases of forwards references) of a column. Currently, for regular columns (not aggregations) you can only see the current name of the column as set up by the developer or the user, if they've customised the name. But this hides information about where that value is actually coming from, making it harder to understand the origin of the data, for example if the user wanted to set up folder filters where they would have to be using the field names in the actual object configuration.

At the moment, this is the only information visible to users for a basic list column's properties, which could have been renamed by either a developer or the user themselves:

Currently, as a developer I need to check in the dev tools' network tab to get the column name and path in the request, then check the object's configuration to find what that field is captioned with. Or check in the page's code to find the configuration that was set up. Neither of these are very user friendly.

Ideally, the properties popup would be enriched with information about the origin of the data similar to what you would see when setting up a dynamic folder as can be seen here:

It would be very useful for many scenarios to be have the "old" (pre-change) values passed into Business Processes triggered by either data updates or deletions. This is possible to get when using Entity Event Listeners, so it seems like the data should be readily available to Business Processes without much overhead, and would unlock a lot of abilities to do via no-code tools that currently are only achievable using C# code or workarounds.

The way I see it working is that the triggered start would be passed in every field value of the old record, which the user could use in the process in the same way users can currently the Id of the changed/deleted record.

Use cases that I've come across:

1. Updating permissions to revoke permissions granted based on the record's old value (currently would either have to be done via code or by revoking all permissions and re-granting the specific ones, which in complicated permissions setups can be very costly to perform and can potentially lead to issues)
2. Sending updates to external systems about the removal of data
3. Updating an automatically-set field that can also be modified by a user directly to see if the old value was automatically set or manually set by the user (by checking if the value matches the automatic construction using the old data)
4. Checking time differences between events without having to build a completely separate logging table

I'm sure there are many more use cases that the community could provide too, as this is a problem I often face and have to find workarounds for or go through the process of creating an Entity Event Listener.

A few Creatio Community posts requesting similar functionality:

• https://community.creatio.com/questions/how-read-pre-change-values-business-process
• https://community.creatio.com/questions/compare-product-price-value-and-after-update
• https://community.creatio.com/questions/read-old-column-value-bp

Hello everyone, 

I would like to suggest adding a "Feedback" button directly on Academy pages. 

As a simple example of the kind of issue this would help surface: The Academy article "Add a campaign" (Creatio 8.3+) contains hyperlinks redirecting to Academy Articles intended for Creatio Version 7.18, as well as completely different articles being referenced for "Campaign Diagram" within the body (-> Campaign element reference, 7.18) and the bottom section (-> Set up campaign diagram, 8.3) of the Article.

Currently, the only way known to me to report issues or suggestions is to leave the Academy page and send a separate email to Creatio Support manually - a step that likely discourages many users from contributing.

An in-page feedback option would lower that barrier significantly and make it much easier for users to flag such issues, ultimately benefiting both the community and the Academy team.

Best,
David