Job Execute and Store Reports

Purpose

The job calls a Webdesk report action in the context of each selected person and stores the results as PDF, print HTML or XLS. The target can be configured as repository, meta structure or SFTP. The job does not send any e-mails.

Person selection

Persons from person, group and client restrictions are processed; the client assigned to the job acts as an additional hard restriction. With Active persons only, inactive users can be excluded.

Loop types

  • Without a loop type or once: exactly one report per person.
  • months: one report object per relevant calendar month.
  • processInstances: one report object per matching workflow process instance, if active.
  • ta_bookingMonths: one report object per booking month of the TA person.
  • ta_employments: one report object per currently considered, mapped and non-planned TA employment; the technical identifier is found under object.taID.
  • ta_employmentCalendarMonths: one delimited report object per TA employment and calendar month, at most up to the previous day and taking the employment and reporting limits into account; additionally object.from and object.to are available.

Important configuration

  • Webdesk URL, Action, Format and optionally Orientation.
  • Target: repository, meta structure or SFTP.
  • File name/path as Velocity expression: The context contains person, object, action and simpleDateFormat. For employment or month loops, employment and date components must be included in the file name so that files are not overwritten.
  • Overwrite existing files, Export attachments, Validate PDF, Preview and Number of threads.
  • Reporting period: From/To dates can be determined as a TA date or JavaScript expression.
  • Filter and optional JavaScript filter: The filter runs per loop object; if no Boolean is returned, the object is processed.
  • Additional action parameters: Values can be calculated from the current JavaScript context.

Multiple TA employments

ta_employments and ta_employmentCalendarMonths process employments separately, resulting in several files per person. Use at least $object.taID, and for monthly intervals additionally $object.from and/or $object.to. Check whether the report action expects the parameters uid, taId, from and to.

Errors and interruption

Errors for one person are logged and the next person is processed. An interruption stops further processing.

Kommentare (0)