Skip to Content
avatar image
Former Member

How to use CBA in FPM OIF applications when CBA driving parameter is determined at initial screen

We tried to adopt EAMS Order and Notification application to drive to the differentadaptation screensdepends on Order and Notification types. For creation mode Order type or Notification type are determined as an input at the initial screen.Problem is that when we try to raiseADOPT_CONTEXT event from initial screenadaptations are not called. Everything works fine when we pass this Order type or Notification type as a parameter in URL but for edit and display mode it is not possible becausethis types can be determined whenapplication is started . It looks thatAdaptation Manager is initializedat the starting point of applicationand when adaptation driving parameter is not determined yet so when weraiseADOPT_CONTEXT event nothing happened . Does anyone know a solution for this problem?. Asa way aroundwe are restartingapplication when driving parameter is determined.It works fine butgives some performance issuesas restarting application takes some additional time.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Dec 11, 2017 at 03:09 PM

    Hello Ajay,

    this is a limitation in the CBA functionality. You can't switch the application's root (or floorplan configuration) after startup.So the root configurations are the configuration for components FPM_OVP_COMPONENT, FPM_OIF_COMPONENT and FPM_GAF_COMPONENT.

    Replacing the roor configuration implies a restart of the application. So the performance penalty can't be avoided.

    This restriction doesn't apply to UIBB configurations. So depending on your use-case it's possible to move the needed adaptations to the UIBB configurations. Especially useful is the option to "hide" a UIBB from inside via CBA. So if you want to have a UIBB A display for context 1 and UIBB B instead for context 2, this is possible even without adaptation of the floorplan configuration:

    Just add both UIBBs to your configuration. Then create an adaptation for UIBB A and set it to hidden for context 2 and vice versa. This way when context 1 is chosen on the initial screen you will only see UIBB B and if context 2 is chosen you will get UIBB A.

    Hope this helps a bit!


    Add comment
    10|10000 characters needed characters exceeded