Content Presenter Dynamic Configuration

The simple type of properties can be coded to enable the reference binding to take the dynamic values at runtime. The properties like enum type can't be reference bind with the current version of the product OMI's framework.  You may want to reach out to the product portfolio for this enhancement to the app. Having said that, there is source code made available for this App as part of the SDK, which means you can customize the app to enable the data binding on the properties as per your needs, compile and use it as your own App :-)

Nenad Kovacevic said:

instead of configuring multiple layouts with different configurations.

However, I do not understand, how enabling the dynamic data binding reference would save you from configuring multiple instance of the App. I am curious to understand what specific scenarios you are trying to achieve in your case.

Let me describe the goal that we are trying to achieve and my thought process.

There is an area hierarchy, and each area contains some real-time KPI dashboards. These dashboard vary in sizes given the nature of KPIs being presented varies between areas. For showing these KPIs, idea is to use Content Presenter app. It would be linked in each of the areas and configured as to display KPI dashboards from areas direcly below the it.  

• Root
  • Level1
    • Sublevel1
    • Sublevel2
    • Sublevel3
    • Sublevel4
    • ...
    • SublevelX
  • Leve2
  • Level3
  • Level4

So from, the example above, when navigating to Root area in OMI navigation hierarchy, one would be presented with a screen that shows 4 KPI dashboards from leves 1-4 through Content Presenter app.

Likewise, when navigating to Level1 area in OMI navigation hierarchy, one would be presented with X KPI dashboards from sublevels 1-X through Content Presenter app.

Dynamic data binding would be used, for example, to configure number of rows and columns that Content Presenter app would try to optimize for. So, at root level, Content Present app's rows and columns properties would be bound to appropriate set of attributes in the root area (for example, 2 rows and 2 columns given that there are 4 dashboards) etc.