Hello,

Unfortunately, this logic is hardcoded and cannot be changed at the moment. We have raised an improvement for the development team to make it possible to configure the default Category for this element in future releases.

Thank you for reaching out!

Thanks Pavlo, so no properties in the JSON can be set for this currently at all then? And no overriding of any of the schema handlers would enable setting them either? We currently have a fair amount of handler code, so wouldn't be too worried about adding some more in for now until this is possible in no code.

Unfortunately, it is not possible to change this logic for this scheme at the moment, even using such handlers.

Hello,

There is no direct method to do that, but here are a couple of options that may help:

1) When opening an object in the designer this service is called (via POST request):

https://creatioAppURL/0/ServiceModel/EntitySchemaDesignerService.svc/Ge…

to get the content of the object (metadata). The body for this request is the following:

{"schemaUId":"5479e4d7-510e-4b18-9242-e2b3125ab786","useFullHierarchy":false}

5479e4d7-510e-4b18-9242-e2b3125ab786 should be replaced with the UId of the object you need. Received JSON string can be then parsed to get the list of columns of the object.

2) You can also create a simple ESQ, use the AddAllSchemaColumns method and then retrieve the list of columns from the Columns property of the ESQ instance you created.

Hello,

We have declined to incorporate this functionality within the Order and Contract Management application. The utilization of this detail within the application is accompanied by existing logic, and as of now, there are no plans to integrate it.

However, I will register such idea.

Hello, 

Thank you for reaching out with your question. I understand that you're looking for a way to apply dynamic filtering, but unfortunately, there is no built-in functionality for this specific feature. 

 

However, as a workaround, you can apply filtration for the table configured in the report setup. This allows you to customize the data that appears in the printable report according to specific criteria. While it may not offer the same level of flexibility as dynamic filtering, it can still help you achieve your desired outcome to some extent. 

For more detailed instructions on setting up reports please refer to the following link: 

https://academy.creatio.com/docs/8.x/no-code-customization/8.0/customiz…

Hi Tom,

What's happening here is that the Account Form page needs to access items that are located in your Custom folder, but because of the hierarchy, it's unable to do so. 



If you move the Freedom UI Account Form page to the custom folder, you can test saving the page and see if that works. If it does, the above is indeed the issue. 



Harry

Dear Smadar,

For Classic UI, you can use a marketplace solution: https://marketplace.creatio.com/app/tree-view-creatio

For Freedom UI, you will need to create your own component. You can find more information about that on Creatio Academy: https://academy.creatio.com/docs/8.x/dev/development-on-creatio-platfor…

I hope this helps.

Have a great day!

and the same in a Detail (Freedom page)?

Hello Julio,

See this article here: https://customerfx.com/article/adding-row-action-menu-items-to-a-creati…

You can override the menu (usually to add other menu items to it). When you do so you override the "Open", "Copy", "Delete" options and need to add them back in. You could override the menu and then just only add back in the "Open" option. It would look like this (the article will provide more details)

viewConfigDiff: /**SCHEMA_VIEW_CONFIG_DIFF*/[
    {
        "operation": "merge",
        "name": "DataTable",
        "values": {
            //...,
            "rowToolbarItems": [{
                type: 'crt.MenuItem',
                caption: 'DataGrid.RowToolbar.Open',
                icon: 'edit-row-action',
                disabled: "$Items.PrimaryModelMode | crt.IsEqual : 'create'",
                clicked: {
                    request: 'crt.UpdateRecordRequest',
                    params: {
                        "itemsAttributeName": "Items",
                        "recordId": "$Items.PDS_Id"
                    }
                }
            }]
        }
        //...
    },
    //...
]/**SCHEMA_VIEW_CONFIG_DIFF*/

Essentially you're replacing the existing menu with one that only has the Open menu option. This works for any list (section or a list on a page)

Ryan

Ryan Farley,

Thanks Ryan, I promise I looked first, before to publish, in your articles, but didn't found this one. Thanks a lot

Regards

Julio

Ryan Farley,

Dear Ryan, I didn't found the crt.DataGrid element in the viewConfigDiff in the code of the listpage, I found it on a FormPage, but I need it also in a the ListPage

solved no need to search crt.DataGrid, jus add it on viewConfigDiff

Julio.Falcon_Nodos,

Yes correct. For the list page, the List (crt.DataGrid) exists in the parent page, you just need to merge in the changes.

Ryan

No worries - there's so much new info now with Freedom UI stuff, it's hard to know what to even search for!

Julio.Falcon_Nodos writes:

Ryan Farley,

Thanks Ryan, I promise I looked first, before to publish, in your articles, but didn't found this one. Thanks a lot

Regards

Julio

This could really do with being configurable using no-code tools, as it's quite cumbersome to apply to every list users will see but is often important - being able to copy records which should have to be created in specific ways is often an issue for business data.

Ryan Farley,

Hello again Ryan

How can I remove the delete option on a Freedom UI page , I see that when I add a detail only a FormPage is created, but there is no ListPage (like in Classic UI). So is it possible to solve this in a Freedom UI detail?

Julio.Falcon_Nodos,

Hi Julio, basically, any time you override the rowToolbarItems it replaces what is there with that you provide. Meaning, all the existing out of the box ones are gone. If you want no items there, you can just add and empty array:

rowToolbarItems: []

However, this has the annoying side effect of leaving an empty menu that pops up when the row actions button is clicked. I'm not sure if there's a property to remove the row actions button completely, so I usually just hide it with CSS.

Ryan

Ryan Farley,

Thanks Ryan, I'm already solved, but I want to maintain "Open", "Copy" and just remove "Delete", how can I did it?

solved... adding in "rowToolbarItems", this piece of code

"rowToolbarItems": [
  // Edit
  {
	type: 'crt.MenuItem',
	caption: 'DataGrid.RowToolbar.Open',
	icon: 'edit-row-action',
	disabled: "$Items.PrimaryModelMode | crt.IsEqual : 'create'",
	clicked: {
		request: 'crt.UpdateRecordRequest',
		params: {
			"itemsAttributeName": "Items",
			"recordId": "$Items.PDS_Id"
		}
	},
  },
  // Copy
  {
	  type: 'crt.MenuItem',
	  caption: 'DataGrid.RowToolbar.Copy',
	  icon: 'copy-row-action',
	  disabled: "$Items.PrimaryModelMode | crt.IsEqual : 'create'",
	  clicked: {
		  request: 'crt.CopyRecordRequest',
		  params: {
			  "itemsAttributeName": "Items",
			  "recordId": "$Items.PDS_Id",
		  },
	  },
  }                      
],

Note, when adding these back in, you'll need to make sure that the "items" and "primaryColumnName" values match the values from your list. For Section Lists. The "Items" and "PDS_Id" values need to be updated to match your List's property values - those can likely stay as-is for section lists, but for new lists added, you'll need to update those values. See for more: https://customerfx.com/article/adding-row-action-menu-items-to-a-creati…

Ryan Farley,

Is there any other way to hide the 3 dots for row action menu to even spawn

Pranshu Basak,

Sadly, removing all menu items does not remove the 3 dots button (in current versions, at least - hopefully that changes). For now I typically just hide it with some CSS.

Ryan

Same here in our cloud dev environment with this new 8.1.2 functionality

You are right, we do not have the problem on our production environment, only on the dev env.

Hello,

Please note that this issue is connected to the 8.1.2 release and in order to fix it you need to create a case directly for our Support team (support@creatio.com) so we could work with the site in question.

Hello,

 

Unfortunately, it is not possible to perform this task in a basic way. You can only filter the data you need in folders, but there is no way to completely move all records from the main contact list page to one folder so that they are only available in one folder and not on the main list page.

 

We've registered this idea in our R&D team backlog for consideration and implementation in future application releases. Thank you for helping us to improve our product.

Hello,

To achieve this task you can try the following approach:

1) Create a system operation in the "Operation permissions" section with the code like "GlobalSearchInputVisible" and grant access rights to system administrators only:

2) Activate the system feature with "AllowCreateAngularSchema" code (it's not available by default in the features list (available via /0/Shell/#Section/AppFeature_ListPage), you need to create a record in the list and enable it for your user).

3) After enabling the featue at step 2 a new option will appear in configurations that allows creating replacements for angular schemas:

Select this option and select "MainShell" as a parent schema for the created module.

4) Specify the following code in the schema from step 3:

define("MainShell", /**SCHEMA_DEPS*/["@creatio-devkit/common", "css!CardSchemaViewModule", "css!MainShellCSS"]/**SCHEMA_DEPS*/, function/**SCHEMA_ARGS*/(devkit)/**SCHEMA_ARGS*/ {
    return {
        viewConfigDiff: /**SCHEMA_VIEW_CONFIG_DIFF*/[]/**SCHEMA_VIEW_CONFIG_DIFF*/,
        viewModelConfig: /**SCHEMA_VIEW_MODEL_CONFIG*/{}/**SCHEMA_VIEW_MODEL_CONFIG*/,
        modelConfig: /**SCHEMA_MODEL_CONFIG*/{}/**SCHEMA_MODEL_CONFIG*/,
        handlers: /**SCHEMA_HANDLERS*/[
			{
				request: 'crt.ContentDisplayedStateChangedRequest',
				handler: async (request, next) => {
					const rightService = new devkit.RightsService();
					const canUseGlobalSearch = await rightService.getCanExecuteOperation('GlobalSearchInputVisible');
					if (!canUseGlobalSearch) {
						var element = document.querySelectorAll('[data-item-marker="AppToolbarGlobalSearch"]');
						element[0].remove();
					}
					return next?.handle(request);
				}
			}
		]/**SCHEMA_HANDLERS*/,
        converters: /**SCHEMA_CONVERTERS*/{}/**SCHEMA_CONVERTERS*/,
        validators: /**SCHEMA_VALIDATORS*/{}/**SCHEMA_VALIDATORS*/
    };
});

The idea here is simple: check if the user has access to system operation and if not - take the element that contains data-item-marker="AppToolbarGlobalSearch" selector and remove it from DOM.

5) Save the schema and refresh the page.

As a result the Global Search input will be hidden for regular users, but will be available for system administrators.