Hi Nikita,

If you're trying to enforce this validation while the Lead is still in Add mode (new record), there is an important limitation to consider: the user cannot add records into the Product Detail until the main Lead record has been saved at least once. Because of this, making the detail mandatory on the initial save would prevent the user from ever creating the Lead.

If the requirement is instead tied to a specific stage or status transition, a better approach would be to override the save logic (for example using a crt.SaveRecordRequest handler in Freedom UI) and validate whether the Product Detail contains at least one record before allowing the save or stage movement.

Business Rules themselves cannot directly validate whether a Detail/List contains records. A common approach is:

• Use client-side validation in the save request handler, or
• Maintain a hidden boolean/count field updated via Business Process and validate against that field.

Good afternoon,

Thank you for your question.

At the moment, it is not possible to configure a Reports page in Freedom UI using out-of-the-box tools. To recreate this functionality in Freedom UI, custom development would be required.

We have already submitted an idea to the R&D team to consider moving the Reports page to Freedom UI in future releases.

We recommend keeping an eye on the Release Notes and Changelogs in Creatio Academy for any updates.

Thank you for your understanding.

Hello,

1. Case creation
Most likely, the Case is being created because the mailbox is configured in the list of mailboxes used for case registration.

To prevent Cases from being created from this mailbox, you may use one of the following options:

• Remove this mailbox from the corresponding lookup used for case registration.
• Remove the service license from the mailbox owner. In this case, Cases will no longer be created for this mailbox.

2. Preventing duplicate Lead creation
Creatio email threading data includes fields such as MessageId, InReplyTo, and ParentMessageId in EmailMessageData. The MessageId and InReplyTo fields are populated from the email headers during synchronization.

To avoid creating duplicate Leads, we kindly recommend configuring your process so that a Lead is created only when all of the following conditions are met:

Activity type = Email
Mailbox = your mailbox
Subject does not start with Re:, RE:, Fwd:, FW:, or Fw:
InReplyTo is empty
ParentMessageId is empty

This approach should help ensure that Leads are created only from new incoming emails and not from replies or forwarded messages that are part of an existing email thread.

Hello,
Most likely, the participants weren't added because your email was in the "New" state, meaning it wasn't created and still does not have a dedicated ID. In order to connect a contact to an email, an ActivityId should be present.
To make this work, you would need to ensure either that:
- the email activity is already created
- the logic of adding recipients is executed after the record is saved

LÉZORAY Nicolas, you have to read selected rows depending selection state from datagrid on the your modal page. and then fill outbound parameter on the page. then process this collection in process. or process selected contacts (emails) on the modal page and update Activity.To there.

Hello,

Thank you for the detailed explanation and screenshots.

Based on the provided screenshots, I would like to clarify the dependency direction first.

In Creatio, the Depends on Packages section shows the packages that the current package requires. The Dependent Packages section shows the reverse relation — packages that currently depend on the selected package.

According to the screenshots:

mygTicketManagement depends on:
- CrtCore
- UsrCrtCustomer360App_gc1j3ru

UsrCrtLeadOppMgmtApp_rjd5oep depends on:
- several Lead/Opportunity/Customer 360 related packages
- UsrCrtCustomer360App_gc1j3ru
- UsrCrtProductivityApp_6xzsf6
- mygTicketManagement

Therefore, the current dependency chain appears to be:
UsrCrtLeadOppMgmtApp_rjd5oep → mygTicketManagement → UsrCrtCustomer360App_gc1j3ru

From the screenshots, there is no direct circular dependency between mygTicketManagement and UsrCrtLeadOppMgmtApp_rjd5oep, because mygTicketManagement does not depend on UsrCrtLeadOppMgmtApp_rjd5oep.

Regarding your questions:

Can Freedom UI Designer create package dependencies automatically? 
Yes, dependencies can be added when configuration elements in one package reference elements from another package. For example, this may happen when a page, section, business process, object, lookup, data source, or other schema stored in one package uses an object or component from another package.

So if a page or configuration element from UsrCrtLeadOppMgmtApp_rjd5oep references an object, page, detail, lookup, or schema from mygTicketManagement, Creatio may require this package dependency to ensure the correct installation and compilation order.

Is a linear dependency structure a best practice?
A controlled layered structure is recommended, but feature packages should not depend on each other unless this is intentional.

A clean structure would usually look like this: 
Base / Core packages → Shared application packages → Feature packages

For example: CrtCore → Customer360 → TicketManagement

This is acceptable if Ticket Management really uses Account and Contact data from Customer 360.

The recommended structure in your case would be: UsrCrtCustomer360App_gc1j3ru -> mygTicketManagement

And UsrCrtLeadOppMgmtApp_rjd5oep should depend on mygTicketManagement only if Lead/Opportunity functionality intentionally uses Ticket Management components.

At this stage, based on the screenshots, there is no confirmed circular dependency. The main recommendation is to investigate why UsrCrtLeadOppMgmtApp_rjd5oep has a dependency on mygTicketManagement and remove it only after confirming that no active configuration elements still reference Ticket Management components.

Phanumas Liawsakulaphichai,

By default, Creatio now determines which package to save a Freedom UI page into based on the object hierarchy. If you want to force Creatio to use your "Current Package" system setting instead, follow these steps:

1. Access Feature Toggling

Navigate to the feature management page by appending one of these to your Creatio URL:

• /0/flags (Fastest)
• /0/Shell/#Section/AppFeature_ListPage (Freedom UI)

2. Disable the Logic

Locate the following feature code: if not create

Feature-UseSchemaDesignPackageUIdByHierarchy

• Action: Toggle OFF both "Is enabled" and "Is enabled for current user."
• Finalize: Click the Clear cache button.

3. Expected Behavior

Once disabled, the editor will respect your Current Package system setting.

Note: The system will still prioritize a specific package if you:

• Open the page directly from the Application Hub.
• Open the page from a specific package within Configuration.

Best,
Bala.

Hello.

If the package icon is greyed out - , this means that the package is locked.

This can occur if the package was installed on your site or if the package Maintainer differs from the value specified in the Publisher system setting.

At the same time, this does not mean that the package cannot be installed on another site. If the states of the environments are aligned, you can export the package and install it on another site. Please note that in this case the package will also be installed as locked.

There are two options to unlock the package, temporary and permanent.

To remove the lock, you can either use the Unlock for hotfix action to unlock the package temporarily
https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/development-tools/delivery/hotfix-mode , or create a ticket for the support team to unlock the package permanently.

If your package has a lock icon next to it but the package icon itself is yellow , this means that the package is unlocked for changes but locked in SVN.

You can find more information regarding this behavior in the following article.

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/development-tools/creatio-ide/operations-with-packages#title-15340-9

Best regards,
Antonii.

Antonii Viazovskyi,

Thank you

Hi Ignacio Alvarez,

It is not possible to add a custom action to the Timeline component. It is generated dynamically in the application core based on the activity type, and its behavior is hardcoded.

Hi, you can clear DateTime values by setting them to: null

Hubert Pacia,

or you can create a date parameter and leave the value empty. Then use that parameter to populate your date field

Hubert Pacia,

Thank you for help, it works :-)

Hello,

colleagues from Creatio, could you please, share your thoghts?

We use Starfish for this (Starfish ETL | Creatio Marketplace) as there is not direct way other then the API to get data out. I have asked many times to be able to Sync the DB directly, but there is no Option. Starfish works well

Hello,
Currently, you have two options accessing the DB:
1) Using marketplace apps like Starfish
2) Writing direct SQL commands in your code
https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…

Hello,

You can use an Organizational role, add users to that role, and then use the Case page logic to limit who can be selected in Assignee field. 

For the page behavior itself, Creatio supports filtering lookup values with business rules. Here is the instruction: https://academy.creatio.com/docs/8.x/no-code-customization/customization-tools/ui-and-business-logic-customization/freedom-ui-business-rules#2416-4-5

You may also create a business process that is triggered when a case is created. This process can retrieve the required information, including the value of the BU field, and automatically assign the appropriate Assignee based on the corresponding role.