Filtered Actions Overview

before start the Filtered Actions , the user need to know about Global or Scoped

Filtered actions are an extremely powerful and extensible part of the Metaflow architecture. They may be performed at a global project level or alternatively at a plan/channel level depending on how/where you invoke the action as per scoping rules.

The general principles of filtered actions follow the procedure outlined here:

User selects a number of bundles
User specifies a filter to further qualify bundles to be affected by action
User validates the bundles to affect.
User chooses action to perform on bundles.

Global / Project level

At a global level (in other words the filtered action is invoked from the plan view), the changes are applied to all bundles and any plans that they are already associated with it will show the changes. However, one additional point to note is that at this level you may also select multiple projects that are visible, and hence perform actions that affect all projects.

Scoped / Plan/Channel level

If, however, the filtered action is invoked from the plan/channel level then all actions will be stored in the appropriate deltas for that plan/channel and will not affect either the global project bundles or any other plan/channel bundles.

Filters to apply to selected Global or Scoped Bundles as explained here

Actions to apply to the Filter selected Bundles here