Differences

This shows you the differences between two versions of the page.

--- guides:apex_county_settings_guide [2018/05/30 16:25] – created administrator
+++ guides:apex_county_settings_guide [2018/05/30 18:47] (current) – administrator
@@ Line 1: / Line 1: @@
-===== Manage County Settings =====
+===== APEX Manage County Settings =====
-Placeholder for 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:
+{{ :guides:images:county_settings-010.png |}}
+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 [[guides:apex_folder_structures|APEX Folder Structures Guide]] for more information about this setting.
+**Comments:** Reference field for miscellaneous comments.