Updating centralized tenant configuration settings

Disable-Audit-Only-Changed-Fields

Flag indicating whether to audit all records, or to audit only those records whose field values have changed.

T—Audit all the records.

F—(Default) Audit only those records whose field values have changed.

Flag indicating whether full text searching is case sensitive or case insensitive. This setting affects all fields indexed for full text search and affects how the indexes are built. Therefore, any changes to this setting trigger an automatic re-index.

0— Full text search is case sensitive

1—(Default) Full text search is case insensitive

Flag indicating whether the server processes the pending indexing tasks.

T—Disable indexing. Pending indexing tasks are recorded for processing later when indexing is enabled.

F—(Default) Do not disable indexing.

T—Disable the full text search engine.

Note: The database search capability continues to work even after the full-text search engine is disabled.

F—(Default) Use the full text search engine.

T—(Default) Use FTS in workflow.

F—Do not use FTS in workflow.

Following is the default location where the files are created:

<tenantDirectory>/ftsconfiguration/collection

Following is the default location where the files are created:

<tenantDirectory>/ftsconfiguration/conf

Location of the directory where the full-text search index log files are stored.

Following is the default file where the log entries are created:

arftindx.log

Indicates the way the FTS server modifies qualifications from the client.

Defines the relevancy weight for Title Field. This setting relates to the fields for which the application business analyst has defined the relevancy when Enabling full-text search capabilities in your application.

0 - 0.9—Reduces the relevancy weight of the Title Field.

1—No change to the relevancy weight.

1.1 - 2.0—Increases the relevancy weight of the Title Field.

(Default) 4.0

0 - 0.9—Reduces the relevancy weight of the Keywords field.

1—No change to the relevancy weight.

1.1 - 2.0—(Default) Increases the relevancy weight of the Keywords field.

Defines the relevancy weight for the Environment Field. This setting relates to the fields for which the application business analyst has defined the relevancy when Enabling full-text search capabilities in your application.

0 - 0.9—Reduces the relevancy weight of the Environment field.

1—(Default) No change to the relevancy weight.

1.1 - 2000—Increases the relevancy weight of the Environment field.

Articles (a, an, the), prepositions (in, on, from, front, beside), and so on.

Press Enter to add a new word in this list.

PC workstation laptop desktop computer

slow sluggish

bright shiny

Type a word followed by its synonyms separated by a space. Press Enter to add a new list of synonyms.

0—(Default) Re-indexing is not performed.

1—Starts re-indexing.

Following is the default file where the log entries are created:

arapi.log

Following is the default file where the log entries are created:

aresc.log

Full path name of the file to use if archiving is on.

Following is the default file where the log entries are created:

ararchive.log

Following is the default file where the log entries are created:

arfilter.log

Following is the default file where the log entries are created:

arsql.log

Following is the default file where the log entries are created:

arthread.log

Following is the default file where the log entries are created:

aruser.log

Following is the default file where the log entries are created:

arprocess.log

Following is the default file where the log entries are created:

arservice.log

T—(Default) Logged lines are written to disc.

F—Logged lines are buffered.

(Default) 0

1

T—Append new log information to the existing file.

F—(Default) Create a *.bak file.

1— (Default) Minimum number of backup log files allowed.

999—Maximum number of backup log files allowed.

0—(Default) Log records to a specific form.

1—Log records to a common log form.

Default—Browser locale

English—en

French—fr

German—de

Italian—it

Chinese—zh_cn

Korean—ko

Portugese—pt_br

Russian—ru

Japanese—ja

Spanish—es

Dutch—nl

Swedish—sv

Danish—da

Norwegian—no

Bitmask indicating the server logging modes. To activate one bit, set this option to its value. To activate two or more bits, add their values, and set this option to the total.

For example, to activate bits 1 and 3, set this option to 5 because bit 1 has a value of 1 and bit 3 has a value of 4. To deactivate a bit, subtract its value from the value of this option.

Unless otherwise specified in the following list, this option turns on logging for the arserverd process. Default log files are in the directory specified by the Server-directory option.

0—(Default) Nothing enabled

1—SQL

2—FLTR

4–-USER

16—API

1048576—PROCESS

1048598—All but SQL

1048599—Turn on all of the above components

Flag indicating whether log files display full SQL statements or not.

For more information, see Knowledge Base article ID 000024691.

0—(Default) Disabled

10—Enabled

0—(Default) Yes, a definition file is created.

10—No, a definition file is not created.

Restrict-Logging

Controls which type of logging restriction is enabled. The value of the Restrict-Logging parameter depends on the combination of logging restrictions that you select. Possible values of the restriction parameters are as follows:

• Users — 1
• Client Type — 2
• RPC Queues — 8

You can have combinations of Users, Client Type, and RPC Queues restrictions. For example, if you select Users and Client Type restrictions, the value of the Restrict-Logging parameter is set to 9 (1+8).

A list of semicolon-separated user names. Restricts the logging only for specified users.

For example, Allen;Mike

A list of semicolon separated process names for which logging is restricted.

(Default) 3600 seconds

Attachment-Ext-Filter

0— No filter.

1—Allow users to attach files that have the extensions specified in Attachment-Ext-List setting.

2—(Default) Disallow users to attach files that have extensions specified in Attachment-Ext-List setting.

A list of comma separated attachment extensions that you want to allow to be uploaded.

For example, sh, pl, dll, exe, dmg, jar, vbs, js, bat, ksh

0— No filter.

1—Allow users to view the attached files that have the extensions specified in Display-Ext-List setting.

2—(Default) Disallow users to view attached files that have extensions specified in Display-Ext-List setting.

Defines the maximum combined size limit for all attachments in an outgoing email.

Example: 5000000 bytes

(Default) 0

Defines the maximum number of attachments that can be added to an outgoing email.

Example: 5

(Default) 0

The system uses the following queries to retrieve records accessible to the user:

0—LIKE queries

1—Regular expression queries

2—Database Full Text Search (FTS) capabilities

How default value is set by the system

• If RLS-Implementation setting is not defined, the default value is 1.
• During an upgrade, the system prepares to use the value 2 to use FTS capabilities. After all data is migrated, the server automatically sets 2 as the default value.
• If at any point, the RLS-Implementation setting is deleted, the system reverts to 1 as the default value.

The unique identifier for your Google Cloud Platform project.

The Gcp-Project-Id can be any alphanumeric string that is unique across the platform and is provided by the user while creating a project.

The project id created while setting up the Google Cloud Platform account.

For more information, see Configuring cognitive service for a custom application by using BMC Native (Google) classification.

IFrame_Allowed_Sites

The FieldId-Range specifies the limit for values that you can assign (or are assigned automatically if you do not assign any value) to the Field ID. You can assign the value to Field ID within the Field ID range.

You cannot assign the lower limit value of the Field ID range to a field.

For example, if the FieldId-Range is 1000:2000, the minimum value that you can assign to a Field ID is 1001. 

Unique string that identifies the organization creating the smart bundle. Each organization developing a Digital Service application must have a Developer ID. When you create a Bundle project by using an archetype, a Developer ID is assigned to the smart bundle by the archetype.
Every definition deployed with the smart bundle has a Developer ID property which is used to identify the organization that creates the definition.

For example: com.bmc.arsys

Controls whether to enable or disable the activity history of a process instance.

If Process-History-Level is set to 0, the process start time and end time will be the same. For instances that are still active, the create date of the Process Context record is the start time and its end time will be null.

0—None

1—Enable at activity level

2—(Default) Enable at audit level

• MICROSOFT—Microsoft Translator API
• GOOGLE—Google Cloud Translation Services

T—Self-signed sites can register

F—(Default) Self-signed sites cannot register

Flag indicating whether to apply the default sort order to search results.

T — (Default) Use the default sort order, which is to sort by request ID.

F — No default sort order exists, and no order by clause is added to the command if a sort order is not specified.

T — Format date on server.

F — (Default) Format date on client.

T — (Default) Allow guest users. Unregistered users have no permissions but can perform some basic operations. For example, they can submit requests to forms to which the Public group has access and whose fields allow any user to submit values.

F — Do not allow guest users. Unregistered users have no access to the system.

The default value is set to F.

• T
• F

If this option is not specified, guest users receive a read license.

• T — (Default) Allow multiple groups in field ID 112.
• F — Do not allow multiple groups in field ID 112.

• 0 — (Default) Users are authenticated when a match exists between every LDAP group to which a user belongs and a corresponding group in AR System.
• 1 — Users are authenticated when any single LDAP group to which a user belongs matches a group in BMC Remedy AR System. Excess LDAP groups are ignored.

This option can be used with the External-Authentication-Group-Mapping option.

• 0 — (Default) The server tries to retrieve this information from AREA.
• Bit 1 (value = 1 ) — No email address is provided.
• Bit 2 (value = 2 ) — No notify mechanism is provided.
• Bit 3 (value = 4 ) — No group identifiers are provided.
• 7--The server potentially can reduce the number of AREA related calls during notification processing.
• Bit 4 (value = 8 ) — No license information is provided.
• Bit 5 (value = 16 ) — No notification user validation should occur. This enables the server to avoid using AREA for notification user validation and information retrieval. Use this setting for sites using a form of AREA that applies user names as email addresses and where accessing an authentication database provides no benefit.

By default, bit 1 to 5 are set.

Default-Allowable-Currencies

• T — Create per-thread log files.
• F — (Default) Do not create per-thread log files.