Stardust provides an index screen for a simple triaging of incoming documents. For details on the general concept of Document Triage in Stardust, please refer to chapter Document Triage in the Stardust Concepts Document Triage in the Concepts part.
Note
This functionality is technology preview only.
It may not be functionally complete and is not intended for production use!
Section Preparing an Indexing Activity required for Document Triage describes the requirements for using the index screen.
The index screen consists of the following panels:
Refer to section Document Triage Example for an example on how to set up a workflow to perform a Document Triage.
To invoke a Document Triage, you require a UI Mashup application activity using specific resources. For details on UI Mashup applications, please refer to chapter UI Mashup Application in the Business Process Modeling Handbook.
The technology preview jar provided for Document Triage contains UI Mashup resources to invoke the Document Triage index screen. To create a UI Mashup application activity using these resources, perform the following steps:
${serverBaseUrl:String}/plugins/document-triage/documentAssignmentPanel.html
http://<server>:<port>/<context-root>/plugins/document-triage/documentAssignmentPanel.htmlFor example:
You can find a completed example model here:
Once the index screen is displayed, a drop-down list is provided to select a Business Object.
Figure: Select a Business Object
Selecting a Business Object populates the Process Data panel accordingly.
Figure: Data Panel populated for Business Object
For details on using Business Objects, please refer to chapter Managing Business Objects (Technology Preview).
In the entry fields you can enter business data from the incoming documents and perform a lookup into a record keeping system.
Figure: Data Entry Fields
Tabbing out of a field where you entered a value, initiates a lookup against a record keeping system. The results are returned in a table below.
Figure: Data Panel Table
Clicking a row in the table selects that participant record and initiates a search for Pending Activities using this record set. The results of this search are populated in the Pending Processes and Activities Panel tree. However, it is not mandatory to select a record set.
Note
Each new search resets the Pending Processes and Activities tree.
A Thumbnail panel is provided to support navigating the documents associated with the in-scope Process Instance and also to support drag operations for adding documents to both, the Pending Processes and Activities Panel and the Startable Processes Panel.
Figure: Document Thumbnails Panel
A checkmark shows if the document, or all pages of the document, has/have been assigned.
Figure: Checkmark indicating that Document is assigned
In case a document has more than one page, you have the option to expand and collapse the pages. Click the expand/collapse icon in the upper right corner of the document thumbnail to expand Document pages.
Figure: Expand/Collapse Document pages
The single pages of the Document are now listed below the Document name.
Figure: Expanded Pages
You have the option to re-order or reverse the order of pages in a document.
To re-order pages in the document, simple drag and drop pages to a desired location in the Thumbnails document.
To reverse the page order of documents having more than one page, click the Reverse Page Order icon in the upper right corner of the document.
Figure: Reverse Page order
Clicking a document or page in the Thumbnails panel opens or updates the Document Viewer Panel with that document or page.
Documents can be dropped onto Process Attachments or Specific Documents to create a document reference in that target process instance. Refer to the Process Attachments or Specific Documents sub-sections of sections Pending Processes and Activities Panel and Startable Processes Panel for details on dragging and dropping documents to these nodes.
Splitting multi-page documents is supported for TIFF and PDF files.
To split a document, select the thumbnail pages of the document that you want to split and drag it to one of the following nodes:
This will create a new document.
A dialog opens to ask if you like to create a new document with the dragged pages.
Figure: Confirm splitting of document
A checkbox is provided to decide if the pages from the original source document should be deleted. Click OK to confirm or Cancel to cancel the split process.
Note that the new document resulting from the split will be saved as a TIFF file. The new document will be created with the selected document pages in the target node and added to the Thumbnails panel.
Figure: New Document created from split pages
A document viewer panel is provided to render document content. Clicking a document or page(s) in the Thumbnail panel opens the document or page(s) in this embedded viewer.
Note that clicking a document in the Pending Processes and Activities Panel or Startable Processes Panel tree opens it in a separate Document Viewer tab and not in the Document Viewer panel.
Figure: Document Viewer Panel
In case a document is not supported, a "unsupported file type" message is displayed in the viewer.
The document toolbar supports:
The Pending Processes and Activities tree lists the process and activity instances matching the participant data that are waiting for documents.
It supports document rendezvous by allowing documents to be dragged from the Indexing Activity of the Process Instance (document thumbnails) to process instances or activities that are waiting for these documents.
For details on the Stardust Document Rendezvous concept please refer to chapter Document Rendezvous in the Stardust Concepts Document Rendezvous in the Concepts guide.
Figure: Pending Processes and Activities Panel
A checkbox is provided to choose if to display or hide completed process instances.
Figure: Show/Hide Completed Processes
The following tree nodes are displayed:
Each top-level node represents a Process Instance that has at least one Activity that is waiting for one or more documents.
An option to launch Process History is provided on the right side of the process instance node.
Figure: Launching Process History
The Descriptors node displays the descriptor key value pairs in a comma separated list.
Activity nodes are listed for each Activity Instance that is waiting for documents. The specific document that the Rendezvous Activity is waiting on appears as a sub-node under the waiting Activity and it is indicated as not filled.
Figure: Rendezvous Activity nodes
When a document is dropped onto a waiting Rendezvous Activity node the document is immediately added and the waiting activity is completed.
Figure: Dragging a document to a Rendezvous Activity node
The node of the completed activity is removed from the tree.
Figure: The Rendezvous Activity node is removed.
For details on the Stardust Document Rendezvous concept please refer to chapter Document Rendezvous in the Stardust Concepts Document Rendezvous in the Concepts guide.
All specific documents for the Process Instance are listed as Specific Documents nodes.
When a document is dropped onto a Specific Document node the document is immediately added to the Process Instance.
Figure: Dragging a document to a Specific Document node
The specific document icon is filled to indicate that a document is added.
Figure: Filled Document icon
Note that this does not trigger any Activity completion!
Once a specific document is filled, that document is locked and is no longer a drop target.
Moving the mouse over a document opens a tooltip with details like content type, name and number of pages.
Process Attachments nodes provide a drop target for adding documents to process attachments via drag-and-drop of the document thumbnails.
Dropping a document onto the Process Attachments node immediately adds that document to the Process Instance as a process attachment.
Figure: Dragging a document to Process Attachments
Figure: Select a
All process attachments in the Process Instance are listed.
Moving the mouse over a document opens a tooltip with details like content type, name and number of pages.
The Startable Processes tree contains all processes that the currently logged-in user is authorized to start.
The following tree nodes are displayed:
Figure: Startable Processes Panel
Each top-level node represents a startable process in Stardust and is used to stage new process instances.
When a Document is dragged onto a Startable Process node as described in section the following happens:
Note that only one Startable Process Instance can be staged per Startable Process at one time. If a user wants to create multiple Process Instances in the same Process Definition, he must stage and submit each of them one at a time.
Each specific document has its own document node and is indicated as either filled or not filled. See section Specific Documents for pending processes and activities for more details.
The Process Attachments node is a container node for adding process attachments. A leaf node is displayed for each document in process attachments. Please see section Process Attachments for pending processes and activities for more details.
To prepare an example workflow to demonstrate Document Triage, we create a model containing two processes, one for Document Rendezvous waiting for incoming Documents, and one for the Document Triage, containing a UI Mashup activity for indexing.
You can also find a completed example model here: ClaimsProcessing.xpdl.
In the model, create the following data:
To prepare a simple process with a Document Rendezvous, which will be available in our document triage, do the following:
The following screenshot shows an example Document Rendezvous process for Claim processing:
Figure: Claims Processing Example Workflow
For details on the Document Rendezvous concept in general, please refer to chapter Document Rendezvous in the Stardust Concepts Document Rendezvous in the Concepts part.
To invoke a Document Triage, we require a UI Mashup application activity as described in section Preparing an Indexing Activity required for Document Triage. Perform the following steps to create a process including such an activity:
The following screenshot shows an example Document upload and indexing process:
Figure: Example Document Upload and Indexing process
To run your Document Triage example:
Figure: Example Index Screen