BPM (Conf)


../../../../_images/bpm.png

Base

  • Instances monitoring: if checked, it enables the monitoring of BPM instances.

  • Instances monitor execution: how often the monitoring of the BPM instances is executed, for further details, refer to the Cron Trigger Tutorial (Quartz Cron) section.

  • Purge instances: if checked, it enables the deletion of BPM instances.

  • Purge instances execution cron: how often the service for deleting the BPM instances is started, for further details, refer to the Cron Trigger Tutorial (Quartz Cron) section.

Variables

  • Show instance variables: if checked, BPM instances variables are shown.

[Advanced] Process Data Warehouse

Collects data on BPM processes and generates reports that can be downloaded alongside the other report.

  • Process data warehouse enabled: if checked, the feature is enabled. Per default this is set to false.

  • Process data warehouse retention period: Number of days the data warehouse records are retained, before deletion.

  • Process data warehouse cleanup cron: the cron expression for the cleanup of old data. For further details, refer to the Cron Trigger Tutorial (Quartz Cron) section.

[Advanced] Binary Data Warehouse

  • Binary data execution ETL enabled: if checked, additional data from BPM instances are made available in the database. These data can be used by reports or widgets afterwards.

  • Binary data execution ETL execution cron: the interval in which the Genius Server checks for ETL data.

  • ETL execution query page size: the size of the query page.

  • ETL target instance: the target instance for ETL which can be: instances started from the MFP or instances started from web.

  • ETL target binary datas: the target binary data for ETL - either all binary data are collected or only those entered by users.

  • Binary data ETL aggregation cron: the interval in which ETL data get aggregated.

Task Node

  • Mail to identity: if checked, an email gets sent to the user who got a task assigned.

  • Join task timeout: the join task timeout in miliseconds.

  • Notification subject: the template used for the email subject sent to the assigned user.

  • Notification body: the templaed used for the email body sent to the assigned user.

  • Task lock confirmation message [Advanced]: if enabled, a confirmations message appears, when a task gets locked.

Starter

  • BPM starter: if checked, it enables BPM definition starter features which are managed in the Genius Server admin web console.

Note

If enabled, instances are started as soon as an event occurs (e.g., a print job on printing queue, a low level of ink, a file added on folder managed by DMS, etc.).

  • Purge enabled: if checked, it enables the purge function for BPM that might be stuck or in a loop.

  • Purge execution cron: the cron expression for the purge event. By default the purge job occurs every 20 minutes.

  • Maximum age: it defines the maximum age of a BPM. Every BPM, which runs more than this period of time (by default, it is 180 minutes), are affected by a purge.

[Advanced] Binary

  • Maximum age binary data: the maximum age of orphan binary data (files not associated to Bpm instances).

  • Orphan binary data check enabled: if checked, the orphan binary data checked is enabled.

  • Delete automatically orphan files found: if checked, found orphaned files are automatically deleted.

  • Orphan binary data check execution: a scheduling time expression to check for orphaned files. To modify its cron expression, press the Edit button, enter the expression and then press Save.

  • Binary data cleanup enabled: if checked, it enables the binary data deletion.

  • Binary data cleanup execution cron: a scheduling time expression of the binary data deletion. To modify its cron expression, press the Edit button, enter the expression and then press Save.

Security

  • File encryption enabled: if checked, it enables the encoding of binary data, which come from BPM processes, before you store them on File System. The encryption is performed by AES 256 bit algorithm.

  • Execute script in secure mode [Advanced]: this mode disables the possibility of the script node to execute potentially dangerous operations (like execute remote command and access system resources).

[Advanced] Layout

  • File inline size: Size of the file showed inline in BPM forms, they can be small or large.

To save, press the Save button and then Back.