RefreshCardInMemory Similar method but takes an instantiated Card, which must be already locked. Upon return of this function, the Card must be stored in order for the effects of the Refresh to be saved. (So cancel functionality on Refresh can be implemented usingn this method.) If bForceRefresh is TRUE, then the Card will always be Refreshed. If bForceRefresh is FALSE, then the Signature of the Card and Document will be compared, with the Card being Refreshed only if the Signatures are different. The optional Summarize flag will, if set to TRUE, specify that the document should be summarized now, as opposed to waiting for the indexing which occurs when the card is stored. Asking the Data Source to do this extra work will slow down this call significantly and should only be done if it it is important to have the summary available for editing before the store. The use of the optional DataSourceProvider argument is identical to that described in ImportDocument, above.
IPTDataSource Interface | com.plumtree.server Namespace