[xpost from livecycle google group]:
So we are designing lots of forms and orchestrations, so obviously we have many re-usable components that are turned into fragments. I'm discovering that you cannot associate a schema field definition with a field that is contained within a fragment on the form.
So I'm finding that we are changing our process to first look at the orchestration, and then, if a field needs to be referenced in an orchestration, then we have to make sure that the field is NOT contained in a fragment so that we can hook up a schema definition to that field (so that it's easy to refer to the field via a process variable)...
Imagine having a block of fields that make up a beautiful fragment, only having to leave out a field because it's needed in an orchestration. Yuk, bleh, nyet, hooey...
If I'm mistaken, please correct me. ;-)
Thanks,
Elaine