You are not logged in. Click here to log in.

codeBeamer ALM

Search In Project

Search inClear

Tags:  not added yet

Create new Upstream/Downstream referring items

This workflow action is the equivalent of the (Create Downstream Reference) menu on the Tracker Item Details page, with the extension, that you can also create Upstream references, not only Downstream references.

When you select this action from the action selector, you also have to select

  • the Relation between the tracker item, that is source/subject of the triggering event, and the new items to create
  • the Project where to create new items (only if there are possible target Trackers in other projects, than the current one)
  • the Tracker where to create new items
from the upcoming cascading menu.



In our example from Forking sub-processes from processes (work items), we choose to create Issues for Subject in the Tracker Approvals (of the current project Workflow Demo):




Create new referring items has four parameters:

  • Field values (required)
  • Distribution (optional)
  • Association (optional)
  • Reference Settings (optional, CB-9.0 and newer)

Field values

These are the initial field values of the new items to create.

The field selector will show all fields of the selected target tracker items, that can be initialized.

All mandatory fields are automatically pre-selected and cannot be removed. More... fields to initialize can be added, if necessary.

You can only Set fields to initial values. Either:

  • (a constant) Value, that you can enter/select via the appropriate value editor, or
  • the Content of an assignment compatible field from the tracker item, that is source/subject of the triggering event, or
  • the Result of evaluating an expression (on the tracker item, that is source/subject of the triggering event), that computes/calculates the value (see Calculated Issue Fields).

For example:
  • Set the Priority of the new items to the Priority of the tracker item, that is source/subject of the triggering event
  • Set Assigned to of the new items to the Owner of the tracker item, that is source/subject of the triggering event
  • Compute Summary and Description of the new items from the first name of the designated assignee (see Distribution below) and the original Summary and Description of the tracker item, that is source/subject of the triggering event

To Edit a field value, you can:
  • Click on the field value you want to change/edit.
  • Click on the Edit link behind the field value.

To Remove the initial value for an optional field:

  • Click on the ALT_WIKI:EMOTICON:%28x%29%20 behind the field value


In CB-7.9.2 and newer, you can also apply additional value operations on fields, that allow multiple values.

For example:
  • Assign the item to all Owners, except those having role Tester
    • Assigned to: Content of Owner, Remove Tester
  • Assign the item to all Owners, plus user bond
    • Assigned to: Content of Owner, Add bond

There can be also constellations with three or more operations, e.g.

  • Assign the item to all Owners, that have the role Administrator, except members of group System Admin
    • Assigned to: Content of Owner, Retain Administrator, Remove System Admin

To add additional field value operations, click on the More... button of the field values editor.




To Remove additional field value operations:
    • Click on the ALT_WIKI:EMOTICON:%28x%29%20 behind the additional field value

Because the order of operations is significant, you can re-order additional field value operations via drag-and-drop (in edit mode).


Please make sure, that you have committed all open field value editors with OK, before you save the action, otherwise the uncommitted editor values will get lost.

Distribution

This parameter controls, how many new items will be created.

The possible parameter values are multiple choice/reference fields of the tracker item, that is source/subject of the triggering event.

  • If no fields are selected (default), a single item will be created with the configured field values.
  • If one or more fields are selected, multiple items will created, one item per field value combination

For each selected Distribution field, there must also be an appropriate Field values entry, that copies this field value to a target field.


In our example above:

  • Distribution is set to Owner (of the tracker item, that is source/subject of the triggering event)
  • Owner is mapped to Assigned to of the new items

This means:

  • A new item will be created for each user, that is referenced in the Owner field of the tracker item, that is source/subject of the triggering event.
    This can also mean: No items at all, if the Owner field is empty, or Owner refers to a role, that has no members !
  • Each of the new items will be exclusively Assigned to one of the original item owners.

Please note:
In the formula/expression, to compute Summary and Description of the new items, we refer to supervisors[0] (Owner[0]) and not to assignedTo[0], as one would expect.
  • This is, because the formula/expression is evaluated on the tracker item, that is source/subject of the triggering event, and not on the new item to create.
  • When accessing a Distribution field (which is a multiple choice/reference field) in a field value formula/expression, it is guaranteed
    • that the field will yield exactly one value, and
    • that value will be different for each of the new items to create.

Association

This parameter controls, whether to create additional Associations between the newly created items and the tracker item, that is source/subject of the triggering event.

For example: Create additional associations of type depends, that should support suspected link propagation:




The default is, to not create any additional associations.

In CB-9.0 and newer, Association should not be used any more, so the value should always be None.

Reference Settings ()

This is the replacement for the obsolete Associations in CB-9.0 and newer.