Document Rendezvous

Document Rendezvous can be used to suspend a work process until a document or documents matching the criteria specified in the wait node rules enter the system. The work process is automatically resumed upon the receipt of the required document(s).

Common Use Cases

Document Rendezvous is a common requirement for practically all Business Processes that are initiated by or otherwise rely on documents.

Use Cases

Use cases are for example:

• A process always requires a request for documentation to be sent out at a specific point in the process and the documents received back in to the system before the process can continue.
• A process may sometimes be missing documentation and a request for the missing documentation must be sent out and the document(s) received back in to the system before the process can continue.

Business Use Case

The following workflow shows a typical Business use case scenario:

• A Process Instance is initiated to fulfill a customer request.
• The processor working the customer request in Stardust discovers that one or more required documents are missing, and the request cannot proceed without them.
• The customer is contacted to obtain the missing documents.
• The customer sends back the missing documents.
• The missing documents enter Stardust (typically via email or scan) and must rendezvous with the original in-flight Process Instance.
• After the documents rendezvous with the in-flight Process Instance the request can continue.

Example Use Case

The following diagrams shows a Claims Processing workflow using Document Rendezvous activities:

Figure: Claims Processing Example Workflow

Setting up the Route Activities

The Document Rendezvous activities have to be set up as follows:

1. Create a separate Route Activity (Task = None) for each document that is requiring rendezvous.
2. Begin the Activity ID of each Route Activity with the term DocumentRendezvous, e.g. DocumentRendezvous_DisabilityCertificate. Do not include spaces in the ID!
3. Mark each of these Activities as Hibernate Initially

Figure: Route Activity configuration

Setting up the Workflow Pattern

1. Set up an In/Out Mapping for the Specific Document that the Route Activity is waiting for.
2. Set up Gateways/Transitions to define the logic of which documents must be present before the Process Instance can continue.
3. Implement the Document Triage screen to provide an interface for rendezvousing incoming documents with existing in-flight Process Instances. Refer to chapter Document Triage for details on the Document Triage concept.

Note that Process Attachments cannot be set up for rendezvous using the above pattern. Each rendezvous document must be a specific document.