At run time, a global app that you build with module-specific app logic retrieves the app user’s subscribed_modules and endpoint_urls from the host information and runs based on it.
FAQ
How can you feed the subscribed_modules and endpoint_urls information to your app when you simulate the app for testing purposes?
As an app testing feature, we offer the System settings page. On fdk run, the System settings page is populated with the modules registered in your app manifest. You can select the modules for which you want to simulate your app run. Based on the module selection, the Enter account URL section is displayed. You can enter the URLs. The entered URLs play the role of currentHost. In the backend, from our internal mapping, we derive the subscribed modules that are present in the app manifest and the endpoint URLs. During local testing, the app is deployed for all such derived modules.
Sample System settings page with modules registered in the manifest
Sample System settings page with provision to enter account URLs