1
0
-1

We are working on our first form bundle.

Things are somewhat complicated by the fact that we are not able to change the xml of one of the forms in the bundle and another form has somewhat complex logic that affects visibility rules on the receipt and collaboration.

I'm hoping someone will be able to share their experiences with bundling and what is the most efficient way to go about it.

The questions that I'm struggling with are:

  1. Is there any real benefit to adding most/all of the shared fields/blocks to the parent form? I think it would make it a smoother experience for the customer, but I'm conscious of then having to edit 1 more form if any changes need to be made to those fields in the future.
  2. Because of the limitations with the form xml of 1 form having to remain unchanged, we are using the data extracts to populate fields. But we are about to do this in Maestro and have found data extracts a bit flakey at times. Is there an advantage to using xml instead? And is this were entities could be helpful as an alternative to using absolute binding to match xpaths?
  3. Is there an easy way to hide or make read-only those fields that are being pre-populated from other forms in the bundle? We don't want to have to add visibility or editability rules to each of those fields individually, especially for the more complex forms.

Thanks!

Lin

    CommentAdd your comment...