Skip to content

SEAL Operator 1.1.0


New Features

  • For the PLOSSYS 4 panel, the schema has been expanded (flagpage, stamps, PLS_FOLD, PLS_FOLD_TYPE, PLS_PUNCH_TYPE, PLS_SORT_TYPE, PLS_STAPLE_TYPE, PLS_SCALE_TYPE)

  • Stamps can be disabled for the additional sheets of PLOSSYS 4 jobs.

  • With the USER_NAME_KEY key, a repro list field can be specified for passing the name of the logged-in user to the repro list.

  • With the RLI_JOBNAME_KEY key, a key in repro list files can be specified whose value is used as job name in SEAL Operator. Default is name. If the specified key is not contained in the repro list file, PLS_PLOTID, PLS_ORIG_NAME and a self generated UUID are used in this order.

  • The connectors can provide plug-ins to SEAL Operator within their metadata. These plug-ins are used to identify the responsible repository interface for downloading the document content. (SOP-89)

  • When printing to PLOSSYS 5, a notification is received after the job has been completed.

  • The printers of a PLOSSYS 5 system are fetched via IPP.

  • Jobs are sent to PLOSSYS 5 via IPP.

  • Some non-IPP attributes are set as seal-attributes in the IPP request.

  • With a cloud installation, the configuration of the connectors is read from a file instead from Consul. The path and name of the file is specified in the CONNECTOR_FILE_NAME environment variable. The default of CONNECTOR_FILE_NAME is /config/connector.yml.

  • Tasks can be created for CSV and RLI files.

  • RLI jobs can be created for PLOSSYS 4.

  • After receiving a SIGINT or SIGTERM signal, the services try a graceful shutdown by closing the HTTP server for incoming connections and waiting until all currently open connections are closed.

  • The items in the task list are updated after a thumbnail has been generated.

  • The documents in repro lists can refer to any repository and not only to My Documents. The documents are accessed not before the connector's request and are not temporarily saved on the SEAL Operator server.


Bug-Fixes

  • The seal-operator-server service is started independently of an already running identity provider.

  • The bug with caching the panel data has been fixed.

  • The bug with HTTP status codes has been fixed.

  • The Format parameter is always visible in the PLOSSYS 4 panel.

  • If an error occurs when copying the document content, a PLOSSYS 4 job is created with header, ready and log files which than can be processed by the PLOSSYS 4 gate. So far, an error message had been output and files such as header files were left over in the gate directory. (SOP-99)

  • The bug with reading the IDP certificate using the seal-json-web-token module has been fixed.

  • An error is output if a subcommand is unknown to SEAL Operator CLI.

  • The housekeeping do no longer sweep directories.


Back to top