Define actions

You can define actions to be executed in relation to a state change, before (input actions), during (state actions) and after (output actions).

Actions for activities and other elements

The following actions are available for activities, artifacts and other project elements:

Create directory on drive

When the state changes, a folder is created in a directory path. The path is defined via a user-defined property.

Example: Create directory ‘Customer requirements‘ 

path-property Select a custom property of type Text.

Create Revision

When the state changes, the element or activity is versioned.

Example: Creates a revision of the current element.

Create Revision for references

When the state changes, all elements related to the element or activity are versioned. The action can be used multiple times.

Example: Create revision from ‘Requirement‘ for all elements with the relationship ‘Test case-Requirement(verify relationships)‘ 

ContextEntity Select the element type.

NavigationPath Select a relationship.

Notify editor

When a state change occurs, an e-mail is sent to the person who created or edited the element. The action can be executed more than once.

Example: Notify project staff who ‘created‘ with ‘Default text‘ by e-mail.

Default text By clicking, navigate to another dialog where you can create an e-mail to send to employees. You can add placeholders to the text, for example to provide a link to the element, the project and other properties. Use the Placeholders and Properties fields for this purpose.

‘…‘ Specify whether emails are sent to the user who created the item or to those who have since edited the item. You can see which users are the editors in the history of the respective element.

Notify assigned project staff

When the state changes, an e-mail is sent to the assigned project members. The action can be used more than once.

Example:  Notify ‘Reviews.Child review comments.Reviewer‘ with ‘Default Text‘ by e-mail.

‘…‘Select the relationship through which the project members are assigned. To select relationships, you must be assigned as a project team member.

Default text By clicking, navigate to another dialog where you can create an e-mail to send to employees. You can add placeholders to the text, for example to provide a link to the element, the project and other properties. Use the Placeholders and Properties fields for this purpose.

Notify element

On state change, the element sends an event to all elements that are related to it. The action can be executed more than once.

Example: Send from ‘Requirement‘ to all elements with the relationship ‘Parent requirements(relationship).Contained in requirement‘ the event ‘Realized‘.

ContextEntity Select the element type that is linked to other elements by a relationship.
NavigationPath Select the relationship. Event Select an event to be sent to the related items.

Notify project group

When a state change occurs, an e-mail is sent to everyone who belongs to a certain project group. The action can be executed more than once.

Example:  ‘Project manager‘ with ‘Userdefined text‘ by e-mail.

‘…‘ Select a project group from the list.

Default text By clicking, navigate to another dialog where you can create an e-mail to send to employees. You can add placeholders to the text, for example to provide a link to the element, the project and other properties. Use the Placeholders and Properties fields for this purpose.

Notify project staff

When a state change occurs, an e-mail is sent to a project member. The action can be executed more than once.

Example:  ‘Armin Röder‘ with ‘Default text‘ by e-mail.

‘…‘ Select a project member here.

Default text By clicking, navigate to another dialog where you can create an e-mail to send to employees. You can add placeholders to the text, for example to provide a link to the element, the project and other properties. Use the Placeholders and Properties fields for this purpose.

Move element

At state transition the element is moved to another package.

Example: Move element to ‘Archiv‘ (relative package/directory path).

‘…‘  Enter the path to the new destination here. The path must be created beforehand as a user-defined property of type Link in the properties. Note also the exact spelling.

Run Extension Function

At state transition an extension function is executed. The action can be executed more than once.

Example: Run Extension Function ‘Refresh identifiers‘ .

‘…‘ Enter the name of the extension function here. Note the exact spelling.

Set current user in user defined property

At state transition, the user who triggers the state change is stored in a user-defined property. The action can be executed multiple times.

Example: Set the current user in user defined property ‘Author‘.

Property Select the property. The property must be of the Type Text.

Set property

On state transition a property value is replaced by a configured value.

Example: Set ‘Priority‘ = ‘high‘.

Property Select the property whose value is to be replaced by another.

‘…‘ Enter here the value to be adopted. The value must be created in the properties and be of type Text, Boolean, Date or Enumeration. Note the exact spelling when entering the value.

Recursive renotify

When the state changes, an event is sent to an activity or the element. You can use the action if, for example, you have defined a condition for subordinate activities or child elements of a requirement and the superordinate element should only change the state if all child elements are in a defined state. The action can be used more than once.

Example: Sends the event ‘Accept‘ to itself.

Event Select the event to be sent.

Actions for elements

The following actions can be defined for various entity types: 

Add current user as staff member

The action is defined for requirements. On state change, the user who triggers the state change is assigned to the element as editor.

Example: Adds the current user as a participating staff member.

Actions only for activities

The following actions are only available for activities:

Copy workload

When the state change occurs, the workload of all assigned requirements is totaled and transferred to the activity as workload.

Example: Copies the workload from the requirement to realize.

Check activity inputs and outputs

Elements that are assigned to an activity as inputs and/or outputs are checked for their state and send an event to the activity(ies). This makes it possible, for example, to trigger the state change of an activity when inputs/outputs are in an acceptable final state.

Example: Sends the event ‘Eingabe/Ausgabe prüfen‘ to all related activity inputs and outputs.

Event Select the event to be sent.

• Eingabe/Ausgabe prüfen Here it is checked whether assigned elements are in the state “accepted” or “not accepted”.
• ActivityPortDeleted (BuildIn) Here it is checked whether assigned inputs and outputs were deleted.

Export appointments to Exchange (Version 6.1 and higher)

When the status changes, the start and end dates are entered in the calendars of the assigned employees.

Example: Exports the appointments of the activities to Exchange to the calendars of the assigned employees.

Finish activity

The action internally sets a flag (set = true; not set = false) when the state changes, for example if the target state is to be a final state. This action prevents the activity from being postponed if, for example, a predecessor activity – triggered by a calculation – changes.

Example: Set activity finished = ‘wahr‘.

‘…‘ Select a value

• true
• false

Set activity dates

The action allows you to change the start and end date of an activity. Use the action to adjust the end date of an activity, for example, if the activity ended prematurely. The action can be used more than once.

Example: Set the ‘actual start date‘ of the activity to the ‘current date‘.

‘…‘ Select the date to be changed.

• actual end date the current end date of the activity
• actual start date the current start date of the activity

‘…‘ Select the new date to be set.

• planned date The start or end date of the activity is assigned the planned date.
• current date The activity is assigned the current date as start or end date.
• current date, if the planned date is in future The activity is assigned the current date as the start date if the start date is in the future. If the planned end date is in the future, the activity is assigned the current date as the end date.

Start activity

The action internally sets a flag (set= true; not set = false) if the activity was begun.

Example: Set activity started = ‘true‘.

‘…‘ Select a value

• true
• false