List of Basic 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 basic process defaults that are supplied 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 might also be some application-specific process defaults.

See these additional process defaults for this application.

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.
Allow saving form  runtime changes If set to 1 (default), users cam 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 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.

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.

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.

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

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 record cap override save This process default specifies whether user overrides of record caps persist (are saved) from one session to the next. Valid values are:
  • 0 (disabled): User overrides are saved.  
  • 1 (enabled, default): User overrides are not saved.
Enable audit logging This process default specifies whether messages are entered in the audit log. Valid values are:
  • 0 (off): Messages are entered.
  • 1 (on, default): Messages are not entered.

If the audit log is on, WinStudio automatically sends messages 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.

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.

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.

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.

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.

ION pulse interface This process default specifies whether to synchronize the Application Event System inbox data with ION Pulse. 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 application and Infor ION to see and respond to notifications and prompts from either system, in either system's user interface.

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 funtionality 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 CloudSuite Industrial 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 builds 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.

Number of deadlock retry attempts This process default specifies the number of times to retry a save operation before a SQL Server deadlock error is returned to the client PC.

The valid range includes all non-negative integers. A value of 0 (default) instructs the system not to discontinue attempts to complete the save operation.  

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

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: (Default) This setting allows any user with valid credentials to sign in and use the smart client from a network-connected computer.
  • Deny: 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 output obfuscation When this process default is set to 1, 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.

If this option is set to 0 (default), report output is directed into these paths, unless a Report Output Directory is specified in the Report Options form or a Report Output Folder is specified in the Sites or Sites/Entities form:

\\TaskMan_Path\Output Files\UserID\ReportName_Site_TaskNumber.FileExtension

\\TaskMan_Path\Output Files\UserID\Preview\ReportName_Site_TaskNumber.FileExtension (for preview)

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

See List of report paper size options.

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.

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

WinStudio max record cap This process default specifies the maximum number of records that users can retrieve in a query.

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

See  About Caps.

Note:  Unlimited queries can adversely affect performance and exceed the resources of the utility server and the client machine.
Related topics
About Process Defaults
Setting a Process Default