List of process defaults

If the value is set to 1 and both the intranet and site From Email fields have values, the site From Email value overrides what is defined in the intranet level.

If the value is set to 1, but the site From Email value is blank, the From Email value of the selected intranet is used.

If set to 0, the originator's email address is used.

• Changing the form size
• Moving the splitter bar
• Hiding either the grid view or the detail view
• Changing the visibility of grid columns
• Changing the sequence of columns in a grid display

If set to 0 (zero), this process default prevents such changes from being saved.

If set to 0 (zero), form developers cannot specify alternate scripting languages for individual scripts, but enforces the default scripting language setting (Default script language).

If set to 1, this process default causes the Static labels on all required fields to display an asterisk (*).

This process default has generally been superseded by the use of themes and by the "Infor" theme in particular.

This process default, then, allows you to set an extra amount of time, in milliseconds, for the components to render before the report is submitted for processing.

This process default causes the Static labels on all required fields to display an asterisk (*). If no other value is specified, a default value of 1000 milliseconds is used.

If this process default value is set to 0 (default), the system does not lock users out of a session because of inactivity.

This process default value must be a positive integer.

If this process default is set to 1, messages of type Diagnostics are included in data collection and can be displayed in the Log Monitor stand-alone utility.

If the timer labeled Send Diagnostics Log Until Time expires, this process default automatically resets to 0.

This process default is closely related to the Minutes to close orphan sessions process default.

This setting affects collection-level queries for form collections and collection-level validations. This setting does not affect SQL SELECT operations or other processing coded in a stored procedure (method) call.

Valid values for this process default are:

• Committed: Use this value when all queries should see only data for which the query can get a shared lock.
• Uncommitted: Use this value when queries can read and display data that has not yet been committed in the database.

  With this setting, you do not need to wait for other long-running transactions accessing the same dataset to complete before your queries can complete. However, an uncommitted record might be rolled back between the time the query displays it and the timaae you want to save updates to it. You cannot save a record if the uncommitted data gets rolled back at some time after the query, because optimistic locking fails. You must refresh the record to get valid data before making changes and saving.

In background tasks, you can override this process default value for individual stored procedures or reports by setting the Background Task Definitions form's Isolation Level field.

Form developers can also override this process default for individual form-collection specifications, in-collection list sources, and in-collection validations by setting the Read Mode property on the Collection properties sheet in Design Mode.

• 0 (default): There are no changes to the standard toolbar mode.
• 1: The main toolbar and Form menu options are combined into a single-level toolbar.

• If set to 0 or blank, there are no changes to the current behavior.
• If set to 1 or justOuter, the data-mgcompname attribute is added to the outer or top level element.
• If set to 2 or andValue, the data-mgcompname attribute is added to the outer or top level element and the data value element.
• If set to 3 or andGridCell, the data-mgcompname attribute is added to the outer or top level element, the grid cell element, and the data value element.

If set to 1, the system honors character (upper/lower) case inputs when setting these behavior properties:

• Visible When
• Required When
• Enabled When
• Theme Class When
• Conditional Action event handlers

If set to 0, the the system ignores character case when setting these behavior properties.

If set to 0 (zero), time is displayed based on the database site time zone.

If set to 1 (default), time conversion is applied based on your local time zone.

You can set your Local Time Zone on the Users form's Login Information tab or on the User Information form.

• Visual Basic (default)
• Visual C#

To be functional, this process default requires a valid email address in the Default Value column.

To send notifications to multiple email recipients, enter the addresses separated by semi-colons.

• 0 (off, default): Messages are not entered.
• 1 (on): Messages are entered.

If the audit log is on, messages are automatically sent to the log when users log on and when they open a form. Messages for other events can be generated if developers create event handlers of the Add Entry to Audit Log response type.

This process default is disabled by default (Default Value = 0). To enable it, add an entry (Enable Automatic Get More Rows) on the Process Defaults form, and set the value to 1.

• 0 (false, default): The prioritization of processing the inbound BOD is disabled.
• 1 (true): The prioritization of processing the inbound BOD is enabled.

• 0 (default): Remote logging is disabled and records are deleted.
• 1: Remote logging is enabled.

Message logs are collected, stored, and displayed in the Log Monitor form.

We recommend that you disable this process default when not in use.

• IDOs and tables
• Table columns in non-user-created tables
• Properties on IDOs that extend non-user-created IDOs

This allows for automatic upgrades.

Also, this process default restricts the user from updating the records of a Table Name that does not start with the current AccessAs value in the In the Application Schema Tables Metadata form and Application Schema Columns Metadata form.

A secondary purpose is to prevent users from deleting SQL tables and columns that they did not create.

If not set or if set to 0, users can give duplicate names to these IDOs and components, which can cause problems when it is time to upgrade.

See About enforced prefixes.

• Bookmark is not enabled
• API exceeds FarmAPIMaxRecordCap setting

• High : Validates filters for all sessions
• Medium (default) : Validates filters for only automation sessions
• Low : Does not validate filters at all

See About filter validation.

If the email address is not available in the upgrade control file or on the patch command line, then Form Sync looks for this process default value by using the target configuration.

Use this process default to override that internal setting and allow more (or fewer) than 9 recursive event handler calls from AES events. Use positive integers to specify how many recursions to allow. For example, a value of 20 allows 20 recursions before halting processing. A value of 3 here would allow only three recursions.

If set to 0 (default), the Check Out buttons are enabled when appropriate.

• When set to 0 (the default) or left as null, the LID values are accepted.

  A security role is only added to the user if the logical ID matches the current Mongoose instance logical ID.

• When set to 1, the LID values are ignored.

  All security roles that are found in the SUM BOD are applied to the user.

• 0 or null: The admin license module is not automatically assigned to all users.
• 1 (default): The admin license module is automatically assigned to all users.

This is part of the process required to allow end users at an enterprise that has both a Mongoose-based application and ION to see and respond to notifications and prompts from either system, in either system's user interface.

This process default determines how the groups assigned to a user should be treated when synchronizing user records with Infor OS Portal or Infor Ming.le:

• When set to 0 or left as null (the default), any groups that are assigned to the user in Mongoose, but that are not referenced by (or known by) Infor OS Portal or Infor Ming.le are automatically removed from the user record in Mongoose during synchronization.
• When set to 1, the default behavior is overridden and the groups assigned to the user are left intact in Mongoose. In this case, if you want to remove a group membership for a user in Mongoose you must remove it manually on the Users form.

• When set to 0 or left as null (the default), any license modules that are assigned to the user in Mongoose, but that are not referenced by (or known by) Infor OS Portal or Infor Ming.le are automatically removed from the user record in Mongoose during synchronization.
• When set to 1, the default behavior is overridden and the license modules assigned to the user are left intact in Mongoose. In this case, if you want to remove a license module assignment for a user in Mongoose you must remove it manually on the User Modules form.

If set to 0 (default), these state records are deleted.

If you need to view the state history of successfully executed events, you can temporarily add this process default and set it to 1. However, the tables containing this state history information grow quickly and adversely affect performance.

This process default was created as a temporary workaround for functionality now provided in ION.

If set to 1, this process default directs that the BOD itself be searched for logical ID information, when dealing with a multi-site environment.

An unresponsive, or orphan, session is different from a session where the user is simply inactive. For example, these situations can cause an unresponsive session:

• Network problems such as a loss of connection
• Problems with the primary domain controller
• A restart of the computer where the user was logged into the client, after the computer froze for some reason

If a session has a process currently running through the IDO layer, the session is not closed, even if it has stopped sending ping messages.

If no value is set for this on the Process Defaults form, then orphan sessions are not automatically closed. The interval at which the client sends a "heartbeat" ping is specified in the Client Minutes to ping session process default.

• Default (default): Treats all literal strings as Unicode strings.
• Ansi: Treats all literal strings as non-Unicode strings.

  Use this option when a non-Mongoose database table makes use of non-Unicode strings.

• Smart: Looks at each string in turn and attempts to determine whether it is Unicode or non-Unicode and processes it accordingly.

Mongoose-based applications build queries that are submitted to the database using literal strings. The literal strings that are used are normally SQL Server Unicode strings.

In the case of non-Mongoose database tables, however, it is possible that non-Unicode columns have been defined in the database tables. In that case, the 'where' clause that uses a Unicode literal string fails to properly use the indexes defined on the table, because it first converts the value in the column to a Unicode value in order to compare it to the Unicode literal. This results in an index scan instead of an index seek.

This means that, if non-Unicode data is defined in a table, a non-Unicode literal is desired, so that you get index seek operations instead of index scan operations.

Valid values for this process default include:

• PAD(x)
• LEFTPAD(y)

where x/y is a single standard keyboard character.

The prefix depends on how the form IDs are handled in Infor OS Portal or Infor Ming.le. You can use the application name as the prefix.

For Mongoose, the prefix is set to CSI_ so, for example, the Customers form is shown in the context message as CSI_Customers.

The default value is empty, which means to use the "Message Bus Logical ID" for this site (from the Sites form).

For a site with a message bus ID of:

lid://infor.mongoose.mongoose/default

The customer can specify that the security roles will have this LID:

lid://infor.mongoose.mongoose

In this case, the full security role will be:

<SecurityRole>
<ID lid="lid://infor.mongoose.mongoose">my-role</ID>
<Description>my role description</Description>
</SecurityRole>

When set to 0 (default), this process default disables client caching of IDO and form metadata.

See Maintaining or Discarding the Local Metadata Cache.

The method must be implemented by the application development team. If specified, this method is called by the framework before each explorer folder node is expanded.

If you want to disable this process default, just change the name in the Default Value field. For example, you might add "Disabled" to the end of the value.

See About “pruning” the Master Explorer folder display.

• Allow: This setting allows any user with valid credentials to sign in and use the smart client from a network-connected computer.
• Deny: (Default) This setting prevents all users from signing in using a smart client from a network-connected computer. .
• PerUser: This setting allows for selective permission to sign in remotely. This setting requires explicit permission for each user, using the Allow Remote WinStudio Sessions option on the Login Information tab of the Users form.

If the value of this process default is not defined, a default internal value of 5,000 is used.

Valid values include all non-negative integers.

This process default creates a separate record cap for reports and allows reports to query more records than queries from other types of forms.

In a multi-tenant farm environment, this process default cannot be used to override the FarmReportMaxRecordCap (farm-wide setting for reports).

\\TaskMan_Path\Output Files\ReportName_GUID.FileExtension

All report files reside in the Output Files folder and are distinguished by the session ID appended to the report name.

When this option is set to 0 (default), the report output destination depends on report output settings on other forms.

This setting can be overridden for any particular report output on either the Background Task Definitions form or the Report Options form. Custom paper sizes can be defined on the Report Paper Sizes form.

See List of report paper size options.

Valid values for this process default are [blank], 0 (zero), and positive integers. Values of [blank], 0, or any non-valid value all disable this feature, which means that the token never expires. By default, this process default is not set and is blank.

Valid values for this process default include:

• Enabled: The right-click action is enabled and the Help option is displayed in all context menus.
• EnabledWithoutHelp: The right-click action is enabled and the Help option is hidden in all context menus.
• Disabled: The right-click action is disabled and context menus are not displayed.

If this process default is not defined, the system defaults to 1.

See About "round robin" polling.

If this process default is not defined, the system defaults to 1000 (one second).

See About "round robin" polling.

• 0 (disabled, default): Overrides are discarded once the user signs out. The selected option for both User Data Record Cap and User List Record Cap sections in User Preferences are cleared and use the default record cap.
• 1 (enabled): Overrides are saved even after the user signs out. The selected option for both User Data Record Cap and User List Record Cap sections in User Preferences are retained.

This process default needs to be added by the user manually and not added by default.

This process default determines whether context messages are sent. If set to 1, the context message is sent when the form is active.

This is typically required in situations where Send Email actions can be initiated in response to a BodOnReceive event.

Another purpose of this process default, in the Application Schema Tables Metadata form, is to populate the Site Column Name field, if empty, with its value.

Also, the SQL Tables form uses this process default.

If the Send Context Message on Form Focus process default is set to 1, the Support Product ID is included in the context message.

• debug: This option runs the current TaskMan thread in debug mode. (Messages are explained in the Creating and Customizing Reports guide.)
• debugrep: TaskMan creates a text file containing a log of messages generated during the running of a report. To use this option, a txt extension for a document type must be defined in the Document Types form. This setting should only be used for report debugging purposes, and must be removed as soon as testing is done.
• eventlog: When debugging background tasks (with the debug option above), TaskMan directs its debug logs to the toolset messaging systems, which can be viewed through the IDO Runtime Host or Log Monitor utilities. If you want to direct TaskMan debug logs to the Windows event systems so you can view and debug them through the Windows Event Viewer, use this option.
• taskmsg: If this is specified, TaskMan inserts some task-specific messages while processing requested tasks. This allows you to review the status/process of tasks. These messages can be viewed in the Task Messages area on the Background Task History form.

When set to 0, the backward-compatility SessionContextNamesBase gets updated. When set to 1 (the default), the SQL Server session variables are used instead.

Valid values are all non-negative integers. A setting of 0 (default) indicates that there is no threshold; in other words, user accounts are never disabled because of inactivity.

See Disabling Inactive Accounts.

Valid values include all non-negative integers. A setting of 0 (default) does not specify a maximum number and honors the default system setting.

See the help topic "About caps".

This process default is automatically enabled in on-premises environments. This setting is disabled or displayed as read-only for multi-tenant farm environments where farm-wide record caps have been set.