If you drag them taller it will give more room for the chart bars/columns and the text will be more readable.

Ryan Farley,

Thank you! This worked. I did not see the little square to drag the chart taller before.

Hello!

Could you please add more details regarding your business aim?

If you mean changing the list page view in the section, in Creatio, list pages typically display data in a tabular format.

The main goal is to implement a schedule for approximately 100 employees.
There was an idea to implement it using a registry element.
However, the usual calendar view does not quite fit (i.e., dates and working hours are represented horizontally, and employees are listed vertically).
Since the number of employees will be relatively static, but weeks/months will continuously be added, the standard registry view is not entirely suitable for implementation.
The need arose to add new records horizontally (with the ability to scroll left/right) — these will be the weeks/months, while employees will remain static vertically.

The idea is to add new records to the registry horizontally, not vertically.
If it's not entirely clear, I can explain in more detail.

Is such implementation possible?
Perhaps you already have a ready solution for the schedule or better alternatives for implementing it?

The list component has a couple of attributes you can use for this. You'll add a handler for the "crt.HandleViewModelAttributeChangeRequest" request and listen for changes to these attributes. There are a few attributes you could use, one that is ListName_NoItems (boolean) (or "DataTable_NoFilteredItems" for when the list is filtered) or ListName_Items (array of items). If your list component is named "DataGrid_ysopiif", your attribute names would be "DataGrid_ysopiif_NoItems", etc.

Add something like the following to the handlers of the page with the list:

{
    request: "crt.HandleViewModelAttributeChangeRequest",
    handler: async (request, next) => {
        if (request.attributeName === "DataTable_NoItems" || request.attributeName === "DataTable_NoFilteredItems") {
            if (request.value) {
                // no records returned for list
            	Terrasoft.showInformation("No results returned!");
            }
        }
    	return next?.handle(request);
    }
}

Ryan

Ryan thanks -- moved to Data_grid and used the following code and it works. 

Now to see how to fix a filter which can show only records which are modified in last 5 mins (out of box gives in hours only)


        handlers: /**SCHEMA_HANDLERS*/[
            {
                request: "crt.RefreshedDataGrid",
                handler: async (request, next) => {
                      const context = await request.$context;
                      const list = await context.DataGrid_cdjhzhp;
                      const listCount = list?.length ?? 0;
                      if ( listCount == 0 &&  await request.$context.SearchFilter_fvbn39g_SearchValue.__zone_symbol__value
!= null ){
                              const uxClaimID= await request.$context.SearchFilter_fvbn39g_SearchValue.__zone_symbol__value
;
                              console.log("Claim Id = " + uxClaimID);
                               const result = await request.$context.executeRequest({
                                          type: "crt.RunBusinessProcessRequest",
                                          processName: "HC_ClaimACID",
                                          processParameters: { ClaimID: uxClaimID },
                                          //resultParameterNames: ["HC_ClaimGUID"],
                                          $context: request.$context
                               });
                               //if (await result.success) { 
                                // }
                       }
                      return next?.handle(request);  
             } 
         }        

Hello! Recursive sub-processes-where a process calls itself directly as a sub-process-are not supported natively in the Business Process Designer, and for good reasons:

Why it's not allowed by default:
Recursion can easily result in infinite process executions if not managed carefully (e.g., no base case or exit condition).

Recursive calls could overload the scheduler queue and background processes.

The BP Designer intentionally filters out the current process from the list of available subprocesses to avoid this scenario.

Alternative Solutions:
1. Create a secondary wrapper process (e.g., MyProcessWrapper) that calls the main process (MyRecursiveProcess).

Inside MyRecursiveProcess, under certain conditions, call the wrapper again.

This technically breaks the direct recursion and gives more control.

2. Instead of recursion, Creatio recommends modeling loops with Gateways (Exclusive or Inclusive) and Intermediate Timer or Signal Events to create a controlled looping behavior.

3. If your recursion is simple (e.g., batch iteration or hierarchical processing), consider using Script Tasks with logic in C# to handle recursion internally. This avoids BPM overhead.

Nick Ovchynnik,

Thank you Nick for the detailed response.

Hello Artem,

You can store record ID in the custom attribute and populate its value when the page is opening in the request crt.HandleViewModelInitRequest.

viewModelConfigDiff: /**SCHEMA_VIEW_MODEL_CONFIG_DIFF*/[
	{
		"operation": "merge",
		"path": [
			"attributes"
		],
		"values": {
			"RecordId": {}
			...
		}
	}
	...
]

handlers: [
	{
		request: "crt.HandleViewModelInitRequest",
		handler: async (request, next) => {
			await next?.handle(request);
			request.$context.RecordId = request.$context.Id;
		}
	}
]

Then you can use this custom attribute in your component

{
	"operation": "insert",
	"name": "CustomTable",
	"values": {
		"recordId": "$RecordId",
		"type": "usr.Table"
	},
	"parentName": "ListOfTarrifGroupByPeriod_ExpansionPanel",
	"propertyName": "items",
	"index": 0
},

Iryna Oriyenko,

Thank you very much!

Hi,

We've investigated this behavior, and unfortunately, the "Process File" element cannot be configured to work with SysFile in cases where a registered [Object]File schema exists for the object in the system.
Currently, this behavior cannot be modified using low-code or development approaches.

At the same time, this is not the expected behavior, and we are already working on fixing this issue as part of the product. For now, the only viable solution is to use [Object]File for your task.

If your goal is to build a universal process that sends emails with attachments from different entities, we recommend creating separate flows for each object. For example, if the entity is Case, use a flow where the "Process File" element is configured for CaseFile; if it's another object without a custom file storage, use SysFile, etc.

We've also raised the priority of the existing task, taking your user experience into account. This will help prioritize and speed up the resolution.

Thank you for your understanding!

Pavlo Sokil,

Thanks for your reply

In my tests the Process File element doesn't work with SysFile for new Freedom UI objects that don't have a registered [Object]File schema. The returned file collection is always empty.

Any suggestions?

Thanks

Massimiliano Mazzacurati,

Hi,

Understood, thank you for letting us know. We've analyzed the situation — currently, the process element doesn't work quite correctly with attachments stored in SysFile.

To resolve this, you’ll need to make a small change to the process metadata. Here's a brief guide on how to do it, using a test section (Test Section) as an example:

1. In the Process File element, select "Uploaded file" (SysFile) as the object.
   
   
2. Then, in the Advanced settings, you’ll see a parameter called "Source data object" (SourceDataEntitySchemaUId) — this is the object to which the attachments in SysFile are linked.
   You’ll need to manually change this in the metadata to the UId of the actual object you are working with.

3. Open the process metadata and switch to Modifications package mode.

    

4. Locate the parameter by its code: "SourceDataEntitySchemaUId", and replace its value with the UId of your desired object.
5. 

   
   You can find the UId in the system configuration by clicking the three-dot menu and choosing "Properties" — for example:

6. 

    

7. After that, in the process metadata, update the "GS2" value for this parameter and save the changes.

   

8. Important: Reload the process page before making further changes in the designer to avoid overwriting the metadata update.
9. Now you will notice the changes in parameter's settings in advanced mode:
    

That’s it — now the attachments will be linked correctly.

Please note that for now, this is a workaround. Our team is actively working to ensure the process element handles this case properly without needing to modify the metadata manually.

Hope this helps solve your business task.

Thanks for reaching out!

An easy no code way would be to bind the value to a read-only Rich Text control on the page. It will display the HTML as HTML.

Otherwise, you'd have to create your own custom control for it.

Ryan Farley,

Thanks for the suggestion! I am looking for custom control.

Is there any reference or example available to create custom control.

Hello Ajay,

Here is the article that contains the explanation and example of how to create custom control

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platform/8.1/front-end-development/classic-ui/controls/examples/add-a-control-to-a-record-page

Also inside your custom control implementation you can add HTML value validation and remove any script elements to provide the level of security. 

Hi Iryna,

Is above link, you provided, applied for Freedom UI module?

The information and example for Freedom UI you can find here:

https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…

This simple example of an IFRAME control could easily be adapted to simple output a div containing the custom HTML instead, plus you'd just bind the column containing the HTML to the control. https://customerfx.com/article/embedding-an-iframe-on-a-creatio-freedom-ui-page/

A full component would likely be a better route, but this simpler option coudl still get the job done.

Ryan