guides:apex_repositories_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| guides:apex_repositories_guide [2017/12/07 21:51] – administrator | guides:apex_repositories_guide [2020/03/02 17:41] (current) – brett.zamora | ||
|---|---|---|---|
| Line 28: | Line 28: | ||
| Information about the Retrieved By County queue will be placed here. | Information about the Retrieved By County queue will be placed here. | ||
| + | |||
| Line 33: | Line 34: | ||
| - | As the name indicates, this queue contains a list of transactions that are currently in Returned By County status. When you click the Returned By County list item in the Remote Payloads section of the Repositories container, the Returned By County detail panel is displayed in the Detail Pane on the right side of the APEX UI as shown below: | + | {{page>[:guides:apex_repositories_returned_by_county_guide& |
| - | + | ||
| - | + | ||
| - | {{ :guides:images: | + | |
| - | + | ||
| - | + | ||
| - | The following grid describes each of the number items in the preceding diagram: | + | |
| - | + | ||
| - | + | ||
| - | {{tablelayout? | + | |
| - | ^ Item# ^ Description ^ | + | |
| - | | 1 | To display a list of transactions that are currently in Retrieved By County status, click the item labeled Returned By County in the list of Remote Payloads. The item selected will be highlighted. | | + | |
| - | | 2 | When a Remote Payload status name has been selected, the Detail Panel will be displayed and the status name will be visible at the top of the panel. | | + | |
| - | | 3 | This 'minus sign' icon (' | + | |
| - | | 4 | When the transaction list is initially displayed, the document list for each transaction is hidden. To expand the document list, click the 'plus sign' icon (' | + | |
| - | | 5 | This icon is used when a document has been recorded. | | + | |
| - | | 6 | For recorded documents, the recording information is displayed as shown. | | + | |
| - | | 7 | This icon is used when a document has been rejected. | | + | |
| - | | 8 | For rejected documents, the reject information is displayed as shown. | | + | |
| - | | 9 | To view/print a recorded document, select a row by clicking it and then click the ' | + | |
| Line 70: | Line 52: | ||
| - | CeRTNA uses a pair of ' | + | {{page> |
| - | + | ||
| - | The following folder/ | + | |
| - | + | ||
| - | {{tablelayout? | + | |
| - | ^ Folder/Path ^ Description ^ | + | |
| - | | {base}\ | Used by the APEX Sender (Note 1) | | + | |
| - | | {base}\RETRIEVED\ | Used by the APEX Retriever (Note 2) | | + | |
| - | | {base}\PROCESSED\ | For files that have been sent. (Note 3) | | + | |
| - | | {base}\INVALID\ | Folder for XML files that cannot be sent. (Note 4) | | + | |
| - | | {base}\APEX_WORK\ | Used by APEX Sender for lock files. (Note 5) | | + | |
| - | | {base}\APEX_WORK\RETRIEVED\ | Used by APEX Retriever for lock files. (Note 6) | | + | |
| - | | {base}\APEX_WORK\PROCESSED\ | Used by APEX Sender for lock files. (Note 7) | | + | |
| - | | {base}\APEX_WORK\INVALID\ | Used by APEX Sender for lock files. (Note 8)| | + | |
| - | + | ||
| - | The following table contains more descriptive notes for each of the folders referenced in the previous table: | + | |
| - | + | ||
| - | {{tablelayout? | + | |
| - | ^ Note ^ Comments ^ | + | |
| - | | 1 | The APEX Sender looks in this folder for XML files that have been placed here by Agent or County interface programs or by the APEX Direct-Entry UI. | | + | |
| - | | 2 | The APEX Retriever process places XML files in this folder thereby ' | + | |
| - | | 3 | After the APEX Sender process finishes sending an XML file to the server, it moves the file to this subfolder. | | + | |
| - | | 4 | Part of the ' | + | |
| - | | 5 | APEX processes use a locking mechanism to assign a Sender thread to a specific XML file. This folder holds the lock files created by the APEX Sender processes. (This folder is intended to be used exclusively by APEX.) | | + | |
| - | | 6 | APEX processes use a locking mechanism to assign a Retriever thread to a specific ERDS or G2G transaction. This folder holds the lock files for the APEX Retriever processes. (This folder is intended to be used exclusively by APEX.) | | + | |
| - | | 7 | This folder holds lock files for the XML files that are being moved to the PROCESSED subfolder. (This folder is intended to be used exclusively by APEX.) | | + | |
| - | | 8 | This folder holds lock files for the XML files that are being moved to the PROCESSED subfolder. (This folder is intended to be used exclusively by APEX.) | | + | |
guides/apex_repositories_guide.1512683493.txt.gz · Last modified: by administrator
