Manage System Settings

In 'System Settings. Open' (MNS090), you can define the system settings.

This table shows the available parameters for the system:

Program ID/Panel Field Description
(MNS090/E) System language The system language is retrieved in this order:
  1. From the user/company setting 'User. Access per Company Division' (MNS151)
  2. From the user 'User. Open' (MNS150)
  3. From the system settings (MNS090).
(MNS090/E) Decimal format If nothing is specified, the default value is .-Period.

The decimal format is retrieved in this order:

  1. From the user (MNS150)
  2. From the division 'Company. Connect Division' (MNS100)
  3. From the company 'Company. Open' (MNS095)
  4. From the system settings (MNS090)
(MNS090/E) Date separator If nothing is specified, the default value is --Dash.
(MNS090/E) Time separator If nothing is specified, the default value is :-Colon.
(MNS090/E) Character table If nothing is specified, the default value is Q256.
(MNS090/E) Usage w blank div Indicates how blank division in 'Function. Connect Authorization by Role' (SES400) is used.

These are the options for Usage w blank div:

  • 0-'Allow for all divisions': A blank division entry for a function means the user will be able to run the function with the corresponding authorization for all divisions in the company. However, a non-blank division authorization will override the blank division authorization.
  • 1-'Allow only for blank division': A blank division entry for a function authorizes the user to the blank division only. In order for users to be authorized for the function in non-blank divisions, an entry for each division must be created.
(MNS090/E) API security Indicates what type of authorization should be used for API transactions.

These are the options for API security:

  • 0-'No security'
  • 1-'Security according to SES005'
  • 2-'Security according to permissions in SES400'
(MNS090/E) Auth indivd pgm Indicates that these user-defined APIs, EXPORTMI, MDBREADMI, CMS100MI, and LISTMI must handle authorization of data in table CSYTAB. This also applies to the 'CSYTAB. Export' (CMS240) program and API CMS240MI.
These are the options for Auth indivd pgm:
  • 0-'Table's browse program': The browse program connected to table CSYTAB in 'Table. Open' (MNS120) is used to check the user's authorization to the table's data.
  • 1-'Individual browse program': The browse program maintaining a type of data, Constant value (STCO), is used to check the user's authorization to data.

    Since the CSYTAB table is used by many programs for different purposes, 1-'Individual browse program': option is preferred from a security perspective but may require more function security setup. The Constant value (STCO) in the table is used to identify the various types of data and to which program a record belongs.

    This is an example of an authorization of data:

    Browse program (CMS240) is connected to table CSYTAB in (MNS120). A user is athorized to (CMS240).

    When 0-'Table's browse program': is used, a user who is authorized to function (CMS240) can view all data in CSYTAB. If a user is not authorized to (CMS240), they cannot access the data in CSYTAB.

    When 1-'Individual browse program': is used, the browse program for CSYTAB in (MNS120) is not considered. Instead, a user who is authorized to 'Country. Open' (CRS045) function but not to 'Salesperson. Open' (CRS100) function can access data with constant value 'CSCD' (Country). However, they cannot access the data with constant value 'SMCD' (Salesperson) in CSYTAB.

(MNS090/E) Blank brw pgm Indicates whether tables with no browse programs in 'Table. Open' (MNS120) can be used by EXPORTMI and MDBREADMI.

These are the options for Blank brw pgm:

0-'Allow list of records': This bypasses the security control for EXPORTMI and MDBREADMI, and enables the APIs to extract data from tables with blank browse program.

1-'Block list of records': This enables the security control for EXPORTMI and MDBREADMI, and blocks the use of tables with blank browse program. To enable the usage of such tables by the APIs, a browse program should be added in the table in (MNS120).

(MNS090/E) Restrict chars Controls if restricted characters like %,&,? should be allowed in identifiers, file names etc.
(MNS090/E) Auth new func The field indicates if automatically added new functions in 'Function. Open' (MNS110) should be set up as requiring authorization.
(MNS090/E) Env responsible Used as a recipient of application messages when no physical user exists, for example sending application messages from an auto job where user M3 is used. Currently not implemented anywhere.
(MNS090/E) Comp for appmsg Indicates the company used for application messages created without any relation to a company.
(MNS090/E) Out serv user Defines the service user for output management. It is used by autojob (MNS950) for resending output and updating job status.
(MNS090/E) Dt of migration The date is display-only and can only be updated through API transactions.

To set the date, MNS100MI, transaction SetMigrateDate has been created which sets the date per division. When set in a division, it is copied as the overall date of migration in (MNS090) if nothing is set.

(MNS090/E) Tenant act date This date indicates the date when the tenant was provisioned. This is a display-only field.
(MNS090/E) Max search rows Defines how many rows Infor Enterprise Search should return to M3 Business Engine (before any filtering in the function).
(MNS090/E) Max show rows Defines how many search rows that should be displayed in M3 BE.
(MNS090/E) Email vld

Indicates the email address validation that enforces input rules in 'Email Address. Open' (CRS111), 'User. Open' (MNS150), and 'Output Media Selection. Open' (MNS205) interactive programs and APIs.

These are the options for Email vld:

  • 0-'No validation': No input validation and accepts all email addresses.
  • 1-'OWASP': Enforces basic email validation rules based on OWASP standards.
  • 2-'RFC 5322': Email validation rules based on IETF technical standards that only accepts Latin characters.
  • 3-'RFC 6530': Email validation rules that are also based on IETF technical standards which accepts non-Latin characters in addition to Latin characters.
(MNS090/E) Email IP addr Indicates the email server address.
(MNS090/E) SMTP srvr port Indicates the SMTP server port.
(MNS090/E) Crypt protoc Indicates the security protocol to use when communicating with the email server.
These are the alternatives:
  • 'No encryption': blank protocol
  • 'SSL-Secure socket layer': SSL protocol used
  • 'TLS-Transport layer security': TLS protocol used
(MNS090/E) User Indicates a user identity in an external system.
(MNS090/E) Password Indicates a password for a user in an external system.

(MNS090) shows the 'Date of migration' field which indicates the date when the migration took place. This also exists in (MNS100) when migrating divisions that were done one by one.