Jul 26, 2021 10:51 AM
We are in the process of deprecating the workflow field in favor of a workflow attach functionality within the form field.
We’ve historically had a workflow module field type. When added to a custom module, the workflow field simply displays a list of your existing workflows. Developers almost exclusively used the workflow field in conjunction with forms. We also recently discovered a fundamental issue between forms and the workflow field, where an enrollment trigger for the form was not always created within the selected workflow. For more information about the issue with workflow fields and the decision to deprecate them, check ....
Because the workflow field was used only with forms, we decided to add workflow attach functionality directly inside the form field. With that update, we were also able to make it so that:
Limitations and issues with the old workflow field
The old workflow field had a number of limitations and issues, including:
What if I have workflows attached to forms in the old way?
We’re still deprecating the old workflow field, so if you see cases where a form was attached to a workflow using the old method, we recommend checking that the workflow you previously attached appears in the new UI as an attached workflow like this:
If it doesn’t appear, it means that the attachment didn’t previously work, and you’ll simply need to re-attach the workflow with the new method - within the form field using the “Add form to another workflow” link.
Overall, we’re excited to ensure that the workflow attach functionality works reliably moving forward, while also offering a more robust feature set within the form field.