Default Value: wfm
Valid Values: " ", wfm
Changes Take Effect: After restart
Dependencies: See Important note in this option
Specifies the provider that performs WFM user authentication.
If this option value is set to:
- " " (empty string)—WFM Server SOAP API authenticates WFM users.
- wfm—WFM Server REST API (on-premises) authenticates WFM users.
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately
Specifies whether or not WFM Builder writes scheduling data, output data, and messages to the Schedule log file.
When this option is enabled (value is set to true), you must specify a Schedule log path. One log file is created for every schedule build.
Used for Schedule debugging only.
Workforce Management Builder Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release includes only resolved issues.
This release contains the following resolved issues:
WFM Builder now builds schedules successfully, displaying no error messages. Previously, WFM Builder sometimes displayed internal errors  or File not opened after building approximately 500 schedules when the [Log] x-ScheduleBuilderTrace configuration option was enabled. (WFM-33132)
WFM Builder now builds schedules successfully if Contracts contain monthly hours, scheduling period work hours, and shifts all with the same paid duration. Previously in this scenario, Builder sometimes got stuck (showed some progress percentage but no actual progress) while building schedules, causing it to loop endlessly, as the longest shifts prevented some shift durations from being scheduled on the subsequent day. (WFM-33121)
WFM Builder now successfully connects to WFM Server over secure SSL/TLS connections. Previously, WFM Builder failed to connect when the [auth] provider configuration option was configured and a self-signed certificate was used for WFM Server. (WFM-33098)
WFM Builder now builds schedules without displaying TVector errors. Previously, WFM Builder intermittently failed to build schedules with error TVector<> index out of range when two or more task sequences assigned to the shift were configured identically. (WFM-33063)
No special procedure is required to upgrade to release 220.127.116.11.