This is an old revision of the document!
Table of Contents
APEX County Administrator Guide
CeRTNA users that have a role of County Administrator will have access to a variety of County Administration functions as shown below:
Overview
APEX manages feature access based on the role that is assigned to the user when their CeRTNA User Profile is intially created. County staff members have the following roles available.
- County User
- County Administrator
Users that are designated with a County Administrator role will see the Administration feature tab and those designated as a County User will not see the Administration feature tab.
If a County Administrator needs to change the role of another staff member, they can send and e-mail to CeRTNA to request the change.
Each of the County Administration features and functions are documented in the following paragraphs.
Authorize Submitters
CeRTNA users that have a role of County Administrator will have access to the Authorize Submitters Module.
Authorize Submitters Overview
The Authorize Submitters module gives County Administrators the ability to Activate or Deactivate CeRTNA submitters. If you are authorized to this module you will see an Administration tab in your Feature panel, as shown in the Overview image below:
In the Overview image shown above you can see that a new Administration feature tab is available. When this tab is clicked, a list of Administration modules will be displayed in the left hand panel of the APEX UI.
To initiate the Authorize Submitters module, click the Manage Submitters item in the Administration/Modules list. This will cause the Manage Submitters tab to be displayed in the Detail Panel on the right side of the APEX UI.
A new Authorize Submitters Management ribbon section is also displayed. The buttons on this ribbon will be disabled until at least one row in the submitter list is selected.
Activating Submitters
To activate one or more submitters, click on the checkbox/checkboxes of the submitters that you would like to activate and then click the Activate Selected Submitters button on the ribbon as shown below:
A pop-up window will be displayed with fields for entering the MOU Version, MOU Date, and an Escrow Account label, which is an optional field entry.
Enter your appropriate values and then click the Activate button. Alternatively, you can click the Cancel button to back out of the operation.
After clicking the Activate button, your submitter(s) will be activated and the Submitter List will reflect the changes as shown below:
Deactivating Submitters
To deactivate one or more submitters, click on the checkbox/checkboxes of the submitters that you would like to deactivate and then click the Dactivate Selected Submitters button on the ribbon as shown below:
A pop-up window will be displayed, giving you the opportunity to Confirm that you want to delete the selected submitter(s). You can click the No button to cancel the request.
After clicking the Yes button to confirm that you want to deactivate the selected submitters, the Submitters list will be updated to reflect the change showing the submitter status is 'Inactive' as shown below:
There may be instances where a County Admininstrator may need to temporarily deactivate a submitter. For that reason, the other settings associated with the submitter record are maintained, as shown above, even though the submitter may be temporarily deactivated.
Multiple submitters can be deactivated at the same time by selecting multiple checkboxes and then clicking the Deactivate Selected Submitters button as shown below:
A pop-up confirmation windows will be displayed and after clicking the Yes button to confirm the request to deactivate the selected submitters, the submitters list will be updated showing the selected submitters as 'Inactive', as shown below:
There are no restrictions on how many times a submitter is activated or deactivated by a County Administrator.
Updating Submitters
The information for an individual submitter can be updated by clicking the Edit icon located to the right of the individual Submitter records. As shown below, clicking the Edit icon will cause a pop-up window to be displayed so that the County Administrator can update the information for that specific Submitter.
After updating the selected submitter, click the Save button and the updates will be reflected in the Submitter list, as shown below:
Manage County Settings
Each county has a group of configuration settings that determine how APEX handles transactions that are associated with their county. To manage these settings, the Manage County Settings page is used. You must be assigned a role of County Administrator in order to access this feature.
To access the County Settings page, click the Administration feature tab and then click the Manage County Settings item in the list of Administration options. After clicking the Manage County Settings item, the following panel will be displayed in the detail area to the right:
The Apply Changes and Discard Changes on the APEX ribbon will activate if an entry in the form is changed.
Although there are several fields on the form, only a handful of them are actually used by APEX and fundamentally, once set, the county settings are rarely changed.
Field Descriptions
Following is a description of each of the fields on the County Settings panel:
County: For County Administrators, this field will have your county name. For CeRTNA System Administrators, this dropdown provides a list of all the counties and the County Settings panel will display the settings for the currently selected county.
Status: The status of the county. It will be either Active or Inactive.
Return Documents: This setting exists from some early ERDS design considerations but it is not actually used. Currently all counties return their recorded documents, so the value will be Yes.
Government Documents Accepted: This is another setting from some early ERDS design considerations and it is not actually used in the ERDS process flow. It is set to No in the ERDS platform and it is set to Yes in the G2G platform, primarily for reference purposes.
ACH Routing Number: Not used.
ACH Account Number: Not used.
Priority One Cutoff Time: This field is used for reference purposes only. It was originally intended to be used in conjunction with the Priority property in the CeRTNA Standard XML to determine if a submitted transaction should be retrieved or held until the next day. It is not enforced at this time.
Priority Two Cutoff Time: This field is used for reference purposes only. At the time of this writing, no CeRTNA ERDS counties are using a secondary cutoff time for electronic recording.
Processing Start Time: This represents the time that a county starts retrieving their electronic recording transactions. APEX, however, does not enforce this field. This field is used by CeRTNA's Submitted Status monitor to determine whether it should send alert e-mails.
Processing End Time: This represents the time when a county 'cuts off' retrieving electronic recording transactions for the current day. Current day transactions that enter submitted status prior to the Processing End Time, will be retrieved by APEX.
Timezone Offset: This field is not used.
DPI: This determines the DPI that TIFF images must have in order to be accepted by the county.
Max Payload Size: APEX enforces a maximum payload size via it's System Settings. A county can use this setting to reduce the maximum payload size by using this setting.
Min Width: This setting specifies the minimum width that a TIFF image must meet in order to be accepted by a county. It is specified in DPI, so it is based on the DPI setting as well. For example at 300 DPI an 8“ minimum width would be specified as 2400. If this field is blank, APEX does not enforce a minimum width.
Max Width: This setting specifies the maximum width that a TIFF image must meet in order to be accepted by a county. It is specified in DPI, so it is based on the DPI setting as well. For example at 300 DPI an 8.5” maximum width would be specified as 2550. If this field is blank, APEX does not enforce a maximum width.
Min Height: This setting specifies the minimum height that a TIFF image must meet in order to be accepted by a county. It is specified in DPI, so it is based on the DPI setting as well. For example at 300 DPI an 10“ minimum height would be specified as 3000. If this field is blank, APEX does not enforce a minimum height.
Max Height: This setting specifies the maximum height that a TIFF image must meet in order to be accepted by a county. It is specified in DPI, so it is based on the DPI setting as well. For example at 300 DPI an 11” maximum height would be specified as 3300. If this field is blank, APEX does not enforce a maximum height.
Indexing Requirements: This field must be set to Minimal Indexing. In the early ERDS design stages, additional indexing fields were considered, however, county feedback indicated that due to the variety of indexing standards, counties would not use indexing data provided by submitters.
Cache Path: This is the base folder that APEX uses to exchange files with the county recorders recording application. See the APEX Folder Structures Guide for more information about this setting.
Comments: Reference field for miscellaneous comments.