System Setup

SYSPRO Ribbon bar > Setup > Setup Options > System Setup

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

This lets you save and print inventory notes against stock items in up to 80 languages.

Any existing stock code narrations (i.e. narrations saved in your database with spaces against the language field) are then labeled as Global Notes.

The global narrations print by default when printing documents (if you don't select the Print Foreign Text option).

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 indicates the nationality of your site.

Entering one of the reserved nationality codes (i.e. CAN, USA, AUS, RSA, UK) affects the display of certain fields (e.g. tax-related) within the system.

The list of SYSPRO nationality codes is defined in the IMPNAT.IMP file located in the \Base\Store folder.

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

This facility is only applicable to systems configured with a double-byte language (e.g. Simplified Chinese).

This is used by support personnel to identify your site.

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.

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.

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.

  • Sensitive information (such as licensing information) is not logged (e.g. COMLGN does not log the XML passed).
  • This log file can grow rapidly in size.

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

  • Sensitive information (such as licensing information) is not logged (e.g. COMLGN does not log the XML passed).
  • This log file can grow rapidly in size.

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

  • Sensitive information (such as licensing information) is not logged (e.g. COMLGN does not log the XML passed).
  • This log file can grow rapidly in size.

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 initiates Analytics server logging that is output to a sub folder (SYSPROAnalytics) in the temporary folder of the machine on which the SYSPRO Analytics Server components are installed.

This is a combination of san001 and san002.

This saves the business object and business layer XML to your temp folder.

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.

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.

This accumulates all SQL statements to the log file.

The generated file {oper}.SQL is created in the \Base\Settings folder (where {oper} is the operator code).

For example:

The ADMIN operator would have a file called: |Base|Settings|ADMIN.SQL.

This log file can grow rapidly in size.

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 initiates client-side logging for all SRS document printing processes except archiving.

The client side logging is created in the client side temp folder and is called Comp_?_Oper_{oper}_SRSLog.txt where ? is the company code and {oper} is the operator code.

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

This initiates SRS Document client side archive logging only.

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

This lets you place the entire system into maintenance mode and prevent unauthorized access to all companies in your environment while conducting maintenance. It solves the issue of having to maintain each SYSPRO company to prevent operators from capturing data in SYSPRO or e.net Solutions when you're conducting maintenance (e.g. upgrading to a new release).

The login process checks this configuration before the company-specific maintenance mode (in the Company Maintenance program) to either allow or deny access to the system.

Only operators who form part of a group with system administrator rights can log into SYSPRO while this option is enabled.

If other operators still require access to SYSPRO during the maintenance period, you can enable the Override when company logins prevented option against their operator code (Operator Maintenance). This override only applies to operators logging into SYSPRO (i.e. it does not apply to e.net Solutions).

Indicate the message to display to any unauthorized operator attempting to access the company during the maintenance period.

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

This logs a record when the number of SYSPRO licenses used reaches the value set in the Log within x users of maximum field.

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 log a record when the number of CMS only users reaches the value set against the Log within x CMS users of maximum field.

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 maximum number of companies that can be used concurrently on a site.

An entry of 0 means that up to 36 companies may be defined for this system.

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

  • Denoted by IMPCMO= in the IMPACT.INI file.

This indicates the number of Point of Sale users allowed to run the system concurrently.

  • Denoted by IMPPOS= 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 defines the maximum number of users that may be running the U/SQL Manager concurrently.

An entry other than 0 indicates that you intend modifying the Universal Data Dictionary (UDD) using the U/SQL Manager software.

  • Denoted by IMPUSQ= 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 number of Client Access Licenses (i.e. SQL Server seats) as defined by Microsoft that matches your license information.

  • Denoted by IMPCAL= in the IMPACT.INI file.

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 users who can concurrently be defined as report designers and may therefore design reports using the SYSPRO Reporting Services program.

  • Denoted by IMPRSD= 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 seats you are licensed to use.

Espresso user licenses are allocated using the Espresso User Licenses program.

  • Denoted by IMPESP= in the IMPACT.INI file.

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 indicates the number of licensed workflows, if you are using the Workflow Services Professional module.

  • Denoted by IMPWFL= in the IMPACT.INI file.

This indicates the number of named-users that have access to the SYSPRO Supply Chain Portal.

Portal users are created and maintained using the Portal User Management program. These users have limited access to portal-specific functions.

  • Denoted by IMPPOR= in the IMPACT.INI file.

This lets you indicate that each of your SYSPRO concurrent licensed users has access to SYSPRO Espresso.

  • Denoted by IMPESL= in the IMPACT.INI file (where 1 means checked).

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 lets you indicate your preferred date display format.

Dates in forms are determined by the Presentation format only (i.e. DDMMYY or YYMMDD).

The short/long date format isn't applied to any date fields in forms

You can tailor your date format using separators (e.g. /,-), as well as additional text within single quotation marks.

For example:

'Today is my birthday' dddd dd MM.

dddd

The day of week (e.g. Monday)

ddd

Abbreviated day (e.g. Mon)

dd

A two-digit day of month (e.g. 01 through 31)

d

A zero- suppressed one digit day

D

A zero-suppressed day of month with 'st', 'nd', 'rd' and 'th' (e.g. 1st, 2nd, 3rd, 4th, etc.)

MMMM

The month in full (e.g. September)

MMM

The month abbreviated (e.g. Sep)

MM

A two-digit month

M

A zero-suppressed one digit month

yyyy

A four-digit year (e.g. 2007)

yyy

A three-digit year (e.g. 007)

yy

A two-digit year (e.g. 07)

y

A one-digit year (e.g. 7)

H

A zero-suppressed 24 hour format

HH

A two-digit 24 hour

h

A zero-suppressed 12 hour format

hh

A two-digit 12 hour format

m

A zero-suppressed minute

mm

A two-digit minute

s

A zero-suppressed second

ss

A two-digit second

tt

A two-character AM/PM indicator

This indicates how the system will display the long 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.

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.

This format is used when you insert the date stamp during the editing of text notes in SYSPRO. You can override this at company level using the Override system date format option (Setup Options > Company > General).

This indicates how you want to represent the Printed: date that appears in the footer of reports alongside the name of the operator who printed the report.

The other dates printed on the report are rendered according to the short date format.

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

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

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

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

This indicates the default folder in which you should store all your multimedia files. If undefined, this defaults your working directory.

Although this field is disabled on the client, you can use the Edit Client Configuration function to define the path on the client.

This indicates the primary location for your SYSPRO data files. You may define alternate folders and configure companies to use alternate locations as required.

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

This indicates the 3rd 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 5th 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 7th 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 9th folder in which you want to store data files for your companies.

This indicates the location of your Requirements Planning snapshot files.

These files are created when you take a new snapshot from within the Requirements Calculation program (if the Requirements Planning module is installed).

These options are ignored for operators configured for Single Sign-on.

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.

You won't be allowed to select the Network user name option if the system detects that there are operators with duplicate network user names. You will first need to ensure that the network user name is unique for all operators.

Indicate the default entry you want to use at the User name field of the Login window.

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

This lets you indicate whether you want the system to remember previous successful user names entered.

These are stored in the \Base\Settings folder on the server (in the [UserName] section of the Login_Dialog_xxxx.TXT file, where xxxx is the network user name).

This lets you indicate the default entry you want to use at the Company field of the Login window.

This lets you indicate whether you want the system to remember previous successful login attempts.

These are stored in the \Base\Settings folder on the server (in the [UserName] section of the Login_Dialog_xxxx.TXT file, where xxxx is the network user name).

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

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 (i.e. access to SYSPRO will be controlled by Microsoft Active Directory (AD) for the defined operators).

Define the endpoint for the SYSPRO 8 Active Directory Sync Service used when installing the service (e.g. net.tcp://MachineName:8733/SYSPRO.AD.Sync.Service).

Select the Test AD connection hyperlink to confirm that your settings are configured correctly.

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 whose status has changed to active from disabled or removed.

  • $SsoOpDisabled$: Count of operators whose status has changed to disabled.

  • $SsoOpRemoved$: Count of operators whose status has changed to removed.

Select the Configure review email template hyperlink to define the review email template and indicate who must be notified when new users (belonging to the SYSPRO.ERP security group) are added to Microsoft Active Directory (AD)

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.

Select the Configure failure email template hyperlink to define the failure email template and indicate who must be notified if synchronization fails.

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

To avoid receiving excessive emails we recommend that you direct these to a specific address for later viewing.

Select the Configure success email template hyperlink to define the success email template and assign which email address must be used.

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

This option is disabled by default.

Multi-Factor Authentication ensures that operators are required to enter an additional authentication method over and above their normal user name and password.

Indicate the operators that require Multi-Factor Authentication:

Select this to ensure that all operators require Multi-Factor Authentication when logging into SYSPRO (except for SYSPRO operators that have the operator code ADMIN - who should already have a strong password).

Be careful when selecting this option if you don't have an ADMIN operator.

Select this to ensure that all operators require Multi-Factor Authentication when logging into SYSPRO (except for SYSPRO administrators - who should already have a strong password).

This option is useful if your systems are down and operators can't access the defined authentication method in order to login to SYSPRO.

An administrator can then still access SYSPRO (without requiring validation by the authentication methods that have been configured) to suspend Multi-Factor Authentication and allow operators to login.

Select this to ensure that Multi-Factor Authentication only applies to specific operators.

Select the Define specific operators hyperlink to define the operators to which this applies.

Authentication emails make use of system-wide Email/SMTP settings, therefore ensure that the Use system-wide SMTP details setup option is enabled in the Setup Options program.

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.

Each password is valid for 5 minutes.

Indicate whether an operator can enter their own email address when first configuring the email authentication for logging into SYSPRO.

If this option is disabled, the email address defined against the operator code is used and can't be changed.

If the Operator can set own email address option is enabled, use this field to define the pattern to which the manually entered email address should conform.

Use the ; character to separate multiple entries, without spaces.

Indicate whether an operator is allowed to see the email address when logging into SYSPRO.

Select the Configure PIN email template hyperlink to define the email template that operators receive.

Select this to make use of the Google Authentication app (or FreeOTP) for authentication.

A QR code is generated when operators first configure their Google authentication for logging into SYSPRO and a Time-based One-time Password (TOTP) then becomes required as part of the verification process for the defined MFA operators.

A Time-based One-time Password (TOTP) is then required for all subsequent logins to SYSPRO.

Each password is valid for 5 minutes.

This validates operator access according to the SQL Server standard user login and password for all operators logging into SYSPRO by default.

You can override this at operator level (Operator Maintenance) which will allow you to trace SQL usage by SQL login.

Select this if the operator login and password required is the network login id that was authenticated by Windows NT.

This indicates the SQL Server name that will be used. This is typically the name of the computer on which SQL is running.

This indicates the SQL driver used in the connection string:

  • SQL Server (the default selection)
  • ODBC Driver 13 for SQL Server
  • ODBC Driver 17 for SQL Server

Only drivers that you have installed are displayed and available for selection.

Select this to ensure that the connection between SYSPRO and Microsoft SQL Server is encrypted.

If you enabled the Encrypted connection string option then you can select this to indicate that the encryption must use a self-signed server certificate.

This option is not available when the SQL Driver to use is defined as SQL Server.

Self-signed certificates don't guarantee security, as the encrypted handshake is based on NT LAN Manager (NTLM). We highly recommend that you provision a verifiable certificate on SQL Server for secure connectivity. Transport Security Layer (TLS) can only be made secure with certificate validation.

This indicates the database of SYSPRO's configuration tables.

Select this to use the SQL Server standard user login and password for all operators logging into SYSPRO.

Select this to use the Login name and Password defined against the operator when logging into SYSPRO.

Select this if you want SYSPRO to generate SQL login details for operators. This becomes the default SQL Login preference for all operators created in future.

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 blank if no prefix is required.

Up to 20 characters can be used. These characters cannot contain backslash or embedded spaces or start with $ or @.

Enter the minimum number of characters for the password. This can be a value of between 0 and 99, however a warning is displayed if less than 8 characters.

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.

The combined length of the following cannot exceed the Maximum password length:

  • Minimum digits required
  • Minimum letters required
  • Minimum special characters required

Enter the minimum number of digits (0 – 9) that must be included in the password. This can be a value between 0 and 99.

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.

Enter the minimum number of special characters (excluding [ ] { }( ) , ? * ! @) that must be included in the password.

This can be a value between 0 and 99.

This indicates the administrator login with the authority to perform advanced SQL functions.

This must be an account login that is a member of the sysadmin fixed server role.

This indicates the password assigned to the administrator login.

Indicates the standard user login.

The user entered here must have the following permissions enabled:

  • datareader
  • datawriter

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

This indicates the system-wide language character set used by the BULK INSERT statement when special characters exist that SQL Server needs to recognize.

The code page configured at company level takes precedence over the code page defined here.

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 use a SQL Managed Instance created in Azure (i.e. this makes programs use logic written specially for SQL Managed Instance).

This is the address that is used to store objects in Azure.

This indicates the credentials that will be used when accessing resources in the Azure Blob storage container.

This is the Azure external data source name (used by SYSPRO for Bulk Inserts).

This relies on SQL authentication for access to the database.

This passes the Windows NT credentials to SQL for authentication.

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

Specify the SQL authentication login here.

Specify the SQL authentication password here.

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

Indicate the name of the SQL server that will be used for the Harmony database.

Provide a valid SQL login name for the Harmony database.

Indicate the corresponding password for the SQL login.

This improves report rendering by moving the XML into a temporary SQL database before binding the data to the .RPT file.

It also frees up resources on the client workstation by transferring processing tasks to the server. The server generates a .PDF file which is sent to the client machine.

This option doesn't require Crystal on the client machine; only an appropriate report reader (e.g. Adobe Acrobat Reader, SYSPRO Office Integration, Espresso).

When enabling this option for the first time, the Documents.XML files are copied to Documents_Server.XML. When you subsequently update printers for documents, the relevant file is updated (i.e. Documents.XML for client-side and Documents_server.XML for server-side printing).

This improves report rendering by moving the XML into a temporary SQL database before binding the data to the .RPT file. All the processing is completed on the client machine.

This initiates client-side reporting (as it was in prior versions of SYSPRO) binding the report to the .XML file on the client machine.

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

Enter the scheduler authentication user name (i.e. the Windows Task Scheduler permission that allows the operator to create and maintain schedules on the server).

Enter the scheduler authentication password (i.e. the Windows Task Scheduler permission that allows the operator to create and maintain schedules on the server).

This lets you purge the document print queue automatically.

Enter the number of days (up to 999) you want an item to remain in the queue before it is automatically purged.

This indicates the IP address or server name where the SYSPRO 8 e.net Communications Load Balancer is installed.

This indicates the SOAP (Simple Object Access Protocol) port that has been configured for the SYSPRO 8 e.net Communications Load Balancer.

This indicates the REST (Representational State Transfer) port that has been configured for the SYSPRO 8 e.net Communications Load Balancer.

The Email/SMTP settings of the System Setup program are required for the following facilities:

  • Forgot Password
  • Multi-Factor Authentication
  • Single Sign-on
  • SYSPRO Supply Chain Portal

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 is the default email address of the sender of the message.

This entry must contain a valid email structure (e.g. auto.generated.mail@company.com).

This the user name of the email account.

This is the password of the email account.

This is the server port to be used.

This indicates that communication with the SMTP server requires SSL encryption (i.e. send email via an SSL connection).

Select this to use the Email/SMTP settings defined in the System Setup program for your companies (i.e. system-wide).

When you enable this option and save your selections, you are prompted to apply the settings to all your companies.

If you choose to update all companies, the Use system-wide SMTP details in the Setup Options program is enabled against each company.

If you choose not to update all companies, then the settings defined in the System Setup program only apply to new companies (i.e. existing companies are unaffected).

You can still manage these settings selectively by company using the Setup Options program (Setup Options > Company > General).

Unchecking the Use system-wide SMTP details option in the Setup Options program will use the settings configured in that program for the company.

The following facilities rely on the Email/SMTP settings configured in the System Setup program to work:

  • Forgot Password
  • Multi-Factor Authentication
  • Single Sign-on
  • SYSPRO Supply Chain Portal

Once you have registered and configured your application within Microsoft Azure, you need to configure your setup here and then configure the Office 365 credentials per operator (SYSPRO Ribbon bar > Home).

This indicates your active directory in the Microsoft Azure portal.

Your SYSPROOfficeCloud application will be added to this folder.

This indicates the URI address to your exchange web service provider.

This setting is used when resolving email addresses.

If you don't have an exchange server, you can use the default provided by Microsoft Office 365 (i.e. https://outlook.office365.com/ews/exchange.asmx).

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

This is pre-populated with https://login.microsoftonline.com.

The System Setup program needs to be accessed and saved so that the pre-populated entry in this field can take effect.

This is pre-populated with https://graph.microsoft.com.

The System Setup program needs to be accessed and saved so that the pre-populated entry in this field can take effect.

Indicate the SYSPRO Avanti website address on your local system (e.g. http://localhost/SYSPROAvanti).

This enables you to use the Notifications Inbox in SYSPRO Avanti.

Indicate the address of the Espresso Server which is used to push notifications to a user's devices (e.g. http://localhost/SYSPRO8Espresso).

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

After configuring this setting the following processes occur in the background:

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

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

Indicate the URL of the SYSPRO 8 Harmony API Service (i.e. the Harmony service installed within IIS).

For example:

http://localhost/SYSPRO8HarmonyAPI/ (where localhost is replaced by your server IP address).

Indicate the SYSPRO 8 Harmony Service address (used to process Harmony transactions).

For example:

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

The port number must match the entry made when installing the SYSPRO 8 Harmony Service.

These options let you indicate how much beat information (beat records and beat record information) is retained in the _Hrm database.

Enable this option for records to be permanently deleted from the database automatically.

This option is disabled by default.

Indicate how long beat records and beat information must be retained in the database (the default is 3 months).

For example:

If you enter 4 months, then no beat information will be older than 4 months.

This indicates the period after which purging will take place.

The data visibility options let you indicate the preferred time span when surfacing data inside Harmony.

This indicates how old data can be when surfaced to the Harmony client (the default is 3 months).

For example:

If you enter 3 months, then only beats 3 months old and younger will be surfaced to the Harmony client.

This reflects how data is surfaced to the Harmony client in years (i.e. if the entry at the Detailed data visibility (months) option exceeds 12 months.

This option is related to how data is surfaced to the Harmony client. It is used for calculating various aspects across beats within the system. These include:

  • Minimums
  • Maximums
  • Averages
  • Standard deviations
  • Importance of beats based on historical data in the system

In other words, all of these counters are used to determine how important a certain beat is.

By default this value is 3 months.

This reflects how summary data is surfaced to the Harmony client in years (i.e. if the entry at the Summary data visibility (months) option exceeds 12 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 is the training endpoint address to the SYSPRO Artificial Intelligence service (e.g. http://localhost:30238/SYSPROMLE/rest) that is used to train projects to generate a model that can be used to perform predictions.

Indicate the Azure App service URL/endpoint where the SYSPRO Bot is hosted (e.g. https://sysproken.azurewebsites.net).

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

This lets the SYSPRO Bot respond with debugging informational messages (i.e. additional error details).

Indicate the SRS order acknowledgment format to be used by the SYSPRO Bot.

This indicates the description of the SRS order acknowledgment format.

Indicate the SRS delivery note format to be used by the SYSPRO Bot.

This indicates the description of the SRS delivery note format.

Indicate the SRS invoice format to be used by the SYSPRO Bot.

This indicates the description of the SRS invoice format.

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

Enter the organization name to be displayed on the SYSPRO Bot login screen.

Enter the website URL to be displayed as a link on the SYSPRO Bot login screen (e.g. https://syspro.com).

This lets operators change their own passwords.

Choose the Select operators hyperlink to select the operators you want to force to change their passwords.

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

You would 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 don't 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.

This forces an entry at the Expiry period field, ensuring that operators change their passwords at prescribed intervals.

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 trying to bypass the system the server's operating system date is used when calculating the expiry period (i.e. 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.

Enter the number of days prior to the expiry of the current password that the operator must be warned that the password is going to expire.

The default warning period is 14 days.

The warning is only relevant in a SYSPRO login environment and does not apply to the e.net login process.

This lets you send auto-generated emails to the user and system administrator when a request to reset the password is received or when the password has been reset.

Select the Configure change email template hyperlink 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.

The supervisor password is only applicable when an operator password is defined. If the password against the operator is blank, then an Invalid operator password message is displayed.

This lets you configure the supervisor password.

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.

Enter the number of hours for which the temporary password is valid.

Select the Configure forgot password email template hyperlink 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 permitted.

The maximum number of login attempts is set in the Security pane of the Operator Maintenance program.

Select the Configure login exceeded email template hyperlink to use the Send Email program to edit the email template of the email that is sent to the administrator when the number of login attempts is exceeded.

This lets you define the rules governing the entry of new passwords.

Indicate the minimum number of characters for a password.

A minimum of 4 characters is recommended.

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

A combination of words and numbers in a password makes it more secure.

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 makes it more secure.

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

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

This lets you prevent operators from recycling their passwords. The system verifies any new password against an encrypted file of previously-used passwords.

If you enabled the Verify password against old passwords 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.

Select the Reset operator password history hyperlink to remove all records of password history generated for operators.