System Setup

This is the two-character language code you want to use by default for all users. Examples include EN, FR, ES, DE, ZH.

If the Multi-language for document printing option is enabled, then you can select the Configure List hyperlink to select up to 80 language codes that you want to use within the system for multi-language document printing.

This ensures that characters are rendered correctly when using SYSPRO Reporting Services.

This is used to output a script or text file in the \Base\Settings folder to monitor and debug problems in e.net or SQL environments.

These options enable you to monitor SYSPRO and CMS only license usage to more accurately predict when you are about to run out of licenses.

This lets you indicate the point at which you want to record a log entry for SYSPRO license limits.

For example: If you currently have a 50-user SYSPRO license and you enter 5 in this field, then an audit log entry is created when the 45th operator logs in.

The log entry created is: Login attempted - license limit approached and is output to the System Audit Query program.

This lets you indicate the point at which you want to record a log entry for CMS only user license limits.

For example: If you currently have a 10 CMS only user license and you enter 3 in this field, then an audit log entry is created when the 7th CMS only user operator logs in.

The log entry created is: Login attempted - CMS license limit approached and is output to the System Audit Query program.

This lets you configure system-wide license parameters.

Changes are validated as part of the registration mechanism and will require you to update the license registration details for each company.

This indicates the number of Contact Management users allowed to run the system concurrently.

• Denoted by IMPCMO in the IMPACT.INI file.

This defines the maximum number of users that may access the Universal Data Dictionary concurrently via ODBC. You won't be allowed to make any changes to the dictionary.

• Denoted by IMPODB in the IMPACT.INI file.

This indicates the number of Dialog System seats you have purchased (if you purchased the Micro Focus Dialog System), which allows you to customize screens using the Screen Customization Kit.

This indicates the maximum number of users who may access the SYSPRO Analytics Viewer concurrently.

• Denoted by IMPSVS in the IMPACT.INI file.

This indicates the maximum number of companies that can be used concurrently on a site.

This indicates the number of Espresso licenses that you have given your customer, allowing them limited access to queries and transaction posting applications.

• Denoted by IMPESX in the IMPACT.INI file.

This lets you indicate whether your entry at the User name login prompt refers to the operator code, or whether the system must use the network user name to establish the operator code.

This lets you indicate whether access to the User name field is allowed.

This lets you indicate whether access to the Company field is allowed.

If you enabled the Use generated SQL user details option then you can enter characters that you want to prefix the operator code with and use as the SQL login name.

Leave the field blank if no prefix is required.

Enter the maximum number of characters for the password.

This can be a value of between 0 and 128 but cannot be less than the minimum password length.

Enter the minimum number of alphanumeric characters (A – Z, a-z) that must be included in the password.

This can be a value between 0 and 99.

This indicates the password assigned to the administrator login.

This indicates the password assigned to the SQL Server standard user login.

Indicates the temporary folder for storing intermediate bulk copy format files (*.bcp).

In a 3-tier environment, ensure that the temporary folder is available to both SQL server and the application tier.

Typically, use a Universal Naming Convention (UNC) address (e.g. \\server-name\path-to-shared-resource).

This lets you change the format in which you want all system dates to be displayed and printed within SYSPRO.

Although your selection here does not affect the way in which dates are stored in the system (i.e. this is always in a CCYYMMDD format), there are instances where SYSPRO overrides your preferred date display format and shows dates in a CCYYMMDD format.

This typically occurs in list views where the date column can be used for sorting purposes.

This indicates how the system will display the short version of the date.

It does not affect the way dates are physically stored on file, it merely provides an alternative way of viewing and printing them.

You can override this date format at company level.

The date entered here is used to display the samples in the date fields below.

This indicates a sample of how the Short date format will appear in the system.

This diagnostic can be used to troubleshoot problems when synchronizing contacts between SYSPRO and Outlook using the Contact Management to Outlook Sync program.

Select this diagnostic, save your changes, exit SYSPRO and rerun the Contact Management to Outlook Sync program. This creates logs in the %temp% folder on the client, with the following structure: CMSSync_OperatorCode_DateTime.txt.

This enables the Show Events Window diagnostics option on the SYSPRO Ribbon bar (SYSPRO Ribbon bar > Administration > Diagnostics).

The events window traces all application events that occur in the normal running of SYSPRO.

The output of the events window is saved in \settings\operator_dev02_debug.txt on the client machine.

This debug file can be sent to SYSPRO for analysis to help troubleshoot problems.

This creates an enetlog.dat and enetlog.idx file in the \Base\Settings folder on the application server.

Each time a business object is executed, this diagnostic code causes the e.net Solutions infrastructure to write to these files.

Typical information written to these files includes:

• Transaction date
• Transaction time
• Operator Business object
• Method name (Post, Logon, Query, Log off, etc.)
• Return status ( a non-zero return status indicates an exception was raised)
• GUID Error messages

You use the Diagnostics Manager program to view these e.net transactions in a list view. The program also lets you to clear the transaction log.

These log files can grow rapidly in size.

Reserved for future use.

This outputs a diagnostic log of all XML strings being parsed or generated (both XmlIn and XmlOut). The files are generated in the \Base\Settings\Diag_log folder.

This outputs a diagnostic log of all XML strings generated (XmlOut only). The files are generated in the \Base\Settings\Diag_log folder.

This initiates Analytics client logging.

The server side logging in a live environment is in a sub folder called SYSPROAnalytics in the system temporary folder of the machine on which the SYSPRO Analytics Server components are installed (e.g. C:\Windows\Temp).

The client side logging is written to a SYSPROAnalytics sub folder in the client side temp folder.

This is a combination of san001 and san002.

This is equivalent of enabling san001 through to san004.

This causes the SYSPRO Office Integration infrastructure to output a log of the process that follows each time a user makes use of the Office plugins.

The file is generated in your temp folder and has the naming convention: SOI_OperatorCode DateTime.txt (e.g. SOI_ADMIN 20xx-xx-xx 08-17-24.txt).

A new file is created each time a new instance of the SOI addin is created.

This causes various programs that have been optimized for SQL to output a trace of the SQL statement being issued. This includes the SQL statements issued by the Report Writer.

Only a trace of the last SQL statement issued is output.

The generated file {oper}.sql is created in the \Base\Settings folder (where {oper} indicates the operator code). For example: the ADMIN operator would create a file called: |Base|Settings|ADMIN.SQL.

Reserved for future use.

Reserved for future use.

This causes the SYSPRO Reporting Services infrastructure to output a log of the process that follows each time a report is run. It also outputs the xmlin that was passed to the business object.

The file is generated in your temp folder and has the naming convention: SRS_OperatorCode DateTime.txt (e.g. SRS_ADMIN 20xx-xx-xx 08-17-24.txt).

A new file is created each time a new instance of SRS is launched.

This initiates server-side logging for all SRS document printing processes, except archiving.

The {oper}.txt log file (\Base\Settings) is generated on the application server - where {oper} is the operator code. For example: the ADMIN operator would have a file called: |Base|Settings|ADMIN.TXT.

This is a combination of srsd001 and srsd002 (i.e both server side and client side logging is enabled).

This saves SRS Document Archiving business object XML to the temp folder.

This activates the diagnostic tool for SYSPRO Reporting Services.

This incorporates all logging from printing and archiving and can drastically affect performance. It is equivalent of having all options Srsd01 through to srsd06 enabled.

The generated file (OperatorName.txt) is output to the \Base\Settings folder of your SYSPRO installation.

The file contains an entry referencing a _T*.DAT temp file in your temporary folder as well as the generated XML. The following files are generated in the temporary folder:

• *.rpt
• *.xml
• *.xsd

Open the *.xml file to see if any errors were generated.

This creates a ??????.txt file in the \Base\Settings folder on the application server (where ?????? indicates the operator code) containing details of all file transfers between the application server and the client workstation. This is typically used to identify problems with self-healing and error messages relating to screen sets and customization settings.

Files transferred include:

• Automation settings
• Customization settings
• Screen set files
• User control files
• Temp files

This displays a message box after each file transfer that occurs between a client and server.

If this code is enabled and you receive an Error 153 message when you log into SYSPRO, it indicates that the message box program itself may not be available on the client workstation. You will need to edit the IMPACT.INI file and remove the sys03 value for the IMPCOM= entry.

Reserved for future use.

This stops the program from deleting any of the files created during the print phase:

• The template file ({operator}-{template}.dot) that was copied to the temporary folder on the client.
• The temporary file that contains the data extracted to print. This file resides in the temporary folder used by SYSPRO on the application server.

This creates a server-side log file (??????.txt) in the \Base\Settings folder on the application server (where ?????? indicates the operator code). This file traces the server-side program execution which can be useful when trying to locate an error during either the design or print phase.

This performs the function of WORD97 and WORD99 (i.e. outputs the client and server side logs as well as attempts to save the normal.dot file).

This indicates the folder that is used for creating temporary files typically used for sorting.

This indicates the 2nd folder in which you want to store data files for your companies.

This indicates the 4th folder in which you want to store data files for your companies.

This indicates the 6th folder in which you want to store data files for your companies.

This indicates the 8th folder in which you want to store data files for your companies.

This indicates the name of the SQL Server hosting the database.

Specify the SQL authentication login here.

This lets you confirm that you can connect to SQL based on your login information entered.

This indicates the address to the reporting host service (e.g. localhost:1979).

Enter the scheduler authentication user name and password.

These are the Windows Task Scheduler permissions that allow the operator to create and maintain schedules on the server.

This lets you purge the document print queue automatically.

This indicates the SOAP port that has been configured for the SYSPRO 8 e.net Communications Load Balancer.

This indicates your active directory in the Microsoft Azure portal.

Your SYSPROOfficeCloud application will be added to this folder.

This indicates the client ID of the SYSPROOfficeCloud application added to your active directory in Microsoft Azure.

This lets you indicate the companies that you want to enable for the Rules Engine.

After configuring this setting and restarting SYSPRO, the following processes occur in the background:

• The applicable SQL tables are created within the SYSPRO database (their names prefixed by the word Rules).
• A new SYSPRO operator is created: __RUL. This operator is required in order for the services to run.

This lets you indicate the companies that you want to enable for Harmony.

Indicate the address to the SYSPRO 8 Harmony Service which is used to process Harmony transactions.

For example: net.tcp://localhost:33334/HarmonyService (where localhost is replaced by your server IP address).

Select an authentication mode to use when processing transactions on the Harmony database.

Provide a valid SQL login name for the Harmony database.

This lets you test the SQL connection to the Harmony database with the parameters indicated.

Enable this option for purging to take effect.

This option is disabled by default.

This indicates the period after which purging will take place.

This indicates how old data can be when surfaced to the Harmony client.

By default this value is 3 months.

This is the prediction endpoint address of the SYSPRO Artificial Intelligence service (e.g. http://localhost:30238/SYSPROMLE/rest) that is used by the SYSPRO Machine Learning module to perform predictions.

This lets you start Bot conversations with an options menu instead of a "What can I do for you" message.

This indicates the SRS order acknowledgment format description.

This indicates the SRS delivery note format description.

This indicates the SRS invoice format description.

Specify a server image path to be displayed on the SYSPRO Bot login screen

This is the default IP address of the specific SMTP server that SYSPRO will use to send messages when the user requests a password reset.

This the email account's user name.

This is the server port to be used.

This lets operators change their own passwords.

Enter the number of days that must elapse before operators are required to change their passwords.

A daily countdown is activated by the system 7 days before a password is due to expire, warning operators to change their passwords.

To prevent operators from attempting to cheat the system by changing the system date on the workstation the server's operating system date is used when calculating the expiry period. The system date on the client workstation is ignored.

When a password expires, the operator is prompted to change the password immediately by entering the old password, followed by the new password.

The expiry period is calculated from the time you set the password. For example: If you set the expiry period to 60 days, but only define the password against the operator on the following day, then the 60 day count down begins from the following day.

Passwords for operators belonging to a system administrator group never expire.

This forces operators to define a new password when next they load SYSPRO. This can be applied per operator, or for all operators.

You typically use this when adding new operators and applying an arbitrary password to the operator code. When the new operator logs into SYSPRO for the first time, the operator can define a new password as required.

Operators who do not define a password are locked out of SYSPRO (with the exception of the ADMIN operator). This lock can be removed manually using the Operator Maintenance program.

Operator selection

Select the operators who you want to force to change their passwords. The following options are available:

• All
• Range - select a range of operators
• Single - select a single operator

Select Maintain to use the Send Email program to change the template that is used to send out the email regarding a password change request.

This lets you create a password that can be used as a substitute whenever an operator password is requested.

This is useful when access to an operator's account is required but the operator is either unavailable or has forgotten the password.

The supervisor password can also be used instead of the Alternate Password defined against the operator.

This lets you confirm the supervisor password.

This lets you allow the operator to reset the password.

This will enable the Forgot password link on the SYSPRO login window.

Select Maintain to use the Send Email program to change the template that is used to send out the email with the temporary password details.

This lets you notify the system administrator when an operator has exceeded the number of login attempts.

Specify the minimum number of characters for a password.

A minimum of 4 characters is recommended.

This lets you indicate that at least one alphabetic character must be included in the password.

You can optionally specify whether the alphabetic character must be in uppercase or lowercase.

Forcing passwords to contain a mix of upper and lowercase characters contributes to an increased level of password security.

If you enabled the Verify new password against password history option, then you can enter the number of previously-used passwords to retain for comparison purposes. The default is 3.

When an operator enters a new password, that password is compared to the previously-used passwords.

Enable this option if Multi-Factor Authentication is required when an operator logs into SYSPRO.

This option is disabled by default.

Indicate which operators to apply Multi-Factor Authentication to.

Select the Configure button to open the MFA Operator Configuration program to define this operator list.

This method sends an email to the defined MFA operators containing a Time-based One-time Password (TOTP) that is required as part of the verification process.

Enable this option if you require SYSPRO operators to be managed by Microsoft Active Directory (AD), once assigned within the Active Directory User Management program.

This results in access to SYSPRO being controlled by Microsoft Active Directory (AD) for the defined operators.

Enable this option to receive an email whenever operators managed by Microsoft Active Directory (AD) require configuration or management in the Active Directory User Management program.

The following variables are passed to the email template when the Microsoft Active Directory (AD) synchronization takes place:

• $SsoUserCount$

  Count of users added for review.

• $SsoOpChanged$

  Count of operators with changes (email, name, etc.,).

• $SsoOpActivated$

  Count of operators who’s status has changed to active from disabled or removed.

• $SsoOpDisabled$

  Count of operators who’s status has changed to disabled.

• $SsoOpRemoved$

  Count of operators who’s status has changed to removed.

Enable this to receive an email if the SYSPRO 8 Active Directory Sync Service fails.

The following variables are passed to the email template when the Microsoft Active Directory (AD) synchronization takes place:

• $FailedMsg$

  If the synchronization fails then this contains the message as it is written to the log file.

Enable this to receive an email every time the SYSPRO 8 Active Directory Sync Service runs successfully.