List of process defaults

Process defaults are settings that system administrators can make to control various aspects of how the system responds to user commands and actions.

This table lists the process defaults that are included with the system. Where a default value is given, it means that the process default value has not been set on the Process Defaults form.

There are also application-specific process defaults.

Process Default Description/Valid Values
Admin License Module Name This process default specifies the license module for an admin user. The default value is MGCoreTrans.
AES From Email use Intranet or Site This process default specifies which email address the Application Event System is to use to send notifications.

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.

Allow saving form  runtime changes If set to 1 (default), users can save minor changes, such as these, to a form made during normal operations:
  • 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.

Note:  This is different from the ability of a user with editing permissions of Basic or higher to save a user version of their form. This setting allows all users to save minor run-time changes and does not require users to have Design Mode permissions.
Allow script language selection If set to 1 (default), form developers can specify a scripting language other than the default for individual scripts, effectively overriding the system setting for the default scripting language.

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

Asterisk as required indicator Deprecated.

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.

Browser Component BG Render Interval This process default can be needed when running a report that contains browser-based components as a background task. These browser-based components include components such as charts or gauges. This is because the chart or gauge can be not finished rendering before the report is processed.

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.

Browser inactivity lock minutes A positive integer in the Default Value column specifies how many minutes to allow a user session to remain idle before locking the user out. For example, if this process default is set to 30, then, if a user were to leave the computer with the session still running, after 30 minutes of inactivity, the computer is locked. To resume the session, the user must enter the user password.

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

Check for New Message Interval This process default determines the interval, in minutes, at which the system checks the Inbox for new messages, and sends a notification.

This process default value must be a positive integer.

Client Diagnostic send to LogMonitor When set to the default value (0), this process default prevents the Log Monitor Service from collecting messages of type Diagnostics.

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.

Client minutes to ping session This process default determines the interval, in minutes, at which clients are to send ping messages to the IDO layer, to indicate that the client is still connected and working.

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

Collection read mode This process default specifies the global transaction isolation level to use for queries. transaction isolation level

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.

Combined Toolbar User Preference Use this process default to set Combined as a Toolbar Mode in the User Preferences form as the default behavior of the toolbar. These are the valid values:
  • 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.
Component Name as HTML Attribute This process default is used to set the mgShowName value.
Note: When a user signs in and creates a Mongoose web session, both the Mongoose IFrame’s URL and the web.config file are examined for the mgShowName value. This value then affects both the overall session information along with extra data being sent to the browser client with every form retrieved.
  • 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.
Conditional actions case sensitive

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.

DateTime in Client Time Zone This process default is used to display time in the user's local time zone.

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.

Default script language This process default specifies the default scripting language for custom form or global scripts. Valid values are:
  • Visual Basic (default)
  • Visual C#
Disable Form Aliasing This process default is used to disable form aliasing. Form aliasing is the procedure to redirect a named form to another named form. When a form is opened, the corresponding form alias will open instead. This also extends to actions, including hyperlinks, right-click menus, and the open form dialog.

If set to 0 (default), Form Aliasing is enabled.

If set to 1, Form Aliasing is disabled.

Email Notifications for Datalake This process default instructs the system to send a notification email to the designated recipients whenever failures or mismatched records are encountered during the localization process.

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.

Enable audit logging This process default specifies whether messages are entered in the audit log. Valid values are:
  • 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.

Enable Automatic Get More Rows Use this process default to enable the application to automatically retrieve more rows as the user scrolls through a grid, without requiring the user to click the option to “Get More Rows”. The additional records are retrieved and load automatically as soon as the vertical scrollbar has reached its end. At that point the number of new records retrieved are limited by the effective record cap.

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.

Enable Inbound BOD Prioritization This process default is used to enable the prioritization of the incoming BODs processing.
  • 0 (false, default): The prioritization of processing the inbound BOD is disabled.
  • 1 (true): The prioritization of processing the inbound BOD is enabled.
Enable Remote Logging This process default is used to view message logs remotely. Valid values are:
  • 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.

Enforce prefix from Access As If set to 1, this process default enforces a prefix on names, based on the Access As identifier, for any user-created:
  • 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.

Error if API Exceeds Max Cap If this process default is set to 1, the API LoadCollection requests returns an error when:
  • Bookmark is not enabled
  • API exceeds FarmAPIMaxRecordCap setting
Note: This process default only takes effect if FarmAPIMaxRecordCap value has been set.
Filter Validation This process default is used to control the scope of validation for any filters used for LoadCollection requests. This process default has three valid values:
  • 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.

FormSync notifications email address This process default is used to store the contact email information that is required in Form Sync upgrades and patch command line options.
Note: This information can be overridden by the currently available -m and -mail command line options.

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.

Framework Event Max. Recursion Depth An internal setting sets a cap of 9 on recursive event handler calls generated by an Application Event System (AES) event. When this limit is reached, the system stops processing the relevant AES handler.

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.

Caution: 
This process default should rarely be used, and then only for emergency or special-use cases. It is useful mostly for very specific troubleshooting cases and should be used only if and as directed by an Infor Customer Support representative. A high value for this process default could result in system disruptions.
IDO checkout disabled If set to 1, the Check Out buttons for IDO editing forms are always disabled.

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

Ignore LogicalID in SUM SecurityRole This process default determines how the logical ID (LID) values for a SecurityUserMaster (SUM) security role should be treated when synchronizing user records with Infor OS Portal or Infor Ming.le:
  • 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.

Inbound SUM Assign Admin License This process default specifies whether the admin license module is automatically assigned to all users, while processing the inbound SecurityUserMaster BOD.
  • 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.
ION pulse interface This process default specifies whether to synchronize the Application Event System inbox data with ION. If this process default is set to 1, then the system creates notifications to send to ION, and monitors incoming notifications, routing them into the AES inbox.

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.

Keep Groups in SecurityUserMaster

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.
Note: This process default has no effect on the ability to add roles to users in Infor OS Portal or Infor Ming.le, which end up as group memberships for that user in Mongoose.
Keep Modules In SecurityUserMaster This process default determines how the license module access 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 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.
Note: This process default has no effect on the ability to add license modules to users in Infor OS Portal or Infor Ming.le, which end up as license modules for that user in Mongoose.
Keep successful event states If set to 1, the application event system saves a set of state records while an event is running.

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.

Logical IDs aliased in BOD Deprecated.

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.

Minutes to close orphan sessions This process default specifies the number of minutes after a "heartbeat" ping that a session can remain open after it has become unresponsive.

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.

Note:  After setting or resetting this value, you must restart the IDO Runtime Service. After the restart, any new orphan sessions will be removed using the information in this process default. However, orphaned sessions that existed prior to the restart must be manually deleted from the database, using the Session Management form.
Caution: 
Restarting the IDO Runtime Service terminates all application sessions, so ensure that all users are out of the system before restarting this service.
Non unicode literal This process default specifies whether the system is to treat strings as Unicode or non-Unicode strings. Valid values include:
  • 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.

NUMSORTCHAR numeric pad This process default specifies overrides to the default padding inherent with a NUMSORTCHAR datatype field when both alphabetic and numeric characters are used in an <alphaPrefix><numericSuffix> format or only numeric characters. If default padding is overridden, this default also specifies what character should be used for the padding.

Valid values for this process default include:

  • PAD(x)
  • LEFTPAD(y)

where x/y is a single standard keyboard character.

Note: 
  • When this process default is set, only new NUMSORTCHAR values are affected. Once a NUMSORTCHAR value has been padded and persisted, this process default has no further effect on that value.
  • The settings you make for this process default are global; that is, they affect all NUMSORTCHAR data type fields, wherever they might appear in the application.

See About NUMSORTCHAR field padding.

Objects metadata linkage This process default specifies the name of the IDO metadata (objects) database that is linked to the application database. This is created by Configuration Manager.
Optional Context Message Form Prefix This optional process default defines the form prefix to make Mongoose-based application forms unique across all applications in the Infor OS Portal or Infor Ming.le portal. The default value is mongoose_.

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.

Outbound SUM Role LID Override This process default is used by the SecurityUserMaster (SUM) outbound BOD and the SecurityRoleMaster (SRM) outbound BOD as an override to the site logical-Id for the <SecurityRole> element.

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>
Note: This process default is intended for use primarily by system administrators setting up the application for use with Infor OS Portal or Infor Ming.le.
Persist WinStudio metadata cache When set to 1, this process default causes the system to continue client caching of IDO and form metadata to XML files on client computers. This is typically done to allow better, faster startup performance.

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

See Maintaining or Discarding the Local Metadata Cache.

Prune Explorer Folder Callout This process default is used to specify a user-defined callout method whose purpose is to prune out form names from an Explorer folder that should not be shown to the current user. The specification must be in the form: IDOName.MethodName.
Note: The IDOName and MethodName are determined by the application developers.

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.

Remote WinStudio Sessions This process default controls what users, if any, can sign in to using a remote session across a network. Valid values are:
  • 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.
Report Batch Size This process default is a fallback for the Report Batch Size property if the property value is -1.

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

This value is the fallback for the report forms that have a Report Batch Size property value of -1.
Note: The value of this process default is not set initially.
Report max record cap This process default specifies the maximum number of records that users can retrieve at a time on report-type forms or DataView reports.

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

Report output obfuscation When this process default is set to 1, all report output is directed into this path:

\\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.

Report paper size This process default specifies what size of paper should be used when printing reports. Valid values include most common paper sizes.

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.

REST Token Lifetime (sec) This process default allows you to limit the amount of time that a web service REST token is valid after its creation. The time limit is set in terms of seconds. When the time limit is reached, the server no longer accepts the token, and the web service can no longer use that token.

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.

Right-Click Context Menu To hide the Help option in context menus, use this process default. You can also use this parameter to globally disable right-click actions, thus, disabling all context menus. This settings applies only in Runtime Mode.

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.
Note: If you do not configure this process default parameter, then the right-click context menu and the Help option are enabled by default.

Alternatively, with a form open in the Web Designer (web client), or in Design Mode (Windows client), to hide the Help option in the context menus of your chosen form components, you can specify the NOHELP() keyword as a Format attribute.

See NOHELP keyword.

Round Robin Batch Size This process default specifies how many configurations/databases the TaskMan is to poll at one go. Valid values are positive integers.

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

See About "round robin" polling.

Round Robin Polling Interval (ms) This process default specifies the amount of time, in milliseconds, that TaskMan is to pause, after one round is complete, before beginning the next round of polling.

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

See About "round robin" polling.

Save record cap override This process default specifies whether user overrides of record caps persist (are saved) from one session to the next. Valid values are:
  • 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.
Send Context Message on Form Focus This process default is set to 1 by default.

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.

Service AES Originator This process default designates a user ID to be used when no "From" data is available for a Send Email event action. This user ID must be the username of a valid system user.

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

Site Reference Column Name This process default designates a value in the SiteRef column of a multi-site table created by the Data Maintenance Wizard instead of the default value, which is "SiteRef".

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.

Support Process ID This process default is used to enable the support of publishing of Infor Business Context message.

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

TaskMan options This process default specifies TaskMan debug options. These options are immediately applied to the TaskMan service and continue in effect until you delete the setting from the Process Defaults form. You can specify one or more of the following, separated by commas, semicolons, or spaces:
  • 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.
Use session variables This process default determines whether the data in the SessionContextNames table is to be moved to SQL Server session variables. SessionContextNames is now a view that looks at either SQL Server session variables or looks at a backward-compatibility table named SessionContextNamesBase.

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

User inactivity threshold This process default specifies the number of days of inactivity to allow before a user account is disabled.

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.

User Preferences Max Record Cap This process default specifies the maximum number of records that users can retrieve in a query.

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".

Note: Unlimited queries can adversely affect performance and exceed the resources of the utility server and the client machine.

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.