This functionality is beneficial for B2Bi Business Process performance when document extraction results in a large number of split documents. BP execution can be slow if many split documents are written to Process Data which can be avoided by using this parameter in conjunction with the for each document service.
Here is the IBM documentation from native SBI Document Extraction service:
Specifies whether split documents will be stored in process data or in the business process context. Valid values are:
The PDToProcessData parameter can be used to improve performance by reducing the overhead associated with persisting large process data information.
The major performance improvement is realized at the current step (Document Extraction) and each subsequent step by persisting a much smaller process data which does not contain multiple split documents. By using the For Each Document service in conjunction with PDToProcessData = No, only the current document is on process data. this avoids repetitive writing of non-current documents. Once documents are in the SplitDocs array, they can be retrieved only by using the For Each Document service.
How will this idea be used?
This functionality would help to avoid performance impacts of writing many split documents to SBI's Process Data after document extraction.
|What is your industry?||Healthcare|
|What is the idea priority?||High|
|Link to original RFE|