Create New Upstream-Downstream Referring Items
This workflow action is the equivalent of the 
(Create Downstream Reference) menu on the Tracker Item Details page but you can also create upstream references.
(Create Downstream Reference) menu on the Tracker Item Details page but you can also create upstream references.When you select this action, you must select the following:
• The relation between the tracker item that is source or subject of the triggering event and the new items to create.
• The project in which to create new items only if there are possible target.
• The tracker in which to create new items.
In the example from Forking sub-processes from processes (work items), it shows how to use Issues for Subject in the Approvals tracker of the Workflow Demo:
The Create new referring items action has the following parameters:
• Field values (required)
• Distribution (optional)
• Association (optional)
• Propagation (optional)
• Editor options (optional)
Field values
These are the initial field values of the new items.
The field dropdown list will show all fields of the selected target tracker items that can be initialized.
Mandatory fields are automatically selected and cannot be removed.
You can use More to add fields to initialize.
You can only set fields to initial values by doing one of the following:
• Entering a constant value in the appropriate value editor.
• Setting the Content of value of a compatible field from the tracker item that is source or subject of the triggering event.
• Setting the Result of value to evaluate an expression on the tracker item that is the source or subject of the triggering event that is used to calculate the value. For more information, see Computed Fields
For example:
1. Set the priority of the new items to the priority of the tracker item that is source or subject of the triggering event.
2. Set the Assigned to entry of the new items to the owner of the tracker item that is source or subject of the triggering event.
3. Compute the Summary and Description of the new items from the first name of the designated assignee and the original summary and description of the tracker item that is the source or subject of the triggering event.
To edit a field you want to update, you can do the following:
• Click the field value you want to update.
• Click the pencil button next to the field value you want to update.
To remove a field from the update action, do the following:
• Click on the x icon after the name of the field you want to remove.
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 update operations, click on the More... button of the field update editor.
To Remove additional field value update operations:
• Click on the x icon of the field value update operation, you want to remove.
Because the order of operations is significant, you can re-order additional field value update 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 or reference fields of the tracker item that is the source or subject of the triggering event.
• If no fields are selected, which is the default, one item will be created with the configured field values.
• If one or more fields are selected, multiple items will be created with 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 the example above:
• Distribution is set to Owner of the tracker item that is source or subject of the triggering event.
• Owner is mapped to Assigned to of the new items.
Therefore, a new item will be created for each user that is referenced in the Owner field of the tracker item that is the source or subject of the triggering event. If the Owner field is empty or Owner refers to a role that has no members, no items will be created. Each new item will be assigned to one of the original item owners.
• 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.
Propagation
This is the replacement for the obsolete Association in CB-9.0 and newer.
Editor options
 | This feature is available from version 9.5. |
This section of the workflow action configuration is available only for Create and Update referring item actions. The two options:
• Open Editor: by default the workflow action creates or updates a referring item and then updates the status of the original item. If this option is checked then the referring item is not updated/created automatically. Instead Codebeamer shows the editor page prepopulated with all the field values that the user specified in the workflow action definition. If the user clicks on save on this editor page then the referring item is created/updated and the status of the original item is updated. If the user clicks on cancel on the editor then the transition is not executed, meaning that the referring item is not created/updated and the status of the original item is not updated.
• Switch to Referring Item: if this option is checked then after the referring item was created/updated by the action the new item page is loaded in the browser.