Jump to: navigation, search

skip-annex-validation

Section: system
Default Value: 0 (zero)
Valid Values: 0 (zero), 1, 16
Changes Take Effect: Immediately
Introduced: 8.5.101.21

Specifies if Configuration Server validates the Annex of an object, checking for an empty or duplicate object section. By default, Configuration Server performs a full validation and rejects modifications that can potentially affect data integrity or cannot be displayed properly by Genesys Administrator.

Valid values are:
0 (zero, the default)—Full validation is performed, and changes are rejected if an empty section and/or a duplicate section are found.
1—Partial validation is performed, and changes are rejected if a duplicate section is found.
16—Disables validation completely.

Warning: Set this option to 16 only when requested by Customer Care.

8.5.101.21

Configuration Server Release Notes



9.0
Configuration Server is part of 9.0 starting in 8.5.101.11.
Release Date Release Type Restrictions AIX Linux Solaris Windows
05/08/18 General X X X X

Helpful Links

Releases Info


Product Documentation

Management Framework

Genesys Products

List of Release Notes

What's New

This release contains the following new features or enhancements:

  • A new Configuration Server option, [system].skip-annex-validation, enables the server to skip all or some validation of changes in the Annex of a configuration object. If you are using Genesys Interaction Routing Designer (IRD) and you are unable to edit Business Process or other objects in IRD, you might need to set this new option to 1.

    skip-annex-validation
    Default Value: 0 (zero)
    Valid Values: 0 (zero), 1, 16
    Changes Take Effect: Immediately

    Specifies if Configuration Server validates the Annex of an object, checking for an empty or duplicate object section. By default, Configuration Server performs a full validation and rejects modifications that can potentially affect data integrity or cannot be displayed properly by Genesys Administrator.

    Valid values are:
    • 0 (zero, the default)—Full validation is performed, and changes are rejected if an empty section and/or a duplicate section are found.
    • 1—Partial validation is performed, and changes are rejected if a duplicate section is found.
    • 16—Disables validation completely.
      Warning
      Set this option to 16 only when requested by Customer Care.
  • The Framework Deployment Guide now includes separate lists of minimum database privileges for deploying and for accessing the Configuration Database and the Log Database.

Resolved Issues

This release contains the following resolved issues:


During upgrade, switchover between Configuration Servers 8.1.3 and 8.5.1 now occurs as expected when the Configuration Database contains a large amount of history records and the backup Configuration Server 8.5.1 loses and then restores its connection to the primary Configuration Server 8.1.3. Previously in this scenario, the switchover sometimes failed. (MFWK-19892)


Configuration Server can now be configured to skip a full validation of changes in the Annex of a configuration object, using the new option skip-annex-validation. (MFWK-19860)


When using LDAP external authentication, clients that cannot be authenticated now terminate with an error message if LDAP is not configured correctly. Previously in this scenario, the unauthenticated clients just stopped responding. (MFWK-19601)


When using LDAP external authentication, an External ID is not required for a Person object to bypass external authentication when enforced at the tenant level. Setting authentication type as internal in the Person object will authenticate the user internally. Previously, configuring External ID in this case caused LDAP to stop functioning. (MFWK-19343)


The Configuration Database multi-language initialization script can now be executed successfully on the MS SQL server with collation set to the following:

Latin1_General_100_CI_AS_KS_WS_SC

(MFWK-19331)


Configuration Server Proxy now reconnects to the master Configuration Server port that it was connected to before the connection was lost. Previously, when connected to a master server that has several listening ports, the proxy server was attempting to reconnect to any of those configured ports in a random order. (MFWK-17094)


Upgrade Notes

No special procedure is required to upgrade to release 8.5.101.21.

Supported Languages

See Release 8.5.x Translation Support.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on September 4, 2018, at 08:38.