configuration.properties

If users want to open multiple objects/tasks at a time, they can select them in bulk, right-click and select either Open or Open in New Window. 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 (Process Assembly perspective) or on the Monitor (Process Monitoring perspective), display the Name of the task first and its Title beneath it. This parameter governs this behavior and allows you to change it.

Take into account that, in addition to the Name and the Title of a task, users can also assign it an Alias. The list below describes the behavior of the Name, the Title and the Alias depending on how you set this parameter:

• wfDisplaySettings=NAME,TITLE

  1st row
  Name: NAME
  Name and Title: NAME
  Name and Alias: ALIAS
  Name, Title and Alias: ALIAS

  2nd row
  Name: empty (short names); name (continued for long names)
  Name and Title: TITLE
  Name and Alias: empty (short names); name (continued for long names)
  Name, Title and Alias: TITLE

  Caption of expanded sub-workflow
  Name: NAME
  Name and Title: NAME
  Name and Alias: ALIAS
  Name, Title and Alias: ALIAS

• wfDisplaySettings=TITLE,NAME

  1st row
  Name: NAME
  Name and Title: TITLE
  Name and Alias: ALIAS
  Name, Title and Alias: ALIAS

  2nd row
  Name: empty (short names); name (continued for long names)
  Name and Title: NAME
  Name and Alias: NAME
  Name, Title and Alias: NAME

  Caption of expanded sub-workflow
  Name: NAME
  Name and Title: TITLE
  Name and Alias: ALIAS
  Name, Title and Alias: ALIAS

automationEngineOpenConnection
TimeoutMilliseconds

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.

The name of the dashboard object (DASH) 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.

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.

Default: DASH.HOME.DEFAULT

customHomeDashboardsFolder

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

For more information, see and Setting Up Home Dashboards for Users.

Default: DASHBOARDS

automationEngineOpenConnectionTimeoutMilliseconds

asyncLoadingTimeoutMilliseconds

automationEngineTimeoutMilliseconds

xRequestExecutorTimeoutMilliseconds

Importing large *.xml files or *.xml files that contain many objects can take a few minutes. While this process is being performed in the background, it can lead to an AWI timeout while waiting for the import to finish and receiving the confirmation.

These 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)

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" or "false"
Default value: "true"

sso.enabled

Specifies whether single sign-on (SSO) can be used for AWI log in, so that users can log into AWI with their domain name and password that they log into their computer with.

true = SSO enabled

false = SSO not enabled (default)

When they first log in, they have to provide their sign-on information and select Kerberos sign-in.

For information about the full setup and details about the login options this approach provides, see Configuring AWI Login and User Authentication.

parameter_login.enabled

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

true = login parameters except password are filled in

false = no login parameters are filled in (default)

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

Note: If your browser is not accessing AWI over an SSL protocol, your URL will start with http://.

For information, see Configuring AWI Login and User Authentication.

automationEngine.index

Also referred to as "multi-connection support," this 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.

Values are:

-1 = Users can choose a connection at login. (Default)

0–n = The number corresponding to the connection element in the
uc4config.xml for the system that all users must use. This is a 0-indexed parameter, so "0" means the first connection that is defined, "1" means the second connection, and so on.

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

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

Values:

true = push is active (default)

false = push is not used

Note: Not all browser types support WebSockets, which push communication uses. If push is active (push = true) and a user logs into AWI on an incompatible browser type, then AWI continues uninterrupted, but it runs all communication over HTTP(S) protocol.

Important: See the Automic Compatibility Matrix for the required versions of tha application server and Java, and a list of compatible browsers.

Troubleshooting: Some antivirus software interferes with WebSocket communication channels. If you find that people are not able to log in, you might have to modify the configuration of your virus scanners to allow WebSocket communications for the AWI.

helpUrl.english *

The location of the start page of the AWI help in English

Default: http://docs.automic.com/documentation/WEBHELP/English/all/components/DOCU/12.1/AWA+Guides

helpUrl.french *

The location of the start page of the AWI help in French

Default: http://docs.automic.com/documentation/WEBHELP/French/all/components/DOCU/12.1/AWA+Guides

helpUrl.german *

The location of the start page of the AWI help in German

Default: http://docs.automic.com/documentation/WEBHELP/German/all/components/DOCU/12.1/AWA+Guides

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.

Values:

true = All mandatory prompt set fields must have values before saving a workflow definition. This is the default.

false = Workflow definitions can be saved without values in all required prompt set fields.