CON-1480 - Magic string as static value for 'Save as content node' workflow doesn't work.

Created by Stief Dirckx 15 Jan 2018, 19:38:59 Updated by Robert Copilau 17 Jan 2018, 09:44:02

Tags: Unscheduled

Subtask of: CON-1390

I'm using the latest version of Umbraco Forms, version 6.0.6.

I tried using 'magic strings' for static values on the 'Save as content node' workflow. But the result was unpredictable. One value worked {record.IP} but another value does not {record.UniqueId}.

I also reported this on Our: https://our.umbraco.org/forum/umbraco-forms/89999-using-magic-strings

Comments

Warren Buckley 16 Jan 2018, 09:05:50

PR for this is here - https://github.com/umbraco/Forms/pull/176

Test Notes

This came from a forum post originally - https://our.umbraco.org/forum/umbraco-forms/89999-using-magic-strings

  • Create a new doctype (that has a few textstrings but mainly one for storing Form Record ID in)

  • Create a form

  • Create a workflow that uses the Save as Content Node workflow

  • In the field mappings map form fields to document type

  • For the Form Record ID in your doctype use the static value section and use the magic string of {record.UniqueId}

  • Submit a form and verify that a content node is created as expected and the record guid/id is mapped across into the content node property as expected


Robert Copilau 17 Jan 2018, 09:39:26

The node is created upon form submit and all the fields where {record.UniqueId} has been used are now populated with the record guid. Nice job @warren.buckley :), merging.


Priority: Normal

Type: Bug

State: Fixed

Assignee:

Difficulty:

Category:

Backwards Compatible: False

Fix Submitted:

Affected versions: 6.0.6

Due in version: 6.0.7

Sprint: Sprint 76

Story Points: 1

Cycle: 7