Skip to main content
Question

Change ApplicationUrl source from IAM to SF for custom components depending on the environment

  • August 24, 2026
  • 1 reply
  • 8 views
T
Rookie

I am working on a custom component that receives a payload from Thinkwise containing an ApplicationUrl.

The custom component uses this ApplicationUrl to fetch data from Thinkwise. However, the ApplicationUrl that is provided in the payload currently points to the IAM metasource by default, while my custom component needs to fetch data from the SF metasource in my development environment.

For example, the payload contains something like:

ApplicationUrl: https://.../indicium/iam/...

but for my custom component I need:

ApplicationUrl: https://.../indicium/sf/...

I don't want to hardcode or manually replace /iam/ with /sf/ in the custom component, because the component should be reusable across different environments.

Is there a Thinkwise configuration or setting that determines which metasource (sf or iam) is used when generating the ApplicationUrl in the payload?

If so, what would be the recommended way to configure this so that the custom component receives the correct ApplicationUrl for the environment it is running in?

Or is there another recommended approach for custom components to determine which Indicium metasource they should use when fetching data?

    1 reply

    T
    Moderator
    • Tim Scholten
    • Moderator
    • August 24, 2026

    Hello TomZ, in what context are you running your application?

    Did you launch the application e.g. using the Launch Application button, and when you navigate to your custom component it'll give you /indicium/iam/..?

    Or do you want, when you synchronize your application to IAM, that it’ll use the model + branch of the synchronized application to gather the /indicium/sf/.. variant when available?

    Terms & ConditionsAccessibility statement