Make unmapped fields in external forms accessible from workflows
A
Andrew Gardiner
Currently unless a field on an external form is named the same as a HL field, or a custom field has been created to match an external form field name - form data is captured as unmapped. It appears in the form submission detail pane - but is not available to use.
If we could have the same behaviour as the Advanced Workflow action, where the response payload JSON fields are available to the following steps in a workflow, this would allow much more flexibility.
Part of the appeal of the external tracker is that we can just "leave alone" the customer's existing forms, and not have to edit them to change fields names etc.
Also, we have experienced some forms which are capturing a large amount of data on the customer's form - of which only a small proportion needs to be in the HL database. The remaining unmapped fields could be appended to a note on the contact record, instead of adding dozens more custom fields to the database.
Log In