You use this file to define a custom color scheme for the AWI user interface, instead of the default color scheme. You can modify this file and add colors to reflect your company brand. You also use it to customize the connection colors and help users easily identify the Clients they are logged into. The connection color is used in the horizontal bar at the top of the page and in the icon in the browser tab. All windows and tabs that belong to a connection use the same color.

The default colors are always available, also if you delete the file, or if you delete the default configuration in this file.

The changes that you make to this file take effect after restarting the web server.

This page includes the following:

Configuration required?

Only when you want to define custom property settings; otherwise the defaults are used. Most of these use default values set by CA Automic for optimum performance and so you should not modify them unless expressly advised to do so by CA Automic support consultants.

Related components

The AWI framework.

File location

When you have installed the AWI, you find this configuration file in your application server, in the folder ...\<AWI>\config.

To Define the Configuration

  1. In your application server go to the folder ...\<AWI>\config.
  2. Open the file and update the configurations by adding the parameters that you need. Use the table that follows as a guide.

    The changes take effect after logging out and back in again.


The following table lists the parameters of the file that you might want to define for your local setup. There are several categories of properties:

General Properties


If users want to open multiple objects/tasks at a time, they can select them in bulk, right-click and select Open. This opens as many tabs or windows as selected objects/tasks.

By default, the maximum number of tabs or windows that can be opened in one bulk selection is limited to 50, however you can change this limit using this parameter.


By default, tasks in a Workflow (whether on the editor in the Process Assembly perspective or on the monitor in the Process Monitoring perspective), display the name of the task first and its title (if available) beneath the name. In addition to the Name and the Title, users can also assign an Alias to a task in the Workflow. However, the task boxes provide only two rows display this piece of information.

With the wfDisplaySettings parameter you determine which of these properties are displayed in the task box, which one goes in the first row and which in the second. It also determines which property is displayed in the caption of expanded, embedded Workflows.

This is important to give more visibility to the property that users need to identify the tasks.

The tables below describe the behavior of the name, the title or the alias depending on how you set this parameter:

Connection Settings


If you have only one connection to the AE, this parameter specifies the timeout interval for the connection between the AWI and the CP.

If you have several connections to the AE, this parameter specifies the time interval for attempting to connect to the next CP in case the previous connection fails.

Default: 10000 (10 seconds)

Tip: Increase the timeout if you have a slow connection between Tomcat and the Automation Engine

Note: You define the connections to the AE in the uc4config.xml configuration file.

Home Dashboards


The name of the Dashboard (DASH) object for the default AWI Home Dashboard for your installation. Change this if you want to replace the delivered default with a company-defined standard dashboard.

Note: Regardless of which dashboard is defined here, users with editing rights to the DASH objects and Dashboards can choose to use another dashboard to be their own home dashboard.



The name of the folder path where the dashboard objects for user-customized home dashboards are stored.

For more information, see Setting Up Dashboards.


Import of Large and Complex *.xml Files

Importing large *.xml files or *.xml files that contain many objects can take a few minutes. While this process takes place in the background, it can cause an AWI timeout while you are waiting for the import to finish, and receive the confirmation.

The following parameters specify the AWI timeouts, on waiting for these background AE operations to finish. You can increase them if you are getting AWI timeouts:





Default:180000 (180 seconds)

Note: All four values should be changed to the same value.



If you set this parameter to true, a cookie for login information is set at user log in. On log in the following information will be stored:

System, client, user name and department (but not the password). This is used to autofill fields the next time the login screen is displayed.

Allowed values: true / false

Default value: true

Login Settings

sso.kdc.enabled / sso.saml.enabled

Specifies whether single sign-on (SSO) can be used for AWI log in. This allows users to use the domain name and password they use to log into their computer also to log into AWI.

Possible values:

When users first log in, they have to provide their sign-on information and select either Kerberos or SAML sign-in. For more information, see Setting up Single Sign-On.

For information about the full setup and details about the login options this approach provides, see Configuring Automic Web Interface.


Specifies whether the AWI login window opens, the parameters for Connection, Client, Name, Department, Logintype and Language are already filled in. Users need to enter only their password.

Possible values:

If this is enabled, then the AWI startup will recognize login parameters that are added to the start URL in the following format:

https://<AWI >/?system=ConnectionName&client=9999&name=MyUserName&department=Dept&logintype=AE(default)|KERBEROS|SAML&language=MyLanguage&autologin=true



Also referred to as multi-connection support, this parameter controls whether users can choose an AE connection when logging into this AWI installation or they are restricted to the specified connection.

The connections are defined in <connection> elements in the uc4config.xml and would appear in a drop-down on the login page.

Possible values:

Note: If only one connection is defined in the uc4config.xml, then just use the default value here.

Network Settings


Activates WebSocket communication between the AWI clients and the web server they run on. WebSockets is the default and recommended communication technology, because it enables faster interaction with the user interface.

Possible values:

Browsers can limit the number of connections that have the same domain name. This might lead to issues (the page does not load, no content is displayed) when users select multiple items in the AWI to open them.


Online Help


Pattern for the context-sensitive help URL. The parameters are placeholders and are defined as follows:

{0} Language, for example {german}

{1} Version, for example {12.2}

{2} Product, which is {CDA%20Guides} or {ADBA%20Guides}.


Default value:{0}/ALL/components/DOCU/{1}/{2}/#CSHID={3}

If your company security policy does not allow Internet access to your users, you can provide the help on your company's secured intranet:

  1. Load the online help onto your intranet.

    1. Download the most recent documentation bundle from
    2. Go to Automation.Platform/Documentation/Guides/webhelp, where .zip files with the documentation in English (en), German (de) and French (fr) are available.
    3. Unzip the file content to a place on your local intranet that your AWI user clients have access to.
  2. Modify the URL manually to lead to the help.htm file at this location. For example:

    • For the English Automic Automation documentation:


    • For the French Automic Automation documentation:


    • For the German Automic Automation documentation:


    • For the CDA documentation (which is available in English only):



Object Validation


Controls whether users who define workflows (JOBP objects) must provide values in all required fields in all prompt sets in the workflow before saving the workflow definition. This includes the prompt sets in the JOBP object as well as those in the properties of its workflow tasks (child objects).

By default, all required prompt set fields must be defined. Turning this off would allow intermediate saves when building large workflows. No matter how a workflow is saved, when a workflow is executed, all required prompt set fields have to be filled before processing can start.

Possible values: