Digital Process Factory 3.1.0¶
New Features¶
-
The default of the
DELETEJOB
parameter has been changed to one hour (1h). (DPF-1523) -
OIDC identity providers such as Google, Azure AD and Keycloak can be configured for DPF Tracker. (DPF-1399)
-
DPF SAP Retriever supports connections to former systems. Only the parameters and tables available in SAP are read and written. (DPF-1488)
-
DPF SAP Retriever supports multiple connections. (DPF-1506)
-
The contents of properties containing "TOKEN" in their names are displayed with asterisks. (DPF-1430)
Bug-Fixes¶
-
When stopping the JavaWU, only the jdbc drivers belonging to it are deregistered. (DPF-1493)
-
If problems occur during the checkout of files from CCC, the correspondent DPF job is terminated correctly. (DPF-1504)
-
DPF SAP Retriever starts even if the configured connections fail, for example, if the server cannot be reached or if connection parameters are incorrect. (DPF-1490)
-
The default of the log level has been changed from
DEBUG
toINFO
. (DPF-1512) -
The sapftp and saphttp RFC servers are (re-)started much earlier in order to avoid checkout errors. (DPF-1505)
-
The bug with displaying the status of DPF SAP Retriever in Conversion Control Center (CCC) has been fixed. (DPF-1531)
-
When checking client names, the name of the SAP system is taken into account in order to avoid duplicates. Misconfigurations are detected and output as warning. (DPF-1522)
-
After a disconnection from the SAP system, DPF SAP Retriever correctly reestablishes the connections. (DPF-1489)
-
Jobs with erroneously configured parameters no longer get hung in the sendback working unit. (DPF-1293)