11 results found
-
Remove workflow syntax prompts where non-applicable
In some cases, the workflow builder suggests syntax prompts that are non-applicable to the section in question. For example, with a Get Images Step the image field name should be copy/pasted exactly as is (ex:"Image", not listed in the variable syntax (ex: "#{trigger.Image}"). Similarly, when referencing a SQL Table in the SQL Upsert Row step, you just need to copy/paste the name of the table in SQL. The workflow shouldn't prompt you to enter GoFormz outputs in the variable syntax.
4 votes -
Drag & Drop Workflow Steps
For long workflows it would be useful to be able to drag and drop workflow steps, rather than needing to push the up and down buttons.
3 votesYou can now drag and drop steps in the Workflow Editor.
-
Stop having 'All Templates' be the default template selected when creating a workflow.
I maybe understand if someone is creating a Workflow from the 'create workflow' button in the workflows section, but if someone is on a particular template, and they go to Workflows from the template section, any subsequent workflows should automatically select that template.
Anywhere that 'All Templates' is default should have some sort of checkbox to confirm that you want this workflow to trigger on every single template.
2 votesIf on a particular template, and you go to Workflows Recipes from the template section, any subsequent workflows will automatically select that template in the trigger.
-
SharePoint DataSource Sync
Ability to create a workflow that pulls site information from Sharepoint to automatically update a DataSource on a daily schedule.
11 votesNew SharePoint Workflow Command "Get Excel Table" allows you to sync your SharePoint table. This step requires ProServices training/support.
-
Adding Template Name as an Output for Workflow Triggers.
Adding Template Name as an Output for Workflow Triggers.
3 votes -
Allow for semicolon to be used as a separator in Send Email action for To, CC, BCC
Suggestion make ; and , acceptable separators in all fields (TO, CC, BCC)
When emailing as part of a workflow if using a ; to separate email addresses in the CC field the workflow will fail. using a , will work. When using a ; in the TO field the workflow does not seem to have any issues.
This is an issue for us as we also integrate with SendGrid and it requires a ; and not , as a separator so a workaround for us means changing our formats based on what we are integrating with at the time.
1 voteThe Send Email workflow action now allows for semicolon to be used as a separator in To, CC, & BCC.
-
Workflow Folders
Ability to organize Workflows into folders.
13 votesWorkflow Folders is now available on all accounts with Workflow access. Learn more here: http://help.goformz.com/en/articles/7128447-workflow-folders
-
Workflow File Transfer
Ability to transfer attachments from one to a newly created form utilizing Workflow.
2 votesAttachment Fields can now be referenced when newly creating a form utilizing Workflow.
-
Workflow Editor - when selecting custom, allow for a custom input without selecting anything from the drop down
When selecting custom, allow for a custom input without selecting anything from the drop down. Currently you have to select something from the drop down, clear it out, then you can manually type.
1 voteBug fix released that was preventing users from selecting custom and automatically typing in input.
-
Workflow Versioning
Alter a current live workflow and publish that as the new version of your workflow. This would allow you to reference previous versions of the workflow to identify what has been updated.
2 votesThis feature is now released. Learn more here.
-
Form Created Trigger
Trigger for Workflow based on a draft of a form being created
0 votesForm Created Trigger is now available in Workflow. Requires ProServices assistance at this time.
- Don't see your idea?