Job Process System Notifications

Purpose

The job processes defined IF6020 events and creates workflow processes from them as system notifications for affected persons.

Prerequisites

  • The TA/IF6020 and Workflow modules must be available.
  • The process definition used must support the expected variables. If no valid process definition is configured, the job uses the default definition WebdeskDefaultProcessDefinitions$SystemNotificationWithRedirect.

Job configuration

  • Months in the past and Months in the future: The period in which IF6020 events are searched for.
  • Client: The job processes persons of the selected client, provided no groups are selected.
  • Groups: Alternatively, the union of the currently valid persons of the selected groups is processed. The TA ID is used for the event search.
  • Notification rows: Each row describes an event and the workflow task to be created from it.
  • IF6020 system event: The event whose open records are processed.
  • Action: Optional Webdesk action linked to from the system notification.
  • URL suffix: Optional Velocity expression for query parameters of the action.
  • List Detail: Velocity/HTML template for the detail column of the workflow task. Line breaks are carried over as <br/>, and the result is sanitized before being inserted into the workflow.
  • Process definition to use: Optional process definition in the format packageName$processDefinitionName.
  • Start workflow process with affected person as author: If enabled, the affected person is used as the process author; otherwise the system administrator.

Velocity context

In List Detail and URL suffix, among others, ta_id, fromdate, from_date, fromDate, year, month, day, person and eventDate are available. Example: $person.getFullName().

Process

  1. The job determines the TA IDs of the configured persons.
  2. For each notification row, events are searched for within the configured period.
  3. For each matching event, a workflow process is created with listDetail and the affected person as recipient. Optionally, redirectToUrl and from_date are set as process variables if the process definition contains these variables.
  4. After successful process creation, the event is marked as processed.

The choice of event, process definition, action and Velocity expressions must be consistent with each other. Check the generated process definition and the variable names in a test environment.

Kommentare (0)