guides:apex_user_guide
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| guides:apex_user_guide [2017/11/02 22:32] – [APEX Reports Module] brett.zamora | guides:apex_user_guide [2022/11/10 18:22] (current) – brett.zamora | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| - | ==== Overview ==== | + | This document is a consolidation of the information that is contained in several other smaller documents. It contains information about how to install APEX, getting around the user interface (UI), and detailed information about the various modules that are available in APEX, for example the APEX Transport module and the APEX Reports module. |
| + | |||
| + | |||
| + | ===== Overview | ||
| Line 8: | Line 11: | ||
| * Secure transport of XML transaction files. | * Secure transport of XML transaction files. | ||
| - | * Reporting | + | * Reporting |
| - | * Administration | + | * Administration |
| - | * Direct Order Entry (Work in progress.) | + | * Direct Order Entry |
| Other lower level features include: | Other lower level features include: | ||
| Line 22: | Line 25: | ||
| - | ==== HW & OS Requirements ==== | + | ===== HW & OS Requirements ===== |
| {{page> | {{page> | ||
| - | ==== APEX Installation | + | ===== APEX Installation ===== |
| - | + | ||
| - | + | ||
| - | APEX is based on the Microsoft " | + | |
| - | + | ||
| - | https:// | + | |
| - | + | ||
| - | The following page is displayed in your browser: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Click the Install button. You should see the following prompt at the bottom of the browser window: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Click the Run button. | + | |
| - | + | ||
| - | Applications that are installed over the Internet should be signed so that you know that the application software is distributed by a trusted source. The following Application Install Security Warning is displayed: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Optionally, you can display the CeRTNA Code Signing Certificate by clicking the link labeled California Electronic Recording Transaction Network Authority. If you click the link, the following panel is displayed to so CeRTNA' | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | When you are finished viewing the certificate details, click the Ok button to close the window. | + | |
| - | + | ||
| - | + | ||
| - | From the Application Install Security Warning window, click the Install button. The APEX application will be installed and a progress window will be displayed as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Once the installation completes, the APEX client application will automatically launch as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | This completes the APEX Installation | + | |
| - | + | ||
| - | + | ||
| - | ==== APEX Login Panel ==== | + | |
| - | + | ||
| - | + | ||
| - | To access the APEX Login Panel, click the User Login button, located on the main APEX ribbon: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | The following Login Panel will be displayed: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | **Field Descriptions: | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | {{tablelayout? | + | |
| - | ^ Field ^ Description | + | |
| - | | User Name | This is your CeRTNA ERDS or G2G userid. | | + | |
| - | | Password | This is your CeRTNA ERDS or G2G password. (Not your token password.) | | + | |
| - | | Platform | Select from the list or type in Production-ERDS or Production-G2G | | + | |
| - | | Status Icon | When you select or type in a Platform value, APEX will verify that it can communicate with the selected platform. A green circle with a white checkbox, means APEX communicate with the selected Platform. A red circle with an X means APEX is not able to communicate with the selected platform. | | + | |
| - | | Refresh Icon | This icon can be clicked to tell APEX to try communicating with the selected platform again. | | + | |
| - | | Show Password | Clicking this checkbox will cause your password to be displayed in plain text. | | + | |
| - | | Forgot Password | Click this link if you need to reset your password. (More detail later in this document.) | | + | |
| - | | Register Workstation | In order to use APEX for sending or retrieving transactions, | + | |
| - | | Login Button | Once a userid, password, and valid Platform name have been entered, this button will be enabled. Click this button to continue logging into the CeRTNA ERDS and/or G2G workstation. | | + | |
| - | | Cancel Button | Click this button to Cancel and close the Login Panel. | | + | |
| - | + | ||
| - | + | ||
| - | After you have entered your User Name, Password, and Platform you can click the Login button. APEX will then initiate a variety of actions including, verifying your credentials, | + | |
| - | + | ||
| - | While APEX is performing these actions, the following panel will be displayed: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | During the login verification process, you may be prompted to enter the password (PIN) for your USB token. If your token password is required, the following pop-up window will be displayed. | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Enter your token password, click the Ok button, and the login verification process will continue forward. | + | |
| - | + | ||
| - | + | ||
| - | Once the login initialization and verification process completes, you will be presented with the main APEX UI as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | Documentation for the APEX UI can be found further down in this document. | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | ==== Forgot Password Panel ==== | + | |
| - | + | ||
| - | + | ||
| - | When you click Forgot Password link on the main Login Panel, the following pop-up window is displayed: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | In the User Name field, enter the userid for the platform that you selected on the Login Panel and then click the Request Password Change button. | + | |
| - | + | ||
| - | A temporary password will be sent to the e-mail address that is associated with the userid that you entered. | + | |
| - | + | ||
| - | When you receive the temporary password, enter the temporary password into the Password Change Code field and then enter your new password into the New Password and the Confirm New Password fields. | + | |
| - | + | ||
| - | If you are uncertain about the password formatting rules, you can click the question mark icon and the following pop-up window will be displayed, showing you the rules for creating a password: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | If you have entered a new password that meets the password formatting requirements, | + | |
| - | + | ||
| - | + | ||
| - | ==== Register Workstation Panel ==== | + | |
| - | + | ||
| - | + | ||
| - | Workstations that are used to transmit ERDS or G2G transactions (payloads) **must** be certified by CeRTNA. The certification process includes a verification that the workstation is configured as outlined in the document Preparing For A System Audit and that an acceptable Microsoft Baseline Security Analyzer report has been submitted to CeRTNA. | + | |
| - | + | ||
| - | The Register Workstation process is the method that APEX uses to ensure that only ' | + | |
| - | + | ||
| - | If you are installing APEX on a workstation that has been certified by CeRTNA, you can register the workstation by clicking the Register Workstation link on the Login Panel. When you click the Register Workstation link, the following pop-up window is displayed: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | All fields are required. Once you have completed filling in the form, click the Register Workstation button and a workstation registration request will be created. CeRTNA staff will receive an e-mail notification that the workstation registration request has been created and a staff member will verify that the ERDS or G2G workstation has been certified. If the workstation has been certified, CeRTNA staff will approve the workstation registration request and this will cause APEX to enable the functionality required to send and retrieve ERDS or G2G transactions. | + | |
| - | + | ||
| - | A confirmation e-mail will be sent to the address provided in the registration request to inform the requester about the status of their registration request. | + | |
| - | + | ||
| - | + | ||
| - | ==== APEX UI Overview ==== | + | |
| - | + | ||
| - | + | ||
| - | Once a CeRTNA ERDS or G2G user has successfully logged into APEX, they will be presented with the main APEX User Interface (UI). | + | |
| - | + | ||
| - | + | ||
| - | The APEX UI is managed dynamically based on each users role, organization, | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | As shown, the main APEX UI contains a series of Containers, Components, and Selectors. Containers will contain one or more APEX functional components. Selectors provide a way to switch between different functional components. | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | The following table describes each item: | + | |
| - | + | ||
| - | + | ||
| - | {{tablelayout? | + | |
| - | ^ Item ^ Name ^ Description ^ | + | |
| - | | 1 | Ribbon Container | This section holds various ribbon components. These components may be buttons that trigger actions or components that simply provide static information. | | + | |
| - | | 2 | Feature Container | This area serves as a navigation area for the various features offered by APEX. As described earlier, the features that will be visble will be driven by the users role and organization. Some initial features may include Repository View, Reports, and Administration. The APEX Health feature is a static feature that is visible at all times. | | + | |
| - | | 3 | Detail Container | This section contains components that respond dynamically based on feature that has been selected in the Feature Container. | | + | |
| - | | 4 | Log Container | This area currently holds the APEX Log Panel. This area may also house the announcements and/or system alerts component. | + | |
| - | | 5 | Actions Component | This ribbon component contains buttons that drive actions. | + | |
| - | | 6 | SysInfo Component | This ribbon component provides static systems information about the current user and the current APEX session. | + | |
| - | | 7 | Health Component | This is a static component that remains visible whenever the APEX window is visible and it provides information about the Health of the current APEX session. | | + | |
| - | | 8 | Repositories Component | This component provides a list of both APEX local and remote transaction repositories. Clicking on one of the repository names will cause the Detail Container to update based on the selected repository. | | + | |
| - | | 9 | Repository Detail Component | This component provides a list of the item contained in the selected Repository. | | + | |
| - | | 10 | Log Panel Component | This is a scrolling log panel that contains real-time event activity. | + | |
| - | | 11 | Ribbon Selector | This selector is used to switch between different Ribbon views. | + | |
| - | | 12 | Log Filter Selector | This selector is used to filter which log messages/ | + | |
| - | | 13 | Feature Selector | This selector is used to switch between different APEX functional features. | + | |
| - | + | ||
| - | Additional detail describing each components specific functionality is contained in their respective sections in this document. | + | |
| - | + | ||
| - | + | ||
| - | ==== APEX Transport Module ==== | + | |
| - | + | ||
| - | + | ||
| - | The APEX Transport Module facilitates the sending and retrieving of transactions, | + | |
| - | + | ||
| - | If you are logged into APEX on a registered ERDS or G2G workstation and your user role is authorized to start/stop the APEX transport processes you will see the Start Payloads Send and Start Payloads Retriever buttons on the Actions ribbon as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | When the Sender and/or Retriever processes are not active/ | + | |
| - | + | ||
| - | Click the Start Payloads Sender button to start the Sender and click the Start Payloads Retriever button to start the respective processes. Once the Retriever/ | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | The APEX detail panel is used to review the list of transactions that are in specific statuses. To view transactions that are in a specific status, click one of the status lines in the Remote Payloads section of the Repositories component. | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | As can be seen, APEX will display an icon next to files that are currently being transported. | + | |
| - | + | ||
| - | An alternative way to see APEX activity is to use the Dashboard View. The Dashboard is accessed by clicking the Dashboard tab as shown below: | + | |
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | The Dashboard view, shows the list of Retriever/ | + | |
| - | + | ||
| - | When a process is not actively sending or retrieving a transaction, | + | |
| - | + | ||
| - | All transaction flow is logged to the Log Panel as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | The Log panel shows separate for when the transaction Sending and/or Retrieving starts and when the transaction Sending and or Retrieving completes. | + | |
| - | + | ||
| - | Retriever and Sender processes are managed independently. In other words you can start and/or stop the processes individually by clicking their respective buttons on the Actions Ribbon. When a Retriever or Sender process is stopped, its corresponding status indicator will turn red as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | To start or stop a Sender or Retriever process, click its corresponding button on the Actions ribbon. | + | |
| - | + | ||
| - | + | ||
| - | ==== APEX Reports Module ==== | + | |
| - | + | ||
| - | + | ||
| - | Reports are available in APEX via the APEX Reports feature, which is accessible on the Feature Selector in the left content panel. | + | |
| - | + | ||
| - | To see the reports that you are authorized to access, click the Reports selector as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | APEX Reports are served up via CeRTNA Microsoft SQL Server Report Services (SSRS). The reports in APEX will look and behave exactly like they did in the CeRTNA web client application. | + | |
| - | + | ||
| - | When you select a report a parameter section and a standard toolbar will displayed as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | The report tool bar has many features. | + | |
| - | + | ||
| - | Several formats are available for exporting reports as seen below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | === Activity Detail Report === | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | The Activity Detail Report is intended to provide totals of activity by various selection criteria. | + | |
| - | + | ||
| - | Parameter selection is based on your user role: | + | |
| - | + | ||
| - | + | ||
| - | **Agent Role Parameters: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | **County Role Parameters: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | After the report options have been selected, click the View Report button to generate the Activity Detail Report as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Clicking on one of the Transaction ID's will cause the Transaction Audit Report to be displayed in a pop-up window as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | === Activity Summary Report === | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | The Activity Summary Report is intended to provide totals of activity by various selection criteria. | + | |
| - | + | ||
| - | This report is produced by selecting a Start Date and End Date. Click View Report to view the Activity Summary Report. | + | |
| - | + | ||
| - | Depending on your role, you will see one of the following formats: | + | |
| - | + | ||
| - | **Agent Role:** | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | **County Role:** | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | === Recordation Report === | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | As the name implies, the Recordation Report is intended to provided detailed recording information based on a variety of user specified criteria. | + | |
| - | + | ||
| - | This report shows information about the County, Submitter, Transaction ID, Primary & Secondary Reference Numbers, Recording Fees, Taxes, Date/Time of Recording, Document Type and Recorded Instrument Number. | + | |
| - | + | ||
| - | This report provides summary information at both county and submitter levels and all totals are rolled into a grand total for the report. | + | |
| - | + | ||
| - | The report can be restricted to a specific date range, selected counties or submitters and depending your role, grouping options may be available. | + | |
| - | + | ||
| - | Output for the Recordation Report is based on your user role. | + | |
| - | + | ||
| - | + | ||
| - | **Agent Role Samples: | + | |
| - | + | ||
| - | + | ||
| - | Agent Recordation Report grouped by County: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Example of summary lines for an Agent Recordation Report grouped by County: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Agent Recordation Report grouped by Submitter: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Example of summary lines for an Agent Recordation Report grouped by Submitter: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | **County Role Samples: | + | |
| - | + | ||
| - | + | ||
| - | County role users do not see a Grouping field. The County view of the Recordation Report is automatically grouped by Submitter. Sample layouts are shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Example of summary lines for a County Recordation Report: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | === Reject Detail Report === | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | The Rejection Detail Report is intended to provide rejection details to Submitters and County. | + | |
| - | + | ||
| - | Parameter selection is based on your user role: | + | |
| - | + | ||
| - | + | ||
| - | **Agent Role Parameters: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | **County Role Parameters: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | After the report options have been selected, click the View Report button to generate the Reject Detail Report as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | === Status Detail Report === | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | The Status Detail Report shows a summary of all payloads by Status. | + | |
| - | + | ||
| - | + | ||
| - | Like the other reports, parameter selection is based on your user role: | + | |
| - | + | ||
| - | + | ||
| - | **Agent Role Parameters: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | **County Role Parameters: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | After the report options have been selected, click the View Report button to generate the Status Detail Report as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | The Transaction History for individual transactions can be viewed by clicking a specific Transaction ID that appears in the detail of the Status Detail Report. When you click a Transaction ID the Transaction history is shown in a pop-up report window as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | === Status Summary Report === | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | The Status Summary Report shows summary counts for each of the major transaction statuses. (Draft, Submitted, RetrievedByCounty, | + | |
| - | + | ||
| - | Following are samples for Agent and County roles: | + | |
| - | + | ||
| - | Agent Role - Grouped by County: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | County Role - Grouped by Agent: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | County Role - Grouped by Submitter: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | Agent Role - Grouped by Submitter: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | If you click a summary value that is greater than zero, the Status Detail Report is displayed in a pop-up report windows for the selected items as shown below: | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | === Transaction Audit Report | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | The Transaction Audit Report reflects the history of a transaction. | + | |
| - | + | ||
| - | To generate the Transaction Audit Report enter the Transaction_Id and click View Report. | + | |
| - | + | ||
| - | + | ||
| - | {{ : | + | |
| - | === Transaction History Report === | + | {{page> |
| + | ===== APEX Getting Started ===== | ||
| - | The Transaction History Report provides a flexible way to review the history of multiple transactions within a single report. | ||
| - | Report sorting and filtering options vary based on user role. | + | {{page> |
| - | Agent role users can sort by County/ | ||
| - | Agent Role sorting by County/ | + | ===== APEX Direct-Entry Module ===== |
| - | {{ :guides:images: | + | {{page>[:guides:apex_direct_entry_ui_guide& |
| - | Agent role sorting by Submitter/ | + | ===== APEX Transport Module ===== |
| - | {{ :guides:images: | + | {{page>[:guides:apex_transport_guide& |
| - | County Role sorting by Agent/ | + | ===== APEX Repositories & Folders ===== |
| - | {{ :guides:images: | + | {{page>[:guides:apex_repositories_guide& |
| - | County | + | ===== APEX County |
| - | {{ :guides:images: | + | {{page>[:guides:apex_county_administrator_guide& |
| + | ===== APEX Reports Module ===== | ||
| + | {{page> | ||
| - | Continue documentation here. | ||
guides/apex_user_guide.1509661945.txt.gz · Last modified: by brett.zamora
