I’d like to navigate from a FreedomUI page to a classic list page, so they don’t loose Dashboards in Freedom.
Is it possible to use the request handler of a button in FreedomUI to redirect the user to the classic list of a specific object?
Thanks!
Like
Hello Andres.
Thank you for your question.
The logic you are trying to achieve can be implemented in a couple of ways. It depends on which sections we are talking about and the reason for doing it.
The first way of redirecting from one page to another is using the handler chain service. For example, in the Contacts_ListPage (Freedom UI) in the HandleViewModelInitRequest, I implemented a handler as follows:
During the page initialization, I use the handler chain instance to call the OpenPageRequest handler, which in turn opens the ContactSectionV2 page (Classic UI List Page). This method is the most straightforward but makes the least sense if you want to apply the redirection logic that you described to those sections that are present in both Freedom UI and Classic UI by default. Instead, you can simply set up your workplace to display the Classic UI section instead of the Freedom UI.
Here you can see that there are two copies of the Contacts page. Some pages are duplicated as they are present in both Classic UI and Freedom UI.
However, there are cases when you might notice that even though you set up your workplace to open a Classic UI version of a page, the system will open a Freedom UI analog. To change this behavior, you can go to Lookups -> Object-specific form page interface in the Freedom and Classic UI shell.
Change the values for the 'Classic UI shell' and 'Freedom UI shell' columns to Freedom UI pages if you want your page to open in the Freedom UI version or to Classic UI respectively. But note that the Freedom UI section ignores any page settings and always opens a Freedom UI page (if there is one). An article regarding this question can be found here.
To summarize, your logic can be implemented in a couple of ways depending on the details.
I hope my answer helps you. If not, I am open to helping you further.
Hello Andres.
Thank you for your question.
The logic you are trying to achieve can be implemented in a couple of ways. It depends on which sections we are talking about and the reason for doing it.
The first way of redirecting from one page to another is using the handler chain service. For example, in the Contacts_ListPage (Freedom UI) in the HandleViewModelInitRequest, I implemented a handler as follows:
During the page initialization, I use the handler chain instance to call the OpenPageRequest handler, which in turn opens the ContactSectionV2 page (Classic UI List Page). This method is the most straightforward but makes the least sense if you want to apply the redirection logic that you described to those sections that are present in both Freedom UI and Classic UI by default. Instead, you can simply set up your workplace to display the Classic UI section instead of the Freedom UI.
Here you can see that there are two copies of the Contacts page. Some pages are duplicated as they are present in both Classic UI and Freedom UI.
However, there are cases when you might notice that even though you set up your workplace to open a Classic UI version of a page, the system will open a Freedom UI analog. To change this behavior, you can go to Lookups -> Object-specific form page interface in the Freedom and Classic UI shell.
Change the values for the 'Classic UI shell' and 'Freedom UI shell' columns to Freedom UI pages if you want your page to open in the Freedom UI version or to Classic UI respectively. But note that the Freedom UI section ignores any page settings and always opens a Freedom UI page (if there is one). An article regarding this question can be found here.
To summarize, your logic can be implemented in a couple of ways depending on the details.
I hope my answer helps you. If not, I am open to helping you further.