Runtime parameters in the ConfigurationParameter table

This parameter sets a default for the notification type for scheduled requests. The valid values are 1 (Never), 2 (On Failure), 3 (Always), and 4 (Action Group).

When a user runs a top-level background action and chooses to schedule the action, the user can select the notification option and thus override the default notification type.

For invoked actions, users cannot select a notification option. In this case, the async.notificationtype.default value will be used, if it has been set. If it has not been set, the system will use On Failure if an email address was entered for the request, and Never otherwise.

Action Group is a special notification type for actions that invoke other actions. It means a success notification will be sent when the entire group is done. However, if any action group member fails, a failure notification will be sent. If an action is invoked in the background outside the action group, that action inherits this notification type but starts its own, separate group.

This parameter can be set on a tenant application data area or on the tenant environment data area. Application data area settings override the tenant environment data area setting.

If set to true, notification information (notification type and email addresses) is copied from the invoking action to the invoked actions. That is, if a background action invokes another background action, regardless of being in the same or different background group, if this parameter is set to true, whatever notification options are on the invoking action will default to the invoked action. Whatever was specified on the topmost action the user scheduled will follow through to any nested background actions.

The default is false

This parameter allows an administrator to control whether actors will receive email notifications based on the existence of an email address in the actor record.

If a request triggers a notification and an email address was specified for the request, then a notification email is sent to that address. In addition, an email may be sent to the actor on the request. Whether an email is sent in this case depends on whether an email address exists on the actor record and on whether the async.actor.notify parameter is set to true.

Note that if the actor is an external actor, you may want to exclude them from getting an email. To do this, use the mail.expression.include and mail.expression.exclude parameters.

If set to true in the tenant environment data area, sets Async to manual configuration instead of automatic. The system then does not validate, create, or remove any requests for any of the tenant's application data areas unless this setting is overridden at the data area level. If false, then configuration is automatic, meaning the system validates and creates or removes requests unless this setting is overridden at the data area level.

The default is false.

If set to true in the tenant environment data area, sets Async to manual configuration for the specified application data area. The system then does not validate, create, or remove any requests for this data area. If false, then configuration is automatic, meaning the system validates and creates or removes requests for this data area.

If set to true in the tenant environment data area, then all application data areas are included if not overridden at the data area level. If false, then data areas are not included unless overridden at the data area level.

If set to true in the tenant environment data area, then the specified application data area is included and records are created if not present. If false, then the data area is excluded and records are removed if present. If this setting is not present, it defaults to the global async.default.include setting. If the data area setting is present, it overrides the global setting. This value if ignored if the async.manual.config.dataarea setting is true, or if that setting does not exist and the async.manual.config is true.

When set in the tenant environment data area ConfigurationParameter table, this determines the default number of retries for all async actions in all application data areas. The default is 10.

You can override the default set in the tenant environment data area by setting this parameter in a specific data area. The value you specify becomes the default for that data area.

The default value is applied when the record is saved, but if a value is specified at the time of scheduling the action, that value overrides the default.

If set to true, a default queue will be created for each data area when needed. If set to false, the system will not create a default queue for each data area, but will rely on the existing queue or queues. The default is true.

If set to false in an application data area, this parameter reverts job stream processing for job streams that were not defined to use step parallel processing to the previous behavior (that is, behavior prior to release 11.0). With the previous behavior, job steps were processed serially with the exception that any jobs spawned by a step were processing independently.

If this parameter is not set or is set to true, then the job stream processing will wait for a step’s spawned jobs to finish before processing the next step.

If set in an application data area, the amount of time in seconds that the stream executor will wait for actions in that data area to complete before going into "WaitForActionGroup."

The default is 60 seconds.

If set in an application data area, the amount of time in seconds that the stream executor will sleep in that data area between checks while within the "max.poll.wait.seconds" time-frame.

The default is 5 seconds.

Set this to true in an application data area to enable you to print or view running statistics for all set actions in that data area. These statistics can aid in determining if an action is doing significant work per transaction.

You view the statistics by selecting the View Trigger Stats drill around on the Triggers form.

You should only set this parameter to true if directed to do so by support personnel. To activate statistics collection, you will also need to use the Save History option for the queue.

Set this to true in an application data area and specify the business class and action in order to enable you to print or view running statistics for a specific set action in that data area. These statistics can aid in determining if an action is doing significant work per transaction.

You view the statistics by selecting the View Trigger Stats drill around on the Triggers form.

You should only set this parameter to true if directed to do so by support personnel. To activate statistics collection, you will also need to use the Save History option for the queue.

This parameter and the mail.expression.exclude parameter enable you to control who gets email notifications. By using regular expression syntax in the and mail.expression.exclude parameters, you can control who is allowed to receive such emails.

Example:

mail.expression.include=.*@.*acmecorp.com$ means that email notifications would only be sent to actors whose email address ends in mail.expression.include.acmecorp.com.

This parameter, in conjunction with the async.notification.email parameter, enables a system administrator to configure the email notifications for cases where a future effective dated transaction fails, including whether email notifications are sent, who receives the email notifications, and for what types of transactions the notifications are sent.

Valid values are 1 (Never), 2 (On Failure), and 3 (Always).

This parameter, in conjunction with the async.notification.type parameter, enables a system administrator to configure the email notifications for cases where a future effective dated transaction fails, including whether email notifications are sent, who receives the email notifications, and for what types of transactions the notifications are sent.

The type of this parameter is EmailAddressField. Valid values are an email address for where emails should be sent.

The async administration email gets notified of all failures regardless of the setting for this parameter.

If the async.notification.type parameter is set to any value other than 1 (Never), standard notification rules apply: Any specified email address is notified and if the actor has an email address, they are also notified unless inclusion/exclusion rules filter out their address.

When set to true in the tenant environment data area, then in all data areas an AuditLogEntry business class is created and then populated with the key identifying data of audit log entries (such as actor, action, effective date, and so on). This is done only for online user transactions and Infor Spreadsheet Designer web service transactions. The full audit log entries are still created as before for each business class that implements auditing. The AuditLogEntry business class can be examined via standard database tools or replicated for analysis by business intelligence tools.

When set to true in the tenant environment data area, audit log entries will be created when users view a list or form or change data in the Web UI and Infor Spreadsheet Designer. Note that selects do not create entries and paging a list will not create entries (only the first access does). You can also have web services calls create audit log entries by including &_clientType=UI in the URL.

The default value for this parameter is false. Also, the default is to not include the list of fields if a form or list name is available (which it will be in normal user interactions). If the form or list name is not available (which can occur is the form or list is accessed programatically), then the list of fields is included. To change this behavior, use the IncludeListFormFieldsViewed and IncludeNonListFormFieldsViewed parameters.

If the CreateViewLogEntryRecords parameter is set to true and you set this parameter to true in the tenant environment data area, then the default behavior of the CreateViewLogEntryRecords parameter is changed. That is, the audit log entries will include the list of fields if a form or list name is available.

The default for the IncludeListFormFieldsViewed parameter is false.

If the CreateViewLogEntryRecords parameter is set to true and you set this parameter to false in the tenant environment data area, then the default behavior of the CreateViewLogEntryRecords parameter is changed. That is, the audit log entries will not include the list of fields if a form or list name is not available (as may be the case if the list or form was accessed programatically).

The default for the IncludeNonListFormFieldsViewed parameter is true.

Set this parameter to true to include future corrections when the include.entrys.after.correction parameter is true. Set this parameter to false (default) to ignore future history corrections.

This parameter can be set in the application data area or in the environment data area. Settings in application data areas override a setting in the tenant environment data area.

Set this parameter to true to replicate all audit log entries after a history correction. Set it to false (default) to ignore history corrections that change records that have already been replicated.

This parameter can be set in the application data area or in the environment data area. Settings in application data areas override a setting in the tenant environment data area.

Set this parameter to true to replicate all audit log entries after a retroactive change and set it to false (default) to ignore retroactive changes that change records that have already been replicated.

This parameter can be set in the application data area or in the environment data area. Settings in application data areas override a setting in the tenant environment data area.

This parameter sets the size for chunks of data when replicated data is being exported. The default is 1000000 (1MB).

This is an approximate size. After a row of data is exported, if the current buffer size exceeds this value, an additional file will be created for the replicated data. The data files will include a number, starting at 0, to indicate the incremental files. Note also that the names of the data files are based on the replication set name and the replication set class name, but that any dots and spaces in those names are replaced with underscores.

These parameters set the transaction size for replication sets that have the Enable Indicator Replication check box selected and are exporting the data in JSON format. This check box is only available in replication sets for business classes whose LPL implements the incremental replication pattern and sets up the indicator field. If the indicator field is enabled, it determines when records should be incrementally replicated.

The json.indicator.transaction.size parameter applies to all business classes. The json.indicator.transaction.size.BusinessClass parameters enable you to set a transaction size that applies to a single business class.

When configured for a business class, this parameter must be set in the application data area that the business class resides in. The global parameter can be set in the application data area or the environment data area, with the application data area setting taking precedence.

When the replication process hits the number of records specified for the transaction size, the chunk size, or the end of records, data is written.

These parameters set the transaction size for replication sets that have the Enable Indicator Replication check box selected and are exporting the data in XML format. This check box is only available in replication sets for business classes whose LPL implements the incremental replication pattern and sets up the indicator field. If the indicator field is enabled, it determines when records should be incrementally replicated.

The xml.indicator.transaction.size parameter applies to all business classes. The xml.indicator.transaction.size.BusinessClass parameters enable you to set a transaction size that applies to a single business class.

When configured for a business class, this parameter must be set in the application data area that the business class resides in. The global parameter can be set in the application data area or the environment data area, with the application data area setting taking precedence.

When the replication process hits the chunk size or the end of records, data is written. When the number of records specified for the transaction size is hit, the current data string is saved for recovery purposes.

These parameters set the transaction size for replication sets that have the Enable Indicator Replication check box selected and are exporting the data in CSV format. This check box is only available in replication sets for business classes whose LPL implements the incremental replication pattern and sets up the indicator field. If the indicator field is enabled, it determines when records should be incrementally replicated.

The csv.indicator.transaction.size parameter applies to all business classes. The csv.indicator.transaction.size.BusinessClass parameters enable you to set a transaction size that applies to a single business class.

When configured for a business class, this parameter must be set in the application data area that the business class resides in. The global parameter can be set in the application data area or the environment data area, with the application data area setting taking precedence.

When the replication process hits the chunk size or the end of records, data is written. When the number of records specified for the transaction size is hit, the current data string is saved for recovery purposes.

Add this numeric type sets the maximum size in megabytes parameter for the actor image file. Add this parameter and enter a value different that the default of 2MB is you need a different size.

Note that if the actor record is opened in the application data area context, the value from the application data area is used. If opened in the environment data area context, the environment data area value is used. It is recommended that these values be kept in sync or the environment data area has a value as large as the largest data area value.

Optional. This parameter is created by the Enable Configurable Features action on the Configuration Parameters list. If this parameter exists and the value is Yes, the Configurable Features tab is enabled on security roles. Configurable Features allows security administrators to control user interface and Landmark features users can and cannot use.

When Configurable Features is enabled, all the security roles should be tailored to enable and disable the appropriate user interface features. Configurable features can also be viewed on actor records.

Optional. Add this parameter if special characters do not export to CSV or Excel properly.

Create a parameter with Type: Alpha, Length: 20 (or large enough for the value you enter)

Value: Can be one of the following (the first two being literal values)

• writebyteordermarker

• systemdefault

• Any valid, supported character set

If you intend to open the export file in Excel, we recommend trying writebyteordermarker first.

These parameters enable you to set a limit at three different levels of specificity for controlling the number of rows a user can export from a list to CSV. This is useful since exporting a large number of rows (such as several hundred thousand or more) can result in memory issues.

list.variable.column.sizes

<businessclass>.<list>.list.variable.column.sizes

Optional. Add a parameter to turn off variable column sizing in PDF files generated from all lists or from a particular list. Variable column sizing means PDF files generated from lists allocates column width based on data type, data size, and label size. Wrapping still occurs, but larger fields generally get more space than smaller fields.

Create a parameter with Type: Boolean and set the value to false.

You can determine the businessclass and list values using Ctrl + Shift + left-mouse click. View the list and hover over the form element you want and press Ctrl + Shift + left-mouse click. An information pop up displays. It includes the business class and name information.

If the parameter is not defined, the default value is true.

cardview.split.rows

<businessclass><list>.cardview.split.rows

cardview.right.column.split.rows

<businessclass><list>.cardview.right.column.split.rows

Optional. Add a parameter to turn off split rows in PDF files generated from all card view lists or from a particular list. Card view lists can contain rich text fields that can contain a lot of content, so it is helpful to allow rows to split across pages.

Create a parameter with type Boolean and set the value to false or true.

If the parameter is not defined, the default value is true. However, the default for the right column still has split rows off, so to enable the right column row splitting, you should add a .right.column.split.rows parameter and set the value to true.

These parameters enable you to set a limit at three different levels of specificity for controlling the number of rows a user can export from a list to PDF. This is useful since exporting a large number of rows (such as several hundred thousand or more) can result in memory issues.

Use this configuration parameter to adjust the placement of images in the header of generated PDFs. Adjustment may be needed because of the varying size of the images used in the header (such as the user images named "reportfirstpageheader" and "reportpageheader" ). Also the font offset applied to the header may create a need for image adjustment.

You can use these settings:

• top - If necessary, pushes the header below the image.
• bottom - If necessary, pushes the header such that the image will be just above the underline.
• none - Makes no adjustment.
• auto - Uses "top" when the header image is left or center aligned, and otherwise uses "bottom". This setting is the default.

Use this configuration parameter to adjust the placement of images in the footer of generated PDFs. Adjustment may be needed because of the varying size of the images used in the footer (such as the user image named "reportpagefooter").

You can use these settings:

• true - Adjusts bottom margin when image infringes.
• footertext - Makes the same adjustment as "true" but also moves the footer text above the image.
• none - Makes no adjustment.
• auto - Uses "footertext" when the footer image is center aligned, and otherwise uses "true". This setting is the default.

The value should be a valid time zone as defined in the Time Zones configuration in Configuration Console. Because the value must match the time zone name as defined in Time Zones screen, we recommend changing the default time zone in Configuration Console > Data Area > Time Zones rather than adding the parameter to Configuration Parameters. See the Configuration Console User Guide for steps to set the default time zone.

Create this parameter (if not present) and set to true in order to enforce a paging size limit for web service list calls. Enforcing a paging size limit can help avoid long-running processes that can impact user interface performance.

The paging size is set with the ws.paging.size configuration parameter. If you do not set that parameter, a default value of 200 is used.

If you enforce page sizing and also specify a "_LIMIT" parameter value, the "_LIMIT" value will only be used if it is less than the ws.paging.size value, if that is specified, or if it is less than 200 if there is no ws.paging size value specified.

When set to true in the tenant environment data area, business tasks can be invoked via the web services layer. This applies to business tasks that are not directly in the context of a business class, and makes these tasks available for REST APIs. Delivered actions include moving configurations from tenant to tenant, and using the configuration export and configuration import utilities, thus enabling you to automate these otherwise manual processes.

When set to true in a data area, the web services raw data Create action API includes the ability to add a file attachment, for example an image file. The default is false. You can set this parameter on an application data area or on the environment data area.

Set this parameter in an application data area in order to enable or disable validation on xref values.

When set to false, in Infor Process Automation if a user adds or updates an xref value, validation will not occur when the optional check box is unchecked, or when the length exceeds the set length.

When set to true, in Infor Process Automation if a user adds or updates an xref value, validation will occur for length and required fields.

The default is false.

If set to true, enables SMTP server authentication. For more information, see Enabling and configuring SMTP server authentication.

Use this to indicate the sent email store protocol to use when storing emails sent from Landmark, such as imap for Internet Message Access Protocol (IMAP).

Use this to indicate the host for storing the emails for a given store protocol.

Use this to indicate the Landmark service for sent email store authentication. The default name for the email store service is "EMAIL." If you do not set this parameter but enable users for the sent email store feature, the system will look for identity records for the EMAIL service.

Use AlphaUpper as the type when creating this parameter.

Set the value for this to either a Boolean value (true or false) or to the name of an actor group. Use all uppercase letters for the actor group value and use AlphaUpper as the type when creating this parameter.

The system will use the values for this parameter and the previous one as follows. When the email is requested, the system will check if a StoreSentMessages.ActorID parameter exists for the actor in play. If the parameter exists, then no further checking is done; a true value enables the feature and a false value disables it. If the previous parameter does not exist, a check is done for StoreSentMessages. If it exists and if the value is true, the feature is enabled. If it is false, the feature is disabled.

If the value is the name of an actor group and the actor in play is in that group, the feature is enabled. Otherwise, if the actor is not in the group or the group does not exist, it is disabled.

If the feature is enabled but the configuration is missing or incorrect, the message will still be sent (providing there are no errors via the transport, typically SMTP) but the store will not be updated and errors will be logged.

The socket connection timeout, in milliseconds, for the specified email protocol server.

This parameter and the mail.email<protocol>.timeout parameter are passed to the email server. For these to have an effect, the email server must be configured to use them. See https://javamail.java.net/nonav/docs/api/com/sun/mail/smtp/package-summary.html.

The socket read timeout, in milliseconds, for the specified email protocol server.

This parameter and the mail.<protocol>.connectiontimeout parameter are passed to the email server. For these to have an effect, the email server must be configured to use them. See https://javamail.java.net/nonav/docs/api/com/sun/mail/smtp/package-summary.html.

This parameter enables you to configure the regular expression used to validate email addresses. If you add this parameter, set the type to Alpha make the length sufficient to hold the size of the regular expression you enter as the value.

The default regular expression is:

^([A-Z0-9'_%-]+[\\.])*([\\+A-Z0-9'_%-]+)@([A-Z0-9-]+[\\.])*([A-Z0-9-]+[\\.])[A-Z]{2,6}$

To set up your regular expression for email validation, consult standard resources on Java regular expression syntax.

Specify a proxy email address to which to send all outbound emails. If this parameter is not set, then emails go to their usual destinations.

This parameter can be set in the application data area or in the environment data area. Settings in application data areas override a setting in the tenant environment data area.

Specify a regular expression to be applied to non-proxy email addresses to determine whether or not a particular email address is exempt from being sent to the proxy email address. To set up a regular expression, consult standard resources on Java regular expression syntax.

This parameter can be set in the application data area or in the environment data area. Settings in application data areas override a setting in the tenant environment data area.