Platform

Callout extension scripts

The custom scripting framework has been updated to support callouts. Callouts provide an interface that customers can use to make modifications to core functionality in Workforce Management. For example, a callout may provide a mechanism to add custom validations when users perform specific transactions.

Customers can implement callouts by developing callout extension scripts. Code templates are provided for each supported callout as a starting point for script development.

These callouts are now supported using the custom scripting framework:

  • Book-off Code Validation
  • Shift Edit Validation
  • Shift Summary UDF and Flag Mapper

For customers with existing implementations of the supported callouts, the class name or bean name is migrated from the registry parameter to the Extension Script Callout maintenance form during upgrades. These related registry parameters have been deprecated and removed from the system:

  • BOOK_OFF_CODE_VALIDATOR_SVC
  • SHIFT_VALIDATION_SVC
  • SUMMARY_TO_DETAIL_UDF_FLG_MAPPER_SVC

See these topics in the documentation:

  • “Extension script callouts” in the Infor Workforce Management Custom Scripting Developer Guide
  • “Callouts” in the Infor Workforce Management MVS Implementation and Administration Guide

SLF4J using logback support for the WFM application

Log4j has been removed as the default logging configuration for the WFM application. SFLF4J using Logback is now the default configuration for logging and default logback.xml files have been provided in the product. However, custom logging configurations must be assessed.

Existing log4j.properties files can also be converted using an online translation tool from the Logback project: https://logback.qos.ch/translator/

Any code that calls Log4j must be removed from extension scripts. At this time, extension scripts do not support logging.

Custom code, including callout implementations, that references the org.apache.log4j.Logger class must be updated to use the new com.workbrain.util.logging.Logger class. This class acts as a wrapper to translate Log4j APIs to SLF4J APIs. Customers can work with Infor Support to identify affected extension scripts and custom code.

These registry parameters related to log4j have been deprecated and removed from the system:

  • LOG4J.APPENDER.R
  • LOG4J.APPENDER.R.FILE
  • LOG4J.APPENDER.R.LAYOUT
  • LOG4J.APPENDER.R.LAYOUT.CONVERSIONPATTERN
  • LOG4J.APPENDER.R.MAXFILESIZE
  • LOG4J.APPENDER.STDOUT
  • LOG4J.APPENDER.STDOUT.LAYOUT
  • LOG4J.APPENDER.STDOUT.LAYOUT.CONVERSIONPATTERN
  • LOG4J.ROOTLOGGER
See these documentation topics for more information:
  • Infor Workforce Management Installation and Configuration Guide
  • "Logging in custom scripts" in the Infor Workforce Management Custom Scripting Developer Guide.
  • "SLF4J replacement for Log4j logging" in the Infor Workforce Management Upgrade Guide.

Cognos Analytics 11.2.2

Cognos Analytics 11.2.2 has been certified and tested for use with the WFM application.

For more information on deploying Workforce Management with Cognos Analytics 11.2.2, see this documentation:

  • Infor Workforce Management Installation and Configuration Guide.
  • Infor Workforce Management Upgrade Guide.

FICO Xpress 8.12.3

FICO Xpress 8.12.3 (also known as Dash server) has been certified and tested for use with the WFM application. It is now the required software version for the FICO Xpress server, and the required license version is 8.14.

For cloud customers, this platform upgrade is performed by Infor Cloud Operations. On-premise customers using LFSO or Auto Assignment must upgrade their FICO Xpress server to 8.12.3.

For installation steps, see the Infor Workforce Management Installation and Configuration Guide.

Red Hat Enterprise Linux (RHEL) 8.6

RHEL 8.6 has been certified and tested for use with the WFM application.

For more information, see Infor Workforce Management Hardware and Software Requirements Guide.

Thread setting for the Start of Day task

The /ruleEngine/createDefaultRecords/SLAVE_THREAD_COUNT registry parameter has been removed from the application and moved to the Start of Day task parameter page. The default setting for the new Number of Threads field in the Job Scheduler task is 8 for new and upgrading customers. The range for this field is between 4 and 32. If you specify a number that is not between these values, then the minimum or maximum value is applied.

If you are migrating to the latest version, then you must review the value before running the task to determine if it is appropriate for your particular environment.

For more information on the Start of Day task, see Infor Workforce Management Time and Attendance Implementation and Administration Guide.

Process Clocks task registry parameters moved to Job Scheduler task parameter page

Settings for the Process Clocks task have been removed from registry parameters and placed in the task parameter page.

These registry parameters have been deprecated:

  • /system/WORKBRAIN_PARAMETERS/numClocksToProcessBeforeCalc
  • /system/clockprocessing/maxClocksToProcessPerInvocation
  • /system/clockprocessing/SLAVE_THREAD_COUNT

It is advisable for users to set the value in the task parameters according to their hardware specs after upgrade. After upgrade, the default value is specified in the task parameter page for the Clock Processing task.

The old values that were configured in the deprecated registry parameters have not been retained after upgrade and may not work optimally with the refactored multi-threading code. The default value is likely sufficient for most customers equipped with a medium sized server. However, if you have a small server or an extremely large server, you must adjust the settings accordingly.

Here are some examples of server size:

  • Medium server is 8 - 16 cores CPU.
  • Small server: 2 - 4 cores CPU.
  • Large server: 32 - 64 cores CPU.

For more information on the Process Clocks task, see Infor Workforce Management Time and Attendance Implementation and Administration Guide.

Extension script support for Schedule Compliance

A DBLookup field has been added to custom rules and custom filters that permits you to specify a script for scriptable extensions.

For more information on scriptable extensions, see Infor Workforce Management Custom Scripting Developer Guide.

Deprecation of automated installers for WFM installation

The automated installers for WFM have been deprecated as of this release. The script method is now the only supported method for installing and configuring WFM in an on-premises environment.

Clock installers continue to be maintained as of this release.

For more information, see Infor Workforce Management Installation and Configuration Guide.

Deprecation of Form Builder and Workflow Editor tools in WFM

The Form Builder and Workflow Editor applet-based tools have been removed from WFM for new installations of on-premises and single-tenant deployments. Existing forms and workflows continue to work as before.