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

Hi,

It would be extremely valuable to allow manual axis limits on charts (Y-axis and/or X-axis), instead of only dynamic scaling.

For example, if a company has a monthly revenue target of 100K, users should be able to:

• Set a fixed Y-axis range (e.g., 0 → 200K),
• Define visual milestones (e.g., 50K, 100K, 150K),
• Add a target line representing the goal.

This becomes critical when comparing performance across periods or segments.

Today, charts automatically rescale based on the data. While convenient, this makes visual comparison unreliable.
For instance:

• Year A: 20K per month
• Year B: 400K per month

Both graphs appear visually similar because each uses dynamic scaling, which defeats the purpose of comparison.

Fixed scaling ensures that:

• Year-over-year comparisons are meaningful
• Multiple product lines or segments can be evaluated consistently
• Performance gaps are immediately visible
• Targets and progress are easier to communicate to stakeholders

Additionally, the ability to add a static target/goal line would significantly improve usability for sales and management dashboards. This is already a standard feature in many tools (e.g., Pipedrive and others for years).

In short, fixed axis controls + target lines would materially improve analytical accuracy and decision-making.

Thank you for considering this enhancement.

Creatio has the ability in charts to set "top N" limits for dashboard widgets like bar and column charts through the code, by modifying the rowCount property (path config > series > data > providing > rowCount) but this property isn't surfaced via the Page Designer UI. This is often a very useful feature, and so it would be good to make it possible to set it via the Page Designer UI to reduce the need to make page code changes.

At the moment, it seems like the Page Designer can quite easily accidentally override the rowCount value by changing small config settings in the graph as well, which is bad for causing regressions. If this were surfaced in the Page Designer, this would presumably resolve this issue too.

Hello

I encountered an issue while uploading corporate branding assets via the Logo Customization feature in SVG format. The system returns the following error message: "Malicious file contents detected, upload canceled."

The SVG file itself is extremely simple. It was created (more precisely, downloaded and recolored) using Inkscape and even subsequently processed through an additional sanitization tool to remove any software-specific stuff. The file successfully passes W3C validation with a "Passed" status and no warnings. The image is rendered correctly by all software tested, including web browsers and various online services.

Unfortunately, I was unable to communicate this issue through the support channel because they think I need consultation or smth (which I absolutely do not). From my perspective, this appears to be a file checker's false positive, which for some reason seems to detect executable content where none exists (or something like that), so I just want to report the issue to devs.

My issue was already solved by using other file format.

The image is in the attached archive (svg uploads isn't supported)
 

Hello. The current implementation of the search field utilizes a "Pattern*" matching strategy (prefix matching), requiring the search term to match the beginning of the string exactly. Searching for a term within the middle of the text (*pattern*) is not supported. 

We suggest implementing an elastic search mechanism for these fields, analogous to the one used for the global search. The introduction of globbing or regular expressions would be highly appreciated.

Sincerely, Alex, Qube-Soft