Modifying operation behavior (preconditions and follow-up actions) in project areas and team areas

You can modify operation behavior in a project area, team area, or process template by setting preconditions and follow-up actions for individual operations.

About this task

Preconditions are conditions that must be met before an operation can be completed. Follow-up actions are work items or events that are generated when the operation is completed. Some preconditions and follow-up actions are enabled by default in the predefined process templates. You can enable or disable preconditions and follow-up actions. You can specify that a precondition or follow-up action applies to specific roles in your project area or team area. You can also specify that a precondition or follow-up action applies only during certain timelines, iterations, or iterations of a certain iteration type.

Note: If multiple preconditions are specified for an operation, all of the preconditions are evaluated, even if one of them fails. This behavior ensures that users are alerted to all unsatisfied preconditions that would cause the operation to fail.

To modify the preconditions and follow-up actions for project operations and the handling of project events:

Procedure

  1. Open a project area, team area, or process template:
    • Right-click a project area in the Team Artifacts view.
    • Right-click a team area in the Team Organization view.
    • Right-click a template in the Process Templates view.
  2. Click Open. The project area, team area, or process template opens in the editor view.
  3. Do one of the following actions:
    • In a project area or process template, click the Process Configuration tab.
    • In a team area, click the Process Customization tab.
  4. Do one of the following options:
    • In a project area or process template, expand the Project Configuration or Team Configuration section. You can specify behavior at different levels in the hierarchy, as described in Table 1. Click Operation Behavior at the level where you want to modify behavior.
      Table 1. Operation behavior in the project area hierarchy
      Location of operation behavior setting Description
      Project Configuration Operation behavior at this level applies to the global project context. The behavior applies regardless of the current iteration or timeline, and it cannot be customized in specific team areas.
      Team Configuration Operation behavior at this level applies to all of the teams that belong to the project area. However, each team area can customize the behavior.
      Iteration Types Operation behavior at this level applies to all iterations of the iteration type. Each team area can customize the behavior for iteration types.
      Timelines Operation behavior at this level applies to all team areas in the timeline.
      Iterations Operation behavior at this level applies to all team areas in the iteration's timeline when the iteration is the current iteration.
    • In the Team Area editor, click the Operation Behavior section. You can specify behavior at the team area level or for specific iteration types or iterations. Click Operation Behavior at the level where you want to modify permissions.
  5. Select a cell in the Operations list. Each cell represents an operation as it is applied to a specific role.
    Note: Because all users are assigned the default Everyone role, you can have specific operation behavior apply to all users by specifying it for the Everyone role; you need not specify it for every role. At runtime, IBM® Engineering Workflow Management (EWM) checks the operation behavior settings for all other roles assigned to the user before checking the operation behavior for the Everyone role. If operation behavior is specified for one of those roles, EWM uses that operation behavior instead of the operation behavior that is specified for the Everyone role.
  6. Perform one of the following steps:
    • To set a precondition or follow-up action for the operation, select Preconditions and follow-up actions are configured for this operation. In the Preconditions or Follow-up Actions list, click Add and select a precondition or follow-up action. For preconditions and follow-up actions that allow configuration options, complete the configuration settings.
    • To disable a precondition or follow-up action, select it in the Preconditions or Follow-up Actions list, then click Remove.
    • To modify the configuration of a precondition or follow-up action that is enabled, select it in the Preconditions or Follow-up Actions list, then edit the configuration settings.
  7. To prevent child team areas, or project areas that consume the process of this project area, from overriding the precondition or follow-up action setting, select Final (ignore customization of this operation in child areas).
  8. Click Save to save your changes to the project area, team area, or process template.

    For information about creating custom preconditions and follow-up actions, see Rational Team Concert 4.0 Extensions Workshop and https://jazz.net/library/article/495.


video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki