In Administration > SETTINGS, shared space admins can configure the shared space by setting properties and enabling features on the UFT Mobile server.
When using UFT Mobile as a managed service provided by an MSP or when shared spaces are enabled during installation, some settings may be controlled globally. For details, see Shared space management (on-premises).
To configure administration settings:
Select a category from the left panel. After you modify the settings in a specific section, click Verify and Save and wait for the server to acknowledge your changes.
To erase the changes that you made, click Discard Changes in the top right of the screen.
Note: Some properties and settings are only available for Trial, Enterprise, and Ultimate license types. For details, see UFT Mobile editions.
This section lets you configure general settings, such as compatibility validation, lock duration (for consecutive failed logins on the account and for idle devices), and password expiration time. For details, see
The following table provides additional information regarding some general settings:
|Enable WebSocket Security||When this setting is enabled, all testing tools and integrated products connecting to UFT Mobile must use an execution key for authenticating the connection. For details, see Access key management.|
The default password expiration is 180 days. Twenty days before the expiration date, UFT Mobile issues a warning to the user to change the password. A "0" value indicates no expiration date.
If a user's password expires or if a user forgets their password, the shared space admin can reset it from Lab Management, or using a script. For details, see Manage user accounts with scripts (on-premises).
To prevent users from being locked out after entering a wrong password three times, set the Lock duration to "0".
|Collect usage data||One type of data collection is for the purpose of evaluating the usage of your lab resources. You can download CSV reports from the console containing reservation, device, app, and job information.|
|Single-Sign-On init string||
This is mandatory for integration with the ALM extension for UFT Mobile. Paste in the value of the COMMUNICATION_SECURITY_PASSPHRASE flag from the ALM Site Administration. If you leave this field empty, single sign-on will not work. For details, see UFT Mobile wizard.
|Device screen view idle timeout||When no actions are performed on the device for the defined period of time, the remote device screen display window is closed. The device remains locked.|
|Device session idle timeout||When no actions are performed on the device for the defined period of time, the session ends and the device is unlocked.|
|Permission to gather data||
|Email address for administrator||The email address of the user to be used when users click Contact your admin from UFT Mobile. The user whose email is provided must be assigned a shared space administrator role.|
|Limit application uploads||Limit the number of uploads for each application. This makes it easier to manage the number of application uploads that need to be maintained and reduces load on the file storage system.|
|Application upload limit||When you define the maximum upload limit, older uploads exceeding the limit are deleted. If you selected to delete old uploads of applications when upgrading the UFT Mobile, your settings will be copied over to this section.
Note that after the setting is enabled, or if the number of uploads to retain is decreased, the deletion of uploads will not be done immediately, but will be done in the background.
|Execution/Connector max duration||Set the maximum number of days that Execution and Connector access keys are valid. After the limit is reached, the keys expire. If you leave these fields blank, the keys have no expiration date. You can also enable a setting to remove expired keys automatically from the list of access keys.
For details on how to create access keys, see Access key management.
|Prometheus integration||Enable or disable the integration with Prometheus. After clicking verify and save, restart the server.|
When using a proxy server, user this setting to configure the proxy server settings.
This section lets you configure device reservation settings such as duration, and number of devices that can be reserved. For more details on these settings, see Device reservation settings.
To enable record and replay functionality when testing certain apps, you need to repackage them with UFT Mobile libraries. These sections allow you to specify the host machine, port, and protocol for the Android packager. You can also specify if packaged apps should trust self-signed and Android system certificates. This is required when recording a script for load testing using the VuGen MITM protocol. For details, see App packaging and signing services.
This section enables you to configure automatic signing and packaging services for iOS apps. For more details on these settings, see iOS packaging service.
Globally control settings for all iOS devices.
|Kanji keyboard support||
When enabled, provides better support for the Kanji (Japanese) keyboard by looking up the key entered from the physical keyboard and passing it to the soft keyboard on the device screen. Note that this option should only be enabled for the Japanese keyboard. Note: The setting is supported on iOS 11.1 and later.
|Prevent Auto-Lock||When this option is enabled, UFT Mobile prevents the Auto-Lock if configured in the Settings on an iOS device, by waking up the device every 30 seconds.|
|Auto-dismiss system alerts when idle||Sometimes, alerts such as iOS update notifications can interfere with the UFT Mobile device plug-and- play process.
When this option is enabled, UFT Mobile automatically dismisses system alerts every 15 seconds. To avoid interfering with tests, UFT Mobile will not dismiss alerts during record and replay.
|Auto-dismiss alerts during app launch||Alerts displayed during the launch of an app, for example a location permission request, may prevent UFT Mobile from identifying that the app was successfully launched.
When this option is enabled, UFT Mobile automatically dismisses system alerts during app launch.
|Support for time and date changes||
Note: Enable this option only if your test involves changing the time and date.
When enabled, this option prevents the remote view from freezing when the date or time is changed.
|Use accessibilityId||For packaged apps, use the accessibilityId property and value for identifying components instead of the accessibilityLabel.|
|Phone call support (Tech preview)||Enable phone calls to be made or received on devices during record and replay. Supported in iOS version 12 and later. Note: After enabling the setting, reconnect the iOS devices for the setting to take effect.|
- UFT Mobile dismisses alerts by selecting the negative option. For example, if the location permission alert is displayed, UFT Mobile will select Don’t Allow.
- The options above are currently supported only for English locale.
Amazon Device Farm integration
Amazon Device Farm (ADF) integration lets you use devices from the Amazon farm for testing purposes.
In this section, you provide the AWS security credentials. If you created a project that you want to use through the EC2 interface, specify its name here.
For details, see AWS Device Farm integration or follow the links to the AWS documentation in this pane.
- These settings override any other settings that you may have defined for your test in the EC2 instance.
- When you disable ADF integration, the change may take up to 10 minutes to take effect.
You can define permissions for users in your workspace regarding actions on apps and devices. By default, users have permissions to perform all actions. For more details on these settings, see User permissions.
Network Virtualization integration
This section lets you specify the NV Test Manager machine information, its authentication token, and the protocol to use (HTTP or HTTPS).
For details about these settings, see Set up Network Virtualization integration in UFT Mobile (on-premises).
For information on how to set up your machine and devices, see .
If your organization uses LDAP to manage user accounts, you can allow users to access UFT Mobile with their LDAP credentials. For more details on these settings, see LDAP settings.
When using shared spaces, some settings are controlled globally by the operator. For details, see Shared space management (on-premises).
UFT Mobile supports single-sign on via SAML 2.0. SAML (Security Assertion Markup Language) is an XML-based standard for exchanging authentication and authorization data between an identity provider (IdP) and a service provider, such as UFT Mobile. In this section of settings, you can enable single-sign-on (SSO). This way, users can use one set of credentials for logging into UFT Mobile, as they do for logging into other SSO applications in their organization. For more details on these settings, see SAML SSO settings.
This section lets you enable integration with a UFT Mobile hosted device lab and specify the Oauth2 credentials needed to access the devices.
Micro Focus provides you with the access key when you purchase your UFT Mobile hosted devices contract. For details, see the Hosted devices datasheet.
Service Virtualization (SV) integration
This section lets you enable Micro Focus Service Virtualization (SV) instrumentation when uploading apps.
This integration enables you to virtualize your sensors, APIs, and devices. For details, see Set up Service Virtualization (SV).
AutoPass license server configuration
Required only when using a time-based device minutes license. After installing the AutoPass license server, specify the details of the AutoPass server machine. For details, see License installation and management.
This section lets you specify the account to use for integration with Genymotion cloud devices. For details, see Genymotion Cloud integration.
Integrate UFT Mobile with Micro Focus Octane to open defects directly from exploratory sessions. Enable the integration setting, and then populate the fields as described below:
- Specify the Octane URL where you want to manage your defects.
- Include the Octane space ID. The space ID is the number that immediately follows the equals sign in the Octane URL, for example 45001 in the example below:
- You can use your own customized Octane form (template) for filling in the description field of the defect. The template must include the placeholder UFTM_TEST_STEPS. The placeholder will be populated with the steps from the step report.
When saving the settings, the connection to Octane will be verified.
This section lets you set the threshold values for alerts for several device health metrics. If a device's metric exceeds a threshold value, its card displays a warning icon .
For example, the default battery temperature for an Android device is 45°. If UFT Mobile detects a temperature that exceeds 45°, the card displays a warning icon. Hover over the icon to see details about the exceeded threshold.
For more information, see View and manage devices.
Note that Battery health is only supported on Android, and that the Thermal state metric is only supported for iOS 11 and later, and for Android 10 and later.
Set the total file storage size for UFT Mobile to store applications. Uploading apps will be blocked if the storage space reaches this limit.
Tip: You can view the file storage status in the admin dashboard. For details, see The UFT Mobile dashboard.
For better management of file storage space, you can also limit the number of uploads permitted per application. If you enable the setting, specify the maximum number of uploads per application to keep (Default: 30). The most recent uploads are kept, earlier uploads exceeding this number are deleted. For example, if you specify 15, only the 15 latest uploads of an app are kept.
In this section you can enable the following:
Anonymous access for Appium (not supported with LDAP). This allows logins from Appium scripts to UFT Mobile when running tests, without an execution access key.
Appium insecure features. When you enable the setting, the Appium server runs with the --relaxed-security flag and all insecure features are turned on. For details on Appium insecure features, see the Appium documentation.