Hello,

In Creatio, signals are event-driven triggers used to start business processes when a particular event occurs on an object, typically the addition, update, or deletion of a record. When a process contains a signal element, it essentially subscribes to a specific system event. When that event is raised, Creatio evaluates all matching subscriptions and initiates the corresponding processes.

In the case where several processes need to respond to changes on the same object but based on different business tasks (such as changes to specific fields), there are generally two architectural approaches. One is to define separate business processes, each with its own signal element. These processes start independently whenever the triggering event occurs and include internal logic to determine if they should proceed based on the field changes. The other is to design a single process with a more general signal and then route the execution flow internally, either through conditional logic or by invoking subprocesses depending on which fields were modified.

Both methods are valid and widely used in different Creatio implementations. The choice between them often depends on the nature of the business logic, the level of process reuse, and how centralized you want the control and evaluation logic to be. Having separate processes allows for more modular and decoupled logic, which can be beneficial for maintainability. A unified dispatcher-style process offers better coordination and visibility but may introduce more complexity up front.

From a performance perspective, it’s important to note that the number of signal-based triggers alone is not typically the main factor that impacts system performance. Rather, it is the overall process design, how much logic is executed, whether service calls are involved, and how efficiently process elements are structured. In environments using RabbitMQ, Creatio is more likely to offload process execution to the background automatically.

If you encounter any issues with a specific process or signal behavior, we recommend creating a support ticket via the Success Portal. Our support team will assist in analyzing and resolving the issue.

Hello!

This is an expected behaviour.

When setting a homepage, please make sure to use only pages that were created using the "Dashboards" template.
Other page types (such as tabbed or detail-driven pages) may not work as a homepage because they often require additional parameters in the URL (e.g., a record ID), which are not available during homepage loading.

If you create the page by clicking the “+” button next to the "Home page" field in the workspace setup, the correct Dashboards template will be used automatically.

Hello!

Our system is not designed to store SSNs and does not have the necessary compliance certifications, so we do not recommend storing this type of data.

However, if you still choose to store it (understanding that we are not compliant), then yes — you can use the "Contains personal data" option.

Currently, we do not have such functionality, but our R&D team is working on it, and it will be included in future updates.

Regards,
Orkhan

Hi Jose,

Please refer to the following Academy article for documentation on WhatsApp integration.

Hi Jose! How are you? Hope you are doing well. I also recommend to checking out our addon: https://marketplace.creatio.com/app/whatsapp-connector-creatio

Regards

Hello, 

Currently, this is the expected system behavior. If the modal/mini page for adding records is configured in Freedom UI, but you have Classic UI enabled, the mini-page will not open. Current mini pages (modal) only work for the shell and Freedom UI pages. However, we already have a task registered in our R&D team to consider and add support for modal/mini page details in Classic UI. 

Hello,

Please note that OOTB business process element "Process file" can only generate Word reports, you can find more details about its functionality in this article:

https://academy.creatio.com/docs/8.x/no-code-customization/bpm-tools/process-elements-reference/system-actions/process-file-element

Instead, you can use the "Generate Excel report" element that is a part of the "Excel reports builder for Creatio" app. 

Please note, that only the reports with "Custom report" type and a checked "Available in process" boolean can be used in the process.

Mira Dmitruk,

Hi, Mira, 

    Thank you for your help, however, I can't find "Available in process" setting in the Excel report setting, that may be the reason that I can't find it inside Excel in BP. What's the reason? I'm using 8.2.1.5446 Creatio cloud version, install the excel builder app few days ago. 
 


Jeffrey.

 

Jeffrey,

That option is only available for Custom Report types, not Section Reports as shown in your screenshot. If you create a new Excel report with type=Custom Report, it will show for that one.

Ryan

The attribute you need to set is the [TabControlName]_SelectrdTabIndex_Profile. If you tab control is named "TabPanel_fb0xrup", then the attribute you would set would be:

// select first tab
request.$context.TabPanel_fb0xrup_SelectedTabIndex_Profile = 0;

Note, the indexes are zero based.

Ryan

Also, to clarify, there is no "set" method in Freedom UI pages like there was in classic pages. You will just set and read values from the attributes directly as normal variables.

Ryan Farley,

Yes, it works fine.

However, how can I get the index of a particular tab using the Element code in the context? #FreedomUI

Ajay,

I am not sure there's a way to get the index at runtime, if there is I've not seen anything yet, but it's possible it's buried somewhere in the $context.

Hi,

The field is filled in, but until you save the entry, the event will not be executed. Please clarify what business task is so necessary?

Hi, 

Scenario : Show a specific field only when the record is created.

Which Business Rule should we use?

Thanks

Sasor

Sasori Oshigaki,

Greetings!

Thank you for reaching out. I looked into possible solutions and came across the idea that you could rely on the Resolution time field or find similar fields that are not created until you press Save. Unfortunately, I don’t see any other viable options in your case.

As in my case:

Regards,
Orkhan

Orkhan,

we have also solved requests like this by using fields that will be filled after the record was saved.

However, it would be great if you could add something like a "mode" to the business rules conditions that would have values like "new" and "update".

BR

You can also add a duration and awaitResponse to the request. Using awaitResponse will have it appear until acknowledged by the user.

request.$context.executeRequest({
    type: "crt.NotificationRequest",
    message: "This is my toast message!",
    awaitResponse: true
});

However, i don't believe there is anyway to have it display until you tell it to close (after the process completes)

thank Ryan,

I tried 

request.$context.executeRequest({
	type: "crt.NotificationRequest", 
	message: "Validando carga Excel...", 
	duration: 60000, 
	awaitResponse: true });

But in this case if the process ends before the 60seconds, need to user to close the message.... 

Is there another way to implement something similar?

Thanks again

Julio

We had a workaround to display the same toast message again but with a very short duration, since only 1 toast can display at a time, the new one replaces the original and then disappears. Not great and it would be nice to be able to hide toast messages on demand - ideally with reference to a specific message, so if we got back some ID from starting the toast notification.

Julio.Falcon_Nodos,

Harvey's idea could work, display the first toast with awaitResponse, then when the process ends display another toast without the awaitResponse and it should take the place of the first one.

Ryan

Harvey Adcock,

Thanks, great idea! I'll try it