Objects related to the task pattern

Caution: For the methodology to work properly, reference objects for the sample tasks need to be set correctly.

The task pattern almost always refers to the specific objects being processed or created within the task.

Examples

• The task pattern for performing testing refers to the tests or to the product (asset or product) to be tested.
• The task pattern for performing tests will refer to the tests; tests within the task are to be created.
• The task pattern for starting the change process refers to the project or plan for the project.
• The task pattern for processing the solution proposal will refer to the requirements.

Why the setting is important

The information to which object the task pattern refers affects when a new task can be created according to the pattern. For example, if the task is related to the tests, it is offered as a task pattern for the tests and nowhere else.

Distinguishing tasks for processing and creating objects

The system distinguishes tasks within which new objects are to be created from tasks within which existing objects are to be processed. The resolution is done by setting the value Task Type.

• If the task type is set to Create Objects, the task is used for creating new objects. The task pattern according to this type is offered for use if the user does not select any objects from the list.
• If the task type is different (typically General Task), the pattern is to process existing objects. For creating a new task, it is offered if the user selects any objects.

In both cases, the pattern is offered in the list with the objects.

What objects the task handles.

The examples in the introduction of the help describe the different variants of which objects the task pattern is to be bound to – e.g. test or asset or product. The correct object depends on how the methodology is defined:

If the methodology contains directly a workflow of testing, tests are not created within the workflow of the methodology because they are already defined by the methodology itself. This case concerns methodologies for repetitive activities, e.g. technological stoppages for maintenance purposes, or methodologies implementing standards that directly define the prescribed verification (e.g. tests that the product does not contain prohibited substances). In these cases, there will be no model task for developing the tests, there will be no tests, and the testing applies directly to the product.

If the tests are developed within the workflow of the methodology (typically a development project), it will be part of the methodology:

• A model task for creating tests with a link to the test and a flag that it is an object-creating task (type of task Create Objects).
• A second model task for performing tests with a link to the test (type of Testing), where testing will be performed according to tests created by the first model task.

Multiple objects related to the task pattern

Although this is not very common, sometimes the same task pattern is used for multiple objects. For example, tests can be performed for a product or for a specific asset. It is therefore possible to attach the task pattern to multiple objects that it relates to. The task pattern will then be offered for all selected objects.

Do not select more than 5 reference objects. The system does not support more. If it is not clear which reference objects it may relate to, do not select any.

Sample tasks without reference objects

Samples that have no reference objects are not offered for any specific objects. Tasks based on such patterns can be created using the New Task button directly in the task list of a specific project or area. They can also be created automatically based on an event.

Reference objects for automatically created tasks

If a task is created based on an event, it is assigned to a project or area that uses the methodology, but is never attached to specific objects.

Example: A project task is automatically created Perform Risk Assessment Even if there are risks in a project, the task is created with no link to those risks.