Generate objects

The generator creates an empty transactional object for each OVID of a recurring object that the generator receives by performing the object search. Whether this object can be filled and saved correctly is determined by the workflow configuration of the transactional object.

Each transactional object type in the workflow has a connection in <state.initial> for which only the generator server tasks are authorized (permission). When the object is created, the generator follows this workflow connection.

Example for the TESTCASE object type

Command chain prepareJob in the testcase catalog.

The chain with which the transactional object is checked and filled is defined on this workflow connection. The first part of the chain consists of derivations of the GeneratorConditionCheckCommand class, each of which checks for the relevant recurring object (for example, test definition) whether all conditions for the generation are met. The second part consists of a derivation of GenerateCommand. Here attribute values are assigned to the new transactional object, for example test case. Since these are commands, the behavior can be adapted by omitting, replacing, and supplementing.

After the chain described above has successfully completed, the transactional object is in the <state.prepared> status. This means that the generator creates the object, but the object is not yet persistent. In the second step, the generator follows the connection for which it is authorized (permission) and which leads to the first workflow status that allows manual processing by the user. In the default configuration, these are the states in which the tasks for the owner or the creator are defined.

Example for the TESTCASE object type

Command chain insertJob in the testcase catalog.

The command prepareJobMessageCommand within this second connection defines which notifications should be sent to the owner. During its cycle, the generator collects the messages from all of the created objects, combines them as far as possible and sends them to the recipients defined above.

Location

XML file in the xml folder

Procedure

  1. Copy the appropriate <catalog> from the default configuration to customizing.
  2. Adapt the command chain.

Documents

  • commandClassMapping.xml, blClassMapping.xsd,
  • commandchains_[module].xml,
  • commandchains.xsd, workflow_[module].xml