Custom component setup for running application

Hi ​@peter.bongers,

Could you clarify what you mean by "two different urls... not in the same proxy"? In the meantime, here's what's possible today if you want to stick with a setup where the custom component is hosted as an external source.

The Docs mention the following:

To refer to different versions of the custom component, you can include {metasource} and {application} variables in the location. Depending on how the application is started, the variables will be resolved to either the Software Factory or IAM, and to the runtime configurations' application ID or alias in the Software Factory, or the application ID or alias in IAM.

In this way, you can host different versions without having to change the custom component reference in the model by using /custom/{metasource}/{application}/my_component.html:

• for production, at /custom/iam/myapp/my_component.html
• for development, at /custom/sf/myapp/my_component.html
• a new branch version at /custom/sf/54/my_component.html

To add on to what the Docs mention: only these two placeholders are supported, no SQL or other expressions. And both resolve to a path segment, not a domain. So if your two URLs differ by domain rather than by path, this won't get you there; there's currently no formal way to make the location field resolve to a different host.

Assuming I understand you correctly, an alternative that avoids this problem altogether: host the custom component from the model itself instead of as an external source (upload it under User interface > Custom components). In that case Universal UI serves the component directly as part of the application, so there's no separate URL/proxy involved at all. If the two applications need different versions of the component, you can still differentiate using {application} in the entry point.

Jeroen,

Thank you for the answer

Is it possible to create a new variabele for the subdomain to use?

Peter