Other Algorithms

CreateDueTasks

Processes all contracts that are still valid but have no task defined for the specific time frame.

PurgeHistory

Purge obsolete data.

PurgeStructure

Purge or update entity objects from the domain model, following a hierarchy from a server-side provided structure-file.

The structure defines a hierarchy of domain entities to traverse, while purging or updating data. The ID of every object is provided during data retrieval operations as :parentId parameter, while iterating it's children. The root element is expected to be of the type omd.domain.Configuration.

Supported attributes for elements in the structure:

• purge sets the type of purge:
  • YES (equals DELETE, which is the default) delete all matching objects
  • NO don't delete or update, just use matching objects for navigation to other children.
  • UPDATE update attributes of matching objects, as defined in assign, attributes, attribute and value.
• namedQuery | nativeQuery | jpqlQuery defines a query for selection of object IDs from the entity.
  • Use the :parentId bind parameter to select related children in a named or JPQL query, or define a diverging parameter name in the attribute bind. A native query is expected to provide one bind parameter ? to receive the parentId.
  • If this attribute is omitted, then the entity is expected to provide a named query, by the name of selectIdFlat.
• bind sets an alternative name for a parentId parameter in a named or JPQL query.
• assign contains the set-clause expression(s), in case of purge="UPDATE". Multiple assignments must be separated by a comma.
• attributes defines a comma-separated list of entity attributes to update, in case of purge="UPDATE".
• attribute defines one single entity attribute to update, in case of purge="UPDATE".
• values defines a value to set all entity attributes, or the single entity attribute to, in case of purge="UPDATE". If omitted, then the specified attributes are set to null.

If assign is defined, then attributes, attribute and value are ignored. All information in these attributes must comply to the JPQL spec, i.e. valid names of entity attributes must be used (not DB columns), and only valid JPQL assignments are allowed.

For good performance, usage of native queries and inner joins might be worth to consider, to ensure a predictable execution plan and to keep the traversed structure flat. Otherwise, discrete traversal is performed on every single matched ID.

Report

Run Jasper Report to generate a report within a job. The report will be attached to an email.

Cheapest Insert

CheapestInsert is a planning algorithm on basis of a set of tasks. It determines the best option for every task and inserts the task accordingly. The tasks can be compiled by a task selector (e.g. the SLASelector). The best options can be limited by optional Date- and ResourceSelectors, and further constraints can be set by the following properties: