I would like to embed a view with in a form. In this view i only want to show the response documents for that particular form only.
Is this possible and how would i go about restricting the view?
Any help appreciated. Thanks
Subject: Restricing an embedded view
Ann,
You can use the single category property of the embedded view (you’ll need to categorize the first column of the view to, say, the unique id of the parent document).
As far as “restricting” the view, it’s not really clear from your post what your intention is. Can you elaborate a bit?
Subject: RE: Restricing an embedded view
Hi chuck,
Well i have a main document which contains all the information about an incident. However there maybe multiple ways to treat this incident.
As each treatment option has to be entered into the system in a structured way. I thought that i could use a response form. That way the information would be easily updatable aswell.
Then when the user looks on the treatment option tab they would see a view with all the suggested options for that particular incident.
Subject: RE: Restricing an embedded view
The design you propose is perfectly feasible (as best I can tell from what you’ve said).
However, you might simplify the design as well as improve performance if you try to incorporate all the information into a single form. Tools you will find here let you enter information in a table format, using a dialog to control entry, store the information in multivalue fields, and display it in a table or other repeating format, which can contain as many entries as you require.
While it makes the design of the one form a good deal more complex, you get better performance from having fewer documents and from not using embedded views, and there are other complexities that you eliminate, e.g.:
Updating information on the response documents when information on the parent document changes, particularly if multiple replicas are being used (so that not all documents are necessarily available yet in the current replica).
Dealing with orphaned response documents (someone deleted the parent document but the responses are left behind).
Dealing with response documents that are copied and pasted as responses to a different document (but still contain fields copied from the original document, not matching the new parent).
Those irritating twisties in your views.
How to make full-text searches that match the solution fields, display meaningful document titles without repeating the same document title several times in the view.
Subject: RE: Restricing an embedded view
Hey Andrew,
Thanks for your comments. I did actually try the method you suggested before my post but had trouble with entries not aligning (eg if a description was three lines and a date is only one line. the next entry was out of alignment.) Also i couldn’t edit the entries (eg if there status was changed to rejected)
maybe i was doing it wrong.
Subject: Re: Restricting an embedded view
Yeah – you can’t just put one field in each column of a regular table. You have to construct a table in a rich text field so that each “solution” can have its own row. There are different ways to do this, discussed in this redbook.
Subject: Restricing an embedded view
If you’re using 6.0 or later, create a view that lists each of your main topic documents as well as their response hierarchies. Then go to the form, embed the view and on the second panel click “Show only current thread”. The embedded view will then show only the responses to the currently open document.
Bill Andreas
Senior Designer, IBM Corporation