Hello Andrew,



It could be achieved by development, please find similar questions bt the links below:

https://community.creatio.com/questions/text-area-field-editable-detail….

https://community.creatio.com/questions/detail-styles-css?_gl=1*1850rv9….

Bogdan,

Hi Bogdan, thank you for the solution links. But the screenshots in the reply are no longer visible. I followed the two steps in the reply, but had no luck. I put my screenshots below, can you correct them for me?

Step1, I created a module in our package Dynasafe1, kept JS empty

Step2, I put the CSS in the LESS

 Step3, I created a replacing view model under Dynasafe1 package

Then I chose "Base schema - Detail with list" as the parent object.

And finally saved this replacing view model with JS kept empty. Did I miss something here?

Thank you for your answer in advance!

Andrew Sheng,

I got the answer! All I had left to do was to fill the JS code with:

 define("BaseGridDetailV2", ["css!UsrDynasafeDetailV2CSS"], function() {
	return {
		methods: {},
		diff: /**SCHEMA_DIFF*/[ ]/**SCHEMA_DIFF*/
	};
});

Hello!

To implement it, you will need at least basic developer skills. In this case, we advise you to contact the manager about this issue.

Hello, 



 

Please refer to this article for detailed information:



https://academy.creatio.com/docs/user/nocode_platform/elements_reference/UI_designer

Best regards,

Orkhan 

Orkhan,

There is no information about having a detail in Freedom UI?

Hassan Tariq,

The Freedom UI component that is the equivalent to a Detail is the Expanded List.

Ryan

Hi!



I wonder, maybe there is step-by-step tutorial or video how to add new detail in Freedom UI?

I've tried several ways, none of them has given success to me



Kind regards,

Vladimir

Hello,

Please refer to this article for the detailed information. 



Best regards,

Anastasiia

Good day,

In the new interface, the details are configured similarly to the mechanism used in the old interface. It also includes automatic mapping to the ID of the current record, so there is no need to add it separately. For example, in the "Orders" detail added to the "Account" section by default, we can see that the detail displays records where Account.Id (of the current record) is equal to Order.AccountId.

Thank you for your question.

Best Regards,

Pavlo

To make a column mandatory in FreedomUI, you can follow these steps:

1. Identify the column you want to make mandatory in the detail view of your form.

2. Open the code or configuration file associated with your FreedomUI implementation.

3. Locate the section or code block related to the detail view of your form.

4. Find the column you want to make mandatory within the code or configuration.

5. Depending on the specific implementation of FreedomUI, you can typically add a validation rule or attribute to the column to make it mandatory.

6. Add the necessary code or configuration to enforce the mandatory requirement for the column. This may involve setting a "required" flag, adding a validation rule, or specifying a validation message.

7. Save your changes and test the form to ensure that the column is now mandatory in the detail view.

It's important to note that the exact steps may vary depending on the version and customization of FreedomUI you are using. Refer to the documentation or consult with the developers or support team of FreedomUI for specific guidance on making a column mandatory in the detail view.



More detail : https://360degreecloud.com/

Nevermind, I've found a solution by changing the parent name to the field group name.

 

				"operation": "insert",
				"name": "My Detail",
				"values": {
					"itemType": 2,
					"markerValue": "added-detail"
				},
				"parentName": "My Field Group",
				"propertyName": "items",
				"index": 1

In the detail schema do the following:

1) Add attribute

attributes: {
	"IsAddVisible": {
		dataValueType: Terrasoft.DataValueType.BOOLEAN
	}
}

2) Add attribute to visible property of add button, add the following to the diff of the detail schema: 

diff: [
	{
		"operation": "merge",
		"name": "AddRecordButton",
		"values": {
			"visible": {"bindTo": "IsAddVisible"}
		}
	}
]

3) Add the following to methods: 

methods: {
	onGridDataLoaded: function() {
		this.callParent(arguments);
		this.setAddVisible();
	},
 
	subscribeGridEvents: function() {
		this.callParent(arguments);
		this.setAddVisible();
	},
 
	setAddVisible: function() {
		var items = this.getGridData().getItems();
		this.set("IsAddVisible", items.length < 3);
	}
}

End result, the add button should only be visible when the detail has less than 3 items.

Ryan

Thanks a lot Ryan. I was using ESQ before, but this is definitely faster and better.