Specifies that a reason has to be added for the JS7 - Audit Log for any changes applied to objects such as adding an Order, cancelling an Order etc.

• This applies to operations from the GUI and to operations from the JS7 - REST Web Service API
• Specifying the value true for this setting forces any API requests that modify objects to provide  arguments for the Audit Log.
• Note that the JS7 - Profiles include a related setting to Enable Reasons for Audit Log that has the same effect. However, its use is voluntary and is restricted to the profile's account. The force_comments_for_audit_log setting enforces this behavior for any user accounts regardless of the profile settings of individual user accounts.

Specifies a list of possible comments for selection by a user when performing a GUI operation that modifies an object. In addition to using list entries, users are free to use individual comments when performing such operations.

• The list is populated from some well known reasons for object modifications.
• Users are free to modify list entries and add their own entries for possible comments.

When user accounts are added to the JOC Cockpit using the JS7 - Identity Services then JS7 - Profiles are created with individual settings for each user account.

• This setting specifies the account that is used as a template for the profile when user accounts are created.
• By default the root account is used which boils down to the fact that a new account's profile is populated from settings such as language, theme etc. of the default profile account.

This setting enables the Remember me checkbox that is available from the login window and which stores user's credentials such as account and password in a site cookie. As a result the user account and password are populated with the next login.

• Some users might consider it a security risk to store credentials with browser data.
• Therefore this setting can be disabled so that this option is not offered to users.

copy_paste_suffix, copy_paste_prefix

Specifies the prefix/suffix to be used for object names when performing copy & paste operations in the JOC Cockpit GUI.

• In the JS7 - Inventory object names are unique for each object type: for example, Workflows use unique names, however, a Job Resource can use the same name as a Workflow.
• Therefore a new object name has to be created when performing copy & paste operations. This is achieved by adding a prefix or suffix which can chosen by users.

restore_suffix, restore_prefix

The JS7 - Inventory, chapter: Trash Operations allow addition of any objects that have been removed to the inventory trash.

• When removed objects are restored from the inventory trash then the original object name might be used by some newer object.
• This setting allows the user to specify the prefix and suffix values to be used when restoring objects from the trash.

import_suffix, import_prefix

The JS7 - Inventory Export and Import operations allow objects to be imported from an archive file.

• When objects are imported then their names might conflict with existing object names.
• This setting allows the user to specify the prefix and suffix values to be used when importing objects.

These settings can be used to disable individual views that are available from the JOC Cockpit GUI by main menu items such as Daily Plan, Monitor, Workflows etc.

• This setting works independently of JS7 - Default Roles and Permissions.
• As a result a user account might have permissions to view data from the JS7 - Monitor view, although the view is not offered from the GUI. At the same time, data from the Monitor view would available for this account when using the JS7 - REST Web Service API.

controller_connection_joc_password, controller_connection_history_password

JS7 offers to display warnings in case of upcoming license expiration, for details see the JS7 - How to manage License Expiration Warnings article.

The feature to display license expiration warnings can be disabled by assigning this setting the value true.

Specifies that a JSON file holding information about the order history is created in case of successful orders, failed orders or both. Possible values include:

• all: create history file for all successful and failed orders.
• failed: create history file for failed orders.
• successful: create history file for successful orders.

Specifies that an order log file is created in case of successful orders, failed orders or both. Possible values include:

• all: create order log file for all successful and failed orders.
• failed: create order log file for failed orders.
• successful: create order log file for successful orders.

Possible values include:

• all: create task log file for all successful and failed tasks.
• failed: create task log file for failed tasks.
• successful: create task log file for successful tasks.