To make a column mandatory in FreedomUI, you can follow these steps:
Identify the column you want to make mandatory in the detail view of your form.
Open the code or configuration file associated with your FreedomUI implementation.
Locate the section or code block related to the detail view of your form.
Find the column you want to make mandatory within the code or configuration.
Depending on the specific implementation of FreedomUI, you can typically add a validation rule or attribute to the column to make it mandatory.
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.
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.
I would like to know the name of the function/handler that's called when creating a record and saving it in an editable detail in FreedomUI so that we can override it. We also noticed SaveRecordRequest doesn't seem to be called here.
on the schema where detail is added and it's successfully triggered:
It also depends on which handler you have specified in the "Add button" properties, you need to find it in the schema diff (in my case it was crt.CreateRecordRequest):
The detail we are working with uses an inline record to create new records which doesn't seem to be calling CreateRecordHandler or CreateRecordRequest.
To my pleasant surprise, it appeared that that attachments component became editable since 8.0.7. If you upgrade your instance you should be able to make it editable.
I have this requirement that should allow users to revert changes of a specific record value. For example:
I have a specific field (Amount), that changes value when a new state is triggered (ex: Processed). It should be possible for the user to revert the value after selecting the previous state.
Our R&D team has an opened task on this topic, there is a test solution, but it cannot be applied to productions. Once the task is completed we will notify all our customers and partners in the Release Notes for the app. Thank you for helping us in making the application better!
This functionality has not yet been implemented, but we have already received many requests from users, so the R&D team should take this task into development.
I have this requirement where I need to refresh the form page of my record using the refresh button of the new Freedom UI. This button was created with the help of the page designer, as you can see on the image bellow.
However, when I try to refresh the page by clicking on the created button. Creatio, instead of refreshing the current page data, it loads the data from another record.
Before refresh:
After refresh:
Could you please help me understand this behaviour and explain me how can be solved.
Thank you for your post and sorry for invonvenience caused by this problem. This behaviour was removed in version 8.0.7 which is going to be released very soon.