Время создания
Filters
DataVisualization
SyntechPivot
PivotTables
DataAnalytics

We’ve released a new version of Syntech Pivot for Creatio.

What’s new
Features
Year-over-year comparison. Each period can now be compared with the same period a year earlier.

Fixes
Date filters no longer fail on the server. 
Between works as a Between filter. 
Date periods sort chronologically instead of alphabetically, in rows, columns, and lookup-based sorts.
Build and dependencies resolve on Angular 20.

Performance
Every record ceiling is now an explicit parameter, lowered to a small default (50) and exposed in the settings panel: page size, related-source page size and record ceiling, column unique-value limit, filter and condition lookup page sizes, and schema load page size.

Version: 1.6.0
Compatible with: Creatio 8.3.1

Explore Syntech Pivot for Creatio and the latest update on the Marketplace

Like 0

Like

Share

0 comments
Show all comments
Gantt_View_Update
syntech_gantt
New_in_Syntech
syntech

Syntech Gantt View for Creatio 5.2.0 is now available.

This release introduces improvements to labor forecasting, filtering, access control, real-time updates, and Gantt usability.

Base record colors
Pick default bar colors per level - projects, tasks/subtasks, and milestones - used whenever no color column is mapped. Configurable in Settings with a color picker.

Labor Forecast is now a real forecast
ETC hours are spread across the timeline by each task’s date range (start → end) instead of piling onto the start date, so the manpower chart reflects load period by period.

Global filters per schema level
Add fixed filter conditions to any connected level (parent / child / milestone / resources) on top of the record scope — e.g. show only records of a given type. Operators include equals, in-list (multi-value), contains, starts/ends-with, comparisons, and is-empty; lookup columns get a value picker.

Fixes
- Fixed a freeze when typing a date manually (invalid/extreme years are now rejected; timeline generation is capped).
- Milestones can now be deleted - from a row action and from the right-click Edit Schedule dialog.
- Parent tasks now resize both ways to match their children (shrink as well as grow).
- Much smoother dragging of a parent with its children - no more jumping while changes save.
- Milestones no longer disappear when filters are active or related tasks complete.

Access control
Restrict who can edit project (parent) dates via a role multi-select (chips) in Settings.

Real-time updates
Live refresh now updates only the record that changed (not a full reload), is gated per board, and is far lighter on the server (cached, Redis-backed - no DB hit per change).

Settings
Restored the Record column picker (host-record scoping) in the settings menu.

Syntech Gantt View for Creatio is available on Marketplace 

 

Like 0

Like

Share

0 comments
Show all comments
New_in_Syntech
syntech_available
todolist

We’ve released a new update for Syntech To Do List for Creatio, focused on usability, data consistency, accessibility, and performance.

The update addresses several everyday scenarios when working with tasks:
Nothing gets deleted by accident. Pressing Backspace used to delete the task you had selected, with no warning. Deleting now always asks first.
Typing works like typing. In search and other fields, the space bar, Enter and Tab used to act on the task list instead of the text box. Fixed.
Settings are for admins only. The settings panel was visible to everyone and could be overwritten by any user. It is now limited to administrators.
Sorting is correct. Sorting only applied to the tasks already on screen, so the order broke as more loaded. It now sorts the whole list.
What you see is what is saved. If a change could not be saved, the list used to keep showing it anyway. Now it reverts, and load errors are shown instead of an empty list.
Reordering sticks. Dragging tasks into a new order used to reset on refresh.

Syntech To Do List can be embedded into Freedom UI pages and connected to different Creatio entities using no-code configuration. It supports hierarchical tasks, priorities, assignees, due dates, projects, and progress tracking. 

View the app on Creatio Marketplace

#Creatio #CreatioMarketplace #SYNTECH #FreedomUI #TaskManagement

Like 0

Like

Share

0 comments
Show all comments
FreedomUI
CustomComponent
integration
json
marketplace
NCS
FreedomUI_Designer

Hi, Creatio community.

If you work with integrations in Creatio, you know what a REST log looks like stored in a long text field: one unbroken line, no indentation, keys and values blending together. You either copy it to a browser tab to read it, or you squint at the record and try to parse it mentally.

We ran into this constantly while building banking integrations, and at some point we decided to fix it properly.

JSON Viewer for Creatio is a free custom component for Freedom UI that renders any unlimited-length text field containing JSON as an interactive tree: expandable and collapsible nodes, real-time search by key or value, copy to clipboard, and fully configurable colors per data type (keys, strings, numbers, booleans, nulls). Dark and light theme, both configurable from the setup panel in Freedom UI Designer. No code required to drop it on a page.

Where it helps in practice:

  • REST API and webhook logs stored in records: instead of a wall of text, you get a navigable structure.
  • Audit trails saved as JSON: your team can inspect them without leaving the record.
  • External service responses (SAP, OnBase, validation services): readable at a glance, without copy-pasting.
  • Any unlimited-length text field storing JSON, whatever the use case is.

Setup takes a few minutes: install from the Marketplace, add NcsJsonViewer as a dependency in your package, drag the component from the Custom Components section in Freedom UI Designer, and point it at any unlimited-length text field that stores a JSON.

It's free and works on cloud and on-site.

Marketplace: https://marketplace.creatio.com/app/json-viewer-creatio

If you're using it and run into something, let us know here or at support@nocode-services.com. And if you find it useful, a review on the Marketplace goes a long way.

Like 6

Like

Share

1 comments

Light and dark theme, colors per data type (keys, strings, numbers, booleans, nulls), and viewer size, all configurable from the setup panel in Freedom UI Designer.

Show all comments
Restrict_Global_Search_filter/dropdown_where_users_can_select_which_column/field_to_search_on.
Studio_Creatio_enterprise_edition
8.0

Hi everyone,

I have a question regarding the Global Search functionality in Creatio.

In Global Search, there is currently a dropdown/list that allows the user to select the column/field on which the search should be performed.

I would like to customize this behavior so that:

  • The search is always performed on one specific column/field.
  • The user should not be able to select a different column.
  • Ideally, the column-selection dropdown/list should be hidden or removed from the Global Search UI.
  • The existing Global Search functionality should continue to work using only the specified column.

Is there a supported configuration or Freedom UI customization that allows us to fix the Global Search to a particular column and remove the column-selection option?

If customization is required, could someone please suggest the recommended approach or the relevant schema/component that controls this dropdown?

Thanks in advance!

Like 0

Like

1 comments

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.

Show all comments