Defaulting Composite Apps via App Setting

Nextworld Platform
1

Is there a way to default a composite application via an app setting so one can use 1 composite app and 2 menus (different app settings) to set the default app?

Example:

  • Composite App: COMPOSITE X
  • Apps on Composite App: APPA and APPB
  • Menus: APPAMenu and APPBMenu
  • APPAMenu should open COMPOSITE X with APPA being active/visible.
  • APPBMenu should open COMPOSITE X with APPB being active/visible.
2

This is currently supported, but it’d be great to get an idea entered for this.

If your use case is for a Guided Composite Application, then there is a workaround you could implement to get this desired behavior. If I have the follow Guided Composite app:

  • GuidedCompositeApp
    • InitializationStepApp
    • StepAppX
    • StepAppY

I can accomplish the behavior your describing by:

  1. Adding a field to my InitializationStepApp (and the backing table for the GuidedCompositeApp).
  2. Then set the field via the App Setting on the Menu for the GuidedCompositeApp.
  3. Add a Form Init Logic Block to my InitializationStepApp that:
    1. Checks the value that was set from the app setting
    2. Conditionally hide the steps you want to skip based on that value
    3. Queue App Link with a “Complete Current Step”
2 Likes