Platform 7.1.0.1 resolved issues
Total: 11 issues
----------------
PLAT-9394
PGP Encryption for Export Files
WFM provides the ability to encrypt the files exported from WFM using a PGP public key that you provide. The PGP public key is stored in the Sensitive Data Configuration form with a configuration type of PGPEXPORTPUBLICKEY.
To encrypt an export file, you must select the PGP Encrypt File check box, which is included as part of all Export Tasks. By default, the check box is hidden and must be enabled in config mode. When the Export Task runs with the PGP Encrypt File option selected, the exported file is encrypted using the stored PGP public key. A third-party encryption tool is required to decrypt the file.
See "File Encryption Using the PGP Library" in the Infor Workforce Management: Installation and Configuration Guide.
----------------
PLAT-9467
Add data replication support for tables RTSS_PROCESS and RTSS_RULE_ERR_LOG
The schema was updated for the WFM_RtssProcess and WFM_RtssRuleErrLog documents to support archiving past RTSS processes.
The changes to these document schemas are backward compatible with any document objects that are already in Data Lake.
See "Infor Data Lake integration" in the Infor Workforce Management Release Notes.
----------------
PLAT-9470
Data Lake configuration for WGB Infor Role column
The schema was updated for the WFM_WorkbrainGroup document to support the WGB Infor Role column.
The changes to the document schema are backward compatible with any document objects that are already in Data Lake.
See "Infor Data Lake integration" in the Infor Workforce Management Release Notes.
----------------
PLAT-9534
An uncaught error is seen when submitting the interaction in desktop application
Uncaught error when submitting a new availability pattern.
Outcome
Fixed.
----------------
PLAT-9553
Fix broken SQL statement in flyway migration
Japanese localization contains a broken SQL statement.
Outcome
Fixed.
----------------
PLAT-9563
7.1 language import
Imported the language packs for release 7.1.0.
----------------
PLAT-9581
IMS User BOD - Option to update WBU_IDENTITY2 value only
The IMS_USER_BOD_RESTRICTED_MODE_ENABLED registry parameter has been added to provide a simplified way to update the WBU_IDENTITY2 field in Workforce Management using the Sync.SecurityUserMaster BOD.
If this registry parameter is set to true, when WFM processes the Sync.SecurityUserMaster BOD for an existing user with an empty WBU_IDENTITY2 field, the WBU_IDENTITY2 field is updated to the IFS GUID. No other fields are updated.
If this registry parameter is set to false, WFM processes the Sync.SecurityUserMaster BOD as documented in the Infor Workforce Management Configuration Guide for Infor Operating Service – Cloud Edition.
Regardless of the value of this registry parameter, to subscribe to the Sync.SecurityUserMaster BOD, WFM must be configured to process BODs as described in the guide.
----------------
PLAT-9585
Provide extension point for IDP initiated SSO
You can now configure an extension point for validating and parsing the SAML token in Mobility, WFM and ETM for IdP initiated SSO. This allows you to unify how the SAML response is handled by Mobility, WFM and ETM. The parser is specified in the /system/security/SAML/TOKEN_PARSER registry parameter.
For more information, see the Infor Workforce Management Registry Parameter Reference Guide.
----------------
PLAT-9592
For Postgres, delete trigger for audit log table in the archive schema is not working
When trying to delete a record from the archive audit log table, the query fails. The query tries to insert the deleted data in the WB_DELETE_HISTORY table instead of the WBARCH_DELETE_HISTORY table.
Outcome
Fixed by correcting table, column, and sequence names and adding missing data.
----------------
PLAT-9599
For Postgres, unable to delete the record from archive.CLOCK_TRAN_PROCESSED
When trying to delete a record from the archive.CLOCK_TRAN_PROCESSED table, the query fails.
Outcome
Fixed by correcting sequence names.
----------------
PLAT-9661
Move Japanese BO and Workflow migrations to core folder
The Japanese Business Object and Workflow migrations have been moved from the Japanese translations folder to the core platform folder. In addition, correction migrations triggered by issues in the above migrations have been removed.
----------------