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.
I have 4 tabs in a form page each Tab has a button named "Continuation". On Click of the button, the current tab fields should be saved and then move to 2nd tab.
In "old style" Creatio is possible to create different section pages depending on a lookup field, just like Activities out-of-the-box section (one page for Task, one for Email, one for Call).
In Freedom UI pages I cannot find the way to do the same thing: how can I setup different Freedom UI pages depending on the value of a lookup field of the record?
Multiple form pages for a single object. It is now possible to create multiple form pages for a single object in the Object Designer as well as in the settings of both List and Button components. The app determines the page to open based on a field value. For example, this lets you have completely different pages for different request types.