DokuWiki

You've loaded an old revision of the document! If you save it, you will create a new version with this data.

===== APEX User Guide =====

==== Overview ====

APEX is CeRTNA's 2nd generation Electronic Recording Delivery System. The software is based on Microsoft's .NET Framework and their "Click-Once" software delivery architecture. APEX supports the following major features:

* Secure transport of XML transaction files.
  * Reporting (Work in progress.)
  * Administration (Work in progress.)
  * Direct Order Entry (Work in progress.)

Other lower level features include:

* Digital signatures, encryption, and decryption based on PKI technology.
  * Multi-threaded processing for improved throughput.
  * Improved error handling and recovery.
  * Multi-workstation support.

The following pages provide a comprehensive outline of APEX functionality.

==== HW & OS Requirements ====

{{page>[:guides:hw_and_os_reqs&noheader&noindent&nofooter&nouser&nodate&noeditbtn&nopermalink]}}

==== APEX Installation ====

{{page>[:guides:apex_installation_guide&noheader&noindent&nofooter&nouser&nodate&noeditbtn&nopermalink]}}

==== APEX Getting Started ====

{{page>[:guides:apex_getting_started_guide&noheader&noindent&nofooter&nouser&nodate&noeditbtn&nopermalink]}}

==== APEX Transport Module ====

The APEX Transport Module facilitates the sending and retrieving of transactions, also referred to as 'payloads' and/or XML files. Transactions can only be sent and retrieved on a registered and/or certified ERDS or G2G workstation.

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/running, the Retriever Manager and Sender Manager rows in the APEX Health component will be red to indicate that those processes are stopped.

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/Sender processes are running, the APEX UI will change as shown below:

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.  A list of XML files that are in the local file system can be seen by clicking one of the line items listed in the Local Payloads section of the Repositories component as shown below:

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/Sender processes (threads) that are currently running. Each process (thread) will identify the specific transaction that it is sending or retrieving.

When a process is not actively sending or retrieving a transaction, its status will show as Idle. A process that is Idle is active but it is waiting for a unit of work to become available.

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.  You can move between pages using the arrows or by typing in a page number to advance to the desired page. You can select an export format from the drop down menu, refresh the report or print the report by clicking one of the buttons.

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.  The Activity Detail Report provides a baseline management tool to monitor activity for the ERDS, Counties, and Submitters.  This report includes the Transaction ID, County, Originator Name, Customer Reference, County Fees, Instrument Numbers or Rejection Codes and a Status.

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.  The Activity Summary Report provides a baseline Management tool to monitor activity for the ERDS, Counties and Submitters.  This report will list the Submitter and give the total Count, Recording Fee and Tax totals.

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.  This report includes Transaction ID, County, Submitter, Primary Reference, Last Modified, Doc Type, Rejection Code, Rejection Code Description and Rejection Message.

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.  This will give the Submitter or County user a snapshot of the activity for a time period and the total number of payloads in any given 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, ReturnedByCounty, RetrievedBySubmitter, and Archived. The Status Summary Reports can be grouped based on your role. For Agent Roles, the report can be grouped by County or Submitter. For County Roles the report can be grouped by Agent or Submitter. If you are a System Administrator Role you can group the report by County, Agent, or Submitter.

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.  All activity is logged by date, time and user.  The report provides a history of each of the status changes associated with the specific transaction.  This report includes the Type, Reference, Status, Agent, Submitter, County, Created By and Modified By for each status change of the transaction.

To generate the Transaction Audit Report enter the Transaction_Id and click View Report.  The report will be generated and displayed as shown below:

=== Transaction History Report ===

The Transaction History Report provides a flexible way to review the history of multiple transactions within a single report.  All activity is logged by date, time and user.  The report provides a history of each of the status changes associated with each transaction that meets the filtering criteria.  This report includes the Type, Reference, Status, Agent, Submitter, County, Created By and Modified By for each status change of the transaction.

Report sorting and filtering options vary based on user role.

Agent role users can sort by County/Submitter or Submitter/County and they can filter based on Start Date, End Date, County, and Submitter as shown below:

**Agent Role Samples:**

Agent Role sorting by County/Submitter:

Agent role sorting by Submitter/County:

**County Role Samples:**

County Role sorting by Agent/Submitter:

County role sorting by Submitter/Agent:

Continue documentation here.

Edit summary

Note: By editing this page you agree to license your content under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International