Skip to content

Release Notes

4.1.0

New Features:

  • seal-dpf-accounting service has been added to write cluster compliant log files. By default, seal-dpf-process-manager is still writing the accounting.log. In cluster mode, you have to change this behavior by setting USE_ACCOUNTING_SERVICE to true. (DPF-1829)

  • The DPF command line client supports now the option --full for the dpf service stop command, which stops the full system including the infrastructure services. Without the --full option only the DPF services are stopped. (DPF-1918)

  • For container based installations, distroless images are available via Github. (DPF-1956)

  • Node.js has been updated to version 22.15.0 due to security reasons. (DPF-1958)

Bug-Fixes:

  • If a job was sent via REST interface, the name of the responsible user is shown in DPF Tracker. (DPF-1949)

  • The REST route /jobs/{jobID}/result allways returns the TargetDir and JobStatus parameters. (DPF-1990)

  • The workflow mapping of conversion jobs, as defined in main.customer.xml, has been fixed. (DPF-1991)

Known Issues:

  • The SOAP interface and thus SOAP Web Service, Mail Service and DPF SAP Retriever are not working with DPF 4.0.0. (DPF-1726)

  • DPF Gate ist not working with DPF 4.0.0. (DPF-1744)

  • As of DPF 4.0.0, DPF Batch Client does not support the option -f to provide a directory or multiple files with a job. (DPF-1768)

  • The environment key SEAL_CUSTOMDIR is not evaluated by the DPF. (DPF-1802)

  • If a sendback workflow is started by the DPF Batch Client via REST interface and the return files are to be placed in a subdirectory, the DPF Batch Client does not create this subdirectory. (DPF-1813)

  • The job type PDFLLSJob is currently not supported. (DPF-1853)

  • If a job was sent via REST interface, the name of the responsible user is not shown in DPF Tracker. This Bug is fixed with the DPF Tracker delivered in FM 2025 respective DPF 3.3.1. (DPF-1949)

  • For the DPF Batch Client to work with the -local parameter, the dpfclient.xml has to be changed. Refer to Installation and Configuration of DPF Batch Client. (DPF-1959)

4.0.0

New Features:

  • With DPF 4.0.0, the internal architecture of Digital Process Factory has been changed to a microservice architecture, thus making it clusterable and faster. For this, the installation of MongoDB, SEAL NATS and SEAL Logrotate are required prior to the installation of Digital Process Factory. The list of services contained in DPF is available in the reference section of this documentation.

  • When installed on the same server as PLOSSYS Output Engine, Digital Process Factory will use the same infrastructure.

  • DPF Tracker reads the job list and history from MongoDB. (DPF-1680, DPF-1681)

  • The sysinit script is used to transfer the old environment settings for the new microservice architecture to Consul, refer to Update for on-premise Windows or Update for on-premise Linux. (DPF-1683)

  • DPF CLI is the command line tool for administrating Digital Process Factory. It is used for managing the system configuration and the services. (DPF-1692)

  • The JobID of a job is unique for the whole cluster. It is built of date, time and a four-digit sequential number. (DPF-1707)

  • Digital Process Factory uses the new SEAL Systems product icon. (DPF-1711, DPF-1761)

  • For the communication between DPF Tracker and MongoDB, a REST API is used. You can find the API specification in the reference section of this documentation. (DPF-1728)

  • As of DPF 4.0.0, folder service is no longer supported. (DPF-1742)

  • DPF Tracker uses the management REST API to communicate with DPF. (DPF-1748)

  • jDPFClient and SOAP API are no longer supported as of DPF 4.0.0. (DPF-1753)

  • The new DPF bundle contains an install and a firewall script, refer to Installation for on-premise Windows and Installation for on-premise Linux. (DPF-1760)

  • When the LOG_LEVEL for dpf-process-manager service is set to info, the first line of job.log states if the new microservice environment was used for the job. (DPF-1762)

  • Parameter changes made by Modify working units are listed in the job history in MongoDB. (DPF-1788)

  • The following settings in the jobcleaner section of main(.customer).xml are obsolet: INSTANCES, KEEPUNTILFORGET, LOGLEVEL, LOGZISE, SLEEP_MILLI_SECONDS, VERSION. (DPF-1801)

  • For the deployment on Kubernetes clusters Helm charts are available. (DPF-1803)

  • A firewall script is available to open the necessary firewall ports. The list of ports used by Digital Process Factory is available in the reference section of this documentation. (DPF-1808)

  • Standard Prometheus metrics are available to analyze the general health of the DPF server. (DPF-1841)

  • For Linux on premise, the required Frozen Master Convert has to run under the service user seal. (DPF-1842)

  • Service log files are provided in machine-readable JSON format. Use Elastic Stack for a human-readable view. For how to install and configure Elastic Stack, refer to SEAL Elastic Stack documentation. (DPF-1877)

  • DPF Admin Client has been replaced by DPF CLI. It is used outside of the DPF environment in a PowerShell or command line. The old function names like dpfclearjobs are implemented as aliases for the new DPF CLI commands.

  • Node.js version 20.16.0 is used. (DPF-1885)

  • The is true operator returns true for all all numeric values not equal 0 and these case-insensitive strings: true, t, yes, y, ja, j, x. (DPF-1908)

Bug-Fixes:

  • The bug has been fixed, that prevented the creation of a result file when calling DPF Batch Client via REST route with the -result option. (DPF-1892)

Known Issues:

  • The SOAP interface and thus SOAP Web Service, Mail Service and DPF SAP Retriever are not working with DPF 4.0.0. (DPF-1726)

  • DPF Gate ist not working with DPF 4.0.0. (DPF-1744)

  • As of DPF 4.0.0, DPF Batch Client does not support the option -f to provide a directory or multiple files with a job. (DPF-1768)

  • If a sendback workflow is started by the DPF Batch Client via REST interface and the return files are to be placed in a subdirectory, the DPF Batch Client does not create this subdirectory. (DPF-1813)

  • The job type PDFLLSJob is currently not supported. (DPF-1853)

  • If a job was sent via REST interface, the name of the responsible user is not shown in DPF Tracker. This Bug is fixed with the DPF Tracker delivered in FM 2025 respective DPF 3.3.1.

  • For the DPF Batch Client to work with the -local parameter, the dpfclient.xml has to be changed. Refer to Installation and Configuration of DPF Batch Client. (DPF-1959)

3.3.0

New Features:

  • The DPF Java servlets and applications support Java 17. (DPF-1513)

  • The Online Documentation shows processes and working units located in SEAL_CUSTOMDIR. (DPF-1023)

  • The print-ipp working unit supports the parameters of PLOSSYS Output Engine for the output without interruption. (DPF-1857)

Bug-Fixes:

  • The print-ipp working unit evaluates job parameters for PLOSSYS Output Engine in the correct order. The parameter values from the set members have higher priority than the parameter values from the set, that means the default parameter values (top in DDD). (DPF-1858)

  • The bug with displaying the log file of a working unit has been fixed. (DPF-1668)

  • The bug that null directories were generated due to incorrect parameter evaluation in the REST working unit manager has been fixed. (DPF-1669)

  • Support packages (lifesaver) can be generated also for jobs whose subdirectories contain blanks or special characters. (DPF-1671)

  • When de- and encrypting the password of the LDAP search user, a key file can be used. (DPF-1780)

3.2.2

New Features:

  • DPF SAP Retriever supports connection via SAP gateways. (DPF-1642)

  • DPF SAP Retriever checks the status of each specific client connection. The status of the specific connection is displayed in the status output. (DPF-1647)

Bug-Fixes:

  • The result files are returned completely again. (DPF-1653)

  • The programs belonging to DPF contain a code signature again. (DPF-1657)

  • The evaluation of LOGLEVEL has been improved and this way a nullpointer exception is eliminated when generating a subjob. (DPF-1616)

  • When an error appears during logon (unknown user name, incorrect password, invalid certificate (SNC)), the client is terminated and this way the automatic re-connecting is interrupted to avoid that the SAP user account will be locked due to repeated failures. (DPF-1643)

  • The support form (aka lifesaver) supports the usage of curly brackets in directory names under Windows. (DPF-1661)

3.2.1

New Features:

  • During installation, directories are no longer created under %PLSROOT%/data, since the data directory can be specified arbitrarily in SEAL Setup. Scripts have to access the data directory via the %PLSDATA% environment variable instead of %PLSROOT%/data. (DPF-1618)

  • When collecting data belonging to a job already deleted, a warning will be output that the collected data only contains the log file and no job data. (DPF-1559)

Bug-Fixes:

  • The bug with the missing libDpfClient.dll for dpf-deploydpfclient has been fixed. (DPF-1610)

  • The REST Web Service, SOAP Web Service and DPF SAP Retriever Java clients set the DPFTRACKER_URL_JOB parameter analog to DPF Batch Client (dpfclient). (DPF-1621)

  • The bug with the encoding of collected files has been fixed. (DPF-1600)

  • In case of a license error, the ERR_REASON DPF parameter will be set. This way, also a helpful error message is displayed in SAP. (DPF-1310)

  • JobDir is generated using the correct filesystem separators in order to avoid errors when using it in environment variables. (DPF-1628)

  • The umlauts in the log messages are displayed correctly. (DPF-1644)

  • The REST WU only reads values from the {{ restwu }} element in the configuration. {{ workingunit }} is no longer evaluated. (DPF-1641)

  • Due to security reasons, the Apache Commons libraries have been updated. (DPF-1614)

  • When starting DPF SAP Retriever, the connection of the RFC servers are checked before processing working packages to avoid errors during checkout. (DPF-1646)

  • The license is checked in subprocesses as well. (DPF-1624)

  • The bug when expanding variables has been fixed. (DPF-1630)

3.2.0

New Features:

  • In the DPF4Convert panel of SEAL Operator, the conversion results are displayed. (DPF-1539)

  • If the connection to the DPF REST WU server is established for a second time, for example, when restarting the client after loosing the connection, the running jobs of the correspondent client are reset and can be processed again. This avoids jobs in the Processing status when the connection to the client is lost. (DPF-1597)

Bug-Fixes:

  • XMLChecker checks if the files contain a byte order mark (BOM) and outputs an error message otherwise. (DPF-1592)

  • The "HTTP Status 500 - Internal Server Error" bug in the JavaWU has been fixed. (DPF-1611)

  • After a crash, DPF Gate will be restarted. (DPF-1601)

  • The navigation to the log file for DPF REST WU nodes in the process graph in DPF Tracker works again. (DPF-1598)

  • The bug with checking the license has been fixed. (DPF-1603)

  • The bug with jumping to the log file from the process graph in DPF Tracker has been fixed. (DPF-1599)

3.1.1

New Features:

  • The output of the REST interface has been optimized: The job ID is output as provided by the REST interface. For each started job, a start message is output. Due to the REST ID is not helpful when searching in DPF Tracker, the DPF Tracker URL is output additionally. After the job is finished, no further messages are output. (DPF-1581)

  • dpfimportjobs also supports customer-specific directories. (DPF-1535)

  • The RFC call for checking out working packages has been changed. The previous call has been marked as obsolete. (DPF-1554)

  • The switch command has been replaced due to this is no longer supported by Perl as of version 5.8. (DPF-1552)

  • Due to security reasons, the log4j library has been updated to version 2.17. (DPF-1543, DPF-1544, DPF-1546, DPF-1547, DPF-1548)

  • DPF SAP Retriever can establish SNC connections to the SAP system. (DPF-1551)

  • The DPF processes support process configurations in the customer-specific directory %SEAL_CUSTOMDIR%/server/dpf/templates. (DPF-1560)

  • The license check uses the standard status values for a consistent display in System Status. (DPF-1557)

Bug-Fixes:

  • The bug with the DPF Retriever reply to CE-F when using Java 11 has been fixed. (DPF-1583)

  • The bugs in passing parameters to DPF REST Service and storing the result files in case of a remote call have been fixed. (DPF-1550)

  • The error messages when replying from DPF Batch Client via HTTPS been improved. (DPF-1582)

  • The misleading warning with local access has been removed. (DPF-1524)

  • The bug with releasing a file after accessing it has been fixed. (DPF-1477)

  • The handling of special characters in XML files has been corrected. (DPF-1553)

  • The DPF SAP Retriever status display in Conversion Control Center (CCC) is also updated when no jobs are being processed. (DPF-1540)

  • The crash (internal server error) when calling the lifesaver action for the first time has been fixed. (DPF-1528)

  • The check of the access permissions for the lifesaver in DPF Tracker has been corrected. Additional security functions have been implemented. (DPF-1495)

  • The sorting in the online documentation has been corrected. (DPF-991)

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 to INFO. (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)

3.1.1.

New Features:

  • DPF SAP Retriever provides process templates that work without parameters. (DPF-1472)

Bug-Fixes:

  • The bug that no jobs were processed via the REST WU has been fixed. (DPF-1476)

  • When using dpfclient via REST, the result files are stored in the correct directory. (DPF-1474)

  • The usage of dpfclient has been fixed. (DPF-1480)

  • The Destination and ProgId parameters for the RFC destination are set correctly. (DPF-1478)

  • If an error occurs between generating the job and starting it, for example, during the download, the job will now be canceled and ERR_REASON will be set. (DPF-1482)

3.0.0

New Features:

  • The DPF programs are available for 64 bit Linux distributions. (DPF-1435)

  • DPF 1.x licenses are no longer supported. (DPF-1432)

  • DPF URL Callback supports Java 11. (DPF-1444)

  • DPF RestWU Manager supports Java 11. (DPF-1458)

  • The definitions of the database tables have been revised so that they are compatible to PostgreSQL 12. (DPF-1438)

  • DPF Batch Client can connect to DPF via the REST Web service. Using this, no ports have to be opened for the database accesses and Frans and file larger than 2 GB can be transferred. The transfer protocol is specified with the -protocol command line parameter. (DPF-1384)

Bug-Fixes:

  • DPF SAP Retriever can connect to multiple SAP systems correctly. (DPF-1468)

  • DPF URL Callback starts correctly on Linux. (DPF-1422)

  • The bug with activating the licenses after uploading via SEALCC has been fixed. (DPF-1453)

  • The evaluation of the maximum allowed size of the log file has been corrected. If the maximum (20 MB) is exceeded, a warning is output to the log file. With -1, the size restriction is deactivated. (DPF-1431)

  • Unless the log level has been configured, INFO is used by default. (DPF-1220)

  • The check of the user name ORIGUSERNAME is case-sensitive. (DPF-1119)

  • The process steps in the log window have been linked to the process graph so that the correct location of the graph is reached from the log. (DPF-1042)

2.4.0

New Features:

  • For connecting a DPF system to the Conversion Control Center (CCC), the new component DPF SAP Retriever is available. (DPF-1407)

  • Jasper reports in the customer-specific directory, %SEAL_CUSTOMDIR%/server/dpf are taken into account when compiling. (DPF-1094)

  • For dpfclearjobs, the option -job <job> is available for deleting a job with all sub jobs. With <job>, the job ID or the job directory can be specified. Unless the job is finished, a warning will be output which can be suppressed by specifying -F. Via the option -status ERROR|SENDING, all finished jobs in an error status or in the sendback status are deleted. (DPF-988)

  • When packing the job for the support (lifesaver icon), JSON files containing the system versions and the installed-packages.txt file will be included additionally. (DPF-1410)

  • DPF URL Callback appends its messages to the job log file. (DPF-1380)

  • When using the remote working unit, the SEAL_CUSTOMDIR path is adjusted to the remote system. (DPF-1397)

  • Due to the Java working unit checks via DB call if an update is required, the script server/dpf/startstop/177.update-java-wu.start has been removed. (DPF-1389)

  • Apache Tomcat has been added to the standard dependencies of DPF due to it is required by the REST service which is an inherent part of DPF. When starting the DPF system, Apache Tomcat is started, too. (DPF-1383)

  • When packing the job the support via lifesaver icon, JSON files containing the system versions and the installed-packages.txt file will be included additionally. (DPF-1410)

Bug-Fixes:

  • DPF SAP Retriever can now be found easier in the task list. (DPF-1417)

  • The wait working unit terminates the wait process if the correspondent module returns an error. (DPF-1405)

  • To avoid collisions when loading classes, the jar files and the other classes are stored for each working unit separately. (DPF-1189)

  • The bug when deleting the current job has been fixed. (DPF-1391)

  • The bug with starting kNet when using the remote working unit has been fixed. (DPF-1403)

2.4.0.1

New Features:

  • Perl 5.30 is supported. (DPF-1424)

Bug-Fixes:

  • The behavior of DPF SAP Retriever if the configuration is missing or incomplete has been improved. (DPF-1441)

  • The starting order when using the Java WU has been corrected. (DPF-1440)

2.3.0

New Features:

  • The DPF Web services support Basic Auth for authentication. This can be configured via sysinit. (DPF-1245)

  • The display of the valid licenses has been improved. (DPF-1362)

  • The maximum length of passwords has been increased to 256 bytes. (DPF-1377)

  • Undefined variables are deleted in account.log. This enables, for example, using the %PARENTJOBID% parameter in a senseful way in order to distinguish between main and subjobs with the evaluation. (DPF-1365)

  • The usability with the license upload has been improved. (DPF-1363)

  • The delivery of DPF Folder Service has been enhanced so that the MS SQL JDBC drivers are provided for being executed with JRE Version 8 and with versions as of 11. (DPF-1357)

  • The DPFUseInteractiveDesktop environment variable for displaying applications on the interactive desktop is no longer supported. Instead of that, the output redirection via SEALService is recommended. (DPF-1372)

  • For the main processes, an index is provided in the Online Documentation. (DPF-926)

Bug-Fixes:

  • The values for EXITSTATUS, WFNAME, WFPOSITION, WFPATH and WUNAME in account.log have been corrected. They are no longer read from the parameters list but (analog to the behavior in DPF Tracker) from the activity. (DPF-1366)

  • The bug with the high processor load without jobs has been fixed. (DPF-1376)

  • The performance with pdfupdate has been improved. (DPF-1154)

  • The existence of a remote DPF system no longer affects the start and stop behavior of DPF URL Callback. (DPF-1378)

  • With sysinit, it is checked if the DPF Tracker base URL has been written to the database correctly. (DPF-1379)

  • Displaying the 0 value with IF-THEN_ELSE blocks in DPF Tracker and DPF Director has been fixed. (DPF-943)

  • A bug when exporting subjobs via the lifesaver icon has been fixed. (DPF-1370)

  • The internal system error when displaying the job log has been fixed. (DPF-1345)

2.3.0.1

New Features:

  • The access to the DPF Web services and the Web applications can be restricted via LDAP. For this, the LDAPS protocol and the correspondent port is default. (DPF-1390)

  • Linux is supported. (DPF-1381)

  • The Java working unit is supported on Linux. (DPF-1374)

  • The wait working unit pauses the process for a while if the processing working unit returns not yet finished. (DPF-1275)

Bug-Fixes:

  • The bug when importing the license on Linux has been fixed. (DPF-1388)

  • The variable names are expanded correctly for the files to be sent. (DPF-1341)

  • The bug with searching and replacing file links has been fixed. (DPF-1333)

  • The link in the header, Job status - <jobid>, refers to the correspondent job and no longer to the main page of DPF Tracker. (DPF-1334)

  • The mapping parameters had been written to the database as permanent parameters. The bug has been fixed. (DPF-1237)

Back to top