Default Name

Allow saving form  runtime changes

If set to 1 (default), allows users to save minor changes to a form made during normal operations. These changes include:

• 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, allows form developers to specify a scripting language other than the default for individual scripts, effectively overriding the setting for the default scripting language.

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

If the name but no value is specified, the system default is to set this value to 1.

Browser inactivity lock minutes

The number (integer, 0 or greater) in the Default Value column instructs the system how long 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, WinStudio locks the computer. To resume the session, the user must enter the user password.

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

Client minutes to ping session

If set, determines the interval, in minutes, at which clients send ping messages to the IDO layer to indicate that the client is still connected and working. For more information, see Minutes to close orphan sessions.

Collection read mode

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.

If all queries should see only data for which the query can get a shared lock, set the value to Committed.

If queries can read and display data that has not yet been committed in the database, set the value to Uncommitted (the default value). 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 may 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 the optimistic locking will fail. You must refresh the record to get valid data before making changes and saving.

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

Form developers can override the Collection read mode 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 WinStudio design mode.

Default script language

Specifies the default scripting language for custom WinStudio scripts. Valid values include:

• Visual Basic
• Visual C#

If the value is not specified or set to a valid value, the system defaults to Visual Basic.

Disable record cap override save

Indicates whether user overrides of record caps persist (are saved) from one session to the next.

Possible values are 0 (disabled) or 1 (enabled). The default value is 1.

Enable audit logging

Indicates whether messages are entered in the audit log.

Possible values are 0 (off) or 1 (on).

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.

IDO checkout disabled

If set to 1, the Check Out buttons for IDO editing forms are always disabled.

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

ION pulse interface

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 not set or set to 0 (zero), 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.

Minutes to close orphan sessions

When set, specifies the number of minutes after a "heartbeat" ping to allow a session to remain open after it has become inactive.

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

If no value is set for this process default, 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.

Non unicode literal

Specifies whether the system is to treat strings as Unicode or non-Unicode strings. Valid values include:

• Default – Treats all literal strings as Unicode strings. This option is the same as not setting this process default at all.
• 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

Specifies the number of times to retry a save operation before a SQL Server deadlock error is returned to a client PC.

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

NUMSORTCHAR numeric pad

Specifies whether padding should be used between the alphabetic and numeric parts of a NUMSORTCHAR field when both types of characters are used in an <alphaPrefix><numericSuffix> format. If padding is specified, this default also specifies what character should be used for the padding.

Possible values include:

•  Pad(x), where x is any alphanumeric character.
• Pad('x'), where the x is any alphanumeric character.
  This option is useful in cases where you want to specify a space as the pad character.
• Pad(), where no pad character is specified, in which case there is no padding between the alphabetic prefix and the numeric suffix.

For example, if an <alphaPrefix><numericSuffix> format is specified for a field with a length of 10 characters, and the value "T455" is entered, by default (with this process default not set), the system displays it as "T000000455".

NOTE: This process default applies only when the <alphaPrefix><numericSuffix> format is used. If only numeric data is entered in the field, the system pads the numerals to the left with spaces, regardless of the setting of this process default (for example, '      T455'). If any other combination of alphanumeric characters is used, no padding is used, regardless of the setting of this process default (for example, 'T455A').

Objects metadata linkage

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, allows 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 (zero), disables client caching of IDO and form metadata.

For more information, see Maintaining or Discarding the Local Metadata Cache.

Report output obfuscation

When this option 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 (the default), report output is directed into the following paths, unless a Report Output Directory is specified in the Report Options form or a Report Output Folder is specified in the 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

TaskMan options

Specifies TaskMan debug options. These options are immediately applied to the TaskMan service and continue in effect until you delete this setting from the Process Defaults form. You can specify one or more of the following, separated by commas, semicolons, or spaces:

• debug - Run the current TaskMan thread in debug mode.
  (Messages are explained in the Reporting Guide.)
• debugrep - 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 will insert some task-specific messages while processing requested tasks, allowing 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

Specifies the number of days of inactivity to allow before a user account is disabled. If set to zero (0), indicates that there is no threshold; in other words, the process default is disabled.

For more information, see Disabling Inactive Accounts.

WinStudio max record cap

Specifies the maximum number of records users can retrieve in a query. The default value, 0, does not specify a maximum number and preserves the default behavior of WinStudio. Under View > Settings, users can specify record caps for data and drop-down lists, choosing to retrieve all records or a maximum number of records that user specifies. The value of this process default, if nonzero, overrides the user settings with a system-wide upper limit on the number of records that can be retrieved.

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