Migration Readiness Assessment

0
Hi Everyone,We are upgrading a Mendix 9.24.26 application where the Deep Link module is currently used.Since the module is deprecated, I want to understand the migration effort.What is the best way to:- Inventory all existing Deep Links- Determine where they are called from- Identify dependencies on pages and microflows- Estimate replacement effort using supported Mendix solutionsHas anyone completed a similar migration and can share best practices?
asked
1 answers
0

Hi Kumar,

I would start by separating the inventory into configuration and usage.

The Deep Link configurations are runtime data, so first retrieve/export the configured DeepLink objects from an environment. This gives you the actual links and the microflows they invoke.

Then, for each referenced microflow, use Studio Pro Find Usages to trace dependencies such as pages, entities, sub-microflows and other application logic.

Also search the application for /link/ URLs and check places such as email templates, navigation, JavaScript and integrations. Keep in mind that some links may be called externally from emails, bookmarks or other systems, so these will not necessarily appear in Studio Pro.

For larger applications, the Model SDK can help automate the model-side dependency analysis and generate an inventory.

For estimating the migration effort, I would classify the links based on complexity: simple page/object navigation, links requiring authentication, and links containing additional custom logic. This makes it easier to determine which can be replaced directly with supported URL/navigation functionality and which require some redesign.

Hope this helps.

answered