Hi,

Thank you for the detailed question. Here are answers to each point, followed by the approach we recommend.

1. Is there a supported way to enable a legend for a doughnut chart?

Unfortunately, no. This is a current platform limitation, not a setting the Freedom UI Designer is missing.

• The Show legend option is available only for Spline, Line, Bar, Area, Column and Scatter charts. Pie and doughnut charts don’t support a legend.
• If you add a legend setting to the doughnut series by editing the page schema, the page saves it, but no legend appears. The chart turns off the legend for pie, doughnut, funnel and waterfall charts.
• You can’t set slice colors either. The series color property is ignored for doughnut charts, and slices take their colors from the built-in palette.

What doughnut charts do show is a “label – NN%” data label next to each slice by default. Long labels wrap. Labels that would overlap are hidden, so very small slices may have no label. The dataLabel.display setting has no effect on doughnut charts.

2. Can a custom legend be added with client-side code?

Yes, as a separate element placed directly under the chart. It can’t be drawn inside the chart, because the chart is a single <canvas> with no extension point for that. This approach leaves the chart widget unchanged, so drilldown, tooltips, data labels and keyboard navigation keep working.

3. How can I get the chart’s labels, values and colors?

Labels and values. When a chart series gets its data through the standard data source (data.providing), the platform creates a page attribute named <ChartElementName>_SeriesData. For example, a chart element named MyDoughnut gets MyDoughnut_SeriesData. The attribute holds one array per series, and each item looks like this:

{
  grouping:    { value, displayValue }, // displayValue is the slice label
  aggregation: { value }                // value is the slice value
}

Please keep in mind:

• The platform generates this attribute and it isn’t part of the documented API, so it may change in future versions.
• It’s created only when the chart element has no explicit seriesData binding.
• It’s filled asynchronously, so await it. It holds empty arrays until the data has loaded.

Colors. No API returns the colors the chart draws. Doughnut slices take colors from the built-in palette by slice index, starting again after the last color:

#0058EF, #F9307F, #08857E, #F86700, #4F43C2, #20A959, #009DE3, #FF4013, #B87CCF, #22AC14,
#247EE5, #FF602E, #9641A9, #0B6A32, #E00022, #1566B9, #BE1B5A, #7848EE, #0D2E4E

A legend that uses this list matches the chart today. The palette is an internal detail, though, so check the legend after upgrades.

Order. If the chart has a sort order (seriesOrder), sort your legend items the same way before assigning colors. Otherwise the colors won’t match the slices.

4. Is there a supported API to get the chart instance?

No. @creatio-devkit/common has no API that returns a page element’s component or the underlying Chart.js instance. The chart widget exposes only its configuration inputs, and clicks on the chart are handled inside the widget without reaching the page.

Reading the Chart.js instance from the component or the DOM depends on internal details, and we don’t recommend it. Chart.getChart(canvas) usually doesn’t work from custom code anyway. Custom code loads its own copy of Chart.js, which doesn’t know about the chart the widget created.

Recommended approach

Add a legend element under the chart and leave the chart widget as it is. There are three options, from simplest to most flexible.

Option 1. Text legend with a label (no custom component)

Add a crt.Label under the chart and fill it from a handler:

viewConfigDiff: /**SCHEMA_VIEW_CONFIG_DIFF*/[
  {
    "operation": "insert",
    "name": "MyDoughnutLegend",
    "values": {
      "type": "crt.Label",
      "caption": "$MyDoughnutLegendText",
      "labelType": "body",
      "visible": true
    },
    "parentName": "<container that holds MyDoughnut>",
    "propertyName": "items",
    "index": 1
  }
]/**SCHEMA_VIEW_CONFIG_DIFF*/,
viewModelConfigDiff: /**SCHEMA_VIEW_MODEL_CONFIG_DIFF*/[
  {
    "operation": "merge",
    "path": ["attributes"],
    "values": {
      "MyDoughnutLegendText": {}
    }
  }
]/**SCHEMA_VIEW_MODEL_CONFIG_DIFF*/,
handlers: /**SCHEMA_HANDLERS*/[
  {
    request: "crt.HandleViewModelAttributeChangeRequest",
    handler: async (request, next) => {
      if (request.attributeName === "MyDoughnut_SeriesData") {
        const seriesData = await request.$context.MyDoughnut_SeriesData;
        const items = seriesData?.[0] ?? [];
        request.$context.MyDoughnutLegendText = items
          .map(item => `${item.grouping.displayValue}: ${item.aggregation.value}`)
          .join("  |  ");
      }
      return next?.handle(request);
    }
  }
]/**SCHEMA_HANDLERS*/,

This option can’t show colored markers. Please check on your Creatio version that the change request fires for the generated attribute.

Option 2. Legend with colored markers (custom view element)

Create a small Angular component in a remote module (see “Develop a custom UI component using remote module” on Creatio Academy):

import { Component, Input, ViewEncapsulation } from '@angular/core';
import { CrtInput, CrtViewElement } from '@creatio-devkit/common';

const PALETTE = [
  '#0058EF', '#F9307F', '#08857E', '#F86700', '#4F43C2', '#20A959', '#009DE3',
  '#FF4013', '#B87CCF', '#22AC14', '#247EE5', '#FF602E', '#9641A9', '#0B6A32',
  '#E00022', '#1566B9', '#BE1B5A', '#7848EE', '#0D2E4E'
];

interface LegendItem {
  label: string;
  value: unknown;
}

@Component({
  selector: 'usr-chart-legend',
  template: `
    <div class="usr-legend">
      <span *ngFor="let item of legend; let i = index" class="usr-legend-item">
        <i [style.background]="color(i)"></i>{{ item.label }} ({{ item.value }})
      </span>
    </div>`,
  styles: [`
    .usr-legend { display: flex; flex-wrap: wrap; gap: 8px 16px; justify-content: center; }
    .usr-legend-item { display: inline-flex; align-items: center; }
    .usr-legend-item i { width: 10px; height: 10px; border-radius: 50%; margin-right: 6px; }
  `],
  encapsulation: ViewEncapsulation.Emulated
})
@CrtViewElement({
  selector: 'usr-chart-legend',
  type: 'usr.ChartLegend'
})
export class UsrChartLegendComponent {
  public legend: LegendItem[] = [];

  @Input()
  @CrtInput()
  public set items(value: any) {
    Promise.resolve(value).then(data => {
      this.legend = (data?.[0] ?? []).map((item: any) => ({
        label: item.grouping?.displayValue,
        value: item.aggregation?.value
      }));
    });
  }

  public color(index: number): string {
    return PALETTE[index % PALETTE.length];
  }
}

Register the component in the remote module the standard way. Then place it under the chart on the Freedom UI page:

{
  "operation": "insert",
  "name": "MyDoughnutLegend",
  "values": {
    "type": "usr.ChartLegend",
    "items": "$MyDoughnut_SeriesData"
  },
  "parentName": "<container that holds MyDoughnut>",
  "propertyName": "items",
  "index": 1
}

Option 3. Load the legend data yourself (fully supported API)

If you don’t want to depend on the generated _SeriesData attribute, load the same aggregated data with sdk.Model. Pass the result to the label from Option 1 or the component from Option 2:

const model = await sdk.Model.create("Account");
const rows = await model.load({
  attributes: [
    { name: "Industry", path: "Industry" },
    {
      name: "Count",
      path: "Id",
      type: "function",
      functionConfig: {
        type: "aggregation",
        aggregation: "Count",
        aggregationEval: "all"
      }
    }
  ],
  parameters: [
    /* the same filters the chart uses */
  ]
});

Use the same grouping column, filters and sort order as the chart so the legend rows match the slices.

Limitations

• A custom legend doesn’t react to the chart’s interactive state, such as a hovered or drilled-down slice.
• The color palette and the <ChartElementName>_SeriesData attribute are internal details that may change in future versions. Please check the legend after upgrades.

Registering the idea

We agree that a built-in legend for pie and doughnut charts would be useful, and adding one needs a platform change. Please send this idea to support@creatio.com so it’s registered with the R&D team and considered for the product roadmap. Including your use case, such as “legend below the doughnut chart with series colors and labels”, will help us prioritize it.

Hi,

The column-selection dropdown is not part of Global Search — it belongs to the crt.SearchFilter ("Search") component on Freedom UI list pages. Real Global Search (the shell header box → GlobalSearchResultPage) has no column selector at all, only a section filter, and nothing configurable changes that. There is no supported switch (feature, system setting, or designer property) that pins the list search to one column or hides the selector — but it can be done declaratively in the page schema, no custom handler needed.

Recommended customization (Creatio 8.3.4+ / 10.x)

In the list page schema (Freedom UI Designer → source code, or the package schema), e.g. Contacts_ListPage / your Usr…_ListPage. Example pins search to Email:

viewConfigDiff — merge into the existing element:

{
  "operation": "merge",
  "name": "SearchFilter",
  "values": {
    "columnsGroupsConfig": { "columnsGroups": [] },
    "_filterOptions": {
      "expose": [{
        "attribute": "SearchFilter_Items",
        "converters": [{ "converter": "crt.SearchFilterAttributeConverter", "args": ["Items"] }]
      }],
      "from": ["SearchFilter_SearchValue", "SearchFilter_FixedColumnsGroups"]
    }
  }
}

viewModelConfigDiff (or viewModelConfig.attributes if the schema uses that form — they are mutually exclusive):

{
  "operation": "merge",
  "path": ["attributes"],
  "values": {
    "SearchFilter_FixedColumnsGroups": {
      "value": [{
        "group":   { "name": "Items", "caption": "Items" },
        "columns": [{ "name": "Email", "caption": "Email" }]
      }]
    }
  }
}

Why it works: a truthy columnsGroupsConfig in the schema makes the preprocessor skip its own binding; with zero columns showColumnsGroups is false, so the icon is never rendered and the component/handler paths tolerate empty groups. The exposed SearchFilter_Items attribute now derives from the constant groups, so every search builds a filter over exactly Email, and the Items data source reloads (loadOnChange). Creatio itself ships a literal columnsGroupsConfig on ConfActivityLog_ListPage, so the pattern is supported metadata, not a hack.

Gotchas (each verified):

• Use exactly {"columnsGroups": []} — an empty {} throws in showColumnsGroups.
• group.name must equal the converter arg / grid items attribute (Items on standard section pages; on other pages check the page's existing _filterOptions, e.g. AddressList). A wrong group name silently disables filtering; a wrong column name yields zero rows.
• Column must be a text/lookup/numeric column of the entity; it does not need to be displayed in the grid.
• Every attribute listed in from must exist, otherwise SearchFilter_Items never emits.

8.3.0 (and earlier 8.x): the preprocessor overwrites columnsGroupsConfig unconditionally unless the schema also defines valueChange. Add to the same merge:

"valueChange": {
  "request": "crt.SearchFilterColumnsGroupsRequest",
  "params": {
    "value": "@event.value",
    "searchFilterColumnsGroups": "@event.columnsGroups",
    "searchFilterGroups": [{ "filterAttributeName": "SearchFilter_Items", "viewAttributeName": "Items" }],
    "searchValueAttributeName": "SearchFilter_SearchValue",
    "searchFilteredColumnAttributeName": "SearchFilter_SearchFilteredColumn",
    "searchFilteredColumnsGroupsAttributeName": "SearchFilter_FilteredColumnsGroups"
  }
}

Lighter alternative if hiding isn't required: keep the default _filterOptions and set a literal columnsGroupsConfig with one group/one column (+ "primaryColumnName": "Email"). The icon stays, but the menu offers only that column (the "All" option needs >1 column).

If you really mean Elasticsearch Global Search

No per-query column choice exists anywhere in the stack (GlobalSearchService.Search(queryString, sectionEntityName, …)). The only column-level control is the GlobalSearchIndexedDataConfig system setting (exclude schemas/columns from indexing; needs re-indexing) plus relevance settings GlobalSearchDefaultEntityWeight, GlobalSearchDefaultPrimaryColumnWeight, UseInexactGlobalSearch, GlobalSearchShouldMatchPercent (Global search). Restricting it to one column would mean excluding every other column from the index — technically possible, not a UI option.

There is some info in this thread about overriding the widget click behaviour here, though it does rely on using the widget's ID to some extent: https://community.creatio.com/questions/disable-crtindicatorwidget-link-list

Not sure exactly how your widgets are being generated dynamically, but perhaps there would be some way of identifying the widget clicked & passing that into the handler described in that comment thread.

The key is the type of container the fields are in. If you use a flex row/column container it will collapse unused rows/columns For your case, I think you just need to make the columns less wide. For this you could try adding more columns (click the container the fields are in an change columns from 2 to something like 4?)

Ryan

Hello,
As Ryan said, it's all about the containers. For example, in the flex container, there is a "Space between" setting.
When arranging components within a flex container on the Contacts page using the "Space between" setting, the space between components becomes automatic, and the "Gap" setting has no visible effect. 
The "Space between" alignment setting evenly distributes all available space between flex container components.
With this mode, the system automatically calculates and applies the maximum possible space between each inserted element, so the manual "Gap" configuration is ignored.
The effect is dynamic: adding more components will automatically narrow the space between them, keeping spacing equal across all elements.
If precise control over spacing and sizing is required, use the Grid component. Grid layouts allow you to specify the number of columns and offer finer control over element arrangement.

Overriding the crt.LoadDataRequest and adding an additional filter (if some boolean attribute is set to true, which your button clicking should toggle) is probably your best bet. Instructions on adding a filter to the LoadDataRequest can be found here: https://customerfx.com/article/dynamically-filtering-a-lookup-on-a-creatio-freedom-ui-page/

Note: this will work if and only if the filter never needs to be applied on initial loading of the page, as Creatio bypasses the LoadDataRequest when loading in the first page of results for a list. It's quite annoying and the workarounds are quite messy. But it sounds like it should work for your purposes if you only want to apply the filter after clicking a button.

Hello,

Couldy you clarify, is this happening with the out-of-the-box Twilio integration in Creatio, or are you using a Twilio connector from the Marketplace? 

If this is out-of-the-box (OOB) Creatio functionality and the matching is failing despite correct, clean phone number data please write to support@creatio.com with a full description (including sample Contact record, the inbound SMS log/number, and screenshots), so the team can investigate.

If this is a Twilio connector from the Creatio Marketplace that was built by a third-party publisher - the matching logic in that case is maintained by the app's own author, not Creatio. Please reach out to that publisher's support channel directly (usually listed on the Marketplace listing page) for a fix or workaround.

Hello,

The User Session object is available in Object Permissions, just make sure to use filter by all objects:

Mira Dmitruk,

Thank you!

Hello,
Theoretically, it is possible, you need to create your own module as a copy of ModuleSectionEnums and inside add a new color. Then you need to override BaseSectionMainSettings and put your new module there instead of ModuleSectionEnums. It should be said, that there are no cases of someone doing it, therefore, it cannot be guaranteed that it will work. Nonetheless, there already exists a problem for the R&D team about the possibility of adding custom colors, but it is still unclear when it will be implemented.

Hello.

Please use the following formula:
([#System variable.Current Time and Date#].AddDays(1 - [#System variable.Current Time and Date#].Day)).AddDays([#EnteredParameter#] - 1)

Where #EnteredParameter# is the value provided by the user.

This formula takes the current date, resets it to the first day of the current month, and then adds the number of days based on the entered parameter. As a result, it sets the desired day within the current month, while preserving the current time according to your requirements.

Best regards,
Antonii.

After fooling' around with different functions, DateTime.Parse() actually works for my use case too. withe MM/dd/YYYY format. I am able to use my parameters with the .ToString() to create the date I need.

So what I did was:

DateTime.Parse(([#System variable.Current Date#].Month).ToString()+"/'+[#User input day of month parameters#].ToString()+"/'+([#System variable.Current Date#].Year).ToString())