How Ad Hoc Correspondence is accessed Figure 7 Accessing Ad Hoc Correspondence in an on-demand scenario How it works 1 A Message ID is retrieved in one of the following ways: – On-demand scenario – In the user interface, an end-user selects a document definition and a data source. A paused Message is created in the Message storage in the runtime repository and the Message ID is returned to the hosting system via the SSSP application. See Accessing the SSSP application. – Batch scenario – In Correspondence Reviewer, an end-user opens a document for editing. The paused Message already exists in the Message storage and the Message ID is sent to hosting system via the SSSP application. 2 A request, including the Message ID, is sent to the SSSP application. The request is passed via the service gateway to the Message storage. 3 In the Message storage, the paused Message is identified and the corresponding document is returned via the service gateway and the SSSP application. 4 Ad Hoc Correspondence opens and previews the document. Each time the end-user edits the document, the paused Message is updated in the Message storage and a new preview is generated. 5 When the end-user has closed or submitted the document, any forward parameters specified in the URL direct the end-user to the next application. For example, back to the hosting system. Note: If no forward parameters are specified, the document is closed but Ad Hoc Correspondence remains in the browser.