Hello.

Using out-of-the-box functionality in Creatio, it is not possible to dynamically add UI elements to a page via a business process.

The business process tools in Creatio are not designed to modify the UI structure.

This type of customization can only be achieved through additional development in the application source code. 

Best regards,
Antonii.

Hello!
In Creatio, the relations between Data Model objects (tables) can be configured in the following ways:

1. One-to-Many (1:M)

• Add a lookup column in the “child” object that references the “parent” object.
• On the parent object’s page, add a detail that displays related child records filtered by this lookup.

This is the most common relation type in Creatio.

2. One-to-One (1:1)

• Create a lookup column in object B referencing object A, and add a unique index on that column (so one A record can only have one B).
• Alternatively, you can use the same Id as the primary key in both objects, establishing a strict 1:1 relation.

Use this type if each record in one table should correspond to exactly one record in the other.

3. Many-to-Many (M:M)

• Create a link object that contains two lookup columns: one referencing object A and one referencing object B.
• Add a composite unique index on both columns to avoid duplicates.

Configure details on A and B pages to show related records through the link object.

Best practices:

• Use clear naming conventions for lookup columns and link objects (e.g., A_B_Link).
• Always add indexes on lookup columns and composite keys in link objects.
• For 1:1 relations, ensure database uniqueness is enforced.
• Add details to the UI so users can easily navigate related records ( for #1 and #2 relations).

Hello Firas,

Since you are working with Freedom UI, the recommended approach is to use crt handlers rather than the old Terrasoft.SysValue. The current logged-in user is available via the $context object in your request handler.

Here’s an example of how you can access the current user in your Angular component logic:

handlers: [
 {
   request: "crt.HandleViewModelInitRequest",
   handler: async (request, next) => {
     await next?.handle(request);
     // Access the current user information from the context
     const currentUser = request.$context?.CurrentUser;
     if (currentUser) {
       request.$context.UserName = currentUser.displayName;
     }
   }
 }
];

You can then use UserName inside your component template or for any business logic you need.

This way, your component will always get the correct logged-in user directly in Freedom UI.

Hi! Currently, in Creatio, adding columns to objects and defining their data types must be performed through either the Object Designer in the Application Hub or the Configuration section. There is no feature within Creatio's front-end UI that would allow end users to dynamically create new object columns on the spot like the functionality you described in Asana or Monday.com.

However, a workaround could involve implementing business processes or custom development that lets users store additional data in dynamically generated fields connected to your objects. This would, however, require developer assistance and predefined design.

Daria Spirina,

Thanks for your help, but to clear things out here, for the workaround to be implemented, how are these dynamically generated fields stored? like will they be added to the object as if I'm doing it from Application hub or Configruation, or what?

Hi! 

My apologies for giving not the full answer. 

The best approach is:

At the page level, you can create fields that are not part of the underlying object but can still hold values and be used in the application. These are called page parameters, and they can be added directly from the designer.

Creating dynamically generated fields is generally not a good idea, because as soon as you add such a field, the system will attempt to recompile with a database structure update. If that does not happen, you will get an error that the column does not exist in the object.

In other words, while it may be technically possible, it is not practical or supported. The recommended approach is to use page parameters instead.

Hello,

In order to disable the Display data/Drill down option, it is necessary to disable the features ChartDrilldown, ChartDrilldownByChartSeriesMenu, and ChartLegendClickMenu 

Please note that this setting will apply to all charts in the system.

Thanks Halyna. In that case, I don't think it will be a suitable solution for our client.

I will explore passing a calculation into an input instead.

Hello Mariam,

The message “Inactive package ‘AmsSurvey’ was not found” indicates the system has an reference to a missing inactive plugin package. To resolve this:
- retrieve the package Id via [SELECT "Id","Name" FROM "SysInactivePackage";]
- delete that entry with [DELETE FROM "SysInactivePackage" WHERE "Id"='AmsSurvey package_id';]
- then rerun the installation to reinstall the package.

Hello,

For the questions related to this marketplace solution, you can contact directly add-on developers for support: sales@psiog.com

Best regards,
Ivan