Zum Hauptinhalt gehen

Promises and Custom Activities

Kommentare

1 Kommentar

  • Tom Neer

    To further add on to this, we are noticing that activities are not executed in order. For example, we have a Set Form Element Item Property activity, in a sub-workflow, before a Loop. However, the Loop is executed before the Set Form Element Item Property. Why is the order of execution not respected? Further looking into this it seems that no matter where we put the Set Form Element Item Property in a workflow, it is always the last activity executed.

     

    Looking through the activities, this seems to be issue in communicating between a sub-workflow and a form, hence the Propagate Form Event activity. This is what we want to do but we are after more than the "Submit" button which this activity seems hard coded only to submit. Can this be extended to all form elements so we can dynamically update a form during code execution?

     

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.