Currently, the interface used when fetching layouts has no way to deduce instance id of the instance requesting the layout. This prevents dynamic/instance specific logic tied to resources/layouts.

The main goal of this issue is to solve this problem.

Obstacles/reflection

Not all requests for layout for all apps make sense to include instance id

• Adding a flag/boolean property to appsettings to enable an alternate request for layouts that include instance id
• Adding instance id as an optional query param that is added if available

Implementation

• Add a feature flag to appsettings, default false, that enables instance id query on app frontend
• Implement a new backend endpoint receiving instance id
• Expose this instance context to the service without breaking changes
• Refactor app-frontend to use this alternate endpoint

Testing/requirements

• Create a test application with the flag enabled, extending this interface and look up instance related data through DI. E.g. access a data element
• Verify existing implementations of the interfaces do not break
• Verify automated tests target and test the core feature