Hello Team, 
We are currently importing Contacts in bulk using the Excel Data Import functionality in Creatio. The import process works correctly when using the Contact object.

However, we have a requirement to automatically assign a specific tag to every Contact that is imported.

Could you please confirm the following:

1. Is it possible to assign a tag directly during the Excel data import process?
2. If yes, which object should be used to map the tag?
3. If not, what is the recommended best practice to automatically tag imported Contacts?

Please note that this task is performed by business users (not system administrators), so we are looking for a solution that does not require advanced system-level configuration.

We would appreciate your guidance on the correct approach.

Thank you for your support.

Nikita Pareek

Hi Community,

I’m on Creatio 8.3.2 (Freedom UI) and I’m trying to set the first tab as the default on every page init, because the designer option under Tabs (“Default tab”) isn’t working in my case, so I’m doing it in code.

What I’m doing

I subscribe to the page model events inside crt.HandleViewModelInitRequest and wait for finish-load-model-attributes, then set the tab index to 0:

{
  request: "crt.HandleViewModelInitRequest",
  handler: async (request, next) => {
    await next?.handle(request);
 
    request.$context.events$.subscribe(async (evt) => {
      const modelMode = await request.$context.getPrimaryModelMode();
 
      if (evt?.type === "finish-load-model-attributes") {
        if (modelMode === "update") {
          request.$context.Tabs_SelectedTabIndex_Profile = 0;
        }
        if (modelMode === "create") {
          request.$context.Tabs_SelectedTabIndex_Profile = 0;
        }
      }
    });
  }
}

The problem

This event is emitted more than once (e.g., when another list/detail inside a tab finishes loading later), so my code keeps re-triggering and forces the UI back to tab 0 even after the user already switched tabs.

Unsubscribe attempt (doesn’t work)

I tried the pattern I saw in a comment on the CustomerFX article about waiting for the model to be loaded (store the returned subscription and call unsubscribe() when the needed payload arrives):customerfx​

const sub = request.$context.events$.subscribe(async (evt) => {
  if (evt?.type === "finish-load-model-attributes" && evt?.payload?.SomeAttribute) {
    sub.unsubscribe();
  }
});

But in my case (8.3.2 Freedom UI) this doesn’t seem to work at all.

Questions

• What is the correct syntax / pattern to unsubscribe from request.$context.events$ subscriptions on Freedom UI pages (8.3.2)?
• Does events$.subscribe(...) always return an object that supports unsubscribe() in Freedom UI, or is there a different disposal mechanism?
• Is there a recommended “run once when page is really ready” event/request that avoids finish-load-model-attributes firing multiple times?

If anyone has a working example for 8.3.x (especially for “run once” behavior or proper unsubscribe), I’d really appreciate it.

Hello,

How can I make text search case-insensitive in the Read data element of a business process?

Different third-party systems write the same code using different letter cases, and because of this the business process doesn’t find an already existing record.

Hi Team, we have create a couple of custom workflows using custom objects. We are trying to generate notifications by adding records in notification object. The notifications are working fine but the thumbnails are breaking. Attached is the screenshot. How can we resolve this?

Hi everyone,

I’m building a Freedom UI dashboard based on the Website Form Submission object and need help implementing global interactive filters.

Use case:

• We have filters like Location, Service Type, Form Type, etc.
• These filters should dynamically affect all widgets (metrics and charts) on the page.
• If a filter value is selected → widgets should update accordingly.
• If no filter value is selected → all records should be shown (no filtering applied).

Currently, when using Page Parameters with widget-level filters, if the parameter is empty, the widget returns 0 records instead of showing all data.

What is the recommended way in Freedom UI to implement optional global filters that:

• Affect all widgets
• Ignore empty parameters
• Work reliably for Metric and Chart components?

Should this be handled at the main data source level instead of per widget?