Aller au contenu principal

Ability to run a workflow with user inputs (form) on startup

Répondu

Commentaires

1 commentaire

  • Cam Barnard

    Hi Denis - some good questions in here.

    If you are looking for maximum performance, we would normally use the "application initializing" event to select the correct layout (no user input) so that you aren't loading the app with a specific layout, and then re-loading a different layout.

    Your original workflow approach would likely work if you used the "map initialized" event on the map component. The app loads completely, then the user is prompted with a question, then the result applied.

    The dialog could also work. It is possible to make a dialog visible by default, but not simple via the Designer interface. The "initially hidden" control we show in Designer works for the vast majority of stuff but isn't a completely accurate representation. Behind the scenes there are three states "default behavior, force on, force off". For most components the default state is to show the component. The toggle switches between default and force hide. For dialog components (a bit of an exception) that gives you a choice between default (Which doesn't show) and force hide (which doesn't show). You can use item manager to update the layout component for dialog manually and it will show when the app is loaded. e.g. 

    <dialog id="dialog-a2ab24b9" config="92ea4cdb-9011-4265-9368-c1ab533808e1" active="true"/>
     
    A little while back we added some new commands and operations around layouts. One of those was to get the currently selected layout from the viewer.
     
     
    0

Vous devez vous connecter pour laisser un commentaire.