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,

As far as we understand,  you are referring to the fact that the "Mulai Bekerja" field is not available for selection in the formula setup.

This is most likely because Creatio currently supports only numeric fields in business rule calculations. Date fields, such as "Mulai Bekerja," are not supported in this context.

Please let us know if you'd like assistance implementing this logic using a business process instead.

Valeriia Hromova,

i have already tried using the business process however am unable to find the year function, so i would like some support here

Michael Fernando Handoyo,

Hello,

Thank you for your follow-up.

You're correct — business rules in Creatio do not currently support date fields in formulas. However, when working with business processes, you can calculate the difference between dates using the C# DateTime structure, as described in the documentation:

https://academy.creatio.com/docs/user/bpm_tools/business_process_setup/formulas/process_formulas#title-1621-4

Also, we have this built-in function that may help you as well:

Substract one number from another, divide it by 30 (if you need months) - here is your result in months (or you can use other math functions from the article)

I Created my own User task which handle all macro which have macro source filled in.

protected override bool InternalExecute(ProcessExecutingContext context) {
			// IMPORTANT: When implementing long-running operations, it is crucial to
			// enable timely and responsive cancellation. To achieve this, ensure that your code is designed to
			// respond appropriately to cancellation requests using the context.CancellationToken mechanism.
			// For more detailed information and examples, please, refer to our documentation.
			if (TemplateCode == Guid.Empty || RecordId == Guid.Empty) {
				isSuccess = false; 
				return true;
			}
 
			var templateEsq = new EntitySchemaQuery(UserConnection.EntitySchemaManager, "EmailTemplate");
			var bodyColumn = templateEsq.AddColumn("Body");
			var macroColumn = templateEsq.AddColumn("Object");
			var templateEntity = templateEsq.GetEntity(UserConnection, TemplateCode);
 
			if (templateEntity == null) {
				isSuccess = false;
				return true;
			}
 
			Guid macroSource = templateEntity.GetTypedColumnValue<Guid>("ObjectId");
			string body = templateEntity.GetColumnValue(bodyColumn.Name)?.ToString() ?? "";
 
 
			var macroSourceEsq = new EntitySchemaQuery(UserConnection.EntitySchemaManager, "SysSchema");
			var idFilter = macroSourceEsq.CreateFilterWithParameters(FilterComparisonType.Equal, "UId", macroSource);
			macroSourceEsq.Filters.Add(idFilter);
			var schemaNameColumn = macroSourceEsq.AddColumn("Name");
			var macroSourceEntities = macroSourceEsq.GetEntityCollection(UserConnection);
 
			if (macroSourceEntities == null || macroSourceEntities.Count == 0) {
				isSuccess = false;
				return true;
			}
 
			string schemaName = macroSourceEntities[0].GetColumnValue(schemaNameColumn.Name)?.ToString() ?? "";
 
			var macroRegex = new Regex(@"\[#(.*?)#\]");
			var matches = macroRegex.Matches(body);
 
			if (matches.Count == 0) {
				ReturnBody = body;
				isSuccess = false; 
				return true;
			}
 
			var esq = new EntitySchemaQuery(UserConnection.EntitySchemaManager, schemaName);
			var columnMap = new Dictionary<string, string>(); 
 
			foreach (Match match in matches) {
				var macro = match.Groups[1].Value;
				if (!columnMap.ContainsKey(macro)) {
					var column = esq.AddColumn(macro);
					columnMap[macro] = column.Name;
				}
			}
 
			var entity = esq.GetEntity(UserConnection, RecordId);
			if (entity == null) {
				ReturnBody = body;
				isSuccess = false;
				return true;
			}
 
			var result = body;
			foreach (Match match in matches) {
				var macro = match.Groups[1].Value;
				if (columnMap.TryGetValue(macro, out string esqColumnName)) {
					try {
						var value = entity.GetColumnValue(esqColumnName)?.ToString() ?? "";
						result = result.Replace(match.Value, value);
					} catch (Terrasoft.Common.ItemNotFoundException) {
						try {
							var value = entity.GetColumnValue(esqColumnName + "Id")?.ToString() ?? "";
							result = result.Replace(match.Value, value);
						} catch {
							result = result.Replace(match.Value, "");
						}
					}
				}
			}
 
			ReturnBody = result;
			isSuccess = true;
			return true;
		}

Check the start of the process (the green circle) and make sure the “run in background” is NOT checked. 
Ryan 

Ryan Farley,

So I checked my object signal (green circle) and the Run following elements in the background field is unchecked. This checkbox is also unchecked for the pre-configured page element. 

Sadly, there's no way to handle the timeout error in the process, it will only put the process in an error state - I do wish it was an option to handle that in the process rather than have the whole process error. 

Only option would be to increase the timeout for the web service call to possibly allow for the additional needed time. Otherwise, I've added script tasks that check for the service availability and can branch as needed to avoid the web service call, but that defeats the benefits of using the no-code web service components in the first place.

Ryan

Ryan Farley,

Thank you, if possible can you please share an example of how did you added script tasks that check for the service availability?

AS,

It was basically just C# that called one of the API methods and then set a param in the process so it knew to proceed or branch elsewhere. How that would look would depend on the API, but essentially you’re just writing code to call the API directly.

Hello,

The contents and structure of the AccountCompactProfile / ContactCompactProfile elements are immutable in the system. Their behaviour is preconfigured and is, unfortunately, impossible to alter.

A request to improve this logic has already been submitted to our R&D team, and they are looking into the possibility of expanding it in the future versions of Creatio.

i see thank you for the information :D

Hello,

Based on the provided information, the error message suggests that there are duplicate element names within the same package. This issue typically occurs when multiple elements in the package share the same name.

To resolve this, we recommend checking the package that contains the Activity object to ensure there are no duplicate element names. Review the elements within the package and confirm that each one has a unique name.

If you identify any duplicates, you will need to rename one of the elements to make it unique within the package. Once the duplicate element names are resolved, you should be able to add the CrtCoreBase package as a dependency without encountering the error.

Best regards,
Ivan

Ivan Savenko,

Hi, 

I confirm that i have duplicate element like

But it  is safe to rename them because one is being used in incoming email message and other in outgoing email message (both section are connected to activity object).

Hello,

Since both sections are tied to the Activity object, it's likely that the error comes from duplicated data bindings in the same package.

You can check the "Data Bound" tab to see which bindings are actually needed. If both are, consider slightly renaming the duplicates (e.g., SysModule_Activity_Incoming, ..._Outgoing) to avoid conflicts.

Alternatively, you could remove or move one of the bindings to another package, depending on your setup.

Best regards,
Ivan

Ivan Savenko,

Hi,

I moved those duplicate elements to other package and now i am able to add new packages in depend on package.

Thanks

Hello!

You can definitely display the resolution time in the list, but unfortunately, applying dynamic coloring directly on the list records is not possible in the current version. However, we have registered the idea for consideration and possible future implementation by our R&D team.

As an alternative, you can consider adding the timer directly in the case record itself in Freedom UI list pages:

You can implement the timer feature within the individual case record:

Thank you!

Creatio does allow you to create your own custom UI components that you can add to the UI and even handle requests, read data, bind properties, etc. Documentation here on creating custom components: https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/category/freedom-ui-component

Video tutorial here: https://www.youtube.com/watch?v=CE5uETqTsyQ&list=PLnolcTT5TeE2BMFf_XmJrSwpnbcLCLJkb

A simple approach (with limited capabilities compared to creating a full control) can be seen here: https://customerfx.com/article/embedding-an-iframe-on-a-creatio-freedom-ui-page/ (you could use this approach to render any HTML, not just an IFRAME as the article shows)

Ryan

For classic details, rules implemented on the page are also manifested in the list for the detail. I believe you can just implement the filtering for the lookup on the page for the detail, then it will work in the list as well. 

Thank you Ryan  for your answer!
Actually, my detail is an editable grid. I noticed that the page-level lookup filtering doesn't propagate into editable grids automatically. From my tests and observations, the editable grids seem to require explicit filtering logic within the generateActiveRowControlsConfig method instead.
Could you please confirm if this understanding is correct, and perhaps suggest any best practices or examples explicitly for editable grids?