Understanding SSR Deep Linking

Question

I m working on a handful of extensions that should be able to be linked to one another In one instance I have one extension that when a button is pressed will redirect the user to a specific page w in another extension My first attempt at creating this behavior has been to add a parameter redirectTo to my Main tecton module config I would assume that I would be able to access the value of that parameter in my extension py file and then render the appropriate page I looked through several properties of the self self request variables in my extension but never saw where I would grab that parameter value from My next attempt was trying to grab the parameter out of the of the URLSearchParams object in the frontend I passed in window location search window parent location search into the URLSearchParams object but never saw an values in there My question is where do I get the values of the module parameter I ve read the following documentation but perhaps missed something https docs q2developer com guides frontend development deep linking html highlight query 20parameters https docs q2developer com guides frontend development additional entrypoints html module parameters I m certainly open to different approaches Thanks

Adam Chester · Accepted Answer

Hi Brock If I am understanding you correctly you want to read the Tecton params on init of your SSR extension and re route to a different routing key inside your extension accordingly To navigate from a button click to another SSR extension passing a configured query param you would do something like below in your template script document querySelector my button addEventListener click function tecton actions navigateTo featureName ExtensionName moduleName Main queryParams redirectTo routingKey script To catch and read this Tecton param at the initialization of your receiving extension you will need to add another script in the default route template of your extension like the example below This should trigger on load and will allow you to check for the parameter and use the requestExtensionData capability to change your routing key and load an alternate template script window tecton connected then function tecton tecton sources paramsChanged params if params redirectTo tecton sources requestExtensionData route params redirectTo script To have your extension correctly handle the query params you want to use the module parameters https docs q2developer com guides frontend development additional entrypoints html module parameters section of the documentation should help you in setting up the redirectTo param in your configuration https cdn4 onlineaccess1 com cdn base tecton v1 21 Documentation capabilities navigateTo https cdn4 onlineaccess1 com cdn base tecton v1 21 Documentation capabilities paramsChanged https cdn4 onlineaccess1 com cdn base tecton v1 21 Documentation capabilities requestExtensionData https docs q2developer com tutorials online banking routing html

Answers