I have set up a collaboration job with the following steps:
I could see that the task has the initial XML as submitted form A XML. However, after saving the task, it clears all elements that does not in exist in Form B.
submitted form A XML is:
Looking at initial task XML TM Transaction Details History tab, it is the same as above, which is as expected.
However, after saving the task, the task XML turns to:<SmartForm><Email></Email></SmartForm>
it clears FirstName and LastName from form B XML as there is no bound field for these two fields in form B.
How can I prevent the clearing of the XML elements without having bound fields in the form?
Logged as TPD-4494
One way to do that is to use a 'Data Field' on second or subsequent forms.
On the second form, add a Data Field with the same name as a field on the first form you want to retain.
Make sure the original field and the new data field both have 'Include in submission data' checked.
The data field contents should carry the original field's value through to the submission XML.
This would work, to bind the data to fields in the second form. However, I would still need the (not bound) XML elements to retain in the submission XML.
My use case is that after submitting the second form, I am creating a third task which would need that from first and second form combined.
We'll be logging a TPD for this to be addressed. I'll post the link here when it becomes available.