<?xml version="1.0" encoding="UTF-8"?>
<!--Arbortext, Inc., 1988-2018, v.4002-->
<!DOCTYPE pubsConcept PUBLIC "-//PTC//DTD PUBS DITA Concept//EN"
 "pubsConcept.dtd">
<?Pub UDT template _font?>
<?Pub UDT _bookmark _target?>
<pubsConcept id="_Properties_Workflow_Documents_33329" xml:lang="en"
xmlns:import="http://www.oberontech.com/import"
import:style="0_TopicSub"
import:map-object="2Heading_to_concept_in_conceptH1">
<title>Workflow and Document Configuration Properties in the Database</title>
<pubsConbody>
<table import:table-style="Format A">
<tgroup cols="2">
<?PubTbl tgroup dispwid="1230.00px"?>
<colspec colname="1" colwidth="244.86*"/><colspec colname="2"
colwidth="240.81*"/>
<thead>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="middle"
><p>Property</p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="middle"
><p>Description</p></entry>
</row>
</thead>
<tbody>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph>mksis.im.additionalTokenCharacters</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>Specifies additional characters that are considered part of a search
token when breaking up a text search string. This property applies
only for <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> servers that are running on an Oracle database.</p><p>If you specify
additional characters here, they must be supported by the database
lexer (or word breaker) of the underlying Oracle database.</p><p>The
following characters are ignored if specified in this policy:</p><p
><codeph>*| " + - ~</codeph></p><p>The default value of this policy
is:</p><p><codeph>_.</codeph></p></entry>
</row>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph>mksis.im.adminObjectConfigurationLocales</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>This localization property allows the administrator to set the locale
code for which translations are required. The locale code value is
a semicolon (;) separated list of supported locales. When the property
is set for a locale, it indicates that administrative operations such
as create, edit, and view can be performed in that locale for the
display name and description attributes of the administrative objects
for Fields, Test Result Fields, Types, and States. When the default
value for a locale is blank, it means that the administrator does
not require translations to be used, and can use any of the PTC supported
locales to manage the administrative operations. </p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.allowAdminDeletionWithAdminMigration</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Permits you to delete admin objects on a staging server, even
if that object has been migrated to the production server. By default,
you may only delete admin objects if they have not been migrated to
the production server. </p><p>Default is <codeph import:style="Literal8"
>false</codeph>.</p></entry>
</row>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph>mksis.im.allowPrincipalCreationOnLockedServer</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>Permits you to create and import users and groups on a locked server.</p
><p>Default is <codeph import:style="Literal8">false</codeph>.</p
></entry>
</row>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph>mksis.im.allowProjectModificationOnLockedServer</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>Permits you to create or modify projects on a locked server.</p><p
>Default is <codeph import:style="Literal8">false</codeph>.</p></entry>
</row>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph>mksis.im.allowDynamicGroupModificationOnLockedServer</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>Permits you to create and modify dynamic groups on a locked server.</p
><p>Default is <codeph import:style="Literal8">false</codeph>.</p
></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.allowOverride<?Pub _newline
?>Suppression</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>This policy is only used if a server is configured to be a staging
server. If set to true, when you launch the migration wizard, it searches
for Type objects in your workflow that have been created but not yet
migrated. You can then choose to not migrate State and Field overrides
that refer to one or more of the Types that you select. This allows
you to not be forced to migrate newly created Type objects if you
want to migrate only States or Fields that reference those Type objects
but not those objects themselves. After the migration, the Fields
and States that had their overrides suppressed will still contain
the original overrides for later migration.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.allowPartialAdminMigration</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Permits administrators to select specific changes to migrate using
Admin Migration Wizard.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.cacheNotificationPoolSize</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Controls the maximum number of threads available to the <ph
conref="../common/text_variables.dita#text_variables/ProdName04"></ph
> for notifying <ph
conref="../common/text_variables.dita#text_variables/ProdName05"></ph
>s about cache updates. Cache update notifications ensure that clients
update their caches to reflect current data on the <ph
conkeyref="text_variables/ProdName01"></ph> server. If users report
that they are not seeing current data on the <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> server, their clients may not have received cache update notifications
yet. You may consider increasing the number of threads to improve
the server's ability to handle the rate at which cache notifications
are generated and sent to connected clients. Before you increase the
number of threads, PTC recommends that you analyze the server statistics
for the thread pool to determine if the value needs to be increased.</p
><p>Default is 50.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.connectionLimit</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Limit number of client connections for <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> to fixed limit. Setting to <codeph import:style="Literal8">0</codeph
> means no restriction set.</p><p>Default is <codeph
import:style="Literal8">0</codeph>.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.contextSearchOn</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Context search indexes. Context search indexes are automatically
built for text searches if underlying database supports it; however,
text search queries perform differently using context search.</p><p
>Default is <codeph import:style="Literal8">true</codeph>.</p><note
><p>If you have queries from previous release that rely on old text
searching behavior, you may want to temporarily disable use of context
search indexes. Otherwise, you can leave context searching enabled
if underlying database supports it.</p></note></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.contextSearchSync</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Setting any value for this property will have no impact on the <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> server.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.defaultSource<?Pub _newline
?>Server</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>The hostname and port for the default configuration management
server. If this property is set, users are not prompted to specify
a configuration management server. If this property is not set, the <codeph
import:font="Courier New">mksis.im.promptSourceServer</codeph> property
must be set to <codeph import:style="Literal8">true</codeph>. </p
></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.distributionChartGroupingMax</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Maximum number of values permitted in a field used by a grouping
in a distribution chart. A larger number requires more server heap
memory.</p></entry>
</row>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph>mksis.im.documentMemoryGovernor</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>To improve the performance, a limit can be set, in bytes, for the
amount of data that is returned for a document. By default, there
is no limit. To set a maximum limit for a document that can be returned
by a server, set this property to a specific value (for example, 10000000
for 10 MB). If this limit is exceeded, the user receives an error.</p
></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.httpSession<?Pub _newline
?>Heartbeat</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>If set to <codeph import:style="Literal8">true</codeph>, the Web
interface issues a “heartbeat” to artificially keep the HTTP session
active while the browser window is open. If set to <codeph
import:style="Literal8">false</codeph>, the HTTP session expires after
the time specified in the <codeph import:style="Literal8">mksis.im.httpSessionTimeout</codeph
> property.</p><p>PTC recommends that you retain the value as true
for best user experience with <ph
conref="..\common\text_variables.dita#text_variables/DocStudio"></ph
></p><?Pub Caret 80?></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.httpSessionTimeout</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Sets the timeout for the server’s global HTTP sessions. If an
HTTP session remains inactive for longer than the timeout period,
the session expires. Sessions associated with the Web interface can
avoid this timeout if they are artificially kept active with the <codeph
import:style="Literal8">mksis.im.httpSessionHeartbeat</codeph> property.
A value of 0 effectively ignores this property and the session timeout
for the Web interface becomes the server's configured value. The value
is stored as seconds.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.ignoreNotificationSecurityRules</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Ignores visibility rules in e-mail notifications, allowing anyone
receiving e-mail notifications to see all available fields. While
this option may improve server performance, it reduces security in
e-mail notifications. </p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph id="Mksis.im.initialRevisionMajor-696F4AE5"
import:style="Literal8">mksis.im.initialRevision<?Pub _newline?>Major</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Sets the starting value for the first part of the revision number,
known as the major revision (the number to the left of the decimal
point) for item types that have been enabled for revisioning. </p
><p>Valid values are <codeph import:style="Literal8">1</codeph> and <codeph
import:style="Literal8">0</codeph>. Default is 0. </p><p>Set this
property in combination with the <codeph import:style="Literal8">mksis.im.initialRevisionMinor</codeph
> property to form a revision number schema. <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> supports four revision number schemas: 0.0, 0.1, 1.0, and 1.1. The
default schema is 0.1.</p><p>Each revision schema produces a unique
revision pattern, as follows:</p><ul>
<li><p>If schema is 0.0, then pattern is: 0.0, 0.1, 0.2, ... 1.0,
1.1, 1.2, ... 2.0, 2.1, ... </p></li>
<li><p>If schema is 0.1, then pattern is: 0.1, 0.2, ... 1.0, 1.1,
1.2, ... 2.0, 2.1, ... </p></li>
<li><p>If schema is 1.0, then pattern is: 1.0, 1.1, 1.2, ... 2.0,
2.1, ... </p></li>
<li><p>If schema is 1.1, then pattern is: 1.1, 1.2, ... 2.1, 2.2,
... </p></li>
</ul><p>A major increment sets the first or next major revision as
indicated in bold. A minor increment sets the first or next minor
revision in the sequence.</p><note><p>Changes to this property take
effect immediately and do not affect existing revisions.</p></note
></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.initialRevision<?Pub _newline
?>Minor</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Sets the starting value for the second part of the revision number,
known as the minor revision (the number to the right of the decimal
point) for item types that have been enabled for revisioning.</p><p
>Valid values are <codeph import:style="Literal8">1</codeph> and <codeph
import:style="Literal8">0</codeph>. Default is 1. </p><p>Set this
property in combination with the <codeph import:style="Literal8">mksis.im.initialRevisionMajor</codeph
> property to form a revision number schema. For information about
the supported revision schemas and the resulting revision patterns
they produce, see <xref format="dita"
href="#./Mksis.im.initialRevisionMajor-696F4AE5" scope="local"
type="codeph">mksis.im.initialRevisionMajor</xref>.</p><note><p>Changes
to this property take effect immediately and do not affect existing
revisions.</p></note></entry>
</row>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph import:style="Literal8">mksis.im.issueLockTimeout</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>The time in seconds that the <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> server is to wait for the release of a database issue lock before
timing out. This property applies only for servers that are running
on an Oracle database.</p><p>The default value is 1, and the maximum
value is 30. If an edit times out because of a database lock, an error
message displays, indicating that the item is currently locked by
another user and to try again later.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.itemTextFilter<?Pub _newline
?>Threshold</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Maximum number of items that can be returned by a query in the
Items view in order for the text filter to be enabled. If the number
of items is greater than the threshold, the text filter is disabled. </p
><p>Default is 1000.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.maxAttachmentSize</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Maximum file size (in megabytes) users can attach to <ph
conkeyref="text_variables/Object_issue2"></ph>. Minimum limit for
attachment size is 1 MB, while maximum limit is 250 MB.</p><p>Default
is <codeph import:style="Literal8">4</codeph>.</p><note><p>For any
changes to take affect, the <ph conkeyref="text_variables/ProdName05"
></ph> GUI must be restarted.</p></note></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.maxDashboardImageSize</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Maximum size for dashboard image in kilobytes. Minimum value is
1&nbsp;KB, and maximum value is unlimited.</p><p>Default is <codeph
import:style="Literal8">100</codeph>.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.maxIBPLIssueCount</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Prevents an item backed picklist field (IBPL) from being created
if it contains more than the specified number of backing items at
its creation or modification. Specifying this value prevents the accidental
creation of an IBPL with large numbers of entries, which can cause
the server and/or clients to run low on memory.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.minimumIssueNumber</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p><ph conkeyref="text_variables/Object_issue3"></ph> number for
next <ph conkeyref="text_variables/Object_issue2"></ph> submitted
to database. If <ph conkeyref="text_variables/Object_issue2"></ph
>s have already been submitted, this number must be greater than the
next <ph conkeyref="text_variables/Object_issue2"></ph> number or
it gets ignored.</p><p>Default is <codeph import:style="Literal8"
>0</codeph>.</p><p>The maximum <ph
conkeyref="text_variables/Object_issue2"></ph> number is 1073741824.
Keep this in mind when setting this property.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.notificationsOn<?Pub _newline
?>AdminLockBreak</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Comma-delimited list of e-mail addresses to be notified when a
server lock is released.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.notifierAddress</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Identifier for server when sending out e-mail notifications (that
is, e-mail address to use in “From” field). Must specify to enable
e-mail notifications, for example: <codeph import:style="Literal8"
>mksis.im.notifieraddress=account@smtp1.abc.com</codeph>.</p><p>Default
is <codeph import:style="Literal8">"Integrity"</codeph>.</p><note
><p>The address may not contain spaces. For example, <codeph
import:style="Literal8">Integrity Server@ptc.com</codeph> or <codeph
import:style="Literal8">Integrity Administrator</codeph> is not acceptable.</p
></note></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.perUserSessionLimit</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Restricts the number of sessions a user can open at one time.
This property is a global value that applies to all users and assists
in managing resource allocation for the <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> server. You can specify a maximum of 100 connections and the default
is 25.</p><p>For example, if you allow users to open 25 sessions at
a time, a user can begin a session in the Web interface, and open
upto 25 tabs in a browser to run a chart in each tab.</p><p>Note the
following:</p><ul>
<li><p>Although this property is a global value, you can override
the value at the group level in the <uicontrol>Create Group</uicontrol
> and <uicontrol>Edit Group</uicontrol> dialog boxes. If no session
limit value is specified at the group level, the global value is used.</p
></li>
<li><p>If there are Web interface users with heartbeat and idle timeout,
then an idle-timed-out user still continues to exist, and is not subject
to this limit.</p></li>
<li><p>If a user belongs to multiple groups and the session limit
value is specified in all or some of the groups, the session limit
resolves to the highest value specified in the groups and global value.
For example, if a user belongs to Group A (session limit = 4) and
Group B (session limit = 7), and the global value is 3, the maximum
allowed sessions  is 7. If the global value is 9, then 9 is the maximum
allowed sessions.</p></li>
</ul></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.promptSourceServer</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Prompts users to specify a configuration management server. If
a default configuration management server is set, this property should
be set to <codeph import:style="Literal8">false</codeph>. If a default
configuration management server is not set, this property must be
set to <codeph import:style="Literal8">true</codeph>. The default
configuration management server is set in <codeph
import:font="Courier New">mksis.im.defaultSourceServer</codeph>.</p
></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.queryGovernor</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Limit returned <ph conkeyref="text_variables/Object_issue2"></ph
> count of query or report. Extremely large queries can demand significant
memory resources from both server and client. Property governs computation
and return of query, and displays a warning message along with the
partial set of results if the number of items returned exceeds the
specified limit. This behavior does not apply to queries that are
not directly run by a run (for example, a query behind a report).
In such cases, <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> displays an error message.</p><p>Minimum value is 100, and maximum
value is unlimited.</p><p>Default is <codeph import:style="Literal8"
>10000</codeph>.</p><note><p>Property governs total of all pages and
is independent of client’s page size.</p></note></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.queryMemory<?Pub _newline
?>Governor</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Extremely large queries, or items with large amounts of history,
or large text fields can take a lot of memory in both server and client.
The full list of all items with their requested information must be
constructed in memory on the server before being sent back to the
client. This limits the maximum memory, in bytes, that the server
can use for a given request. The actual memory usage is estimated
for performance purposes. If the limit is exceeded, the user will
receive an error. This applies to all requests for item information,
whether viewing an individual issue, running a query, a query behind
a report, or other methods.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.QueryTimeOut</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>A limit on the execution time in seconds for the running of a
database query. The value 0 indicates no timeout.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.QueryTimeOut.<?Pub _newline
?>Default</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>The default limit on the execution time in seconds for the running
of a database query. The value 0 indicates there is no default and
the <codeph import:font="Courier New">mksis.im.QueryTimeOut</codeph
> will be used.</p></entry>
</row>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph>mksis.im.reportCreationLanguageList</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>Used to externalize and localize static reports, and specifies the
languages that the report recipe will be saved as (in the database).</p
><p>The property value is a semi-colon (;) separated list of languages.
For example, <userinput>en;de;ja;zh_CN;ko,fr</userinput>. The list
must only contain languages supported by <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
>.</p><p>Setting languages makes the static report generate in those
languages for your users, based on the locale. For example, If English
and German are specified, then both English and German locale users
will run the report in their locale language.</p><p>Setting this property
to a blank value has the following impact:</p><ul>
<li><p>Created reports are saved in the client language, so they can
be run at a later time in that language. For example, if the client
language is German (de) then the static report is created only in
the German language. </p></li>
</ul><p>Users with a client locale that is not specified in this property
will see a report with tokens as the resource. For more information
on tokens used in reports, see the documentation for localizing report
recipes.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.reportMemory<?Pub _newline
?>Governor</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Specifies the maximum amount of memory, in bytes, that the server
can use to run a report. Extremely large reports containing a lot
of items in the top-level query or large text fields can consume large
quantities of memory on the client and server. If the memory limit
is exceeded, the user receives an error message.</p><p>Default is <codeph
import:style="Literal8">10000000</codeph> bytes.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.spelling<?Pub _newline
?>Dictionary=</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>External dictionary to use for spell checking in rich content
fields. Must be a valid and accessible URL (an <codeph
import:style="Literal8">http://</codeph> URL for a Web service, or
a <codeph import:style="Literal8">file://</codeph> to a UNC path of
a known public share). If unspecified, the internal English spelling
dictionary is used. </p><p>This property value can only be changed
for the external spelling dictionary, it cannot be changed for the
internal user dictionary.</p><note><p>This property must conform to
the format of either one word per line and sorted, or one letter per
line with words after the “=” and separated by “;”.</p></note></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.sqlGenerationHints</codeph
></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>Workflow SQL generation hints. The general format is a semi-colon
delimited list of key=value Valid values are <codeph
import:style="Literal8">1</codeph> and <codeph import:style="Literal8"
>0</codeph>. Default is <codeph import:style="Literal8">1</codeph
>.</p><p>.&nbsp; All hints are undocumented and should only be used
on when recommended by <ph conkeyref="text_variables/ProdName01"></ph
> Technical Support.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><p><codeph import:style="Literal8">mksis.im.useBcc</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><p>If <codeph import:style="Literal8">true</codeph>, causes server
to send e-mail notifications as blind carbon copies preventing recipients
from viewing e-mail addresses not their own. If <codeph
import:style="Literal8">false</codeph>, other recipients e-mail addresses
appear in <uicontrol import:style="GUI8">To</uicontrol> field of e-mail
header.</p><p>Default is <codeph import:style="Literal8">false</codeph
>.</p></entry>
</row>
<row>
<entry colname="1" morerows="0" nameend="1" namest="1" valign="top"
><?PubTbl cell border-bottom-width="0.50pt"?><p><codeph
import:style="Literal8">mksis.im.validURLPrefixes</codeph></p></entry>
<entry colname="2" morerows="0" nameend="2" namest="2" valign="top"
><?PubTbl cell border-bottom-width="0.50pt"?><p>Specifies valid URL
prefixes for hyperlinks in rich content fields. You can add URL prefixes,
permitting users to include external hyperlinks to third party applications,
for example, adding <codeph import:style="Literal8">doors://</codeph
> to allow external hyperlinks to requirements in DOORS. Similarly,
you can remove URL prefixes, preventing users from clicking certain
types of external hyperlinks.</p><p>Default values are <codeph
import:style="Literal8">http</codeph>, <codeph import:style="Literal8"
>https</codeph>, <codeph import:style="Literal8">mailto</codeph>, <codeph
import:style="Literal8">file</codeph>, <codeph import:style="Literal8"
>\\</codeph>, and <codeph import:style="Literal8">integrity</codeph
>. Each value is separated by “<codeph import:style="Literal8">;</codeph
>”.</p><p>Note the following:</p><ul>
<li><p>For changes to this property to take effect, the <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> server. and client must be restarted.</p></li>
<li><p>For some URL prefixes, such as <codeph import:style="Literal8"
>https</codeph>, <ph
conref="../common/text_variables.dita#text_variables/ProdName01"></ph
> does not automatically create a hyperlink. Users may need to select
the URL in the rich content field and insert the hyperlink manually.</p
></li>
</ul></entry>
</row>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph>mksis.im.privateUserPrefs</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>This property defines the private user preferences. This is a system-generated
property. User must not edit this property.</p></entry>
</row>
<row>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-left-width="0.50pt"
border-right-width="0.50pt"?><p><codeph>mksis.im.publicUserPrefs</codeph
></p></entry>
<entry><?PubTbl cell border-bottom-width="0.50pt" border-right-width="0.50pt"?><p
>This property defines the public user preferences. This is a system-generated
property. User must not edit this property.</p></entry>
</row>
</tbody>
</tgroup>
</table>
</pubsConbody>
</pubsConcept>
