Re: What are the guidelines for using FVAs vs. Computed Fields?

You may want to consider a trigger that will:

1. Update all node items for the field of interest when the field of interest in the segment changes and
2. Set the field of interest when the "Contained By" relationship changes.

You may have a number of fields you want to do this on, so a trigger becomes more efficient.  A some examples would be:

1. intDocumentID - usefull for qbrs.  I've had some issues trying to use "Document ID" in the past, but can't remember exactly what.
2. Status flags for editability
3. Document Title - so you can see what document the content item belongs to.
4. Assigned User
5. intReferenceID - usefull for qbrs, constraints for sub segments.

One thing to note:  The Document ID field is a little wierd.  Grab the Document ID value from the parent of the delta bean.  Don't try to use getNewFieldValue("Document ID").