--- sourceDocument: Australia Employee Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/employee-service-management Release : - australia ft:locale : - pt-BR ft:publication_title : - Australia Employee Service Management ft:clusterId : - emplsm bundleId : - emplsm workflow : - Employee --- # Set up Contact Tracing properties # Set up Contact Tracing properties {#ariaid-title1} * Versão de lançamento: Australia * * Atualizado 12 de mar. de 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 min. de leitura Configure system properties to adjust how contact tracing data is used. ## Antes de Iniciar Role required: admin ## Por Que e Quando Desempenhar Esta Tarefa Employers remain solely responsible for complying with their legal obligations under applicable law, including data protection laws on collection, use, disclosure, and retention of personal data, and should enable, choose not to enable, or customize any functionality available within the application to meet the Employers' specific requirements. Nota: For system properties associated with tracing systems, see [System properties for tracing systems in Emergency Exposure Management](https://www.servicenow.com/docs/qGoVjfTLXZ8C0S_4xzIOEg "System properties associated with tracing systems that are available in the Emergency Exposure Management application."). ## Procedimento 1. Navigate to AllContact TracingAdministrationProperties. 2. Set the following property values. {#configure-contact-tracing-properties__table_lxd_w4y_cnb__entry__2}{#configure-contact-tracing-properties__sysprop_auto_case_task} | Property | Description | |-|-| | sn_imt_tracing.data_retention_period | Number of days after which the data collected for contact tracing is automatically deleted from the system. The retention period is calculated from the last updated date of the data. The retention policy applies to the following contact tracing data: * Badge swipe data. * User daily contact logs, daily log notes, and daily log acknowledgment data. * All closed and canceled cases and associated potentially exposed contacts, case tasks, diagnostic requests and the underlying source data, and diagnostic events. Nota: A survey associated with cases eligible for deletion after the retention period is not deleted because surveys have their own retention period. For more information, see [Clean up assessment data](https://www.servicenow.com/docs/access?context=t_CleanUpAssessmentData&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). * Wi-Fi access register data {#configure-contact-tracing-properties__ul_mxd_w4y_cnb} The default value is 90. | | sn_imt_tracing.auto_create_case_tasks | Enables or disables automatic creation of a case task when a case manager adds a potentially exposed contact to a contact tracing case. If the property value is set to Yes, the base system workflow, Create case tasks for exposed contacts, triggers the creation of a case task when a potentially exposed contact is added to a case. The default value is Yes. | [Tabela 1. Properties for Contact Tracing] {#configure-contact-tracing-properties__table_lxd_w4y_cnb} {#configure-contact-tracing-properties__table_r2w_1cr_zlb__entry__2} | Property | Description | |-|-| | sn_imt_tracing.data_retention_period | Number of days after which the data collected for contact tracing is automatically deleted from the system. The retention period is calculated from the last updated date of the data. The retention policy applies to the following contact tracing data: * Badge swipe data. * User daily contact logs and daily log acknowledgment data. * All closed and canceled cases and associated potentially exposed contacts, case tasks, diagnostic requests and the underlying source data, and diagnostic events. Nota: A survey associated with cases eligible for deletion after the retention period is not deleted because surveys have their own retention period. For more information, see [Clean up assessment data](https://www.servicenow.com/docs/access?context=t_CleanUpAssessmentData&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). * Wi-Fi access register data {#configure-contact-tracing-properties__ul_ang_p1f_dmb} The default value is 90. | | sn_imt_tracing.badge_data_page_size | Number of records to process at a time for badge reader data. The default value is 500. | | sn_imt_tracing.badge_reader_location | The field in the Badge Access Register table \[sn_imt_tracing_badge_access_register\] that refers to the location of the badge reader when the Use badge reader option is selected on the Diagnostic Request form. You can also specify a dot-walked field, for example, floor.floor_name. The default value is the floor_name field in the \[sn_imt_tracing_badge_reader\] table. | | sn_imt_tracing.badge_owner_field | The field in the Badge Access Register table \[sn_imt_tracing_badge_access_register\] that refers to the badge owner when the Use badge reader option is selected on the Diagnostic Request form. You can also specify a dot-walked field, for example, user.user_name. The default value is the user field in the \[sn_imt_tracing_user_badge\] table. | | sn_imt_tracing.wifi_client_table | The CMDB Class table to look up to identify the device and owner matching the Wi-Fi client in Wi-Fi access logs. The default value is cmdb_ci_computer. | | sn_imt_tracing.wifi_client_mac_field | The field in the CMDB Class table \[cmdb_ci_computer\] that stores the mac address of the Wi-Fi client. The default value is mac_address. | | sn_imt_tracing.wifi_client_owner_field | The field in the CMDB Class table \[cmdb_ci_computer\] that identifies the owner of the Wi-Fi client from the Wi-Fi access logs. The default value is assigned_to. | | sn_imt_tracing.wifi_client_identification_fields | The fields in the CMDB Class table \[cmdb_ci_computer\] that identify the Wi-Fi client matching the Wi-Fi client in the Wi-Fi access log. The default values are mac_address, name. | | sn_imt_tracing.wifi_ble_client_table | The CMDB Class table to look up to identify the device and owner matching the Wi-Fi Bluetooth LE (BLE) client in the Wi-Fi access logs. The default value is cmdb_ci_wearable. Nota: The Wearable Technology table \[cmdb_ci_wearable\] is installed with the CMDB CI Class Models application available on ServiceNow Store. For more information, see [CMDB CI Class Models](https://www.servicenow.com/docs/access?context=cmdb-ci-class-models-iot&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). | | sn_imt_tracing.wifi_ble_client_mac_field | The field in the CMDB Class table \[cmdb_ci_wearable\] that stores the mac address of the Wi-Fi BLE client. The default value is mac_address. | | sn_imt_tracing.wifi_ble_client_owner_field | The field in the CMDB Class table \[cmdb_ci_wearable\] that identifies the owner of the Wi-Fi BLE client from the Wi-Fi access logs. The default value is assigned_to. | | sn_imt_tracing.wifi_ble_client_identification_fields | The fields in the CMDB Class table \[cmdb_ci_wearable\] that identify the Wi-Fi asset matching the Wi-Fi BLE client in the Wi-Fi access log. The default values are mac_address,asset_tag. | | sn_imt_tracing.mist_api | API that gets the Wi-Fi access logs from Mist Systems. The default value is https://api.mist.com/api/v1. Nota: This property applies only if you collect Wi-Fi access logs using Mist Systems. | | sn_imt_tracing.mist_visits_page_size | Maximum number of records to process by Mist Systems API calls. The default value is 1000. Nota: This property applies only if you collect Wi-Fi access logs using Mist Systems. | | sn_imt_tracing.wifi_proximity_preference | Level of proximity to consider user interaction with an affected user as potential exposure. The available options are 30ft, Floors, or Buildings. The default value is 30ft. Nota: This property applies only if you collect proximity reports using Cisco DNA Spaces. | | Properties that apply only if you collect Wi-Fi raw data from Cisco DNA Spaces using Wi-Fi raw data files || | sn_imt_tracing.wifi_log_sftp_server | URL or IP Address (for example, 192.168.1.1) of the secured FTP (SFTP) server from which to access the Wi-Fi raw data files imported into the Wi-Fi Access Register \[sn_imt_tracing_wifi_access_register\] table. | | sn_imt_tracing.wifi_log_sftp_port | Port on the SFTP server to allow an FTP connection to access the files. | | sn_imt_tracing.wifi_log_sftp_file_path | File path on the SFTP server where the Wi-Fi access data files from Cisco DNA Spaces are stored. For example, in the file path /upload/Visit Data/Daily/ServiceNow_Daily_Visits_ * /upload/Visit Data/Daily/ is the folder location on the SFTP server where the files are stored. * ServiceNow_Daily_Visits_ is the first part of the default file name that Cisco DNA Spaces uses, followed by the date and the upload time. {#configure-contact-tracing-properties__ul_xsd_qgp_vmb} For example, the default file name for the Wi-Fi access data for 19 August 2020 at 0100 UCT would be ServiceNow_Daily_Visits_2020-08-19 0100 UTC.csv: * ServiceNow_Daily_Visits_ is a fixed value * 2020-08-19 is the date the Wi-Fi access data was captured * 0100 UTC is the time scheduled by you for Cisco DNA Spaces to upload the file {#configure-contact-tracing-properties__ul_krr_ln5_5mb} Nota: Make sure that only a limited number of users have read and write access to this location. | | sn_imt_tracing.wifi_log_sftp_load_time | Time in HH:mm format when the Cisco DNA Spaces system uploads the day's Wi-Fi access data files on the SFTP server. This timestamp is the last part of the name of the Wi-Fi access data file. | | sn_imt_tracing.wifi_log_sftp_username | User name required to log in to the SFTP server. Nota: Make sure that the SFTP user is not a privileged user such as an administrator. Assign the minimal privilege required to read the files in the directory set in the sn_imt_tracing.wifi_log_sftp_file_path property. | | sn_imt_tracing.wifi_log_sftp_password | Password required to log in to the SFTP server. | | sn_imt_tracing.wifi_log_cisco_tier | Integration tier with Cisco DNA Spaces to fetch Wi-Fi access data. The available options are proximity_report and wifi_log_report. Nota: This property applies only if you are using integration with Cisco DNA Spaces to get the Wi-Fi access data. | [Tabela 2. Properties for Contact Tracing] {#configure-contact-tracing-properties__table_r2w_1cr_zlb} 3. Click Save.