This content has been marked as final. Show 4 replies
You can definitely use the same schema for different XDPs using different fields.
The part you're missing (I think) is to assign the data from the FormA variable to the FormB variable you're probably using on the second user operation.
You're probably using two user operations where
for user A, you set the input and output mapping to FormA variable and
for user B, you set the input and output mapping to FormB variable.
The problem is there is no place where you specify that the data element for FormB has to equals the data element from FormA.
To achieve that, you can have an intermediate setValue operation that will make sure to set the data element of the FormB variable to FormA. Something like:
/process_data/xfaFormB/object/data = /process_data/xfaFormA/object/data
This way your second XDP contains the same data as the first XDP.
Something else you can try (I've never tried it myself) is to set the Output Form Data (from Form Data Mappings) to be the Form B variable on the first user operation. That might work and would be a better solution. I'll give it a try on Monday.
Let me know.
yes Jasmin, that makes sense. I shall try that. thank you.
I want to mention though, in LC-7, I didn't need to do the SetValue. I could use one Form Variable, and at the User QPAC, it has an option for me to select another form. But I can't find this feature in ES anymore...
That LC 7 option might be replaced with the second option I just explained(setting the output Form Data from Data Mappings).
I tried the "SetValue" method, and it worked. Thanks Jasmin.
I also tried the "Output Form Data mapping", but it did not work. Somehow the User task #2 displayed Form A, even though its "Input" form variable was set to Form B. And the Output form mapping was set to Form B at task #1 as well.
But that's ok. As long as the "SetValue" works, it's fine. Because, suppose I have multiple routes coming out of Task #1, and there are multuple User tasks (each uses different forms sharing the same XSD) downstream, I think I'll still need to use the "SetValue" method anyway.
I still hope ES could merge this extra SetValue step into the User task property sheet...much like what LC-7 had.