Configuring the Settings for Host Profiles
The Settings tab in a host profile has options for themes, external resources, and deployment settings.
TE host profiles allow you to create global themes that change styles across all screens, though this does not change a screen's status from "Predictive" to "Template." Only manual changes performed an individual screen's elements will force the creation of a template from the Velocity Console.
For both TE and Web profiles, you can add files (such as HTML and grammar files) to the deployment so that you can reference from scripts. There are also settings for encrypting the deployment file and including a copyright notice.
On the Screens page, configure each element on a screen-by-screen or template-by-template basis. When you modify elements on the Settings > Modern Theme tab, the elements are configured globally.
For more information about the elements and how to configure them, see Editing Screen Elements.
You can use a custom CSS to style screen elements in a Velocity project. Export the default CSS by clicking the Export CSS button on the Settings > Modern Theme > Screen page, and customize it using the classes defined in the default CSS. Then import it back into your project.
If you choose to use a custom CSS, be aware that it interacts with the theme you have customized and other style settings in the Client. For example, styles you define in your custom CSS may be overridden by styles defined somewhere else depending on order or specificity.
Test your custom CSS before you deploy it in a production environment to make sure elements display correctly.
The following options are available on the Settings > Native Theme page. When you edit the screen properties, the screen on the left shows the colors and font size you've selected.
•Size. Sets the font size for Native mode.
•Enable custom colors. When enabled, you can choose the foreground and background colors for the native screen.
The resources added here are associated with a directory and bundled with your project during deployment. This way you don't have to reference absolute or relative directories, but can instead list a file name that the Velocity Client then locates when executing.
When a script in Velocity references a file external to your project, such as a CSS file, it should be added as a resource to the project. If you're using Speakeasy and add a grammar file, then you can load the grammar file using a script.
When you add resources, reference them in the velocity://resources location. For example:
•Add. Associates a resource file with your project.
•Delete. Removes a resource file from your project and the referenced script (if the Resource Taken From Scripts check box is marked). This action does not delete the file itself, it just prevents the file from being included in the project when it is exported or deployed.
The following options are available on the Settings > Deployment Settings page.
•Encrypt deployment. Encrypts all the files included in a deployment (.wldep) package. The file uses the same extension, but all of the scripts, files, and images included in the deployment package are encrypted using AES 128-bit encryption. This prevents tampering or editing of the deployment file after it is created. To make any changes (including adding scripts or images), you must make them in the Console and re-deploy the project. The Velocity Client decrypts the deployment file automatically when it runs, and the device user's experience is the same whether or not the deployment package is encrypted.
Encrypted deployment files are only supported on clients that are version 2.1.16 or newer. Older clients will not recognize an encrypted deployment file.
When the deployment is encrypted, the log file will no longer include script logging.
This option does not affect global (.wlxgp) or Speakeasy (.wlvpk) deployment files.
•Copyright notice. Provide a copyright notice that is included in the deployment when you are encrypting the project.