Microflow/page URLs dont support more than one prefix?

0
Because of its deprecation, we are moving away from the Deeplink module and are currently investigating the use of microflow/page URLs and the impact it will have. Our current deeplink implementation uses a specific setup with multiple levels in the deeplink's URL path: {{baseUrl}}/link/Start/{page-that-should-be-opened}. However, when I change the default URL prefix p to link/Start in the app's Runtime settings, thereby recreating the existing deeplink setup of our current implementation, it breaks. The microflow/page URL is setup correctly, but when navigating it in the browser, the page can't be found. It works with just 'link' or 'Start' as the URL prefix, but combining them in a path doesn't work... Do microflow and page URLs not support extended paths/URL prefixes? I would hate to have to change the generic deeplink setup and have hundreds of deeplinks break at the same time...
asked
2 answers
0

Hi Bart,

 

You can add your second and subsequent layers of the URL prefix in the Page or Microflow URL. It is a bit more work, but at least you will be able to move away from the Deeplink module.  

You don't have to add the first / to your URL, which will be added by default. 

 

Hope this helps you move away from the deprecated module.

KR, Jurre

 

answered
0

Thanks, Jurre!

Then I will definitely raise a feature request for URL prefixes to support multiple path fragments, instead of just one... ;)

answered