Required Fields. In the Enterprise Permitting & Licensing software, some fields are “Required Fields,” and the associated columns must be populated for records to be written to the Enterprise Permitting & Licensing db. On occasion, these required fields will not be available in the legacy source data, so a simple default value can be written to the EG_Template db to fulfill any NOT NULL constraint. Dropdown picklist columns restrict the user from entering certain values in the Enterprise Permitting & Licensing db. Conversely, drop-down fields do not have a restriction on values written to the EG_Template db. Therefore, exact spelling or careful matching to the Enterprise Permitting & Licensing configured values is not a requirement for fields intended for Enterprise Permitting & Licensing drop-down fields. Tyler maps the values through a separate table to translate the values to the appropriate Enterprise Permitting & Licensing value during conversion and collaborates with the Jackson County to validate the resulting mappings during the development phase of the conversion. Custom Fields (any fields not available in the master table for the module in question) Most legacy systems have some attribute fields that are not specified in the corresponding master table within EG_Template. ▇▇▇▇▇ refers to these as custom fields. Within each module exists a child table for such custom fields. Since these fields are specific to the legacy system(s), the Jackson County may add columns to these tables in EG_Template to accommodate any needed custom fields in the migration. For example, ‘permit_additional_fields’ is the table for extra fields relating to the ‘permit’ records. Gap Handling (where legacy data doesn’t fit anywhere within EG_Template) On occasion, legacy systems contain special features for which Enterprise Permitting & Licensing does not account in the EG_Template db. As a result, the need may arise to develop a modified solution to address special cases. Contacts Contacts generally fall into two categories:
Appears in 2 contracts
Sources: Software as a Service Agreement, Software as a Service Agreement