Hi there,
I’m integrating this feature Redirecting… for my application.
When enabling the feature I can see the deep link works on my entities.
However, when reloading the application, it automatically reset the link to an empty link, as you can see in the image below:
My setup:
{
customSagas: [
...CRUDFactories.createSagas(),
...formEngineSagas,
...cdmSagas,
loadModelGraphSaga,
...applicationSagas,
DeepLinkingFactories.createWelcomePageSaga({ applyTriggers: [UaaActions.loggedIn] }),
...DeepLinkingFactories.createSagas({ applyTriggers: [UaaActions.restoreSuccess]}),
// add the relationship sagas
...RelationshipFactories.createSagas({ dataHandlers })
]
}
Is there any additional work needed to achieve this requirement?
Thank you!
P/s: I’m using A12 2023.06-ext3!
Not sure, but it seems to me, that something is not matching. Based on docs “If the Activity encoded in the URL is not found, the default page will be loaded”. Could you e.g. add more triggers, maybe the activity is available only after loggedIn and the restoreSuccess is before.
Do you mean we have to implement the Activity-encoded URL?
As you can see in the image below, they’re action lists when reloading the application:
- No, Deeeplinking is doing it itself - takes URL and “parse” it to activity - you have it on first screenshot - feature, model, instance
- From activity list, you can see that the
RESTORE_SUCCESS if before models are added, so then Deeplinking doesn’t know about your models and can’t redirect to them.
Try to use same trigger as for welcome page, at that point models should be already added.
Even while I set the trigger event with the same as the welcome page:
DeepLinkingFactories.createWelcomePageSaga({ applyTriggers: [UaaActions.loggedIn] }),
...DeepLinkingFactories.createSagas({ applyTriggers: [UaaActions.loggedIn]}),
I still got this issue
pollingMiddleware.ts:35 extensions/deep-linking Error: No scene reference found for activity 1.
at determineLoadingStateFromScene (utils.js:74:19)
at determineLoadingStateFromScene.next (<anonymous>)
at next (redux-saga-core.esm.js:1180:29)
at currCb (redux-saga-core.esm.js:1274:7)
at runSelectEffect (redux-saga-core.esm.js:754:5)
at runEffect (redux-saga-core.esm.js:1227:7)
at digestEffect (redux-saga-core.esm.js:1294:5)
at next (redux-saga-core.esm.js:1184:9)
at currCb (redux-saga-core.esm.js:1274:7)
at runSelectEffect (redux-saga-core.esm.js:754:5)
Hi @nhat-round-cloud,
I tried integrating the deep link into the latest project template, and it seemed to work with this config. Could you please check with the following changes?
customSagas: [
...CRUDFactories.createSagas(),
...formEngineSagas,
LoadModelGraphSaga,
setLanguageSelectedInLoginForm,
// DeepLinkingFactories.createWelcomePageSaga({ applyTriggers: [UaaActions.loggedIn] }),
...DeepLinkingFactories.createSagas({ applyTriggers: [UaaActions.loggedIn] })
],
Sadly it doesn’t work for me…
Could you check if it works in minimal way, just reload from different module from menu “Client”, “Broker”, “Contract”. If you do not have any extra middlewares it should work as @loi wrote.
Based on your new error it seems, that there is some logic about which deeplinking is not aware and then can redirect to the activity, because it doesn’t exist or is not ready yet.
Hi @ondrej-virtual-peak,
The links of the overview work as expected.
So Should I create a ticket to support it if it’s not ready yet?
There is a problem, that you would like to support specific feature of your project, which the Deeplinking is not aware of by design. Imho what do you need is implement custom routing based on your URLs and activities. This will allow you also to do more fancy stuff, like preload data, trigger custom actions and so on. But as it is also written in docs Deeplinking uses only latest activity.
+ About the ticket. I’m not from Client team, so I can’t say, if the ticket will be accepted or about latest plans with Deeplinking functionality.
+ You can find already some routing topics here in Discourse: https://discourse.geta12.com/search?q=router
Hi @ondrej-virtual-peak @loi-risen-dale ,
I found in my project using the priorScene feature which is not supported by the deep link. Remove the configurations of priorScene to make the deep link work for my project.
Thanks for taking of my topic!
Best regards!