13.07.2015 Views

Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

Picture Perfect 4.6 Enterprise Edition User Manual - UTCFS Global ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

52<strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> <strong>Enterprise</strong> <strong>Edition</strong><strong>User</strong> <strong>Manual</strong>ER is applied to the following <strong>Picture</strong> <strong>Perfect</strong> tables (see Figure 4):• person• badge• person_user• person_category• temp_category• notes (only for person/badge)• category• facility• person_type• department• permission_group• host_bid_format• custom_form• custom_list_elem• site_lists• form_tab• custom_control• custom_control_arg• time_zone• time_zone_dstFor person-related and global tables, replication is applied in both directions between nethost andsubhosts (up to 31 subhosts).Note:Although part of the Facility form, facility_email and email_ran tables are not replicated. In <strong>Picture</strong><strong>Perfect</strong> 4.5.1 and <strong>4.6</strong>, the facility email feature is managed locally for each server. Every server needsto manage its own list of facility emails.In an <strong>Enterprise</strong> system environment, there are some hardware-dependent fields that are notrefreshed by networking to other subhosts. These fields include antipassback (APB), lastaccess reader, last access date, last access time, last access area, usagecount, download upon save, card trace, and keypad response. If the optional GuardTours package is installed, the field tour badge is also not refreshed. Due to the site-dependentinformation found in these fields, you would not want them to be refreshed. For example, subhost 1reader 1 is located at the back door. Subhost 2 reader 1 is located at the side door. To send theinformation in the field last access reader from subhost 1 reader 1 to subhost 2 reader 1 would notbe useful to an operator on subhost 2.The dbrfsh refresh process is applied to the following <strong>Picture</strong> <strong>Perfect</strong> tables (see Figure 4):• badge_history• alarm_history• operator_his• tour_history (optional package)For history tables, the refresh process is applied in one direction from subhosts to nethost.Note:<strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> introduces database schema changes for history tables to unify their layout acrossthe <strong>Enterprise</strong> configuration (see the <strong>Picture</strong> <strong>Perfect</strong> <strong>4.6</strong> Tables and Fields Reference <strong>Manual</strong>).

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!