System to System Requests

ATIPXpress 10.5 introduced the ability for interaction between multiple ATIPXpress systems, allowing organizations to employ a "high-side/low-side" architecture to protect classified data while sting providing comprehensive responsive documentation for information requests. This is known as System to System (S2S) request processing.

For example, an organization may employ an Unclassified environment, exclusively hosting documentation labeled as Unclassified, while simultaneously utilizing a Classified-side environment to protect access to Classified information. System to System Requests allow a user in the Unclassified side to submit a request for documents to the Classified side. This request duplicates the metadata from the Unclassified request on the Classified side, allowing a processing agent with access to Classified materials to provide responsive documents. These documents can then be provided for inclusion with the final delivered documents.

For ATIPXpress applications with S2S processing enabled, there are some changes and additions to the user interface and request process.

S2S Request Processing

S2S Requests are completed according to each organization's requirements and processes, however a basic overview of the process is outlined below.

NOTE: The steps below are provided as a high-level example, and may not each user's individual processes and environment.

1. A request is received. The request is logged in the low-side environment (containing no classified data) just like a normal request.

2. If the Request Type is enabled for System to System Requests, a button appears on the Request Information page as shown in the following example:
   

3. Click Submit Request to X (ClassNet is the system name for the connected system in the example above, but this is dependent on configuration). A verification message appears as shown below. Click OK to proceed.
   
   

4. After submitting the request to the connected system, another pop up confirms that the request was submitted. Click OK to dismiss.
   
   

5. The Request Information page refreshes, with some changes to the UI. Notably, the Submit Request to X button is gone, as this action is complete. In addition, a new button appears next to the Request Number.
   
   

6. Clicking this button pops up the System to System Request History, as shown below:
   
   
   

NOTE: For details on the System to System Request History, see the S2S Request History section in this topic.

7. In the System to System Request History, the following actions are logged:
   
   

1. Job created to submit the request to the connected system

2. Request submitted to the connected system

3. Request created in the connected system (with the ID of the connected request provided)

8. In addition, the connected request is added as a Sub Request under the original request in the low-side system. See the example below.
   
   

9. In the connected (high-side) system, search for the newly-created request using the ID shown in the System to System Request History. The Request Information screen will show the same metadata provided on the original low-side request.

10. On the high-side, process the request and provide responsive documentation, adding documents to the Request Folder as needed.

NOTE: If Documents are not delivered to the low-side system as part of the application processing. Documents must be delivered manually, as noted on the Document Delivery screen below.

11. When all actions on the high side are complete and the request is closed, processing can return to the original low-side request. Complete all processing activities in the original request before delivering documents.

NOTE: Connected requests must be closed before the original request can be closed. Users will be unable to close a request when a connected request is still open in the connected system.

12. When closing the request at the Close Request screen, documents utilizing S2S processing have an additional option. The screen below shows the Note button adjacent to the Number of Pages Released/Reviewed fields. Click Note to pop out a window with the number of documents from these counts coming from the high-side system:
    

System to System Request History

A primary change to the UI when processing S2S Requests is the addition of the System to System Request History button. This button is available on any Request that is (A) an eligible request (the Request Type is configured for S2S Requests) AND (B) the Request is submitted to a connected system.

When an eligible request is created and submitted to the connected system, the System to System Request History is available via a button next to the Request ID. This button is highlighted in the following image:

NOTE: The history is also available via the More Actions menu in an eligible request, as shown below:

Clicking this button pops out the System to System Request History screen, as shown in the sample below:

This history includes a listing of all actions taken regarding system to system processing. Any data transferred between the systems is captured and detailed in this history. In addition to the basic request information, the following details are included for each logged entry in the history:

There are also options to Refresh the history, if actions were taken that have not been included on the log. This refreshes the history to display any recent activity. Additionally, click Close to close this window.